Samsung Galaxy Note Upgrade/Update Experience from 4.0.4 with aftermarket ROMs

It really seems that 4.4.4 is not ready or stable for the i717 yet and this makes sense since it takes a lot of work/development and testing to get the factory stock ROMs working well.  In the end I used the 4.1.2 based Blackstra BlackJelly because it was fast, stable and just works and feels great.  The aftermarket support is great but many devs are focussed on adding features and customization that most of us don't want or need rather than getting things smooth and stable.

 

CandyKat-quincyatt-4.4.4.release.v1.5.7-Official-20140801.zip
Problems:
No sound
Hardware keys don't work
Comments: I don't like the style/layout of the ROM, it is too bare-bones and the sweetener packs don't make sense (just include them).

LS-KK-v3.1-OFFICIAL-quincyatt.zip
Problems:
Random reboot/freeze/crash
H+ no LTE (network eventually stopped working altogether)
Comments: Perfect layout and setup and functionality aside from frequent random freeze/crash/reboots.

BeanStalk-4.4.4007-20140711-quincyatt.zip

Problems:
The only hardware key to work is the "back" button.
Comments

BlackStar BlackJelly ver 2.zip

Problems:
Saw the ATT Logo moving and then it freezes and never booted
.......actually waited a few minutes longer after reboot and it worked.


Tags:

samsung, galaxy, upgrade, update, aftermarket, romsit, factory, roms, blackstra, blackjelly, devs, focussed, adding, features, customization, candykat, quincyatt, zip, hardware, comments, layout, rom, sweetener, packs, ls, kk, reboot, lte, altogether, functionality, reboots, beanstalk, quot, blackstar, ver, att, logo, freezes, booted,

Latest Articles

  • QEMU / KVM How To Manually Create Basic Virtual Machine VM
  • Linux wlan0 check all wireless clients
  • PHP Issues With Decoding Strange Smart Quotes And Non-Standard ASCII Characters
  • /etc/iproute2/rt_tables default settings file in Linux Centos 6,7 and most other NIX's
  • bind named error solutions named[2169]: error (no valid DS) resolving / error (broken trust chain) resolving / : error (no valid RRSIG) resolving 'com/DS/IN':
  • iptables how to log ALL dropped incoming packets
  • How To Edit Linux Based NM Network Manager Connection Settings Without GUI
  • Linux Disable IPV6 Centos / Debian / Mint Howto
  • Linux use growisofs to burn a larger file on a BD-R / Bluray Disc
  • Linux partprobe/partx cannot access last and 4th partition
  • DRBD Errors Caused By Physical Corruption
  • mdadm: add new device failed for /dev/sdb4 as 3: Invalid argument solution
  • Linux named / bind how to dump, view and clear the cache!
  • Centos 6 / 7 / 8 How To Change Default nameservers in /etc/resolv.conf when using DHCP / dhclient
  • Adobe Acrobat Reader for Linux to use and view XFA Fillable Forms
  • Debian Linux Mint Ubuntu iptables save and restore settings automatically onboot and reboot
  • Why SMART is not smart at all and doesn't properly predict disk errors that cause a kernel panic or crash
  • scp: ambiguous target error and solution
  • VirtualBox How To Add iSCSI Storage using VBoxManage
  • iSCSI on Centos 7 Configuration and Setup Guide for Initiator and Target