Hi everyone, I hope this is an ok place for this post.
I am shortly getting a new Android based head unit for my car, it's a PX6 based unit though I don't know the specific details as I don't have it yet.
I'm familiar with changing ROMs like hot dinners when I used to use Android phones, but can someone explain the basics of why these custom ROMs on the forums exist?
I am currently working on a better front end for the head unit to suit the car, simply using Nova and KLWP to do what I need, but is there any benefit to having a custom ROM, will it make the interface better or anything like that?
Basically just looking to understand what they offer over what's installed as standard (assuming I create my own front end on the default software).
Same goes with the MCU upgrades, I assume they will already work well with the car in terms of integration and so on with buttons etc. What does the MCU upgrade do and why do people do it?
Hope that's not too much to ask, just looking for a simple summary
Thank
I would recommend getting the head unit and install it in your car first. See what works to your liking and what does not. Maybe you will find that it works well enough with the factory ROM and MCU that comes on it and not need any updates right away. It is not recommended to update either unless you know for sure that the update you're applying specifically fixes an issue you have with your head unit.
Quite honestly when you start updating the ROM and MCU, you run the risk of getting more problems than fixes and/or feature. Also I would suggest giving the factory ROM a chance before trying any of the custom ROMs like Hal9k and/or Malaysk.
I guess a lot of it comes to what your expectations are and how you plan to use the head unit.
jlbooth said:
I would recommend getting the head unit and install it in your car first. See what works to your liking and what does not. Maybe you will find that it works well enough with the factory ROM and MCU that comes on it and not need any updates right away. It is not recommended to update either unless you know for sure that the update you're applying specifically fixes an issue you have with your head unit.
Quite honestly when you start updating the ROM and MCU, you run the risk of getting more problems than fixes and/or feature. Also I would suggest giving the factory ROM a chance before trying any of the custom ROMs like Hal9k and/or Malaysk.
I guess a lot of it comes to what your expectations are and how you plan to use the head unit.
Click to expand...
Click to collapse
I guess I want to know what, apart from fixing problems, do the custom ROMs offer? Is there anything extra or is it just a better more streamlined and bloat free install?
To be honest, all I want my unit to do is display a nice front end, which as I've said I will make with Nova and KLWP (I assume that will work ok on a stock ROM), and then to open the apps that I will hard code for my use in the interface, things like radio, nav, maps, Spotify etc, but most importantly I'll be using it to launch the CarPlay app (ZLINK) as that will be where I spend most time
If you plan to use ZLink most of the time, you may find that the stock ROM suits your needs. I use ZLink most of the time for wireless AA. And yes you will be able to install Nova on the head unit. I like Car Launcher Pro pretty well.
Just FYI, I've asked the forum moderator to move this thread to MTCD Head Units Q&A as the discussion has nothing to do with software development.
jlbooth said:
If you plan to use ZLink most of the time, you may find that the stock ROM suits your needs. I use ZLink most of the time for wireless AA. And yes you will be able to install Nova on the head unit. I like Car Launcher Pro pretty well.
Just FYI, I've asked the forum moderator to move this thread to MTCD Head Units Q&A as the discussion has nothing to do with software development.
Click to expand...
Click to collapse
Thanks, it sounds like I will be ok then at least to start with.
I've read somewhere that if using third party launchers that you lose access to some native apps like radio and so on. is that true?
That is not true (at least not with my head unit - PX6 SYGAV/DASAITA unit for 2015-2017 Toyota Camry). The stock radio app shows up just like any other app in the custom launcher app drawer.
Regarding what you get with custom ROMs, you may get more frequent updates, usually rooted, and sometimes better control over when apps get closed and stuff like that.
Again I think it kind of depends on how you plan to use the head unit. Try not let "FOMO (Fear of Missing Out)" drive your decision to switch to a custom ROM. Not saying they're bad or not useful. It all depends on what the expectations are and how the head unit is going to be used.
Custom ROMS are actually Modded Roms/APKs, no one has access to the source on these typically chinese origin devices.
marchnz said:
Custom ROMS are actually Modded Roms/APKs, no one has access to the source on these typically chinese origin devices.
Click to expand...
Click to collapse
got that, but do I need access to the source ifs just want to use it as standard with my own front end and it works ok?
@dchuraman , as an end user of stock OR custom ROM you would not need access to the source to accomplish what you want to do.
Basically the custom ROMs originate from a stock ROM in binary form and the applications contained in the ROM are customized mostly in ways that even the custom ROM developer does not need the actual source code to make changes (just one example - changing visual resources in the contained applications).
Again that sounds like something that would be way outside the scope of what you are wanting to accomplish with your head unit.
One additional thought regarding ZLink. The app will automatically launch the moment your phone connects to the head unit Bluetooth, so you might not be using the ZLink shortcut all that often. You will need the shortcut like if you leave CarPlay to adjust sound settings like equalizer, but for normal usage, you should not need the ZLink shortcut very often. Also once ZLink launches and it gets connection to your phone, it automatically brings up CarPlay without any action on your part.
ZLink will also launch if you connect a USB cable between the head unit and your phone (assuming you're not using wireless CarPlay).
I'll explain why.
MTCE/D ROMs are fairly swappable and there's not much difference in them.. that's where the Custom ROMs come in. They come with fixes for the bugs in the "official" roms, they come with root and things like Vipe4Android and/or Xposed which haven't been easy to implement on these Rockchip devices. They also extend the support for these devices. Hal9k Mod v5, you not only have Magisk installed but you can actually update it now. Before, it would result in a bootloop 99% of the time. It's a fairly "Golden Age." There is now a root method to install SU then Magisk on most Android 10 ROMs(thanks to @AlFerro) but the Hal9K Mod allows for even more customization and like I said, he tries to fix any bugs in the normal roms when he makes his mod. Malaysk is similar but I don't have as much to say since I'm not as versed in using it.
As for MCU updates, think of them similar to BIOS updates. They effect some compatibility with ROMs but mostly control the Canbus/"Stereo" part of things. MCU is what makes the Android system communicate with the "stereo" part of the system. Otherwise, it'd just be a android tablet wired into the speakers (poorly).
**Don't confuse this with needing to upgrading the MCU every update by a manufacturer. Manufacturers don't always release updates that are compatible with older units, especially in the cheaper ones. Check to see if the ROM works first on the MCU you're on, if it doesn't work then try to update the MCU
Thanks all, it sounds like I probably don't need to run a custom rom, but one question. My unit hasn't arrived yet but in screenshots I see this top navigation bar in all apps, and therefore reducing the useable screen real estate. Is there a way to get rid of that and the floating home button?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Depending on which launcher you use, there may be an option to hide the status bar using the launcher settings.
The floating help button should have options to to tell it to not show. Otherwise you may be able to simply disable the app for the floating home button. Typically the Joying branded units have that floating home button and should have an option to disable.
dchuraman said:
Thanks all, it sounds like I probably don't need to run a custom rom, but one question. My unit hasn't arrived yet but in screenshots I see this top navigation bar in all apps, and therefore reducing the useable screen real estate. Is there a way to get rid of that and the floating home button?
View attachment 5399509
Click to expand...
Click to collapse
Best find out what device you own first.
Not an MTCD/E/P device, so you've posted in the wrong forum.
Android-headunits is where you will find FYT or TS10 info.
marchnz said:
Best find out what device you own first.
Not an MTCD/E/P device, so you've posted in the wrong forum.
Android-headunits is where you will find FYT or TS10 info.
Click to expand...
Click to collapse
How can you tell it's not a MTCx device?
You can find out if the head unit is MTCD/E from the system about page. This detail is important especially if you are considering installing a custom ROM. Based on the screenshot you provided before, I would venture say that the head unit that you have ordered is not MTCD/E head unit.
Why is this important? Malaysk and Hal9k custom ROMs are for MTCD/E head units and would not be compatible with your head unit if not MTCD/E. You could brick or damage your head unit if you attempted to load up a custom ROM that is not compatible.
I am going to request the moderator move this thread to Android Head Units.
No I get that what type of unit it is is important I just want to know how that was established from the screenshot.
I thought all PX5/6 units were MTCx
Might not always be the case. Best way to find out is to post a screen shot of the system about page. Quite honestly, regardless of whether your head unit is MTCD/E or not, you created a new thread for your discussion which makes it easy for the moderator to move the whole thread if indeed it is not MTCD/E.
dchuraman said:
No I get that what type of unit it is is important I just want to know how that was established from the screenshot.
I thought all PX5/6 units were MTCx
Click to expand...
Click to collapse
It may have been inferred a little bit (maybe by me mentioning Joying) and the fact that it was never really established whether MTCD/E in the discussion. When the discussion was started, it was indicated you had not received your head unit yet. So it would have been difficult for you to say one way or the other. I just wanted to make sure you were aware of the difference and perhaps reduce the potential of damaging your system.
As previously stated, if perhaps your system is not MTCD/E then this whole thread could easily be moved to the correct forum by the moderator.
Related
The first custom ROM for the Epic is now live! See this thread for details.
So a friend of mine got his hands on one of these, and since he asked me about flashing Gapps into the device, I was wondering if any one of you guys have been doing something just as "epic" for this children's tablet. And yes, I started this thread as a sort-of sequel/follow-up to the VTech Innotab Max thread I posted a year ago.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TECH SPECS:
Display: 7-inch capacitive touchscreen with TN LCD display
Resolution: 1024x600
Operating System: Based on Android 4.4 (modified, of course)
Processor: Quad-core, 1.3 GHz (reported by CPU-Z as MediaTek MT8127)
Memory: 1GB RAM
Storage: 16GB; 9GB available for /sdcard partition
Micro SD Card Slot: Yes, expandable up to 32GB
Camera - Rear: 2MP
Camera - Front: 2MP
Audio: 3.5mm stereo jack with microphone
Wireless: Wi-Fi 802.11 b/g/n
Bluetooth: Bluetooth 4.0
Battery Type: Rechargeable lithium-ion
Battery Life: 6+ hours; results will vary based on usage and settings
Port: Micro USB
Sensor(s): Accelerometer
Much to my disappointment, LeapFrog didn't equip the tablet with a GPS module, and despite the potential privacy issues that may arise with including one, it could be legitimately used for certain applications like tracking the device or your son or daughter in case he/she gets lost. The usual backdoor leading to Developer Options is also disabled for some reason, though it can still be accessed through third-party utilities such as this. And maybe it's just my modded Epic, but beaming stuff from another device to an Epic using ShareIT appears to suffer from connection issues, i.e. the device is detected but the sender is unable to connect to it; a workaround for this would be sending a file or two from the Epic and then having the sender do the same from his/her device.
APKs from outside sources can be installed either through ADB or by downloading it on your device and installing as usual, not to mention that there's a semi-hidden feature (tucked away under the Parental Controls panel) that allows for the Amazon AppStore to be loaded. As for rooting, Kingoroot should do the trick from what I've read here, but you can manually install SuperSU on it if you prefer the more established root access app. ADB-wise, the latest debug and fastboot binaries should work on the device from what I can attest.
Oh, and here's a link to the Antutu test results:
http://our.antutu.net/api/?action=v5&act=benchmark&id=54239552
CPU-Z report:
Kernel sources:
Code:
https://www.dropbox.com/s/vo6u4s6b3shjrhb/epic.iso?dl=0
https://github.com/huckleberrypie/android_kernel_quanta_narnia
Mad props to RAMChYLD for volunteering to have the sources mailed to him, as I'm reluctant to have them mail the goods to me no thanks to the rather abysmal postal service here in my place.
Pre-rooted ROM dump courtesy of @epic__fail; This can only be flashed with an unlocked bootloader.
Code:
http://www.needrom.com/download/leapfrog-epic-v1-stock-rom/
Note that while the unsigned ROMs cannot be flashed directly using SP Flash Tool, you can get around this by using the hidden Write Memory option. A quick guide on how to do that can be found on page 12.
Signed ROM dumps. Can be flashed directly using SP Flash Tool v5.1744. Make sure to perform a full backup of the tablet before flashing!
Code:
Epic Academy Edition:
v1.1.95: https://androidfilehost.com/?fid=6006931924117902657
v1.8.160: https://androidfilehost.com/?fid=6006931924117908682
v1.8.804: https://androidfilehost.com/?fid=4349826312261819358
LeapPad Academy:
v1.1.171: https://androidfilehost.com/?fid=4349826312261738402
P.S.: If you're getting a signature error upon flashing, try unticking SEC_RO and then try again.
Official flashable ZIP files:
Code:
Regular:
http://lfcdownload.leapfrog.com/epic/en/KOT49H.user.1.0.124.20150709.140831-to-KOT49H.user.1.5.45.20160310.231145.zip
http://lfcdownload.leapfrog.com/epic/en/KOT49H.user.1.1.146.20150825.120621-to-KOT49H.user.1.5.45.20160310.231145.zip
http://lfcdownload.leapfrog.com/epic/en/KOT49H.user.1.2.90.20150924.150837-to-KOT49H.user.1.5.45.20160310.231145.zip
http://lfcdownload.leapfrog.com/epic/en/KOT49H.user.1.3.27.20151026.144847-to-KOT49H.user.1.5.45.20160310.231145.zip
Academy Edition:
Latest Version: "KOT49H.user.1.1.95.20171215.140555"
KOT49H.user.1.1.52.20170522.123745
URL: http://lfcdownload.leapfrog.com/epic/en/v2/KOT49H.user.1.1.52.20170522.123745_to_KOT49H.user.1.1.95.20171215.140555.zip
Patch notes: This is an incremental update from KOT49H.user.1.1.52.20170522.123745 to KOT49H.user.1.1.95.20171215.140555
KOT49H.user.1.1.62.20170627.010228
URL: http://lfcdownload.leapfrog.com/epic/en/v2/KOT49H.user.1.1.62.20170627.010228_to_KOT49H.user.1.1.95.20171215.140555.zip
Patch notes: This is an incremental update from KOT49H.user.1.1.62.20170627.010228 to KOT49H.user.1.1.95.20171215.140555
KOT49H.user.1.1.64.20170704.010259
URL: http://lfcdownload.leapfrog.com/epic/en/v2/KOT49H.user.1.1.64.20170704.010259_to_KOT49H.user.1.1.95.20171215.140555.zip
Patch notes: This is an incremental update from KOT49H.user.1.1.64.20170704.010259 to KOT49H.user.1.1.95.20171215.140555
KOT49H.user.1.1.66.20170712.151925
URL: http://lfcdownload.leapfrog.com/epic/en/v2/KOT49H.user.1.1.66.20170712.151925_to_KOT49H.user.1.1.95.20171215.140555.zip
Patch notes: This is an incremental update from KOT49H.user.1.1.66.20170712.151925 to KOT49H.user.1.1.95.20171215.140555
JSON files for the updater:
Regular:
http://lfcdownload.leapfrog.com/epic/en/NarniaSystemUpdateVersions1.json
Academy:
http://lfcdownload.leapfrog.com/epic/en/NarniaSystemUpdateVersions_epic2.json
LeapPad Academy:
http://lfcdownload.leapfrog.com/epic/en/NarniaSystemUpdateVersions_epic3.json
The above ZIPs are incremental patches used to update an existing system to a newer build; I couldn't seem to dig up a full system image, let alone a scatter file, for a bricked or bootlooping Epic to be restored back to factory condition though, but still I'm keeping this as a reference in case any one of you guys is interested in downloading them manually. Apparently "KOT49H.user.1.1.99.20150807.173011" is unique to demo units, hence why there weren't any updates available for my device when I ran the OTA utility.
Demo-to-retail conversion tutorial
A tutorial on how to convert a store demo unit into a fully-functional Epic can be found here:
https://huckleberrypie57.blogspot.com/2018/12/and-i-came-in-for-another-leapfrog-epic.html
Custom ROMs
Unofficial LineageOS 14.1 by mac2612, blakegriplingph and kai2000: https://forum.xda-developers.com/android/development/rom-lineageos-14-1-leapfrog-epic-t4161311
The modifications to the way locale is set means that Bluetooth HID like keyboards can pair but cannot work since it cannot be set to be used for input (the options to change or add keyboard layouts is disabled in the Android settings screen and instead is selected from LeapFrog's own screen which divides the world into 7 regions- US, UK, Canada, Australia, New Zealand, Ireland and Other. When you pick Other it forces the UK keyboard and locale on you, which is ridiculous since some countries uses varying combinations of either (for example, Philippines uses US English 100%, while Malaysia uses UK English but US Keyboard). However bluetooth does work with A2DP devices.
Yeah, the CPU-Z and AnTuTu benchmark are my doing. I am the friend Blake mentioned. I should add that the device ran the Project Anarchy demo in AnTuTu somewhat well, averaging at 15fps.
MTK's spec sheet mentions that the SoC also has GPS and FM Radio, but I suspect that both are disconnected on the device since Android doesn't detect them.
The option to enable installation of packages from untrusted sources is still in the android security screen in settings tho, and you will be instructed to turn it on as part of the steps to install the Amazon AppStore.
I actually emailed LeapFrog as to whether they can release a tarball to the MTK kernel sources they used, and I'm keeping my fingers crossed but since they had a history of doing so in compliance with the GPL (c.f. the links to Didj/Leapster sources on eLinux provided by none other than LF themselves), I have high hopes for custom ROM development or at least some mods for the device.
Well, my only problem with the device is that the input method and locale selection is locked down and selected by the "Device Locale" screen, instead of allowing the much more granular selection allowed from the Android settings screen itself. I have determined that the same lockdown prevents bluetooth keyboards from pairing properly with the device. Also, several apps defaulted to downloading videos from UK servers instead (ie BabyFirst TV, Fisher-Price Puppy Player and Little People Player) and thus have what I perceive as "wrong voices".
I'm still waiting for LeapFrog's reply concerning the kernel sources, and if all goes well we'll be golden.
Good luck.
Well, drat. Leapfrog's asking me for a mailing address so they can send me the source CDs. Problem is I am wary of the postal servce here at my place, so is there anyone who's willing to get the sources?
So I bought one of these leap pad epics. Got it at toys r us. It was a return so open box. They gave it to me for $70 (they retail for $169.99+tax) because the last person who owned it left their passcode on it. I can't figure out how to get it off. Any ideas??
Hang in there. I've contacted Leapfrog via Facebook and am awaiting a reply.
RAMChYLD said:
Hang in there. I've contacted Leapfrog via Facebook and am awaiting a reply.
Click to expand...
Click to collapse
Wouldn't doing the standard factory reset procedure be enough for that (as with those who ended up flinging way too many patterns on their device), or is there anything special that's needed to be done?
Okay, got a reply. Go into the parent screen to bring up the pin entry, then enter 4 1 9. Now, when your cursor is in the last textbox, hit the backspace and enter 2 7. Apparently this is a hidden backdoor that Leapfrog puts into the system for cases like these (ie improper returns).
I've tested it, entering 4 1 2 7 upfront doesn't work. It has to be 4 1 9 <backspace> 2 7.
As for doing a factory reset, well, It's a catch 22 situation- to get into the settings screen, you need to enter the password first - they actually modified the settings app. If you don't have the password, well, you're SOL unless you call Leapfrog support, who will probably give you this code anyway. If the ADB interface is up, you could probably do it from there, but I'm not sure if it is.
Hmm, now I'm wondering if there's someone who's up to doing an SP Flash Tool dump of the device.
Good news: RAMChYLD just got his hands on the source tarball, and as such he gave me a link to the ISO containing the kernel sources, ripped off the disc LeapFrog mailed to him recently:
Said link to the sources can be found on the first post, in case you guys are interested.
Actually, Blake did the bulk of the work, talking to Leapfrog and arranging the CD to be sent to me. But yeah.
RAMChYLD said:
Actually, Blake did the bulk of the work, talking to Leapfrog and arranging the CD to be sent to me. But yeah.
Click to expand...
Click to collapse
Yup, pretty much. Though to tell you one thing, I was a bit worried that the sources either wouldn't arrive in time or not at all.
RAMChYLD said:
As for doing a factory reset, well, It's a catch 22 situation- to get into the settings screen, you need to enter the password first - they actually modified the settings app. If you don't have the password, well, you're SOL unless you call Leapfrog support, who will probably give you this code anyway. If the ADB interface is up, you could probably do it from there, but I'm not sure if it is.
Click to expand...
Click to collapse
You can factory reset by holding down Power + Volume Up at boot.
Is any one of you guys here interested?
I will be. I'll be buying my son one this weekend.
alienundies said:
I will be. I'll be buying my son one this weekend.
Click to expand...
Click to collapse
If you could provide an SP Flash Tool dump of the stock ROM it'll be golden., along with a TWRP/Clockwork recovery image. I really wish that I could get my hands on one, but the local Toys R Us here sells it for like twice the price even though it's just some glorified MediaTek device made with children in mind.
XbooX08 said:
You can factory reset by holding down Power + Volume Up at boot.
Click to expand...
Click to collapse
Does that work? They even went as far as to disable the ability to screenshot with power + volume down until I installed an app to re-enable it.
blakegriplingph said:
If you could provide an SP Flash Tool dump of the stock ROM it'll be golden., along with a TWRP/Clockwork recovery image. I really wish that I could get my hands on one, but the local Toys R Us here sells it for like twice the price even though it's just some glorified MediaTek device made with children in mind.
Click to expand...
Click to collapse
+1. The Asian importers for the device are charging way more for it over here than the device sell for in the US. It's going for an insane RM1000 at Toys R Us and Hamleys here. Which imo is ridiculous given that there are vendors selling (malware-laden) Chinese tablets for less than a fifth of that.
Update 2021-05-14:
A new version, a bit of cross-promotion for annother variant (USB DAB modules) - and some interesting new insights ...
I have managed to build a new app with the same UI concept, but this time for USB DAB receivers. I know there is already the excellent DAB-Z, and I want in no way compete with it.
I just like simplicity; that's why I transferred the UI part of the "old" app to the one for USB.
In the process, I also added some improvements to this one, so there is a version "2.0.0" now.
To help with future updates and statistics, I published it on Google Play:
DAB+ Radio for Klyde Headunit - Apps on Google Play
Control serial DAB+ module by Klyde - only for special hardware, NOT for USB !!
play.google.com
Changes included against the old version here:
- Some UI changes, nothing fundamental
- Now up to three text chunks are displayed, eliminating the frequent change
- Station lists are ordered alphabetically
We are MONO !!
At some point I realized that there was definitely no Stereo audio when listening on the DAB+ app. First I suspected misconfiguration, maybe the wrong MCU firmware. However there were no changes, whatever I tried. What's suspicious though is that there is signal on both speakers. That implies that the distribution to both channels must be done deliberately at some point, else only one speaker would get a signal.
Anyway, for the new development, I pulled the headunit out of the car and set it on my desk. This allowed me to run hands-on experiments. And voilà: I managed to stick some thin cables into the output plug of the module - and got regular Stereo sound out of it immediately!
It turned out the cable of one of those channels was CUT right before the HU plug !!!
It seems that there was a lack of pins in that plug/socket, so only one channel goes into the HU and is obviously routed to both speakers internally ...
<To be continued >
----------------------------
Original post:
With my new headunit (PX5 Oreo from Autojeta, based on Klyde KD-7602), I had ordered an external DAB+ module which is connected with a proprietary cable to the rear socket panel. It has a serial control connection, power and likely a TOS audio wire.
The app for operating the module which was offered for download is incomplete, to say the least. Presets weren't working at all, it was not even possible to save any.
So I did a bit of re-engineering and built a DAB+ controller how I imagined it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changes against the original:
- Many, total rewrite
- Infotext is complete (the last character was always missing before)
- New layout, eye- and finger-friendly
- No more ugly images and buttons
- Plenty of room for long infotexts
- Presets are working
- Setup window for less-used options
- Unnecessary permissions and resources removed
- German translation included
Update 2019-01-30:
- extended compatibility down to Android KitKat (4.4)
- empty preset entries can be clicked anywhere to set; no need to hit the edit button
- attempt to make layout independent from resolution
If anybody is interested, I can provide the "strings" files so that more translations are possible.
Enjoy!
Current version: 1.2 (obsolete, see 2.0.x on Google Play)
JFDee said:
With my new headunit (PX5 Oreo from Autojeta), I had ordered an external DAB+ module which is connected with a proprietary cable to the rear socket panel. It has a serial control connection, power and likely a TOS audio wire.
The app for operating the module which was offered for download is incomplete, to say the least. Presets weren't working at all, it was not even possible to save any.
So I did a bit of re-engineering and built a DAB+ controller how I imagined it.
View attachment 4657027
Changes against the original:
- Many, total rewrite
- Infotext is complete (the last character was always missing before)
- New layout, eye- and finger-friendly
- No more ugly images and buttons
- Plenty of room for long infotexts
- Presets are working
- Setup window for less-used options
- Unnecessary permissions and resources removed
- German translation included
If anybody is interested, I can provide the "strings" files so that more translations are possible.
Enjoy!
Download: View attachment 4657026
.
Click to expand...
Click to collapse
Great work, plays nice
JFDee said:
With my new headunit (PX5 Oreo from Autojeta), I had ordered an external DAB+ module which is connected with a proprietary cable to the rear socket panel. It has a serial control connection, power and likely a TOS audio wire.
The app for operating the module which was offered for download is incomplete, to say the least. Presets weren't working at all, it was not even possible to save any.
So I did a bit of re-engineering and built a DAB+ controller how I imagined it.
View attachment 4657027
Changes against the original:
- Many, total rewrite
- Infotext is complete (the last character was always missing before)
- New layout, eye- and finger-friendly
- No more ugly images and buttons
- Plenty of room for long infotexts
- Presets are working
- Setup window for less-used options
- Unnecessary permissions and resources removed
- German translation included
If anybody is interested, I can provide the "strings" files so that more translations are possible.
Enjoy!
Download: View attachment 4657026
.
Click to expand...
Click to collapse
Nice work. It is compatible also with the USB receiver version ?
royalhawk2002 said:
Nice work. It is compatible also with the USB receiver version ?
Click to expand...
Click to collapse
No, I don't have such a device.
This version is hard-wired to use /dev/ttyV3, a serial port that is related to the firmware. It will only communicate if "com.microntek.CarManager" is instantiated in the Java code.
I suspect that the USB version may be very similar though. Can you point to an app that DOES work with it? I could have a look.
.
@JFDee
It seems well done, congratulations!
can you enter the link to buy that form dab?
* I do not want to occupy my usb sockets.
P.S. does anyone know a dab module that fuses with an external antenna and has better reception?
* because with the internal adhesive antenna I do not feel well, in fact I have mounted it on a truck and often happens to have to replace the glass, due to small scratches, which would not allow to pass the review ... with the adhesive antenna I would have to replace the antenna every time ... for now I stuck it with transparent scotch but it is quite disgusting and also the reception is poor.
JFDee said:
No, I don't have such a device.
This version is hard-wired to use /dev/ttyV3, a serial port that is related to the firmware. It will only communicate if "com.microntek.CarManager" is instantiated in the Java code.
I suspect that the USB version may be very similar though. Can you point to an app that DOES work with it? I could have a look.
.
Click to expand...
Click to collapse
you can take a look to dab-z from realzouzu...here on the forum
Inviato dal mio SM-N960F utilizzando Tapatalk
fur0n said:
can you enter the link to buy that form dab?
* I do not want to occupy my usb sockets.
Click to expand...
Click to collapse
Here are two links:
https://www.aliexpress.com/item/KLY...ouch-Control-For-Android-6-0/32848949738.html
https://www.aliexpress.com/item/Ext...l-For-Android-Car-DVD-Player/32826477767.html
However, you need the matching socket at the rear of the HU. On the photo, it's the 6-pin socket below the hole named IPOD.
.
.
Great job; finally klyde dab work very good...
if you could add station logos it would be great
pakoner said:
if you could add station logos it would be great
Click to expand...
Click to collapse
I can't say if the DAB+ module can provide these. It's basically a "black box" that accepts serial control commands and returns station parameters and infotext updates. The sound seems to come out as a digital stream over some of the cables in the proprietary connector.
So far, I'm using the unchanged control commands from the original program because there is no documentation of what they do. It's obvious which ones start the station scan or change the station, but there may be others that provide further functions.
The module inside the housing is a shielded circuit, which I suspect can be found in many car and stationary radios. It says SHINWA on the shield.
Edit: This is the module in the box:
http://www.shinwa.com.cn/product/meBroadcast/backdab/DB-MF03.html
I'm sure the documentation of the commands is available for purchase ...
.
Parsing Problems
Thanks for your work,but I can't install your dab. apk.file.Message is : parsing problem .I have a mtcb unit with the latest malaysk Android rk3188 4.4.4 800x480 rom.At the moment,i have the same DAB + reciever like you,working with the redesigned dab+ app of Oberbergler.Any idea?
Strike03 said:
apk.file.Message is : parsing problem .I have a mtcb unit with the latest malaysk Android rk3188 4.4.4 800x480 rom.
Click to expand...
Click to collapse
I only tested with Android 8 here. I will test again in an emulator with Android 4.4.
JFDee said:
I only tested with Android 8 here. I will test again in an emulator with Android 4.4.
Click to expand...
Click to collapse
This would be very kind,thank you.I hate the normal interface and your one looks very good.
JFDee said:
Here are two links:
https://www.aliexpress.com/item/KLY...ouch-Control-For-Android-6-0/32848949738.html
https://www.aliexpress.com/item/Ext...l-For-Android-Car-DVD-Player/32826477767.html
However, you need the matching socket at the rear of the HU. On the photo, it's the 6-pin socket below the hole named IPOD.
.
View attachment 4661961
.
Click to expand...
Click to collapse
M8 great work you did here.
I own a pumpkin 8core android 8 mtcd KLD so i suppose it's same klyde like yours and then the rear serial interface must work right?
Lol I will not tell anything if it doesn't work but seems to me it will work... I attach a rear image of Myne where i see that plug
BlueChris said:
I own a pumpkin 8core android 8 mtcd KLD so i suppose it's same klyde like yours and then the rear serial interface must work right?
Click to expand...
Click to collapse
I don't see why it shouldn't. The hardware layout looks identical.
The app also works fine with Hal9k.
Strike03 said:
Thanks for your work,but I can't install your dab. apk.file.Message is : parsing problem .I have a mtcb unit with the latest malaysk Android rk3188 4.4.4 800x480 rom.
Click to expand...
Click to collapse
The app was definitely not compatible with KitKat. I have changed that so it should at least install and open.
I'm not sure it will fully work as I can test for Kitkat only on an emulator. Also, I did not check the layout for issues on 800x480 yet.
If you get any layout distortion, it would be helpful if you could post a screenshot.
Edit: just did annother update after streamlining and testing the layout on 800x480.
See top post for the update.
.
JFDee said:
The app was definitely not compatible with KitKat. I have changed that so it should at least install and open.
I'm not sure it will fully work as I can test for Kitkat only on an emulator. Also, I did not check the layout for issues on 800x480 yet.
If you get any layout distortion, it would be helpful if you could post a screenshot.
Edit: just did annother update after streamlining and testing the layout on 800x480.
See top post for the update.
.
Click to expand...
Click to collapse
Thank you very much for your work.
Installing was no problem with your updated app and layout with 800x480 looks very good. But it´s stuck in initialization mode.If i press a button, nothing happens or it shuts down.
https://www.bilder-upload.eu/bild-b1849c-1548867502.jpg.html
https://www.bilder-upload.eu/bild-2c1fe9-1548868034.jpg.html
Strike03 said:
it´s stuck in initialization mode.If i press a button, nothing happens or it shuts down.
Click to expand...
Click to collapse
The hardware setup is probably different from the one used in the MTCD version.
Do you have an "official" app that works, at least with selecting channels?
JFDee said:
The hardware setup is probably different from the one used in the MTCD version.
Do you have an "official" app that works, at least with selecting channels?
Click to expand...
Click to collapse
I use the app of Oberbergler and in former times the one of treibstoff. Both work, but the layout of your one looks better.
Here is the link of the mtcb software section with the working dab APP 1.5 Modded apk.You have written there about your new designed app some days ago.
https://forum.xda-developers.com/an...development/klyde-dab-app-1-5-modded-t3484902
Strike03 said:
Here is the link of the mtcb software section with the working dab APP 1.5 Modded apk.
Click to expand...
Click to collapse
Thanks, got it. The appearance of the original ('official') app seems to be identical to mine, but something inside must be different.
I will reverse engineer that app. Please stand by ...
.
JFDee said:
I will reverse engineer that app. Please stand by ...
.
Click to expand...
Click to collapse
Ok:good:
I made the title as self descriptive as possible. Im a huge anonimity nerd and i debloated my android to my style (Samsung Galaxy A32 5g) since there was no compatibility for Lineage or /e/OS in it. In doing so, i retain pretty much all i want, however one of the weird functions that doens't work as well as it used to is the GPS. I'm pretty sure what i did was disable an APK that uses the phone reception to track location, since when i enable GPS i can still get my location with amazing accuracy, however it takes several minutes (and i mean SEVERAL) after being turned on to track where i am, and in other apps it does not track at all.
The issue is that im an Uber Eats worker (not exactly, but similar style of work) and resetting the phone to factory would mean to debloat all over again.
So, does anyone knows more or less which APKs specifically interact between location and other apps to know which one to enable again?
Might be easier if you listed what you removed.
Dependencies...
blackhawk said:
Might be easier if you listed what you removed.
Dependencies...
Click to expand...
Click to collapse
The issue is that i've removed quite a number of things across several days and didn't realize that my GPS wasn't working snap-fast as it was before very much late.
hahaNSAgoBRRRR said:
The issue is that i've removed quite a number of things across several days and didn't realize that my GPS wasn't working snap-fast as it was before very much late.
Click to expand...
Click to collapse
Off the top of my head I no clue which apk(s) do that. The apk names can be misleading.
Many of the smaller apks just sit there unless needed.
Especially on Samsung's you can really screw up functionality by disabling blindly, worse it may net near zero performance/increased battery life.
One reason I use a package disabler is mistakes are easy to correct when experimenting with minimum consequences.
Someone here likely does know so keep trying. If that model has it's own section on XDA, post a thread there.
It may be one of these although likely not the last one...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
blackhawk said:
Off the top of my head I no clue which apk(s) do that. The apk names can be misleading.
Many of the smaller apks just sit there unless needed.
Especially on Samsung's you can really screw up functionality by disabling blindly, worse it may net near zero performance/increased battery life.
One reason I use a package disabler is mistakes are easy to correct when experimenting with minimum consequences.
Someone here likely does know so keep trying. If that model has it's own section on XDA, post a thread there.
It may be one of these although likely not the last one...
View attachment 5467967
Click to expand...
Click to collapse
Afraid it wasn't any of them, but thanks, im gonna look around.
hahaNSAgoBRRRR said:
Afraid it wasn't any of them, but thanks, im gonna look around.
Click to expand...
Click to collapse
MDM App might be needed... best to not disable this probably.
blackhawk said:
MDM App might be needed... best to not disable this probably.
Click to expand...
Click to collapse
Afraid it didn't made a difference. Another weird issue i got however i think this is more of my android config is that after a while with the phone locked whatsapp closes and im not being sent any notifications until i unlock it and open it again. Do you suspect of any apk that need to be on to run the app or what setting could have messed that? I set the phone to never optimize battery and to not turn off data when locked and to not restrict it on whatsapp yet i still randomly open it to find several messages from hours ago that i never got notified for.
Ditch WhatsApp; trashware/malware.
Reload and start from the beginning.
blackhawk said:
Ditch WhatsApp; trashware/malware.
Reload and start from the beginning.
Click to expand...
Click to collapse
God i wish i could delete whatsapp but i live in one of those countries where everyone and everything uses it.
As for reloading from the start, i've been thinking about it, but it took so much to delete so much bloat that i'd rather first try and see what i could salvage. After all, all the apks that i removed are still existing in the ROM as installers.
Reload, and use this this to at least set it up and determine what's safe to debloat.
If you disabled more than 90 apps, you probably killed more than is needed...
blackhawk said:
Reload, and use this this to at least set it up and determine what's safe to debloat.
If you disabled more than 90 apps, you probably killed more than is needed...
Click to expand...
Click to collapse
Oh, dont worry, i use ADB, although next time i should probably keep in a list what i uninstalled.
hahaNSAgoBRRRR said:
Oh, dont worry, i use ADB, although next time i should probably keep in a list what i uninstalled.
Click to expand...
Click to collapse
Problem being Samsung's are feature packed and many are useful. After 2 years I'm still exploring my N10+.
If you inadvertently kill a parent app all it's children dependencies go nuts. Some apps serve more functions than you'll ever find listed.
With no way to easily renable them... you have no hope of easily discovering them.
To this day I still update and modify my bloat list to make the device more functional and efficient.
Be careful what you kill... especially if you haven't used Samsung's extensively. I have 2 N10+'s, one running on 9, the other 10. The Q variant literally has dozens of small system apks than the P variant. Both devices behave almost identically. These dozens of small apks allow this. They use almost no resources or battery.
The Q variants battery life is the same or better.
Blocking these apks would serve no purpose and likely screw up the newer N10+. It has about 150 more new packages in the Q variant than the P. I used my imported block list from the AT&T P variant for the non carrier Q variant. I took out a few new ones that were bloatware but the disable head count remains similar between both devices.
So don't go too nuts as Samsung has added many new system apks to tone down and make Android 10 and up UI usable, look nice and prevent lose of functionality
blackhawk said:
Problem being Samsung's are feature packed and many are useful. After 2 years I'm still exploring my N10+.
If you inadvertently kill a parent app all it's children dependencies go nuts. Some apps serve more functions than you'll ever find listed.
With no way to easily renable them... you have no hope of easily discovering them.
To this day I still update and modify my bloat list to make the device more functional and efficient.
Be careful what you kill... especially if you haven't used Samsung's extensively. I have 2 N10+'s, one running on 9, the other 10. The Q variant literally has dozens of small system apks than the P variant. Both devices behave almost identically. These dozens of small apks allow this. They use almost no resources or battery.
The Q variants battery life is the same or better.
Blocking these apks would serve no purpose and likely screw up the newer N10+. It has about 150 more new packages in the Q variant than the P. I used my imported block list from the AT&T P variant for the non carrier Q variant. I took out a few new ones that were bloatware but the disable head count remains similar between both devices.
So don't go too nuts as Samsung has added many new system apks to tone down and make Android 10 and up UI usable, look nice and prevent lose of functionality
Click to expand...
Click to collapse
Gotcha, although i've always been one for simplicity and all, to be honest i kinda wish i could just grab a barebones android OS for my phone and modify it from there.
hahaNSAgoBRRRR said:
Gotcha, although i've always been one for simplicity and all, to be honest i kinda wish i could just grab a barebones android OS for my phone and modify it from there.
Click to expand...
Click to collapse
Depending on the model and how much support there is, you can, but it's going to be a time eating gravity well.
It's a lot easier to use stock Samsung's and configure them to suit your needs. Samsung probably has the best launcher out there at least on the N10+.
blackhawk said:
Depending on the model and how much support there is, you can, but it's going to be a time eating gravity well.
It's a lot easier to use stock Samsung's and configure them to suit your needs. Samsung probably has the best launcher out there at least on the N10+.
Click to expand...
Click to collapse
Guess that's what i get for getting a phone a few months in the market.
hahaNSAgoBRRRR said:
Guess that's what i get for getting a phone a few months in the market.
Click to expand...
Click to collapse
Been a bad year for phones and Android.
I spent a -lot- of time dialing in my N10+, but once done it runs great. You need to find the solutions and use work arounds when needed.
Stock Androids are almost impossible to crash. So... play with it.
Just make sure all critical data is redundantly backed up to at least 2 hhds that are physically and electronically isolated from each other and the PC. Do this or eventually you will lose data.
blackhawk said:
Been a bad year for phones and Android.
I spent a -lot- of time dialing in my N10+, but once done it runs great. You need to find the solutions and use work arounds when needed.
Stock Androids are almost impossible to crash. So... play with it.
Just make sure all critical data is redundantly backed up to at least 2 hhds that are physically and electronically isolated from each other and the PC. Do this or eventually you will lose data.
Click to expand...
Click to collapse
I trust you on that! Thanks a lot for your help UH60.
Hi guys, i'm a little confused and between 2 minds on my joying headunit. I've been running the android 10 unit for quite some time now (https://www.joyingauto.com/joying-9...-android-10-0-car-autoradio-ips-1280x720.html) and generally really like the spec, features and responsiveness. However there seems to be a lot of different ways of using it. And i can't quite decide what would be the 'best' way.
1. I can use the unit natively, by installing the apps like waze, spotify, etc directly to the headunits storage and either fitting a 4G data sim
2. I can use the unit natively, by installing the apps like waze, spotify, etc directly to the headunits storage and using my phone as a wifi hotspot and tethering the internet to it to keep everything running natively.
3. I can use Android Auto and mirror my phones apps to the headunit and use it that way.
Just looking for opinions and discussion around how peope are using there's and why? I use mine in configuration 2 above.
As a side note, i'd love to install a custom rom onto the unit rather than use joying's image but can imaging a 100 things would break and that i'd potentially brick the unit by just attempting it. Even their update process seems to be a blog post that says "Here's some links, if you not sure what to use, email us and we'll advise." But i don't trust that i'd get much support with a bricked or dodgy update. Thouhts?
I do 1 and 3 on mine, but with CarPplay.
Reason being: CarPlay nav is more "on the road friendly" in that the UI is designed to be used while moving.
Native functionality is good when I want the unit to do the stuff while I just BlueTooth sound from a different device.
My one issue is that if I have data turned on and enable CarPlay, my phone uses the head unit as a hotspot which isn't ideal.
thestraycat said:
Hi guys, i'm a little confused and between 2 minds on my joying headunit. I've been running the android 10 unit for quite some time now (https://www.joyingauto.com/joying-9...-android-10-0-car-autoradio-ips-1280x720.html) and generally really like the spec, features and responsiveness. However there seems to be a lot of different ways of using it. And i can't quite decide what would be the 'best' way.
1. I can use the unit natively, by installing the apps like waze, spotify, etc directly to the headunits storage and either fitting a 4G data sim
2. I can use the unit natively, by installing the apps like waze, spotify, etc directly to the headunits storage and using my phone as a wifi hotspot and tethering the internet to it to keep everything running natively.
3. I can use Android Auto and mirror my phones apps to the headunit and use it that way.
Just looking for opinions and discussion around how peope are using there's and why? I use mine in configuration 2 above.
As a side note, i'd love to install a custom rom onto the unit rather than use joying's image but can imaging a 100 things would break and that i'd potentially brick the unit by just attempting it. Even their update process seems to be a blog post that says "Here's some links, if you not sure what to use, email us and we'll advise." But i don't trust that i'd get much support with a bricked or dodgy update. Thouhts?
Click to expand...
Click to collapse
I believe you mean FYT UIS7862 based unit. Joying is a made up brand.
3. Pseudo Android Auto- reality is it is a hack that will eventually frustrate as google and phone manufacturer release updates. These units are NOT Android Auto.
Re. Custom ROMs. None exist and are not needed.
System Specs
Baseband Version
FM_Base_18B_W21.12.3|sc9873A_modem|03-24-21 03:14:08
MARLIN3E_TRUNK_W21.13.3|uwe5623_marlin3E_usbhub|03-31-21 01:19:48
Build Number
QP1A.190711.020 release-keys
System Info
App 1280x720 2021-11-10 09:57:06
CPU Info
CPU:UIS8581A Octa-Core [email protected] GB(Memory) + 32GB(Storage)
MCU Version
2021.10.09 10:12:29 YIN_53_L6315_G23P48F64_E60_V:1.0
Bluetooth Version
BLINK_2161_RELEASE/2021:09:14:19:38:05_blink
Hi there, trying to figure out why no sound is made from the head unit OR the phone when connected through bluetooth.....Not running Android Auto (disabled app).
Is there something simple I'm missing? 1st dive into these android head units, Any help is greatly appreciated.
Thank you!
Mekede or Winca or ???
****added hwinfo pics
Only solution I've found is to disable Sounds option in bluetooth access on the phone AUDIO and MESSAGE ACCESS. This at least allows the phone to make it's notification sounds while connected to head unit.....phone calls still get routed to head unit.
Doesn't seem there's any working method to have a notification on screen/with sound with this head unit....for now this will do
Update......it appears setting the unit's bluetooth Version to AVRCP 1.6 (in developer options) allows for app notifications to sound through the head unit.....No on screen toast etc, but I'm happy with the notification alerting audibly
Added info/pics
What unit is this?
What can i do/what can't i do?
Can/how can i root it ?
I've been reading but it is all just a blur of info to me at this point......anyone care to help clear the clouds for me??
Thank you in advice!
Trying to answer a bit of your questions, as notifications via Bluetooth are also a grey area for me.
Your unit has a fyt manufacturer id of 116. That id is used by YIN, NaviFly , Mekede , Prelingcar, Runningway, NIDYGR, Hengcheng, COHO and a number of unbranded units/resellers (and the list grows almost daily on aliexpress). Pick the one you like , but actually it doesn't make a difference. A Mekede firmware (last one 14 March 2023) will do fine.
What notifications do you want?
WhatsApp -> Register your unit under your phone, and it will receive notifications as well. @Clandaries wrote a post about that. See here.
Use the paid version of Tapatalk on your unit and do the same. It can relay multiple notifications.
About rooting: Why do you want to do that? What do you think it will bring?
"What can I do? What can't I do?" Wow! This is really a very broad question which can result in thousands of answers. Tell us what you want. That gives us the option to give you more specific answers.
surfer63 said:
Trying to answer a bit of your questions, as notifications via Bluetooth are also a grey area for me.
Your unit has a fyt manufacturer id of 116. That id is used by YIN, NaviFly , Mekede , Prelingcar, Runningway, NIDYGR, Hengcheng, COHO and a number of unbranded units/resellers (and the list grows almost daily on aliexpress). Pick the one you like , but actually it doesn't make a difference. A Mekede firmware (last one 14 March 2023) will do fine.
What notifications do you want?
WhatsApp -> Register your unit under your phone, and it will receive notifications as well. @Clandaries wrote a post about that. See here.
Use the paid version of Tapatalk on your unit and do the same. It can relay multiple notifications.
About rooting: Why do you want to do that? What do you think it will bring?
"What can I do? What can't I do?" Wow! This is really a very broad question which can result in thousands of answers. Tell us what you want. That gives us the option to give you more specific answers.
Click to expand...
Click to collapse
Thank you for clearing up some questions i had! It really helps me out. As to notifications, mainly it'd be nice to receive sms messages w/pop up on screen (not required, but it would be convenient)
Root, well honestly I'd like to use viper, i see that it's mentioned that it doesn't "work", that's something I'd like to play with (again not a necessity but i use viper on my phone and it makes a huge difference on vs off.
I think however most of what I'd like to do is run through different firmwares , for instance (not sure if available) but I'd like to try different firmwares with different camera apps, for instance current firmware has a Front Camera app....but nothing to manually view the rear cam....i believe, could be wrong, that some firmwares might even have a camera dvr app built in .....features like that which are missing....i tried a 3rd party dvr app from playstore but they all seem tailored to using cellphone cameras so its hit or miss as to if the apps even recognize the cameras......
Had one app that recognized front camera and it would record, but even switching to reverse would stop the recording and not resume.
Most of what I'd like to do may just be out of range of potential for these units....I'm really trying to feel out the limits and expectations.
Thank you 1000 times !!!
I appreciate you taking your time to answer my posts and helping to educate me on these devices.
I'll be reading back and forth through these post until i feel comfortable enough to start tinkering (and grab a factory firmware in case i mess up )
louforgiveno said:
Root, well honestly I'd like to use viper, i see that it's mentioned that it doesn't "work", that's something I'd like to play with (again not a necessity but i use viper on my phone and it makes a huge difference on vs off.
Click to expand...
Click to collapse
Viper might work nicely on a phone without DSP.
However, all these units come with a highly modifiable DSP nowadays. You don't need Viper (from my point of view).
And indeed, to prevent usage of Viper, you can now only use it when rooted.