[ROM] [MK4] digiblurROM Note2 - 2014.01.23

Search This thread

coiledwire

Senior Member
Oct 20, 2010
2,216
697
norcal
Digiblur, patiently waiting for your hotspot mod sir,probably still can't find time, I understand though...

Sent from my HTCONE using Tapatalk

You'll wait an eternity. Digiblur will never post a hotspot mod; it violates your T&C. You can use the hotspot mod from other roms but it'll probably break another feature; its a trade off you'll have to make.
 

Arjohns

Senior Member
Nov 12, 2011
472
207
It only breaks the all app multi window feature I believe. I'm sure its mentioned within the last few pages.

Sent from my Nexus 5 using Tapatalk
 

internetpilot

Senior Member
Jan 26, 2011
895
276
Fairfax, VA & Ponte Vedra, FL
  • Like
Reactions: smaw51 and JT man

supaumar

Member
Jun 9, 2010
35
5
If I'm running Paranoid Android 4.4 how would I go about installing this ROM. Tired of the instability/battery life on AOSP. Should I just wipe, flash MK4 baseband, and flash the ROM? Will wifi work? Would prefer not to flash a fix via Odin, don't have access to a PC, only Mac.
 

ColeTrain!

Senior Member
Nov 12, 2011
750
345
St. Louis, MO. Go Cardinals!!
If I'm running Paranoid Android 4.4 how would I go about installing this ROM. Tired of the instability/battery life on AOSP. Should I just wipe, flash MK4 baseband, and flash the ROM? Will wifi work? Would prefer not to flash a fix via Odin, don't have access to a PC, only Mac.

I put this together. Might have to do the Wifi fix, Idk and mac idk. But there is a link for the mk4 that is very easy. I'd do nandroid, mk4, wipe process B, rom, wifi fix,

Honestly, it's been too long. I forgot all the process. Lol

http://forum.xda-developers.com/showthread.php?t=2648855
 

ankurcshah

Senior Member
Dec 5, 2010
661
68
27
Coimbatore
Hey I dont have the option to send files via wifi direct and nfc just fc's as soon as I bump the phones. I need the wifi direct. Anyway I can get it to work? Love this rom otherwise

Sent from my SPH-L900 using Tapatalk 2
 

anishannayya

Senior Member
Dec 1, 2010
106
56
digiblur, first off, I'd like to thank you for all your hard work and dedication. It sucks that you are moving on to a different platform. I really wish that there were Google Play editions of Sprint phones...

In any case, I'd like caution anyone else who is considering upgrading but hasn't. I upgraded by going back to stock (with the KNOX platform). Issues I've noticed:

1) Wake lock issues. The phone simply doesn't want to go to sleep anymore, which means HIGH battery drain.
2) Random FCs and reboots. In fact, the entire experience is laggy.
3) Screen is laggy to turn on. It sometimes doesn't turn on at all (requiring a battery pull).
4) Audio glitches, especially when the screen is off. This indicates to me that the kernel isn't correctly scaling the CPU.
5) I hate the new jumbo fonts. I didn't buy a big phone to be able to read the same amount of text as an other 4.x" device. Worse, they occasionally don't rasterize properly.

Of course, I've tried re-flashing, re-downloading, etc.

What I would recommend (and I'm going to revert back to):
1) digiblurROM_20130602 (MC2)
2) Perseus-alpha36.3-l900
3) MK4 baseband

The above combination results is predictable performance and great battery life.
 

datdirtyscrew

Senior Member
Sep 11, 2010
488
88
Tone City Texas
digiblur, first off, I'd like to thank you for all your hard work and dedication. It sucks that you are moving on to a different platform. I really wish that there were Google Play editions of Sprint phones...

In any case, I'd like caution anyone else who is considering upgrading but hasn't. I upgraded by going back to stock (with the KNOX platform). Issues I've noticed:

1) Wake lock issues. The phone simply doesn't want to go to sleep anymore, which means HIGH battery drain.
2) Random FCs and reboots. In fact, the entire experience is laggy.
3) Screen is laggy to turn on. It sometimes doesn't turn on at all (requiring a battery pull).
4) Audio glitches, especially when the screen is off. This indicates to me that the kernel isn't correctly scaling the CPU.
5) I hate the new jumbo fonts. I didn't buy a big phone to be able to read the same amount of text as an other 4.x" device. Worse, they occasionally don't rasterize properly.

Of course, I've tried re-flashing, re-downloading, etc.

What I would recommend (and I'm going to revert back to):
1) digiblurROM_20130602 (MC2)
2) Perseus-alpha36.3-l900
3) MK4 baseband

The above combination results is predictable performance and great battery life.

I get none of the issues you get. Sorry. You must be special.
 
  • Like
Reactions: flofy22

anishannayya

Senior Member
Dec 1, 2010
106
56
Odd. Back to 4.1.2; stable as a rock again. I honestly don't know what it might be then. I'm using the exact same apps...

If T-mo had any reasonable amount of off-network roaming, I'd get a bloat-free device in an instant, ETF be damned.
 
digiblur, first off, I'd like to thank you for all your hard work and dedication. It sucks that you are moving on to a different platform. I really wish that there were Google Play editions of Sprint phones...

In any case, I'd like caution anyone else who is considering upgrading but hasn't. I upgraded by going back to stock (with the KNOX platform). Issues I've noticed:

1) Wake lock issues. The phone simply doesn't want to go to sleep anymore, which means HIGH battery drain.
2) Random FCs and reboots. In fact, the entire experience is laggy.
3) Screen is laggy to turn on. It sometimes doesn't turn on at all (requiring a battery pull).
4) Audio glitches, especially when the screen is off. This indicates to me that the kernel isn't correctly scaling the CPU.
5) I hate the new jumbo fonts. I didn't buy a big phone to be able to read the same amount of text as an other 4.x" device. Worse, they occasionally don't rasterize properly.

Of course, I've tried re-flashing, re-downloading, etc.

What I would recommend (and I'm going to revert back to):
1) digiblurROM_20130602 (MC2)
2) Perseus-alpha36.3-l900
3) MK4 baseband

The above combination results is predictable performance and great battery life.

I had the battery drain issue, none of the other though.

Sent from my SPH-L900 using xda app-developers app
 

Bill720

Senior Member
Mar 13, 2013
695
135
AT&T HTC One
Moto X Pure
intermittent problem

...

What I would recommend (and I'm going to revert back to):
1) digiblurROM_20130602 (MC2)
2) Perseus-alpha36.3-l900
3) MK4 baseband

The above combination results is predictable performance and great battery life.

Would there be any forseeable problems with using the latest Devil kernel instead? Because that's what I've been on, and I have been having problems with it completely locking up on me (why don't smartphones have reset pins anymore?). Usually happens when it's asleep, but has happened when it is awake, and usually 10 or more hours apart. I've tried raising the "underclocking" minimum in the Devil Tools control panel as suggested in another thread, but I still had it happen to me again today. Is there any easy way to troubleshoot this or common cause? I'll raise the minimum CPU frequency again to 700Mhz this time, so we'll see if that helps any, but in the meantime, does anyone have any other suggestions or an idea as to what might be causing the problem?

Thanks.


b
 

ColeTrain!

Senior Member
Nov 12, 2011
750
345
St. Louis, MO. Go Cardinals!!
Would there be any forseeable problems with using the latest Devil kernel instead? Because that's what I've been on, and I have been having problems with it completely locking up on me (why don't smartphones have reset pins anymore?). Usually happens when it's asleep, but has happened when it is awake, and usually 10 or more hours apart. I've tried raising the "underclocking" minimum in the Devil Tools control panel as suggested in another thread, but I still had it happen to me again today. Is there any easy way to troubleshoot this or common cause? I'll raise the minimum CPU frequency again to 700Mhz this time, so we'll see if that helps any, but in the meantime, does anyone have any other suggestions or an idea as to what might be causing the problem?

Thanks.


b

Why do you want to use devil kernel if you are having trouble with devil kernel?
I had the same problems as you. I believe is TWiz related. Some don't have issues. We are the lucky ones , i guess.
 

Bill720

Senior Member
Mar 13, 2013
695
135
AT&T HTC One
Moto X Pure
kernel inquiry

Why do you want to use devil kernel if you are having trouble with devil kernel?
I had the same problems as you. I believe is TWiz related. Some don't have issues. We are the lucky ones , i guess.

I'm not even really entirely sure if that is what is causing the problem at all. I just got the device last week, and this is the first real kernel and rom combination that I've actually spent more than 45 minutes with.

But to answer your question of why I'm using devil kernel; unless I'm mistaken (and I very well may be), Devil Kernel seems to be the only kernel that supports some form of Voodoo Sound (Boeffla Sound in this case) in addition to a way to correct the nasty green tint inherent with the super amoled display (I was actually at a loss after looking at all the settings until I checked "Master Sequence" inside of the "color calibration" screen in the "screen settings" tab of Devil Tools, and that fixed 90-95% of the problem right there on the spot). If you're pretty sure this is the problem and if you know of any other kernel that can do the audio and screen tweaks, I'm all ears.


b
 
Last edited:

ColeTrain!

Senior Member
Nov 12, 2011
750
345
St. Louis, MO. Go Cardinals!!
I'm not even really entirely sure if that is what is causing the problem at all. I just got the device last week, and this is the first real kernel and rom combination that I've actually spent more than 45 minutes with.

But to answer your question of why I'm using devil kernel; unless I'm mistaken (and I very well may be), Devil Kernel seems to be the only kernel that supports some form of Voodoo Sound (Boeffla Sound in this case) in addition to a way to correct the nasty green tint inherent with the super amoled display (I was actually at a loss after looking at all the settings until I checked "Master Sequence" inside of the "color calibration" screen in the "screen settings" tab of Devil Tools, and that fixed 90-95% of the problem right there on the spot). If you're pretty sure this is the problem and if you know of any other kernel that can do the audio and screen tweaks, I'm all ears.


b

On Twiz devil is the only one... It doesn't work for me. There is one more for AOSP and devil works there too.
 

Bill720

Senior Member
Mar 13, 2013
695
135
AT&T HTC One
Moto X Pure
kernel information

On Twiz devil is the only one... It doesn't work for me. There is one more for AOSP and devil works there too.

What was it doing for you? Was it just locking up or was it something else?

For me, the reason I'm trying to stay with TouchWiz versus AOSP/CM based roms is a long list of small features and annoyances. For me, the experience offered by digiblur and Devil has been pretty good, and I was able to fix the few problems I did have (with the possible exception of the default picture/avatars in the dialer and contacts apps, those are just weird).

b
 
Last edited:

digiblur

Senior Member
Jul 24, 2007
3,149
2,074
digiblur, first off, I'd like to thank you for all your hard work and dedication. It sucks that you are moving on to a different platform. I really wish that there were Google Play editions of Sprint phones...

In any case, I'd like caution anyone else who is considering upgrading but hasn't. I upgraded by going back to stock (with the KNOX platform). Issues I've noticed:

1) Wake lock issues. The phone simply doesn't want to go to sleep anymore, which means HIGH battery drain.
2) Random FCs and reboots. In fact, the entire experience is laggy.
3) Screen is laggy to turn on. It sometimes doesn't turn on at all (requiring a battery pull).
4) Audio glitches, especially when the screen is off. This indicates to me that the kernel isn't correctly scaling the CPU.
5) I hate the new jumbo fonts. I didn't buy a big phone to be able to read the same amount of text as an other 4.x" device. Worse, they occasionally don't rasterize properly.

Of course, I've tried re-flashing, re-downloading, etc.

What I would recommend (and I'm going to revert back to):
1) digiblurROM_20130602 (MC2)
2) Perseus-alpha36.3-l900
3) MK4 baseband

The above combination results is predictable performance and great battery life.

Sprint has Google Play editions. It's called the Nexus 5 ;)
 

ankurcshah

Senior Member
Dec 5, 2010
661
68
27
Coimbatore
Hey I dont have the option to send files via wifi direct and nfc just fc's as soon as I bump the phones. I need the wifi direct. Anyway I can get it to work? Love this rom otherwise
Sent from my SPH-L900 using Tapatalk 2
 

Top Liked Posts

  • There are no posts matching your filters.
  • 101
    digiblurROM MK4 Note2 Deodex - 2014.01.23

    ATTENTION Thin Skinned Users: Dry humor ahead 1 post.

    I've always enjoyed a nice simple to the point ROM on my phone. It seems many ROMs start out as this but tend to stray quickly so I have shared mine for everyone to hate or enjoy. If you are looking for some heavily themed ROM with 68 notification toggles, everything turned purple, etc, then press the back button now.

    What the ROM does NOT have:
    - Some cute build name
    - A cool team name
    - beta or alpha version number
    - themes
    - crazy zombie jumping out the phone for a boot screen
    - kiddie boot sounds
    - annoying Sprint boot animation/sound
    - dumb Sprint shut down animation/sound
    - stupid camera shutter sound during screen shots and camera usage(turn off in camera settings)
    - idiotic 777468(SPRINT) code requirement on the ##DEBUG# menu (entire prompt is gone)
    - MSL code checks on ##DATA# Editing (to quickly turn off LTE without a reboot or MSL code)
    - tons of Samsung & Sprint bloat
    - 1.21 gigawatts of overclocking
    - unnecessary carrier customizations that screws up your Sensorly points
    - eyeball icon in the taskbar (removed properly)
    - redundant "You have lost data..blah blah" message when switching to roaming (we have a triangle on our signal already!)
    - full battery charge notification
    - sympathetic support team
    - Sprint connection optimizer toggling your wifi and spying on the usage of the neighborhood's open wifi access point
    - KNOX garbage and knags
    - Headphone volume level too loud nag

    What it does have:
    - Proper base with Sprint sales code
    - 1X signal type display corrected (shame on you Sprint!! Tested and works!)
    - modified battery icons with battery percentage
    - PRL Write enabled in the ##DATA# menu (-PRL Thread Here-)
    - 4-in-1 reboot mod
    - A mod that announces "I'm watching porn!" every 30 seconds if you write those dumb 00001 PRLs (I wish!)
    - All apps multi-window mod built from proper MK3 base files
    - KISS principle
    - Dry humor in the ROM first post and continued posts throughout the thread by the ROM author
    - Google Maps 6.14.2 w/KML layer usage (remove updates if it gets auto-updated)
    - Blacked out Google Hangouts (the way it should look!)

    Screenshots
    None needed as it is stock. Just a status bar shot is necessary

    S3STATUSBAR.jpg


    Changelog
    2014/01/26 - complete revamp based on MK4 4.3 Note2 stock base

    2013/06/03 - reworked from the ground up on the MC2 deodexed base provided by crawrj. No old MA7 files were used or harmed in this build! Removed additional APK bloat.

    2013/02/25 - corrected issue of factory reset after flash showing black background and no status bar. Also included a patch for the removal of the prompt at ##DEBUG# screen.

    2013/02/24 - Removed the calls to show the "eyeball" icon when smartstay is turned on. Removed the 100% battery notification. Removed FWUpgrade.apk. Removed the "You have lost data connectivity" nag when you switch over to roaming. Look at that! I didn't add anything new but released a new version! WOOHOO

    2013/02/19 - Initial Release

    -Download digiblurROM MK4 Note2 Deodex - 2014.01.23-
    -Download Removed APKs for digiblurROM MK4 Note2 Deodex - 2014.01.23-

    VERIFY YOUR MD5 AFTER DOWNLOADING! Androidfilehost.com doesn't calculate them and show them just for kicks!

    Huge Thanks to LilCozyFab as this wouldn't be here today without his extensive/tiring testing, the very high risk of killing his device due to the issues we had, and motivation/pushing me to do this!

    To Do List:
    - Correct Live Wallpaper crash issue

    Disclaimer:
    This ROM might eat your phone, USB cable, charger, SD card, unborn child, children, significant other, fried chicken, and/or anything else you own. As with any phone modifications you are own your own and accept all responsibilities of doing so by downloading/flashing anything contained on this website or any other website.

    How to upgrade to digiblurROM MK4

    ***Please backup any pictures, info, documents, etc from your device to separate device/computer!***

    I recommend a pure 4.3 updated phone but this does mean you will have the KNOX bootloader warranty value tripped. If you do not prefer to have a 4.3 pure phone then please skip to the section for flashing with the 4.1.x bootloader.

    1. You will need to be on the 4.3 stock version of Android for the Sprint Note2. To accomplish this you can either use one of the one touch ODIN back to 4.1.x unrooted stock and let the 4.3 update download and install. Or you can flash the full 4.3 ODIN update.

    Instructions for returning to Stock unrooted 4.1.x:

    http://www.sxtpdevelopers.com/showthread.php?t=228

    Instructions for going straight to 4.3 unrooted:

    http://forum.xda-developers.com/showthread.php?t=2591898

    2. Once you are on the Stock 4.3 update please verify the baseband and such in the Settings -> About phone. For safe measure make sure your cellular and WiFi data connection and voice connections work as well.

    3. If you are not familiar with getting into recovery mode I suggest reading this: Recovery mode is a bit tricky at times. If you're a second too early or too late, your phone will skip going into recovery and boot normally. If this happens you will have to repeat the Odin process in it's entirety. So unless you are familiar with this, I would give it a few practice runs before starting Odin: Recovery mode is achieved pressing and holding "volume UP, power button and the (physical) home button simultaneously. Watching the screen closely, release all 3 buttons as soon as you see the word Samsung. If timed correctly it will boot into recovery in about 10-20 seconds (after releasing). Remember if you are too early or late the phone will boot normally and skip recovery.

    4. First get ODIN on your machine and working with your phone. I already had ODIN and the drivers from a while back on my machine but I believe you can get the standard Samsung and Odin driver/app here: http://forum.xda-developers.com/showthread.php?t=2011491

    5. Download the latest TWRP or Philz Recovery for the Sprint Samsung Note2. Get the ODIN flashable TAR. Your decision, both work fine but some people claim Philz is better for Android 4.3 backups and restores

    TWRP:

    http://teamw.in/project/twrp2/117

    Philz CWM:

    http://forum.xda-developers.com/showthread.php?t=2552653

    6. Download the the latest digiblurROM for the Note2. Verify the ZIP file and copy it to the internal or external SD card of the Note2.

    7. Power off the Note2 with no USB cable attached, go ahead and remove the back cover for easy removal of the battery after flashing.

    8. Get into download mode by pressing and holding volume down, power button and the (physical) home button simultaneously. You will continue to hold all 3 buttons until you see a warning. Then press the volume up button and you will be in download mode.

    9. Plug in the USB cable into your phone and open ODIN. If ODIN is working you should see a COM port listed in the box towards the upper left.

    10. Verify that both Auto Reboot and F. Rest Time are UNCHECKED.

    11. The only check mark should be next to PDA. Select PDA and browse to the TAR file you downloaded for TWRP or CWM.

    12. Hit start. Watch the progress on the upper left. Once recovery is installed, pull the battery, so the phone doesn't reboot normally, and disconnect the usb cable.

    13. VERY IMPORTANT. You will need to reboot into Recovery mode without the phone booting up normally! If you miss it then the phone will boot into the OS and overwrite the recovery you just installed.

    14. Once you are in TWRP/Philz CWM, I do recommend doing a full data/factory reset.

    15. Install the digiblurROM zip by choosing the options to install the ZIP.

    16. After the successful install of the digiblurROM zip flash, reboot the device using the reboot option in TWRP/CWM.

    17. The phone will take a few minutes longer during this initial boot due to building the cache/dalvik. Do not worry, this is normal.

    18. Go through the standard Android setup process. Please note, the Play Store and other apps may appear to hang as the Google Services framework is updating to the latest version. I have included the older 6.x version of Google Maps for those that prefer this version since it allows KML layers and other features. The Play Store will automatically update this app when on WiFi, turn this option off and uninstall any updates to Google Maps if you prefer this version.

    19. Enjoy!

    How to Flash with the 4.1.x bootloader

    1. I will assume you already have a custom recovery installed. I would take this time to update it to the latest version before continuing. You can find the links to TWRP and CWM above for updating.

    2. Flash the MK4 baseband via recovery:. http://www.androidfilehost.com/?fid=23212708291682160

    3. Reboot and verify the baseband installed.

    4. Download the the latest digiblurROM for the Note2. Verify the ZIP file and copy it to the internal or external SD card of the Note2.

    5. Reboot into Recovery mode. If you do not have a ROM installed with a Reboot into Recovery mode option please power the device off and use this method: Recovery mode is achieved by pressing and holding "volume UP, power button and the (physical) home button simultaneously. Watching the screen closely, release all 3 buttons as soon as you see the word Samsung. If timed correctly it will boot into recovery in about 10-20 seconds (after releasing). Remember if you are too early or late the phone will boot normally and skip recovery.

    6. Once you are in TWRP/Philz CWM, I do recommend doing a full data/factory reset.

    7. Install the digiblurROM zip by choosing the options to install the ZIP.

    8. After the successful install of the digiblurROM zip flash, reboot the device using the reboot option in TWRP/CWM. Your wifi may not work, we will fix this after the reboot.

    9. The phone will take a few minutes longer during this initial boot due to building the cache/dalvik. Do not worry, this is normal.

    10. Go through the standard Android setup process. Please note, the Play Store and other apps may appear to hang as the Google Services framework is updating to the latest version. I have included the older 6.x version of Google Maps for those that prefer this version since it allows KML layers and other features. The Play Store will automatically update this app when on WiFi, turn this option off and uninstall any updates to Google Maps if you prefer this version.

    11. If your WiFi is not working - Since you have the older bootloader you will need to flash the WiFi fix found here via ODIN: http://forum.xda-developers.com/showpost.php?p=47817184&postcount=81
    18
    I just finished up and posted the S3 version. The changes should be the same between the two. I was working on both but decided to push forward and get the S3 done as I had the device to test on. I do not have the Note2 in possession but I do have a device to send test builds to. My goal is to have it out in a week if everything goes as planned.
    16
    I figure I should update this instead of just dropping off the earth. Unfortunately for the Note2 users I've moved on to the Nexus5 and no longer have a Note2 to develop/test on. I appreciate all the great thank-you's I've received from all of you, it made it all worth it! Thanks!

    As of now, this is where the era of the digiblur Note2 ROM ends. What now? A few options: 1. Do nothing and disable the notification to receive updates. 2. Disable the notifications and write the new MK4 baseband (confirmed by many it works great, including myself). 3. Drop my ROM like your ex-old lady, shake it off and move to something better! I recommend the_plattypus's work. He does a great job with his ROMs. Check out his SynergyROM here: http://forum.xda-developers.com/showthread.php?t=2090160

    Thanks again and see you guys around.
    14
    Thanks for the testing! The OP has been updated with the new ROM download.
    12
    I will say this once in here and then I will leave you guys alone. (Just trying to be proactive before it gets to a point where it gets out of hand).

    ~This is not a thread to rant about what YOU think the rom should be, or what YOU think the OP should say.

    ~This is not a thread to try and bring up an already dead argument from another thread.

    ~The rules are simple here: If it isn't relevant to this rom, then there isn't any reason to be posting at all in here. Be respectful when posting. Respect is EVERYTHING.

    If you have a sincere question, then by all means ask. If you knowingly post something that will cause an issue, then that post will disappear and the person posting it might disappear for a little also. Not trying to sound threatening or trying to "flex my muscle" (believe me I'm pretty weak :p ), just giving a fair warning for all to see. Have a good day and happy flashing.
    :victory:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone