3459 replies to this topic

[ras0787]

Having huge issues with the 4-17 build as well

 

Boooo. Clean install or dirty flash?

[PillClinton]

Not yet...have you?

Its not available yet...well I haven't seen it yet

It's available:

Please Login or Register to see this Hidden Content

 

I have downloaded but haven't yet installed.

[PillClinton]

Boooo. Clean install or dirty flash?

 

You beat me to the punch, I was just about to ask the same question.

[sporkd2]

Seconding big issues with 4.17, going back to 15

[dtomlin]

Just checked the change log. They are reverting what broke the 4/16 build in the next nightly(4/18). Didn't fix in time to make 4/17.

Sent from my XT912 using Tapatalk 2

[minabeshara]

Updated to 4/17, phone has restarted on its own 3 times in the past hour. Back to 4/15 i suppose.

[thrasher194]

Running 4/17... Wiped everythung clean even my sd-ext and flashed gapps 20121212...


All is good now.

[thrasher194]

Well. Everything was fine til just random reboot like three times .

[The Persuader]

It's available:

Please Login or Register to see this Hidden Content

 

I have downloaded but haven't yet installed.

PC...

 

Believe it or Not CM 10.1--Nightly # 16 Blew 2 hours ago...Just as I mentioned having to do with the Lock Screen Interferring with my Sycing and Locking up/Rebooting my phone...

 

Getting ready to redo my Slot for Restore my Nandroid...

 

Its Bubba

[theunbound1]

If i'm lucky the rom will boot...then if i let the screen turn off...it never comes back on.  back to stock till fixed.  Must run the Kexec kernel because moto broke audio with the OTA.  broke audio = dsp manager no work-o....n7 player's built in eq worked well with the leak, but is a horrible fail with the newest ota.  basically music sucks with moto kernel. 

[iaminflames]

Yea 4/16 and 4/17 were both borked. Dhacker and Hashcode evidently made a kernel change that screwed it all to hell 4/18 should be fixed.

Sent from my Motorola RAZR MAXX using Tapatalk 2

[robocuff]

Kexec...
What does this mean with the build?

Its Bubba
~Stubborn In Your Bones~
*FlyingJelly*

 

 

 

Kexec is an exploit.  Basically, in really simple terms, the stock kernel you're using gets hijacked (so to speak) during the boot process and a custom kernel is loaded on top of the stock.  The rom runs completely off this custom kernel.   It's pretty much the same as if you had an unlocked bootloader and flashed a custom kernel.  Only thing is, when the phone is rebooted your stock kernel is still there and available if you should decide to flash one of the non kexec roms.   Rebooting wipes the kexec kernel from memory and it's gone until you boot back to the kexec rom.  

 

Perhaps you've seen where people ask which kernel they need for this and the answer is "it doesn't matter".  The reason it doesn't matter is because the stock kernel isn't used.  If we could get Moto source code it would be as good as an unlocked bootloader.   Just need that source code.

 

[lutheranpriest]

Is the most current ***STABLE*** build the 4/15 version?

[caniphilyouup]

Is the most current ***STABLE*** build the 4/15 version?

Yes

Sent from my XT912 using Tapatalk 2

[violaian]

I was able to fix the problem with the screen not turning on by changing the governor. However, I am still experiencing a huge amount of random reboots on 4/17 nightly. Funny thing, though; it doesn't happen when phone is charging.

[PillClinton]

I was able to fix the problem with the screen not turning on by changing the governor. However, I am still experiencing a huge amount of random reboots on 4/17 nightly. Funny thing, though; it doesn't happen when phone is charging.

 

What governor were you using?  I was using hotplug with the noop scheduler at the time I was having these issues and without the extra kernel modules available, that's typically what I've been using with CM 10.1.

[tad1073]

Updated to 4/17, phone has restarted on its own 3 times in the past hour. Back to 4/15 i suppose.

Same issue here but with both 16 and 17.

 

I'm also have an issue with touch screen not being sensitive enough on 14 and 15.

[violaian]

What governor were you using?  I was using hotplug with the noop scheduler at the time I was having these issues and without the extra kernel modules available, that's typically what I've been using with CM 10.1.

I switched from hotplug to interactive. I also noticed that the minimum CPU frequency button is blacked out. I thought that if i could raise it it might help.

[thrasher194]

Is the most current ***STABLE*** build the 4/15 version?

 

 

Yes!

[violaian]

Yea 4/16 and 4/17 were both borked. Dhacker and Hashcode evidently made a kernel change that screwed it all to hell 4/18 should be fixed.

Sent from my Motorola RAZR MAXX using Tapatalk 2

I hope so cuz I love this ROM, and the previous updates have been so smooth.