Database Info

Can't overclock my Nexus S

Hey all,
I've tried on multiple occasions now to overclock my phone, using both the Trinity & Netarchy (1.1) kernel, everytime I have done so however it will put me into a bootloop, sometimes not getting past the nexus boot animation or lock screen, I'm sure that I'm doing everything right
1. Wipe data/cache
2. Flash ROM (I've tried Stock, Bionic, CM & Modaco, which I use currently.)
3. Boot
4. Flash kernel
5. Boot
I've no idea what's going on, I've just about given up, perhaps I've been handed a crappy piece of silicon, should have returned it before it was too late
Any help appreciated anyways, peacee.

Instead of flashing the ROM and then immediately applying the kernel, let the phone completely reboot. Then go back into recovery and flash the new kernel. Should work.

I've tried this already dude, probably should of mentioned it in my steps cheers anyhows

risegeek said:
I've tried this already dude, probably should of mentioned it in my steps cheers anyhows
Click to expand...
Click to collapse
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?

kenvan19 said:
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?
Click to expand...
Click to collapse
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms
I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock )

risegeek said:
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms
I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock )
Click to expand...
Click to collapse
Have you tried Netarchy 1.2 yet? I've had a lot of issues with CM7, including kernels. Sometimes I would have to just flash the kernel 3 times and then it would work. Now I'm using MoDaCo and it is infinitely more stable. I've noticed the trinity kernels tend to be a little more volatile and hit or miss than the Netarchy one seems to be. If it is really of grave concern to you, if you live in an area where a return would be easily possible and if you are within your return period, return it and try a different slice of silicon

I've actually had this phone since release date, sadly I am out of the return period, I don't really mind all that much, this phone has been amazing coming from a constantly slow and crashing iPhone 3G.
I've just downloaded the new kernel from Netarchy, it seems to address stability issues regarding voltage, which I think it might be. I'll flash it and update this post in a second.
EDIT: Hasn't helped seems to be looping at the Google screen now.

Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.

What the heck? I keep hitting edit but it keeps quoting =( please delete.

sanketrino said:
Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.
Click to expand...
Click to collapse
Have you tried Netarchy's kernel? A link to his thread is in my sig and it works great for me. It will boot you to 1GHz then using SetCPU (which can be attained for free on XDA, legally, just search for it. The Dev posted it) you can up the clock speed. You should take note however that the Nexus S is damned fast stock. I typically run my phone at 1.2GHz unless I want to show off to my friends and then I bump it up hehe
EDIT: Thank you also for not posting a new thread about this Its nice to see people using the search function!

Blah please delete.

I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.

sanketrino said:
I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.
Click to expand...
Click to collapse
Odd...for my own testing purposes I've been running at 1.4GHz (testing battery life vs other clock speeds) since yesterday and haven't had a single crash. What ROM are you using?

I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
Sent from my Nexus S using XDA App

sanketrino said:
I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Hmm, I used his 1.1v kernel on MoDaCo but never the new kernel so I can't speak to its stability.

Some phones are able to run up to 1.4-1.5 without issues whereas some aren't due to hardware limitations (different batch,build quality etc).
Most however, from what i read in the forums, are able to clock up to 1.3 with either kernels (CFS or BFS, versions types etc) without facing the issue of random rebootings.
Personally, i'm only able to clock up to 1.3. I'll get random reboots if i run smartbench with a 1.4. Quadrant is fine for me at 1.4 though. Was able to get ~3500-3600 scores but in terms of real life situations, i can't tell the difference between a 1.3 to 1.4.

Hey guys,
seems my thread is still alive I flashed the newest version of netarchy the other day, I can manage 1.2-1.3 quite happily atm - I have to manually use SetCPU after each boot though, if I set on boot it will loop
ah well.

[Q] No audio from video recordings...maybe ROM related? [SOLVED]

Update-Solutions added
This thread kinda rambles, and covers a couple different issues.
I'll try to summarize the solutions to each to time and eliminate extra reading for those who might end up here later.
Issue #1: My Mesmerize was not recording sound with videos
Solution: Go into Voodoo Sound Control app (download from market if you don't have it) and under [recording profile], select "Original". Solved!
Issue #2: I was having various minor issues that sounded as thought they might be fixed by flashing a new kernel.
scarmon25 suggested that I try out OTB-Reloaded. He was right, this is a great kernel! It allows overclocking and undervolting at the same time. I'm hoping this will give me both better performance and greater battery life.
Solution: Backup everything (Nandroid and TiBackup suggested), Flash the new kernel from recovery (you can use ROM manager to boot into Clockwork Mod Recovery) and reboot.
I'm not about to get into a discussion of backups, recovery, flashing, which kernel you need, etc... This is just a plug/endorsement for the OTB-reloaded kernel, period.
Issue #3: At some point while updating to 2.2 Froyo and flashing new kernels, ROMs, etc... my home screen started rotating along with my apps. I could turn rotation on/off from the notification tray, but that disabled it for apps also.
Solution: It was pointed out by add144 that it's the home screen launcher that controls home screen rotation.
I'm running LauncherPro, be he mentioned that most other launchers (ADW, GO Launcher, etc...) also have the ability to allow or lock home screen rotation.
In my case (LauncherPro), here's the process for locking your homescreen rotation while still allowing auto-rotation in other apps:
1) From home screen, go to Menu (button) -> Preferences
2) Select Behavior Settings
3) Uncheck "Enable Auto-rotation"
4) Done!
I hope this summary saves someone some time and fruitless searching.
Cheers!
-Mike
----Original message follows---
Hi all,
I apologize for this question being a bit light on useful details, but my memory isn't so great.
I have a Mez, running 2.2 Froyo (updated from USCC), a custom ROM (I think), and a custom kernel (not sure which one).
I know that sounds insane, but there was a time a while back when I was flashing different things trying to find something that worked to my liking, and honestly just can't remember what combination I settled on.
It doesn't help that I'm still fuzzy on the whole ROM vs Kernel thing.
Anyway, here's the issue...
The videos I record on the phone have no sound.
You can hear a little background hiss, but no actual sound from the mic.
I can't remember if it worked before I updated to 2.2, but I suspect it did or I think I'd have noticed it before.
I guess I could flash everything back to stock and see if that fixes it, but I'd REALLY rather not do that, since it would take me so long to get it back sorted.
Is there a way to figure out exactly what I currently have installed on the phone?
Also, can anyone think of things I can do to troubleshoot the no audio issue?
Thanks in advance,
-Mike

This sounds like a issue I had on one of the earlier voodoo kernels. The fix was to download the voodoo control appear from the market and set recording preset to normal. This was fixed in the later releases of voodoo. Do you know which kernel your are on. That would help us narrow it down for you.
Edit. If you download the cpu spy app from the market you can pull your info up and see which kernel your on. It won't say exactly which one but should have the authors name in it so we can know which one your on to an extent.
Sent from my SCH-I500 using XDA Premium App

Thanks for the quick reply scarmon.
I checked my voodoo sound options (already had the app) and I don't have a 'normal' recording preset.
My choices are:
Original
Balanced (new default) - with DRC
High Sensitivity - with DRC
Loud Environment - with DRC
I assume this means I have one of the newer versions of voodoo sound?
I'll get that cpu spy app and see what it says about my kernel.
Thanks!
-Mike

Elmojo said:
Thanks for the quick reply scarmon.
I checked my voodoo sound options (already had the app) and I don't have a 'normal' recording preset.
My choices are:
Original
Balanced (new default) - with DRC
High Sensitivity - with DRC
Loud Environment - with DRC
I assume this means I have one of the newer versions of voodoo sound?
I'll get that cpu spy app and see what it says about my kernel.
Thanks!
-Mike
Click to expand...
Click to collapse
Use original

Switched to Original, audio works now, thanks!
I wonder why the "new" profiles don't work?
Is it a limitation of this phone or a problem with voodoo?

The newer voodoo kernels have that issue fixed. I believe it was just a issue with the first few ec10 voodoo kernels. May wanna try one of the new OTB or imnuts kernels. The recording works on those as I have tried both.
Sent from my SCH-I500 using XDA Premium App

scarmon25 said:
The newer voodoo kernels have that issue fixed. I believe it was just a issue with the first few ec10 voodoo kernels. May wanna try one of the new OTB or imnuts kernels. The recording works on those as I have tried both.
Click to expand...
Click to collapse
Good to know, thanks.
Is updating to one of those kernels you mentioned a simple 'boot to recovery and flash zip from SD card' or something more?
Here's a screenshot of my current kernel info from cpu spy...
Does that help any? I don't recognize that author.
EDIT: That OTB kernel sounds really interesting.
Please refer to my above question about the simplicity or complexity of flashing that kernel over the one I have now.

Yeah u flash in CWM. If your on voodoo and 2.2 then you shouldn't have any issues. If u go with OTB make sure to get the voltage control app. So u can adjust it. Just go easy on the over clock and undervolting till u see how your phone reacts. If u go with OTB let me know and I will post my settings. Been running them for a while and they seem pretty stable.
Edit. Switched to PC to correct my spelling.
Sent from my SCH-I500 using XDA Premium App

The above is what I'd try first. If you still find that you're having issues even with a new kernel, I'd consider flashing a new ROM as well.

scarmon25 said:
If u go with OTB let me know and I will post my settings. Been running them for a while and they seem pretty stable.
Click to expand...
Click to collapse
I'll be flashing OTB shortly and would love to get your settings.
Thanks!
-Mike

K, This is what I have been running and it seems pretty stable for me. Keep in mind each phone is different and yours may not respond as well, or it may do even better then mine. I would suggest using the apply for now option in voltage control for a few days and once you know there good, you can apply at boot. Also nemisses included and great feature in CWM that allows you to remove boot settings in the event that you set something at boot and it doesn't work. You will get this once you flash the OTB v1.3 kernel. This will update CWM and the feature is under the advanced section of CWM if you need it. Here's the settings I have been using.
For the Scheduler I use BFQ
I set the Max Clock to 1200mhz
I have the following step and voltage drops enabled
200 mhz -100
400 mhz -100
600 mhz -75
800 mhz -75
1000 mhz -75
1200 mhz -50
With theses settings I am getting about a day of moderate use from my battery and great performance. You may play around with it and may get better results. Hope this helps.

OTB 1.3?
The thread I was watching only goes to v1.2 for OTB-reloaded.
What am I missing?
I also noticed that is was technically a Fascinate kernel, is that a problem?

It works on the mesmerize too. That's what I'm on. There should be a link in the OP that's has v 1.3. Its he second link at the bottom of the OP
Sent from my SCH-I500 using XDA Premium App

Okay, I think I see the issue.
I was looking at this thread, whereas I think you're referring to this thread, right?
What's the difference between those 2 kernels, other than the OTB version?

one is Touch wiz and one is AOSP. If you are on stock Froyo you need touchwiz. AOSP will not work on stock ROM. You posted in the right one for OTB. This is the one you need for Stock Froyo
http://forum.xda-developers.com/showthread.php?t=1011626
The 1.3 link is towards the bottom of the first post.

scarmon25 said:
one is Touch wiz and one is AOSP. If you are on stock Froyo you need touchwiz. AOSP will not work on stock ROM. You posted in the right one for OTB. This is the one you need for Stock Froyo
http://forum.xda-developers.com/showthread.php?t=1011626
The 1.3 link is towards the bottom of the first post.
Click to expand...
Click to collapse
I don't think I'm on stock froyo, though.
As far as I can tell, I'm running SuperFrankenClean 0.292.
I base this on the files I found on my SD card while I was moving some stuff around just now.
In any case, it sounds like the touchwiz kernel is the one I need.
I'm downloading it now and will flash in a few.
Let me know if it looks like I'm about to frag something and I'll wait.
-Mike
OOPS! That should be SuperFrankenClean 2.9.2 ROM and EC10_ulv_voodoo kernel....I think.
Does that change anything?

Wait. Let me pull that ROM and I can tell you.
K this is showing to be used with touchwiz based kernels so u should be good to go.
Sent from my SCH-I500 using XDA Premium App

Yeah your good man flash away. As long as its a touch wizard kernel you good to go. If u used the one I linked u too then u will be fine.
Sent from my SCH-I500 using XDA Premium App

Awesome, flashing now....
If you hear a scream, it means it didn't work. lol
-Mike

Well I'm here all night so if it does go wrong we will fix it. But honestly you shouldn't have any issues
Sent from my SCH-I500 using XDA Premium App

I still have random reboots....

Will these ever go away on my nexus s? I have gotten them in everything from stock 2.3, cyanogenmod 7, stock ICS, oxygen, and every single ICS rom I have used. I understand some software bugs take a while to find but I have had this bug for over a year, will it every get a fixed? (Or is this not a software bug but an actual issue with my phone?)

Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA

ThisNight said:
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.

tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
Well, you're running an overclock... Try running without.
CM7 has a sleep of death/reboot bug, so try another ROM not based on CM7 too.
Highly recommend Oxygen 2.3.2 coupled with Franco 08.12.2011 GB kernel.

If you're interested in ICS ROM, give AOKP ROM and Matr1x kernel a try. It's rock stable for me. I just rebooted to flash the new build, but before that it lasted for couple weeks for me without rebooting. Link to AOKP ROM is in my sig.

tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.

I'd highly recommend the Androxide ROM along with Air Kernel. I've been running this combo overclocked to 1200 without any voltage setting changes for a decent amount of time.
random reboot frequency - about once a week ..

AeroEchelon said:
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
Click to expand...
Click to collapse
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.

zgomot said:
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
Click to expand...
Click to collapse
Thirding it.
If you are having problems then roll everything back to stock... its not good enough to say you have run every rom , yet fail to mention you OC. What other tweaks do you run? Deep Idle?
I'd bet if you flash CM9 with no tweaking it, it will be fine.

bringonblink said:
I'd bet if you flash CM9 with no tweaking it, it will be fine.
Click to expand...
Click to collapse
Or just about *ANY* rom for that matter. First ensure you can run it stable without OC, UV, didle, mods, themes etc then, by all means, go ahead and tweak to your hearts's content.

Overclocking to 1200mhz CPU only does NOT require extra voltage across the board, but possibly a boost at the 1200mhz voltage. Each frequency runs at a different, changeable voltage which has nothing to do with all the others. LiveOC, however, raises the frequency of each step and as such generally requires a boost in voltage across the board or thereabouts.
As for the problem the OP is having, who knows. Could you describe any specific things you've done, though? Full wipes (detail what you wipe), titanium backup restores, etc.
First thing i would be trying now is to do a full wipe (factory/data reset, format /boot, format /system), flashing either stock 2.3.6 or 4.0.3 and installing only necesseties and try for a week or so. If there are still reboot problems, describe them and hopefully i can give you some useful things to try. If you had this problem before the 1 year mark you could have probably gotten the phone fixed/replaced under warranty, though. If it is now over a year i'm afraid that's too late though.

Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..

Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.

Have you tried other ROM besides CM7? I remember when I flashed CM7 for the first time. My phone never liked it, it was all bugs for me. I even noticed that OC'ing would generate problems on any ROM.
I just ran away from CM7 and OC'ing.
Try Oxygen ROM (or stock as they stated before) with all set up to defaults and test for a while.

hutzdani said:
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Click to expand...
Click to collapse
I admit I had reboots with cm7' but with latest cm9 nightly I have none. Stock kernel stock oc and stock voltage with deep idle off
Sent from my Nexus S using Tapatalk 2 Beta-2

bmszabo said:
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Click to expand...
Click to collapse
The update was pulled for many reasons. Try stock GB or Oxygen ROM and enjoy life without freeze, sleep of death or reboot...

Synergy or Beans?

I am currently running beans custom stock ROM v5 and I haven't ran synergy yet but I was wondering which ROM was better. Before I get Beans v6 I'd like to have some input on which ROM was better based on battery life/other things.
Sent from my SCH-I535 using Tapatalk 2

Well I started with bean R2 when I first rooted. Then tried synergy which my buddy had phenomenal battery life with. I however didn't even though I was running less and theoretically should have had better. I gave it a week but didn't see any improvement. Went back to bean but tried his updated 3.1. Was better than synergy In my opinion as far as battery life goes but had some quarks with it. Next day he came out with V5 so I flashed that. Had worse battery life than 3.1 but better than synergy. Meanwhile my buddy was still getting better battery life with his synergy. I decided to go back to the original R2 I had at first. It is the best performing For ME. I would try each and see what you like better. I was on my the boat all day today (again, currently running R2) and got 84% 12 hours. Keep in mind most of that was minimal use of texts and web browsing. Mist was screen off with with setcpu screen off profile (348). Still was nice to have a full day with it turned on even if screen was off and then still have a full battery to use when I got off the river.
For me...bean R2 for the win. I don't mind wiping and trying a promising ROM but I also like having a solid ROM that gets me what I want/need without having to worry about what the next new thing is.
Sent from my SCH-I535 using xda app-developers app

I'm also using beans r6. Everything seems a lot smoother...but my phone does run hot. He has the default CPU set at 1.9 gighz. Sometimes it doesn't clock down with the app. I'm going to try synergy when they release the new version...but its hard not to like beans.
Sent from my SCH-I535 using xda app-developers app

I used both, beans r5 kept rebooting on me but the battery life seemed better than stock. Then i switched to synergy 1.3 and it is an awesome rom. 4x5 homescreen alone is worth the upgrade from bean, but the battery is just a little less than bean r5. I have no tried r6 but i dont think i will because i just flashed CM10 an hour ago and couldint be happier. I forgot how much i miss stock android JB (used to have galaxy nexus). its a lot smoother and better to use and look at obviously. Only thing i dislike about the rom is the hardware buttons back and menu dont turn off they stay on if the screen is on, but its not that bad. I saw Flash CM10 you will be happy!

CM10 is a half working rom at this point, don't know how anybody uses it as a reliable daily driver, as for clocking on Bean's rom, you can control it yourself, just run the cpu bin from a terminal window, or use rom tools or setcpu

I use beans but I use beans 3.1 before the stupid overclocked kernel and before kexec kernel /recovery
Sent from my SCH-I535 using Tapatalk 2

p-slim said:
I use beans but I use beans 3.1 before the stupid overclocked kernel and before kexec kernel /recovery
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
the overclock issue is fixed...beans b6 rocks! actually i never had that issue anyways.

I think I'm going to stick with beans r6 I'm loving the jelly bean theme. If your complaining about battery on beans because of the kernel just under clock it or use power saving, your phone will not run hot and you will get better battery life. If you want a higher clock speed use 1512 or 1674 MHz, you may run a little hotter and your battery may drop a little faster than if you were on power saving though.
Sent from my SCH-I535 using Tapatalk 2

bobcaruso said:
CM10 is a half working rom at this point, don't know how anybody uses it as a reliable daily driver, as for clocking on Bean's rom, you can control it yourself, just run the cpu bin from a terminal window, or use rom tools or setcpu
Click to expand...
Click to collapse
I have to disagree strongly with the assertion that CM10 is a "half working rom." If you're not one of the people experiencing data connectivity issues, the current bugs are: bluetooth audio, MMS, camera autofocus with stock camera app (for some), and that native wifi tethering only works unsecured (usb & bluetooth tethering work fine.)
I used it as my daily driver from 7/21 on, and the only thing I personally missed was secure wifi tethering. If the above bugs don't affect things that you use, CM10 is much snappier overall than any of the 4.0 based roms.
I actually decided to try Beans again just to see if I missed any touchwiz features (smart stay, direct dial, etc.)

synergy
I'm currently running synergy v1.3, but i liked v1.2 a lot better. Mainly because the grid size was changed so now widgets look a little weird on my phone =/ but other than that i haven't had a problem. Battery life is insanely good. I used bean's rom when it first came out, got me 50gb of dropbox for free which was awesome. The stock apps weren't on the first build though, that's why i switched over to synergy. I think Bean's rom has them back on though. I suggest trying them both and making backups, they're both very good

Yea Im running Beans v6 just upgraded from either 3 or 2, and yea its wicked fast. I guess with Synergy there are more themes but they should work on Beans too. Anyway it is definitely worth a try just backup beforehand :good:

kabro91 said:
Yea Im running Beans v6 just upgraded from either 3 or 2, and yea its wicked fast. I guess with Synergy there are more themes but they should work on Beans too. Anyway it is definitely worth a try just backup beforehand :good:
Click to expand...
Click to collapse
yeah synergy 1.4 just came out late last night, and it is nice with the google now baked in. try it out

They are both good. It's a subjective preference and you won't know which you prefer until you try both.

Saauron said:
I have to disagree strongly with the assertion that CM10 is a "half working rom." If you're not one of the people experiencing data connectivity issues, the current bugs are: bluetooth audio, MMS, camera autofocus with stock camera app (for some), and that native wifi tethering only works unsecured (usb & bluetooth tethering work fine.)
Click to expand...
Click to collapse
LOL, all those bugs certainly sound like it is half working (or not working depending on how you look at it).
I tried it for a few days & will definitely agree that's it's way to buggy to be a daily driver at this point.
IMHO, to be a daily driver all the native functions the system came with have to work 100%

Yeah synergy 1.4 is insanely snappy and quick. To a noticeable degree. I love v6 of beans though, but synergy just goes without having to be pushed
But I still use both just to get my flash fix, lol. Beans has more of what I'm looking for (aosp theme) with stock feel.
Sent from my Galaxy S3 using Tapatalk 2

Just the thread I was looking for! I am currently getting tired of the random bugs with CM10, but I'm wondering if I can just flash Synergy or Beans the way I have been flashing CM10 builds using the Kexec recovery. It looks like Beans does this method, but I just want to confirm before I brick my phone

Synergy
I'm using Synergy atm and I love it so far..... Battery life is amazing....

FreeRefreshments said:
I am currently running beans custom stock ROM v5 and I haven't ran synergy yet but I was wondering which ROM was better. Before I get Beans v6 I'd like to have some input on which ROM was better based on battery life/other things.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I think both are great RomS. I personally have synergy installed right now because it was just released. There are some things I like about synergy and some things I like about beans. With beans you can flash different kernels without any problems but when I try to flash different kernels on the synergy1.4 I keep getting bootloop. Beans and synergy both seem to be pretty good on batter but I also use CPU sleeper which might also help.
Sent from my SCH-I535 using xda app-developers app

adriang1984 said:
I think both are great RomS. I personally have synergy installed right now because it was just released. There are some things I like about synergy and some things I like about beans. With beans you can flash different kernels without any problems but when I try to flash different kernels on the synergy1.4 I keep getting bootloop. Beans and synergy both seem to be pretty good on batter but I also use CPU sleeper which might also help.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Good call, I'm gonna start using CPU Sleeper now

adriang1984 said:
I think both are great RomS. I personally have synergy installed right now because it was just released. There are some things I like about synergy and some things I like about beans. With beans you can flash different kernels without any problems but when I try to flash different kernels on the synergy1.4 I keep getting bootloop. Beans and synergy both seem to be pretty good on batter but I also use CPU sleeper which might also help.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yeah. 1.4 isn't compatible with custom kernels, I'm waiting for a possible fix until I flash 1.4 just because Imoseyons lean kernel is amazing on this phone. I've gotten a day and a half on a single charge with 4 he's and 29 minutes in screen time..plus I also use CPU sleeper with the lean kernel you can also have your phone speed charge..and I mean really fast compared to stock.
Current~Samsung Galaxy S3 SynergyRom 1.3 & Imo's Lean Kernel v12 Oc'd @ 1.9ghz
~Acer Iconia A500 Stock
Past~Droid X Gummy ICS 1.2

LG g2x eagles blood ICS

Hello
I have installed Eagles blood ICS 4.0.4 but after that I feel performance is very slow and battery discharges fast.
pls can anybody help me to improve performance.?

What was your flashing procedures? Did you do a FULL wipe to include format/system under mounts and storage? Did you flash a kernel with it? Gapps? I use the same ROM and its one of the fastest roms I've used and by far the fastest and smoothest ics for this device
Sent from my LG-P999 using xda premium

Pain-N-Panic said:
What was your flashing procedures? Did you do a FULL wipe to include format/system under mounts and storage? Did you flash a kernel with it? Gapps? I use the same ROM and its one of the fastest roms I've used and by far the fastest and smoothest ics for this device
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I've actually found that out of all the ICS roms, this discharged battery the least.* Lag does happen, but it comes and goes (welcome to G2X hackfested ICS+ roms)
*Pain-N-Panic, does this rom ever go into an extreme deep sleep for you if left unattended? My main problem was that my alarms wouldn't go off at the right time, they'd only activate after pressing the power button to wake the device up.

a--c said:
I've actually found that out of all the ICS roms, this discharged battery the least.* Lag does happen, but it comes and goes (welcome to G2X hackfested ICS+ roms)
*Pain-N-Panic, does this rom ever go into an extreme deep sleep for you if left unattended? My main problem was that my alarms wouldn't go off at the right time, they'd only activate after pressing the power button to wake the device up.
Click to expand...
Click to collapse
Woah, no sir, not at all. That's a serious problem lol. However, I do not use my phone as an alarm so I can't honestly say so. One of the best things about this ICS ROM compared to some of the others is that it comes with a great kernel that can be overclocked and undervolted. I run mine at 1000 max and 216 min and undervolt everything at -50 with SetCPU. With this setting my battery life is on par with stock CM7, which in my opinion has the best battery life of any ROM for this phone. Another little goodie to add to this rom is the Lag free/dalvick fix. It's a build.prop mod that can be executed with script manager. You can find it in the g2x android development forum. However, if you decide to use this mod i recommend adding the scripts to your build.prop manually on your pc or text editor on your phone. I used the build.prop file that came with the mods pre-loaded and it actually slowed down the device a little. When I added them manually, eaglesblood has never ran smoother or been more snappier.

Haha, I wisened up and went back to CM7 and got an alarm clock.
I've seen the build.prop mod, but with CM7, it's not needed
If I do ever need my ICS fix, this would still be my go-to ROM.

Yup, I switch back and forth from cm7 and eagles blood as well. Whenever I need a working video camera is when I flash back to cm7. Wish they could get working video on ics.....damn drivers! Although the lag free fix isn't needed on cm7 it can be used if you wanna try it out. I myself have never tried but plan on doing so whenever I go back to it
Sent from my LG-P999 using xda premium

I just followed procedure mentioned in the eaglesblood thread for this ROM.I did wipe/format and installation through CWM(but dont know is that a full wipe or have to do something more?) .I guess i flashed kernel as it is different from my previous GB.Also I did flash Gapps mentioned in the forum.
then I run script tune.sh mentioned in the thread for lag free runing using sm manager and keeping 'Run in root' option but no luck it's having lag.battery discharges within 8-10hr.How much your battery last for if you keep wifi,bluetooth options on?

ICS
Pain-N-Panic said:
Woah, no sir, not at all. That's a serious problem lol. However, I do not use my phone as an alarm so I can't honestly say so. One of the best things about this ICS ROM compared to some of the others is that it comes with a great kernel that can be overclocked and undervolted. I run mine at 1000 max and 216 min and undervolt everything at -50 with SetCPU. With this setting my battery life is on par with stock CM7, which in my opinion has the best battery life of any ROM for this phone. Another little goodie to add to this rom is the Lag free/dalvick fix. It's a build.prop mod that can be executed with script manager. You can find it in the g2x android development forum. However, if you decide to use this mod i recommend adding the scripts to your build.prop manually on your pc or text editor on your phone. I used the build.prop file that came with the mods pre-loaded and it actually slowed down the device a little. When I added them manually, eaglesblood has never ran smoother or been more snappier.
Click to expand...
Click to collapse
Can you tell me how to and what to put in build.prop manually?

If you're keeping wi-fi AND bluetooth on, continuously, then 8-10 hours of battery life is to be expected. I never use blue tooth and I keep data and/or wifi OFF unless I am using it at the time. Once I finish using the internet for whatever it is that I am doing I shut it off. Instead of giving you a tutorial, I can just post a copy of my build.prop and you can use that instead.

ICS
Pain-N-Panic said:
If you're keeping wi-fi AND bluetooth on, continuously, then 8-10 hours of battery life is to be expected. I never use blue tooth and I keep data and/or wifi OFF unless I am using it at the time. Once I finish using the internet for whatever it is that I am doing I shut it off. Instead of giving you a tutorial, I can just post a copy of my build.prop and you can use that instead.
Click to expand...
Click to collapse
Thank you very much,your help is appreciable.

ICS
Pain-N-Panic said:
Woah, no sir, not at all. That's a serious problem lol. However, I do not use my phone as an alarm so I can't honestly say so. One of the best things about this ICS ROM compared to some of the others is that it comes with a great kernel that can be overclocked and undervolted. I run mine at 1000 max and 216 min and undervolt everything at -50 with SetCPU. With this setting my battery life is on par with stock CM7, which in my opinion has the best battery life of any ROM for this phone. Another little goodie to add to this rom is the Lag free/dalvick fix. It's a build.prop mod that can be executed with script manager. You can find it in the g2x android development forum. However, if you decide to use this mod i recommend adding the scripts to your build.prop manually on your pc or text editor on your phone. I used the build.prop file that came with the mods pre-loaded and it actually slowed down the device a little. When I added them manually, eaglesblood has never ran smoother or been more snappier.
Click to expand...
Click to collapse
I'm also agree to a--c and have observed same deep sleep issue don't know because of what but sometimes if we keep it unattended it goes on deep sleep. And in that case I have to remove battery,replace and restart.

dman31 said:
I'm also agree to a--c and have observed same deep sleep issue don't know because of what but sometimes if we keep it unattended it goes on deep sleep. And in that case I have to remove battery,replace and restart.
Click to expand...
Click to collapse
Are you running stock or custom kernel? Do you have a CPU app? If so, what is your cpu clocked at (both min at max)?
Here's my build.prop file:

Pain-N-Panic said:
Are you running stock or custom kernel? Do you have a CPU app? If so, what is your cpu clocked at (both min at max)?
Here's my build.prop file:
Click to expand...
Click to collapse
Thank you pain-n-panic.I just have to copy this build prop file and paste it in the folder where the previous build prop is,right? or their is another technique for that to do?
and about cpu it's clocked at 216Mhz-1.41 Ghz..kernel is 3.034-egb_p999-5 so my guess is it's came with EGB rom.

Call Audio
Does the call audio work in this ROM?

dman31 said:
Thank you pain-n-panic.I just have to copy this build prop file and paste it in the folder where the previous build prop is,right? or their is another technique for that to do?
and about cpu it's clocked at 216Mhz-1.41 Ghz..kernel is 3.034-egb_p999-5 so my guess is it's came with EGB rom.
Click to expand...
Click to collapse
Yes, I like to use Root Explorer to navigate around my system files and folders. All you have to do is drop the build.prop into your system folder and hit yes when it asks you to replace the existing build.prop file. MAKE SURE that you read the directions in the thread and that you set the permissions correctly on the modded build.prop file. I do not recall what they had me set the permissions to but that is very important for you to set the permissions correctly on the modded build.prop before dropping into your system folder.
I figured that was the case....your CPU is maxed out at 1408. This is why your battery life is weak. Drop is down! 1015 mhz max WITH undervolting I still get smooth performance and great battery life. There is an awesome tutorial I read posted somewhere in the g2x forum about how to properly undervolt your device. Its a pain in the butt when you're in the process but so worth it in the end. Try searching it and giving it a try if battery life is a main concern for you.
YES call audio works on this ROM!

Pain-N-Panic said:
YES call audio works on this ROM!
Click to expand...
Click to collapse
In both 4.0.3 and 4.0.4? Because I need a daily ICS ROM where I can use calls with audio.

ldnjsphtnz said:
In both 4.0.3 and 4.0.4? Because I need a daily ICS ROM where I can use calls with audio.
Click to expand...
Click to collapse
Yup. I like 4.0.4 much better than 4.0.3. I used 4.0.3 for about 20 minutes and flashed back to 4.0.4, never even made a phone call so I can't honestly say how calling works on that ROM. I use 4.0.4 as my daily driver and calling works just fine.

Pain-N-Panic said:
Yup. I like 4.0.4 much better than 4.0.3. I used 4.0.3 for about 20 minutes and flashed back to 4.0.4, never even made a phone call so I can't honestly say how calling works on that ROM. I use 4.0.4 as my daily driver and calling works just fine.
Click to expand...
Click to collapse
Hmmm, is there any chance that the video recording can be fixed?

Nope. Video recording/playback is broken on every ics/hackfest for our device. We don't have the proper drivers
Sent from my LG-P999 using xda premium