Related
How well is the radio working with older RUU? Also, how is the battery life?
Haven't really had a chance to test it. I installed SetCPU to make profiles when the screen is off and etc. Hopefully by tomorrow I will know how it goes. I only made it 8hrs on the "Out of the Box" config. So hopefully this puts a few more hours on to it.
any idea how high we can over clock?
Stock Kernel you cannot overclock
how much space do you have availible once bloatware is removed?
honestly I haven't personally deleted much of anything, as I am afraid that like other Verizon phones. I may delete a key app, that will disable the phone. Until I get a proper recovery going I have to say, you will need to find someone with more balls that I.
I suppose I could go re-flash the custom RUU that was made for rooting to get it booting again, as I have saved many people's non booting phones that way. However that would require more time than I care to waste, since I have alot of work related info I just got restored on the phone.
i sucked down 50% battery in 6 hours, not really using it much more than a few texts... and i have the LTE radio turned off in the service menu.
and, on the RUU with r/w system the phone was choppy / slow.
that sounds like my stock TB, but I use it a lot
gsxr1kmatt said:
i sucked down 50% battery in 6 hours, not really using it much more than a few texts... and i have the LTE radio turned off in the service menu.
and, on the RUU with r/w system the phone was choppy / slow.
Click to expand...
Click to collapse
Looks like I will wait til we can root the current firmware
LTE on the older RUU used for root is horrible.. Compared to my buddies stock TB, he's pulling over 15 meg down.. I couldn't get more than 3 ever..
Flashed back to stock and now my speeds line up exactly with his.
I am getting 14Mbps with Wireless Tether right now! Not too bad.. haven't noticed any difference with the older rooted firmware... keeping this until CM7 for TB!
So, I have one of the first Vibrants to hit the store. I'm running Neobuddy ICS Passion V8. Before the *****ing begins I want to say that I love this rom.
I followed the install instructions to a "T".
I used antutu cpu master to overclock to 1.3 because I read that other people were doing it and didn't see any complaints. When my phone booted to the point where the message that cpu master had superuser privileges came up, it froze and the display changed colors getting lighter and washed out looking. That scared the crap out of me and I thought I had just cooked my cpu. I pulled the battery and rebooted then tried to open the app and change the settings before it froze and failed, rebooting 6 times, battery pull each time. I finally relented and did a factory reset. Previous to this adventure I had it clocked at 1Ghz max and 100 min and was experiencing no lag. I just got greedy. I only changed it at all because I was getting 16 hours of battery life and thought I could trade some battery for speed. I have it running at 1.2 now and it's fine. So this is not so much a question but an answer to anyone who might be asking themselves if they should overclock to 1.3.
Bugs
mute/unmute necessary for incoming call audio
automatic brightness not responsive
complaints
contacts app doesn't match the rest of the theme
no text button next to phone button on contact
no long press functionality on contact
When it comes to Vibrants, all our phones are different. Some users will be able to run at 1.3 from now until our Zombie overlords take over and we're forced into indentured servitude. Others, like you and I will be lucky to run a mild OC without freezes.
I used to oc to 1.6 ghz on cm7
sent from the xda app on my android smartphone.
What he said!
younix258 said:
I used to oc to 1.6 ghz on cm7
sent from the xda app on my android smartphone.
Click to expand...
Click to collapse
My first Vibrant T959, manufactured prior to Oct 2010, used to fly, and overclock like there wasn't any tomorrow, and would flash anything! Was the most cooperative phone I ever had! Wish my wife was like that. LOL
Then I unfortunately got into a true HardBrick with it, and stupidly, instead of JTAGing it, got T-Mobile to exchange it, for a same model, but with a manufacturing date on it of 8-2011!
And this replacement phone, hasn't even ever performed as well as the old one, despite how I set it up, And at first it was stuburn as hell to get it to cooperate with flashing, until I unlocked it, and it calmed down alot, even though that makes no sense at all, but nun the less, it is what it is!
Point is, that each week, month or quarter, the phones aren't consistent in manufacturing qualities or how they run and perform, or the components they use. I had a Thoroughbred in the beginning, and now I how a plow horse, yes she still works well, but needs alot of coaxing, I had to re-do the GPS contacts right so there was firm pressure, and the SW flashes were a ***** in the beginning!
But I believe when this phone first came out, there was better quality of manufacturing and they used the same consistent components, until they shifted their focus on other models to push onto the market!
So again, what Billy Bobs got going with his, Isn't what it ll be with yours!!
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.
Many have complained about issues with the kernel in ICS. On any build, it is vital that you not use setcpu or any other cpu scaling app. Don't change the max/min freq, don't change the governer, nothing. Perflock will constantly reset any changes and cause the cpu to run at either full throttle or full min - no in between. Until we get kernel source and custom kernels, this will always be the case. It's something HTC does.
Many cpu monitor apps will do the same. The link in my sig has more info, and a link to a cpu monitor app that is safe to use with our kernel.
Actually when I was on the second ics leak, and setcpu worked fine. I know this because I benchmarked before and after setting frequencies
Sent from my ADR6425LVW using XDA
benchmarking doesn't mean it wasn't running at full tilt when you didn't need it to. unless your kernel magically doesn't include perflock, it was.
also, there are some combinations of setcpu and monitoring that will work. at one point if i used setcpu, cpu monitor, and one other which i forget now, it would work, kind of. definitely not recommended.
Thats why I deaded mine. Phone was constantly overheating
Sent from my ADR6425LVW using xda premium
since i stop fighting with the kernel i've had nothing but great battery life and performance since the first ICS leak.
tsp, what i don't understand is why something like system panel, which shows you scaling (but doesn't let you change it) showed the proper correct scaling between 384 and 1512 and hardly EVER hit full throttle on GB, but on ICS, it's always showing full throttle.
then i installed your widget you showed me, and it showed constantly chagning like system panel used to on GB.
any idea why? which one is rgiht??
tspderek said:
since i stop fighting with the kernel i've had nothing but great battery life and performance since the first ICS leak.
Click to expand...
Click to collapse
Agreed. I had set CPU try to disable perflock and limit to 1200mhz on conservative and it ended up being worse battery and slower overall.
You're exactly right I advise everyone I discuss the topic with to make sure and avoid trying to over ride perflock with a CPU management app. It causes a conflict in my opinion which is a huge battery drain and also causes excessive heat due to the process of fighting for its life.
Sent from my ADR6425LVW using xda premium
I've been saying this I even started a thread to smash this rumor of ICS kernels running bad...apparantely people like to give out wrong information on these forums, reminds me of the news channels.
THERE WAS NEVER ANYTHING WRONG WITH ANY ICS LEAKS. JUST USER FAULT
Sent from my ADR6425LVW using XDA
richii0207 said:
I've been saying this I even started a thread to smash this rumor if ICS kernels running bad...apparantely people like to give out wrong information on these forums, reminds me of the news channels
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
You are correct. I would say upwards of 20% of what I read here is incomplete or straight up wrong.
con247 said:
You are correct. I would say upwards of 20% of what I read here is incomplete or straight up wrong.
Click to expand...
Click to collapse
My favorite part is when they try to sound like a dev, I guess everyone's a dev on here ;-P. At least I only say something I know from EXPERIENCE and not what I read ;-)
Sent from my ADR6425LVW using XDA
jayochs said:
tsp, what i don't understand is why something like system panel, which shows you scaling (but doesn't let you change it) showed the proper correct scaling between 384 and 1512 and hardly EVER hit full throttle on GB, but on ICS, it's always showing full throttle.
then i installed your widget you showed me, and it showed constantly chagning like system panel used to on GB.
any idea why? which one is rgiht??
Click to expand...
Click to collapse
the widget i posted is what you want. it should be scaling up and down, and settling eventually when nothing is really going on. the system panel that you tried clearly affected the perflock in some way. from what i understand, some apps/widgets look at the cpu itself, while others hit up the kernel for status. the ones that hit up the kernel are the issue. i'm not 100% on this, that's just what i've been told. all i know is my experience seems to match this.
tspderek said:
Many have complained about issues with the kernel in ICS. On any build, it is vital that you not use setcpu or any other cpu scaling app. Don't change the max/min freq, don't change the governer, nothing. Perflock will constantly reset any changes and cause the cpu to run at either full throttle or full min - no in between. Until we get kernel source and custom kernels, this will always be the case. It's something HTC does.
Many cpu monitor apps will do the same. The link in my sig has more info, and a link to a cpu monitor app that is safe to use with our kernel.
Click to expand...
Click to collapse
Hmm, that's weird, cause I've been using setCPU with ICS on the Rezound for months and it works great! My CPU scales fine and hits all the frequencies its supposed to. The min and max frequencies do change around seemingly randomly, but anyone can see by watching the current frequency display that it is always somewhere in between the range I selected, and always appropriate for the system load.
I've always had CPU Master installed. I just removed it, we'll see how it goes.
Im running a fascinate with cm10 nightly, stock kernel. I was hoping to overclock cpu to 1200 mhz, and I can't figure out a way to do it. I tried changing the gorverner, but they're all capped at 1000 mhz. What can I do?
Lootzifer said:
Im running a fascinate with cm10 nightly, stock kernel. I was hoping to overclock cpu to 1200 mhz, and I can't figure out a way to do it. I tried changing the gorverner, but they're all capped at 1000 mhz. What can I do?
Click to expand...
Click to collapse
You need a kernel that is capable of overclocking. If you look through the Development thread, you can find one to do so.
Lootzifer said:
Im running a fascinate with cm10 nightly, stock kernel. I was hoping to overclock cpu to 1200 mhz, and I can't figure out a way to do it. I tried changing the gorverner, but they're all capped at 1000 mhz. What can I do?
Click to expand...
Click to collapse
youll wanna find the devil kernel in development
Lootzifer said:
Im running a fascinate with cm10 nightly, stock kernel. I was hoping to overclock cpu to 1200 mhz, and I can't figure out a way to do it. I tried changing the gorverner, but they're all capped at 1000 mhz. What can I do?
Click to expand...
Click to collapse
download devil 1.6.1 for fascinate
Newest is 1.7.4 actually, get it from http://rootaxbox.no-ip.org/derteufel/Helly_Bean/kernel/
Crawshayi said:
Newest is 1.7.4 actually, get it from http://rootaxbox.no-ip.org/derteufel/Helly_Bean/kernel/
Click to expand...
Click to collapse
Yeah, but at the time I didn't realize he made a new folder for 1.7., so I looked but all I found was 1.6.1.. but at least, 1.6.1 won't screw your Rom if you have an old partition (current being nightly cm10)--I learned that the hard way.
Sent from my Nexus 7 using xda app-developers app
Actually 1.6.1 was for the newer partition layout I think the last one he made for the old one was 1.5.4 or something. Anyway, he just released 1.7.5 last night, grab it from http://rootaxbox.no-ip.org/derteufel/jellybean/175/ :good::good:
im using the 1.7.5 release on LagFree
i dont want to overclock it tho because idk if it would mess up my phone .
Crawshayi said:
Actually 1.6.1 was for the newer partition layout I think the last one he made for the old one was 1.5.4 or something. Anyway, he just released 1.7.5 last night, grab it from http://rootaxbox.no-ip.org/derteufel/jellybean/175/ :good::good:
Click to expand...
Click to collapse
[er, I kinda meant to say "if you have the new partition layout," not old..]
but well...... :S I was right and wrong, because the old partition layout [with /datadata] is technically the "old" layout [the one that everybody always had], until for some reason they decided to move it around, so that you only had 400MB for apps, which I quickly ran out of after restoring my TiBu apps...and then they finally came around and put /datdata back, so theoretically it's the "new" layout, but..well yeah, hopefully you know what I mean.
mvmacd said:
[er, I kinda meant to say "if you have the new partition layout," not old..]
but well...... :S I was right and wrong, because the old partition layout [with /datadata] is technically the "old" layout [the one that everybody always had], until for some reason they decided to move it around, so that you only had 400MB for apps, which I quickly ran out of after restoring my TiBu apps...and then they finally came around and put /datdata back, so theoretically it's the "new" layout, but..well yeah, hopefully you know what I mean.
Click to expand...
Click to collapse
The reason it was moved around and suddenly you only had around 400MB was because the Fassy has 2 chips, 1 is fast as hell and the other is slow. Problem was, the fast chip only had so much storage space, so that was the trade off, good performance but poor storage space. For the newest layout, Jt didn't simply just 'put back' /datadata, the new layout actually is a completely new arrangement that gives us the fast speed AND storage space. If you want to read about it go over to the CM10 thread on Rootzwiki, Jt explained what he did. What this means in practical terms is that we now have a device with good speed and storage space that can handle the newer Android OSes :good:
whats the worst that can happen if you overclock ?
AndroidGee209 said:
whats the worst that can happen if you overclock ?
Click to expand...
Click to collapse
Short term: Glitchy behavior (freezing/crashing/etc) and random reboots (this is more likely if you're doing Live OC versus just bumping up your CPU MHz)
Long term: Shortened device lifetime due to component stress; in other words if you plan to use your phone for a very long time don't overclock
Not all phones react the same way to overclocking, you might not get the same results as others are. For example, a lot of people seem to have good luck with 110% Live OC, however I can only get 105% on my phone before it becomes unstable.
Crawshayi said:
The reason it was moved around and suddenly you only had around 400MB was because the Fassy has 2 chips, 1 is fast as hell and the other is slow. Problem was, the fast chip only had so much storage space, so that was the trade off, good performance but poor storage space. For the newest layout, Jt didn't simply just 'put back' /datadata, the new layout actually is a completely new arrangement that gives us the fast speed AND storage space. If you want to read about it go over to the CM10 thread on Rootzwiki, Jt explained what he did. What this means in practical terms is that we now have a device with good speed and storage space that can handle the newer Android OSes :good:
Click to expand...
Click to collapse
Exactly
AndroidGee209 said:
whats the worst that can happen if you overclock ?
Click to expand...
Click to collapse
You remember that Mayan end of the World thing...
Crawshayi said:
Short term: Glitchy behavior (freezing/crashing/etc) and random reboots (this is more likely if you're doing Live OC versus just bumping up your CPU MHz)
Long term: Shortened device lifetime due to component stress; in other words if you plan to use your phone for a very long time don't overclock
Not all phones react the same way to overclocking, you might not get the same results as others are. For example, a lot of people seem to have good luck with 110% Live OC, however I can only get 105% on my phone before it becomes unstable.
Click to expand...
Click to collapse
Again, exactly...
Yep I accidently at my OC too high once and I got an immediate reboot, setting itself back to std
Sent from my swagger