Related
On the 32 GB:
On this one it downloads the .zip but when I attempt to flash it, it does not do anything; here are the reasons/issues:
*On this one the volume works backwards. That should be the download I made which is an older one.
*I did not partition this tablet because I figured it has the memory to operate properly.
*About tablet:
Android version 4.1.2
Cyanogenmod version: 10-20130418-EXPERIMENTAL-tenderloin-FOR_LIMITED_TESTING_ONLY_CAM
Build: Thu Apr 18 00:04:59 CDT 2013
Memory 864 MB
model no. cm-tenderloin
CPU ARMv7, Processor rev2 (V7l)
*TWRP message: "Root is required for this app" WTH??
*ROM Manager msg:"You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use Google Search on your computer to find instructions to root your phone --->OK.
*SuperUser: I have four logs, 10/3/2013 Voodoo OTA RootKeeper; three are allowed, one is created.
*Voodoo OTA Root Keeper v. 2.0.3
*Checked statuses on this app: Superuser app installed, /system supports root protection.
Hope this information helps, if this causes issues with you guys when it comes to following different solutions I NEED THEM IN A SPECIFIC ORDER (not shouting but stating the obvious) for the flash to function properly on the tablet. I deleted apps and skimmed through the File Manager and deleted unnecessary files but did not touch anything that was downloaded with the Android.
Please please be kind with me! I downloaded with YouTube and my family has enjoyed the tablet tremendously now that it has Android, especially with our Chromecast.
chicawhyte
32 GB Stuck At Order And Flash Selected
UPDATE: 16 GB Updated Successfully! Didn't do anything in particular, it just worked .
Now the 32 GB is stuck on the same spot as before, where it doesn't allow me to flash. Same issues at above. I have combed the threads but I am concerned on what to fix first, in order for the tablet to work smoothly. If you believe I have to flash from the desktop, please let me know.
Thanks,
chicawhyte
Bypassed TWRP Root Message, Read Below
Directory:
TWRP/sdcard/goomgr
It says that it's installing my update plus a new gapps file, I selected:
Backup
Wipe Cache
Wipe Dalvik
I downloaded OpenRecovery--->never ran, it's not inside the GooMgr folder. There's that arrow swipe to unlock, it does not do anything. Left or right, still it says it's downloading both files.
chicawhyte
MODERATOR: Please close this thread
Update:
Roland sent me a message to flash that tablet from my computer then it will fix the issues, and I did. After this happened, Goo.im popped that I had a new OS update, and it flashed on the tablet.
Thanks to Roland for the helpful information. Now both are up to date with the same updates and running smoothly :victory:
chicawhyte
I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!!!
STOCK RELOADED v1 fix 1
Kernel base: stock XXUANC3 (kernel 3.4.0-1131235)
Kernel ramdisk: modded
Features: a few...
Security level: low!
Purpose: giving everyone who loves free exploring of Android secrets and who doesn't consider security as an absolute priority and who wants to put some life in this, indeed, awesome device, a possibility of playing with his device without disturbing restrictions, forced by Samsung, at least until fully-custom kernels, compiled from sources, appear (and that may take some time, as source code available atm seems to be broken, causing all the compiled kernels to stuck at boot screen).
Features working out-of-the-box:
- su binary from SuperSU by Chainfire @ /sbin/su (binary only for scripting purposes! Flash cf-root to use SuperSU app!)
- busybox 1.22.1 binary compiled by Stericson @ /sbin/busybox
- init.d support - just put your favorite scripts into /system/etc/init.d using any file manager and chmod 755 (not 777! it's NOT smart to permit write access for "world" to any system file), chown root:root, they will run on every boot. Well, to be honest, above permissions are given to all the scripts automatically during boot, but it has not yet been tested
- SELinux: Permissive - Samsung's most recent policy of forcing SELinux Enforcing mode by pre-compiling it into a kernel binary part, found in latest KitKat builds since at least a few months, HACKED FOR THE FIRST TIME EVER using innovative method of injecting an information directly into kernel memory space and forcing overwriting potentially-persistent kernel symbol value on-line during boot!)
- unsecure adb access (not tested yet)
- ext4 tweak: 20 sec (instead of stock 5 sec) write commit delay for /data partition (significantly increases IO performance!)
- some further, minor modifications
WARNING!!!
- flashing this WILL undoubtly trip KNOX, avoiding your warranty (which atm cannot be reverted! in any way)
- flashing this WILL cause a warning message of avoided warranty to be displayed on every boot (ofc it disappears right after reverting to stock boot.img)
- flashing this WILL disable some of the very important security features provided with stock firmware!!!! For advanced and experienced users only!!! Use at your own risk!
Known issues:
- AllCast Share mirroring not working (typical for all Samsung devices running not-exactly-stock kernels since S3). WORKING FIX AT POST #16!!!
http://forum.xda-developers.com/showpost.php?p=54516532&postcount=16
Please consider solution from post #3 as not-always-working and depreciated!
Installation:
- compatibile with XXUANC3 firmwares but probably also with other (past and hope future too...) KitKat 4.4.2 Samsung branded firmwares;
- rooting by Chainfire's CF-Root first recommended as it will install SuperSU app in Android (this kernel contains su binary only giving su access without any policy settings!);
- enter download mode and plug the tablet via USB...
- ...select provided file in PDA section (and NOT touch anything except that)...
- ...and flash with Odin in a same way as CF-Root or like anything else...
- enjoy.
DOWNLOAD HERE:
Current version - STOCK RELOADED v1 fix 1
http://www63.zippyshare.com/v/87557346/file.html
FIXED: file name changed so it can be flashed directly by Odin without renaming! Sorry for this silly mistake!
=======
Changelog:
v1 fix1:
- fixed permissive mode due to trivial error;
- delayed init.d execution to a moment AFTER init process set cfq scheduler so it is not overriding mmcblk0 tweaks (if put in init.d) anymore;
- minor code cleanups
v1:
- initial release
- init.d support
- SELinux permissive
- unsecure ADB
- ext4 delayed commit for /data
=======
Stock XXUANC3 kernel (to revert changes)
http://www65.zippyshare.com/v/32441894/file.html
Revert using Odin, in the same way you've installed a Reloaded Version....
Awww man,...I wish i could flash this, but I'm on the exynos =(
Sent from my SM-P900 using Tapatalk
rgolnazarian said:
Awww man,...I wish i could flash this, but I'm on the exynos =(
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Sorry pal, Qualcomm only, not even a chance to run this same way as the devices (and mostly important: provided software, ie. system structure) DIFFER A LOT between themselves.
Update 1: uploaded fix #1 which is resolving some trivial issues found in initial version; sorry for that, now we can say that every described feature has been included hope for some feedback... thank you...
Update 2: FIX FOR NOT WORKING SCREEN MIRRORING CAN BE DOWNLOADED HERE:
http://www67.zippyshare.com/v/25492738/file.html
I have personally modified a library that is being used by screen mirroring feature, which forces video encryption using keys from stock kernel, and which prevents to run mirroring at all . This is an issue of any modified kernel, on any Samsung device. Attached library fixes this, by disabling HDCP at all. It has been reported that the library resolves the issue for any Qualcomm based Samsung device running 4.4.2 KitKat and for any custom kernel. It will NOT work for Exynos devices...
Installation:
- download attached libwfdsm.so file
- overwrite genuine one in/system/vendor/lib (important! NOT /system/lib!!!!)
- chmod 644 libwfdsm.so ||| chown 0.0 libwfdsm.so ||| restorecon -R /system/vendor/lib
- mirroring will work again after reboot!!
YAY!
Beautiful, absolutely beautiful. You made ma a very happy man with this. I'll flash this as soon as I get home from work. Can't wait to try it out, the stock kernel is giving me SOD and frozen wifi issues sometimes.
esgie said:
Sorry pal, Qualcomm only, not even a chance to run this same way as the devices (and mostly important: provided software, ie. system structure) DIFFER A LOT between themselves.
Update 1: uploaded fix #1 which is resolving some trivial issues found in initial version; sorry for that, now we can say that every described feature has been included hope for some feedback... thank you...
Update 2: FIX FOR NOT WORKING SCREEN MIRRORING CAN BE DOWNLOADED HERE:
http://www67.zippyshare.com/v/25492738/file.html
I have personally modified a library that is being used by screen mirroring feature, which forces video encryption using keys from stock kernel, and which prevents to run mirroring at all . This is an issue of any modified kernel, on any Samsung device. Attached library fixes this, by disabling HDCP at all. It has been reported that the library resolves the issue for any Qualcomm based Samsung device running 4.4.2 KitKat and for any custom kernel. It will NOT work for Exynos devices...
Installation:
- download attached libwfdsm.so file
- overwrite genuine one in/system/vendor/lib (important! NOT /system/lib!!!!)
- chmod 644 libwfdsm.so ||| chown 0.0 libwfdsm.so ||| restorecon -R /system/vendor/lib
- mirroring will work again after reboot!!
Click to expand...
Click to collapse
I was literally just about to post in the old thread with bad news about the modified "libwfdsm.so" file & screen mirroring with a custom kernel...if u remember i confirmed that the file u altered would work with a custom recovery on the 8.4 lte & i just assumed that it would work with an altered boot.img as well but unfortunately thats not the case after testing the other night (unless something else is wrong with my setup). So...my question is have u changed something else since then to allow it to work again & have u personally tested this yourself?
sorry to hijack the thread...didnt know if i should pm or post in the older thread
THEDEVIOUS1 said:
I was literally just about to post in the old thread with bad news about the modified "libwfdsm.so" file & screen mirroring with a custom kernel...if u remember i confirmed that the file u altered would work with a custom recovery on the 8.4 lte & i just assumed that it would work with an altered boot.img as well but unfortunately thats not the case after testing the other night (unless something else is wrong with my setup). So...my question is have u changed something else since then to allow it to work again & have u personally tested this yourself?
sorry to hijack the thread...didnt know if i should pm or post in the older thread
Click to expand...
Click to collapse
No problem, anyway, thanks for pointing the issue out! This may be an important information for mirroring users!
Since then I didn't change anything, yet. Really, I am also not sure if I have tested it with modified kernel, as the one posted here is the first kernel for P905 at all, and it's not even "fully" customized, as the kernel binary base was left unchanged.
So, I'd like to be sure: you are saying that modded lib:
- fixed the problem for custom recovery, but...
- ...didn't fix it for custom kernel
right?
I was looking for a solution to persistent enforcing mode since some time, so I was flashing test boot.imgs from time to time, then reverting to stock again, meanwhile I created above lib, I can't really be sure about if it is working when both bootimg and kernel are customized (this would also be an opposite to previous Sammy's Android releases, where a single fix was solving all the issues related to customizations of both kernel and recovery!).
We also have to be aware that the issues may not be a result of flashing different kernel at all, but a result of the changes themselves, ie. disabled knox, disabled encryption of i-dont-really-know-what, etc, etc.
And the most important thing! Since I have heard of AllShareCast/Screen Mirroring for the first time (it probably appeared for the first time in S3/Note2/Note10.1), it always required resetting the flash counter - which could be viewed in download mode and which is NOT the same as Knox flag - to ZERO and that requirement AFAIR remained totally independent from the requirement of having stock boot/kernel (or lib patch). Have you checked the counter state? Did you reset it to zero again using Chainfire's Triangle Away after flashing non-stock kernel (which, obviously, TRIPPED the counter)? Can you check if it is working? Note that at least on my P905, Triangle Away still works flawlessly and resets the counter without any problems and even without a need of reboot!
Please check above info and try if the issue is fixed after running Triangle Away. I am leaving for a short business trip soon, so I'll perform my own tests with AllShare cast until next of the week, however, neither today nor tomorrow...
I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.
cavkic said:
I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.
Click to expand...
Click to collapse
Argh possibly too many dots in filename... will correct it tomorrow.
cavkic said:
I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.
Click to expand...
Click to collapse
same here...
Hi,
I have a problem with screen mirroring.
Installed the patch and mirroring connects to the dongle, but the TV screen turns just black.
The dongle works perfect with HTC One M8, it must be a softwareproblem?
Thanks for help!!!
Will this work on the P905V (Verizon Variant)? I need to downgrade the permissions in my Security in order to use Towelroot, because they're set to Medium and I believe that prevents Towelroot to work properly. Most of the other Note 12.2 variants have been rooted....except the Verizon version.
Can anyone give me some advice please. When I enter the command in terminal emulator I get an error saying "Unable to open chown. No such file or directory". Am I missing something obvious lol.
Will this work on p907a AT&T version of note pro 12.2?
Sent from my SAMSUNG-SM-P907A using XDA Premium 4 mobile app
cnote74 said:
Will this work on p907a AT&T version of note pro 12.2?
Sent from my SAMSUNG-SM-P907A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
On the topic name it says [P905 LTE ONLY], and your device is some different..
tdetroit said:
Will this work on the P905V (Verizon Variant)? I need to downgrade the permissions in my Security in order to use Towelroot, because they're set to Medium and I believe that prevents Towelroot to work properly. Most of the other Note 12.2 variants have been rooted....except the Verizon version.
Click to expand...
Click to collapse
I would like this answered as well. I also have the "v" variant. Maybe saying LTE includes many? See my link I attached, found while investigating this specific question.
http://www.usatoday.com/story/tech/2013/07/07/sprint-att-verizon-phones-network-carriers/2486813/
Ever since I rooted my tablet it goes on random reboot kicks. I want to start over. Also TWRP will not stick when I try to flash it.
I have many issues which I'm currently posing in their appropriate forums. It would be nice to wipe to a rooted stock.
Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!
Thanks. The Galaxy is connecting to theTV, but the screen is only turning black - no Display...
Any idea?
Thank you.
esgie said:
Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!
Click to expand...
Click to collapse
esgie said:
Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!
Click to expand...
Click to collapse
I tried both methods and still get no devices found when I turn on screen mirroring.
ColBill said:
I tried both methods and still get no devices found when I turn on screen mirroring.
Click to expand...
Click to collapse
Hm.
This is weird, as the problems with allshare cast + custom kernels is not that "no devices are found" but that devices ARE found without any problem but the connection process fails after a few secs. This solution may help with the issue i described, but it will surely not solve the problem with no peers detected at all.
No peers detected = problems with wifi direct (are you able to send files between wifi direct between devices?)
Can you tell me what is your exact device config? And are you using allsharecast dongle or other third party hardware?
@fokus
Only one: also reset flash counter with Triangle Away and then try again. And make sure you spell the value in the command as "disable" not "disabled" - it's tricky and one can miss it...
Well, there are two additional things to add.
Guys, make sure you have updated Samsung's ScreenMirroring firmware update app to the latest version. And check out the samsung mirroring fix app in google play, which solves some issues for various devices (dunno which ones exactly as i have never been in need of using it).
The fix half worked for me lol. The tablet now connects fine to the Netgear PTV3000 but all I get is black screen. Step in the right direction though as at least it connects now. Just need to get a picture to show lol.
I bought the tablet back on December 2014 with Android 4.4.4 installed. My Teclast x98 Air II model Is (HG6M). There are 2 major problem on the tablet :
1. The playstore will force to close
2. The most critical problem : I cannot play most of the 3D Games, especially those heave 3D Games. I know many user face the same problem.
After month of attempt to contact the Teclast company and seller in Aliexpress, finally they release a solution.
Solution 1 : Play Store Issue
1. Teclast have release a firmware update especially for Teclast x98 Air Series Tablet. You can use the build in TeclastUpdateTool to check the firmware update.
2. If you fail to update (just like me), then you have to manually download the firmware and use the factory flash tool to do a clean install. Meaning all your data will lost, please backup first before proceed.
Link : http://www.teclast.com/tools/pad/pad.php
3. sorry they are all in chinese.. When the page load click on the right hand blue color text. Then it will bring you a new page to enter your model number.
3. Download the firmware
Solution 2 : 3D Games Freeze Issue
1. Download 2 files : 3Dgame update.zip & 3Dgameupdate.zip.tdlex from this link :
http://pan.baidu.com/s/1pJ9LjTL
2. Then use the build in TeclastUpdateTool to flash the file 3Dgame update.zip
3. Reboot the tablet and you will find that a new apps call [Fastmode] installed in the tablet.
4. Every time before play 3D Games make sure the fastmode is enable.
5. Note: if tablet have reboot, the fastmode will be disable. So you have to enable it again before play 3D games.
So far with the fastmode apps , i never have any problem playing heavy 3D Games. Hope this will help those who been looking a solution for the major issue. I consider myself lucky, as the seller able to help me get the solution from Teclast.
adyjob said:
Solution 2 : 3D Games Freeze Issue
1. Download 2 files : 3Dgame update.zip & 3Dgameupdate.zip.tdlex from this link :
http://pan.baidu.com/s/1pJ9LjTL
2. Then use the build in TeclastUpdateTool to flash the file 3Dgame update.zip
3. Reboot the tablet and you will find that a new apps call [Fastmode] installed in the tablet.
4. Every time before play 3D Games make sure the fastmode is enable.
5. Note: if tablet have reboot, the fastmode will be disable. So you have to enable it again before play 3D games.
So far with the fastmode apps , i never have any problem playing heavy 3D Games. Hope this will help those who been looking a solution for the major issue. I consider myself lucky, as the seller able to help me get the solution from Teclast.
Click to expand...
Click to collapse
Is this patch suitable for X98 Air III ?
biktor_gj said:
Hello everyone!
Android Wear for Gear 2 / Gear 2 Neo
This thread is about development of Android Wear for Gear 2 & Gear 2 Neo
IF YOU HAVE A QUESTION, ASK IT HERE: http://forum.xda-developers.com/gear-2/help/qa-porting-android-to-gear-2-t3018159
View attachment 3279773 View attachment 3279774 View attachment 3279775View attachment 3299034View attachment 3299035View attachment 3312899View attachment 3312900
DISCLAIMER
Code:
Your warranty is now void. Not only void,
it's not comming back. The moment you
flash anything on this thread you can say
goodbye to it. I almost hard bricked my
watch once. It can happen to you too.
I do my best to post things that aren't
dangerous for the device, but anything
as simple as a 9 instead of a 4 in the GPU
driver might make it overheat and kill it.
Everything here is at your own risk.
You have been warned.
Current development stage
Kernel:: Still work in progress. Most functions are working correctly. Expect some bugs.
GITHUB REPO: Github Android B2 Repository
Recovery:: Minimal image. Not actively worked on, but enough to wipe and access ADB: MediaFire
Android: Most of it is working, and for me at least, IS usable. Some things are still missing and will need to be worked out though.
Working:
Boot
USB: ADB, MTP [july 19th]
Display: Software rendering, OpenGL and mixed compositions
Screen dimming
Screen always on
Battery reporting and charging
Oportunistic Sleep (kernel)
Bluetooth: basic functionality (working for notifications, music control etc), Tethered internet access (still some bugs to work out though)
Vibration
Heart Rate Monitor
Accelerometer sensor
Step counter
Gyroscope (this includes tilt to wake)
Power management: CPU Hotplugging, frequency scaling, Amoled LPM, runtime suspend and opportunistic sleep.
Depending on use, can give from 12 to 48 hours of battery life. Normal use gives me about 18-20 hours with screen always on
Audio: Input and Output
Infrared
Basic TWRP recovery functions
Not working:
Camera
There's no way of playing music to the speaker directly from the watch
There's no gallery app
Palm-on-screen to suspend
Anything that's not specifically put as "working"
Latest development image:
August 13th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Bugfix release,
Full flash Package:
Mediafire: http://www.mediafire.com/download/ar8ir73m32yx05n/Wear_511__08_13_2015.tar
Includes: Kernel Settings application:
* Control vibration intensity
* Control brightness in ambient mode
* Enable / Disable Partial Redraws (enable for best battery life)
* Enable / Disable Idle Mode (reduces color depth in ambient mode to enhance battery life)
If you want root, Install the root package from TWRP after installing the Odin Package: (recommend to ADB sideload it)
http://www.mediafire.com/download/9ppo5zd6f9y41yl/Wear-SuperSU-v2.40(1).zip
Previous builds:
July 22nd, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Bugfix release
Full flash Package:
Mediafire: http://www.mediafire.com/download/pr3vljpdecep0dd/wear_511__07_22_2015.tar
md5: def249f18214c7ca00a5bc65391d0c0f wear_511__07_22_2015.tar
After flashing the big file, flash one of these, depending on what you need:
ADB only boot image: http://www.mediafire.com/download/cuo5fa95d5tgmv5/bootimage_ADB_ONLY.tar
ADB+MTP boot image: http://www.mediafire.com/download/bs6rwapqcc35sc6/bootimage_MTP_AND_ADB.tar
July 17th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Screen always on in Low Power Mode, MTP Support, @bitstra IR App Updated
Full flash Package:
Mega: https://mega.co.nz/#!0ZxgQYZA!7m986voG9NLYUUx7Nxzx8EiYbdgXxwFi56otuxQFZbM
Mediafire: http://www.mediafire.com/download/k71o1m16g32x65y/Wear__5_1_1__07_19_2015.zip
MD5: deffb5160968d81a4e560416315791eb Wear__5_1_1__07_19_2015.zip
July 13th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Infrared support (thanks @bitstra for your IR app!)
Full flash Package:http://www.mediafire.com/download/6mmb33lftfrr8w8/Wear_511__07_13_2015_Try2.zip
July 12th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J) ** Screen always on + Audio IN/OUT modifications
Full flash Package: http://www.mediafire.com/download/myzqnv4bkwa55b3/Wear_5_1_1_07_12_2015.zip
July 5th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J) ** Audio support!
Full flash Package: http://www.mediafire.com/download/eths38jax91sgnd/Wear_511_07_05_2015.zip
July 1st, 2015: Android Wear Lolipop - 5.1.1 (buildLDZ22J)
Full Flash Package: http://www.mediafire.com/download/6rzpfswta2s8fg3/Wear_511_07_01_2015.zip
June 27th, 2015: Android Wear Lolipop - 5.1.1 (build LDZ22J)
Full Flash Package: http://www.mediafire.com/download/bmcjbaikve5sob2/Gear2_Wear_Lolipop_5.1.1_06292015.tar.zip
June 27th, 2015: Android Wear Kitkat - 4.4.2W (build KNX01Q)
Full Flash Package: http://www.mediafire.com/download/2ar5ye1vla8g8gf/full_06_27_2015.zip
Everything I have/done with the Gear 2 is available on this folder: https://www.mediafire.com/folder/092gaz7gudh0f/Gear2, in case you want to dig a bit deeper
Installing
Odin: http://www.mediafire.com/download/v67itqpjitxxogi/Odin3_v3.09(1).zip
User @alvaromartinezb has made a really good video explaining what you have to do, check it out! https://www.youtube.com/watch?v=bBqg72z8LOk&feature=youtu.be
@alvaromartinezb Walkthrough video on audio: https://www.youtube.com/watch?v=klYqseFd90g
KNOWN ISSUES
USB doesn't work! --> Check if you're running latest build, check your drivers. Windows 7 may have some issues with MTP
ADB doesn't work! --> You might need to manually install the driver on the device manager in Windows (you can use Google SDK's bundled driver)
Battery doesn't last! --> Be careful with battery hog watchfaces, some will prevent the watch from entering suspend, or keep the heart rate sensor active at all times.
I can't play music from the watch to the speaker --> I haven't found an app that works. We're the only people with a speaker on an Android Wear device, and there aren't many 3rd party apps for that. Driver level is OK
I can't take photos! --> Work in progress, everything takes time, and my watch doesn't even have a camera!
Calls don't get routed through the watch and without it I will die! --> Then go back to Tizen. That functionality doesn't exist in Android Wear, and hundreds of hours of work for a function that probably wouldn't end up working anyway. And I hated it when I had it on Tizen, it only gave my phone issues when connecting to my car's bluetooth handsfree, and forcing me to choose back my phone on each and every call. I'm not developing that. If you want to try to code it yourself and you succeed, I can link to your work if you want, but I'm not wasting my time on that.
Going back to Tizen
BE ADVISED: GOING BACK TO TIZEN MIGHT PROVE DIFFICULT TO ANYBODY WITHOUT KNOWLEDGE OF THE WATCH, SDB, ADB, AND ANYONE WHO DOESN'T USE ODIN. DON'T PM ME FOR IT. IT'S WRITTEN BELOW. ASK IN THE Q&A SECTION PLEASE. THIS IS A DEVELOPMENT THREAD, AND THESE IMAGES ARE FOR DEVELOPMENT ONLY.
BE ADVISED (again): There's no PIT file for this watch. If your favourite flashing app for samsung phones requests one, use Odin. I know, I don't like it either. But we live in a world full of virtual machines with the ability to share USB ports. Now it's your chance to use them if you don't feel like installing Windows in your machine.
*. Walkthrough video by @alvaromartinezb : https://www.youtube.com/watch?v=LhzIqFopQNY&feature=youtu.be
1. Flash this file: http://www.mediafire.com/download/3cg2eazoouur0bs/Tizenmod-Full-Restore.tar
2. When it fails to boot and the screen goes blank, reboot to the bootloader menu and select recovery.
Extreme Recovery mode - Only use if above method doesn't work
YOU NEED TO KNOW HOW TO USE ADB/SDB FOR THIS.
It may happen that you try to recover your watch but for whatever reason it still enters a bootloop when attempting to boot Tizen. This might happen if you played with partitions, if some permissions were set where they shouldn't be, etc. If you enter recovery mode in Tizen and you don't see a confirmation that the watch is being restored to default, you can try this:
*NOTE* This is highly destructive. You do this wrong, your watch might not boot again. I'm not responsible for whatever damage you do to your watch.
First of all download everything from this folder:
https://www.mediafire.com/folder/a1tcatuw1a8t3/Full_Restore
And then follow these steps:
Code:
1. Flash TizenModFull
It will start rebooting itself
2. Flash recovery_fota_cache
3. Enter recovery, and run the following commands through ADB:
adb shell ->
umount /data
mount /dev/block/mmcblk0p15 /system
mount /dev/block/mmcblk0p13 /system/opt
mount /dev/block/mmcblk0p14 /system/opt/usr
rm -rf /system/opt
cp /system/usr/system/RestoreDir/opt.zip /system
cd /system
unzip opt.zip
sync
cd /
umount /system/opt/usr
umount /system/opt
umount /system
Exit the shell and select "Reboot -> PowerOff" from TWRP
4. Now press and hold the power button until "Rebooting..." appears, then enter Download mode
5. Flash kernel_tizen.tar
6. Reboot again to download mode
7. Flash tizenmod2.tar
Some info about the device
Gear 2 specifications
Samsung Exynos 3250, dual core up to 1GHz
512 Mb of RAM
4 Gb of flash, divided in 15 partitions (see below)
Mali 400 GPU, using Exynos DRM driver
YMU381 audio, supported by ALSA
BCM4334W Bluetooth/WLAN controller, already supported by Android in a bunch of phones
Samsung SensorHub (STM32) controlling Gyro/accelerometer and HRM. Supported in the kernel and seen in Android HAL.
Partition layout
bota0 -> ../../mmcblk0p1
bota1 -> ../../mmcblk0p2
csa -> ../../mmcblk0p3 --> ext4 -> /csa
boot -> ../../mmcblk0p5 --> Main Kernel
csc -> ../../mmcblk0p12 --> ext4 -> /system/csc
fota -> ../../mmcblk0p10 --> seems empty
ramdisk-recovery -> mmcblk0p8 -> ext4 -> Unused in tizen --> USED AS BOOT PARTITION IN ANDROID
module -> ../../mmcblk0p9 --> ext4 -> /lib/modules --> USED FOR TWRP IN ANDROID
rootfs -> ../../mmcblk0p15 ext4 "/" --> Root file system, recovery works from here too. If you break it it will only boot to download mode. --> USED AS SYSTEM PARTITION IN ANDROID
system -> ../../mmcblk0p11 EMPTY --> Did samsung start with Android on this thing then changed their minds?
system-data -> ../../mmcblk0p13 --> ext4, /opt --> If you erase this partition, your watch won't boot back into Tizen. Do not touch it unless you have a backup and know your way into restoring it.
user -> ../../mmcblk0p14 EXT4, /opt/usr --> all user data, including the MTP available part (/opt/usr/media) --> USED AS DATA & SDCARD IN ANDROID
Click to expand...
Click to collapse
Original thread -----
http://forum.xda-developers.com/gear-2/development/please-help-kernel-compiling-android-t2992953
Straightforward install. OP you da MVP!
Sent from my iPad using Tapatalk
Keep working on it man! Fantastic work!
Link to the original thread is wrong...
Sent from my SM-N910C using Tapatalk
Any updates?
Sent from my Nexus 6P using Tapatalk
I love you.
I take à neo for xmas.
It never appear on my z2.
I flash with Android wear today immediatly work.
Ty ty ty à lot
1.3 ROM update
Excellent!!!
But remember to flash with 1.3 ROM. It fixed OK Google and Always On issues.
Search youtube for "Android Wear for Gear 2 1.3 Update!"
any new updates for Geo s2 neo and android wear ?
Thanks,
Mike
Yes, i like a port of aw to the gear 2 (the only thing i would buy a 2, have a Gear 1 with Tizen and am missing features from my LG G).
And i appreciate the work.
But i am not so sure about some things mentioned here:
Using the speaker to play music on watch and phoning with it: Since there are some devices with speakers (Zenwatch 2, Huawei watch and others (more expensive ones)) and i read that android wear 6 will be out only for such devices... There should bei possibilities to use the speaker "full" - except it is a problem of missing drivers because the port comes from a device that lacks of speaker?
I am pretty sure that i had seen apps for that, but hadnt tested because my G has no speaker.
Is there any newer/more information?
Edit:
Its german, but f.e. it is mentioned there that with aw 1.4 came support to phone via watch and to watch videos with sound:
http://www.cnet.de/88165305/asus-br...e-fuer-zenwatch-2-und-neue-smartwatch-modelle
SirTurbo said:
Yes, i like a port of aw to the gear 2 (the only thing i would buy a 2, have a Gear 1 with Tizen and am missing features from my LG G).
And i appreciate the work.
But i am not so sure about some things mentioned here:
Using the speaker to play music on watch and phoning with it: Since there are some devices with speakers (Zenwatch 2, Huawei watch and others (more expensive ones)) and i read that android wear 6 will be out only for such devices... There should bei possibilities to use the speaker "full" - except it is a problem of missing drivers because the port comes from a device that lacks of speaker?
I am pretty sure that i had seen apps for that, but hadnt tested because my G has no speaker.
Is there any newer/more information?
Edit:
Its german, but f.e. it is mentioned there that with aw 1.4 came support to phone via watch and to watch videos with sound:
http://www.cnet.de/88165305/asus-br...e-fuer-zenwatch-2-und-neue-smartwatch-modelle
Click to expand...
Click to collapse
Biktor, the developer who made the AW port for the Gear 2 (Neo), has indeed ported most of the AW 1.4 functionality.
The speaker is working (the watch rings when a call comes in), but he didn't succeeded in actually taking the call on the watch.
So you will still need to take the calls on the phone itself.
There is a program called "Wear Notifications" which allows to read out loud the notifications on the watch
(really cool feature), but also that developer has stopped developing. The latest version has problems reading out loud the notifications.
When you flash the AW port on the Gear 2 (Neo), be aware that other features also don't work...like camera, BT calling on watch.
And the battery life on AW is worse than on Tizen.
I know this is probably a pipe-dream but, I would be so happy if we see an android wear 2.0 port once it drops this month. Or ever for that matter. *crosses fingers*
SumTuusDeus said:
I know this is probably a pipe-dream but, I would be so happy if we see an android wear 2.0 port once it drops this month. Or ever for that matter. *crosses fingers*
Click to expand...
Click to collapse
Yes!!! Me too
I guess that something has updated but suddenly, when I was in the pub last night, the watch face had changed - digital clock at the top and a background that changes with the time of day and weather (pictorially) - never seen it before - it seems to be called Incrememt according to the Android Wear app - I don't remember downloading it - If I try and change the watch face back I get the message 'Unfortunately Zenwatch manager has stopped'.
Anyone else had this / know anything?
***FIXED*** by reflashing watch
I flashed this the other day and can't get my mic to work. Is there a work around for it or did I miss something?
I would suggest reflashing. Because, my mic works.
How about notification sounds. Mine doesn't seem to have those either.
That works for me too.
Are you using the newest build in the OP?
Yup
Maybe I have an app or permission causing my mic and notification sound to break. New to android wear device
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