[KERNEL][AOSP4.4/5.1/6.0/7.1] dkp - d2spr - 2/4/18

ZipAddict

Senior Member
I flashed to the latest 5.1 Kernel (12-27-2015) on here, but I see the Kernel version is still 3.4.109. A user posted above who is on MM has 3.4.110.

Is this correct?

If so, what's the reason behind not updating all of them to the latest kernel despite same base (3.4)?
This is correct. Im on 5.1 and its the same. Everything is synced up so i think it is just typo in that file but i will look into it this week.
 
  • Like
Reactions: SonicPower

beany23

Senior Member
Jan 15, 2015
628
483
83
Fantastic! I'm not running mm right now (Bluetooth doesn't work on any mm ), but I am going to test the 5.1.x kernel now.
Thanks decimalman! You rock bro.
I'm currently running the latest octos weekly build and Bluetooth works flawlessy. I'm not sure if u know if it works now or not just thought I'd let ya know
 
  • Like
Reactions: madbat99

wilberfan

Senior Member
Jan 4, 2011
545
66
58
So Cal
I'm running the latest AICP MM nightlies on my d2spr (VirginMobile). Everything is fine with the stock kernel, but when I flash the 1227 dkp I lose my data connectivity. I've tried a lot of different combinations of reflashing--of the kernel, of the APN -- but I've been unable to get my data back without reverting to the kernel that comes with the AICP.

Any suggestions?
 

beany23

Senior Member
Jan 15, 2015
628
483
83
I'm running the latest AICP MM nightlies on my d2spr (VirginMobile). Everything is fine with the stock kernel, but when I flash the 1227 dkp I lose my data connectivity. I've tried a lot of different combinations of reflashing--of the kernel, of the APN -- but I've been unable to get my data back without reverting to the kernel that comes with the AICP.

Any suggestions?
I had the same issue on my phone. To fix it I had flash APN the clear cache then flash again then reboot recovery flash one more time then once booted I turned on airplane mode on then off then my data came on and has been working since then. Give it a try
 

wilberfan

Senior Member
Jan 4, 2011
545
66
58
So Cal
I had the same issue on my phone. To fix it I had flash APN the clear cache then flash again then reboot recovery flash one more time then once booted I turned on airplane mode on then off then my data came on and has been working since then. Give it a try
My first attempt didn't work; want to verify the sequence:

  1. Flash dkp kernel (over AICP nightly)
  2. flash APN
  3. Clear Cache (JUST cache, or dalvik and cache?)
  4. Flash APN again
  5. reboot (into system? or reboot recovery directly?)
  6. Reboot into Recovery
  7. Flash APN again
  8. Reboot into System
  9. Toggle Airplane Mode On/Off

Is this correct?

[edit] This sequence didn't work for me. Would the baseband make any difference? I'm on ND8.
 
Last edited:

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
My first attempt didn't work; want to verify the sequence:

  1. Flash dkp kernel (over AICP nightly)
  2. flash APN
  3. Clear Cache (JUST cache, or dalvik and cache?)
  4. Flash APN again
  5. reboot (into system? or reboot recovery directly?)
  6. Reboot into Recovery
  7. Flash APN again
  8. Reboot into System
  9. Toggle Airplane Mode On/Off

Is this correct?

[edit] This sequence didn't work for me. Would the baseband make any difference? I'm on ND8.
Update to nj2 at least. I've seen that fix data issues for many ppl.
 

bhays33

Senior Member
Apr 25, 2014
62
14
0
Beany23 - I'm not sure how you have Bluetooth working flawlessly but I would like to know. I'm pretty sure Bluetooth isn't working correctly on marshmallow. I have been able to get media playback to work perfectly however I cannot get it to operate under the phone functions at all. I've tried all marshmallow builds with and without kernels with and without G apps still no go. Will not receive calls when bluetooth is connected and will crash the phone app when trying to make a call with Bluetooth

Sent from my SPH-L710 using Tapatalk
 

beany23

Senior Member
Jan 15, 2015
628
483
83
Beany23 - I'm not sure how you have Bluetooth working flawlessly but I would like to know. I'm pretty sure Bluetooth isn't working correctly on marshmallow. I have been able to get media playback to work perfectly however I cannot get it to operate under the phone functions at all. I've tried all marshmallow builds with and without kernels with and without G apps still no go. Will not receive calls when bluetooth is connected and will crash the phone app when trying to make a call with Bluetooth

Sent from my SPH-L710 using Tapatalk
I'm running the 1-16 build from octos with dkp 6.0m same with ROM and I have had not one single issue. I'm also using the triband which is d2rfreshspr . are u using d2spr or same as me? Also I can receive and send files between w.e. device with no issue
 
Last edited:

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
Do we know if the NJ2 is the latest and greatest available for our phone?
Don't think it is. I saw a .tar of oh1 somewhere. But you have to look at the name of the file carefully. Apparently there is oh1 for regular and one for triband. Brilliant.
Not even sure if oh1 is the latest, but its the latest .tar available. Anything newer is just available as update .zips.
 
  • Like
Reactions: wilberfan

wilberfan

Senior Member
Jan 4, 2011
545
66
58
So Cal
Don't think it is. I saw a .tar of oh1 somewhere. But you have to look at the name of the file carefully. Apparently there is oh1 for regular and one for triband. Brilliant.
Not even sure if oh1 is the latest, but its the latest .tar available. Anything newer is just available as update .zips.
And the NJ2 has to be ODIN'd, correct? There aren't any flashable .zips? Followed by re-rooting the phone, etc...?
 

ZipAddict

Senior Member
Hey. Any update on this?

I'm wondering what's stopping people from flashing the 6.0 Kernel onto into 5.1.
My apologies i have had internet troubles and my reply did not go through like i thought. This is not a typo. It is on 3.4.109 according to the top of the makefile in the kernel source code. Most likely this is because recoding everything to update would be a nightmare and have minimal improvement on performance or it may just be unnecessary. I will ask decimalman about this in my next message to him.

In the meantime, if anyone can come up with info/links that shows that upgrading the kernel version for our device and android version would result in performance improvements, then I am sure it will be considered.

Dont ever flash anything that is meant for a different android version. At minimum it will soft brick the device.
 
Last edited:

SonicPower

Member
Oct 29, 2009
38
4
0
My apologies i have had internet troubles and my reply did not go through like i thought. This is not a typo. It is on 3.4.109 according to the top of the makefile in the kernel source code. Most likely this is because recoding everything to update would be a nightmare and have minimal improvement on performance or it may just be unnecessary. I will ask decimalman about this in my next message to him.

In the meantime, if anyone can come up with info/links that shows that upgrading the kernel version for our device and android version would result in performance improvements, then I am sure it will be considered.

Dont ever flash anything that is meant for a different android version. At minimum it will soft brick the device.
I discovered how to check CM kernel code, and yeah, it hasn't been updated for 3-4 months on the 12.1 line. Everyone moved on to CM 13, so despite having a 0.0.1 tick version difference, devs aren't going to work on 12.1 any more to maintain compatibility.

Theoretically, it should work in this sense, but whatever.

Users should probably move on to CM 13 then.
 
  • Like
Reactions: ZipAddict

ZipAddict

Senior Member
I discovered how to check CM kernel code, and yeah, it hasn't been updated for 3-4 months on the 12.1 line. Everyone moved on to CM 13, so despite having a 0.0.1 tick version difference, devs aren't going to work on 12.1 any more to maintain compatibility.

Theoretically, it should work in this sense, but whatever.

Users should probably move on to CM 13 then.
If u must try flashing the other kernel, then make a nandroid backup first and test it by restoring it as well. Have the stock firmware/debrick image and adb setup, etc so that you can fix things. I would bet $ it will cause a soft brick if it successfully executes.

I have been training for months to work towards maintaining DKP because decimalman is very busy. I am almost there. Everyone hang in there and i plan to maintain 4.4.2 and up. I have much still to learn along the way, but updates will be coming soon and DKP will not die anytime soon. Thank u for everyones loyalty and support to DKP!
 

dingermtb

Senior Member
Sep 5, 2010
1,650
1,588
0
Richeyville
If u must try flashing the other kernel, then make a nandroid backup first and test it by restoring it as well. Have the stock firmware/debrick image and adb setup, etc so that you can fix things. I would bet $ it will cause a soft brick if it successfully executes.

I have been training for months to work towards maintaining DKP because decimalman is very busy. I am almost there. Everyone hang in there and i plan to maintain 4.4.2 and up. I have much still to learn along the way, but updates will be coming soon and DKP will not die anytime soon. Thank u for everyones loyalty and support to DKP!
Thanks mate. This is probably the best news I've heard all night. And also I like to add that Thursday I have a surgery and another one on March 10th and if all goes well my vision could be restored and if that happens I'm going back to making splash images that can be used with the dkp. Also if I'm not mistaken look back through the thread I believe I posted my thread for the splash screen images and you can use them with DKP

Sent from outside the 9 using my Exodus SGS3
 
  • Like
Reactions: ZipAddict