Jump to content

Nightly-Kernel-3.4 (Based 100% on Mourta's, updated 02/24/2015)


Guest NothingSerious

Recommended Posts

Guest NothingSerious

Pretty much the only reason I thought of this name is because every kernel build posted here is a testing version. This kernel build will be updated pretty much every time a new commit is added to Mourta's bitbucket, only one version each day though. NOTE: Mourta cannot provide any support for this kernel, therefore do not attempt to report bugs or any issues to him. Since you are also using a SNAPSHOT version, expect bugs and perhaps bootloops. Built with 4.9-SaberMod.

For changelogs, refer to Mourta's bitbucket: https://bitbucket.org/mourta/mourta-kernel-3.4.git

Finally, a big shoutout to Giuseppe and his testing crew who have helped us experience new possibilities for our lovely x3 :) owait...

Recommended: http://www.mediafire.com/download/6dfaxasc8a2ue3a/Nightly-Kernel-3.4-12-01.zip

All versions: https://www.mediafire.com/folder/g44692oa9st1i/Nightly-Kernel-3.4

-Latest 3-
12/02: http://www.mediafire.com/download/2c4gaabb8i31aqy/Nightly-Kernel-3.4-12-02.zip General updates and fixups. (Not for general use)
12/19v3: http://www.mediafire.com/download/jnp5uaqafso5vxb/Nightly-Kernel-3.4-12-19v3.zip V3 includes a new fstab (Updates/fixes, removes GPU overclock) ( May cause data loss!)
02/24/2015: http://www.mediafire.com/download/sy142xkbw154r0w/Nightly-Kernel-3.4-02-24-2015.zip All 2015 commits included, abyssplugv2(avoid for now), probably has some cpufreq issues.

Avoid discussing Mourta's work in this thread. You're doing it wrong and you should post in his threads instead, thanks.

 

Latest versions, starting with 2015, only work with Mourta's LiquidSmooth.

Edited by NothingSerious
Link to comment
Share on other sites

Pretty much the only reason I thought of this name is because every kernel build posted here is a testing version. This kernel build will be updated pretty much every time a new commit is added to Mourta's bitbucket, only one version each day though. NOTE: Mourta cannot provide any support for this kernel, therefore do not attempt to report bugs or any issues to him. Since you are also using a TESTING version, expect bugs and perhaps bootloops.  Built with 4.9-SaberMod.

 

For changelogs, refer to Mourta's bitbucket: https://bitbucket.org/mourta/mourta-kernel-3.4.git

 

11/25: http://www.mediafire.com/download/b0wdvney2z9836e/Nightly-Kernel-3.4-11-25.zip

 

Well done. :)

Link to comment
Share on other sites

Thanks, surprisingly nobody has used this name :P

 

I think someone did. ;)

 

Just remember to thank Giuseppe, without him you would not have access to this code, quite literally.

Link to comment
Share on other sites

Hi, i use mourta kernel from any months, but i've 2 problems with all versions of this kernel:
1) the speakerphone is not working. When I start a new call "headphones" I hear it all, but when i click on the speakerphone icon, the sound disappears completely and the only thing to do is close the call. Even re-clicking the icon the sound not back through headphones. 

2) if I connect the charger, and reboot the device, no longer recognizes that it is charging. If I unplug the charger does not recognize that is statp removing the charger and the classic wakelock of when is connected to the charger remains active, discharging the battery.

 

I wiped cache and dalvik few times and no problems with other kernel. I using Dalvik.

STEPS:

1)

- Make a call

- Click on headphones icon

- sounds disappear totally on speakerphone and if i re-click the icon sounds on headphones not return

- Only one solution: close the call.

 

2) 

- plug the charger

- reboot with charger connected

- not recognize che charger and if i unplug the charger, wakelock eat the battery

- must disconnect charger, reboot and plug charger for recognize it

Edited by devilo
Link to comment
Share on other sites

Guest tool_king

Hi, i use mourta kernel from any months, but i've 2 problems with all versions of this kernel:

1) the speakerphone is not working. When I start a new call "headphones" I hear it all, but when i click on the speakerphone icon, the sound disappears completely and the only thing to do is close the call. Even re-clicking the icon the sound not back through headphones.

2) if I connect the charger, and reboot the device, no longer recognizes that it is charging. If I unplug the charger does not recognize that is statp removing the charger and the classic wakelock of when is connected to the charger remains active, discharging the battery.

I wiped cache and dalvik few times and no problems with other kernel. I using Dalvik.

STEPS:

1)

- Make a call

- Click on headphones icon

- sounds disappear totally on speakerphone and if i re-click the icon sounds on headphones not return

- Only one solution: close the call.

2)

- plug the charger

- reboot with charger connected

- not recognize che charger and if i unplug the charger, wakelock eat the battery

- must disconnect charger, reboot and plug charger for recognize it

You should have posted this in this thread:

http://www.modaco.com/index.php?/topic/373265-User-reported-problems-for-Liquid-and-Mourta-kernel-goes-here.

Link to comment
Share on other sites

12/02 online - General updates and fixups.

 

Last update is not for general use and will not work properly on any ROM.

 

This is a testing update that i'm using to test limits on other issues that have been reported from my testing crew.

Edited by Mourta
Link to comment
Share on other sites

Guest moneyvirus

Maybe im just lucky but it boots and it scales properly will try to get a log of the Bluetooth problem and my bluethooth headset it pairs but no sound need a reboot for sound

But this is a problem I have with all the 3.4 kernels

Edited by moneyvirus
Link to comment
Share on other sites

Maybe im just lucky but it boots and it scales properly will try to get a log of the Bluetooth problem and my bluethooth headset it pairs but no sound need a reboot for sound

 

 

No it doesn't.

 

You are just not aware of it, i know because i wrote it and i won't have a discussion of my code in a thread that isn't mine, if you have a problem with my code you go to the thread for reporting problems about my stable kernel.

 

Be sure to note what ROM you are using and what kernel. If it's not my Liquid and not my stable kernel i will ignore it completely.

Link to comment
Share on other sites

Guest NothingSerious

Last update is not for general use and will not work properly on any ROM.

 

This is a testing update that i'm using to test limits on other issues that have been reported from my testing crew.

 

In either way, it has been stated in the main post that nothing may work properly. It's up to the user if they want to install it or wait for a stable release. Thanks for the additional warning though.  :)

Edited by NothingSerious
Link to comment
Share on other sites

Guest moneyvirus

No it doesn't.

You are just not aware of it, i know because i wrote it and i won't have a discussion of my code in a thread that isn't mine, if you have a problem with my code you go to the thread for reporting problems about my stable kernel.

Be sure to note what ROM you are using and what kernel. If it's not my Liquid and not my stable kernel i will ignore it completely.

OK man I get your message, will give it a try with your last posted kernel from 27-11-2014 and ofcourse your ls ROM because I honestly love it

OK sorry man you are right (as always [emoji6] )

With your stable version from 27-11-2014 everything is working perfect

Edited by moneyvirus
Link to comment
Share on other sites

In either way, it has been stated in the main post that nothing may work properly. It's up to the user if they want to install it or wait for a stable release. Thanks for the additional warning though.  :)

 

 

If anyone is blaming you, send them over to Stockholm and i will give them a stern talking to. ;)

 

It's just a heads up, it's a special case, it will get worse before it gets better too, i'm pushing the very edges of the limit of what we can do with our device now.

 

The end result should be something pretty great though.

 

Only 396 000 lines of code left until it's time to optimize it... :S

Link to comment
Share on other sites

i use it with your ls rom and work good so far maybe the sound qualiti isnt so good but no prob

 

 

I'm sure that you have a better idea about the code of this kernel than i do so surely you are correct on this.

 

I wrote that code but still, i'm sure you know better.

Link to comment
Share on other sites

Guest abhi08638

I think he means there's some stuff that are broken underneath the UI. As in there are errors happening in the os that is causing performance to degrade. I would trust Mourta on this since only he knows what's really going on under the hood

Link to comment
Share on other sites

  • 3 weeks later...
Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.