Ive noticed that every single ROM has this line in their build.prop has this
#Modify MTU from 1500 to 1472 on 3G network
ro.ril.set.mtu1472 = 1
why would I want a lower MTU, that can cause a higher ping rate and limit BW, sure it can be helpful for people with ****ty data signal... but... "Im in Miami, *****"
Anyways... A little insight on this? I usually remove the whole line or set to 0.
Tilde88 said:
Ive noticed that every single ROM has this line in their build.prop has this
#Modify MTU from 1500 to 1472 on 3G network
ro.ril.set.mtu1472 = 1
why would I want a lower MTU, that can cause a higher ping rate and limit BW, sure it can be helpful for people with ****ty data signal... but... "Im in Miami, *****"
Anyways... A little insight on this? I usually remove the whole line or set to 0.
Click to expand...
Click to collapse
1472 mtu sounds like it has been adjusted to allow the ip overhead in an ipsec tunnel.
if youre phone had the ability of a cisco 2811 and could send 120-160,000 packets a second, then i would fret the 28b. with your phones processing power, you may gain <1kb per second....
Also, this has nothing to do with ping rate nor does it limit your bandwidth. it is only the size of each packet that is leaving the interface. it may cause a 1500 byte ping to fail, or in the case of a packet, it will defragment it. bandwidth is more or a ppsxmtu than mtu alone. If a cell phone user was having to retransmit packets due to corruption or loss from a weak signal, what is the difference in MTU supposed to help? Having a smaller MTU in cases of tcp resync or retransmit, will cause more PPS which actually clogs up the buffer quicker than sending a bigger packet. Its not the size, but the number of packets it can send a second that is gonna make the difference.
welrope said:
1472 mtu sounds like it has been adjusted to allow the ip overhead in an ipsec tunnel.
if youre phone had the ability of a cisco 2811 and could send 120-160,000 packets a second, then i would fret the 28b. with your phones processing power, you may gain <1kb per second....
Click to expand...
Click to collapse
lol a kilobit isnt necessarily my worries... im looking to lower latency...
and what about reverse tunneling... wouldnt that play nicely with 1500units...
i remember in WinMo we had our MTUs at 1500... i would play halo on XBL no lag... and on a TP2 with 528mhz CPU and a way lower milliwat[ted] antenna
Tilde88 said:
lol a kilobit isnt necessarily my worries... im looking to lower latency...
Click to expand...
Click to collapse
I wouldn't expect it to hurt no more than having a 1472 might actually help. Depends on the media (ethernet,dsl,frame-relay,oc,ds,and serial links all have varying MTU's. So what works for some may not work for others. If you really are after latency, then i would set my mtu to 1200, test latency and make 20-40 byte jumps till i found my sweet spot.....and i doubt it will be 1500.
welrope said:
I wouldn't expect it to hurt no more than having a 1472 might actually help. Depends on the media (ethernet,dsl,frame-relay,oc,ds,and serial links all have varying MTU's. So what works for some may not work for others. If you really are after latency, then i would set my mtu to 1200, test latency and make 20-40 byte jumps till i found my sweet spot.....and i doubt it will be 1500.
Click to expand...
Click to collapse
lol so very true.... thanks for that... its only logic! lol dont know how i didnt think to start low
Tilde88 said:
and what about reverse tunneling... wouldnt that play nicely with 1500units...
i remember in WinMo we had our MTUs at 1500... i would play halo on XBL no lag... and on a TP2 with 528mhz CPU and a way lower milliwat[ted] antenna
Click to expand...
Click to collapse
It would still depend on the media and the protocol used to transmit across the media. Example. If you're packet leaves your phone at 1500byte, and travels to Raliegh, NC-You will more than likely travel through several providers. Level 3, sprint, twt, and maybe a few locals/ If one of them paths has an mtu set lower than your 1500, that packet will get fragmented into smaller pieces and reconstructed at the other end. If that is the case, you will get better latency with an MTU that is smaller than the lowest hop's MTU. Also, some equipment reaches peak performace at a certian size MTU, and its not always 1500. And also,,,it depends on the traffic you are sending. It also depends on the size of the packet that the app on your phone is generating as well. . So there is a whole lot of variables that play into MTU size, and more i didn't mention.
Tilde88 said:
lol so very true.... thanks for that... its only logic! lol dont know how i didnt think to start low
Click to expand...
Click to collapse
Do let me know what ends up working for you!
Glad i could help
welrope said:
Do let me know what ends up working for you!
Glad i could help
Click to expand...
Click to collapse
lol i prob wont even bother... just a tweak freak...
if only setprop (command) didnt require reboot... any way around?
Tilde88 said:
and what about reverse tunneling... wouldnt that play nicely with 1500units...
i remember in WinMo we had our MTUs at 1500... i would play halo on XBL no lag... and on a TP2 with 528mhz CPU and a way lower milliwat[ted] antenna
Click to expand...
Click to collapse
I have had a lot of issues lately on the 1.4 pri as well as the earlier on with ****ty signal strenth with some roms. I swear, im in downtown GBO, and with CM nightly, my signal is -80dbm, and with any htc rom, same spot gets me -60 with full bars. Some roms drop calls on the way home when switching from tower to tower, some roms don't. But damn, even with no 4g, and crappy signal, CM has been my daily driver for about 3 weeks now....
welrope said:
I have had a lot of issues lately on the 1.4 pri as well as the earlier on with ****ty signal strenth with some roms. I swear, im in downtown GBO, and with CM nightly, my signal is -80dbm, and with any htc rom, same spot gets me -60 with full bars. Some roms drop calls on the way home when switching from tower to tower, some roms don't. But damn, even with no 4g, and crappy signal, CM has been my daily driver for about 3 weeks now....
Click to expand...
Click to collapse
dude I know exactly what you [email protected]!
srsly how the hell can a rom do that... perhaps they are doing like apple? using a 'bad formula to display signal strength' lol.
Maybe they modded their fieldtrial
**** i gotta go bbl bro
Anything old that is left in a modded rom or residual or even introduced into a new rom cleary stands a chance of screwing things up.
This is just common sense really.
You never introduce old code into new code and expext equal results unless bit for bit the old and the new code are identical.
There is also the theory that by modifying a rom it can break things.
Then again a flakey phone could do the same thing.
That was with regards to the pri 1.4 comment.
With regards to the MTU... any mtu will work as long as it is a match all along the way. But as it was stated if there is a change it could be fragmented.
Im a little rusty but thee are commands or rather homemade programs to test for mtu limits/point of dragmentarion.
Every single 1500 mtu is really 1472 underneath the overhead if i remeber correctly. Add 28 for the headers???
It may be very very well worth changimg it to 1500 and trying it out.
Now days mtu wont kill speeds or ping unless it is way off.1472 isnt going to be.much different than 1500 but it could verywell create issues sometimes.
Here is a link on dslreports to test for best mtu. Not sure how we can do this on our phones
Sent from my PC36100 using XDA App
Not to sure what all that was about..
1. If there is any residual code or modded code in my rom, it was put there by cyanogen. Also, I think most.people could tell a flacky phone. Point blank..stand in one location with ANY HTC based rom and have neg65 signal. Flash cyanogen it my go into 1x. Its simply a incompatibility between his code and sprints pri.
2. 1500 includes all the over head needed when using Ethernet. DSL uses 1492, due to the overhead of the "timing bits. Ipsec tunnel uses 1472 to allow for the IP header in the tunnel....over Ethernet. Most of this has already been discusses in the thread anyway.
Feel free to search any of CM threads for countless others with the same issue.
Sent from my PC36100 using XDA App
Related
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
I have an Inspire that is rooted,and after 5 different Roms for1 day each, I have settled into the revolution ROM and it really works great.I have my unlimited plan4G (most of the time I think)and I have my tendering. My question is when running the "sweetest.com" application I get 331 down and 783 up inthe evening and 2592 down and 1447 up in the morning until about noon,is this network congestion? Is there a different radio mod or flash or something that software locks the radio in HSUDA mode or whatever is making it that fast?? If anyone knows of a setting or .apk that addresses this or a setting possibly I would appreciate it,or an explanation if its not a tweakable thing might save hours of obsessing over trying to fix it.Thanks, Vegas
Sent from my Desire HD using XDA App
Yeah, the slow speeds at times are due to all the iphones tying up the network.
newter55 said:
Yeah, the slow speeds at times are due to all the iphones tying up the network.
Click to expand...
Click to collapse
Funny, but I notice my speeds do the same. But most of the time it's relatively good.
I definitely think this is network congestion. My best speeds are late at night (usually about 2.5 down/1.5 up). Most of the time my upload stays about the same (between 900k and 1.5mb), but my download goes anywhere from 400k to 2.5mb..or lower
So 2.5 down is the fastest I can expect and the radio with the Revolution ROM is the Best one I could be using? I have heard 4G was capable of 6mbps,No..Anyone?? Is it gonna get better in phases,anyone know the truth?Vegas
I have this in my review post but wanted to call it out separately to see what others are experiencing. My G2’s best speedtest.net score is 10289 down and 1582 up. The average is in the mid-8’s down and about 1.2mb up. The best score on the G2X is 7013 down and 1263 up. Average is in mid-6’s down and 1mb up. I took the tests at the same time and after the G2X was loaded with the identical apps and configuration that was on my G2. I know both sets of numbers are good compared to some areas of the country, but if the percentage of degradation is the same everywhere the slower the connection the worse the G2X will perform compared to other T-Mobile 4G phones. I'm guessing it's either LG's implementation of the radio hardware and/or software. I'm hoping it's the latter which can be fixed via an update.
I got 8 at tmobile where the myt4g only got 6... Id say its good..
different days have different uses and network clog, one days worth of testing wont prove enough.
try at night, and again tomorrow
xguntherc said:
different days have different uses and network clog, one days worth of testing wont prove enough.
try at night, and again tomorrow
Click to expand...
Click to collapse
They were done side by side. So any network congestion would have effected both equally. They're also configured identically, unlike units tested in a store which are stock.
Wow you guys are lucky, I was getting 3 down on the G2 and am getting about 4.5-5 down on the G2x
7 down seems fine enough to me on a mobile phone.
Anyways point being i'm seeing higher speeds locally on my 2x compared to my G2, so who knows.
I get anywhere from 4-7 MB/s down and a solid 2.5-3 Up on my MT4G in vegas..
I'd check my G2x speeds but I boxed it up and it's going back because backlight bleed issue is worse than most I've seen here. Hopefully the next will be a little better.. I can live with a little, not a lot.
Maybe I'm alone in this, but I don't really care if my phone is pulling 2mbps or 10mbps. When I'm surfing the web, everything loaded quickly. When I installed Dungeon Defenders, the update was done downloading in around 5 minutes. Considering it was over 100mb, that's more than acceptable to me.
Does tmo charge extra for 4g like sprint or veriz?
That would upset me if i paid for it. If not then........
Sent from my GT-I9000 using XDA Premium App
mr.orange303 said:
Does tmo charge extra for 4g like sprint or veriz?
That would upset me if i paid for it. If not then........
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
No they don't...
My Lg G2X is getting on average 7mb DL and 1.5mb UL. My MyTouch 4G is getting 6mb DL and 1.3mb UL. Same apps, time and location. The LG G2X is faster.
smashpunks said:
No they don't...
Click to expand...
Click to collapse
But Its also capped at 5GB and then goes to dial up speed after the 5GB, where as on Sprint %100 unlimited.
Oh c'mon.......
I'm starting to agree with the "I turn my phone on vibrate and won't cut my chicken" guys.
This thread is just ridiculous. Seriously are you TRYING to find things to complain about. These silly data rate comparison threads come up every time a new official rom is released for any phone as well. One guy says it's far worse than before, the next guys says it's the best ever!!! The point is, unless you want to continue your little test in 100 different locations at 100 different times of the day, you're not doing a reasonably analytical test. This is why no two people will ever agree on the results of one persons "scientific" test.
I'm sure the results are "real" to you, but they don't really matter to anyone else.
MWBehr said:
This thread is just ridiculous. Seriously are you TRYING to find things to complain about...
Click to expand...
Click to collapse
First, here a quote from the TechCrunch review:
A quick note on the network speed. The G2x is, like the G2, kitted out for T-Mobile’s “4g” HSPA+ network. The G2 got around 9Mb/s down in my neighborhood, with around 3Mb/s up. The G2x reliably goes at half that rate – between 3 and 5 megabits down and around 1.5 up. Not exactly the lightning-fast advertised speeds, but they were fairly consistent and for all the usual uses it was quite fast – loading pages and games in the browser or downloading apps, that is to say.
So, I'm not crazy. And to expect T-Mobile's self-proclaimed flagship to outperform an older slower phone (the G2) isn't an invalid expectation. Having a super fast processor and a slower connection nets you about the same performance as a slower processor and faster connection when streaming video. My G2 actually plays Hulu faster than my G2X over 4G. On top of that, the G2X is silly fast over Wi-Fi so it's not the phone, it's the implementation of the radio. I like the phone but I'd really like to see it reach its full potential. If you (or anyone else) are fine with it the way it is then you should really have no interest in this thread anyway.
It's Tmobile... not the phone.
Sent from my LG-P999 using Tapatalk
BarryH_GEG said:
First, here a quote from the TechCrunch review:
A quick note on the network speed. The G2x is, like the G2, kitted out for T-Mobile’s “4g” HSPA+ network. The G2 got around 9Mb/s down in my neighborhood, with around 3Mb/s up. The G2x reliably goes at half that rate – between 3 and 5 megabits down and around 1.5 up. Not exactly the lightning-fast advertised speeds, but they were fairly consistent and for all the usual uses it was quite fast – loading pages and games in the browser or downloading apps, that is to say.
So, I'm not crazy. And to expect T-Mobile's self-proclaimed flagship to outperform an older slower phone (the G2) isn't an invalid expectation. Having a super fast processor and a slower connection nets you about the same performance as a slower processor and faster connection when streaming video. My G2 actually plays Hulu faster than my G2X over 4G. On top of that, the G2X is silly fast over Wi-Fi so it's not the phone, it's the implementation of the radio. I like the phone but I'd really like to see it reach its full potential. If you (or anyone else) are fine with it the way it is then you should really have no interest in this thread anyway.
Click to expand...
Click to collapse
Well i think any potential buyer wikl check out this thread. My vibrant was horrible with reception.
My old g1 got double the signal.
So ill report my findings tomorrow and hope its better than my vibrant.
Sent from my GT-I9000 using XDA Premium App
I have the G2x for the 14 day trial period to test it out and see if the network suits my needs (possibly switching from Verizon). I never really speed tests this often, but I feel it is necessary so I can get an idea of the speeds based on my frequent locations. Verizon is too slow in some key areas for me.
I was surprised to see people talk about 7mb down on T-Mobile, because on the G2x for the few days I've had it, I have yet to see more than 1.5mb down. This is in all different areas and with a full 4G signal. One time a full signal on 4G was much slower than 1 bar of 4G - that never made sense to me? The phone stays on 4G pretty much all the time and even with a full 4G signal, I average about 500kbs down.
I'm hoping it's the phone/software... because if the network performs better than what it does now, I would be much more impressed with the network and would be more inclined to switch. It seems to work okay with basic browsing, but at times it does show that it's slow (like when downloading apps from Market).
Well coming from evolution on sprint I am 100% happy. No BS I was getting .12mbps on sprint 3g and on the rare occasion I got 4g I would avg around 6. But 4g was really limited in the dfw area and battery life was garbage. I'm running cm7 with stock kernal.
With the g2x for the first few days I'm getting 5-7mbps with peaks of 11. And the battery life is immensely better. I haven't transferred my acct from sprint because I wanted to test and so far I'm blown away.
Sent from my PC36100 using XDA Premium App
Found and interesting article and i thought i'd throw it out there. Basically when it comes to quadrants you will have two very polarizing point of views. You will have those that LOVE the program and they must test everything. And those that swear never to use it. But i found an interesting command line from the CMD prompt.
Code:
mount -t tmpfs tmpfs /data/data/com.aurorasoftworks.quadrant.ui.standard
Long story short it mounts the Quadrant Standard application on the RAM of the phone so you can get a true reading. Since the I/O is what bottle necks everything
I ran three test with the QS after three test i got a high of 2528, and a low of 1918. 610 point difference. Not to shabby for running CM7N75 O/C'd to 1516 with a performance governor
Then i mounted QS on the RAM of the phone and ran three test. The highest being 2997 and the lowest being 2785. 212 point difference.
just throwing out some food for thought.
Why do people always cry about Quadrant? those lil silly numbers means nothing I love how all the idiots who review the roms and make videos always do it and gives general public this idea that its real.
5th March 2011 said:
As I said before as syntactic benchmark means nothing as it does not translate in to real world performance. If someone wanted to really inflate it lol they wouldn't have to do much other than allocate it on tfs or ram as they will get higher score on I/O and R/W which will inflate the score which is very easy to spot as its never consistent with regular.
Click to expand...
Click to collapse
UsrBkp said:
Why do people always cry about Quadrant? those lil silly numbers means nothing I love how all the idiots who review the roms and make videos always do it and gives general public this idea that its real.
Click to expand...
Click to collapse
first and foremost - personal attacks aren't needed, wanted, or warranted.
I am sorry if you thought I personally attacked you but I assure you that was not the case. As I was speaking more in general, but what I said still stands.
UsrBkp said:
I am sorry if you thought I personally attacked you but I assure you that was not the case. As I was speaking more in general, but what I said still stands.
Click to expand...
Click to collapse
I know you weren't coming after me. But still in general. We are here to help one another and expand horizons. Not belittle each other.
UsrBkp said:
Why do people always cry about Quadrant? those lil silly numbers means nothing I love how all the idiots who review the roms and make videos always do it and gives general public this idea that its real.
Click to expand...
Click to collapse
I personally don't use quadrant, but any time someone talks about performance they can either post quadrant/linpack results, or they can say "it's really fast." You can't call someone who posts quadrant results an idiot unless you call anyone who has ever commented on a phone's performance an idiot. We talk about this stuff all the time, no need to demean anyone unless you have the one-stop end all of performance gauges.
I love it when people talk and talk and talk but they never listen. As once again the message was lost, which still exist on the original message. I don't know where he got the idea I was attacking him as that maybe some type of paranoia or delusion.
darinmc that will never happen due to the different hardware archstructure. Even when device is using ARMv7 the instruction set is interpreted differently from manufacture to manufacture. Great example is Snapdragon vs Hummingbird where NEON is utilized to improve the IOPs. If its allocated on top of davlik it can be cheated its simple as that.
UsrBkp said:
I love it when people talk and talk and talk but they never listen. As once again the message was lost, which still exist on the original message. I don't know where he got the idea I was attacking him as that maybe some type of paranoia or delusion.
Click to expand...
Click to collapse
Sorry for the typo
i guess that " n't " means alot. Sorry again.
Quadrant has become very popular with people to see where their phones stand performance wise, but at times I find it not to be the most accurate...Unlike Neocore or Linpack which I think are better ways to test GPU/CPU instead. The scoring system may need some work to make it balanced. Personally I think it needs work, earlier I tried Faux's Ginger rom and it scored about the same as the stock MT4G rom...This is clearly odd since the ginger is lighter and actually has a much much smoother experience and higher response times. Quadrant doesnt deal with real world usage. Feel free to disagree if you feel differently.
how about smartbench, is that any better than quadrant?
clarknick27 said:
how about smartbench, is that any better than quadrant?
Click to expand...
Click to collapse
From what I seen Quadrant favors Snapdragon while Smartbench favors Hummingbird. But try GLBenchmark thats what we mostly use as its more comprehensive.
"As I said before as syntactic benchmark means nothing as it does not translate in to real world performance." - HKM
UsrBkp said:
From what I seen Quadrant favors Snapdragon while Smartbench favors Hummingbird. But try GLBenchmark thats what we mostly use as its more comprehensive.
"As I said before as syntactic benchmark means nothing as it does not translate in to real world performance." - HKM
Click to expand...
Click to collapse
thanks Ill give it a shot
UsrBkp said:
From what I seen Quadrant favors Snapdragon while Smartbench favors Hummingbird. But try GLBenchmark thats what we mostly use as its more comprehensive.
"As I said before as syntactic benchmark means nothing as it does not translate in to real world performance." - HKM
Click to expand...
Click to collapse
Hahahaha, where have you been? Thought you retire drop by Sensation section help me out with the SamSux troll over there
Sent from my HTC Vision using XDA Premium App
epsix said:
Hahahaha, where have you been? Thought you retire drop by Sensation section help me out with the SamSux troll over there
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
LOL I see people still recognize me. I mean hopefully "they" don't know you know who, as ill try to keep low profile for now. Only reason I came back was due to the recent interest in "fail-pu" which I was trying to shed some lights in here few months back and got myself you know what in CM7NB thread. Hopefully "they" don't go crazy and start issuing you know what as originally ordered by the 2 heads. I am sure MT4G community will suffer if they do it, I mean here I hacked the mmcblk and posted the info and risked my device to help others yet Mr New.Sheriff wanted to show himself as the big man. Oooh well ill help ya much as I can and look in to the Sensation section.
What makes you think that mounting the application in RAM (thus minimizing I/O interactions) gives you a "true reading"? It's not like all your applications are stored in RAM. They access the file system also. So the speed of your phone's filesystem obviously affects the overall speed of the phone and should be included in a good benchmark. Unless you're only interested in comparing CPU/GPU speeds.
sundayhustler said:
What makes you think that mounting the application in RAM (thus minimizing I/O interactions) gives you a "true reading"? It's not like all your applications are stored in RAM. They access the file system also. So the speed of your phone's filesystem obviously affects the overall speed of the phone and should be included in a good benchmark. Unless you're only interested in comparing CPU/GPU speeds.
Click to expand...
Click to collapse
I don't think anyone in this thread said allocating it to tfs gives true reading. All the OP was doing was posting how one can easily hack the score. Its which we known ages ago but the point was when you make an standard everyone must follow it. So obviously if you allocate the whole ROM in RAM instead of NAND or SDCard the IOPs will always be higher.
If its software it can be altered simple as that and someone will always do so and try to pretend they have the legit score but for people like me we can easily tell what is real and what is fake. The legit max score verified by me was 3618 I think without any type of hack all I did was strip the rom and made it cleaner. Which you folks can get around 3200-3400 using AOSP with no problem. Now if you scoring 3800-4000 then well you know whats going on. I am not going to name folks but come on they aint fooling anyone.
neidlinger said:
Found and interesting article and i thought i'd throw it out there. Basically when it comes to quadrants you will have two very polarizing point of views. You will have those that LOVE the program and they must test everything. And those that swear never to use it. But i found an interesting command line from the CMD prompt.
Code:
mount -t tmpfs tmpfs /data/data/com.aurorasoftworks.quadrant.ui.standard
Long story short it mounts the Quadrant Standard application on the RAM of the phone so you can get a true reading. Since the I/O is what bottle necks everything
I ran three test with the QS after three test i got a high of 2528, and a low of 1918. 610 point difference. Not to shabby for running CM7N75 O/C'd to 1516 with a performance governor
Then i mounted QS on the RAM of the phone and ran three test. The highest being 2997 and the lowest being 2785. 212 point difference.
just throwing out some food for thought.
Click to expand...
Click to collapse
Off topic, but what font are you using in those screenies? And a link maybe?
UsrBkp said:
darinmc that will never happen due to the different hardware archstructure. Even when device is using ARMv7 the instruction set is interpreted differently from manufacture to manufacture. Great example is Snapdragon vs Hummingbird where NEON is utilized to improve the IOPs. If its allocated on top of davlik it can be cheated its simple as that.
Click to expand...
Click to collapse
That was pretty much my point, that an end-all doesn't exist. I'm no android pro, just think that if nothing can define performance then everything is game. It's all subjective anyway. My phone, for instance, is really really really fast. Yours is probably just really fast. Mine is 2 really's faster. It's how I roll.
darinmc said:
That was pretty much my point, that an end-all doesn't exist. I'm no android pro, just think that if nothing can define performance then everything is game. It's all subjective anyway. My phone, for instance, is really really really fast. Yours is probably just really fast. Mine is 2 really's faster. It's how I roll.
Click to expand...
Click to collapse
lol and that kind of the reason is why we have Quadrant in first place. Its all about false sense of security as the owner of the device is just simply fooling themselves. Now I am not sure if you know as all chips are different which actually depends on each wafer. But in perfect world with same defect rate as 2 let say you and me both have same phone. You running ROM X1.0 and I am also running ROM X1.0 and with the same settings. Now if you score 100 and I score 105 thats discrepancy. For it to be truly applicable it has to yield the same result over and over. Now thinking it would yield different result is known as insanity unless your fan of quantum mechanics that is yet ironically do to that we have chips today lol.
Think of it as 2 Fords they both running in the same road same model and one of them goes ahead. They are still bound by the same hardware but do to other variables it yields different results. Now those variables are not always predefined and it can be altered without any hardware modifications. But for it to be standard it has to be same. Now if you also have a Ford but have 300mph v8 under the hood you just cheated and inflated the score.
I am not sure if what I am saying is making any sense to anyone but to think your MT4G is better than someone else's is just crazy lol good luck putting that on ebay/cl saying you scored +300points extra on quadrant than other owners see how that goes for ya IRL.
my 3800 quadrant phone sold for eleventy million dollars thank you very much (it came with a case).
This supposed lag fix has blown up over at r/android. I tried it on my G2x and it for sure booted up the launcher faster on startup. Check it out!
http://forum.xda-developers.com/showthread.php?t=1987032
Sent from my LG-P999 using Tapatalk 2
Thanks for sharing, looks pretty promising. Going to test it out for a bit .
I was wondering if this matters whether CM7 or cm10?
Thanks for sharing this. Installed the apk and it seems a little quicker with things, but that might just be in my head.
I'm not sure if it ****s on your battery life or not, seems like my battery just demolished itself, but now that I think about it I got 6 hours on 52%
Thus why I don't have it
Sent from my LG-P999 using xda app-developers app
I tried it for couple hours and it doesn't seem to work for me.
Sent from my LG-P999 using xda app-developers app
Everything seems pretty good for me. I'll post back in a couple days to say if it's held up.
Sent from my LG-P999 using xda app-developers app
I've installed it last night. My usual morning lag that I experience wasn't there so I believe there is some merit to what this mod is supposed to provide. I'll be tracking the battery life, as that's more important to me than a reboot once a day.
Yes I can also confirm that this app works. Even makes one of my slowest apps (amazon appstore) open much faster. Everything is a bit quicker.
My only concern is battery life, which I am going to be testing over the weekend. Loving the mod so far though.
I can verify this works well use to take close to a minut to load my xda ap lol. Not so any more. Also switching from app drawer to home screen, no lag. I used v6 supercharger for a while and i think that for now im just gonna use this. My phome is much more responsive than it use to be, especially when opening my settings menu. I will be paying attention to battery as well. Thanks for your work.
Edit. My cpu clock speed magically set it self to 1552. Dont ask me how that happened cuz i dont know. Now normally at this speed my phone would freeze. How do i know this? Cus its happened on more than one occasion. I dont overclock anymore because of it. I ran this app all day with no adverse effects. I cant say one way or another if this app works because i dont know when my phone was set to overclock. With the controversy surrounding this.... Im glad i didnt pay 1.50 for it or id feel like a really dumb***
Sent from my LG-P999 using xda app-developers app
RC calls BS
https://plus.google.com/115049428938715274412/posts/GWr72W9zmY2
From his post:
"So to be clear... IMNSHO, the recent entropy pool fad is bull****. The only users of /dev/random are libcrypto (used for cryptographic operations like SSL connections, ssh key generation, and so on), wpa_supplicant/hostapd (to generate WEP/WPA keys while in AP mode), and the libraries that generate random partition IDs when you do an ext2/3/4 format. None of those 3 users are in the path of app execution, so feeding random from urandom does nothing except make random... well... less random
The only conceivable reason some devices may feel faster is because by constantly polling the PRNG, it keeps the device's I/O in constant use (which in turn, depending on device, will make the CPU stick to higher clock frequencies to keep up and/or ramp up the IO scheduler)."
Yes it's bullish**. The whole explanation for this mod doesn't make sense and I just can't figure out how this would help at all. As RC said excellently, it would simply prevent I/O functions to go to sleep and keep your CPU higher. TL;DR : Raise your CPU clocks, change your I/O scheduler and you'll get better performances.
One more thing... I dont know when my phone was set to overclock but here are some interesting screen shots for you.
This is a 1500Mah stock battery. The original batter. I got with the phone over a year ago btw.
Something to cbew on i think. My phone has never run this well. Wtf?
Sent from my LG-P999 using xda app-developers app
Apparently everyone in that thread still thinks it works... I don't think they read Ricardo's post. Someone should keep posting it lol.
jryan388 said:
RC calls BS
https://plus.google.com/115049428938715274412/posts/GWr72W9zmY2
From his post:
"So to be clear... IMNSHO, the recent entropy pool fad is bull****. The only users of /dev/random are libcrypto (used for cryptographic operations like SSL connections, ssh key generation, and so on), wpa_supplicant/hostapd (to generate WEP/WPA keys while in AP mode), and the libraries that generate random partition IDs when you do an ext2/3/4 format. None of those 3 users are in the path of app execution, so feeding random from urandom does nothing except make random... well... less random
The only conceivable reason some devices may feel faster is because by constantly polling the PRNG, it keeps the device's I/O in constant use (which in turn, depending on device, will make the CPU stick to higher clock frequencies to keep up and/or ramp up the IO scheduler)."
Click to expand...
Click to collapse
Isn't faster performance accomplished by keeping the I/O constantly running and the CPU at higher clock speed than it would otherwise be?
Call me crazy but using this made my phone constantly stay in deep sleep! I've never, ever seen my phone stay asleep for so long and so consistently before.
buru898 said:
Call me crazy but using this made my phone constantly stay in deep sleep! I've never, ever seen my phone stay asleep for so long and so consistently before.
Click to expand...
Click to collapse
Does it ever wake up ?
Sent from my LG-P999 using xda app-developers app
New2my8125 said:
My only concern is battery life, which I am going to be testing over the weekend. Loving the mod so far though.
Click to expand...
Click to collapse
I've been using this mod for a little over a week. While RC might be right about what this mod really is doing, my phone hasn't been snappier. As for battery life, I've lost about 10% more battery a day using this. I've got the Anker 2800mWh battery, and at the end of the day I'm usually sitting around 55-60% battery remaining. On hard use days I'd be around 30% battery remaining. Overall I'm still getting a full days use out of the phone.
If someone could suggest what scheduler I should use (instead of this mod) then I'd gladly try RC's suggestion and see if he is right as well.