Related
This is place where you can come and ask questions regarding support as well as any other general discussion for the Null rom. Please keep the development thread to just that DEVELOPMENT. The developer of this rom is here to develop and not here to answer your questions because you can't take the time to figure out the answer yourself. This will be a community driven thread. Therefore, if you feel something needs to be added to the OP please mention me in a post and I'll take a look
If you need to download the rom free to stop by the dev thread to download. However, if I see you ask a question in here and then go to that thread to ask the same question I will be handing out infractions. Please consider this your only warning.
On a side note, I'll be transferring the OP of this thread to a person with this device in due time. However, for the moment this needed to be created. If you are willing to take the OP from me please feel free to send me a PM. The only requirement that I would have is that you keep it updated properly.
FAQ / IT DOESNT WORK ! WAH
INTERNET ACCESS
GO INTO "FULL SETTINGS -> BLUETOOTH -> SELECT YOUR PHONE SETTING ICON (ON THE RIGHT OF PHONE NAME) -> TICK INTERNET ACCESS".
ENSURE BLUETOOTH TETHERING IS ENABLED ON YOUR PHONE BEFORE HAND OBVIOUSLY.
*NOTE* ENSURE YOUR MOBILE DEVICE SUPPORTS TETHERING, US VARIANT PHONES HAVE RESTRICTIONS INPLACE. REFER TO THE US INTERNET TETHERING THREAD.
*NOTE 2* BLUETOOTH TETHERING DOES NOT AUTO RECONNECT, INSTALL THIS THIRDPARTY SOLUTION ON YOUR GEAR TO ENABLE AUTO RECONNECT.
PLAYSTORE / GOOGLE ACCOUNT MANAGER HAS STOPPED..
VERIFY YOU HAVE A BLUETOOTH INTERNET TETHERING CONNECTION ESTABLISHED BEFORE ATTEMPTING TO ADD A GOOGLE ACCOUNT.
MUST NOT BE USING THIRD PARTY TETHERING, EG. PDANET.
HOW DO I FULL WIPE?
BOOT INTO RECOVERY MODE AND SELECT THE "RECOVERY" OPTION. DO THIS AFTER FLASHING THE ROM
UNABLE TO WAKE GEAR WHILE IN PHONE CALL
THIS IS CAUSED BY THE HOME BUTTON REMAP MOD, THE HOME BUTTON MUST BE PRESSED IN ORDER TO WAKE THE GEAR UP IN THIS STATE.
ONLY WORK AROUND IS TO EITHER USE THE WRIST WAKEUP GESTURE OR DISABLE THE HOME BUTTON REMAP MOD.
*NOTE* BY DISABLING THE HOME BUTTON REMAP MOD, THIS WILL DISABLE THE ABILITY TO MANUALLY LOCK THE SCREEN WHILE USING A CUSTOM LAUNCHER.
DOUBLE TAP BRIGHTNESS/SOUND TOGGLE HAS DISAPPEARED
THIS IS CAUSED BY USING THE FULL SYSTEM UI, SIMPLY PUT IT REPLACES THE DOUBLE TAP WINDOW WITH THE NOTIFICATION SHADE. BY USING GRAVITYBOX YOU CAN ADD ADDITIONAL TOGGLES LIKE BRIGHTNESS & SOUND TILES TO THE FULL NOTIFICATION SHADE.
OTHERWISE SIMPLY REFLASH THE ROM WITH THE FULL SYSTEMUI OPTION UNTICKED.
SCREEN FLICKERING/GITTERING
THIS IS CAUSED BY THE INITIAL BOOTUP, REBUILDING THE CACHE AND INITIALIZING ALL THE APPS. GIVE YOUR GEAR A FEW MINUTES TO SETUP AND RESTART.
SCREEN UNLOCKS TO NOVALAUNCHER PAGE PREVIEW?
GO INTO "NOVA SETTINGS -> GESTURES -> HOME BUTTON -> NONE".
ENABLE DEVELOPER SETTINGS / USB DEBUGGING
GO INTO "SETTINGS -> GEAR INFO -> ABOUT GEAR", TAP SOFTWARE VERSION 10 TIMES.
ENABLE UNKNOWN SOURCE APK INSTALLATION
GO INTO "FULL SETTINGS -> SECURITY -> TICK UNKNOWN SOURCES".
ENABLE MTP
GO INTO "FULL SETTINGS -> STORAGE -> MENU BUTTON (TOP RIGHT OF SCREEN) -> USB COMPUTER CONNECTION -> MEDIA DEVICE (MTP)".
WATCH STYLER NOT WORKING
ENSURE ITS SELECTED AS THE DEFAULT WATCHFACE IN GEAR MANAGER.
IF CLOCK FACE DOES NOT UPDATE UPON CHANGING, RESTART GEAR.
DOUBLE CLICK HOME BUTTON DOESNT WORK ON TOUCHWIZ LAUNCHER !
*NOTE* DO NOT DO THE FOLLOWING IF YOU ARE USING NOVALAUNCHER, YOU WILL NOT BE ABLE TO MANUALLY LOCK YOUR GEAR.
*NOTE 2* YOU CAN SIMPLY REFLASH THE ROM WITHOUT WIPING AND DISABLE THE HOME BUTTON REMAP MOD.
NAVIGATE/PULL THE FOLLOWING FILE FROM YOUR GEAR: /SYSTEM/USR/KEYLAYOUT/GPIO-KEYS.XML
EDIT IN A TEXT EDITOR SO IT LOOKS LIKE THE BELOW:
Code:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 116 POWER WAKE
[B]key 172 HOME WAKE[/B]
edit
Amazing. This thread is very much needed song as how the dev thread keeps getting cluttered with posts that wouldn't be there if some one would have read
sent from my Note 3 or Galaxy Gear
Yeah this thread is an awesome idea to leave the general discussion and support issues out of the other thread.
Whenever I select "recovery" it doesn't give me an option to install the rom?
I followed the steps for the root and the add the .zip to my SD card on the phone. When I select the option for recovery it just does a system restore on it. Any help?
You need to flash twrp first
sent from my Note 3 or Galaxy Gear
feature request
[what about to include support fpr AquaMail client?
I'm using it and I think it is the better at the moment
The developer could be interesting....
Just a quick (somewhat noob) enquiry about the Gear and what this ROM can do for it, as I'm thinking of picking up a Note3 + Gear from work (Vodafone), as the watch is free.
Firstly, I hate Touchwiz with a passion! I don't wish for anyone to read that in an angry way, but I'm really not fond of the colours, themeing, etc. of that particular UI. I much prefer vanilla Android and, as such, would look to root the Note3 and install CM or an equivalent on it.
Would I then lose any functionality of the Gear? Can the GearManager APK be installed on a non-TW ROM?
I'll need a bit of an idiot's guide for the whole thing, but it's nothing I can't research.
Pepski said:
Just a quick (somewhat noob) enquiry about the Gear and what this ROM can do for it, as I'm thinking of picking up a Note3 + Gear from work (Vodafone), as the watch is free.
Firstly, I hate Touchwiz with a passion! I don't wish for anyone to read that in an angry way, but I'm really not fond of the colours, themeing, etc. of that particular UI. I much prefer vanilla Android and, as such, would look to root the Note3 and install CM or an equivalent on it.
Would I then lose any functionality of the Gear? Can the GearManager APK be installed on a non-TW ROM?
I'll need a bit of an idiot's guide for the whole thing, but it's nothing I can't research.
Click to expand...
Click to collapse
No. Sadly not.
Or at least not with all the bells and whistles working.
I actually am testing CM11 on my note 3 as I type. I was wondering if someone could link me to the latest gear manager so I could test how it works.
Sent from my Note 3 w/ CM11
ktetreault14 said:
I actually am testing CM11 on my note 3 as I type. I was wondering if someone could link me to the latest gear manager so I could test how it works.
Sent from my Note 3 w/ CM11
Click to expand...
Click to collapse
Here's 2 versions. The latest and the previous one, a lot of people are having problems with the latest, and even Samsung supposedly admitted it was bugged and they were going to release a new one. The previous version seems to work fine for people, and there's no real functional updates on the latest one anyway, so you might prefer it.
Latest version - 1.5.121601
Previous version - 1.5.120903
I couldn't get cm11 to download the necessary apks for gear manager so I restored a tw backup and backed up the apks themselves. When I went to restore them the only ones that would not restore were the weather and svoice. It is paired now with gear manager running in the notifications. Still testing out what works and what doesn't
Sent from my Note 3 w/ CM11
Running 16, removed Ms. Pac-Man for running too slow on the Gear, everything's running smooth.
Sent from Spaceball One.
I have nexus 5 rooted and running null16, could anyone please point me out how to make gear manager to work?has anyone made notifications work? so far i can just make calls from it and syncs the time.I have read everywhere but nothing works so far and i can't seem to find a reliable sorce of information. If we could make something like an app and null to be modified to work with that so we lose gear manager dependency i belive that would be a game changer . Fomey i will donate something pretty soon as i allways apreciate work from people creative like yourself .
EDIT: 15 AUD for you Fomey, thank you for your work !
reboot after install of null_16
i have attempted several times now to install the null_16 on my galaxy gear. after each time i attempt to go into the recovery mode to actually install it, it reboots and resets the device. i have read numerous times to flash the null_03_TWRP2.7.tar.md5 file and i have done this with odin and received a pass at the top left of the odin program and then it reboots the galaxy gear. i then install the null_16 file on the root of the sd card directory with wondershare mobilego (left zipped as noted in several videos i have watched) after this i remove device from charging device and this is when i try to go to recovery modeto install. after getting to recovery and holding power button for approximately 3 seconds and release this is when it reboots and has reset itself. any help would greatly be appreciated and yes it is rooted with supersu. I am sure i am doing something wrong but not sure what.
ernie36564 said:
i have attempted several times now to install the null_16 on my galaxy gear. after each time i attempt to go into the recovery mode to actually install it, it reboots and resets the device. i have read numerous times to flash the null_03_TWRP2.7.tar.md5 file and i have done this with odin and received a pass at the top left of the odin program and then it reboots the galaxy gear. i then install the null_16 file on the root of the sd card directory with wondershare mobilego (left zipped as noted in several videos i have watched) after this i remove device from charging device and this is when i try to go to recovery modeto install. after getting to recovery and holding power button for approximately 3 seconds and release this is when it reboots and has reset itself. any help would greatly be appreciated and yes it is rooted with supersu. I am sure i am doing something wrong but not sure what.
Click to expand...
Click to collapse
Read.
ernie36564 said:
i have attempted several times now to install the null_16 on my galaxy gear. after each time i attempt to go into the recovery mode to actually install it, it reboots and resets the device. i have read numerous times to flash the null_03_TWRP2.7.tar.md5 file and i have done this with odin and received a pass at the top left of the odin program and then it reboots the galaxy gear. i then install the null_16 file on the root of the sd card directory with wondershare mobilego (left zipped as noted in several videos i have watched) after this i remove device from charging device and this is when i try to go to recovery modeto install. after getting to recovery and holding power button for approximately 3 seconds and release this is when it reboots and has reset itself. any help would greatly be appreciated and yes it is rooted with supersu. I am sure i am doing something wrong but not sure what.
Click to expand...
Click to collapse
Download mk7 for your country.... I don't care if you are already on it just do it! Flash with Odin then flash twrp recovery..... Use adb to boot to recovery....... Trust me it works!
Sent from my Note 3 SM-N900A rooted by Designgears
OMG i got it running!
thanks so much for all the work done with this rom... Everything seems to be running perfect...
At first i couldn't get it to flash properly... I was trying everything. Took hours to initially get the recovery going. It ended up being a driver issue and after a lot of reading and troubleshooting i was finally able to get it up and running.
One question that i have that i couldn't find the answer too... Is there any way to have the watch widget (either the stock clocks or watch styler) appear as a full screen widget without the launcher or the status bar at the top... yet keep the status bar and launcher on the other pages? I am assuming that i can't do it after reading countless of pages... Because i do like the full screen watch face.
Thanks again for all the hard work!
---------- Post added at 09:05 PM ---------- Previous post was at 09:00 PM ----------
eroracing said:
Download mk7 for your country.... I don't care if you are already on it just do it! Flash with Odin then flash twrp recovery..... Use adb to boot to recovery....... Trust me it works!
Sent from my Note 3 SM-N900A rooted by Designgears
Click to expand...
Click to collapse
I had to follow this step in order to get the recovery to stick. No matter what i did including flashing the stock recovery then flashing twrp i couldnt get it going until i did this:
almulder1092 said:
Installing Null_ TWRP: (Version as of this tutorial is Null_ 03 TWRP)
Thanks to fOmey for this Null_ TWRP
Installing Null_ TWRP:
Preparation:
Download Null_ TWRP - fOmey
READ THE NULL_ TWRP Original Post
Installation:
Put your Gear into Download Mode
Connect your Gear to you PC.
Open Odin
Click on the PDA Button
Locate the Null_ TWRP file and select it. (It should be a .md5 file, if it is zipped, then unzip it)
Press Start
Once it is completed it will reboot the gear.
Null Quote:
If you find the recovery is not sticking & your Gear wipes when attempting to access recovery after flashing, you must root your Gear prior to installing TWRP again & Run the following commands in ADB:
*NOTE* You will gave to accept a supersuser request popup when executing "SU" command
*NOTE 2* Probably a good idea to run this prior to first installation (To save time)
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
ADB stands for Android Debug Bridge
If needed "ADB" can be found here on xda - Thanks to shimp208
.[/CENTER]
Click to expand...
Click to collapse
gypsydigi said:
OMG i got it running!
thanks so much for all the work done with this rom... Everything seems to be running perfect...
At first i couldn't get it to flash properly... I was trying everything. Took hours to initially get the recovery going. It ended up being a driver issue and after a lot of reading and troubleshooting i was finally able to get it up and running.
One question that i have that i couldn't find the answer too... Is there any way to have the watch widget (either the stock clocks or watch styler) appear as a full screen widget without the launcher or the status bar at the top... yet keep the status bar and launcher on the other pages? I am assuming that i can't do it after reading countless of pages... Because i do like the full screen watch face.
Thanks again for all the hard work!
---------- Post added at 09:05 PM ---------- Previous post was at 09:00 PM ----------
I had to follow this step in order to get the recovery to stick. No matter what i did including flashing the stock recovery then flashing twrp i couldnt get it going until i did this:
Click to expand...
Click to collapse
You cannot do what you are asking.... But you can set clock widget. Use Nova settings to hide notification bar, dock and scroll indicators then use gesture and button settings to create gesture to accommodate just about anything! I have swype down to open notification bar..... Swipe up open notification app.... Double tap opens app drawer and 2 finger Swipe up opens my dialer! Just set widget long press and resize to full screen. You may have to adjust colums and rows in Nova settings to accommodate whatever widget you are using in order to center properly. Hope this helps!
Sent from my Note 3 SM-N900A rooted by Designgears
On the newest release (16) there is support for custom boot animation and includes the null boot animation. Is that a part of the aroma installer or is the custom null boot animation a part of the rom that you cannot remove? I'd rather stick with the stock if you don't mind.
in the subsequent posts below, you will find all the info you need for not only the device but the ROMs I have had my hands in.
each person who I pulled the files from will get a thanks in the posts as necessary
NonSense 1.04
Disclamer: these files are meant specifically for the HTC Desire 510. Use these files at your peril, you assume any responsibility for loss or damage that may result from use of these files or procedures. what has been included in this tutorial is for the HTC Desire 510
You have been warned.
note: from now on CRI signifies cricket, and B-S signifies sprint/boost if those signifiers aren't used, it applies to both type of this phone
now to the goodies.....
List of supplies:
1. Phone (HTC Desire 510)
2. USB cord that syncs with the PC
3. USB drivers installed for the phone
4. the zip files from this location. click here
4.1 there are 2 different versions of the same ROM, but the *1.04-lean.zip is US only (refer to changes to see why).
4.2 CRI for cricket/att, B-S for boost/sprint
5. read these instructions completely before attempting
before we get started make sure you have supersu (which can be downloaded from here), and NonSense1.04.zip copied to the root of your external SD card
NETWORK UNLOCK (I.E. switching services)
as this phone is LTE compatible, it takes a SIM card no matter the service to receive calls and data. so it stands to presume all you need to do is network unlock the device (Sprint calls it UICC unlock, others it's the Network Unlock Code)
the phone needs to be network (SIM) unlocked in order to switch it from cricket to sprint, or from sprint to virgin mobile, etc.
to network unlock the phone:
1. make sure you are on stock ROM (the one that came with the phone, not the one listed in this post nor CM)
2. call the respective original service provider of the phone (i.e. cricket, sprint, etc.) and tell them that you are leaving the country (like to Australia) and you want to unlock the SIM so you can use your device for service down there.
2.1 if you bought the phone second-hand or don't have service on it, you will have to find a reputable unlock service online
2.2 for sprint customers, your account HAS to be at least 6 months old before they will give you the UICC(SIM unlock) code
2.3 for boost customers, your account HAS to be at least a year before they will give you the UICC(SIM unlock) code
3. once you have the SIM unlock code, pull battery from phone, remove the original SIM, put your services respective SIM in (i.e. originally a cricket phone now running a T-Mobile SIM), put in battery, boot phone, and enter the unlock code where it asks.
4. once your back into device, you'll notice you will have no data.
4.1 what needs to be done is to program the APN (google will be your best friend here - for example sprint lte apn settings, or T-Mobile lte apn settings).
5. now that you have the APN settings, you can program them into the phone.
5.1 APNs can be found in the device by going to settings, then mobile data, clicking on access point names. in there in the upper right hand corner should be 3 dots that are verticle. click on that and then on new APN.
5.2 add the respective settings, click save and then make sure it has a green dot next to it.
6. sit back and enjoy the fruits of your labor
APNs for this device can only be written once the phone has been UNLOCKED and the original (cricket) service providers SIM is NOT inserted, and your using another service Provider ( sprint, T-Mobile, etc.) SIM.
UNLOCKING BOOTLOADER
1. for the drivers, use the ones contained here in the HTCDrivers.zip and extract them to the desktop
1. extract and use the file contained in adb.zip to flash unlock token
2. follow this tutorial and choose all other supported devicess when it asks about device.
INSTALLING TWRP AND KERNEL
in the adb file you should notice a file called recovery.img. that is TWRP recovery for the device
there is also a file called boot.img. this will allow read/write permissions at the System level once root is obtained
if you have either the sprint, boost or another service provider's variety of this phone, try flashing their respective kernel after you install the ROM or before you root (no guarantees that flashing the respective kernel will work. as I have the cricket variety of this phone, I am only developing for that one)
1. from home screen, go to settings and scroll down to power and then scroll all the to the bottom of that and uncheck "fast boot"
2. shut down phone completely
3. go back into fastboot (vol down + power)
4. Select fastboot from the menu list and press the power button.
5. open command prompt and use the CD command to get it to the root of the adb folder (CD C:/users/sky/desktop/adb).
6. plug in device and wait for it to say fastboot USB
7. type in command prompt "fastboot flash recovery recovery.img' (should complete within 4 seconds)
8. in the same command window type "fastboot flash boot boot.img" (should complete within 4 seconds)
8.1 step 8 can be skipped if your just flashing *NonSense1.04*.zip
9. pull battery once that is completed and put it back in.
10. power device on (skip this step if rooting)
OBTAINING ROOT (can be skipped if installing NonSense1.04 as it's already rooted)
1. re-enter fastboot mode and choose recovery. press power to select it
2. once in recovery select install and go to external SD and select the supersu update package.
3. once selected, you should see a slider on the bottom of the screen that says swipe to confirm. do so
4. once package is installed you should see a button that says reboot device. do so
5. wait for it to fully load
INSTALLING NonSense 1.04
1. re-enter fastboot mode and choose recovery. press power to select it
2. once in recovery select install and go to external SD and select the NonSense1.04.zip.
3. once selected, you should see a slider on the bottom of the screen that says swipe to confirm. do so
3.1 beware, it may take a bit to install. just be patient, it's working.
4. once package is installed you should see a button that says reboot device. do so
5. wait for it to fully load. be forewarned, it may take about 15 minutes to load
CHANGES
CRI versions
1. DEODEXed the ROM
2. added external SD support into the ROM
3. fixed FC on clock app (switched clock/alarm from stock worldclock.apk to AOSP clock)
4. changed bootanimation.zip, boot sound, and stock ringtones and sounds.
5. added more stable kernel to flash file.
6. added Pandora (no-ads vers. 5.5), SpiritUL (FM radio support), Facebook, RootBrowser, Adobe reader, Adobe flash player, and Viper4android (DSP/equalizer)
6.1 all apps that have been listed in 6 can be uninstalled without the need for root
7. root and SU have been added and are up to date in this rom as of 11:45PM MST on 3/1/215
8. added apns-conf.xml from CyanogenMod
9. got native APP2sd support thanks to pattyboi's kernel
B-S versions
1. mostly DEODEXed the ROM
2. fixed FC on clock app (switched clock/alarm from stock worldclock.apk to AOSP clock)
3. changed bootanimation.zip, boot sound, and stock ringtones and sounds.
4. added more stable kernel to flash file.
5. added Pandora (no-ads vers. 5.5), SpiritUL (FM radio support), Facebook, RootBrowser, Adobe reader, Adobe flash player, Wifi Tether, and Viper4android (DSP/equalizer)
5.1 all apps that have been listed in 5 can be uninstalled without the need for root
6. root and SU has been added
*1.04-lean
list of removed apps
1. Dropbox (can be found in playstore)
2. Google plus (can be found in playstore)
3. Hangouts (can be found in playstore)
4. HTC Dot View(can be found in playstore)
5. keyboard language packs for Arabic, Chinese, English UK, French, German, Greek, Italian, Portuguese, Russian, and Spanish (not in play store) if needed, flash language.zip found here
6. VPN dialogs (not in play store) if needed, flash missing.zip found here
7. HTC Zoe (can be found in playstore)
BUGS
CRI versions
1.USB internet pass-through not working
2.WiFi direct (miracast) not working
3. want to get rid of annoying volume too loud warning
B-S versions
1. native hotspot says internet when connected to win 7 machine, but will not allow it to go through. Have included wifi tether as a workaround until the issue can be resolved
THANKS
CRI versions
I thank wolfaas12345 for his awesome tutorial on bootloader unlocking, pattyboi for providing a more stable kernel, and chainfire for providing a great solution to provide the SU binary and app for rooted devices. and of course, CraviingCritic for providing the original ROM in which this wouldn't be possible
B-S versions
I thank wolfaas12345 for his awesome tutorial on bootloader unlocking, pattyboi for providing the current kernel, and chainfire for providing a great solution to provide the SU binary and app for rooted devices. and of course, LarryBoyG for providing the original ROM in which this wouldn't be possible
please feel free to let me know if there's any issues with this release and i will fix them as they are found for now as this device is the one i primarily use as of right now.
I will also be keeping the links updated for as long as I own the device (being that my HTC Desire 510(Cricket) is network unlocked, that may be a long time - or until I get a better device).
UPDATES
for those of you who have downloaded the ROM since first release, I will include an CRI_NSupdate.zip or B-S_NSupdate.zip file found here. it will include the changes I have made to the rom since it's initial upload.
the file by the name of NSupdate.szip will include update that pertain to both the CRI and B-S ROMS
to install the updates, just put the update file onto the root of the SD card, reboot into recovery, choose install, pick the update file, swipe the blue button on the bottom, reboot and enjoy.
EDITING THE BOOTUP
location of files mentioned is in /system/customize/resource
to change boot animation
1. find your favorite boot animation
2. rename it to AIO_bootup.zip
3. copy/move and overwrite the original with a root explorer to /system/customize/resource
to change the boot sound
1. find a sound file you like and want to hear every time the phone boots (can be changed at any time)
2. convert it to wav (the file has to be wav in order for the phone to recognize it)
3. rename it to CRICKET_LOGO_24bit28k_STEREO.wav
4. copy/move and overwrite the original with a root explorer to /system/customize/resource
reboot and enjoy...
THINGS NOTICED WHILE CREATING ROMs
1. both (cricket and boost/sprint) phones are exactly the same except for the boost/sprint ones contain a CDMA chipset.
1.1 the only things I had to change from the cricket rom to the boost rom was apns.xml in framework-res, apns-conf.xml, and the preferred network type in build.prop.
2. all kernels work for both (US) versions
3. the same recovery is used on both (US based) devices
so essentially, if we develop for the boost/sprint version of the device, change a few things, it will be ready to roll for the cricket version as well
TO FIX NATIVE TETHER ON B-S VERSIONS
1. Install Script Manager – SManager app from the Play Store.
2. Open the app and grant it root access when prompted.
3. Now, navigate to /system/etc/init.d and tap “tether” script.
4. Click on SU and Boot (Android skull and gear icons, respectively)
5. Click on Run and Save options.
The issue should be fixed now. Reboot and enjoy!
thanks goes to qwerty6532 and LarryBoyG for the fix. now to add that permanently to the ROMs and then they'll be absolutely stable enough for me to be happy and start working on CM11
CM11
I will be building CM11 for the device for both the cricket and boost models. look for the info here as I update it a I need
****edit**** ok so I figured out some of the issue with CM11 not wanting to install apps. I got the internal memory pulling the 1.1 gbs but now I need to symlink the external memory where it goes.
****edit**** so I have figured out what needs to be done...... the kernel for CM11 needs to be built from the ground, up (or one needs to be built that is compatible with it). i'll upload the current one that fixes the memory error (look in downloads).
reserved
so as i have not been actively developing on the phone i will no longer supply updates. all flash files are up to date as of 8 months ago and should be working with out an issue.
again, reserved
same to you...
This would have to be one of the most comprehensive tutorials I have read. 10 out of 10 and kudos. Pity I have a 64 bit device and can't use most of it lol.
Burtrum57 said:
This would have to be one of the most comprehensive tutorials I have read. 10 out of 10 and kudos. Pity I have a 64 bit device and can't use most of it lol.
Click to expand...
Click to collapse
if I had a 64-bit version for this device, I would have it out as soon as I could. and thanks
Great job. Off and running now
I'm not sure how to add the tether fix to the ROM. Not really a developer more of a tester.. Wish I could get into developing don't really know where to start lol.
If you need any help testing or working on CM11 for Boost shoot me a PM I'd be glad to help
Sent from my 0PCV1 using XDA Free mobile app
Question to you Schizoidd......If I install the new 1.04lean over the previous build, do I still need to flash that update or is is already included in 1.04lean. I already falshed that some time ago when you first put it out, so I'm just not sure if its needed again or not. Thanks bro.
CSP III said:
Question to you Schizoidd......If I install the new 1.04lean over the previous build, do I still need to flash that update or is is already included in 1.04lean. I already falshed that some time ago when you first put it out, so I'm just not sure if its needed again or not. Thanks bro.
Click to expand...
Click to collapse
When you flash the new one, wipe the system partition and then use an explorer to remove v4a from the user apps. Which is located in /data/apps and reboot
qwerty6532 said:
I'm not sure how to add the tether fix to the ROM. Not really a developer more of a tester.. Wish I could get into developing don't really know where to start lol.
If you need any help testing or working on CM11 for Boost shoot me a PM I'd be glad to help
Sent from my 0PCV1 using XDA Free mobile app
Click to expand...
Click to collapse
Well it's added to it. It just needs to be activated for now until I can figure out how to add it to automatically start from the first run of the Sprint/boost ROM
schizoidd said:
When you flash the new one, wipe the system partition and then use an explorer to remove v4a from the user apps. Which is located in /data/apps and reboot
Click to expand...
Click to collapse
Sorry, not following "wipe the system partition" ???
CSP III said:
Sorry, not following "wipe the system partition" ???
Click to expand...
Click to collapse
if you in recovery, go to wipe and then advance wipe and check system. wipe it like u would as if ur doing a factory reset
schizoidd said:
if you in recovery, go to wipe and then advance wipe and check system. wipe it like u would as if ur doing a factory reset
Click to expand...
Click to collapse
Yeah, I figured as much. Should have been clearer with my ? Is that before or after I flash the new lean. I though if I did it after, that it would set me back to square one. As in having to start fresh setting everything up again, which I really dont want to have to do. Apologies for my unclearness.
CSP III said:
Yeah, I figured as much. Should have been clearer with my ? Is that before or after I flash the new lean. I though if I did it after, that it would set me back to square one. As in having to start fresh setting everything up again, which I really dont want to have to do. Apologies for my unclearness.
Click to expand...
Click to collapse
it'll leave ur data alone, just delete the OS. do not touch internal memory, davlik, data, or cache and ur stuff will be safe. I have done it and my stuff is fine
schizoidd said:
it'll leave ur data alone, just delete the OS. do not touch internal memory, davlik, data, or cache and ur stuff will be safe. I have done it and my stuff is fine
Click to expand...
Click to collapse
Right on buddy. I'll take you at your word on it. I've never had to do that before so it naturally made me a little nervous. Not that I couldnt have just restored a backup, but still . Many thanks.
Problems
System UI force closes and power button doesn't turn the screen back on when I flash the latest cricket version.
schizoidd said:
I
for those of you that build the kernels, do you think u can build one that is AOSP and compatible with the device for android 4.4.4?
Click to expand...
Click to collapse
we cant really do a "aosp" kernel because of htc's modifications to the board and pins,and they have their own dtb issues...im 99% sure mine works with android 4.4.x because of larry using it in gpe,just repack the ramdisk the zimage and it should be okay
Bobby060 said:
System UI force closes and power button doesn't turn the screen back on when I flash the latest cricket version.
Click to expand...
Click to collapse
If you're going from bone stock to this, you need to do a factory data reset. Just make ssure you back up your data and use nandroid manager to pull it data back into the new ROM
HuiFei - 2 DIN Pure Android 4.2.2/4.4.2/4.4.4 RK3066/RK3188 Car Stereo Radio Head Unit. KGL/KLD/RM/GS/JY/MD/KYD/BN/HA [ROOTED]
This is a new thread for this car dvd that was first reported on comment #2224 of the AN-21 U thread.
Probably you are here because:
you want to root your unit. Only units with ROMs 4.2.2 can be rooted (see below how). The only way to have a rooted 4.4.x is installing a pre-rooted ROM (see below how)
you have a problem (no internet, no sound, buttons do not work, bad mic quality, rear camera image not showing, door opening not showing, etc.
you want to upgrade your unit to a newer software that has sleep mode, personalized music app, personalized functions, root, xposed, can remap buttons, etc.
All this is covered in this post and most of the problems that you can have are summarized in this post too. Please read this first post before asking. And use the search function of the thread, before asking. Thanks.
TRICKS THAT MIGHT SAVE 1000 QUESTIONS ON THE THREAD
Read below and here for basic questions asked and answered 1000 times.
How to root my unit. Only 4.2.2 can be rooted with an app (see below). To have rooted 4.4x you must install a pre-rooted ROM (see below)
Get sound when in reverse (thanx to @Keylo Lo)
here
Engineering/Factory settings password "126" (thanx to @blankers)
This allows you to change logo, sound volume, SWC codification, etc.
Activate USB debugging --> Go to Factory Settings and enter password "adbon".
System sound is low compared to Radio--> Go to Factory settings and change volume levels
GPS button does not trigger GPS app You need to choose predefined GPS app, in Settings--> GPS
Get Into Recovery
1 Press reset button and power button together
2 After about 5 secs release reset button, but keep pressing power button
3 When booting screen appears release power button.
4 It boots into recovery.
--Update 1-- some units without front USB have a different procedure
Firstly power on the unit and then long press the power button and then reset. Then the unit will get three rings and you loose your hand on the power button and short press the power button again. (thanx @netay)
--Update 2-- some others have this procedure (thanx @R4D3N)
1. Turn off the unit by holding 3-4 sec the power button.
2. Hold the RESET button + POWER button for 5 sec
3. Release the RESET button and keep pressing the POWER button for 2 sec
4. Release the POWER button and wait. The Recovery menu appears.
5. With the Volume knob you can move up/down and long press on Volume/Power button to select the option.
Get Into Bootloader
The process is basically the same, with the difference that you need to have the computer attached to the unit via the front miniUSB (if you do not have a front USB, you will have to ask your seller how to get into bootloader mode)
1- boot the unit as usual.
2- plug the front usb of the unit to your computer usb.
3- Then, push the reset button and the power button at once and keep them pushed. The reset button is the tiny pin next to the mp3 sdcard. The power button is the volume knob. You will hear the power cut throught the speakers.
4- Release reset button and keep power button pushed. Now the unit will reboot. You will see nothing, just a black screen. Do not release the power button yet. Your computer will detect a " new hardware", that is the RolckChip. When you hear the windows noise of new detected hardware, you can release power button. It will automatically install the drivers.
------------------------------------------------------------------------------------------------------------
HOW TO UPGRADE YOUR SYSTEM
BEFORE UPGRADING YOUR UNIT YOU MUST KNOW
MCU your unit, there are many (KGL, KGL1, KGL2, KGL3, KGL4, KGL5, KLD, KLD1, KLD2, JY, GS, KYD, MD, BN, HA, MX), If you install the wrong MCU, you will brick your unit.
To know which one you have. Go to Settings -->About
If still not clear, see: here or here.
If you cannot find it here, it probably means that you are in the wrong thread.
Resolution of your unit. 800x480 or 1024x600. If you install the wrong ROM, you will brick your unit.
Chip of your unit RK3066 or RK3188. It does not really matter, ROMs and MCU are compatible between chips.
IT IS ADVISABLE TO BACKUP YOUR SYSTEM BEFORE PLAYING WITH IT
Upgrading is supposed to be a safe operation, but you never know what can happen. So, before updating make sure that:
1- To backup of your system the easiest way is download nandroid root from google play, and do a nandroid backup with TWRP format). Save it in your external SD.
2- make sure you can enter in bootloader mode (see below how to)
3- it is recommended to backup your apps and data (use titanium from google play). The update will do a factory reset.
FOLLOW THIS TO UPGRADE YOUR ROM AND/OR MCU
0- Do a back up (copy the files somewhere safe) of your internal SD card memory. It will be wiped during the process.
1- Download the ROM (Resolution 1024x600 or 800x480) and MCU (KGL, KLD, JY, GS,RM, MX, BN, HA) for your unit.
ROMs--> repository This will get you a file named update.img. There are different "flavors" of ROMs.
Code:
- [user=853627]@coudu[/user] (rooted, stock). Early v4.0 and v4.1 have some problems.
- [user=3590033]@Malaysk[/user] (rooted, with very useful mods, some come with NEXT launcher)
- [user=6041319]@dsa8310[/user] (rooted, almost stock)
MCUs--> Latest MCUs by Malaysk are here . This will get you a file named mcu.img
2- copy the update.img you have chosen to the root of your GPS card.
3- copy the mcu.img for your specific unit to the root of your GPS card (if you do not want to update mcu.img, you can skip this step)
4- insert back the GPS card to the unit. If no window pops up, reboot the unit. At boot, the presence of update.img will be detected and a pop up window will ask you whether you want to update your unit. It will automatically reboot into recovery mode and update your unit. Once done, remove update.img and mcu.img from the root of the gps card or you will be asked every boot for an update.
5- In some Coudu´s (sd partition of 3Gb) and Malaysk´s ROMs versions, it is necessary to do a factory reset just after the first boot so that everything works properly.
6- If you lost buttons or radio after the upgrade --> Go to Factory settings (password 126) and choose the proper canbus for your car and the radio chipset. You can change boot logo if you want.
* If you get Google services error after upgrading to KitKat see this and this
------------------------------------------------------------------------------------------------------------------
THINGS YOU MAY WONDER BEFORE BUYING A HEADUNIT
Code:
[B]- Boot Up:[/B]: time is around 30s.
[B]- GPS[/B]: GPS positions very fast. TomTom, Navigon, Sygic, and regular off-line GPS work. Navigon and Sygic have some problems with some ROMs
[B]- Stand by mode[/B]: Latest ROMs and MCU have the possibility of choosing stand by mode with various times chosen.
[B]- Radio:[/B] radio stations are saved as frequencies
[B]- Bluetooth contacts:[/B] contacts are saved on the device.
- Works fine with Bose system (Audi)
- Possible ground loop noise that needs some tricks to be removed (see section problems)
- Torque works and can run in parallel with A2DP
- ELM327 works (might need special app like CarService in very weird cases)
- Camera works (might be better to get the one with RK3188 chip)
- There is no automatic brightness control because the unit does not have light sensor, but there are apps that can help
- The touch screen is extremely responsive. It works as good as most phones.
-------------------------------------------------------------------------------------------------------------------
HOW TO ROOT AND INSTALL TWRP
Instructions to get root (thanx to @webdude12)
It only works for Android 4.2.2. If you want to root 4.4.x you need to take apart update.img and inject SuperUser app (this is only for experts as @coudu, @Malaysk, @dsa8310 ). The alternative is to install a 4.4.x pre-rooted image and you do not have to do anything else. See below in HOW TO UPGRADE YOUR UNIT section how to do it.
If you want to root your 4.2.2, download Root Master 2.1.1 here
Code:
1- Install the APK.
2- Make sure you are connected to WiFi and you have an internet connection.
3- Open Root Master (do not upgrade to newer version unless you can read chinese, The newest version has different options, all in chinese. Version 2.1.1 just has a button that says "root".))
4- Press root button
5- Chinese characters will flash across the screen.
6- A second popup box will appear, press the purple button.
The app will automatically install SuperUser.
This program connects to servers oversea sending hardware information. The downloads a script that will attempt to root the device. If the first script fails, it downloads additional ones. Future goal is monitor this communication with a data logger and find which script works, so that a unique program can be written to achieve root.------------------------------------------------------------------------------------------------------------------
How to install TWRP recovery (thanx to Abdul_pt from Freaktab and 1-2-Hak and coudu)
You do not really need to install TWRP unless you wanna mod the rom yourself, if you mod roms you will know that already.
- a.t.m. you need a mouse to use TWRP because touch is not working yet
- if you install TWRP, you will not be able to update the update.img and mcu.img the way it was explained above.
If you still want to install TWRP:
Android 4.2.2 800x480
Download files here
And follow the post by 1-2-Hak
Android 4.4.2 800x480
Follow this: this
TWRP for 1024x600
See this post------------------------------------------------------------------------------------------------------------------
TRICKS AND MODDED APPS THAT DO WONDERS
Install app without adb when regular install does not work
Sometimes the app won't install normally and you need to sideload it.. This means that you need a computer and adb wifi. There is another way with which you won't need a computer. You just need to install a terminal emulator (you need root ).
1- Download the terminal emulator app you prefer
2- Download the app you want to install to /mnt/sdcard
3- Open terminal emulator
4- On the terminal navigate to /mnt/sdcard by typing
Code:
- cd /mnt/sdcard
- su
- pm install "NameOfTheApp".apk
Done, you are app is now installed.
Modified Radio Apps
To install radios you need to copy the app using ESExplorer or Root Explorer straight to /system/app in place of MTCRadio.apk
Radio version 4.2.2 800x480
Blue theme (thanx @1-2-Hak)
Rally style Buttons have been moved and skin changed for a Rally like one.
Forest style. Colors have been changed and frequency name is in big.
Radio version 4.4.4 800x480
Blue tint. Stock radio with big names and all in blue shades.
Red tint
Radio version 4.4.4 (Malaysk v1, aka alive)
1024x600. Has animation, in blue tones
[*]Car Service. Allows to use SWC and buttons with 3rd party apps (Latest Malysk ROMs already include it).
Download here (thanx @@KeiserSozeyFr)
If it does not install, copy directly to /system/app
[*]Microntek HeadUnit Service Latest Malaysk ROMs include it. It allows to use SWC with non native apps. It allows to make calls and send messages from Android part of HU, and to show toasts. You can find it straight on Google Play.
There is a modified version (probably outdated) with early start of services here
[*]Moded Music app. Two versions. One is the original with expanded list, so full names can be seen, and the other one has the list integrated in the background so it is always visible.
http://forum.xda-developers.com/showpost.php?p=53352994&postcount=894 (thanx to @dark alex)
anoher one here
[*]Set Loud Latest ROMs do no need it.
Method 1:
Just install this app: http://forum.xda-developers.com/showpost.php?p=53463910&postcount=963 (thanx to @dark alex)Method 2:
You need Tasker or Automagic or similar app.
Set up a task that runs at boot with the following code as "shell command"
am broadcast -a com.microntek.irkeyDown --ei keyCode 44
How to: http://forum.xda-developers.com/showpost.php?p=53553617&postcount=1058
[*]Speed-sincronized volume increase (AKA GALA)
This app will modify the volume of your unit according to the speed. The amount sensitivity can be adjusted.
http://forum.xda-developers.com/showpost.php?p=53441283&postcount=931 (thanx to @dark alex)
[*]PowerAmp Toast (thanx @agentdr8)
This app will show title/album/album art when tracks change while PowerAmp is in background.
http://forum.xda-developers.com/showpost.php?p=53964813&postcount=1461
[*]Rear Camera without icons (icons were included in the KitKat version 4.4.2) (thanx @typos1 and 4pda.ru guys)
http://forum.xda-developers.com/showpost.php?p=56888840&postcount=5096
[*] KLD Launcher 4.4.2 with bigger date
Launcher see picture
---------------------------------------------------------------------------------------------------------
FILE REPOSITORY, FIRMWARES and MCUs for KGL/KLD/GS/RM/JY/MD
Repository (everything is here, firmware up to date, mcus not so much)
More updated MCUs from @Malaysk & @darkleo --> here
Some of the firmwares are... (list not updated)
Custom KitKat 4.4.2 by 4pad.ru (RK3066)
Coudu's 4.4.4 v4.2 (RK3066) (January 2015 release), see here
- Coudu v4.0 and v4.1 have some problems. v4.2 is good (specially releases 150113 for KLD and 150113 for KGL). You might need MTCControlSettings.apk as in these latest releases coudu removed it.
Malaysk's roms (RK3066) w/ and w/o NEXT launcher, also 4.4.4 here
JY Android version is this one
Malaysk's roms (RK3066) version 24/05/15 Download here. It allows the remapping of the radio buttons.
dsa8310 JY rooted ROM 150513 (RK3188) Download here
-------------------------------------------------------------------------------------------------------------------------------
WIKI-Page
Basic info on everything
Another wiki with general info here-------------------------------------------------------------------------------------------------------------------------------
PROBLEMS AND SOLUTIONS FOUND BY THE USERS
Unfortunately the first issues with the promising unit arrived.
@webdude12 got a black screen while driving due to a broken clip (see attachment to figure out which one). One solution is to glue the clip so that it does not get loose. Not doing that can end up in major problems.
Unit might not boot on very hot conditions as it has a thermostate to avoid possible problems. It will work normally when cooled down.
Some apps do not show completely in the screen due to the low resolution.
However, there's a great solutions for that:
- you need root
- install xposed framework (google it)
- probably you need to sideload the apk with ADB as the unit refuses to install it normally.
- install "app settings" module in xposed framework (you can change dpi for individual apps and make them fit in the screen)
When add a google account, it doesn't show under accounts
fix --> http://forum.xda-developers.com/showpost.php?p=53809274&postcount=1303
Wifi or buttons do not work after update to 1.86 or 1.99 firmware versions
- This happens because the MCU or kernel of the new version is not adequate for your unit. Luckily MCUs and kernels are mixable for the same unit.
fix --> Install newest firmware with an older MCU in the usual way. Then install the kernel of a version you know used to work.
To install kernel alone --> Here and files needed here.
Kernel install for doomies (with pics): here
No radio reception
fix --> your ground cable might be loose Sold it back. see this and this and this.
SD card unexpectedly removed // USB unexpectedly removed
fix --> Thanx to @ R4D3N here
Mic sound is awful
-- WARNING --
For any unit, before removing the capacitor with the purpose of separating the BT card from the internal mic, you must make sure (with a multimeter) that the capacitor to be cut interconnects the MIC entry of the BT card with the internal mic. Please note that the capacitor is on the motherboard in the immediate vicinity of the (vertical) BT card (pics on fix for JY units can help you)
fix for JY units --> http://forum.xda-developers.com/showpost.php?p=57982083&postcount=7036
fix for KGL units --> http://forum.xda-developers.com/showpost.php?p=55775852&postcount=3982 and http://forum.xda-developers.com/showpost.php?p=55769511&postcount=3964
fix for KLD units --> http://forum.xda-developers.com/showpost.php?p=56529110&postcount=4592
Bluetooth modules not pairing
fix --> http://forum.xda-developers.com/showpost.php?p=56450438&postcount=4544
Google service error after upgrading to KitKat 4.4.2
fix --> http://forum.xda-developers.com/showpost.php?p=56791126&postcount=4866
and --> http://forum.xda-developers.com/showpost.php?p=56793317&postcount=4925
Wrong door being shown open. Only VW and KitKat 4.4.2
fix --> Go to factory settings, change "Rude"
TomTom not working on KK 4.4.*
fix --> http://forum.xda-developers.com/showpost.php?p=56991862&postcount=5336
--WARNING-- if you installed chainfire SuperSU you have to slightly modify install-recovery.sh. You must substitute /system/xbin/su --daemon & --> /system/xbin/daemonsu --auto-daemon &
TomTom bundle: use maps stored on external SD// Update TomTom maps with map share free// Early start of softwares// SWC from boot/install-recovery.sh
see --> this (thanx to @dsa8310 WARNING: see post #10440 and comments therein when using install-recovery.sh)
summary of early start services commands --> here
Sygic not installing
see --> http://forum.xda-developers.com/showpost.php?p=58983985&postcount=9020
3G USB Dongle not working properly
Probably is due to the USB is underpowered. Use a (externally) powered USB hub. Or follow this how to to power the USBs of your unit.
how to --> http://forum.xda-developers.com/showpost.php?p=58949495&postcount=8949
short version-->http://forum.xda-developers.com/showpost.php?p=58970437&postcount=8983
the following 2-3 pages contain comments about that mod worth reading.
see --> http://forum.xda-developers.com/showpost.php?p=58249825&postcount=7614
Another how to for external powered USB hub--> http://forum.xda-developers.com/showpost.php?p=58979534&postcount=9011
3G connection lost after some drive
see --> http://forum.xda-developers.com/showpost.php?p=58539736&postcount=8162
and --> http://forum.xda-developers.com/showpost.php?p=58982926&postcount=9017
DVR camera not recording or stopping - DailyRoads Voyager app
see --> http://forum.xda-developers.com/showpost.php?p=58648519&postcount=8383
also --> http://forum.xda-developers.com/showpost.php?p=58977534&postcount=9007
Viper4Android not working properly
Check this and look for Viper4Android config here
When I try to install an app, I cannot tap the "install" button
This happens because you are using a screen dimmer. It is a protection function. Just temporarily disable screen dimmer app and you will be able to install the app.
Radio does not show proper pty
Download this modified version (it is v 4.2.2) of RadioMTC
Start apps while booting, you need install-recovery.sh script (included in latest Malaysk ROM)
Read this post to understand how it works. If PowerAmp is auto starting at everyboot, see this
Improve Radio quality by replacing hardware parts. Thanks to 4pda.ru
see --> http://forum.xda-developers.com/showpost.php?p=60895894&postcount=12932
and http://forum.xda-developers.com/showpost.php?p=60896400&postcount=12936
Remap radio buttons. Thanks to 4pda.ru and agentdr8
see -->http://forum.xda-developers.com/showpost.php?p=60941619&postcount=13030
Upgrade RK3066 to RK3188 (needs hardware replacement)
see --> http://forum.xda-developers.com/showpost.php?p=60972222&postcount=13086
or this --> http://forum.xda-developers.com/showpost.php?p=62832292&postcount=18752
Replace damaged touch screen
tutorial --> http://forum.xda-developers.com/showpost.php?p=62832292&postcount=18752
I did not want to create a thread for this but I think it is best kept here then so if anyone want's to copy my signature to add aome links to the other sections here is it for you convenience:
Code:
MTCB Android Headunits: [*URL="http://forum.xda-developers.com/android-auto/mtcb-android-head-units-qa"]Questions & Answers[/URL] | [*URL="http://forum.xda-developers.com/android-auto/mtcb-android-head-unit-general"]General[/URL] | [*URL="http://forum.xda-developers.com/android-auto/mtcb-hardware-development"]Hardware-Dev[/URL] | [*URL="http://forum.xda-developers.com/android-auto/mtcb-software-development"]Software-Dev[/URL]
"MTCB" covers Klyde, HuiFei (KGL), Joyous (Joying is reseller), GS, Eonon and many more vendors. Please check Settings->About tablet -> MCU Version. If it starts with "MTCB-" you are right in above forums.
Please remove the asterisks (*) - That looks like this:
MTCB Android Headunits: Questions & Answers | General | Hardware-Dev | Software-Dev
"MTCB" covers Klyde, HuiFei (KGL), Joyous (Joying is reseller), GS, Eonon and many more vendors. Please check Settings->About tablet -> MCU Version. If it starts with "MTCB-" you are right in above forums.
Click to expand...
Click to collapse
Updated version of this ROM: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]G930TUVU4CRI2
ROM last updated: 10/30/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This ROM is a complete rewrite of my ROM [ROM][TMOBILE][S7_SM-G930T][Oreo Rooted] That ROM doesnt have WifiCalling & I couldn't get it to work for the life of me, so I rewrote it. I started with stock, and slowly stepped back making changes, reinstalling each time, confirming it still worked. About 200 installs later & 1000s of changes, this is the result. Yes, it took a LONG time. Hope you enjoy it! Don't forget to say Thanks so I know it is actually helpful to others, and continue doing this!
Description:
Stock Tmobile Oreo 8.0 modified (G930TUVU4CRF1)
EXTREMELY debloated! Nearly bare minimum, while still retaining hardware functionality. Eg, Samsung Gallery & Camera exist so we get 4k recording, and there aren't errors when we pull up the Gallery to edit, etc. Yes, this means NO Samsung or Android Pay. There could be more apps to debloat but Im out of time for now! (Please provide suggestions if interested)
Everything possible I replace Samsung with Google
Solid ROM. It was actually kind of slow for me, but I'm curious how this works for others.
Xposed is part of the guide, which will give you infinite customization & tweak-ability
If you hate Samsung SW and just want a solid working ROM with very few install options to get you up and running this is for you.
This will delete all of your data on the phone! (Not external SD card) This is the only way so don't ask. Backup your data!
Features:
Tmobile Wifi Calling works, along with Visual Voicemail & Mobile Hotspot
Many Aroma Installer app options
(Optional) KevinsFavorites option in Aroma. I'm not sure I'd recommend it due to my tastes. If you're looking for some good common apps tho, it includes: Amazon, AmazonMusic, AquaMail, Gmail, GoogleDrive, GoogleKeep, GooglePhoto, Hangouts, IFTTT, Pandora, RootBrowserClassic, TitaniumBackup, Uber, & Wink (If you install these and want to remove them later, use TitaniumBackup (or similiar) to uninstall
Root Features: See Downloads->Recommended Root Zip & say Thanks!
Debloated
De-Knoxed
Decrypted /data/ partition
OTAs disabled
Speed & Build Prop Tweaks
Dual speaker
Ruthless Launcher
Apps
AdAway
AOD Clock Face Themes
CPUSpy
DisableService
Kernel Adiutor
Samsung Video Editor and Trimmer
Xposed
Many more...
Download Links:
Base.7z & Oreo_Kevin71246Modded_v3.#.#.zip
Installation:
This will delete all of your data! If you continue, you acknowledge that the Author is NOT responsible for anything that happens to your phone!
Summary (for Pros)
Flash Oreo stock
Root
Flashfire
Oreo_Kevin71246Modded_v3.1.##, Auto-mount, Mount /system read/write Option
Go through Aroma setup. When finished, it should boot to Recovery (if not do this). Do a "Wipe data/factory reset"->Reboot
Detailed Steps
Install Stock Oreo:
Download mode & Setup
Make sure you have latest device drivers setup on your PC
Enable USB Debugging on phone in Developer Settings
Boot phone into Download Mode:
Turn off your device
Press and hold Volume Down + Home + Power button
When you see the warning screen, release buttons & press Vol UP. Phone should say "Downloading..."
Download and unzip Base.7z to PC (This contains stock Oreo, ODIN, & root)
ODIN
Open ODIN on PC (\Base\Odin_313.exe)
Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
Select AP, BL, CP and CSC files from the \Oreo_Stock\Base\ folder for corresponding files
Select HERO2QLTE_USA_VZW.pit
Select Start
Finished: Phone will reboot & show Carrier screen for 3-5mins. Wait until Setup screen & go through quickly (bare minimum) since you'll wipe it again. Once in Android, go to Settings->Display->Screen resolution->WQHD->Apply
Root Instructions: (+Flashfire, SuperSU)
Reboot phone into Download mode
Odin
AP: Select \Base\Root\AP_SM_G930_OREO_ENG_BOOT.tar
Start-> Wait for phone to boot to Android OS
Root
Double-click \Base\Root\cmd-here.exe & Type: root.bat [enter]
Option: 1 (Install Root No tweaks) (Or pick whatever you want)
*Note: With this system root, do not update su binary. Disable notifications for SuperSU app. Don't flash any superuser zips in recovery that are not made by jrkruse
Install Custom Hybrid ROM & Xposed
Download & copy Oreo_Kevin71246Modded_v##.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash Zip or OTA->Oreo_Kevin71246Modded_v#, Auto-mount, Mount /system read/write Option->Check mark
Click Lighting bolt at bottom-> OK
Phone will reboot to Aroma. Go through setup. (See above for what's in KevinsFavorites)
When finished, allow Aroma to exit.
It should reboot into Recovery (If not, do this: immediately hold Vol-Up btn+Home btn until you see recovery on screen. If you missed it, try again: hold Vol-Down+Pwr btn ~10sec until phone restarts & immediately hold Vol-Up btn+Home btn until you see recovery on screen.)
In recovery: Factory Reset->Yes->Restart phone
*Wait 5-10min on loading screens
Go thru Android setup. Ignore "Xposed Installer has stopped" error
Followup-Steps:
Set Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Recommendations:
Xposed
Setup Xposed: Xposed Installer app:Install framework option & restart phone
Xposed Installer app: Settings button (3 lines)->Download->Search "GravityBox [O]"->Click it->Versions tab->Download->Install->Back arrow (upper left)->Settings->Modules->Check box next to GravityBox [O]->Restart phone
GravityBox [O] Tweaks: (Open GravityBox app)
Battery indicator: Statusbar tweaks->Battery settings->Turn on Master switch->Battery indicatory style: None->Battery percent text...->Back
Clock: Statusbar tweaks->Clock settings->Turn on Master switch->Center clock...
Firefds Kit [O] Tweaks: (Install same way as Gravity box)
This is a supplement to Gravitybox. Things of note: Advanced power menu, call recording, & disable bluetooth toggle popup, etc
Known Issues:
Visual Voicemail may fail to register, but restart phone and give it a few hours. It works eventually.
RCS (Rich Communication Services/AdvancedMessages/Chat) texts don't show up in Android Messages & Textra, etc apps (This is an issue on stock as well!!)
Fix: (Use Samsung Messages)
How to Install Samsung Messages via ADB (Easiest way though is just reinstall!):
Download Messaging_SEP81.zip, unzip, & manually copy apk to phone via usb/Windows My Computer
adb shell (Get into shell to run beow commands)
su (Run as root)
mount -o rw,remount /system (Mount system read/write since default it read-only)
chmod 755 /system/priv-app/Messaging_SEP81 (Set permissions on folder)
chmod -R 644 /system/priv-app/Messaging_SEP81 (Set permissions on apk file)
ls -l /system/priv-app/Messaging_SEP81 (Check permissions - Should be: -rw-r--r-- 1 root root - not sure what 1 & 2 is)
ls -l /system/priv-app | grep "Messaging" (Check permissions - Should be: drwxr-xr-x 2 root root)
reboot (Reboot device)
Changelog:
Version 3.1.32: First stable build
Ver 3.1.36:
-Disabled encryption on /data/ partition to resolve "Bluetooth paired devices deleted after reboot" issue & so mods play nicer with ROM
-Fixed "Device not supported" error on Google Phone app
Ver 3.1.37:
-Added most of the apps I replaced or added as options in Aroma Installer now
Credits:
- @jrkruse & @klabit87 for Root
- @partcyborg for helping jrkruse
- @jrkruse for his similar ROMs as guides & help
- @Lanc-City for assistance in ROM modding
- @gustco for eng boot.img
- @Raymonf for modified odin
- @amarullz for Aroma Installer
- @Chainfire for FlashFire & SuperSU
- @rovo89 for Xposed
- @JaeKar99 for the cool & colorful boot animation
- @mrRobinson for AdAway ADAway.org
- Brandon Valosek for CPUSpy
- WangQi for DisableService
- Willi Ye for Kernel Adiutor
- @shubby for Ruthless Launcher
- @Craz Basics for Dual Speaker Mod
...
- Please PM me if you were forgotten!
Some screenies:
Saved2
Saved3
Well nice job!
jrkruse said:
Well nice job!
Click to expand...
Click to collapse
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
kevin71246 said:
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
Click to expand...
Click to collapse
Is this Ufirm firmware?
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
I have so many FW packages on my PC at this point, from so many places that I used while trying to get this to work, but I think it might be a package from one of your threads(?) Since I'm not exactly sure what you're asking regarding "Ufirm FW", I'll elaborate hoping that answers your question. (Tho I'm thinking you mean the U variation/unlocked. So based on these stock files below I guess the answer is no.) If you're question is really, "is it possible to get tmobile wifi calling to work on a U model #", then I'd have to really think about that. But at this point I don't have an answer. I can tell you a million dependencies about it tho! (I seriously have hundreds of revisions I made while testing, & notes. The symbolic & meta links in Aroma initially broke it, as I found out after a week or so of testing - wish I knew a bit more about them, and why they're all there, then I'd know what was wrong about them...)
High-level process:
1)Flash Base/Stock/Oreo Rom:
- AP_G930TUVU4CRF1.tar
- BL_G930TUVU4CRF1.tar
- CP_G930TUVU4CRF1.tar
- CSC_TMB_G930TTMB4CRF1.tar
- HEROQLTE_USA_VZW.pit
2)Root with your method
3)Flash Xposed framework & my ROM (it's a "start with stock then remove what we don't want" type of Aroma/Edify script)
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
kevin71246 said:
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
Click to expand...
Click to collapse
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
It works perfectly!!
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
charredchar said:
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
Click to expand...
Click to collapse
I believe I know what the issue is, I'm testing a fix (for THIS ROM) as we speak. Stay tuned. Maybe tomorrow if I have time and it works I'll update the OP. BTW, this ROM and my other ROM are TOTALLY different. Thanks for the feedback!
FranMLG said:
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
Click to expand...
Click to collapse
What do you mean by this? "but if you do not pull them, let me know"
And tell me more about Viper4Android, and if it works solid for you on this ROM...then I'll consider adding it. Thanks!
New version, see change log in OP for details.
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
jrkruse said:
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
Click to expand...
Click to collapse
Hi, why you have to flash this - HEROQLTE_USA_VZW.pit on 930t, is it ROM specified? if I do and don't then what are pro and cons?
---------- Post added at 01:36 PM ---------- Previous post was at 01:26 PM ----------
josh2020glacier said:
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
Click to expand...
Click to collapse
since bootloader is locked you can't use TWRP so you have to use Flashfire to install this ROM, as you know flashfire required root so you have to setup the base per OP and then root the base then install the ROM and then root it again, read the first page I don't think you will get a instructions more detailed then his
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Alkan3 said:
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Click to expand...
Click to collapse
Nauseating rainbow? LOL. Sorry. This is much more of a general question though, that wouldn't exactly pertain to this ROM specifically. And given I don't have an answer, I'd try searching BootAnimation How-Tos to get this customized. The ONLY thing I did regarding this was replaced the existing files with the rainbow ones. That's it. Apologies in advance.
Just discovered an issue: RCS (Rich Communication Services / Chat) texts don't show up in Android Messages app. See "Known Issues" in OP for a solution. BTW I posted a new ROM version a few days back that allows many choices in Aroma Installer. Make sure to pick Samsung Messages (instead of Google), so you get RCS chat text messages!
Warning: Don't install an older OS on top of a newer one, you may have a very high chance of bricking your phone. If you are ready to take risk of bricking for the sake downgrading / requirement or already bricked, then only attempt the following . you need an autoloader & build version exactly matching to your phone.
I have downgraded successfully from Build ABP244 (Android 8.1.0) to AAX862 ( Android 7.1.1)
Caution: Blackberry/Google may introduce any constraints against downgrade through future OTA updates to strengthen the security etc.
My Phone Details:
BlackBerry, Keyone, Special Edition, Dual Sim, India.
PRD: PRD-63764-001 (Group: KEYone BBB100-7)
OS Build: ABP244 (Android 8.1.0)
[Upgrade history from ABB216 (android 7.1.1) to ABG076 (Android 8.1.0 ) ….to…to ABP244(Android 8.1.0 )]
1. I have checked phone PRD, by typing the following code into the phone dialer:
*#2886#
Clicked on "MANU"
Clicked on "Traceability"
There you can see phone's manufacturer no: Mine is PRD-63764-007 (for example) (photo#1 in attachment)
Exited from the menu click "PASS"
Then again clicked "PASS"
At the end of the menu clicked "exit"
2. compared with PRDs master at https://tclota.birth-online.de/ and download suitable Autoloader (ROM and its flasher)
3. AAX862 (it is written as AAX863 but actually AAX862) which is suitable to above PRD No is downloaded from
https://androidfilehost.com/?fid=890129502657599708
Topic: https://forums.crackberry.com/blackberry-keyone-f445/blackberry-keyone-autoloaders-1108372/
4. Removed passwords /patterns / finger prints from screen lock (settings>security>screen lock>select none), Removed google account [ settings>Users & Accounts (or Accounts in case of android 7.1.1 ) >googel>options>Remove, remove google]
[removed find my device at device administrator , find from Google Account (settings> google> google account >options (3 horizontal line at rhs bottom)>manage devices>black berry keyone>remove>remove- i have done but this may not be needed]
Theory: On BlackBerry devices powered by Android, Factory Reset Protection (FRP) is enabled by default to reduce the value of a stolen device. This feature prevents the use of a BlackBerry device powered by Android unless authorized by the known user.
Once you sign in with a Google account, FRP is enabled. Once enabled, only users who have reset their device via Settings > Backup & reset > Factory data reset may proceed through the setup wizard without being prompted to enter the Google login information that was previously used on the device before resetting. This form of reset is the only reset flow that is considered trusted.)
[I have reset the device from Android (I have done, but this may not be needed]
[Enabled Developer options and usb debugging was made on (I have done, but this may not be needed)]
5. Rebooted to fastboot mode by switching off >pressed and held volume down button and simultaneously , pressed power button till the phone restarts , then released volume down, once fastboot loads
[>select fastboot by pressing volume button , I have done, but this may not be needed (no further power button press)]
(photo#2 in attachment)
6. Installed BlackBerry-USBDrivers-5.0.0.2 downloaded from the link below for windows and restarted the windows.
Downloaded from https://swdownloads.blackberry.com/Downloads/entry.do?code=4EE0932F46276313B51570F46266A608
7. Connected it to Windows PC through USB port (Windows device manager photo#3 in attachment)
8. Extracted AAX862Universal.7z with 7z
9. Browsed to the above extracted folder, double clicked on file flashall.bat to run batch file (other option available is flashallnowipe.bat ).
10. Entered y in response to question …….. to continue (y/n), (photo#4 in attachment)
it immediately rebooted to fastboot again (photo#5 in attachment) but the process was going smooth.
Process successfully completed (photo#6 in attachment) and phone is rebooted to OS in Auto
Sometimes, the phone can get stuck when booting for the first time. If this happens to you, make sure you've waited long enough, and then just hold the power button down to force a reboot.
It needs simcard or internet to reach user interface.
Caution:
When Autoloader build no AAY819 (common/universal to many PRDs but not all) downloaded from https://mega.nz/#!wVxBxYZA!BahovAZA_...M5Ic_QkJigS3LI and flashed, flashing is successful but when is updated from App Drawer >updates…22 mb downloaded , install started , rebooted and installed to 100% but message appeared that “ This is embarrassing, the update failed, try to install again later, your phone will reboot after 120 sec…. Error code 3305” , It reboots and build no shows as ABB216 but 2nd Sim is not working.
Reflashed with Build No AAX862, both sims and other hardware are working normal , Further when update option is used it is getting updated to ABB216 without any error again both sims and other hardware are working normal .
Stop updates
(this facility not available in Oreo)
Pre requisite : disconnect phone from Internet (Put off Wifi and mobile data)
1). App drawer>Updates>Options(3 vertical dots)>settings>system> check for updates –Off (=never), Automatically download – off (=ask to download)
2). App drawer>Updates>Options(3 vertical dots)>settings>System applications > Automatically update –off (=never), new app notifications –off
If system update already started or pre -requisite is forgot: Go to Settings>Apps>Updates>Storage>clear data , now repeat step 1 & 2
Advantages:
1) The feel, the look , the smoothness , the speed , low in bugs of the build ABB216. It is excellent
2) “True phone dialer & contacts” app has all most all the features, you ask it has already has, like blue mark for outgoing calls, green for incoming, saffron for canceled, red for missed call as history (it cannot work properly with Oreo latest due to restriction on call log, restrictions increased in ascending order from Build ABG076 to ABJ879 to ABM376 to ABP244 ). Never hangs while calling (OS).It has contact share through SMS with pleasant interface, excellent dual sim management etc.
3) SMS Organizer by Microsoft also appears to be facing restrictions with Android 8.1.1 , hence it will be working excellently.
4) Rear camera (of Build ABB216)a lot nearer to true to actual ( than Oreo Build ABG076)
5) Light Manager works flawless with very low power consumption for customization of notification LED as keyone has no built in facility to customize.
Disadvantages:
1) less secured than Oreo,
2) 7.1.1 Camera not far better than improved camera by build ABP244.
3) Oreo has configurable alarms but same is achieved in Nougat with updating of Time App
4) Oreo has PIP useful e.g. for maps
5) Google playstore installs regular patches without our control making older android slow
6) call history symbols are rarely used and minor , further they can be seen at stock phone (the issue still exist with Oreo compatible TruePhone v1.78) advantage 2 may be considered almost nullified
7) file Explorer scrolling goes back if some shaking taking place.
8) Download is interrupted few times from playstore even when Download from mobile data
9) usb data transfer is slow
10) all features of Silence premium do not disturb app are not working ( my favourite profiles app ) like whitelist and repeat calls will enable ring, interruptions to silence mode (app is defective up to v 2.15f ) but they have created v2.17 which works as designed but does not install on nougat.
11) Light flow can be installed in place of Light Manager on Oreo , hence advantage 5 nullified
However I am happy with downgrade and will maintain as long as possible or till I get apps to get the nougat like flexibility and user experience as per above mentioned facts at advantages.
Thanks to the respective contributors& community. This is only experience sharing , no credit or responsibility.
As the time progressed, disadvantages increased and advantages reduced . I have re-upgraded please on 22.12.19 especially due to functional requirement of Silence Premium as mentioned above and no equivalent is available.
@knreddy, good work, please do you know if this exact firmware will work on the sprint variant of the keyone?