Related
hi everybody.
i am thinking about to buy a htc wizard (qtek 9100).
i now noticed that the qtek s110 has 416mhz, but the 9100 only 200.
is there a big difference between the two, or is the 200mhz processor as fast as the one with 416?
thx
the Wizard has a differend type of processor than the s110. Its kind of like Intel vs AMD. The mhz doesn't mean it is slower.
I think the wizard is slightly quicker then the intel one but what slows it down is lack of programs using the texas instruments processor extensions and the
non persistant program memory which slows the program loading times quite a lot.
but u get more use out of your batt as it doesnt reserve 30% batt life for ram.
Does the universal lose everything if the battery goes to 0% ? I thought the wizard and the universal were both the same in that they retained their status even on no power ?
knowsleyroader: you are correct. They use persistent memory that will be retained without power. They're slower as a result, but the benefit is what is considered a marginal battery life improvement.
All should read this:
http://blogs.msdn.com/windowsmobile/archive/2005/11/17/494177.aspx
Wizard is generally considered fine for cpu power. I've never used it, but most seem to say it's fine on everything except Skype (which some have found ok). Since you can't get another device with WM5 of the Magician's size (I think), the Wizard is pretty much your only choice right now.
Unless you've got a 700w
V
Pocket Quake runs at a respectable 8.5fps (default settings), and 14.5 (optiomized settings, no sound). I have the Spb Benchmarks (overview below) if you want them.
I find the device slow, but it is not the processor that really slows it down, it is the IO.
On the keeps memory on power-off. I have read reports of the battery needing some fiddling inorder to recharge the battery if you let it run flat.
Spb Benchmark index 232.4 (iPAQ 3650 scored 1000)
CPU index 927.45 (iPAQ 3650 scored 1000)
File system index 94.72 (iPAQ 3650 scored 1000)
Graphics index 2862.38 (iPAQ 3650 scored 1000)
Platform index 273.92 (iPAQ 3650 scored 1000)
intel vs AMD. The mhz doesn't mean it is slower
Click to expand...
Click to collapse
speed is everything my friend
well i had a xda2 mini s had it not even a week and took it back to the o2 shop . and told the guy that the phone is far to slow for what i use it for . so i changed it for a xda2i . and now i am very happy with it never crashes and does not hang up while changing screens like the mini .
intel (r) pxa275
speed 520mhz
128mb ram
thats the speed of my 2i . in my eyes the mini is a phone and just a phone . it cant handle being a pda also . it just dont have the power . and as for the slide out keypad what a joke . my one was starting to get slack in no time . i just could not imagine how this phone would look 6 months down the line of day to day use . be smart and get something that works . ok it looks good but its slooooow
my 0.002 pence worth
musiccube said:
intel vs AMD. The mhz doesn't mean it is slower
Click to expand...
Click to collapse
speed is everything my friend
Click to expand...
Click to collapse
Speed may well be to you, personally i find the functionality more important, but the MHz quote says that processor speed doesn't mean the device operation is slower. it uses a different architecture so the clock speed doesn't need to be as high for the same output (CPS would be a better measure of cpu performance IMO then all processors would be on the same scoresheet regardless of technology or clockspeed)
http://forum.xda-developers.com/posting.php?mode=reply&t
Sorry to drag this off topic a little, but I was reading the XDA-developer encylopedia, which gives claims duel core. Is it? And does duel core in the mobile world mean the same as in the desktop?
Thanks, Mike
Having owned quite a number of Pocket PCs and Windows Mobile devices over the years I have come across this sort of conversation a number of times.
The real point from my experience is that QVGA devices such as the Wizard / Mini S do not need the speed of say a VGA device such as the Exec / HP hx4705. Speed is needed on VGA devices due to the quantity of pixels that need to be updated on the screen. My HP 2210 QVGA device was quicker in a number of ways than my hx4705 and there latter machine was quoted to have more than a 50% speed increase.
I do notice my Wizard slow a little using PocketInformant when I need to filter or search. That to me looks like processor speed. But for that I get a good battery life while using the phone side quite a bit each day (it's a work sim card in there, fully paid for). My Exec however is quicker at data sorting, filtering etc. but relatively slow to update the screen, rotate the screen etc. Exactly the same as my hx4705, also VGA running the last version of Windows Mobile.
I have no reservation in suggesting the Wizard to people wanting to do a bit of everything. I haven't tried playing a film on it yet but I would expect that to be ok as long as the film is encoded to suite. But power users would likely look to either a more powerful solo device or have a second device to compliment it.
I was just lucky that O2 in the UK are offering such rediculous prices for both the Wizard and the Exec that I could get both.
acetuk said:
Wizard / Mini S do not need the speed of say a VGA device such as the
of everything. I haven't tried playing a film on it yet but I would expect that
Click to expand...
Click to collapse
Except the magican (a model down, sports the same size screen) is 400MHz.
That's a very interesting point. But is it the same make of processor? I expect it was running a Xscale processor.
It might well be that HTC decided / realised that for a phone edition model with a small QVGA screen pure raw speed is not really needed. By moving to the TI processor they kept to about the same speed for most real world scenarios (loading programs, looking up contacts, making calls and so on) and then gained elsewhere (received good battery life etc).
All I can really say is that my wizard is faster in certain core areas of these devices (screen redrawing for example) but loses out on pure raw data processing. But as I said at the start of this I don't read the benchmarks. My wizard is a fraction of a second slower than my exec at loading PocketInformant which I can live with.
I think the wizard is positioned correctly after one week of using it. But then I never used the predecessor so I can't compare the two. Having come from one of the fastest non-phone devices on the market though I can't say I'm really noticing the slowness of these devices. Not out in the real world when I am using them.
Now, I just have to sell on my hx4705. And to say that must mean I am happy!
Thanks for the interesting conversation - I'm new here but already feel at home.
well, but I heard alot that the MDAcII with its TI CPU is too slow to open large documents and so is useless for bussiness and that seems to be a problem of the CPU-power!
I've been using a Blue Angel for the last year and actually think that the Wizard is faster for my own use, as a Phone first and PDA second the market that IMHO opinion the Wizard is actually aimed at.
I use SPB to close down apps properly that I use infrequently (word/Excel etc..) and just minimize apps that I use frequently such as Outlook/Phone and my Wizard flies. Even TomTom5 appears to run much faster than on Blue Angel with route replanning completing in the blink of an eye.
Fair enough if you are asking it to run intensive apps a 2i or universal will be faster but those devices are more PDA than Phone whereas the Wizard is the reverse.
For reference mine is an O2 UK supplied XDA Mini S branded device on standard O2 UK rom with all O2 active rubbish removed. Even the battery life beats my SE k750i mobile it has just replaced!
wilesd said:
I've been using a Blue Angel for the last year and actually think that the Wizard is faster for my own use, as a Phone first and PDA second the market that IMHO opinion the Wizard is actually aimed at.
Click to expand...
Click to collapse
Ooh so I'm not alone!
Same here, especially for browsing heavy sites. The BA would take ages formatting the pages, the Wizard also takes time but less. Interface seems faster to me too (once apps loaded - loading time is dependent on the new memory architecture).
Browsing photos with Resco photo explorer is about the same.
The only point on where I can see big difference is video playback. I haven't been able to play a single video without hangups yet, either by using the same ones than I had on the BA or by trying to reencode differently (using TCPMP). A video that would play at 125% on the BA runs maybe at 75-80%. That annoys me because I would like to use it to show videos to people as a demo, which obviously looks less serious if not smooth.
I wonder if that is TCPMP-related or OMAP-related...
BUT, battery life is great!!
Hey guys, i'm considering 'upgrading'(?) from an xda2i to the mini s, and i've noticed you talking about different programs running faster/slower on either device. Was wondering if you could give me a 'rule of thumb' as to which programs would have loss performance in the mini s compared the the 2i?
Thanks
kilrah said:
wilesd said:
I've been using a Blue Angel for the last year and actually think that the Wizard is faster for my own use, as a Phone first and PDA second the market that IMHO opinion the Wizard is actually aimed at.
Click to expand...
Click to collapse
Ooh so I'm not alone!
Same here, especially for browsing heavy sites. The BA would take ages formatting the pages, the Wizard also takes time but less. Interface seems faster to me too (once apps loaded - loading time is dependent on the new memory architecture).
Browsing photos with Resco photo explorer is about the same.
The only point on where I can see big difference is video playback. I haven't been able to play a single video without hangups yet, either by using the same ones than I had on the BA or by trying to reencode differently (using TCPMP). A video that would play at 125% on the BA runs maybe at 75-80%. That annoys me because I would like to use it to show videos to people as a demo, which obviously looks less serious if not smooth.
I wonder if that is TCPMP-related or OMAP-related...
BUT, battery life is great!!
Click to expand...
Click to collapse
Similar experience here - my former PDA is a Dell X50V with a 624Mhz processor and PocketPC 2003SE, at times it's surprisingly sluggish. However, the wizard is more responsive - although I miss the VGA screen in general I prefer the Wizard for browsing.
My only complaint about the processor so far (I haven't tried gaming) is that it's not much good for playing back wmvs. I've not experimented much with it but this is an area where the X50V is very good - it can play highish bitrate WMVs no sweat. The Wizard seems to struggle, even with lower resolution and bitrate wmvs it stutters.
John
About this, how to overclock the wizard ... ??!!
musiccube said:
intel (r) pxa275
speed 520mhz
128mb ram
thats the speed of my 2i .....
Click to expand...
Click to collapse
The Universal has all that too. But, guess what, the overall experience of that "flagship" is slower than the Wizard. Which goes to show, the CPU clock speed has b*gger all to do with how a device performs in the real world.
What on earth is going on? I know where talking about 2 different Moblie operating Systems and devices, but he performance difference explains alot in terms of why the TyTN/Hermes....is underperforming in the Video department, especially with TCPMP.
If this is the case with Video, which can easily be measured for performance, how much more are these Hermes devices lacking in other departments.
Apparently the developers of TCPMP at corecodec are aware of this problem, but it seems to be more related to the Hermes itself.
Below are a few screenshots of 2 different Pocket PCs using the same Samsung 400 Mhz CPU but with completely different results.
Also, I would not necessariliy pay the figures too much mind if the Video performance was at least as good as on the Vario I or the HTC Prophet, but it is not IMHO.
Tell me what you guys think. Maybe I've got it all wrong.
I did have it at all wrong. please read up about the ATI thingy in other post.
I'm dissapointed with the speed too. I'm wondering if it's got anything to do with the 32-bit bus used?
bydandie said:
I'm dissapointed with the speed too. I'm wondering if it's got anything to do with the 32-bit bus used?
Click to expand...
Click to collapse
Hi bydandie.
You may have a point, but then I'm not having any other speed issues. What were the bus speeds on the Universal and Wizard? Do you know? Also;
Samsung (R)2442A [Hermes]
Samsung S3C2440 [HP iPAQ rx3715]
Both run @ 400Mhz
but as we can they don't appear to be identical processors. I'll google around for some info as I'm no expert, but it may still be ROM specific.
What Hermes variant have you got again? and what ROM version?
I was hoping the upgraded 200 extra mhz over the Vario, would be good, apprently it doesn't sound like the video playback is that much better. What is the video playback like ?
This is down to the Hermes not being able to utilise the ATI acceleration technology (can't remember the actual name) properly.
If you try playing a video in TCPMP with the acceleration on, on the Hermes, you will find that the screen shutters like mad!
So you can only use raw video mode for now, which is pretty slow. (But plenty quick enough for 320x240 videos, i.e. most "pocket pr0n")
mackaby007 said:
bydandie said:
I'm dissapointed with the speed too. I'm wondering if it's got anything to do with the 32-bit bus used?
Click to expand...
Click to collapse
Hi bydandie.
You may have a point, but then I'm not having any other speed issues. What were the bus speeds on the Universal and Wizard? Do you know? Also;
Samsung (R)2442A [Hermes]
Samsung S3C2440 [HP iPAQ rx3715]
Both run @ 400Mhz
but as we can they don't appear to be identical processors. I'll google around for some info as I'm no expert, but it may still be ROM specific.
What Hermes variant have you got again? and what ROM version?
Click to expand...
Click to collapse
The Wizard was 16-bit. I'm using the v1605 but with the HTC ROM.
mackaby007 said:
Hi bydandie.
You may have a point, but then I'm not having any other speed issues. What were the bus speeds on the Universal and Wizard? Do you know? Also;
Samsung (R)2442A [Hermes]
Samsung S3C2440 [HP iPAQ rx3715]
Both run @ 400Mhz
but as we can they don't appear to be identical processors. I'll google around for some info as I'm no expert, but it may still be ROM specific.
What Hermes variant have you got again? and what ROM version?
Click to expand...
Click to collapse
Both run at the same CPU speed, but have very different operating systems. According to the screen shot in the first post, the rx3700 tested is running pocket pc 4.21 (2003 second edition IIRC), whereas the Hermes is running Windows Mobile 5. I would guess the rx3700 doesn't have the slowdown related to persistant storage (for example), using some form of flash for memory is going to be slower than RAM.
I have a Eten M600 on WM5 and the samsung 400 proc. the TyTN use also the 400 proc.
When i compare them both on speed then my Eten is much faster in every way. much more responsive. opening and rendering screens.
Altough i prefer my TyTN over the M600, the build-hardware and sound is much better.
I guess it must be the ROM that isn't perfect yet ( and it isn't perfect yet for sure).
I have a Eten M600 on WM5 and the samsung 400 proc. the TyTN use also the 400 proc.
When i compare them both on speed then my Eten is much faster in every way. much more responsive. opening and rendering screens.
Altough i prefer my TyTN over the M600, the build-hardware and sound is much better.
I guess it must be the ROM that isn't perfect yet ( and it isn't perfect yet for sure).
ROM or CPU lacking?
luminus said:
I have a Eten M600 on WM5 and the samsung 400 proc. the TyTN use also the 400 proc.
When i compare them both on speed then my Eten is much faster in every way. much more responsive. opening and rendering screens.
Altough i prefer my TyTN over the M600, the build-hardware and sound is much better.
I guess it must be the ROM that isn't perfect yet ( and it isn't perfect yet for sure).
Click to expand...
Click to collapse
Thanks for your input guys. Luminus your point sounds like there may be hope for us all yet, but having said that, bydandie has switched to the TyTN ROM and I have moved to the I-mate ROM and admittedly we have both both probably experienced some improvements over the ROMs our devices shipped with but the Video playback issue remains, albeit slightly improved too (therefore indicative of being software related).
I spent several hours reading up on the SC32442A Samsung processor and I have to admit, whilst not having enough knowledge to fully understand all the technicalities, it seems that the CPU in the Hermes is one serious 'dude' which is not being used to its Full potential. Apparently its just as quick as a Xscale 520MHz CPU!
I can believe it due to the responsiveness of my device in general (with I-mate ROM), but its just not evident in the Videoplayback department.
I've also tried many differently encoded movie clips like its native MP4 and Divx etc but only negligable differences. I now believe, as posted by bydandie (I think), that its due to the ATI acceleration chip/software not doing what it is supposed and that maybe HTC should look into this as the different ROMs don't seem to make any worthwhile difference in this particular department.
For anyone who's reading this for the first time let me clarify that playback speed is acceptable to watch any well encoded movie (320x240 @ up to 768 kbps) but pausing, forwarding etc then resuming playback is where the problems occurr (for me anyhow). Benchmarking shows that the Wizard (overclocked @240MHz) easily outperforms the Hermes, but not in everything else. Though admittedly I also find the overclocked HTC Prophet @240MHz more responsive all round! Again this seems to indicate that acceleration support is missing across the border.
For the record: I no longer believe TCPMP is in any way at fault. It performs outstandingly on every other device I have ever installed it on, including Samsungs i300 which also had a 400MHz CPU and benchmarked the same videos at well over 300% compared to 120% - 180% were getting on the Hermes!
I give up for now, the problem is way beyond me but hopefully not far off from being found.
Samsung CPU
I'd be interested where you read about this CPU.
It's based on ARMv4 dating back to 2002 and as such is functionally very poor in comparison to the ARMv5 Xscale platforms. This is why it won't allow the current versions of iPlay to operate. It's also unlikely to have the xscale power and performance scaling capabilities as it pre-dated Xscale.
In practise the only thing that has affected me is iplay.
I have just upgraded my 2750 to WM5.
Contrary to what I was told when I purchased the upgrade (many months ago) it is much much faster than the tytn in every respect. It also seems more stable.
For day to day work though - I don't use the TyTN for video - ipod and Archos cover that for me - I find performance very adequate though.
Paul.
Re: Samsung CPU
pgamble said:
I'd be interested where you read about this CPU.
It's based on ARMv4 dating back to 2002 and as such is functionally very poor in comparison to the ARMv5 Xscale platforms. This is why it won't allow the current versions of iPlay to operate. It's also unlikely to have the xscale power and performance scaling capabilities as it pre-dated Xscale.
In practise the only thing that has affected me is iplay.
I have just upgraded my 2750 to WM5.
Contrary to what I was told when I purchased the upgrade (many months ago) it is much much faster than the tytn in every respect. It also seems more stable.
For day to day work though - I don't use the TyTN for video - ipod and Archos cover that for me - I find performance very adequate though.
Paul.
Click to expand...
Click to collapse
Hi again pgamble. I remember you answered an earlier post of mine regarding the CPU. It seems you understand more on these CPUs than I do.
I've provided the linl below to where I read all about the 2442 CPUs (they seem to have variants of it). Hope you understand it better than me. Please let us know what you make of it. Bydandie mentioned that the Hermes uses a 32bit Bus as opposed to the 16 bit Bus used on the first Vario. Do you know if this would negatively or positively affect the speed of data? I would have thought positive, but then I don't fully understand all the technical jargon in the provided link which will probably explain how the technology is utilised.
I hope it doesn't have to share too much of the available data bus/ bandwidth (whatever it is), thus bottlenecking the CPU. I still think at this time its related to the acceleration technology of the ATI Imageon.
http://www.samsung.com/products/sem...ationProcessor/ARM9Series/SC32442/SC32442.htm
http://forum.xda-developers.com/viewtopic.php?t=61370 :wink:
Hermes is a mini-powerhouse!!
Sorry I should have elaborated in that last post which directs you to more accurate information since I started this thread. The Hermes is in fact a mini-powerhouse and even beats the Universal for playback performance under the right conditions.
It's great that the Hermes is powerfull and beats the Universal under the "right conditions"!
But under the "right conditions" DOS beats Windows, it's just a matter on how you compare... :wink:
However, TCPMP still doesn't work as it should on the Hermes. *Standing by for new ROM*
Moskus said:
It's great that the Hermes is powerfull and beats the Universal under the "right conditions"!
But under the "right conditions" DOS beats Windows, it's just a matter on how you compare... :wink:
However, TCPMP still doesn't work as it should on the Hermes. *Standing by for new ROM*
Click to expand...
Click to collapse
The ROM ive settled on (imate) will play back no problems with rawframebuffer set for the video output. Admittedly id prefer to use the ATI acceleration but this temporary measure is still ok for me. Sound playback has improved as it does not stutter to a halt after a pause or skip. (for the record im using a 2pass Xvid encoded avi file with 128kbps MP3 audio) this is evident in both the imate and dopod roms......but not the updated HTC rom.
ATI & The Core Player v1.0
I agree with you both (last 2 posts), but from further investigations, it seems that the problem is not related to the ROM either but onlt to the ATI decoder. I've e-mailed ATI in the hope that they can enlighten or help us all. :lol: Fat chance of that I know, but in the ATI Hanheld Interface, there is a version number v2.30.......maybe that can somehow be updated directly if ATI will offer some support or through a ROM update (though it does seem like firmware) .
Anyway all said and done I'm going to keep looking until I find a way to get that bloody decoder to work permanently as it seriously improves all video formats by at least 100% in benchmarking, which means no dropped frames for High Quality encoded files.
Alternatively keep an eye out for the new TCPMP player (The Core Player v1.0) which will hopefully address all these issues within the coming weeks/months. :wink:
Yer i can imagine a ROM update may include an ATI-written updater within it which will sort out the problems. It DOES sound like something that can be fixed though so hopefully soon we will all have it working correctly. :lol:
So, AKU3.3 ROM did fix the problem with ATI, where you had screen going crazy, but there are decoding artefacts which I belive are down to TCPMP/Coreplayer to fix.
schriss said:
So, AKU3.3 ROM did fix the problem with ATI, where you had screen going crazy, but there are decoding artefacts which I belive are down to TCPMP/Coreplayer to fix.
Click to expand...
Click to collapse
Yer, if you look on the coreplayer forum there is a recommended encoding rate etc... but ive still watched videos no problem even using a different encoding rate.
So I thought I was running into a driver issue while working on my ROM, but I now believe it is the Snapdragon downclocking itself (presumably to save power). I would be happy if I was wrong.
If you use Windows Default home screen (Titanium) instead of LG Idles or what ever, you may notice that the Snapdragon processor provides exceptionally fluid animation when using the up/down controls to cycle between the list.
If you don't see it, try turning your device off for a second and then back on, then try moving up and down. Ahhh, beautiful isn't it?
If your device is plugged in, it should stay this way. If your device is running on battery, then within 10 to 15 seconds of turning on you will see the fluid animation stops and instead you get clunky animation similar to all the other 500 Mhz devices out there.
Initially, I thought it was something in my ROM. After trying a bunch of things I loaded up the stock IQ ROM to confirm if the issue existed there. At the time I was plugged in so I thought it didn't exist. Later on at home (running on battery) I noticed the issue again with the stock ROM. Anyway, I realized it was behaving like the CPU was downclocking. I plugged it in, turned it off and back on again and voilà, smooth animation that didn't stop after 10 to 15 seconds.
I suppose if we had manual control of the CPU speed we could avoid this issue, but the battery would probably be hit pretty hard.
Just for fun, I ran a quick test using a hardware accelerated version of CorePlayer. On AC, I get close to 400% playback speed while benchmarking a VGA DivX video. On battery, 127%.
I'm thinking of posting a question about this in the HD2, TG01 and newTouch forums to see if they experience the same thing. It is possible that different drivers handle CPU scaling differently.
I guess I should have looked before I posted. Apparently, Titanium is not resource intensive enough to cause the CPU to run at full speed. It will run at full speed while on AC, but clocks down 128 or 256 MHz while idling on battery.
Using LeoCpuSpeed I locked the CPU at 1 GHz and confirmed that it was the CPU auto scaling and that turning off auto scaling restores full performance, but at the cost of battery life and heat.
Wow this is very interesting. Im gonna have to play around with the LeoCpuSpeed app. I was aware the cpu usage throttled itself but had never noticed a negative effect before, great find imo.
I was also surprised that the CPU runs at a lower speed while running CorePlayer. I suppose you don't want to run the battery down too fast while watching a movie, but there must be a balance to prevent dropped frames.
I tested a 480p mkv trailer of Iron Man 2 using CorePlayer. At 1 GHz, I had 60 dropped frames. On battery with scaling enabled, over 500 dropped frames. That pretty bad for a 2 minute clip (24 fps).
trueg said:
I was also surprised that the CPU runs at a lower speed while running CorePlayer. I suppose you don't want to run the battery down too fast while watching a movie, but there must be a balance to prevent dropped frames.
I tested a 480p mkv trailer of Iron Man 2 using CorePlayer. At 1 GHz, I had 60 dropped frames. On battery with scaling enabled, over 500 dropped frames. That pretty bad for a 2 minute clip (24 fps).
Click to expand...
Click to collapse
im going to ask netripper to to make a new app that if a certain app is running(aka coreplayer) that it forces the cpu up...
have you seen the leo / hd2 cpu control app it works on the expo.
josefcrist said:
have you seen the leo / hd2 cpu control app it works on the expo.
Click to expand...
Click to collapse
it does, i also talked to NetRipper(the guy who's writing it) about adding some cool features to it. While he liked the ideas, idk if he has done anything with them yet.
josefcrist said:
have you seen the leo / hd2 cpu control app it works on the expo.
Click to expand...
Click to collapse
Indeed it does.
I mention testing with it in my second post above.
There was a hack earlier that allowed n1 to record 720p video. Apparently now it's official. Would something like this be possible on our hero?
http://www.androidcentral.com/nexus-one-720p-video-recording
djoanes said:
There was a hack earlier that allowed n1 to record 720p video. Apparently now it's official. Would something like this be possible on our hero?
http://www.androidcentral.com/nexus-one-720p-video-recording
Click to expand...
Click to collapse
I wouldnt think 720p, but something like 640x480 might be possible
i think that hero hw specs are far from 720p requirements.
spooke said:
I wouldnt think 720p, but something like 640x480 might be possible
Click to expand...
Click to collapse
My old N95 could do it so I suppose Hero can as well... That said N95 had a custom dedicated graphic chip and Hero's Adreno engine's integrated into CPU and not as powerfull, but everything else seems to be much more than N95 has, so some kind of compensation should be possible to get the camera to record 640x480.
I don's see anyone ever giving a shot at it, though. They're too busy cooking ROMs. ^__^
oh well, i'm happy with 2.1
maybe audio recording codec can be improved, i don't know how, but a rom that include this feature will be much appreciated as it would enable a "new" usage of hero.
RapFan said:
maybe audio recording codec can be improved, i don't know how, but a rom that include this feature will be much appreciated as it would enable a "new" usage of hero.
Click to expand...
Click to collapse
Oh Yes!!
This is the greatest problem of HTC Hero!!
Horrible audio rec and Horrible video rec!!
tron13 said:
Look here at my last post: http://forum.xda-developers.com/showthread.php?t=697296
Click to expand...
Click to collapse
I don't see your point. What do you mean? Or are you just threadjacking to promote your rom
Would love to see 720P on our HERO's , if not at least 640x480 wouldnt be bad either... Get on hacking the kernel for our camera to record HD style now devs!!
Hanser01, Radug, behnaam,... waiting for you people to develop in your ROMS
720p is the future for our HEROS, not Froyo
rafi300 said:
720p is the future for our HEROS, not Froyo
Click to expand...
Click to collapse
Correction 720p WITH froyo. Best of both worlds.
the recording isn't the issue..It's the saving .
Our Hero doesn't has the power to compress the video to anything worth watching if you go above 352x288... the framerate is already low as it is.
So in _theory_ you could make a 640x480, 1280x720 or even higher capture tool. But it has nowhere to dump it's data.
Anything compression scheme that has low enough cpu requirements, probably generates too much bandwidth to be writable, even if you have a high-speed SD card. And I'm ignoring the storage-requirements with this.
Use the NDK to create a simple MJPEG or HuffyUV saver... and write an Android app that uses that NDK library to compress raw 640x480 images and write it to the SD card in any workable format.
I don't know if this works, I don't even know if the SDK exposes direct-camera access.. if it worked, the amount of data generated would be a couple of MB's for just a few seconds of video.
Doesn't sound usable, so it doesn't sound wise to invest the time.
A 'kernel hack' is out of the question with the Hero, I hope you guys realize that thinking a hack like that could work on the Hero is just plain stupid.
dipje said:
the recording isn't the issue..It's the saving .
Our Hero doesn't has the power to compress the video to anything worth watching if you go above 352x288... the framerate is already low as it is.
So in _theory_ you could make a 640x480, 1280x720 or even higher capture tool. But it has nowhere to dump it's data.
Anything compression scheme that has low enough cpu requirements, probably generates too much bandwidth to be writable, even if you have a high-speed SD card. And I'm ignoring the storage-requirements with this.
Use the NDK to create a simple MJPEG or HuffyUV saver... and write an Android app that uses that NDK library to compress raw 640x480 images and write it to the SD card in any workable format.
I don't know if this works, I don't even know if the SDK exposes direct-camera access.. if it worked, the amount of data generated would be a couple of MB's for just a few seconds of video.
Doesn't sound usable, so it doesn't sound wise to invest the time.
A 'kernel hack' is out of the question with the Hero, I hope you guys realize that thinking a hack like that could work on the Hero is just plain stupid.
Click to expand...
Click to collapse
The legend has 640x480 video and a 600 mhz processor. Heros can be clocked to above 700 mhz.
therevell said:
The legend has 640x480 video and a 600 mhz processor. Heros can be clocked to above 700 mhz.
Click to expand...
Click to collapse
The top Pentium 4 CPU was clocked to 3.8GHz, and a Core2Duo E6600 is clocked to 2.2GHz but it's still faster. Clock doesn't mean anything if the CPU aren't based on the same architecture, which Legend and Hero aren't.
therevell said:
The legend has 640x480 video and a 600 mhz processor. Heros can be clocked to above 700 mhz.
Click to expand...
Click to collapse
Well, the legend and hero are the same Cpu architect actually. So the 600mhz 7227 in the legend is almost the same as our 518mhz 7200. The Droid / milestone for example is way (WAY) faster at 550mhz than the legend's 600mhz.
Anyway, why is 640x480 possible on the legend and at least very difficult on the hero?
The 7227 SoC is quite different ! It's flash controller is way faster, and more important: it has (more) hardware accelerated media functions (better media support chip in the package) .
The hero doesn't have a chip like that, so it has to do it completely on the CPU, where the legend has (limited ) hardware support / acceleration .
sizanx said:
The top Pentium 4 CPU was clocked to 3.8GHz, and a Core2Duo E6600 is clocked to 2.2GHz but it's still faster. Clock doesn't mean anything if the CPU aren't based on the same architecture, which Legend and Hero aren't.
Click to expand...
Click to collapse
Clock speed does mean something. Your example isn't that correct. The 3.8ghz P4 only has 1 core whereas the Core2Duo has 2 cores each running 2.2ghz so that's like a total of 4.4ghz.
Sorry for the offtopic, but @info5i2002, don't say something you are far from knowing. It does not matter how many cores you have since the "clock speed" does not add up. E6600 is 2.2GHz. This means it has two cores running at 2.2GHz. You can't say it's running at 4.4GHz. And the high-end P4 was dual-core. P4 6xx I think. And also, you can compare clock-per-clock performance only when you're comparing CPUs with the same architecture.
RaduG said:
Sorry for the offtopic, but @info5i2002, don't say something you are far from knowing. It does not matter how many cores you have since the "clock speed" does not add up. E6600 is 2.2GHz. This means it has two cores running at 2.2GHz. You can't say it's running at 4.4GHz. And the high-end P4 was dual-core. P4 6xx I think.
Click to expand...
Click to collapse
I ain't saying that the clockspeed add up together. What I'm saying is that it is akin to having a combined clockspeed of 4.4ghz. Its like how a dual core 1ghz is still somewhat slower than a single core 3ghz.
Clock speed is not the only important thing when you compare two CPUs, the CPU architecture is extremely important too.
RaduG said:
Clock speed is not the only important thing when you compare two CPUs, the CPU architecture is extremely important too.
Click to expand...
Click to collapse
Yes yes, I understand that too. Like how ARM Cortex A8 is so much better than say our ARM11 processor (i think its 11)
what someone said is wrong...
HERO/and Sapphire 32A could have 640x480 recording, because MSM7200 has a QDSP5 inside it. and recording is proceeded by VFE functions and not by CPU.
and it is tested with a legend port on Sapphire 32A, yes the fps is low, but I think that it could be improved, if we could get better camera libs and apps to proceed the output frames (which are from hardware and redirected to userspace by Camera kernel driver) faster.
Hello !
After long weeks of searching the answer and solution to my problem, I am exhausted. So I would like to ask the biggest Android community for help
Well, I know it's not new, but I have problem with my S7 Edge (Exynos) performance
I experience FPS drops in almost every game I play. As for games it's not that irritating, but recently I have bought Gear VR and while having this thing so close to your eyes, you see every frame skipping.
Apps for checking the CPU throttling shows that after 5-10 minutes the 4 bigger cores slow down to about 50% of their full speed. It leads to ~30% performance slow down.
I tried every solution that doesn't require root access and warranty void. For example: disabling certain packages and services (Game Launcher, Game optimization service); different settings in Game Tuner; performance mode; factory reset etc. Nothing works.
Does this kind of problems can be repaired on warranty? I know that in order to fix this you can change kernel setting, cpu governor etc but ofc they don't do that in Samsung Service Center. Is it possible for them to replace the main board and cpu with Snapdragon one?
I would not like to root my device because I didn't want to lose my 3 years warranty and I am using a lot of applications that may not work with a root.
Thank you in advance for all your replies
Did you try the game performance mode? As the "performance mode" is just screen resolution and brightness. The game mode is the real performance mode where the temps throttling is relaxed and higher clock speeds allowed(you can also edit the profile to set the resolution manually to wqhd). You can also try to set the resolution to full hd and see how it goes (tho for VR it won't be cool, but for the test it won't hurt). Also if the phone is new, it will need atleast 10 days to settle and become faster, smoother, better. Apply updates if they are pending too.
Otherwise you can't do much without root, but even then you are limited to what you can achieve so be careful + samsung have a fuse into the chip that burns out when you root the phone, it's not possible to hide the intervention and they can deny warranty for that reason (and often do so).
high_voltage said:
Did you try the game performance mode? As the "performance mode" is just screen resolution and brightness. The game mode is the real performance mode where the temps throttling is relaxed and higher clock speeds allowed(you can also edit the profile to set the resolution manually to wqhd). You can also try to set the resolution to full hd and see how it goes (tho for VR it won't be cool, but for the test it won't hurt). Also if the phone is new, it will need atleast 10 days to settle and become faster, smoother, better. Apply updates if they are pending too.
Otherwise you can't do much without root, but even then you are limited to what you can achieve so be careful + samsung have a fuse into the chip that burns out when you root the phone, it's not possible to hide the intervention and they can deny warranty for that reason (and often do so).
Click to expand...
Click to collapse
Thank you for your reply
Yes, I've tried "game mode" but there is no difference. Changing resolution to Full HD helps for a while, but the Gear VR software doesn't work properly on anything other than WQHD. It just doesn't scale properly and you are unable to see whole content.
I'm just wondering whether every S7 Edge has problems like mine. I understand throttling after 20-30 minutes of intensive gameplay, but ~40% slow down after 3-5 minutes seems strange, especially because phone doesn't even get warm.
emsitek said:
Thank you for your reply
Yes, I've tried "game mode" but there is no difference. Changing resolution to Full HD helps for a while, but the Gear VR software doesn't work properly on anything other than WQHD. It just doesn't scale properly and you are unable to see whole content.
I'm just wondering whether every S7 Edge has problems like mine. I understand throttling after 20-30 minutes of intensive gameplay, but ~40% slow down after 3-5 minutes seems strange, especially because phone doesn't even get warm.
Click to expand...
Click to collapse
Hard to tell, got the phone, but no vr... :/
Otherwise I don't have problems with gaming, the game mode smooths a little the already fluid gaming(but then again, the game I play mostly is vainglory and that game runs great on htc m8 that is almost 4 years old). You are talking about some more massive performance drop. Many phones start to throttle early and throttle hard, samsung is one of them for sure (they want the phone cold).
@hamdir can you lend a hand on that one? You are tons more experience with VR than me.
high_voltage said:
Hard to tell, got the phone, but no vr... :/
Otherwise I don't have problems with gaming, the game mode smooths a little the already fluid gaming(but then again, the game I play mostly is vainglory and that game runs great on htc m8 that is almost 4 years old). You are talking about some more massive performance drop. Many phones start to throttle early and throttle hard, samsung is one of them for sure (they want the phone cold).
@hamdir can you lend a hand on that one? You are tons more experience with VR than me.
Click to expand...
Click to collapse
Well, there is an app called CPU Throttling Test on Google Play. I would be really thankful if you give me information how your phone behave in this app. Mine throttles hard after 3-8 minutes. Clock speed of the better cores goes down to about 1.6GHz each. Sometimes even below 1.5GHz.
emsitek said:
Well, there is an app called CPU Throttling Test on Google Play. I would be really thankful if you give me information how your phone behave in this app. Mine throttles hard after 3-8 minutes. Clock speed of the better cores goes down to about 1.6GHz each. Sometimes even below 1.5GHz.
Click to expand...
Click to collapse
From a cold phone, 1.9GHz almost right away(I guess the highest freq is only for burst load, like app launching) and kept for 8 minutes then drop to 1.57GHz on the big cores. So I think it's in line with your result.
high_voltage said:
From a cold phone, 1.9GHz almost right away(I guess the highest freq is only for burst load, like app launching) and kept for 8 minutes then drop to 1.57GHz on the big cores. So I think it's in line with your result.
Click to expand...
Click to collapse
Yeah, that would be it. Thank you for your time. So it seems to be normal, I hope I'll get used to it somehow
I also wrote an email to Oculus, maybe they heard sth about this issue and know a fix for frames skipping.
The notorious feature known as DVFS is the likely culprit. Some forum members suggest it throttles the GPU and CPU to improve benchmark results or otherwise to protect the device. I've noticed it can lock-up and end up overheating the device but that's just an anecdote.
You can try forcing the app to run at a lower resolution which Samsung's Game Tuner does for some games, or find other solutions for unrooted devices like capping CPU frequency for a smoother experience.
nexidus said:
The notorious feature known as DVFS is the likely culprit. Some forum members suggest it throttles the GPU and CPU to improve benchmark results or otherwise to protect the device. I've noticed it can lock-up and end up overheating the device but that's just an anecdote.
You can try forcing the app to run at a lower resolution which Samsung's Game Tuner does for some games, or find other solutions for unrooted devices like capping CPU frequency for a smoother experience.
Click to expand...
Click to collapse
Almost all the phones are tweaked to use max freq only on single core load and app startup (burst). If their power management detect heavy load on all cores, it will automatically scale down to lower freq state to prevent heat building up fast. In reality in our case this is 1.87GHz for all big cores + the small ones (higher if only the big cluster is used, leaving the small cores off). The first actual thermal throttling level is 1.56-1.57GHz at around 8 minutes mark. Games would take a lot longer and in my observation as the phone is big and none will use 8 cores at the same time - there will be no throttling, just power management and stable fps. His case is different tho, VR is really a heavy one on the CPU.
As for DVFS (and extended to samsung power management, every manufacturer has it's own management) - it's there for a reason, to use your phone without major slowdowns due to heat and to be cold in touch, i.e. better for use. You can always change the behaviour via custom kernel, but you can't get more performance without heating the phone to the point of hardware throttling or uncomfortable to hold. Actually as you said - the right way if modify is to cap to lower freq and try to command the phone to keep them. This would still lead to a lot of heat, but will take some time to build up (and it will look smoother, tho with lower fps). OC is pointless for speed gains, will work only for burst loads. UV is not effective too as nowdays the SOC's are heavily binned for optimal settings from the factory.
Disable throttlinf dvfs exynos
Check how disable it . My youtube channel URLGAMEPLAY