Hi All,
Since i have problems with the performance of my Archos 70IT 250gb, i was curious to see if other people have the same issues.
I've searched the forums and found as well various problems, but as well people who seemed to be happy with this tablet.
What are my problems?
- At first everything smooth for like an hour after that device just locks up
- Stuttering after running some applications
- Bad performance in applications (stuttering)
I've tried to keep the device running without any changes
I've tried to only use setcpu to overclock to 1.2ghz
I've tried to only use a swap file
I've tried to use a swapfile and the overclock to 1.2ghz
I've tried to use only a taskkiller
I've tried to use a taskiller and a swapfile and an overclock to 1.2ghz
I've tried to use a Stagefright build.prop with swapfile and an overclock to 1.2ghz.
But doesn't mater what i do it after a while just everything locks up.
I've done multiple resets/full firmware reinstallations.
--------------------------------------------------------------------------------------------------------
Please do tell if your device is running good, what your setup is.
What applications you use to keep it running good and what you have changed to the default build, also state your firmware version.
Thanks in advance, i hope to learn something from it and i think other people will benefit from this as well!
No problems here, I tried Uruk for a while but that gave me troubles. Now I'm usung just the stock firmware 2.1.8, and that runs smooth.
Sent from my A70H using Tapatalk
I've found it to be really slow. Just all the time. It doesn't play games well at all and makes my desire s look like a gaming rig.
My guess is the 250gb hdd is the cause of all this as it's likely to be the read/ write access speeds.
Related
Is it possible to overclock the HTC Hero's processor to past 528 mhZ? I've heard that it is slightly sluggish and i thought if it is possible, then this might solve the issue
First of all, its sluggish, when many applications an widgets run at the same time, thats ok for a MOBILE PHONE, Mobile phones do not have to be multitasking pros.
But yeah, i asked this myself too yesterday and googled about that, but found no real answer.
So, if theres a way to overclock the Magic's or Dream's CPU it should also be possible for the HERO! MY Hero in a few days in germany
the processor maxes out a 528
if u get it past that ur just damaging it...
just like overclocking a computer
the higher u go the more cooler power u need
mobile phones are not cooling geniuses lol
That doesnt exclude the possibility to overclock a mobile cpu, many people overclocked their HTC Herald CPU, like me from 198MHZ to 250MHZ, and it was perfekt.
Rotkaeqpchen said:
That doesnt exclude the possibility to overclock a mobile cpu, many people overclocked their HTC Herald CPU, like me from 198MHZ to 250MHZ, and it was perfekt.
Click to expand...
Click to collapse
But if I remember correctly, just like the Dream/Magic, the Hero CPU runs the same MSM7200a proc. as the Dream/Magic which maxes out at 528Mhz. However, HTC has, for whatever the reason, underclocked them. It runs at 328Mhz max typically on the Dream (& i'm assuming this is the same on Magic).
We Dream/Magic users aren't really overclocking the CPU as much as just clocking it. I forget the exact parameter but in the beginning we just used a terminal command to set the cpu_scaling_freq (or something like that) to the max 528Mhz. Once root is gained on the Hero this should be easily accomplished there from the terminal or an app as well.
Rotkaeqpchen said:
That doesnt exclude the possibility to overclock a mobile cpu, many people overclocked their HTC Herald CPU, like me from 198MHZ to 250MHZ, and it was perfekt.
Click to expand...
Click to collapse
The Herald just as my old Hermes ran OMAP processors, pretty easily tweaked.
No one has as of yet discovered a way to overclock a Qualcomm , and they have been round a good year or 2 now.
p.s.. Processors dont max out as such, they just overheat and burn!!!
Fact is, that before trying to do stuff like this you first need to gain root on the Hero.
And indeed like said before: The G1/Magic _underclock_ their CPU to save battery. Only in a few situations will it do it's job at 528mhz, otherwise it's 320-something mhz.
So when a G1/Magic user is telling they 'overclocked' their CPU, they just removed the underclock and it's running at the normal 528mhz for the MS7200.
Really _over_clocking it, by running it at like 650mhz or higher, I didn't see before.
PS: The slugginess is more a RAM and disk i/o thing than directly cpu-related.
thanks for all the info guys. so should i be worried about getting the phone, or do u think it won't be that bad?
No you shouldnt, i am waiting too for my hero to arrive. So can anyone tell, what it means to "root" android? why should i root my hero when i have it and what does it affect? thanks in advice.
Rotkaeqpchen said:
So can anyone tell, what it means to "root" android? why should i root my hero when i have it and what does it affect? thanks in advice.
Click to expand...
Click to collapse
you become a superuser with more privileges and total control.
Thank you, now i understand. So how can we set the clockspeed to 528mhz permanentely?
Rotkaeqpchen said:
Thank you, now i understand. So how can we set the clockspeed to 528mhz permanentely?
Click to expand...
Click to collapse
First off, we don't know if it's even needed. Maybe it's running on 528mhz already.
Second: You can't. Until the Hero is rooted nothing like this is possible, so getting 'root' access if first step in ANY kind of tweaking.
Ok, thanks. so lets wait till we hold our heroes in our hands to see at what speed it runs and hopefully be able to root the phone.
Have been using my Hero for a few days now - and don't really notice any speed issues that concern me.
Seconded.
I have a Hero and have for a couple of days on Orange, and have no qualms about the speed whatsoever.
HTC say the processor dynamically clocks up to the maximum 528MHz when needed, so unless you want to push it out of spec (if its even possible) - there's no need to set the clock. Leave it be
thats sounds reasuring, thank u for letting me know
to be honest i just bought mine yesterday
and its not terribly slow
ive read bout it and be careful we are talking bout reviewers and most review websites dont know a lot bout half of what the say
slow no
unresponsive no
a bit laggy yes
this phone is brilliant
and is quite speedy considering how much things you got on desktop
for anyone worried about the slow speed of the Hero, the firmware update fixes this. its soooooooooo much faster.
Bump, what spped is hero running on? I have mcr 3.1 installed and since we have root now............
AFAIK, the Hero runs at 528MHz when in use, but underclocks to ~300 when not in use (ie. screen off etc.) Really, in MCR3.1, you shouldn't be needing to overclock- it really flies. If not, did you do a wipe before install?
If not, I strongly recommend you do (back up data first!), as it made mine a lot faster and was worth the hassle!
Hi all,
I have been browsing this forum for a while now and finally decided to register.
After getting incredibly frustrated waiting for HTC and T-mobile to get their act together and release 2.1 I followed the guides on here and rooted my G2.
I originally flashed VillainROM10.3 and then upgraded to VillainROM12. Both of which are great!
I have since been playing with the CPU speed. I see many people on here claiming CPU speeds of ~750Mhz, however the most I seem to be able to get out of my phone is ~650Mhz (I'm using OverclockWidget from the market to set the frequencies). Is this a problem anyone else has experienced? If so is it down to my phone having a duff CPU or could the problem be with the ROM or the widget I'm using. Whenever I set the phone to anything higher than 650 it either just freezes or reboots itself.
Thanks Guys (and girls?)
hopoffbaby said:
Hi all,
I have been browsing this forum for a while now and finally decided to register.
After getting incredibly frustrated waiting for HTC and T-mobile to get their act together and release 2.1 I followed the guides on here and rooted my G2.
I originally flashed VillainROM10.3 and then upgraded to VillainROM12. Both of which are great!
I have since been playing with the CPU speed. I see many people on here claiming CPU speeds of ~750Mhz, however the most I seem to be able to get out of my phone is ~650Mhz (I'm using OverclockWidget from the market to set the frequencies). Is this a problem anyone else has experienced? If so is it down to my phone having a duff CPU or could the problem be with the ROM or the widget I'm using. Whenever I set the phone to anything higher than 650 it either just freezes or reboots itself.
Thanks Guys (and girls?)
Click to expand...
Click to collapse
It's as simple as; some phones simply can't handle higher MHz
So if I flash for example SuperHero which is supposed to be clocked by default at 691Mhz will my phone freeze on boot or is it smart enough to figure out its max speed.
hopoffbaby said:
So if I flash for example SuperHero which is supposed to be clocked by default at 691Mhz will my phone freeze on boot or is it smart enough to figure out its max speed.
Click to expand...
Click to collapse
It will probably freeze but there are kernels the isn't overclocked that high by default
So I don't mean to keep going on about it but when I flashed VR12 the description said:
...
- 19MHz to 748MHz OC kernel
...
However when I run it the default speed its using is 619? Is that normal?
hopoffbaby said:
So I don't mean to keep going on about it but when I flashed VR12 the description said:
...
- 19MHz to 748MHz OC kernel
...
However when I run it the default speed its using is 619? Is that normal?
Click to expand...
Click to collapse
Yes. Many ROMs aren't set to the highest available clock speed by default because there are phones like yours that can't handle it
Hi - quick question for everyone. I have loaded a variety of ROMs (and done the partition fix) but am frequently getting a full crash where the system totally locks up with a single color on the screen with two sets of dotted lines on the left side of the screen (in landscape). The color varies but the dotted lines are always there.
It happens at random times - but sometimes it is consistent. I always get it with VEGAn-TAB when doing google voice search (hooked up to Dolphin HD) and sometimes when just doing regular tasks (downloading from the market, flash videos, etc).
Is this generally a hardware issue or ROM related? Just curious if I have a problem with my gTablet hardware or if I just need to fully wipe it and start over to resolve the problem.
Also - thanks to all the devs for the great work!
Update: I totally wiped everything and went to TnT Lite 4.4.0. Everything is working fine (including google voice searches) - but if I use anything for too long (like a long flash video) it will still lock up with the two dotted lines on the left hand side. Anyone else seen this behavior?
Update 2: Looks like these freezes (CPU crashes) are indicative of a hardware problem if you are only running at a max frequency of 1GHz. After some troubleshooting with Pershoot I decided to return my gTablet and hope the new one isn't so sensitive. Apparently this is not a common problem with custom kernels at 1GHz max frequency or less.
Just received mine yesterday.
I have the exact problem you are describing (good job describing it) & I am also wondering hardware/software to know if I need to return it. I'm waiting for the battery to die to see if that helps.
I'm using the the default ROM with the OTA 3588 update with a factory data reset done (still remembers my timezone ...).
Thanks for the reply. I went back to stock 3588 with the enhancement pack and flash 10.2 - ran a flash video for a good 15 min and everything was fine. Decided to move back to Vegan 5.1.1 and so far no issues. My common thread so far is when I use any of the newer kernels (like what is included in TnT lite 4.4.0 I see the issue. Then again I have been really careful with mounting system/data partitions when doing my ROM upgrades/wipes so maybe that has something to do with it.
Going to keep using Vegan 5.1.1 over the weekend with the stock kernel and see if I get the frozen screen again.
Anyone else seen the issue on their gTablets?
Anyone seeing this issue with newer ROMs? I was hoping the RC1 Vegan-Ginger build would solve the problem but I still get the frequent freezing. I saw this with TnT 4.4.0 as well but Vegan 5.1.1 never has the problem...
Wondering if it is a hardware, software or install related problem.
I think this might be an overheating issue, since I experience crashes like this while under a heavy processor load, e.g., while using Rockplayer or Google Earth.
Like you, I never experienced these crashes under Vegan 5.1.1. I've only experienced them after recently upgrading to Vegan 7.0.0. I'm using an overclocked kernel, but I get crashes even when I limit the CPU speed to the normal 1.0 GHz.
I did some detailed troubleshooting with Pershoot on this and the conclusion was it might be a bad processor (or really sensitive one) if these crashes are happening with the max frequency set to 1GHz. I too wouldn't see the issue with stock Vegan 5.1.1 - it has a stock kernel. Any modified kernels would have the issue at 1GHz or more. I was able to get it working well with a custom kernel at 912MHz but nothing more than that.
End of the story is if you are getting crashes at 1GHz it is probably a hardware issue - and not a common issue either.
Anyway, my gTab has appeared to be a return (purchased from Woot) - I decided to keep it initially but after learning this I asked them if they could swap it for a new unit. They were great about it - I have a new one on the way. My guess is somebody had a similar issue and returned it (probably to Staples) then Viewsonic sold them to Woot, and Woot sold it to me.
Fingers crossed that the new gTablet will not have such a sensitive processor.
Special thanks to Pershoot for helping me figure this one out!
It happens to me too but only when it's rock player or full screen YouTube. I'm running vegantab 7. Nice rom.....flacky video....I 'don't think it's hardware!
Sent from my VEGAn-TAB using XDA Premium App
macbroom said:
It happens to me too but only when it's rock player or full screen YouTube. I'm running vegantab 7. Nice rom.....flacky video....I 'don't think it's hardware!
Sent from my VEGAn-TAB using XDA Premium App
Click to expand...
Click to collapse
Try runnung the Antutu benchmark from the Market a few times. I found that anything that taxes the CPU enough would cause it to crash. Initially I thought it was only certain tasks but anything seems to do it given enough time.
Seems to last a little longer on a cold boot - once the processor has warmed up and you do something taxing it crashes though.
Ran 3 times....no issues. Maybe your CPU is overheating.
Sent from my VEGAn-TAB using XDA Premium App
macbroom said:
Ran 3 times....no issues. Maybe your CPU is overheating.
Sent from my VEGAn-TAB using XDA Premium App
Click to expand...
Click to collapse
I think it was - on my unit at least it appeared to be a hardware problem.
I switched back to Vegan 5.1.1 and I was still getting crashes when I intentionally stress tested the gTablet. Now I'm trying pershoot's kernel with the default 912 MHz and it seems pretty stable. I'm curious how many other reports of hard-crashed tablets we'll see now that this thread's up.
Good to know - I suspected mine would crash under 5.1.1 if stressed enough but never got it to happen before returning it. If you see any crashes at 912 with pershoot's it would be good to note - mine seemed stable at 912 though.
My gtablet has the same problem. I have tried VEGAn GE v. 7.0.0 STABLE RC1 and CM7.0.3. I tried to adjust the CPU frequency in CM7. Anything above 1000 crashes almost instantly if stressed; at 912, it can run for a few minutes. It seems to be stable at 812, but I haven't tested long enough.
By the way, I got this used off ebay. Does it mean this one has a really bad CPU?
I have been using the franco.Kernel from the first release..... And lately I've been having a couple of problems.
The first problem is with random crashes. This occur when I'm playing a game or browsing. I didn't experience this problem before and I have the phone for 6 months now.
I've OC'd the CPU to 787/245 MHz with Smartass governor. The problem is recent (since v11 onwards). Although v13h was stable under heavy usage. I've tried other kernels, re-flashed the ROM (void.ECHO) and the problems never occurred. It seems that it has something to do with Franco's Kernel. On DookMatt's kernel I was even able to keep the phone stable on 806 Mhz using performance governor; tried just to make sure it wasn't a hardware problem.
The other problem with the kernel since v12 is during file transfer on USB storage mode. The files take a long time to copy on to the SDcard and the Writing/Pasting speed drops to 0 kB/s and again speeds up. Then slows down again, speeds up again and so on.
I've tried transferring files using a standalone USB card reader. On another phone, different ROMs and kernels and it seems that the problem is with the kernel.
I could've posted this on the Franco.Kernel thread but it seems that I can't cause I don't have 10 posts yet.
I'm not a n00b and neither am I a genius. So before anyone points out that it's this or it's that, I've told you about what I've tried and what I've found.
Don't get me wrong, I love the work that Francisco has put into making the Kernel and I really appreciate the time and effort he's put into it. Also I love the constant updates he releases to make our phones ever more faster and responsive. This is just a little problem/bug I found and would really love if Francisco would solve it on the next release.
If anyone have this problem or could help me with this, then I'll be very grateful. And if anyone could post this on Franco's thread then may be he'd help us out.
I would say the problem might be 787 oc. When you say the phone was stable at 806 MHz in other roms does it mean that it was stable at standby? Or were you able to play heavy games at 806 MHz? Try reducing the OC.
As for the fluctuating sd card speeds, I have noticed this happening with all the roms I've used, don't know why you are facing this in franco kernel only.
748 MHz is ur answer
Yup... I've played NOVA and Assassin's Creed on 806 MHz on DookMatt kernel....
And also the stuttering while writing onto the SD card has only been experienced since v12 of Franco's kernel.
I hope he fixes it..... because it takes ages to copy stuff onto it.
The random crashes during gaming have disappeared since installing ChainFire 3D drivers.... It's also increased the performance quite a bit!!!
viikraam said:
Yup... I've played NOVA and Assassin's Creed on 806 MHz on DookMatt kernel....
And also the stuttering while writing onto the SD card has only been experienced since v12 of Franco's kernel.
I hope he fixes it..... because it takes ages to copy stuff onto it.
The random crashes during gaming have disappeared since installing ChainFire 3D drivers.... It's also increased the performance quite a bit!!!
Click to expand...
Click to collapse
ChainFire 3D drivers? Can you link me please I only found it for windows mobile devices.
Some1 posted it in themes and apps section...
franciscofranco said:
ChainFire 3D drivers? Can you link me please I only found it for windows mobile devices.
Click to expand...
Click to collapse
Here you go...... http://www.mediafire.com/?a4p6esrfpdvddma
This is the Market Link................ https://market.android.com/details?id=eu.chainfire.cf3d&feature=search_result
As for the original thread from Chainfire himself....... http://forum.xda-developers.com/showthread.php?t=1087427
He does say that it requires Open GL ES2.0 and in my testing the Electopia Benchmark which makes use of Open GL "PROPERLY" does work on P500.
My benchmark scores on 729/245 MHz is 17 FPS on 320*480. Chainfire doesn't increase this score, but the use of QUALCOMM (ATI) plug-in does increase real world performance in games such as NOVA and Assassin's creed. By this I mean that they render more smoothly, which otherwise would be stuttering.
The Link to the API for the plug-ins is........... http://www.mediafire.com/?bit1zhjplxygh4g I've attached it on my post as well!!
BTW.... Thanks for all the effort Francisco. Appreciate all the work.
Little by little I'm learning. I install no frills cpu overclock and did NOTHING with it so far.
It does, however, appear that this phone with jmz kernel is capable of oc.
I'd like to try this responsibly unless someone has good reason to avoid it.
So it's sort of an open topic...
Have you tried oc the desire 610?
What do you set it to?
Do you apply it automatically on boot?
What are the potential dangers of this?
I overclock my rpi openelec with pretty amazing results and it's worked fine for a long time. But this will be the first android device I've attempted it on. If in fact I do...
No frills works well. I tested it on my kfhd7 running cm11 and wow!! What a difference!!!
Our phone obviously has better hardware but after trying it ion fire I bit the bullet and tried it on desire. The results might've been placebic but it feels smoother to me. Of course I use modest settings. But did some reading beforehand, this app has safeguards built in. Been running it awhile. Battery drains a little faster so I switch to conservative when I'm not home.