[blue duck butter]

No, not here at least. Sounds like a kernel problem. Try flashing the new R133 through the franco updater, use the ondemand governor, and don't check hot plug. If you checke hot plug, it might conflict with it automically hot plugging.

You could ALSO raise your voltages 25-30 for each increment.

Thanks for the reply. I am VERY new to this. I believe i'm running the Trinity kernel at the moment. How do I go about flashing the R133 through the franco updater? And what is the ondemand governor and hot plug?

[dmmarck]

Thanks for the reply. I am VERY new to this. I believe i'm running the Trinity kernel at the moment. How do I go about flashing the R133 through the franco updater? And what is the ondemand governor and hot plug?

Do you have the franco updater app? It's $1.93 in the market (or was), and it's highly recommended--you can flash his kernel or imo's lean kernel.

If you're on M1, I believe its default kernel is franco's R121 release.

So buy the updater, and go to flash the current nightly. You can download it and do it yourself or autoflash.

Ondemand = his default/"best" governor, essentially it bumps power when it's needed, but when it's not needed it stays low

Hot plug = we have 2 cores in the GN. When the screen is off ("screen_off"), CPU1 turns off. When the screen is on ("screen_on"), CPU1 kicks back. It may have negligible battery effects, but it's sorta neat.

It could also be that trinity just doesn't like your phone. That happens and it's exactly why the franco app is nice, b/c you have 4 kernel options--franco "stable" and nightly releases and imo/lean kernel "stable" and nightly releases.

[blue duck butter]

Do you have the franco updater app? It's $1.93 in the market (or was), and it's highly recommended--you can flash his kernel or imo's lean kernel.

If you're on M1, I believe its default kernel is franco's R121 release.

So buy the updater, and go to flash the current nightly. You can download it and do it yourself or autoflash.

Ondemand = his default/"best" governor, essentially it bumps power when it's needed, but when it's not needed it stays low

Hot plug = we have 2 cores in the GN. When the screen is off ("screen_off"), CPU1 turns off. When the screen is on ("screen_on"), CPU1 kicks back. It may have negligible battery effects, but it's sorta neat.

It could also be that trinity just doesn't like your phone. That happens and it's exactly why the franco app is nice, b/c you have 4 kernel options--franco "stable" and nightly releases and imo/lean kernel "stable" and nightly releases.

Thank, will try. It's funny being the guy needing the advice and direction now. I used to give lots of advice in the webOS forums at webOS nation. Glad to be see there is a community outside webOS that is as helpful and passionate as they (we) are. THanks again!

[dmmarck]

Thank, will try. It's funny being the guy needing the advice and direction now. I used to give lots of advice in the webOS forums at webOS nation. Glad to be see there is a community outside webOS that is as helpful and passionate as they (we) are. THanks again!

No problem, that's why we're here .

Let me know if that works out. I really think it's a kernel issue. Don't worry, my phone hated trinity too.

If that doesn't work, I suggest a clean install of Patient Zero M1. Re-download it (doesn't hurt, trust me!), put it on your SDcard if it isn't already, and then flash it again.

[dmmarck]

MORFR is coming...

From DT himself:

Okay Boy and Girls... I have Toggles, APM and CPU Management in Pure AXI0M. Plus, Beats Audio, Sony Bravia, INIT.D, CMPLXTH3ORY Script set, reworked Busy box, Built a solid DSP Manager, and Xcompressed the OS, so the er is optimized and fast as a Cheetah on Meth. That is just AXI0M Base (Official).

I also have a CM9 Module, AOKP Module and a CNA Module that flash and interchange without losing any data, plus they will replace each other so you can switch when ever you want.

I am hoping for tonight, but worst case.... Tomorrow. I am proud as **** about this!!!

[2defmouze]

Everything dmmarck said... with emphasis on bumping the voltages up as that's what is very likely causing your SOD's (screen of death's).

In the kernel app or your ROM control, raise each slot by at least 25-50, hit Apply, test out for a good while to make sure you have no issues, then you're safe to click Set at Boot. If you have issues, bump them up a little more. Make sure you are solid for at least 2 days before checking Set at Boot... and note that without it checked, any time you reboot remember to go back into the controls and hit Apply to the voltages or it will revert to the default ones.

[dmmarck]

Thread updated with a placeholder for MORFR. I changed around some of the information featured, and will do a better/cleaner overhaul tonight/tomorrow.

[dmmarck]

Everything dmmarck said... with emphasis on bumping the voltages up as that's what is very likely causing your SOD's (screen of death's).

In the kernel app or your ROM control, raise each slot by at least 25-50, hit Apply, test out for a good while to make sure you have no issues, then you're safe to click Set at Boot. If you have issues, bump them up a little more. Make sure you are solid for at least 2 days before checking Set at Boot... and note that without it checked, any time you reboot remember to go back into the controls and hit Apply to the voltages or it will revert to the default ones.

Also, re: set at boot, when you flash a NEW kernel, make sure to uncheck that before you flash. It caused havoc when franco lowered overclocking mhz a month or so ago, and it's good practice IMO.

[2defmouze]

Also, re: set at boot, when you flash a NEW kernel, make sure to uncheck that before you flash. It caused havoc when franco lowered overclocking mhz a month or so ago, and it's good practice IMO.

Absolutely... glad you remembered to mention that, lol. Any time you flash a new or updated kernel or ROM, even if you are doing a full wipe for a ROM, its recommended you remember to uncheck any Set at Boot options you have set.

[dmmarck]

No problem .

How's the OP redo look? Still some work to do...had to change the title b/c I ran out of space lol

[blue duck butter]

So Is having the Axi0m ROM, ROM Mananger app and franco kernel updater app the basic stuff I need to overclock, underclock and otherwise go wild on my GN?

[dmmarck]

More or less, yes .

The rom may have some controls over overlocking, etc., but that's usually through the kernel. Franco makes kernels. Roms will come with different kernels; some their own make, some like imoseyens (the lean kernel), franco, trinity, etc. What's great about the updater app is that you have so many controls over the kernel in that app. It's really my one-shot stop for overclocking, volting, etc.

[blue duck butter]

Incredible. Kudos to all developers. Who do I paypal donate to? Are there certain factions that are doing this? In webOS, it was easy to donate to webOS Internals, headed by Rod Whitby. Is there anything like that here? Is it too fragmented to sensibly donate? If need be, I will alpha test various projects. PM me.

[dmmarck]

Incredible. Kudos to all developers. Who do I paypal donate to? Are there certain factions that are doing this? In webOS, it was easy to donate to webOS Internals, headed by Rod Whitby. Is there anything like that here? Is it too fragmented to sensibly donate? If need be, I will alpha test various projects. PM me.

You could (and should ) always donate to DroidTh3ory. Check out the droidHIVE link for PatientZero and click donate.

The franco updater is paid, but you could also find him on RootzWiki or XDA and donate through there as well.

I'd also LOVE to be a tester lol

[2defmouze]

No problem .

How's the OP redo look? Still some work to do...had to change the title b/c I ran out of space lol

I noticed the title first and was like "haha yeah that's about what you have to call it at this point..."

OP is nicely organized... I would probably say you can drop the crossbreed section because that's dead... And really once MORFR is complete you should be able to consolidate everything into once section just under MORFR... as that will be the base (well, Driven will be).. then the modules could each get a section. I imagine that's how its going to work, as th3ory did similar projects for the bionic called SHIFT3R and then KIN3TX and they both followed that same kind of organization. MORFR is going to be a whole different kind of beast though... since each module is going to basically make you a different ROM.. That's insane. I can't wait to see this.

I got off track... Nice job DM!

[2defmouze]

Thinking about it, might even be a fair idea to start a new thread, lol. I'm sure Th3ory is going to on the hive for this, its a new project altogether. Your choice tho, obv, doesn't make much difference

Regarding donations.. guys can donate to th3ory directly on droidhive.com.. he certainly deserves it. FWIW, I'd say its probably a nice idea to throw a donation toward the ROM devs making all the swag you use, or are going to use, for the MORFR modules, whether it be Roman and the AOKP team, CM9, CNA, whatever... you can find all their info easy enough in the nexus section on rootzwiki. I've thrown a number of donations th3ory's way since I got my bionic in september, lol... have been meaning to throw some dough toward AOKP for a couple weeks now since we've been enjoying all their swag in Patient Zero / Crossbreed.. keep forgetting lol.

[dmmarck]

I may start a new one or remove Crossbreed (and just simply link to it) and make it PZ + MORFR. That should clean it up nicely into 2 parts, right? I don't want folks to get confused lol

[2defmouze]

I may start a new one or remove Crossbreed (and just simply link to it) and make it PZ + MORFR. That should clean it up nicely into 2 parts, right? I don't want folks to get confused lol

Right, I only say it because, technically, crossbreed is dead and PZ is more or less dead. Going forward its all MORFR. A new thread is a nice clean slate... but hey, you're the boss here

[dmmarck]

Right, I only say it because, technically, crossbreed is dead and PZ is more or less dead. Going forward its all MORFR. A new thread is a nice clean slate... but hey, you're the boss here

Don't worry, a full scale rewrite is happening when I get home ;-)

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk

[dmmarck]

Cleaning up this and a separate thread is coming

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk

[2defmouze]

Guess what theory just gave me to play with.......



Sent from my Galaxy Nexus using Tapatalk 2

[dmmarck]

First, you're a ****.

Second, WTF w/ no caps in the title.

Third, post in the correct thread, noob.

[stacman.nexus]

Guess what theory just gave me to play with.......



Sent from my Galaxy Nexus using Tapatalk 2

I like it, but that Nav Bar needs to change to look sleek like the toggles...

[dmmarck]

I just asked him whether or not we can flash softkeys w/ ZipThemer. Hopefully we can. If so, I want to know which file we configure/update edify with--the base or the package.

Anywho, let's take MORFR discussion to its own thread .

[2defmouze]

I like it, but that Nav Bar needs to change to look sleek like the toggles...

Lol that was just a shot of me downloading it from patient zero...I'm running it now..

Sent from my Galaxy Nexus using Tapatalk 2