Okay, let's try not to get this thread cluttered up with off-topic speculation like the last one. Starting with what we know already:
There is a ~30 frames per second cap on 2D and 3D rendering. This can be established both visually (play Doodle Jump) and through a benchmark.
If you boot a Nexus One 2.2 ROM, the animation seems to run at 60FPS for a while. This, however, is not totally certain.
This seems to be a software cap, not a hard cap. However, an HTC product representative says otherwise. Jury's still out, apparently.
There is speculation that the cap might be due to the HDMI out on the graphics chip.
Kernel source is being released "soon".
There is touch sensing lag, but this seems to be unrelated.
This issue affects all EVO hardware builds and all EVO ROMs currently.
HTC claims that the cap is by design to improve battery life.
If there is anything else that you have to add that has reasonable evidence backing it up, please do.
EDITED BY TOASTCFH:
Issue of 30fps has been resolved on the devices with Epson pannels through the work done on the kernel reverse engineered kernel source provided in the thread below. for more information and source code for the fix/fixes. also a update.zip can be found on the OP for Fresh 0.3 containing a boot.img containing the kernel compiled with the fps fix.
{KERNEL-SOURCE} GoDmOdE-EVO-2.6.29 {Make Shift Kernel}
enjoy
END OF EDIT
Correct me if I'm wrong but while running fps2d, aren't there slight flashes where the fps jumps over 30? That in and of itself should prove that the cap isn't hardware based.
Krandor311 said:
Correct me if I'm wrong but while running fps2d, aren't there slight flashes where the fps jumps over 30? That in and of itself should prove that the cap isn't hardware based.
Click to expand...
Click to collapse
Very true! I'm not versed very well in the actual mechanics of the hardware, but that does sound like a good sign.
well, a good idea to see if it's a hardware cap or whether it's with the kernel is to try using toast's ported incredible kernel? since the incredible doesn't have the 30fps issue, and assuming it's software(kernel) based, then we shoudln't have that problem.
someone willing to try? sorry, i can't do this on my evo at the moment
I would try if I had the kernel made for me in zip format to flash. Since I have one of the I/O devices I would be able to try but I dont know how to make the kernel to flash.
This thread is gonna get merged...
timgt said:
I would try if I had the kernel made for me in zip format to flash. Since I have one of the I/O devices I would be able to try but I dont know how to make the kernel to flash.
Click to expand...
Click to collapse
Try one of the overclock builds. They are using toast's source. I want to think this has been tried before.
EDIT:
Seems it was tried on these builds:
RvU Rom: On android central
AOSP Rom: Avalaunch's AOSP Rom
FroYo Rom : Avalaunch's FroYo Rom
http://forum.xda-developers.com/showpost.php?p=6769032&postcount=88
Vinny75 said:
Try one of the overclock builds. They are using toast's source. I want to think this has been tried before.
Click to expand...
Click to collapse
I'm pretty sure it has and still has the same issues the board files for the evo are in there though not the incredibles
I don't think it is firmware. The RUU for the EVO and Incredible both contain the same tp_amtel224_16ab.img which may be the firmware for the Amtel 224 touchscreen controller. (http://forum.xda-developers.com/showthread.php?t=704640)
From ffolkes
i've been working on this all day. literally. about 9 hours straight.
this is what i've found. changing the mddi clk_rate to anything but 384000000 results in it getting set to 117965000 according to dmesg. now 384/20 = 19.2 which is precisely the frequency of TCXO. seems a bit odd. it's also exactly half of the other clock defined, GLOBAL_PLL at 768mhz. PLL1 (core) is also 768. another clock is defined, AXI at 128mhz, that acronym is mentioned in the video/gpu drivers. not sure if that's related to that clock, or just some video thing i'm not familiar with and completely unrelated.
changing PMDH_CLK (in devices.c) to OFF | MINMAX or just MINMAX *AND* changing the mddi freq to anything higher than 384000000 results in dmesg saying mddi was set to 235930000 (instead of 117965000) but i still get the same 30fps id get if it was at 384000000. so when you think about it, this means mddi can't be capping it, otherwise i'd see a difference between 235930000 and 384000000. but they're exactly the same fps. it HAS to be happening elsewhere.
i've also found removing the adreno200 drivers from /system/lib/egl results in a silky smooth sprint boot animation, the gui flickers crazily, but fps2d still shows 29. perhaps this is what people were seeing with the froyo boot animation looking smooth.
you know, this 29fps thing is very specific...ntsc is 29.97fps. coincidence? i really don't think so. fps2d always averages out to 29, not 30.
i also tried removing all the hdmi code in the board files, that didn't change anything.
i find it very unlikely this is hardware limited though. the gpu is on die with the cpu, so unless htc had qualcomm make them a custom chip, it's all software controlled. there's nothing to suggest the gpu has its own crystal on the pcb. i mean, if we can completely control the cpu frequency via software, the same stands to reason with the gpu.
if it was something hdmi hardware related, it should be able to be disabled in the kernel and the evo wouldn't even know it was there, just like with the sensors that don't work.
it appears the evo uses a SIL9022A for hdmi, which makes no mention of requiring any change to the lcd frame rate. (http://www.siliconimage.com/products...t.aspx?pid=150)
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showpost.php?p=6854074&postcount=664
I did a little experiment to see if the restriction was in user-space or the kernel:
- First I set up my machine like I described in the "Getting a wider set of development tools on the phone" thread
- Then I wrote a little program (attached) that suspends the phone compositing manager and wrote to the frame buffer device directly.
The conclusion: Even when writing straight to /dev/graphics/fb0, talking straight to the kernel, there's a 30fps limit.
halfline said:
I did a little experiment to see if the restriction was in user-space or the kernel:
- First I set up my machine like I described in the "Getting a wider set of development tools on the phone" thread
- Then I wrote a little program (attached) that suspends the phone compositing manager and wrote to the frame buffer device directly.
The conclusion: Even when writing straight to /dev/graphics/fb0, talking straight to the kernel, there's a 30fps limit.
Click to expand...
Click to collapse
So does this hint that it's a board driver issue and not a hardware issue? Is the fps being sent to fb0 already at 30fps? Sorry, just trying to understand. Been working on this issue for days too.
AssassinsLament said:
So does this hint that it's a board driver issue and not a hardware issue? Is the fps being sent to fb0 already at 30fps? Sorry, just trying to understand. Been working on this issue for days too.
Click to expand...
Click to collapse
I think it would be very strange if it were a hardware issue, but this test unfortunately doesn't help answer that question.
As far as I can tell, the way drawing works on the phone is... Every app communicates with this "system_server" compositor process. That compositor is what sends the drawing to the framebuffer device. The individual apps use shared memory to share what they want drawn with the compositor.
The question I was trying to answer was. Is the system_server compositor limiting the framerate, or is it the kernel? My program takes the compositor out of the picture, and just does some very fast drawing straight to the framebuffer device as quickly as possible. It measures the framerate at which the drawing is getting processed by the kernel. If I let it run for a while the output is like:
30 frames in last second, 29.7 average fps, total time 102 seconds
which leads me to believe it's definitely not the compositor (or say userspace libraries) imposing the 30fps framerate.
halfline said:
I think it would be very strange if it were a hardware issue, but this test unfortunately doesn't help answer that question.
As far as I can tell, the way drawing works on the phone is... Every app communicates with this "system_server" compositor process. That compositor is what sends the drawing to the framebuffer device. The individual apps use shared memory to share what they want drawn with the compositor.
The question I was trying to answer was. Is the system_server compositor limiting the framerate, or is it the kernel? My program takes the compositor out of the picture, and just does some very fast drawing straight to the framebuffer device as quickly as possible. It measures the framerate at which the drawing is getting processed by the kernel. If I let it run for a while the output is like:
30 frames in last second, 29.7 average fps, total time 102 seconds
which leads me to believe it's definitely not the compositor (or say userspace libraries) imposing the 30fps framerate.
Click to expand...
Click to collapse
Ok, thanks. Here is what I've tried so far:
I've taken the full stock HTC Incredible source (similar device), and just put in 9 board supersonic files into it, changed the makefile to compile those supersonic specific files and the kernel boots and everything is fine, but its still capped at 30fps. The HTC Incredible does not have the 30fps issue, so it's 1) code that I can't find in those 9 board supersonic files, or 2) Hardware capped.
That's my best thoughts for now on it
I think it has to do with the htc lock screen. The lockscreen is difficult to remove in custom roms (i haven't seen anybody do it yet) and when you run fps2d with the screen off you get 60 fps (or like 57)
Hey... you guys do know that720p LCD HDTVs display at 30Hz right? Newer ones do 240 and whatnot, but if you have an LCD monitor that's high def (like our evos), play with the refresh rate... just saying
Tilde88 said:
Hey... you guys do know that720p LCD HDTVs display at 30Hz right? Newer ones do 240 and whatnot, but if you have an LCD monitor that's high def (like our evos), play with the refresh rate... just saying
Click to expand...
Click to collapse
I don't think any one here knows that. At least anyone that has done their homework.
-Roger
hibby50 said:
when you run fps2d with the screen off you get 60 fps (or like 57)
Click to expand...
Click to collapse
If that is true, wouldn't this be evidence that it is not hardware capped?
roghaj said:
I don't think any one here knows that. At least anyone that has done their homework.
-Roger
Click to expand...
Click to collapse
I don't know what thats supposed to mean so ill ignore it...
How about trying the straight to kernel test on avalaunchs' froyo v8 with the OC revision flashed? seems like something different... custom kernel, overclocked, and the cameras not working could be a plus for the benchmark... hopefully hdmi is dead too....
Does anyone know if the hd2 has this issue doesn't it have the exact same screen and alot of the same hardware as the evo just different OS
Related
hi all -
i have seen alot of the custom roms advertize with "1ghz hack" - i like the stock 1.66 new rom but is there anyway the 1ghz hack can be made into a cab to be installed?
thanks
what is the "1 ghz hack" exactly doing?
from what I can understand,
the phone is capped below 1ghz somewhere around 700mhz, and the rom will make it go all the way up to 1ghz.
as if this info is true or not, I dont know. maybe someone else can shed some light
jgtthd said:
hi all -
i have seen alot of the custom roms advertize with "1ghz hack" - i like the stock 1.66 new rom but is there anyway the 1ghz hack can be made into a cab to be installed?
thanks
Click to expand...
Click to collapse
is your phone to slow ?
I've not come across this '1GHz hack'. I understand however that the HD2 automagically underclocks itself when it's not being used / has low battery, to save power.
While any resource-intensive application is running, the HD2 should run at full speed.
Hello
I read a lot about that, and even there is a cooked rom with title 1 GHz hack
but
I don't read any thread about "how to calculate Qualcom speed", or a an app prove that this rom has 1 GHz hack
with 3D Driver Patch we have a proof by simple app
I appreciate any one can guide us to that 1 GHz hack
but until that, I satisfied there is no 1 GHz hack
Well
I tried the 1ghz rom and it def is a lot faster with some things.
Benching the CPU gets approx 5 - 10% on the pure CPU marks.
Disk was only average. The biggest diff I noticed was launching TomTom took a flat 2 seconds where most roms are around the 3.5 seconds.
Very interested to see this in other roms.
dusty_nz said:
I tried the 1ghz rom and it def is a lot faster with some things.
Benching the CPU gets approx 5 - 10% on the pure CPU marks.
Disk was only average. The biggest diff I noticed was launching TomTom took a flat 2 seconds where most roms are around the 3.5 seconds.
Very interested to see this in other roms.
Click to expand...
Click to collapse
ok, great things, but this is tweaked things, we are talking about hacking from 700 Mhz to 1 Ghz about 50% increasing in speed, can you calculate the maximum CPU clock speed before and after this rom ??
that is what I talk about
I think its in the msm_clk.dll
Im a big noob so thats all i now ...
Just an idea:
Is it simply the fact, that the hack forces the device to always stay in 1GHz-Mode? Thinking about Desktop-CPUs they're "faster" too if you disable speedstep. If that's true you should notice a remarkable loss in battery life too.
From what I have read
On boot the CPU sits at around 1 ghz.
Once it has finished booting it tends to only hover around the 400 to 700mhz range. This is normal powersaving.
Thats why if you use coreplayer straight after a boot it will bench faster than after half an hour (Not personally tested)
The hack supposedly encourages the CPU to hover around the 400-1000ghz range.
Also its not a cab able thing, Needs to be built into the Rom as its a locked windows file.
Again, This is what I have heard. For such a great thing its not easy to pin down. Will re-flash with the Rom and test again. Will post actual bench marks.
Straputsky said:
Just an idea:
Is it simply the fact, that the hack forces the device to always stay in 1GHz-Mode? Thinking about Desktop-CPUs they're "faster" too if you disable speedstep. If that's true you should notice a remarkable loss in battery life too.
Click to expand...
Click to collapse
not true, because that is make the rom has a battery drain issue, and there is no report about it
Where can i find this hack?
--- nobody ?
It's just a hoax.
As mnet stated:
"This rumor was started single-handedly by kholk in order to promote his ROM. See this thread.
He provided ZERO evidence that HTC is lying and that the HD2 is not really clocked at 1GHZ
Then he posts a hack that has been confirmed fake.
I can't believe someone would spread so much misinformation just to promote a ROM."
For all the story, just check this thread:
http://forum.xda-developers.com/showthread.php?t=628671
seatone said:
It's just a hoax.
As mnet stated:
"This rumor was started single-handedly by kholk in order to promote his ROM. See this thread.
He provided ZERO evidence that HTC is lying and that the HD2 is not really clocked at 1GHZ
Then he posts a hack that has been confirmed fake.
I can't believe someone would spread so much misinformation just to promote a ROM."
For all the story, just check this thread:
http://forum.xda-developers.com/showthread.php?t=628671
Click to expand...
Click to collapse
WTF!?!???? How lame can you be?? There should almost be a sticky on this false rumor..
As there has been much discussion about this I thought I'd start a thread and try and get this worked out properly.
http://www.phoronix.com/scan.php?page=article&item=linux_2637_video&num=1
This 200 line patch is a subject of debate on here, some people claiming it will make a difference, some claiming it won't. Personally I don't think it will. So lets put this to bed.
A backport of this patch is available here -:
http://mirror.couttstech.com/android/bravo/kernel/taskgroup-2.6.38-backport-2.6.32.patch
Any kernel devs willing to try this are most welcome
I have built a kernel with this patch applied, that is available here -:
http://mirror.couttstech.com/[email protected]_CMBattFix_AUTOGROUP_CFQ.zip
Now, this kernel works fine for me, however, some people have reported blank screen problems. I have recompiled and re-uploaded, so if anyone could test that would be great.
Currently I am getting between 1500 and just under 1600 in quadrant with this kernel. I get slightly higher with a BFS/BFQ version on the same kernel. It does feel smooth, but so does the BFS version.
So if anyone can help test this, it would be appreciated.
*****NOTE***** I do not accept any responsibility for any damage this kernel may cause to your device.
I guess one can't see any big difference, because this patch is about Linux Desktop Machines. Their hardware and system architecture is just too different to really compare it. It might have a real effect on a desktop.
I tried your kernel. When the screen is off. I turn it on and it hang .The top of the screen have a white line and i can't do anything. back to the other kernel is ok.
Why do you think your bench score should increase?! As i understood it the patch only increases the responsivness under heavy load. So to test it, one should get the cpu to 100% load and then see if other apps/screen transition/etc are more responsive.
Well even if this patch helps then I wonder if this is still needed. I don't compile stuff or encode videos in background on my phone ;-) . Can't really think off many situations when I would have a heavy cpu load in background. Or do you compile stuff on your phone with 64 jobs while watching some vids (like in the vid of the article)?
What cpu gobernor are you using? With smartass i get a black screen, may be with other there isnt problem.
Br.
Sent from my HTC Desire
yukkio said:
What cpu gobernor are you using? With smartass i get a black screen, may be with other there isnt problem.
Br.
Sent from my HTC Desire
Click to expand...
Click to collapse
Interactive
I've been running autogroup kernel all day no with no problems.
Just changed back to BFS
melethron said:
Why do you think your bench score should increase?! As i understood it the patch only increases the responsivness under heavy load. So to test it, one should get the cpu to 100% load and then see if other apps/screen transition/etc are more responsive.
Well even if this patch helps then I wonder if this is still needed. I don't compile stuff or encode videos in background on my phone ;-) . Can't really think off many situations when I would have a heavy cpu load in background. Or do you compile stuff on your phone with 64 jobs while watching some vids (like in the vid of the article)?
Click to expand...
Click to collapse
I don't think bench should increase, and agree with everything you have said, this patch should make no difference. But some are adament that it does, hence this thread
The problem is (if I understood the patch right) that the automated taskgroup thing is based on tty. Android don't use a tty so first we need something like that Implement automated per session task groups. That should behave better (need to test it but I think it will). Maybe this is the problem and it solves the blank screen problem.
Benee said:
The problem is (if I understood the patch right) that the automated taskgroup thing is based on tty. Android don't use a tty so first we need something like that Implement automated per session task groups. That should behave better (need to test it but I think it will). Maybe this is the problem and it solves the blank screen problem.
Click to expand...
Click to collapse
Ah, excellent, I'll have a good look at that. Thanks!
Not sure about the black screen problem as I don't experience it.
Sent from my HTC Desire using XDA App
coutts99 said:
Interactive
I've been running autogroup kernel all day no with no problems.
Just changed back to BFS
Click to expand...
Click to collapse
May be the problem is the cpu governor. I will probe with interactive.
Br.
Edit: same thing, black windows.
Is it your desire slcd or amoled? Mine amoled.
Sent from my HTC Desire
yukkio said:
May be the problem is the cpu governor. I will probe with interactive.
Br.
Edit: same thing, black windows.
Is it your desire slcd or amoled? Mine amoled.
Sent from my HTC Desire
Click to expand...
Click to collapse
I'm also getting the black screen issue, a white strip at the top, and a bunch of green pixels at the bottom, but the phone is still funtioning, because when i press the volume buttons the phone responds with an audio tone and when i keep on pressing the volume down button the phone vibrates signaling vibrate only...
I was browsing the Optimas 2x forum today and ran into an awesome kernel with GPU overclock. which sounds pretty cool to me. also the dev mentioned something about overclocking "system bus" which improvers memory/2D/3D/etc. i think someone in this forum should take a look into this KERNEL and try letting us taste some of this goodness.
Here are the links:
http://forum.xda-developers.com/showthread.php?t=1119771
http://forum.xda-developers.com/showpost.php?p=14654927&postcount=36
while im no genius when it comes to this stuff, somehow i would suspect that people here are already looking into this.
i could be wrong tho lol
pyckvi said:
I was browsing the Optimas 2x forum today and ran into an awesome kernel with GPU overclock. which sounds pretty cool to me. also the dev mentioned something about overclocking "system bus" which improvers memory/2D/3D/etc. i think someone in this forum should take a look into this KERNEL and try letting us taste some of this goodness.
Here are the links:
http://forum.xda-developers.com/showthread.php?t=1119771
http://forum.xda-developers.com/showpost.php?p=14654927&postcount=36
Click to expand...
Click to collapse
The person to ask this to is Morfic. He's all about tweaking bus speeds to improve not only cpu but gpu performance as well. But much of what you've already requested has been incorporated
jlevy73 said:
The person to ask this to is Morfic. He's all about tweaking bus speeds to improve not only cpu but gpu performance as well. But much of what you've already requested has been incorporated
Click to expand...
Click to collapse
But where is he...??
G2X
CPU overclock is something that makes sense for us right now but what would a GPU overclock get us? To me thats just something that will lower the life of our phone with no real reward until games come out that our phone can't run. Right now our phone can run pretty much all games at full speed.
gpu overclocking would be sweet... now my question would be has anyone tried to load Optimas 2x kernel/software on the g2x since they are pretty much the same hardware(in theory you would think it would work)... i might even try to load this kernel onto my phone when i get home from work so if i mess anything up ill have my gear to fix it
crisis187 said:
gpu overclocking would be sweet... now my question would be has anyone tried to load Optimas 2x kernel/software on the g2x since they are pretty much the same hardware(in theory you would think it would work)... i might even try to load this kernel onto my phone when i get home from work so if i mess anything up ill have my gear to fix it
Click to expand...
Click to collapse
Please don't try to load O2x software on your G2x.
pyckvi said:
I was browsing the Optimas 2x forum today and ran into an awesome kernel with GPU overclock. which sounds pretty cool to me. also the dev mentioned something about overclocking "system bus" which improvers memory/2D/3D/etc. i think someone in this forum should take a look into this KERNEL and try letting us taste some of this goodness.
Here are the links:
http://forum.xda-developers.com/showthread.php?t=1119771
http://forum.xda-developers.com/showpost.php?p=14654927&postcount=36
Click to expand...
Click to collapse
I remember reading a while ago that GPU/System bus overclocking was attempted by some kernel dev, then later on, the dev realized through extensive testing that GPU and system bus clocks were locked, the changes to the kernel source had no effect (hardwired). Now this was a few months ago when I was reading up on Tegra kernel development before I got my G2x. Now all these could have been obsolete, and maybe now someone has found a way to do the above via kernel source updates.
Another issue that most people don't mention here and many people have been guilty of, is the GPL issue. The guy who supposedly did this overclocking has not published his kernel source code anywhere (GPL/XDA rules issues), so no one can examine what he did and prove that it worked....
GideonX said:
Please don't try to load O2x software on your G2x.
Click to expand...
Click to collapse
have you tried it yet though is my question
im not worried if i flash a kernel and it doesnt work i can reflash my old kernel if it doesnt work and gets stuck into a bootloop
crisis187 said:
have you tried it yet though is my question
Click to expand...
Click to collapse
Someone in another thread tried this and it messed up their baseband. A restore doesn't fix it apparently.
Big rush dog, the tiamat kernel guru and Guy getting engadet headlines for oc the xoom to 1.7 ghz has gpu oc in his kernels. I will be honest though, I can't tell the difference except maybe video streaming works a little smoother. I personally don't think it is worth the devs time...
Sent from my LG-P999 using XDA App
Howdy! I'm the developer of that kernel
To be honest the GPU overclocks aren't all that beneficial. There is a little bit of a speed bump (I managed to get the highest score on nenamark2 for example). But the difference is was 27fps vs 32fps. If someone is interested in incorporating that into the g2x I'll be happy to show them the changes I've made. I haven't released the source because I'm lazy but there isn't too much to it.
Actually, if you look at the voltKernel sources for the O2X you'll see the same changes there.
chuckhriczko said:
CPU overclock is something that makes sense for us right now but what would a GPU overclock get us? To me thats just something that will lower the life of our phone with no real reward until games come out that our phone can't run. Right now our phone can run pretty much all games at full speed.
Click to expand...
Click to collapse
Yes, superficial benchmarks like quadrant can be pushed to 5400 only with max cpu oc.
However, did you notice how 1.2 thru 1.5 gets you the same fps with no added benefit than more heat created?
Pushing other things other than cpu should let us remove bottlenecks and not tighten them up.
If you want your G2x to life 20yrs, 1.5ghz is not the way to go.
I have no kernel ready for release, to notice changes, I stuck to 1.5ghz, but the final result will be more likely 1.2 or 1.3ghz.
Maybe with a "don't hold my hand, give me freedom or give me death" DBU version at 1.5Ghz later.
I'm not shy to increase vcore on a SoC. But unlike the Nexus S, this thing gets HOT, fast.
Avetny pointed out that thread, I'll see if fallout hit something I have missed so far.
The clocks get compared to chip defaults in many places, choosing the smaller of the two, so it's just tedious replacing them with sane defaults, unless I stick to my current approach of offsets instead of absolutes.
We'll see.
That's also the reason I don't update my kernel often. Right now commits in cm git are only preparatory, config changes that made things smoother I already used.
I'll release something if they finish their version of BLN.
Or if I'm happy with gpu/bus/ram oc/tweaks.
not going to make people flash a kernel for no reason. As jlevy can attest, kernel not following cm git, not even based on it can work very well.
Not having latest cm commit on kernels that take another approach is not always useful.
Especially if we track regressions that cm devs back out later, that's all this gains.
So yes, there will be a gpu oc, when it's ready.
Great!
@ fallout0 thank you i hope that you can help out one of our devs on this.
morfic said:
Yes, superficial benchmarks like quadrant can be pushed to 5400 only with max cpu oc.
However, did you notice how 1.2 thru 1.5 gets you the same fps with no added benefit than more heat created?
Pushing other things other than cpu should let us remove bottlenecks and not tighten them up.
If you want your G2x to life 20yrs, 1.5ghz is not the way to go.
I have no kernel ready for release, to notice changes, I stuck to 1.5ghz, but the final result will be more likely 1.2 or 1.3ghz.
Maybe with a "don't hold my hand, give me freedom or give me death" DBU version at 1.5Ghz later.
I'm not shy to increase vcore on a SoC. But unlike the Nexus S, this thing gets HOT, fast.
Avetny pointed out that thread, I'll see if fallout hit something I have missed so far.
The clocks get compared to chip defaults in many places, choosing the smaller of the two, so it's just tedious replacing them with sane defaults, unless I stick to my current approach of offsets instead of absolutes.
We'll see.
That's also the reason I don't update my kernel often. Right now commits in cm git are only preparatory, config changes that made things smoother I already used.
I'll release something if they finish their version of BLN.
Or if I'm happy with gpu/bus/ram oc/tweaks.
not going to make people flash a kernel for no reason. As jlevy can attest, kernel not following cm git, not even based on it can work very well.
Not having latest cm commit on kernels that take another approach is not always useful.
Especially if we track regressions that cm devs back out later, that's all this gains.
So yes, there will be a gpu oc, when it's ready.
Click to expand...
Click to collapse
thanks morfic i hope everything goes smooth with your kernel, i would love to test it out once u feel it is ready. and thanks for not rushing it.
faux123 said:
I remember reading a while ago that GPU/System bus overclocking was attempted by some kernel dev, then later on, the dev realized through extensive testing that GPU and system bus clocks were locked, the changes to the kernel source had no effect (hardwired). Now this was a few months ago when I was reading up on Tegra kernel development before I got my G2x. Now all these could have been obsolete, and maybe now someone has found a way to do the above via kernel source updates.
Another issue that most people don't mention here and many people have been guilty of, is the GPL issue. The guy who supposedly did this overclocking has not published his kernel source code anywhere (GPL/XDA rules issues), so no one can examine what he did and prove that it worked....
Click to expand...
Click to collapse
You should talk to Fallout0 he seems like he got past the system bus/GPU locked issue. both of you can maybe learn something new from each other. & it would be awesome if the both of you can work on a kernel together.
Wouldn't a higher clocked G2x cause more heat? Heat being the reason this things reboots so often? Maybe a slower G2x is the way to go.
Would overclocking the gpu help run nds4droid any better? What else would ocing the gpu do? Everything seems to be very fast as it is lol
Sent from my LG-P999 using XDA Premium App
dkb218 said:
Wouldn't a higher clocked G2x cause more heat? Heat being the reason this things reboots so often? Maybe a slower G2x is the way to go.
Click to expand...
Click to collapse
Pushing cpu more I don't see useful other than keep up with your buddy's Nexus S' quadrant scores and make sure your hands stay warm in a cold Chicago winter.
I build kernels usually when things stutter or otherwise annoy me. The pushing the OC usually comes by request of those who just want more more more.
I do like to remove bottle necks.
The hardwired clocks. Well the.cpu ones are hardwired too.
The gpu/bus oc works, until boost and throttling kick in, where again values are compared to hardwired values. using offsets after the comparison would be the way around without killing boosting and throttling.
Guess main thing that stopped me is the heat at 1.5ghz, and the frowns over 1.2ghz and 1.3ghz kernels, without further "what else is in there"
Still hoping fallout can share what he/she has, it'll help making this a reality, sooner.
It's tedious. Most of all.
This is a question for devs who know more about kernels than I do. The Infuse 4G and I9000-based phones like the Captivate all have 512MB of RAM, but the Infuse 4G has a lot more of that memory available to the user and applications. I'm guessing that I9000-based phones reserve more of the RAM for specific functionality like video recording and playback.
Now for my question: is it possible to implement an I9000 kernel style of reserved memory in an Infuse kernel? I ask this because the Infuse's RAM management has resulted in unreliability of system functions (particularly video playback) under the testing I've done. In comparison, the Captivate leaves system and stock app functionality rock solid even when the RAM is loaded with background apps.
I'd much rather have ~340MB of user addressable RAM than 428MB if it allows me to watch my 1080p videos without needing to clear the memory every time.
What type of 1080p videos are you watching that's causing instability? I don't think I've ever seen anything like it... even while outputting FHD over HDMI. Then again all my videos are h.264 based.
XGX5309 said:
What type of 1080p videos are you watching that's causing instability? I don't think I've ever seen anything like it... even while outputting FHD over HDMI. Then again all my videos are h.264 based.
Click to expand...
Click to collapse
The issue isn't just 1080p. I have a post here that details all the issues. All the files in question are H.264/MKV (excluding the AC3 issue), and they all play without issue on my Captivate (except for 1080p which the Captivate doesn't support): http://forum.xda-developers.com/showthread.php?t=1292304
strychninetwitch said:
If you're having playback issues, something's wrong with your phone. I'm 100% stock and I never have video playback issues, smooth as hash oil.
Click to expand...
Click to collapse
+1 I've had the same issue before, but it was rom related, I switched rom and that problem was no more
Sent from my SAMSUNG-SGH-I997 using XDA App
strychninetwitch said:
If you're having playback issues, something's wrong with your phone. I'm 100% stock and I never have video playback issues, smooth as hash oil.
Click to expand...
Click to collapse
Go away. I post questions here because this is a developers forum. I expect posters to read and understand my post before replying, unless they need me to clarify something. If I wanted "herp derp works for me lolol" responses I would have gone somewhere else.
SMaximus7 said:
+1 I've had the same issue before, but it was rom related, I switched rom and that problem was no more
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Would you be willing to test sample videos? I don't doubt that some videos play fine on the Infuse: it came preloaded with a 1080p trailer that plays without issues. The real problem is that most of my video library that plays fine on my Captivate has major problems on the Infuse, and this happens regardless of ROM/kernel/video player. And this is not specific to a certain kind of video like 1080p.
Just like video recording, the video playback capabilities of the Rogers libraries might be gimped.
strychninetwitch - go away, you provide no constructive value to these forums. Your first post was flaming us for looking forward to official AT&T Gingerbread because it was a "minor update", yet you keep joining on on threads discussing the various deficiencies of Rogers Gingerbread.
Entropy512 said:
Just like video recording, the video playback capabilities of the Rogers libraries might be gimped.
strychninetwitch - go away, you provide no constructive value to these forums. Your first post was flaming us for looking forward to official AT&T Gingerbread because it was a "minor update", yet you keep joining on on threads discussing the various deficiencies of Rogers Gingerbread.
Click to expand...
Click to collapse
The deficiencies in question apply to the stock AT&T ROM's as well. Even though stock AT&T and Froyo have 1080p support (while Rogers doesn't), it still seems to be heavily RAM-dependent for some videos, mostly MKV's of 720p or greater, which isn't the case on the Captivate. When I get the chance, I'm going to compare some of the Captivate/I9000 and Infuse kernel source, but I was hoping for developer input about specifically the memory reservation model.
I thought the infuse had 640mb of ram? I see Wikipedia lists it at 512 now, but I had definitely heard 640 a lot.
araemo said:
I thought the infuse had 640mb of ram? I see Wikipedia lists it at 512 now, but I had definitely heard 640 a lot.
Click to expand...
Click to collapse
I've never heard the 640MB figure. That sounds pretty odd for RAM.
GGXtreme said:
I've never heard the 640MB figure. That sounds pretty odd for RAM.
Click to expand...
Click to collapse
it is just different advertising. 128 mb video ram
some Verizon adverts shoe the fascinate ad 384 mb ram. 384 + 128 = 512 total ram
the infuse has 512 system ram and another 128 video. I believe one of the kernel devs was able to verify the 640 figure.
infuse advertises system ram. sgs advertises total ram.
though the mod is sloppy and I'm sure not all of it is good maybe look at dynamic rams memory mod. but clean out all the stagfreight and other build.prop garbage. it is easy enough to remove the script if it doesn't work and it seems to resolve some flash playpack issues I had. there are also reports of it making gameplay choppy on the high end gameloft games but it couldn't hurt to try.
Dani897 said:
it is just different advertising. 128 mb video ram
some Verizon adverts shoe the fascinate ad 384 mb ram. 384 + 128 = 512 total ram
the infuse has 512 system ram and another 128 video. I believe one of the kernel devs was able to verify the 640 figure.
infuse advertises system ram. sgs advertises total ram.
Click to expand...
Click to collapse
That might be the answer I'm looking for. Although, it doesn't really explain anything. If the Infuse and the I9000 both have 128MB of reserved video memory, then filling up the RAM with background apps shouldn't affect video playback on either device. In reality, it does affect the Infuse's video playback.
GGXtreme said:
That might be the answer I'm looking for. Although, it doesn't really explain anything. If the Infuse and the I9000 both have 128MB of reserved video memory, then filling up the RAM with background apps shouldn't affect video playback on either device. In reality, it does affect the Infuse's video playback.
Click to expand...
Click to collapse
I don't know what else sammy did differntly. lets just hope they do better on 2.3.5 when it comes out.
the player still uses system ram. that video ram helps the gpu process opengl and some effects and things. I guess there is hardware acceleration on the video too but that doesn't mean it exclusively uses the video ram. there are other system and app processes involved.. I wish I knew what causes the issues but I don't. and I don't think our kernel devs watch much media and may be unaware of the issue. you are the first to report it and I don't use the videos enough to know fore sure if I have the same problem.
Dani897 said:
I don't know what else sammy did differntly. lets just hope they do better on 2.3.5 when it comes out.
the player still uses system ram. that video ram helps the gpu process opengl and some effects and things. I guess there is hardware acceleration on the video too but that doesn't mean it exclusively uses the video ram. there are other system and app processes involved.. I wish I knew what causes the issues but I don't. and I don't think our kernel devs watch much media and may be unaware of the issue. you are the first to report it and I don't use the videos enough to know fore sure if I have the same problem.
Click to expand...
Click to collapse
Hmm. I'm going to post a video demonstrating the issues better, because I'm guessing not many people here use their phone for video enough to understand the issues I'm describing. But whether or not it just affects video playback, it is a system issue and I'm interested in a fix, using the I9000 as reference (since it doesn't have any video playback issues).
hopefully linux bozo or entropy can look at it but i think they are heading in the direction of cm7 development. it would seem to be a kernel issue if even the i9000 ports are doing this.
GGXtreme said:
That might be the answer I'm looking for. Although, it doesn't really explain anything. If the Infuse and the I9000 both have 128MB of reserved video memory, then filling up the RAM with background apps shouldn't affect video playback on either device. In reality, it does affect the Infuse's video playback.
Click to expand...
Click to collapse
Get CPUspy and clear the counters before you do your testing.
I'm curious if the infuse properly scales to 1.2Ghz or if it sits at a lower speed. I've been seeing a lot of governor weirdness on mine, but I don't have a reproduceable test case, and it always happens far away from my computer. Then again, I'm running CM7, so the governor might be even weirder than on stock.
But basically, clear the timers, run your testing(try to do this on both the infuse and the i9000), and see if one is sitting mostly in lower-power states when you see the playback issues? I've seen mine loving 200Mhz while I'm actively using it, despite all sorts of interface lagginess and interaction.
Here is a video I made demonstrating the effect of memory usage on video playback on the Infuse:
Edit: Watch it on YouTube so you can see the annotations.
I'm in the process of making another one (when this camera is charged) to show that even the preloaded 1080p trailer lags when the memory starts getting full.
araemo said:
Get CPUspy and clear the counters before you do your testing.
I'm curious if the infuse properly scales to 1.2Ghz or if it sits at a lower speed. I've been seeing a lot of governor weirdness on mine, but I don't have a reproduceable test case, and it always happens far away from my computer. Then again, I'm running CM7, so the governor might be even weirder than on stock.
But basically, clear the timers, run your testing(try to do this on both the infuse and the i9000), and see if one is sitting mostly in lower-power states when you see the playback issues? I've seen mine loving 200Mhz while I'm actively using it, despite all sorts of interface lagginess and interaction.
Click to expand...
Click to collapse
I'll give this a try.
strychninetwitch said:
I've the right to post where I please. I'm telling you something is wrong with your phone if you can't play 1080p videos. It's not a memory issue and you very well know that.
Click to expand...
Click to collapse
I never said it couldn't play 1080p videos. You didn't read or understand my posts, yet you keep posting. I reported you.
strychninetwitch said:
I've the right to post where I please. I'm telling you something is wrong with your phone if you can't play 1080p videos. It's not a memory issue and you very well know that.
Click to expand...
Click to collapse
Get outta here. Grow up too
Sent from my SGH-I997 using xda premium
Dani897 said:
hopefully linux bozo or entropy can look at it but i think they are heading in the direction of cm7 development. it would seem to be a kernel issue if even the i9000 ports are doing this.
Click to expand...
Click to collapse
Could be the video libraries not supporting certain modes.
In the Froyo kernels there were configurable reserved memory sizes in the defconfig. These don't appear to be configurable in Gingerbread.
Dani897 said:
hopefully linux bozo or entropy can look at it but i think they are heading in the direction of cm7 development. it would seem to be a kernel issue if even the i9000 ports are doing this.
Click to expand...
Click to collapse
That's what I'm thinking. In Captivate/I9000 kernels, developers could make multiple options that disabled specific features (like 720p video recording) in order to give the user more RAM for apps. I'm wondering if something along those lines (but in reverse) can be done on the Infuse.
araemo said:
Get CPUspy and clear the counters before you do your testing.
I'm curious if the infuse properly scales to 1.2Ghz or if it sits at a lower speed. I've been seeing a lot of governor weirdness on mine, but I don't have a reproduceable test case, and it always happens far away from my computer. Then again, I'm running CM7, so the governor might be even weirder than on stock.
But basically, clear the timers, run your testing(try to do this on both the infuse and the i9000), and see if one is sitting mostly in lower-power states when you see the playback issues? I've seen mine loving 200Mhz while I'm actively using it, despite all sorts of interface lagginess and interaction.
Click to expand...
Click to collapse
Just did this. Both phones run at 400MHz when playing 720p content. The CPU doesn't seem to be the issue.
strychninetwitch said:
You know, looking at that video. I think, that perhaps, possibly, somehow, maybe you could press the play button and it would play?
Click to expand...
Click to collapse
You know, looking at that video, I think, that perhaps, possibly, you'd notice the video timer is counting and nothing is happening? Or that the second time around, the audio is playing but there's still no video? Or that the third time around, the video is laggy? I reported you again, and now you're going on my ignore list. Goodbye
Hey all -
I have been a Transformer (and modding) fan since my TF101, and I just leapt from a TF201 to the infinity.
I'm not sure quite what I was expecting, but I surely wasn't expecting it to be slower. Responses to screen taps and swipes are very delayed, to the point where it's extremely annoying.
This is all subjective, I realize, but I was wondering if this is a widespread thing or if I should try to RMA it.
I had heard that CROMi-X was the rom to have, so I flashed 4.6.7.
I had also heard that the GPU was an ass-kicker, so I put on my favorite piece of eye-candy (that I've purchased) which is "Asphalt 7: Heat." - and it ran DOG SLOW, and wasn't particularly candy-ish.
Well, maybe that's an exaggeration, but having the 201 and 700 side-by-side (literally, driving one with each hand, and poorly at that) the 700 was choppy and would pause every so often. It took MUCH longer to load, too.
So I was unhappy.
I read about the slow internal I/O and re-flashed with a Data2SD option, formatted the microcard, the whole nine yards, and it didn't really get any better. fsync is turned OFF.
I side-graded to the older CleanROM Inheritance 3.4.7, and it actually seems SLIGHTLY better, but the UI has a tendency to be very laggy.
I'm going to try "AndroWook" next, I had that on my Prime with good success.
I've googled and found plenty, plenty plenty of people who have a problem with the TF700 and its speed, which is really disappointing because it's supposed to be the top of the line.
So.. is anyone out there really HAPPY with their TF700? Is it zippy and satisfying? What ROM are you using?
Maybe I'll try to unload it on craigslist and go back to the TF201. It has lower "Androbench" marks, but is crazy more responsive.
*shrug*
I'd love to hear anyone's thoughts...
R
Just learned about 'lagfix.'
Gonna try that.
Is 4.1.1 better performance? I realize it'd technically be a step backwards...
rprussell said:
Just learned about 'lagfix.'
Gonna try that.
Is 4.1.1 better performance? I realize it'd technically be a step backwards...
Click to expand...
Click to collapse
I'm still using 4.1.1. I run Cromi 3.4.6 with Hund's kernel 2.2, along with most of the tweaks found here (http://forum.xda-developers.com/showthread.php?t=2232715). I am not running data2sd and my CPU/GPU profiles are not as aggressive. Apparently some people have been getting bootloops after applying these tweaks but I've never had it.
I've tried 4.2 several times (with different versions of Cromi-X) but usually come back to 4.1.1 within a day because it seems to run better.
Having said this, I think "lags" can be quite subjective - I personally think my tf700 is zippy but perhaps you wouldn't agree.
rprussell said:
Hey all -
I have been a Transformer (and modding) fan since my TF101, and I just leapt from a TF201 to the infinity.
I'm not sure quite what I was expecting, but I surely wasn't expecting it to be slower. Responses to screen taps and swipes are very delayed, to the point where it's extremely annoying.
This is all subjective, I realize, but I was wondering if this is a widespread thing or if I should try to RMA it.
I had heard that CROMi-X was the rom to have, so I flashed 4.6.7.
I had also heard that the GPU was an ass-kicker, so I put on my favorite piece of eye-candy (that I've purchased) which is "Asphalt 7: Heat." - and it ran DOG SLOW, and wasn't particularly candy-ish.
Well, maybe that's an exaggeration, but having the 201 and 700 side-by-side (literally, driving one with each hand, and poorly at that) the 700 was choppy and would pause every so often. It took MUCH longer to load, too.
So I was unhappy.
I read about the slow internal I/O and re-flashed with a Data2SD option, formatted the microcard, the whole nine yards, and it didn't really get any better. fsync is turned OFF.
I side-graded to the older CleanROM Inheritance 3.4.7, and it actually seems SLIGHTLY better, but the UI has a tendency to be very laggy.
I'm going to try "AndroWook" next, I had that on my Prime with good success.
I've googled and found plenty, plenty plenty of people who have a problem with the TF700 and its speed, which is really disappointing because it's supposed to be the top of the line.
So.. is anyone out there really HAPPY with their TF700? Is it zippy and satisfying? What ROM are you using?
Maybe I'll try to unload it on craigslist and go back to the TF201. It has lower "Androbench" marks, but is crazy more responsive.
*shrug*
I'd love to hear anyone's thoughts...
R
Click to expand...
Click to collapse
It is odd. With what you said, your TF700 should be very smooth unless there is a hardware problem Did you try a clean install? BTW, if you reinstall again, I would recommend that you should use Cromi X V4.6.5 instead of 4.6.7.
For some reason when I used the Advanced Wipe and wiped everything in TWRP. I still found some old files on my internal SD. However, when I used a formatted option, everything was gone and clean. Maybe you should do that. Also if you use Data2Ram, you should reformat your MicroSD as the same time with your clean install. A combination of Fsync Off, D2R, and Cromi X should work very well. My kernel is Hund's V3.0.6 with OC of 1.4G CPU, 520M GPU for Power Saving, 1.6G CPU, 600M GPU for Normal, and 1.8G CPU, 650M GPU for my Performance with UV about 35mV. My quandrant scores are 5800 for Power Saving = Game Mode, 6400 for Normal = Normal Activities, and 7000s for Performance = Browsing and streaming movies. Please report back if you decide to do a clean install, thanks and good lucks.
Here are my settings and quadrant scores using Hund 2.2:
Power Saving - GPU 650Mhz, CPU 1.45/1.4Ghz - Quadrant 5331
Balanced - GPU 700Mhz, CPU 1.65/1.6Ghz - Quadrant 6336
Performance - GPu 775Mhz, CPU 1.85/1.8 Ghz - Quadrant 7005
Personally I take the quadrant scores with a grain of salt because I've had setups where the scores were better but the tablet was not as responsive. I mostly run on Power Saving mode without any problems.
LetMeKnow said:
Did you try a clean install? BTW, if you reinstall again, I would recommend that you should use Cromi X V4.6.5 instead of 4.6.7.
Click to expand...
Click to collapse
Several totally clean installs at this point.
AndroWook was bust, it didn't even get past the "ASUS" logo.
I'm back to Cromi 3.4.7 with _that's kernel 3.1.10. A lot of folks are mentioning Hund 2.2, perhaps I'll try overlaying that now.
Drenus said:
Having said this, I think "lags" can be quite subjective - I personally think my tf700 is zippy but perhaps you wouldn't agree.
Click to expand...
Click to collapse
I totally agree. I added a bunch of the PimpMyRom tweaks and rebooted. I'm letting it settle down and then going to see what's what.
I can't get the GPU overclock to take, though. I think I've mounted the FS r/w and I'm editing the GPU cap files to contain 1460 as directed, but the next time I open the file it's back to 1300. Weird.
So, my Quadrant score after all the tweaks were put in, on "Balanced," is 5266. On "Performance," it's 5139.
Erugh?
rprussell said:
So, my Quadrant score after all the tweaks were put in, on "Balanced," is 5266. On "Performance," it's 5139.
Click to expand...
Click to collapse
Strange. I get 5200 in balanced mode without any special tweaks, and over 6000 in performance mode with fsync off.
The general user experience is acceptable, but not exceptionally smooth - lost frames in animations are common, but there are no long waiting times anywhere.
_that said:
Strange. I get 5200 in balanced mode without any special tweaks, and over 6000 in performance mode with fsync off.
Click to expand...
Click to collapse
Did I mention I also have fsync off?
('Coz I do.)
Maybe it's faulty, which would make me sad because I doubt I can return it what with unlocking and flashing the crapola out of it. Hm hm.
rprussell said:
I can't get the GPU overclock to take, though. I think I've mounted the FS r/w and I'm editing the GPU cap files to contain 1460 as directed, but the next time I open the file it's back to 1300. Weird.
So, my Quadrant score after all the tweaks were put in, on "Balanced," is 5266. On "Performance," it's 5139.
Click to expand...
Click to collapse
That is really odd. Unfortunately my knowledge of tweaking is entirely based on following other people's instructions so I don't know why the GPU changes are not taking. Are your CPU changes taking? Did you follow the instructions on init.d scripts/enabling his voltage table and governor tweaks?
Here's are my cpu.sh files. I switched the profile for powering saving mode and balanced mode because the tablet always defaults to balanced mode.
-----------------------
Also, when I made the profile too aggressive (too high on CPU or GPU), the tablet got way hot and my quadrant score dropped. Since our tablets are all different on the amount of overclocking they can handle, maybe you're pushing your tablet too much. Have you tried easing down on overclocking?
Drenus said:
Here are my settings and quadrant scores using Hund 2.2:
Power Saving - GPU 650Mhz, CPU 1.45/1.4Ghz - Quadrant 5331
Balanced - GPU 700Mhz, CPU 1.65/1.6Ghz - Quadrant 6336
Performance - GPu 775Mhz, CPU 1.85/1.8 Ghz - Quadrant 7005
Personally I take the quadrant scores with a grain of salt because I've had setups where the scores were better but the tablet was not as responsive. I mostly run on Power Saving mode without any problems.
Click to expand...
Click to collapse
LOL I totally agreed with on that. :laugh: However, I still think that it is better with some numbers as references others than words lags, smooth, choppy, slow, fast, and so on. :good: It is just my way of explanations.
This might be my final entry - after doing the PMR tweaks, and flashing Hund 2.2 (no offense, _that ) the Quadrant score in Performance mode is ... uh.. well, indeterminate because suddenly I can't attach to our wifi. Sigh. Perhaps I overtweaked.
Although, Asphalt ran VERY smoothly. I credit the GPU overclock, in combination with assigning all the 2D stuff to the GPU.
Yeah, definitely. After flashing hund 2.2, it won't acquire an IP address.
Today is surely an interesting day.
rprussell said:
This might be my final entry - after doing the PMR tweaks, and flashing Hund 2.2 (no offense, _that ) the Quadrant score in Performance mode is ... uh.. well, indeterminate because suddenly I can't attach to our wifi. Sigh. Perhaps I overtweaked.
Although, Asphalt ran VERY smoothly. I credit the GPU overclock, in combination with assigning all the 2D stuff to the GPU.
Yeah, definitely. After flashing hund 2.2, it won't acquire an IP address.
Today is surely an interesting day.
Click to expand...
Click to collapse
You probably have problems because of PMR tweaks I remember I also had wifi issues after PMR and I think I didn't enable all the tweaks in the guide. Try PMR recovery where it restores all your previous settings-it should restore your wifi. If not, then maybe a clean install of Cromi and then doing the init.d/Hund/CPU/GPU tweaks should give you quite a bit of performance boost.
Hope by "final entry" you don't mean you're giving up!
Drenus said:
You probably have problems because of PMR tweaks I remember I also had wifi issues after PMR and I think I didn't enable all the tweaks in the guide. Try PMR recovery where it restores all your previous settings-it should restore your wifi. If not, then maybe a clean install of Cromi and then doing the init.d/Hund/CPU/GPU tweaks should give you quite a bit of performance boost.
Hope by "final entry" you don't mean you're giving up!
Click to expand...
Click to collapse
Yeah, it seems as if the "Fast DNS" internet tweak means it has somehow thrown off DHCP.
I'm connected to the wifi AP, but I get no IP address, etc.
I guess I'll flash the recovery thing. Darn, everything but that was working great
No, I had meant to say 'final entry' insofar as I was finally happy with it - but while i was typing it, I wanted to put in the Quadrant score, and then I realize I couldn't connect to the website, and then I realized I had no IP, and here we are.
So that post sort of morphed as I was typing...
rprussell said:
I guess I'll flash the recovery thing. Darn, everything but that was working great
Click to expand...
Click to collapse
Huh.
Wont' flash, at least not with twrp 2.4.4.0
Growf.
rprussell said:
Huh.
Wont' flash, at least not with twrp 2.4.4.0
Growf.
Click to expand...
Click to collapse
Which is just as well, since when I rebooted I had an IP again.
Recovery image went south too, and I had to re-flash that via adb.
There is truly some weird stuff happening here.
Anyway, the quadrant score - now on "Performance" because I swapped cpu2 and cpu3, what a great idea - is...
IS.....
IS.....
5057.
Ah, the hell with it.
rprussell said:
Which is just as well, since when I rebooted I had an IP again.
Recovery image went south too, and I had to re-flash that via adb.
There is truly some weird stuff happening here.
Anyway, the quadrant score - now on "Performance" because I swapped cpu2 and cpu3, what a great idea - is...
IS.....
IS.....
5057.
Ah, the hell with it.
Click to expand...
Click to collapse
Wow, that is just odd. Does the tablet get really hot when you run quadrant? It might be that the GPU/CPU settings are too high. Hope actual performance is still working out for you.
And as for recovery, I meant running the rescue package inside PMR that "un-pimps" the rom. Thinking back on when I installed the tweaks, I think I did everything mentioned in PMR except for Network & Internet mods. And I love the xloud mod!
Drenus said:
Wow, that is just odd. Does the tablet get really hot when you run quadrant? It might be that the GPU/CPU settings are too high. Hope actual performance is still working out for you.
And as for recovery, I meant running the rescue package inside PMR that "un-pimps" the rom. Thinking back on when I installed the tweaks, I think I did everything mentioned in PMR except for Network & Internet mods. And I love the xloud mod!
Click to expand...
Click to collapse
It was pretty warm, yeah. I knocked the cpu back from 1900mhz to 1800mhz - which doesn't seem to matter since according to the little floating CPU monitor I have ("Cool Tool") it's never going over 1600mhz anyway.
I mean, I've got PMR trying to control stuff on one hand, the built-in "Power Saving/Balanced/performance" thing on the other, and also "Trickster Mod"
Idunno.
It does seem perkier after all this, so maybe it doesn't matter.
I wish Quadrant would let me see my score without hitting the internet though. I backed off the voltages by 0.025v per speed, and came up with 5499 this time. Although I don't know whether that's "performance" or what.
rprussell said:
It was pretty warm, yeah. I knocked the cpu back from 1900mhz to 1800mhz - which doesn't seem to matter since according to the little floating CPU monitor I have ("Cool Tool") it's never going over 1600mhz anyway.
Click to expand...
Click to collapse
Did you use Hundsbuah's app to set whatever parameters need to be set?
Sorry for not being more specific, I have no experience with it, I just know Hundsbuah didn't only add awesome overclocking features into his kernel, but he also wrote an app to control it.
rprussell said:
I mean, I've got PMR trying to control stuff on one hand, the built-in "Power Saving/Balanced/performance" thing on the other, and also "Trickster Mod"
Click to expand...
Click to collapse
And this is in addition to changing cpu#.ch files? I wonder if you've got too many cooks in the kitchen.
rprussell said:
It does seem perkier after all this, so maybe it doesn't matter.
I wish Quadrant would let me see my score without hitting the internet though. I backed off the voltages by 0.025v per speed, and came up with 5499 this time. Although I don't know whether that's "performance" or what.
Click to expand...
Click to collapse
Is Asphalt still running better than before? I think the most important thing is that the applications you use are running smoothly and not upsetting you that (1) you spent $$$ on the tablet, (2) you spent a lot of time tweaking the tablet, and (3) you're not getting the performance you want.
I once spent a few hours tweaking CPU/GPU to figure out how I can maximize Quadrant score and what I came away from it is that high score doesn't matter if the tablet is getting way to hot for comfort and that low score doesn't matter if the tablet is running to my satisfaction. I almost never change my power setting and that means my score is probably around 5300, but I still like how the tablet responds.
Anyways, hope your tablet's running better than before and good luck with any additional tweaking! :victory:
_that said:
Did you use Hundsbuah's app to set whatever parameters need to be set?
Click to expand...
Click to collapse
Well.. that's just madness.
No, I was not. I had these other tools and was messing with those.
Might be time to re-flash the kernel again.