Related
Hey whats up guy?
all this Temp-Root and ADB, and bat.file's, and what not is relatively new to me...seeing that ive never needed to use it previously, im kinda paying the ultimate price for it now LOL...So, yesterday i used "Wisefire's" Temp-Root method and it worked perfectly...but now im looking to use the OC bat.file that was included in the zip.....ive tried other method of Temp-Root and changed my uder variables and what not and my PC became a huge mess.....but with alot of help from the guys in that thread we got things worked out and i was able to run the bat.file just fine....now i seem to be getting the same error in the CMD and im not sure where to go from there to resolve the issue.....i keep getting a "NO SCRIPT OR DIRECTORY" error......ill attach a SS of the CMD and what it keeps giving me....if anyone can help me resolve this or maybe even stir my to a differ method of using SETCPU to OC my device, i'd be grateful for that.....thanks guys......i really appreciate it
I was having that exact same problem..i couldnt fig it out for nothing..i still dont know how i got it to work...i just tried extracting the overclock bat in the unzipped easy frevo file and when it asked to replace i said no and it send me back to the easy frevo file folder and i did process and it work..same thing worked with my wifes..so wierd..i dont know if ur using windows but u could try it..lol
EDIT ....I have heard problems with OC in yesterdays easy frevo..there is and updated one with frevo, OC, and bloat from today that one is one that worked for me
Helper
Ok lemmi take a shop at this.
1. Make sure you have the right .KO file! There is one for non-ota and phones that have takes the ota (over the air update)
This is the command I used and got it to work.
adb push 8x60_oc.ko /data/local/tmp/
adb shell insmod /data/local/tmp/8x60_oc.ko scpll_l_val=33 vdd_uv=1375000
Make sure to change the .ko name to the one you have. You can simply edit the .bat and use these lines.
Good luck hope it helps!
oc app.
could someone please tell me the best overclocking app.to use for my evo3d,i searched a couple but some had bad reviews or didnt even list the evo3d as being compatable.
thanks keith
Mondays suck!
krazykeith64 said:
could someone please tell me the best overclocking app.to use for my evo3d,i searched a couple but some had bad reviews or didnt even list the evo3d as being compatable.
thanks keith
Mondays suck!
Click to expand...
Click to collapse
Setcpu. Choose auto detect.
Locked & Loaded
thank u bro, I got it and so far works great, I have it on conservative, tomorrow I play around with it a bit and see what happens, besides auto detect does u our anyone else no the best settings to put it at?
Sent from my PG86100 using XDA Premium App
krazykeith64 said:
thank u bro, I got it and so far works great, I have it on conservative, tomorrow I play around with it a bit and see what happens, besides auto detect does u our anyone else no the best settings to put it at?
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
It's very device and "needs" specific. Everyone is different. If you're looking for the best battery life go as low as you can tolerate. If you're looking for speed crank it as high as you can without the phone locking up or getting sluggish, and play around with conservative/on demand governors. Avoid performance governor.
hockeyfamily737 said:
It's very device and "needs" specific. Everyone is different. If you're looking for the best battery life go as low as you can tolerate. If you're looking for speed crank it as high as you can without the phone locking up or getting sluggish, and play around with conservative/on demand governors. Avoid performance governor.
Click to expand...
Click to collapse
didnt know every evo3d device was so differant,website said perf.gov.could help but im taking ur advice instead,will play around with it today,im learning here,very new at this so thank u much for taking time to help me.
Keith
krazykeith64 said:
didnt know every evo3d device was so differant,website said perf.gov.could help but im taking ur advice instead,will play around with it today,im learning here,very new at this so thank u much for taking time to help me.
Keith
Click to expand...
Click to collapse
Performance governor just clocks your cpu @ the max wether needed or not and yeah the phones are all different. Well made, but still made by people and machines. So there's still some variance. I'm a phone geek by hobby but manufacturing specialist by trade lol. Anyways, glad to help.
krazykeith64 said:
thank u bro, I got it and so far works great, I have it on conservative, tomorrow I play around with it a bit and see what happens, besides auto detect does u our anyone else no the best settings to put it at?
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
No prob man. Glad you got it worked out. Also if you plan on experimenting with the overclock and underclock make a mental note to be by a pc/laptop. I say this because if you go to high your phone could freeze and lock up requiring a battery pull this applys with the underclock as well. If it does freeze up and you have to do a battery pull it will mean reboot and you will loose root and have to do your choice of rerooting and reoverclocking. Also I'd recommend reading the overckock thread to look at some members experience with overckocking and underclocking to get a general idea of were to start. Well hope this helps.
Locked & Loaded
I had an earlier bat file that worked for rooting but the overclock wouldn't.
I took the working bat file and edited it. I then copied the first line (where it had cd) to the other bat file.
Worked great.
Sent from my PG86100 using Tapatalk
lost root
laie1472 said:
No prob man. Glad you got it worked out. Also if you plan on experimenting with the overclock and underclock make a mental note to be by a pc/laptop. I say this because if you go to high your phone could freeze and lock up requiring a battery pull this applys with the underclock as well. If it does freeze up and you have to do a battery pull it will mean reboot and you will loose root and have to do your choice of rerooting and reoverclocking. Also I'd recommend reading the overckock thread to look at some members experience with overckocking and underclocking to get a general idea of were to start. Well hope this helps.
Locked & Loaded
Click to expand...
Click to collapse
i did read them and the devs.setcpu website,set it to some profiles and charged overnight till 4am,went to work used the phone listened to my mp3 music(alot)got home bout 5:00p and still had 70%batt.left...think i done good,internet seems alittle faster too,thanks for the advice.
keith
hockeyfamily737 said:
Performance governor just clocks your cpu @ the max wether needed or not and yeah the phones are all different. Well made, but still made by people and machines. So there's still some variance. I'm a phone geek by hobby but manufacturing specialist by trade lol. Anyways, glad to help.
Click to expand...
Click to collapse
manufacturing specialist...cool job,heavy equipment operator/mechanic/welder here,and gadget nut...anyway did some configs and profiles,stayed away from performance gov like u said,went to work at 4am got home at 5p used phone internet listened to mp3 most of day and still had 70%batt left over...think i done ok for not knowin what im doin,lol,thanks amillion for ur time and advice,ur a big help,still gonna play with configs some more and see if i can get even better results from battery,phone didnt hang up or freeze at all.Gps got screwed up sayin i was in ny for weather when im in hillsborough nj,go outside and it says hills nj,came back in and says im in ny,lol,concluded its my airave interfering with gps,turned it off and I'm back home in hillsborough,will call airave tomorrow.
Called sprint and they reset my phone tryin to figure this out lost root and setcpu,had a heartattack,lol,but rerooted and everything was saved from the first root and setcpu so im back where i was.
u where a really big help my friend and i appriciate it.
keep in touch.
Keith
28 August 2011
Alright I tried this out already. You just have to follow the instructions, and also don't use other memory apps like auto killer memory optinizer, or task killers like advanced task killer. It really makes your phone run more smoothly.
Simple instructions are in post #18 by molohov.
molohov said:
I just ran the script with Aggressive 2 settings (6, 8, 25, 30, 35, 35)
Very easy to apply and run. It's a little difficult to weave through Zepp's writing, but essentially it boils down to this:
1. Download V6_Supercharger_for_Android-update8.sh.txt (at the bottom of the first post) to the sdcard
2. Download Script Manager Market Link
3. Open Script Manager and open the .txt file you just downloaded. Make sure Run as Root is selected.
4. Pick one of the many presets!
5. Reboot
Have yet to do some more testing with the current preset, but I'm sure it'll be good
Click to expand...
Click to collapse
You need busybox 1.18.2 or lower for this script to work properly. Below is the Market link to busy box installer. Thank LibertyMonger for suggesting to me to add this into the OP!
https://market.android.com/details?id=com.jrummy.busybox.installer
In the script manager, its a little like using terminal or command prompt. Just load up the txt and run as root. They will ask you to choose your scrolling speed (just type 0 so the text appears fastest inside the script manager) so you have to tap the screen for the keyboard to appear. You need the on screen keyboard to choose the presets too. Just choose one of them. I chose option 2 (aggressive setting 2) and currently my phone feels very fast.
ive found a video tutorial on how to install this script on youtube. http://www.youtube.com/watch?v=WADt5tK6Ths
Issues:
(PM me or leave a reply so I can put them here and warn the others not to use unsuitable presets)
------------------------
21 August 2011
hi guys, i saw this supercharger on a lg optimus one subforum. claims it works on all android phones.
it says
"What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind "
heres the link http://forum.xda-developers.com/showthread.php?t=991276
dont know whether it will work or whether it will give us much improvement to our phone. any one?
eejin2 said:
hi guys, i saw this supercharger on a lg optimus one subforum. claims it works on all android phones.
it says
"What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind "
heres the link http://forum.xda-developers.com/showthread.php?t=991276
dont know whether it will work or whether it will give us much improvement to our phone. any one?
Click to expand...
Click to collapse
Im thinking of giving this a try. It also has an androidiani recovery zip. Hmm...
Looks great. Anyone tried yet?
Sent from my MilestoneXT720 using XDA App
I'll have look when i get home, sounds promising though.
But even better is if one of our devs check this out to really see what's up..
Sent from my XT720 [MZ - CM 6.3.0]
You just as well use minmod open recovery it has a very similer memory managment.
Sent from my XT720 using XDA Premium App
mchlbenner said:
You just as well use minmod open recovery it has a very similer memory managment.
Sent from my XT720 using XDA Premium App
Click to expand...
Click to collapse
I suggest you read the OP, it specifically says that it is NOT the same as minmod, minfree, auto killer or all that..
JiroPrinz8 said:
I'll have look when i get home, sounds promising though.
But even better is if one of our devs check this out to really see what's up..
Sent from my XT720 [MZ - CM 6.3.0]
Click to expand...
Click to collapse
so how's it? does it work?
edit
wait i just saw that they talked only about gingerbread, and the linked tutorial said too that it was only for cm7 (he might have wanted everyone to play safe and not risk screwing up their phone)... anyone tried this yet?
It says for Milestone only, so does that mean what it says? For milestone only? We have the Xt720 (well I'm sure you know that lol)
Yeah and you're right eejin2 looks like it's for CM7. So maybe if we get CM7 then it won't be for milestone only
But while on the subject of speed, with the Special's governors fixed and overclocked at 1200, wow dude it's super fast! don't think this is even needed! lol
haha. yeah its fast of course.. but im currently on cm6.3 and im very satisfied. not a single hang since i flashed 6.1.2. only overclocked at 900, and underclocked at 500 sometimes. never had to do a battery pull at all. wont long term running overclocked at 1200mah damage your processer?
eejin2 said:
haha. yeah its fast of course.. but im currently on cm6.3 and im very satisfied. not a single hang since i flashed 6.1.2. only overclocked at 900, and underclocked at 500 sometimes. never had to do a battery pull at all. wont long term running overclocked at 1200mah damage your processer?
Click to expand...
Click to collapse
Long term heat will damage your processor. Obviously if OC'd at 1200 and running intensive apps, your temp will shoot up. SetCPU or any other profile mgr has profiles to ramp up or down you CPU speed accordingly. I have run 1100/74 sinceI first installed MSOC but I have SetCPU profiles to throttle it back when I don't need that much power and speed.
Woodrube said:
Long term heat will damage your processor. Obviously if OC'd at 1200 and running intensive apps, your temp will shoot up. SetCPU or any other profile mgr has profiles to ramp up or down you CPU speed accordingly. I have run 1100/74 sinceI first installed MSOC but I have SetCPU profiles to throttle it back when I don't need that much power and speed.
Click to expand...
Click to collapse
Yeah I use setcpu as well but only for temperature. I let it run natural otherwise. But like i said, I have been on so many ROM's and I like to put them to the test so I have been at 1200 since march for the most part and never have any overheat issues. No reboots. And if it does burn up I have a year and a half left on my warranty lol. CBW gives 2 year warranties. I don't need it clocked that high, it will run well at 800, I just like to put it to the test. And being at 1200 on the special now has made the biggest difference out of all that I have tried. But of course haven't tried it long enough to really compare with cm6.
Seems like 1200 since march is pretty much long term lol. My phone is still like new!
Anyone tried this yet? Any comments?
Sent from my MilestoneXT720 using XDA App
It works very well with phones having limited memory. Must try. Zepp is good.
Sent from my GT-I9100 using Tapatalk
sileshn said:
It works very well with phones having limited memory. Must try. Zepp is good.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
isnt it for gingerbread only? i read it in the post...
eejin2 said:
isnt it for gingerbread only? i read it in the post...
Click to expand...
Click to collapse
No. It is for a variety of phones with different OS. He started of by creating it for the milestone and then made it universal.
Sent from my GT-I9100 using Tapatalk
so is it 100% safe to use it on our phone? im currently on cm6.3.
eejin2 said:
so is it 100% safe to use it on our phone? im currently on cm6.3.
Click to expand...
Click to collapse
Backup and try. You can even undo its effects as it backs up the files it modifies. Ask Zepp about the best settings for your phone by giving your phone details.
Sent from my GT-I9100 using Tapatalk
I just ran the script with Aggressive 2 settings (6, 8, 25, 30, 35, 35)
Very easy to apply and run. It's a little difficult to weave through Zepp's writing, but essentially it boils down to this:
1. Download V6_Supercharger_for_Android-update8.sh.txt (at the bottom of the first post) to the sdcard
2. Download Script Manager Market Link
3. Open Script Manager and open the .txt file you just downloaded. Make sure Run as Root is selected.
4. Pick one of the many presets!
5. Reboot
Have yet to do some more testing with the current preset, but I'm sure it'll be good
Running the multi-tasking option (no.7); for me it is quite smooth but will wait and see.
I saw it long time ago but never had the confidence in trying this out
MilestoneXT720 - CM 6.3.0 by MZ
molohov said:
I just ran the script with Aggressive 2 settings (6, 8, 25, 30, 35, 35)
Very easy to apply and run. It's a little difficult to weave through Zepp's writing, but essentially it boils down to this:
1. Download V6_Supercharger_for_Android-update8.sh.txt (at the bottom of the first post) to the sdcard
2. Download Script Manager Market Link
3. Open Script Manager and open the .txt file you just downloaded. Make sure Run as Root is selected.
4. Pick one of the many presets!
5. Reboot
Have yet to do some more testing with the current preset, but I'm sure it'll be good
Click to expand...
Click to collapse
Wow thanks man, you made it seem much easier than the original post! lol. Very useful bro thanks again
Is there an app or one being worked on that will eun both cores at the same time? Thanks guys for ure help
Sent from my PG86100 using XDA App
I put out a modified kernel that enables the second core all of the time. You just can't use SetCPU or it will revert back to one core active/second core active on demand.
I appreciate it brother and you have been thanked. I see you said not to use Setcpu with this so is there another over clocking agent I can use? I want my phone as fast as can be and absolutely hate the fact it is dual core and does not use its full potential against the other duals out there.
Thanks again brother, so many **** post going around it is nice to see someone give a straight answer with no bs
Derek
sprintuser1977 said:
I appreciate it brother and you have been thanked. I see you said not to use Setcpu with this so is there another over clocking agent I can use? I want my phone as fast as can be and absolutely hate the fact it is dual core and does not use its full potential against the other duals out there.
Thanks again brother, so many **** post going around it is nice to see someone give a straight answer with no bs
Derek
Click to expand...
Click to collapse
I've been researching this myself, and the two best candidates that don't mess with the second care are: CPU Master/CPU Tuner.
I prefer CPU Tuner, but for some reason, it doesn't work correctly with my phone (it doesn't detect governors). Maybe it will with yours. 2.7.6 is the version that did work but it also had an issue where it would scale the CPU up to its max when you launch the app, which would cause my phone to reboot since it doesn't handle 1.836 GHz very well. It's up to 2.7.8 now and I've been exchanging emails with the dev on the issue. Hopefully it is resolved soon because it is a very very good app.
CPU Master is a bit more lightweight and a little less frills but it seems to do the job quite well most of the time. However, sometimes it does get confused on what profiles it should be using.
To be honest, you can pretty much use any kernel and with a simple script, enable the second core to run all the time. It doesn't necessarily need to be mine (since it's simply a modified stock kernel and doesn't support overclocking).
Once you settle on a kernel, I can provide the script or show you what needs to be done to enable the second core all the time.
I prefer to run bcb blend. Can u please provide me the script and a walkthrough to get this going? Thanks so much for your help bud
Sent from my PG86100 using XDA App
sprintuser1977 said:
I prefer to run bcb blend. Can u please provide me the script and a walkthrough to get this going? Thanks so much for your help bud
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I wanted this as well, but I talked to Cayniarb he says it makes the phone worse. Then smokin tried to enable it for are aosp roms and he said it gave alot of issues and bugs. Honestly when I was using the dual core mod on Showdowns' rom, I didn't have a problem, with battery life or anything. Something may come up again in the future. I just want this beast to run like it should.
私の"DU4L C0R3 SH00T3Rは"³Dであなたを撃墜！トゥパックをねじ込みます 。
"AOSPのBACK!" ┌П┐[◣_◢]┌П┐
sprintuser1977 said:
I prefer to run bcb blend. Can u please provide me the script and a walkthrough to get this going? Thanks so much for your help bud
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
There are a number of ways to go about doing this:
ramdisk
init.d
init.post_boot.sh
But, the easiest fastest way to get this accomplished is to either upload and post your init.post_boot.sh file, which is located in /system/etc/, OR edit it manually yourself.
There are other ways but this file already exists, and has most of what you need in it and it gets executed at boot anyway.
Take note of the permissions set for this file, because they will need to be set back if you choose to edit outside of Android. You can also edit the file with Android's file editor if you use Root Explorer.
If you choose to edit it yourself and outside of Android, you will need to open the file with Notepad++ (Or whatever qualified editor you use) and add this in anywhere before the line "chown system /sys/devices/system/cpu/cpu0/online"
echo "1" > /sys/devices/system/cpu/cpu1/online
chmod 0444 /sys/devices/system/cpu/cpu1/online
echo "ondemand" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
chmod 0644 /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
What this does is set the second core's online state to 1 (enabled) and the second line sets this value as read-only, so that the system can't disable its online state when it feels the second core is no longer needed. The third line sets the governor, and I assume you can use any governor that's available in the kernel. However, I'm not sure if both cores can have separate governors. Changing one may change the other. I haven't tested this myself, but sampling frequency and up-threshold works like this, so I assume governors may as well. The last line, if it has anything in common with the third, sets the governor so that you may infact change it with CPU Tuner (since it has the ability to control the second core as well as the first). This line may be obsolete and was only added in as a fail safe.
While you're in there, you can tune your cores even more (assuming you don't use anything like virtuous OC, CPU Tuner, ETC) and set the min and max values by adding this (there should already be something like this for the first core so you can go ahead and add this below that):
echo 192000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 192000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 594000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
As a way to conserve battery life, I set the second core to run at half its max (stock kernel), This works fantastically for CPU Master, which only controls the first core, as you can have all your profiles set, without messing with the second core. (I've found that you can run the first core at 192MHz with the screen off/low battery while still maintaining minimal lag by setting the second core's max to 594MHz!)
Once you've edited the file, you can go ahead and push it back to your device (assuming you've edited it outside of android) and set the permissions back to what they were and reboot.
As always, if any of this is overwhelming, I'll be happy to edit the file for you.
To check whether or not your edits were successful, you can navigate with root explorer to /sys/devices/system/cpu1 and look for "online" which should have permissions of r--r--r-- You can view the file and see if "1" is in there, indicating that the second core is active. You can also use SystemPanel to check your CPU activity, which should show both cores active. As a legend, a grey pie chart means the second core isn't active, but they should both be green and actively being used.
Good luck!
Dude I really appreciate your help and I sincerely mean it. Thank you
Sent from the deep South in Ga
I hate to ask but can u edit the file for me? I am not too versed in this area
Sent from the deep South in Ga
I edited and did what you said. So far no issues....
Sent from the deep South in Ga
sprintuser1977 said:
Dude I really appreciate your help and I sincerely mean it. Thank you
Sent from the deep South in Ga
Click to expand...
Click to collapse
no problem!
sprintuser1977 said:
I hate to ask but can u edit the file for me? I am not too versed in this area
Sent from the deep South in Ga
Click to expand...
Click to collapse
sure
sprintuser1977 said:
I edited and did what you said. So far no issues....
Sent from the deep South in Ga
Click to expand...
Click to collapse
lol looks like you got a bit anxious. Glad its working
Its people like you why I come to xda. Willing to help people learn. You da man
Sent from the deep South in Ga
What about for aosp, I got kind of lost.
Edit: I PM'd freeza and he was a big help.
should be the same way, but if you don't have the file, you can create a init.d script
look in system/etc/init.d if there are any scripts there take one open it in notepadd++ delete all but the first line and insert the dual core line in. Then save the file as something different and push back to phone
Click to expand...
Click to collapse
私の"DU4L C0R3 SH00T3Rは"³Dであなたを撃墜！トゥパックをねじ込みます 。
"AOSPのBACK!" ┌П┐[◣_◢]┌П┐
The past two days my phone has been randomly rebooting. It has happened twice in two days. I have no idea how to pull any information from my phone to possibly see what is happening. I am moderatly tech savvy so with good directions I can do just about anything. If anyone is willing to help that would be great.
Phone: At&t GSII (obviously)
Rom: Cognition beta-4
Kernel: Entropy's doom v2
I am using set CPU with profiles. Not over clocking or undervolting, I just use it to underclock when phone gets to hot or battery gets to low.
Anything else you need to know or want me to do please let me know. Thanks.
Sent from my SAMSUNG-SGH-I777 using xda premium
Emil9727 said:
The past two days my phone has been randomly rebooting. It has happened twice in two days. I have no idea how to pull any information from my phone to possibly see what is happening. I am moderatly tech savvy so with good directions I can do just about anything. If anyone is willing to help that would be great.
Phone: At&t GSII (obviously)
Rom: Cognition beta-4
Kernel: Entropy's doom v2
I am using set CPU with profiles. Not over clocking or undervolting, I just use it to underclock when phone gets to hot or battery gets to low.
Anything else you need to know or want me to do please let me know. Thanks.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Complete reboot back to Samsung screen? Or back to bootanimation?
If all the way back to the Samsung screen, there isn't much you an do right now other than wait - I'll be putting an update out tonight, and one of the main features is that I finally got ramconsole working. Ramconsole is how /proc/last_kmsg (the last things a kernel printed before a reboot or crash) is implemented. Once I release my next kernel, if you flash it and another reboot back to the Samsung screen happens, the following will give valuable debug information if executed from Android Terminal Emulator or a similar app:
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Then zip up last_kmsg.txt and post it - but as I said, you'll need to wait for the next kernel release before you can do this.
I haven't seen it reboot but it asks what launcher to use (because I didn't set a default) and the battery useage is reset. It will say it has been unplugged for 20 min while it has been for a few hours. Those factors make me think it does a full reboot.
Don't know if that helps. If there is anything else let me know aside from that I will flash the new kernel when its out. Thanks for all the great work
Sent from my SAMSUNG-SGH-I777 using xda premium
RE: Random Rebooting
Emil9727 said:
The past two days my phone has been randomly rebooting. It has happened twice in two days. I have no idea how to pull any information from my phone to possibly see what is happening. I am moderatly tech savvy so with good directions I can do just about anything. If anyone is willing to help that would be great.
Phone: At&t GSII (obviously)
Rom: Cognition beta-4
Kernel: Entropy's doom v2
I am using set CPU with profiles. Not over clocking or undervolting, I just use it to underclock when phone gets to hot or battery gets to low.
Anything else you need to know or want me to do please let me know. Thanks.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Very simple fix:
Uninstall SetCPU and reboot the phone and magically it will
no longer randomly reboot.
(you can always re-install it if you don't mind random reboots )
Good Luck!
You think it's set CPU even though I'm not over clocking?
Sent from my SAMSUNG-SGH-I777 using xda premium
SetCPU
Emil9727 said:
You think it's set CPU even though I'm not over clocking?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
How long do you actually think that it takes to simply uninstall
and reboot your phone to see for yourself?
Even if you don't over-clock whatever you do with it can cause
the rebooting problem you are describing.
I certainly am not going to test it for you since I never over-clock
or under-clock anything including my phone and computer.
If the phone was meant to run a lot faster or slower than the
the manufacturers would be advertising the phones with faster
specifications so they can sell more of them.
It's only makes good advertising sense.
Think of it this way, lets say you buy a new car and decided to put
jet fuel into the gas tank to make it have more horsepower so it can
run lot faster than it was designed for, do you think doing this will
make the car more or less reliable in the short or long term?
Misterjunky said:
Very simple fix:
Uninstall SetCPU and reboot the phone and magically it will
no longer randomly reboot.
(you can always re-install it if you don't mind random reboots )
Good Luck!
Click to expand...
Click to collapse
You claim SetCPU is the problem, where is your evidence?
I test my kernels using SetCPU, I have never had a problem.
I keep hearing anecdotes about SetCPU causing problems for people, but there is no way it can possibly cause stability issues. sysfs is sysfs, and that's that.
The only place where SetCPU might cause a problem is with screen-off profiles less than 800 MHz on kernels that don't have the SoD patch.
To the OP - Sorry I didn't release tonight, I got caught up in trying to help someone track down a power management issue with wifi. I'll do it when I wake up.
I am not stupid and the reason I was questioning was because I have OC/UC/UV before and I know what the stability issues are like with them. It is not something that happens frequently so it is hard to test. I have been going now for over 24 hours and no reboot. No changes to set CPU either. Primarily though I wanted a concise way to pull info so I can help people like entropy.
(Off topic a little) Manufactures might UC hardware for a few reasons. Battery capacity and heat are usually two of the big ones. If you stuck your phone in the freezer you could probably OC this phone to 2ghz and run stable. I OC to 1600 for fun and its completely stable. I clock it down if I'm out and it is hot or I am in the sun.
To entropy: its cool I check the forums every hour if not more frequently LOL. I think it has become an addiction. Once the kernel is out let me know what I can do to help.
*Cog + doom = cheat codes*
Sent from my SAMSUNG-SGH-I777 using xda premium
Flash the latest 10/16 releases and if you have another reboot you should be able to pull a /proc/last_kmsg
Entropy512 said:
Flash the latest 10/16 releases and if you have another reboot you should be able to pull a /proc/last_kmsg
Click to expand...
Click to collapse
Will do
Does this new release have OC/UC support?
Emil9727 said:
Will do
Does this new release have OC/UC support?
Click to expand...
Click to collapse
Same as the previous releases, which do.
Alright So here it goes:
Problem: EVO 3D CDMA version constantly locks up when in a screen off state, making it where the unlock button does not work. (Holding down Volume -, Volume +, and Power reboots it) which can mean that it doesn't lock up it actually shuts off..maybe.
What I've tried: Somebody gave me the idea to take the 2.08 RUU and go back to stock, take OTA for 2.17 and reroot and unlock the bootloader using HTC's method (keep in mind i've been on hboot 1.5 the entire time). This didn't seem to help (although did fix a random reboot problem, but besides the point.)
I have also tried uninstalling any application relating to the Prox. Sensor (explanation in notes below)
Notes: I believe everytime that I have seen the issue, the screen has been locked and the phone has been put in my pocket. It virtually never happens when it is out in the open which leads me to believe maybe something with the proximity sensor.
Also this does not seem to be specific to any ROM, Although I have not flashed an AOSP ROM as of yet
Any ways any advice would be appreciated, because as you know a mobile device does spend quite some time in your pocket and it would suck to keep having to reboot it everytime I take it out.
even if you can't provide advice, thanks for reading
almost sounds like it would be a hardware issue with the power button itself... have you tried pulling the battery out and booting into your fastboot screen and into the rom itsself?
ther have also been reports of the handset itself being too warm for it to function...maybe try keeping it out in the open and then unlocking it and see how it works from there... post your results please... im curious now
wloftus said:
almost sounds like it would be a hardware issue with the power button itself... have you tried pulling the battery out and booting into your fastboot screen and into the rom itsself?
Click to expand...
Click to collapse
Yea I can do that easily. The power button works fine, I can keep unlocking/locking whenever, it's just whenever I lock the screen and then put it in my pocket, 95% of the time it tends to lock up (or shut off idk what exactly is going on yet) and then performing a hard reset or taking the battery out will boot it back up
see my edit about the over heating... you responded before i could post it fast enough lol
I had a similar issue. It turned out to be an app. In my case, opensignal maps which is a cell tower and WiFi location app.
Sent from my Clean and MeanROM 3D
wloftus said:
see my edit about the over heating... you responded before i could post it fast enough lol
Click to expand...
Click to collapse
Oh ok, Idk if that could be it. Using it I can leave it out in the open for hours (with wifi tether running and it charging at the same time) and it will unlock and function fine.
but without all of that, 5 min in my pocket and done, I get the lockups/shutoff
guitardoc64 said:
I had a similar issue. It turned out to be an app. In my case, opensignal maps which is a cell tower and WiFi location app.
Sent from my Clean and MeanROM 3D
Click to expand...
Click to collapse
Yea I thought it might have been an app, but ive uninstalled every app I could think might cause the problem so I don't know I can't rule that out though
notsointeresting said:
Oh ok, Idk if that could be it. Using it I can leave it out in the open for hours (with wifi tether running and it charging at the same time) and it will unlock and function fine.
but without all of that, 5 min in my pocket and done, I get the lockups/shutoff
Yea I thought it might have been an app, but ive uninstalled every app I could think might cause the problem so I don't know I can't rule that out though
Click to expand...
Click to collapse
i run the wifi tehter app as well and it will heat up your phone substantially putting in your poclet can be insulating it and then your body heat building it up further... but if you leave it out of your pocket and it performs fine... i would definitely explore that route....
wloftus said:
i run the wifi tehter app as well and it will heat up your phone substantially putting in your poclet can be insulating it and then your body heat building it up further... but if you leave it out of your pocket and it performs fine... i would definitely explore that route....
Click to expand...
Click to collapse
Yes it does, but I most definitely don't run it while in my pocket or in another concealed area. I was just giving an example of when it would be substantially hotter than when in it is in my pocket
notsointeresting said:
Yes it does, but I most definitely don't run it while in my pocket or in another concealed area. I was just giving an example of when it would be substantially hotter than when in it is in my pocket
Click to expand...
Click to collapse
it for sure does not heat up too much running the tether but the insulation of your pocket can be causing it... tether on monitors the battery temp... not the internal temp of the phone itself ... id be more inclined to lean to it over heating
wloftus said:
it for sure does not heat up too much running the tether but the insulation of your pocket can be causing it... tether on monitors the battery temp... not the internal temp of the phone itself ... id be more inclined to lean to it over heating
Click to expand...
Click to collapse
And I could go with that, but compared to using things like Wifi Tether I can tell it gets a lot hotter than when I take it out of my pocket and notice it won't turn on.
And I mean 2-3 Minutes and it locks up ,which is why I said it might be tied into the proximity sensor, and it hasn't been in my pocket every single time, but like 95% it has.
notsointeresting said:
And I could go with that, but compared to using things like Wifi Tether I can tell it gets a lot hotter than when I take it out of my pocket and notice it won't turn on.
And I mean 2-3 Minutes and it locks up ,which is why I said it might be tied into the proximity sensor, and it hasn't been in my pocket every single time, but like 95% it has.
Click to expand...
Click to collapse
againt you MAY be right.... i wont negate that... but the battery temp and the phone temp settings are totally different ill leave it at that bc thats all i can come up with but like i said again... you may be right... i still think it is an overheating on the core hardware of the phone itself....
what ROM?
what kernel?
any cpu control apps?
list of root apps?
il Duce said:
what ROM?
what kernel?
any cpu control apps?
list of root apps?
Click to expand...
Click to collapse
Currently using MeanROM, but have also seen the issue in my time using, CleanROM Reborn, and Eternity 3.0.
Always stock OTA Kernel at stock clock speeds.
There have been times when I have used SetCPU and times when I haven't, never a difference.
Root Explorer, Titanium Backup,SetCPU,SuperUser (of Course), Wireless Tether App,
notsointeresting said:
Currently using MeanROM, but have also seen the issue in my time using, CleanROM Reborn, and Eternity 3.0.
Always stock OTA Kernel at stock clock speeds.
There have been times when I have used SetCPU and times when I haven't, never a difference.
Root Explorer, Titanium Backup,SetCPU,SuperUser (of Course), Wireless Tether App,
Click to expand...
Click to collapse
fyi it's quite possible those ROMs set a LOW minimum (sleep) frequency, which SOME devices don't like. stock (like HTC stock) is 384000, but a LOT of devs set theirs to 192000 to conserve battery.
check here and report YOUR value:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
if it's 192000 that's likely your problem, set it to 384000. if it's already 384000 then it's something else, you ever looked at the scripts you have in init.d and what they're doing?
EDIT: and if you REALLY wanna know what's happening and what's erroring, hook up adb and watch the log, pull a last_kmsg, dmesg, etc. Maybe it would help narrow things down
il Duce said:
fyi it's quite possible those ROMs set a LOW minimum (sleep) frequency, which SOME devices don't like. stock (like HTC stock) is 384000, but a LOT of devs set theirs to 192000 to conserve battery.
check here and report YOUR value:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
if it's 192000 that's likely your problem, set it to 384000. if it's already 384000 then it's something else, you ever looked at the scripts you have in init.d and what they're doing?
EDIT: and if you REALLY wanna know what's happening and what's erroring, hook up adb and watch the log, pull a last_kmsg, dmesg, etc. Maybe it would help narrow things down
Click to expand...
Click to collapse
It was set to 486mhz
And I was going to pull a logcat, but since this seems to happen when in a pocket for some reason its hard to keep it connected to a cable lol, but ill try the others
seriously the most simplest of answera isa the one over looked.....it sounds too basic and the rest are over delving in to the matter sometimes the right answer is tho most simplest.....
wloftus said:
seriously the most simplest of answera isa the one over looked.....it sounds too basic and the rest are over delving in to the matter sometimes the right answer is tho most simplest.....
Click to expand...
Click to collapse
Well I think im going to go back to stock unrooted via RUU for a couple days, this will be the most obvious way to figure out if it is an overheating/hardware problem.
But in using the device, and seeing the conditions this problem arises in , it just doesn't feel like it. but hell you might be right lol , we'll see
notsointeresting said:
Well I think im going to go back to stock unrooted via RUU for a couple days, this will be the most obvious way to figure out if it is an overheating/hardware problem.
But in using the device, and seeing the conditions this problem arises in , it just doesn't feel like it. but hell you might be right lol , we'll see
Click to expand...
Click to collapse
Have you made any progress with this? I think I have the exact same problem you have. At first I thought it was because of the pocket, but now I figured out it only freezes if the screen is turned off and the phone is not connected to a charger.