GNEX over clocking questions - Samsung Galaxy Nexus

I've made a account for this post and sorry if I posted this in a wrong section,
I have a gnex running 6.0.1 android, and its only able to get to 1.65ghz.. But thing is my goal for this phone is to make it feel more faster and more "up to date" with the other phones out there.
I am wanting to use another kernel for over clocking, but I don't know if I have to switch ROMs as this kernel that supports 2.0ghz.. But it was released back in 2013.. GlaDOS kernel is the name of it supposedly.
Can I still use that kernel? And what other stuff can I do to the phone aswell? The phone works fine except it keeps crashing on my or freezing then reboots it self, then I have to take the battery out and back in to have it start up again. Also when ever I turn WiFi on on there it lags my phone like crazy, and drains my battery under 20-30mins I have no charge left.
Anyone have any suggestions or tips? Thanks!
And when it does work fine the temperature CPU, reach well over 70c.. great hand warmer in Canadian winters
I just want the 2.0ghz or anything higher than 1.6 as I need the performance. I can't stand having the phone lagg every day I use it.

Related

[Q] advice on Undervolt/havs and overclocking

Yesterday I put the netarchy havs less kernel on my phone and with some stress testing and general testing found that it worked well at 1.15 mhz. I carried it around all day messing with it no problem. Today, the real test came when I ran GPS on my phone in my car. The phone lasted about 3 minutes of GPS before it started rebooting. Then my 4g was broke from it somehow. Anyhow, I restored my phone and all seems well now.
I still want to mod the voltage and clock speed. Any advice on this? The phone always gets hot when I use GPS because it uses a lot of processor, frequently its on the charger and possibly in sunlight. When it was not overclocked or undervolted my phone NEVER reboots not once since I've had it.
Is the problem the undervolting, overclocking or both? Should i give up on this due to the way I use my phone?
Thanks in advance.
Try different kernels. I use netarchy sbc 4.2.2 more havs, works great. I also use his 4.3.4 more havs sbc. They both work for me. Battery life is awesome and gps works good. No prob here. Try those out and see what happens. Hope this helps.
Sent from my HTC EVO Phone, should'nt we all have one?
Okay so is there any danger to this? It seems like every time my phone starts rebooting from overclocking or undervolting apps start disappearing from my phone and stuff stops working.
I use amon RA 2.3 and every time I recover it works again but I was just wondering how dangerous it is for me to experiment they way I have been. I have already recovered my phone 3 times from issues like this that broke it.
Every phone reacts differently to kernels, undervolting, and overclocking so you will have to experiment to find out what works for you and what doesn't. Just make sure that you dont check the "set on boot" box until you know your setup is stable. A reboot shouldn't hurt anything though.
I am running Netarchy 4.3.4 more havs, overclocked to 1190 and it's as stable as can be on my phone. However, if I go over 1190 it immediately locks up and reboots.
Sent from my HTC EVO 4G with Tapatalk
kd0axs said:
Every phone reacts differently to kernels, undervolting, and overclocking so you will have to experiment to find out what works for you and what doesn't. Just make sure that you dont check the "set on boot" box until you know your setup is stable. A reboot shouldn't hurt anything though.
I am running Netarchy 4.3.2 more havs, overclocked to 1190 and it's as stable as can be on my phone.
Sent from my HTC EVO 4G with Tapatalk
Click to expand...
Click to collapse
Yeah but the reboots are hurting my phone! I have to restore it due to the problems the reboots and freezing causes (sometimes I have to battery pull due to full lockup). 2 times when I pulled battery due to full lockup apps went missing from phone memory but the available space on the phone was as if the apps were still there. Another time my 4g wouldn't turn on.
Is that abnormal? Can it mess up my phone in a way that recovering wont be able to fix or is recovering generally a sure shot?
The reboots should not be hurting the hardware, unless you overclock excessively. What the reboots are doing is corrupting your file system because open files do not get closed properly.
Are you after speed or battery life? I think the two are mutually exclusive. If you have great speed (be it governor or because of overclock), you will pay the price in battery life. I think the trick is to find the balance between the two that suits *you*.
gpz1100 said:
The reboots should not be hurting the hardware, unless you overclock excessively. What the reboots are doing is corrupting your file system because open files do not get closed properly.
Are you after speed or battery life? I think the two are mutually exclusive. If you have great speed (be it governor or because of overclock), you will pay the price in battery life. I think the trick is to find the balance between the two that suits *you*.
Click to expand...
Click to collapse
Because I use the 1-1-1 power management system (see sig) my main concern is performance. I love my phone and when I use it I want it to be fast and smooth. I would *prefer* if the extra speed didn't dramatically change my battery life but I'm okay with a small decrease in battery life if the speed gain is reasonable for the tradeoff. Anyhow I thought a lot of people ran HAVS along with overclocking to have both to a degree.
Only time I charge my battery is when I am using it in the car with my car charger. At home I charge all my batteries on an external charger - my phone is a mobile device I prefer to never be bound to a cord. I sleep with my phone next to me off the charger lol.
Okay so my phone is running more HAVS now and it seems the same as before so I guess my friend is HAVS friendly. I will run this for a day to check if any reboots happen and aim for tomorrow to overclock again. It may have been the 1.19 mhz that caused the issue. I will drop it down to 1.15 or 1.1 and see if its stable.

So is it just my epic?

So no matter what rom i load on my phone i get the same thing.... it will not wake up and i have to remove the battery. Now on stock its fine! but any rom.. and yes i have tried them.. numerous times.. Right now i have AOSP genocide 2 and its working the best. I can go 4 or 5 hours before i need to do a battery pull (sometimes). This morning i have had to do i battery pull twice but now it seems to be fine.
Now its not over clocking that is doing it. I have been all through that. My phone blazes when at 1.3ghz but will not turn back on ever with out a battery pull. right now there is no overclocking and voltage control is denied root. This seems to be working the best.
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
NissanNick said:
So no matter what rom i load on my phone i get the same thing.... it will not wake up and i have to remove the battery. Now on stock its fine! but any rom.. and yes i have tried them.. numerous times.. Right now i have AOSP genocide 2 and its working the best. I can go 4 or 5 hours before i need to do a battery pull (sometimes). This morning i have had to do i battery pull twice but now it seems to be fine.
Now its not over clocking that is doing it. I have been all through that. My phone blazes when at 1.3ghz but will not turn back on ever with out a battery pull. right now there is no overclocking and voltage control is denied root. This seems to be working the best.
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
Click to expand...
Click to collapse
Are these freezes ONLY happening when running o/c? If so, then your hardware might not like o/c speeds. Please clarify that it is not an o/c issue due to the information you provided above.
If you're stable and having no locking issues on stock, then flash ROMS/kernels and of the bat start boosting to o/c speeds then seeing instability, how/why are you ruling out it's not a o/c or hardware limitation?
NissanNick said:
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
Click to expand...
Click to collapse
I don't think sprint will swap your phone out just because you can't manage stable o/c speeds on your phone. LOL
Sounds like you need to do the classic Wipe 3X before flashing.
Sorry guys i should have been more clear. I am not a noob i always wipe 3x. It is not a O/C issue. I have gone through all the clocking and my phone just does not like it.. I can live with that. What i am saying is even when not O/C and denying all access from anything that could effect my processor the ROM's Still don't work right. They freeze even with NO O/C at all! Every one of them. So i am thinking i just got the bad end of the silicon?
Also i relies Sprint will not just exchange my phone.. But im sure i could come up with something lol.
Well i really like my epic but i am thinking of switching to the photon if i cant get the ROMS to work right. I really wanted to wait until next year to upgrade.
NissanNick said:
Sorry guys i should have been more clear. I am not a noob i always wipe 3x. It is not a O/C issue. I have gone through all the clocking and my phone just does not like it.. I can live with that. What i am saying is even when not O/C and denying all access from anything that could effect my processor the ROM's Still don't work right. They freeze even with NO O/C at all! Every one of them. So i am thinking i just got the bad end of the silicon?
Also i relies Sprint will not just exchange my phone.. But im sure i could come up with something lol.
Well i really like my epic but i am thinking of switching to the photon if i cant get the ROMS to work right. I really wanted to wait until next year to upgrade.
Click to expand...
Click to collapse
It's not the overclocking that causes your phone to go into sleep of death, it is the low end. 100 Mhz causes sleep of death on a lot of phones on a custom ROM. Set your minimum frequency to 200 Mhz and you will be fine. Don't change any of the stoick voltages.
Try using stock speeds (400-1000). Then work your way incrementally in both directions to see which frequency(ies) cause your issues. Each phone is unique, so find the sweet spot.
I get the black screen of death about twice a month running twilight 1.1.1. My phone runs 200-1000 with no undervolting and set on conservative. I'm just too lazy to bother playing with settings since I'm holding out for SRF 1.3 to release.

[Q] Defy+ Temporary bricking due to overheating?

Yeah, got a major issue: My Defy+ is overheating and I usually end up with a blocked phone, which ends up being useless for about 4-5 hours. And it's becoming more often.
I have 2.3.4 on it, but I seriously doubt 2.3.6 solves this issue.
Any tips?
Deformat said:
Any tips?
Click to expand...
Click to collapse
Try custom ROM's and DO NOT flash 2.3.6 full sbf as it's quite buggy and you'll be stuck with it.
You could also try to undervolt the CPU. In what conditions do you get an overheated phone?
vap_66 said:
You could also try to undervolt the CPU. In what conditions do you get an overheated phone?
Click to expand...
Click to collapse
How could I do that?
Also, I get it for no reason whatsoever. It gets overheated and that's it. I left it to cool about 4 God damn hours, and yet when I open it it works a bit, then it gets stuck. It's as if the memory isn't well processed.
To give ya an example, I left it over night and even charged it. Everything went fine.Then, got to school, got a break, wanted to listen to a song. Fine, listened to a song. A guy wanted to waste some time on Opera Mini with his Ikariam game. Fine, let him waste that 1 tab and browse online.
But then, when he gave it to me it was stuck.
Wait a lot of time to stop it via Android's button, did it eventually. Left it to cool 2 hours, tried again. Again, after less than 3 minutes of usage (wanted to share a file via bluetooth, but got to the folder only) it got stuck again. This time it was pointless, 30 minutes later I wasn't able to stop it so I took the battery off.
I kinda don't know if I should change it or still have faith in it.
Right now stuff seems worse. Sometimes it reboots itself, but that doesn't help with anything IMO.
BTW, would the 1% battery patch help? Might put that 720p functionality in there as well.
As Auris said, try flashing a custom ROM (CM7.2 is a good choice, stable and fast enough). For undervolting (if you are on a stock ROM only - because CM7 has a built-in CPU manager, accessible from the bootmenu) ), install SetVsel from the Play Store. Like PC overclocking/undervolting, be careful about the values you choose. You'll find a thread in the General section about SetVsel values.
If these ideas don't help you solve your problem, I think it might be hardware related.
Trimis de pe Defy CM9
My defy+ gets really hot on just about everything except stock! Undervolting didn't help, nor underclocking. Putting it in the fridge temporarily helped, but when I started using it again the temp climbed again!
What should I do? :-/
Sent from my Defy+ using Tapatalk 2 Beta
Well, since you flashed custom ROMs (unlike the OP), how about the baseband? I remember that when I flashed CM7 for the first time I didn't get 3G signal and the phone was overheating because the signal was too poor for the baseband that I used. Switched between a few and finally managed to get one with good signal and 2G/3G/3.5G working fine.
I never use 3G, so I've never bothered changing it. By the way... what are the differences between basebands with the same frequencies?
Could flashing a different kernel solve it?
Sent from my Defy+ using Tapatalk 2 Beta
Well, there are different regions - I don't know the technical details, but maybe some basebands work better with certain network operators. It's a trial&error method, you could choose one that works better or one that performs worse.
Regarding the kernel: I have no idea about the heat dissipation, but from what I've read there is a GB kernel that supposedly has better battery life. Ask Auris, he uses it (it's the kernel by walter79).
Okay, seems the issue solved itself, since now it works perfectly :|
I didn't play a game, which was kinda retarded: low quality, a simple Android game, and playing Temple Run/Angry Birds/ Angry Birds Space didn't give you me any issue.
I don't get it.

[Q] Battery Life?

Hey there XDA, got a question for ya.
I've had my AT&T S3 for a while now and I love the phone a lot, the only thing that is plaguing me is the battery life.
Now for a phone with dual core processors, a nice Super AMOLED screen that runs at 720, all the connections that you'd ever want, I expect it to use some battery life, but I feel like I should be doing better than I should.
When I'm browsing the internet or reddit I can watch the percentage just slowly crawl down. Within 30 min or so I've gone through 7-8% I want to say. Not 100% sure, but the numbers have been enough to make me concerned.
Currently I am running Diet ICS 08.08.12 with no major modifications other than the apps I use and Apex Launcher.
I've got my BetterBatteryStats dump and a screenshots of the battery page from System from last night. I'm attempting to use Juice Defender today (I've tried it in the past and it did alright) as well as Samgsung's battery saving mode (which seems to prevent the processor from going over 1.0 Ghz), which as of right now I'm at 36%. I feel like I can do better than that
So, thoughts? Opinions?
What kernel are you running?
mdg071191 said:
What kernel are you running?
Click to expand...
Click to collapse
I don't think Diet ICS swapped kernels, so stock as far as I'm concerned.
Alright. For stock kernel (I'm not too sure about with power saving), those numbers are fairly decent. I was able to get some better numbers on faux123's TW kernel (the 1.65ghz, not 1.85), but I can't be too sure of the exact time, as I'm currently on 1.85ghz OC, and I charge my phone nightly. You could try other kernels, and just roll back with a nandroid to this one if you do not like the difference.

Puzzling Random Reboot Issue

I've been trying to figure this out for months and have had no luck so I wanted to see if any of you had any recommendations.
I used to run Sense roms like the stock one and the sense 2.1 mctwist rom and they had no issues.
When CM9 came out, I decided to switch over to that. It functioned fine except I would get random reboots about 1-2 times each day. Tried clean installs, etc but nothing work.
Then CM10 came out and I upgraded. Once again, it works excellent except I still get random reboots once or twice a day.
And just recently I tried the AOKP Jelly Bean ROM, hoping it was a CM issue, but I also got the random reboots on AOKP.
What could be causing this? Occasionally I can go through the day without a reboot, but 9 out of 10 times, I get at least one reboot each day. Sometimes it happens while it's in my pocket and I don't even notice for a few hours.
These reboots are basically the phone starts showing the boot animation, but with a very dim screen and it just stays stuck with the spinning boot animation. It won't reboot until I pull the battery or do the 3 button reset.
Any advice? Should I try a different radio or...? I don't even know. I love JB so much so I'd hate to have to go back to a sense rom, but I can't take these reboots anymore.
Thanks
jpzsports said:
I've been trying to figure this out for months and have had no luck so I wanted to see if any of you had any recommendations.
I used to run Sense roms like the stock one and the sense 2.1 mctwist rom and they had no issues.
When CM9 came out, I decided to switch over to that. It functioned fine except I would get random reboots about 1-2 times each day. Tried clean installs, etc but nothing work.
Then CM10 came out and I upgraded. Once again, it works excellent except I still get random reboots once or twice a day.
And just recently I tried the AOKP Jelly Bean ROM, hoping it was a CM issue, but I also got the random reboots on AOKP.
What could be causing this? Occasionally I can go through the day without a reboot, but 9 out of 10 times, I get at least one reboot each day. Sometimes it happens while it's in my pocket and I don't even notice for a few hours.
These reboots are basically the phone starts showing the boot animation, but with a very dim screen and it just stays stuck with the spinning boot animation. It won't reboot until I pull the battery or do the 3 button reset.
Any advice? Should I try a different radio or...? I don't even know. I love JB so much so I'd hate to have to go back to a sense rom, but I can't take these reboots anymore.
Thanks
Click to expand...
Click to collapse
It could be an app causing it, or overheating. Do you over/under clock/volt? You may want to try underclocking a little, or raising the voltage a little. You may also want to check the system and kernel logs to see if they reveal the issue.
cmlusco said:
It could be an app causing it, or overheating. Do you over/under clock/volt? You may want to try underclocking a little, or raising the voltage a little. You may also want to check the system and kernel logs to see if they reveal the issue.
Click to expand...
Click to collapse
I used to overclock on my sense roms with no issue. But on CM10 I just have it set to stock speeds with no overclocking or adjusting the voltage. Could my phone be getting old and so even stock speed is causing overheating? My phone doesn't feel noticeably hot, unless it gets stuck in one of these reboots. Then it feels rather warm. What would you recommend I change my voltage to?
And I tried doing logs but they get wiped when I restart
EDIT: Odd thing I just discovered. I borrowed my friend's seido extended battery for the dinc and popped it in my phone. After charging it up for a bit, I used the phone and within 10 minutes it started acting weird and rebooted. And after restarting, it rebooted again a few minutes later. So basically it was even worse. Any correlation here? Does the extended battery = more heat = that's why my phone is rebooting?
It's hard to even guess unless you can get a log. If you give one of the stock based ROMs another trial for a few days, and the phone does not reboot, then it is safe to say it is not hardware. I'd start by at least ruling out the hardware possibility.
Do not use Titanium or some other app to restore any sort of data from one ROM to another. That often seems to cause a lot of people problems.
If your phone isn't that hot, I agree that heat isn't likely the problem. Mine absolutely roasts while navigating (while charging, screen on, gps and 3g antennas on, music playing, overclocked, weak original stock battery, otterbox case so it can't breathe, etc.) and it doesn't ever reboot from heat.
Everyone uses their phones differently. So what may be stable for one person might not be for others. I've come to the conclusion that there is only one person who can determine if a ROM is stable... that is the one person who uses it everyday. Just because some other people are using a ROM and getting good results, it doesn't mean that you ever will (even with you wiping/flashing/installing apps by the book).
CM9, CM10, or any and all ICS and JB roms are going to have things that aren't working right for some time still. It's just the nature of the beast. App compatibility, especially, is just one of those things. It's a testament to how good those awesome devs are that anything works on our Dinc running JB and ICS.
I never ran the ICS and JB ports for long (in fact only very short periods of time) because my problems far outweighed the benefits. There is no shame in GB working better for you. I run a variant of CM7 (which is gingerbread)... it is definitely different than stock-sense. Then I use alternate launchers (Go launcher is my favorite) to change it up even more. You can do so much customization that isn't dependent on the ROM. Then I can use something like ROM TOOLBOX PRO for even more customization.
Software is not fashion. What actually works never goes out of style (despite what the hipster kids on xda might be saying ...get off my lawn... grumble...)
jpzsports said:
I used to overclock on my sense roms with no issue. But on CM10 I just have it set to stock speeds with no overclocking or adjusting the voltage. Could my phone be getting old and so even stock speed is causing overheating? My phone doesn't feel noticeably hot, unless it gets stuck in one of these reboots. Then it feels rather warm. What would you recommend I change my voltage to?
And I tried doing logs but they get wiped when I restart
Click to expand...
Click to collapse
I would use incredicontrol and raise all max voltages by 25 or one push of the plus button. Sometimes as phones get older the processors get worn , and have issues with not enough power or even with the stock max frequencie of 998mhz. If raising the max voltage dosent help, i would underclock down from max 998.
Thank you both for the replies. I really appreciate it. I'll try overvolting and see how it goes tomorrow. If I still get reboots, I'll try running a stock rom for a few days and see how it performs.
jpzsports said:
Thank you both for the replies. I really appreciate it. I'll try overvolting and see how it goes tomorrow. If I still get reboots, I'll try running a stock rom for a few days and see how it performs.
Click to expand...
Click to collapse
Pardon me harping on my pet issue, but my phone does that if I underclock the CPU minimum to 128MHz. If I leave it at 245 I can go for days on end (I've seen uptimes of over 200 hours). For whatever that's worth...
musical_chairs said:
Pardon me harping on my pet issue, but my phone does that if I underclock the CPU minimum to 128MHz. If I leave it at 245 I can go for days on end (I've seen uptimes of over 200 hours). For whatever that's worth...
Click to expand...
Click to collapse
That is true, if i go down to 128 i have screen on freezing issues, and random reboots.
EDIT: Odd thing I just discovered. I borrowed my friend's seido extended battery for the dinc and popped it in my phone. After charging it up for a bit, I used the phone and within 10 minutes it started acting weird and rebooted. And after restarting, it rebooted again a few minutes later. So basically it was even worse. Any correlation here? Does the extended battery = more heat = that's why my phone is rebooting?
Click to expand...
Click to collapse
This is certainly a clue... but I don't know what it means...
I would not think the the extended battery would produce more heat. Since both batteries should be discharging at the same rates the heat output should be the same (just that the bigger one would take longer since it has more reserve). I've ran across stories of people who had phones that went completely wonky when they tried swapping batteries or getting a new one. I really don't know anything about it, I'm still on my stock battery.
It certainly couldn't hurt to try wiping your battery stats in clockwork. There is apparently some magic methodology to do it "correctly". I don't know about that either... here is a thread.
http://forum.xda-developers.com/showthread.php?t=1359395
Well just as an update, I tried the overvolting and clearing the battery stats but still got the reboots. I installed one of the Stock Sense ROMs and it's been running great with no reboots. Apparently my phone just doesn't like non-Sense ROMs for some reason. Oh well. At least I have a working phone. Pretty amazing how fast the stock rom runs!
Well, I guess it's good to hear the hardware is ok.
You still could try out the CM10s (or other JB roms) by starting off without installing your apps (if you can live without them). App compatibility might be your problem. Let it run for a while with no additional apps added. Then, add them back slowly (one or two a day or every couple of days) from the market only. If the reboots start up later on... you will probably recognize the one that is the source of trouble.
Of course you still have plenty of options in the gingerbread family to choose from. If you've never tried out some GB AOSP/CM roms, that would be worth a try. You've got stock roms, stock roms with sense removed, and the whole variety of AOSP/CM7 (official and unofficial) to choose from. Launchers...themes... mods... etc... all kinds of ways to change from whatever you start with. The only GB roms that I ever had problems with were the official "stable" CM7.0 and CM7.1 ROMs. I've been running one unofficial CM7 build (about 99.99% of the time...except to test drive newer stuff) for almost a year. Its been the best thing that's ever happened to my phone.

Categories

Resources