I have a long time doesn't flash third-party ROMs since One X, and now I got One M8 for a month, everything is great!
That makes me want to try third-party ROM again.
But as I known, lots of ROMs is based on WWE version to develop, and it's use MSM8974AB (2.3GHz)
And...I'm Taiwanese, so obviously my M8 is use MSM8974AC (2.5GHz)
Some information I found, says that these two different model using a different CPU voltage table.
And I don't know I can use these ROMs or not because the kernel is different.
Does anyone using 2.5GHz version M8 and tried the ROMs on this forum?
Yeah, it works fine.
BenPope said:
Yeah, it works fine.
Click to expand...
Click to collapse
Thanks for ur reply, now mt mind is easier now.
But I still get little worry that because voltage table is different.
Is that may cause CPU get problem easier in the future?
I highly doubt the voltage table is not looked up by the cpu type. Do you have any evidence for this?
BenPope said:
I highly doubt the voltage table is not looked up by the cpu type. Do you have any evidence for this?
Click to expand...
Click to collapse
Actually, this information is from Taiwan's forum and that guy who told me this message is a developer, too.
Maybe he checked kernel and sure that voltage table is different.
Related
Regardless of the mythical talk of overclocking your HTC device being a bad thing (if done reasonably) Has no drastic effect on your device! For the past 2 years I have been using a small yet simple app called performance. With the app, you can overclock your device up to 624mhz (for those with lesser performance) or underclock your higher powered device to save battery life!
All you have to do is unzip the file save it the memory card, then copy it to your device root menu (NOT WINDOWS ROOT), run the app, enable the software, and there you go, simple and easy!
I'm not going to take any credit for this app, because it isn't mine! There is no mention of anyone who created this app. But, if you are out there, let me know!
If any one has any other questions, drop me a line!
dude, for what CPU is it made...
Has no drastic effect on your device!
Click to expand...
Click to collapse
well, oc should have drastic effect..
--
ehhh.. doesn't work on pxa270 cpu. it looks just as uni oc-er, if i remember right.
it is not working at all(cpu clock is NOT changing, as i supposed.
---
also, it is hard to imagine 620 mhz omap, lol.
I'm talking in the negative sense! It doesn't hurt the phone! As I mentioned, I have been using it for 2years now and I have not had any issues!
This app is good for ARM and OMAP processors!
nothin said:
dude, for what CPU is it made...
well, oc should have drastic effect..
--
ehhh.. doesn't work on pxa270 cpu. it looks just as uni oc-er, if i remember right.
it is not working at all(cpu clock is NOT changing, as i supposed.
---
also, it is hard to imagine 620 mhz omap, lol.
Click to expand...
Click to collapse
Ok, I apologize, the oc'er is best utilized with HTC devices. I did my further research and found out! Sorry for the misleading info! However, I am pretty sure there are other oc'ers out there that will SAFELY oc your device! As, I mentioned, I have been doing for the 2 years!
For those who are uncertain check out this thread. Yes, I started it, but the feed back speaks for itself!
http://forum.ppcgeeks.com/showthread.php?p=699069#post699069
Im new to the HTC scene, and have recently just purchased a Touch Pro...
Will this over clockin app work with this model HTC?
Cheers
i've used battery status to determinate if there is an effective increase of performance in my polaris ; the clock speed is still 400mhz
edit:
doesn't work with htc cruise. tested with sbp benckmark
I have tested this app, on a Touch Vogue, PPC6700 and a Touch Diamond, and noticed a difference with all three, one more than the other and vise-versa! Its small enough to take no room on your device and its an .exe file, so, nothing is created on your devices root or anywhere else!
does this work for newer devices like dhd?
pashkustva said:
does this work for newer devices like dhd?
Click to expand...
Click to collapse
Dude, this thread is almost a year old.
Try:
Oc/uv beater-dhd forums, not supported anymore but still works.
Systune-market
Nofrills-market
Possibly voltage control-market
If you use CM OC ability it's built into settings.
SetCPU-market
bclark said:
Dude, this thread is almost a year old.
Try:
Oc/uv beater-dhd forums, not supported anymore but still works.
Systune-market
Nofrills-market
Possibly voltage control-market
If you use CM OC ability it's built into settings.
SetCPU-market
Click to expand...
Click to collapse
+1 on the oc/uv beater. Really nice
Sent from my Mikrunny'd Vivo_w
I'm in a pretty bad situation. I don't know why it happened, but my phone screen went crazy so i took out my battery and tried rebooting. on the "tmobile mytouch 3g" the screen is fine and clearly ledgible, but once it boots up into the rom it goes crazy and is unreadable. I can't fix this because its fine for the hboot but when you try to go into recovery you can't see your screen, and therefore can't flash a different rom.. help? i'm running cm6.1, i had it overclocked to like 700
mr.johnsexydavis911 said:
i had it overclocked to like 700
Click to expand...
Click to collapse
There sir, is your answer.
EDIT: Since I'm sure I'll get flamed, let me explain why I say this. Our processor might be rated at 800mhz (while it's down-clocked to 600mhz), but that doesn't mean it can operate at 800mhz once it's built into a tiny device like a phone. Not to mention being along side a GPU which puts out a significant amount of heat as well. It's likely the device was being stored under less-than-ideal conditions and there was a run-away process eating up CPU. Result? Damaged GPU.
thanks... i guess haha. is there anyway to fix it?
mr.johnsexydavis911 said:
thanks... i guess haha. is there anyway to fix it?
Click to expand...
Click to collapse
The hardware is damaged - it's the risk you run when overclocking. You'll have to see if you can return it to T-Mobile under warranty and hope they don't figure it out. Is that ethical? No, but neither is charging $550 (retail) for a mid-grade phone and not delivering Froyo on-time.
You can try flashing the stock nbh in the dev forum. Thats done by simply placing it on the root of the sdcard and then booting into hboot.
Edit: I should clarify that I am not suggesting this as a fix, but as a way to try and get the phone to stock before trying a warranty switch.
nbetcher said:
The hardware is damaged - it's the risk you run when overclocking. You'll have to see if you can return it to T-Mobile under warranty and hope they don't figure it out. Is that ethical? No, but neither is charging $550 (retail) for a mid-grade phone and not delivering Froyo on-time.
Click to expand...
Click to collapse
Just curious, at what mhz would you recommend is safe for overclocking and do you know if the Slide is underclocked? For example the Slide claims to have a 600mhz processor, is the processor set to 600 max by default or is it set to something like 528mhz max? Thanks in advance.
P.S. Long time no talk Betch. How you've been?
Black myTouch Slide w/stock rom
www.GoTeamFriday.com
There are 3 kernels that you can use to overclock above 600 but below 800. One is 728? and the other is around 787. Most people are able to safely oc to 806 but it would seem you are definitely not one of them (some can go over 900). The last one allows you to oc to any normal speed you want, from underclocking at 245 to oc up to around 900. You have to set the boot speed via the 00banner file though.
If flashing the nbh file in Hboot doesn't work I would suggest (if you have insurance) running it over with your car or drop it off something really high. I don't believe they check the software, most likely because they couldn't since the hardware would be fubar.
As the title says, no matter what I try, I cannot push my device up to 1809Mhz or higher. Has anyone been able to? Could you drop a tip or two about what voltages I should try?
tpike1296 said:
As the title says, no matter what I try, I cannot push my device up to 1809Mhz or higher. Has anyone been able to? Could you drop a tip or two about what voltages I should try?
Click to expand...
Click to collapse
Depends on the kernel too. Some phones will be better to support higher speeds than others.
tpike1296 said:
As the title says, no matter what I try, I cannot push my device up to 1809Mhz or higher. Has anyone been able to? Could you drop a tip or two about what voltages I should try?
Click to expand...
Click to collapse
I've gone up to 2106MHz with @ktoonsez kernel using the default voltages, I was also able to undervolt too.
Edit, some differences in the manufacturing causes each phone to be different. What works with one phone might not work with another. My point: some phones can't be over clocked passed a certain point. My E4GT couldn't go pass 1.5GHz no matter what I did.
Second edit: why do you want / feel the need to overclock this phone?
Aaron Swartz, Rest in Pixels.
jamcar said:
I've gone up to 2106MHz with @ktoonsez kernel using the default voltages, I was also able to undervolt too.
Edit, some differences in the manufacturing causes each phone to be different. What works with one phone might not work with another. My point: some phones can't be over clocked passed a certain point. My E4GT couldn't go pass 1.5GHz no matter what I did.
Second edit: why do you want / feel the need to overclock this phone?
Aaron Swartz, Rest in Pixels.
Click to expand...
Click to collapse
I haven't felt the need, currently running BMS kernel-asswax gov. Superb battery life.
Sent from my hybrid GalaxyS3
joeyhdownsouth said:
I haven't felt the need, currently running BMS kernel-asswax gov. Superb battery life.
Sent from my hybrid GalaxyS3
Click to expand...
Click to collapse
I haven't either, with this phone, other than to do a benchmark and to say I could. I'm just wondering why the OP feels the needs.
Aaron Swartz, Rest in Pixels.
tpike1296 said:
As the title says, no matter what I try, I cannot push my device up to 1809Mhz or higher. Has anyone been able to? Could you drop a tip or two about what voltages I should try?
Click to expand...
Click to collapse
You could try raising your voltages alittle
Sent from my SPH-L710 using xda premium
If you are in TW, search ziggy's in Google.
infected with the unspeakable
Yeah, I suggest you look up "CPU binning" and see what you have as not all processors can handle the same things, and you can seriously damage your phone by overclocking too high or something similar.
jamcar said:
I've gone up to 2106MHz with @ktoonsez kernel using the default voltages, I was also able to undervolt too.
Edit, some differences in the manufacturing causes each phone to be different. What works with one phone might not work with another. My point: some phones can't be over clocked passed a certain point. My E4GT couldn't go pass 1.5GHz no matter what I did.
Second edit: why do you want / feel the need to overclock this phone?
Aaron Swartz, Rest in Pixels.
Click to expand...
Click to collapse
The only real reason I wanted to overclock was to say that I could (and do some benchmarks). Curiosity, mainly. I've since realized that even going to 1728Mhz has proven fairly useless except if I want to reduce battery life, or get a *tiny* boost when emulating the N64. Thank you for the explanation of why it most likely wouldn't work. Seems I always get devices that don't really like overclocking, as my HTC EVO 4G didn't seem to like more than a tiny boost, either.
Hi, thanks for reading.
I am a HongKonger. As I know, the global version of M8 is using the snapdragon801AB while Asia version is using the snapdragon801AC. I know the only different of the two cpu is simply overclocking to different frequency. Would the different make development very difficult to support the two at the same time? Or it will just be the same?
I afraid there will be less support for the Asia M8. Will this happen?
I am so sorry that my English is not good enough. Hope you guys could understand what I'm talking about.
Thanks.
CPU Difference
Hi.
I suggest you to be extra cautious about cross-flashing.
S801AB and AC are two different CPU although they are almost identical structure wise speaking.
What might really happen if you cross flash is that ROMs for AB doesn't have a proper CPU scheduler for AC. I am talking about the voltage input for CPU. You might very likely be running AC (0.8V required) with AB's voltage (1.0V). Sure, your CPU can take this little voltage surplus but in the long run this is no different than chronic suicide. The best way to get a proper ROM is to request for one that is made specifically for AC variance. Or, if I had to guess, keeping your stock kernel might do the trick here.
All in all, be very careful.
Hi guys,
I have been testing many different ROMs and kernels so far and still haven't found a kernel which really permits underclocking below 1113 Mhz (for big cores) and 633 Mhz (for little cores).
Do you know any kernel which allows setting cores for a minimum of 300 Mhz for instance?
Many thanks.
Patoilo said:
Hi guys,
I have been testing many different ROMs and kernels so far and still haven't found a kernel which really permits underclocking below 1113 Mhz (for big cores) and 633 Mhz (for little cores).
Do you know any kernel which allows setting cores for a minimum of 300 Mhz for instance?
Many thanks.
Click to expand...
Click to collapse
Maybe Agni kernel do this.
IceCold Kernel up until (including) R3.5 has this feature. The feature was then removed without reason by the developer, but you can still download R3.5.
I'm using (and underclocking) it with Havoc OS 2.5 and it works great.
JosephusQuint said:
IceCold Kernel up until (including) R3.5 has this feature. The feature was then removed without reason by the developer, but you can still download R3.5.
I'm using (and underclocking) it with Havoc OS 2.5 and it works great.
Click to expand...
Click to collapse
Thanks a lot for the tip. I will flash it to test.
Any experience of those builds till 3.5 working with MIUI-based ROMs?
Patoilo said:
Thanks a lot for the tip. I will flash it to test.
Any experience of those builds till 3.5 working with MIUI-based ROMs?
Click to expand...
Click to collapse
I have never used it for MIUI-based-ROMs, so I can't speak on that.
JosephusQuint said:
I have never used it for MIUI-based-ROMs, so I can't speak on that.
Click to expand...
Click to collapse
I will see how it goes and will post the results here.
But I am also interested in testing the Havoc ROM. I actually did it before but got poor battery results. Do you have an idea of your screen-on-time with the combo Havoc + IceCold 3.5?
Patoilo said:
I will see how it goes and will post the results here.
But I am also interested in testing the Havoc ROM. I actually did it before but got poor battery results. Do you have an idea of your screen-on-time with the combo Havoc + IceCold 3.5?
Click to expand...
Click to collapse
I will make a screenshot tomorrow evening of the battery life, and put it in the thread. (It's bedtime here)
JosephusQuint said:
I will make a screenshot tomorrow evening of the battery life, and put it in the thread. (It's bedtime here)
Click to expand...
Click to collapse
Thank you in the meanwhile, I clean flashed IceCold 3.5 Pie and minimum big cpu still stays at 1113 MHz
No option to set 300 MHz
JosephusQuint said:
IceCold Kernel up until (including) R3.5 has this feature. The feature was then removed without reason by the developer, but you can still download R3.5.
I'm using (and underclocking) it with Havoc OS 2.5 and it works great.
Click to expand...
Click to collapse
are you sure he removed it without given a reason.?? it was removed caused those frequencies was useless.
raptorddd said:
are you sure he removed it without given a reason.?? it was removed caused those frequencies was useless.
Click to expand...
Click to collapse
He removed it, because he thought them useless. What is useful and what isn't, is of course subjective, and I for one disagree with his view. He decided it wasn't worth keeping in; however, the feature was working and not "useless" in the sense that it was incomplete.
Regardless, this is not a discussion for this thread; you may ask him directly in his.
The underclocking frequencies were removed due to the Pie firmware disabling the ability to underclock below 1113MHz.
IceCold R3.5 + Oreo FW should still work.
JosephusQuint said:
He removed it, because he thought them useless. What is useful and what isn't, is of course subjective, and I for one disagree with his view. He decided it wasn't worth keeping in; however, the feature was working and not "useless" in the sense that it was incomplete.
Regardless, this is not a discussion for this thread; you may ask him directly in his.
Click to expand...
Click to collapse
bcoz its not useful at all. its all inefficient frequency and he is right. we all tested that alot and found it to be as good as previous undercocked 300mhz freq. just test and see instead of saying this.
people dont even try and complain
JosephusQuint said:
I will make a screenshot tomorrow evening of the battery life, and put it in the thread. (It's bedtime here)
Click to expand...
Click to collapse
There you go. It took a bit longer because I normally have 2 SIM-Cards active (but that uses up more battery). So the pictures are from only 1 SIM card active and mobile data always on.
jokerpappu said:
bcoz its not useful at all. its all inefficient frequency and he is right. we all tested that alot and found it to be as good as previous undercocked 300mhz freq. just test and see instead of saying this.
people dont even try and complain
Click to expand...
Click to collapse
You know what people also do? Assuming without evidence what other people did/thought, instead of asking them.
I did test and compare, and I do have a measurably better battery life than with later versions of the Kernel. I also didn't complain, I stated how it is.
Grow a thicker skin; people like you are not helpful. Not worshipping every move of a developer doesn't mean not being grateful.
I maintain that underclocking is an important feature to have, others may disagree. Some people want NFC and Wireless Charging, I could not care less.
It boggles my mind, that on XDA of all places you regularly find people that tell you what you do or don't need.
JosephusQuint said:
You know what people also do? Assuming without evidence what other people did/thought, instead of asking them.
I did test and compare, and I do have a measurably better battery life than with later versions of the Kernel. I also didn't complain, I stated how it is.
Grow a thicker skin; people like you are not helpful. Not worshipping every move of a developer doesn't mean not being grateful.
I maintain that underclocking is an important feature to have, others may disagree. Some people want NFC and Wireless Charging, I could not care less.
It boggles my mind, that on XDA of all places you regularly find people that tell you what you do or don't need.
Click to expand...
Click to collapse
latest test builds have better bb than older underclocked builds.
if u have had enougj acting like a idiot better use it and see the magic instead of bullshiting here. come 8n tg group and see thick head