Using beta ICS? Turn off logging. - Huawei MediaPad, T-Mobile SpringBoard

So, noticed the logging is on by default in the current ics roms.
To turn it off Dial * # * # 2846579 # * # * (or get any cut from play, create shortcut-> activity->testing)
->project menu act->background setting>2. log setting.> log switch->turn off.
Then delete folder huaweilog under sdcard (it can be 500MB+ big)

Great discover!

mangoman said:
So, noticed the logging is on by default i the current ics roms.
To turn it off Dial * # * # 2846579 # * # * (or get any cut from play, create shortcut-> activity->testing)
->project menu act->background setting>2. log setting.> log switch->turn off.
Then delete folder huaweilog under sdcard (it can be 500MB+ big)
Click to expand...
Click to collapse
Wow, thanks! I just got back 2.7GB!

Found you can upgrade to a new rim from here also
project menu act --) upgrade --) sd card upgrade and then pick the upgrade
Haven't tried it tried it exactly but when I did click one it restareas and went to the upgrade screen
Sent from my HUAWEI MediaPad using xda premium

Excellent, noticed that the device seems more nippy once i disabled this.

nice...

Related

[SCRIPT - 2/7/11] NookColor Auto Config (Windows) 1.0.0, 1.0.1 & 1.1.0

Shout out to Mistar Muffin for his script for other OS's. I've added my knowledge of DOS and some extra stuff. Enjoy guys it works perfectly. I've tested this thing fully it works....again it works. Run it over your messed up Nook and it should fix it. LOL, hopefully!
Prerequisites; Super user and adb working or auto-nookered! Enjoy I've tested this on Nooks DIRECTLY OUT OF THE BOX and with Nooks that have been partially modded.
Recommendations? Yea if you don't like the fact that I edited the volume buttons I've taken it out of the autonook.bat and added it to a separate batch file.
Features 1.0.0:
Code:
* Creates .Android Folder & adb_usb.ini *
* Installs Busybox *
* Updates settings.db *
* Disables OTA Updates *
* Enables Multitouch In Apps *
* Converts Volume Buttons (Back, Menu) *
* Installs Live Wallpapers *
* Installs Email *
* Enables Location Service *
* Installs YouTube! *
* Installs DroidX Keyboard *
* Replaces Boot Animation with DroidX *
* Installs Framework and Gapps *
* Modifies system fingerprint *
* Modifies packages.xml *
* Fixes Permissions *
* Installs Applications *
- REBOOTS NOOK COLOR -
* Fixes Broken YouTube *
Features 1.0.1:
Code:
* Creates .Android Folder & adb_usb.ini *
* Fixes YouTube just incase its broken *
* Converts Volume Buttons (Back, Menu) *
* Updates settings.db *
* Replaces Boot Animation with DroidX *
* Uninstalls Softkeys & Installs Launcher Pro *
* Installs Applications *
Features 1.1.0:
Code:
* Creates .Android Folder & adb_usb.ini *
* Fixes YouTube just incase its broken *
* Converts Volume Buttons (Back, Menu) *
* Installs SQLite3 *
* Blocks Future B&N Updates *
* Replaces Boot Animation with DroidX *
* Uninstalls Softkeys & Installs Launcher Pro *
* Installs Applications *
Things to do:
Update Android Market
Download:
Auto Configure Script 1.0.0
Auto Configure Script 1.0.1
http://www.megaupload.com/?d=EGCZAHNP
P.S - If you break your Nook I'm not going to take any responsibility. This will not format your system32 or deltree your windows folder...just enjoy!
Need to get back to stock?
WARNING: Make sure your battery is CHARGED before attempting!
Code:
adb pull /rom/devconf/BootCnt
echo -n -e "\x08\x00\x00\x00" > BootCnt
adb push .\BootCnt /rom/devconf/BootCnt
adb reboot
There is a batch file that runs the above code included its called (factoryreset.bat)
This will set the boot count to 8 and reboot your device sending it into Factory Reset mode. Once your factory reset is complete you can force shutdown (by holding power for 15 seconds) and hold then hold the "n" button and "Volume +" while powering the unit on to reset your data. After this is done its like you just pulled the nook out of the box for the first time.
Remove your SD Card and turn on your Nook Color, register your device and plug in the USB cord. Go DOWNLOAD the 1.0.1 update and save it to your "MYNOOKCOLOR" drive's root folder. Reboot your device should start to update your nook to 1.0.1!
Now that your Nook Color is on 1.0.1 firmware you want to root it with Auto-Nooter you can follow this thread to do so.
Enjoy
Didn't need the whole script, but I modded my volume buttons with your files and code. Thats a great feature. Thanks!
donballz said:
Can you document what this does and why I should care?
Most importantly: In what way did you mod the volume buttons? Thanks.
Click to expand...
Click to collapse
Eh...read the title of the code he posted. Do believe he modified the buttons to act as back / menu.
A...colorful post ;-)
"DIRECTLY OUT OF THE BOX" so it works on...unrooted Nooks ?
After two spontaneous resets yesterday I'm ready to try anything at this point, especially since I can't get mine to update to 1.01 with the manual method...
...which raises the question, does this work with 1.01 ?
1. "DIRECTLY OUT OF THE BOX" - no, still needs nooter for ADB, makes sense
2. Does not work with 1.01+nooter - it hangs on boot at the Adobe screen, like the original script and autonooter I understand.
Will have to do it the manual way or maybe keep some of the automation, must say the script is well documented ;-)
So I did the 8 finger salute and it flashed itself to...1.0.0 ! So after clearing the memory I am now running the script, currently installing the apps...
Seems to have worked pretty well, I did have a problem with the menu button not working until YouTube got fixed by the script, so I got around that problem by commenting on a video at which point it asked me for my log in info.
Now updating to Maps 5.00!
Hopefully the OTA killing in the script will prevent an update to 1.01...
post Maps 5 and ill update my script accordingly
should work on 1.0.1, any testers?
Whoa.....it installs flash?
Sent from my LogicPD Zoom2 using XDA App
Yup flash for 2.1
xboxexpert said:
should work on 1.0.1, any testers?
Click to expand...
Click to collapse
Nope, like I said above it doesn't, fortunately a "factory reset" took my NC back to 1.0.0 so I was able to run it and no "spontaneous resets" so far, must have been something in Autonooter.
Not sure how to get the MAP 5 apk, would Titanium do that ?
I'll look into the map 5 app Maybe marketplace then download from /data/app. I'll get it when I get a change. I wonder if the reason why this doesnt workon 1.0.1 is because of my change of the bootanamation. If anyone would like to run this on 1.0.1 with out my boot animation change that would be fanstastic. I know alot of you guys are younger then me but I have to go xmas shopping with the woman
:edit
Also might be a problem with the framework but I replace the framework package with the hacked one on the main 1.0.1 so I dont know what could be the problem.
Girlfriend is wrapping some gifts I'm going to update the 1.0.0 version with new google maps 5.0 and I'm going to remove the 1.0.1 for now until I test fully
Does Flash for 2.1 actually work with this device? I tried loading the Flash for Eclair devices a couple days ago and it would load but no flash activity.
Thanks for the hard work.
Probably not I added it cause I saw it here. I'll remove it on mine and in the next version. Unless you find a working one. I think Java is needed for Flash to work.
I wondered why there was so much unnecessary swearing in the original post and then I saw "Xbox" in his name...
Fits...
I was hammered...which is probably the only reason I released it
Been stable since last night, more than I can say of my experiences with Autonooter (spontaneous hardresets at random), but I'm not getting WiFi location in Maps, something I had with Autonooter, anyone know how to enable this ? The location boxes were checked in the wizard.
webvan said:
Been stable since last night, more than I can say of my experiences with Autonooter (spontaneous hardresets at random), but I'm not getting WiFi location in Maps, something I had with Autonooter, anyone know how to enable this ? The location boxes were checked in the wizard.
Click to expand...
Click to collapse
Me3 This was my main reason for re-rooting..
Yes, Auto-Nooter must be doing something the scripts aren't doing, not sure whether it can be done manually via ADB...
If you guys want to stick with the old nooter and then I can just add enabling super user to my script....let me know if this is something you'd like me to add.

Question about MiniCMSandwich

Hi friends, I have questions about the firmware MiniCMSandwich. First, why do not works the code service - * # * # 7378423 # * # *.
Secondly, tell me how to replace the standard Caller ID.what file apk is responsible for it?
Found, in the system there is no application (servicemenu.apk). I downloaded it from ICS, trying to establish. Error. ..
Help me, please.
Because it is Sony's own menu, which is not in other ROMs.
Sent from my Xperia Arc S using xda premium

DELETED

DELETED
Installation Instructions
Comming from a Pre "Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839" ROM
Do a back up!
Do factory reset/ wipe (incl. /system)
In recovery: flash ROM zip file. (You WILL get an assert error!)
Read the warning on the screen.
Flash the ROM again!
If you have and international device flash the INT Kernel from the OP.
Flash Gapps
Reboot.
Comming from "Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839" ROM or later
Do a back up!
Do factory reset/ wipe (incl. /system)
In recovery: flash ROM zip file.
Ignore the warning on the screen.
If you have and international device flash the INT Kernel from the OP.
Flash Gapps
Reboot.
Change Log:
NOTE: All future changelogs will be attached below!
Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839 --> Slim-venturi-4.4.2.beta.1.9-UNOFFICIAL-20131223-1727 changes:
SlimRoms/frameworks_base:
2013-12-22: systemUI: fix notification dissapearing during recreation and possible <@Lars Greiss>
Code:
app crashes due that binded notifications are not there anymore
as well small cleanup
Change-Id: Ieed143088a55693fc56e6526e6b349d72b7b25cc
2013-12-22: Merge "fb: use SlimActions for torch tile and send as qualified user" into kk4.4 <@Gerrit Code Review>
2013-12-22: Merge "fb: lock statusbar recreation and release after ticker is done" into kk4.4 <@Gerrit Code Review>
2013-12-22: fb: use SlimActions for torch tile and send as qualified user <@Lars Greiss>
Code:
the broadcast and do not collape the panel bar
as well send with qualified user the IME switcher broadcast.
Change-Id: Ibad8b4f908e6d701999712f58b9996cd7a805fc4
2013-12-21: fb: lock statusbar recreation and release after ticker is done <@Lars Greiss>
Code:
In rare cases it happens that the ticker call just happened and a recreation
was called which results in a crah due of the missing binder.
To avoid it lock the recreation when a ticker call is in progress
and release it after it is done and notify the recreation to go ahead
Change-Id: Iedbf858bdb2ac2ad97563e344a571b384e17cfc7
2013-12-21: trds:[framework] dark images adjustments <@kroz>
Code:
Change-Id: Ie038c4a1aa535708c23f099fb5e836407e3d1603
SlimRoms/packages_apps_Camera2:
2013-12-22: TrueView Returns! <@Gerrit Code Review>
Code:
This adds the ability to view the complete sensor frame image
rather than the cropped preview used by AOSP to fill the entire
surface.
Change-Id: I79b14a165c66fa4f8b8e43598bd6a80e4de1c08b
2013-12-22: Fix Smart Capture label display <@Lars Greiss>
Code:
Change-Id: Ia3cceda0bf7fec21f2d019f07d416bfe8ebf211d
2013-12-22: Fixes Mako continues focus problem <@Lars Greiss>
Code:
rebase
Change-Id: I25187998003d357ec5ed3b10329fb39941f47bea
Signed-off-by: Josue Rivera <[email protected]>
2013-12-22: camera: Add ZSL support for Samsung/Qualcomm cameras <@Lars Greiss>
Code:
* Preview management for Samsung/Qualcomm cameras
Patchset 3: merge conflicts fixed
build errors fixed
PatchSet 4: codestyle corrections
Change-Id: Ib36bd21c9a76b45bced3eee2f25acc35b5d82b30
SlimRoms/packages_apps_InCallUI:
2013-12-21: Merge "TRDS: Dark InCallUI" into kk4.4 <@Gerrit Code Review>
2013-12-19: TRDS: Dark InCallUI <@kroz>
Code:
PS2:
- moved into right folder
PS3:
- redirect colors of original layout xml
Change-Id: I5bcfeb692bc4653e240df7c47216826452ee7d47
SlimRoms/packages_apps_Settings:
2013-12-22: Merge "First translation of Settings for KitKat" into kk4.4 <@Gerrit Code Review>
2013-12-18: First translation of Settings for KitKat <@gwindlord>
Code:
"Go To Sleep" paraphrased
Removed whitespace
Change-Id: I666cb60da3a0751ba1d4f351c2a46b1b159d9dd3
SlimRoms/packages_apps_Torch:
2013-12-22: Torch: add better error handling and added fallback mechanism <@Lars Greiss>
Code:
The handling of the Torch if an exception occured was very bad and
it was easy to break:
- notify the user with toast if the camera interface is not pressent
- catch the case that sys led controlled devices have wrong permissions
(eg third party kernel) and torch will completly crash.
Checking now if sys init is present.......if not successful
try to switch back to the camera interface.
- send broadcast change only if the state really switched
- when error occured turn off the service and the notification
- cleanup
- send broadcast with qualified users
Change-Id: Iabeb3b5f1c17d784a06c154f9a33e8d3d5214b7d
2013-12-21: make torch to a real system app <@Lars Greiss>
Code:
give it the correct permissions to allow to write
to sys interface with less permissions needed to
keep security alive
Thanks Alex for the hint to the hidden API
and gmillz for the idea
Change-Id: I44f70bdf3ecfb57ccac85eebe61e57a163bdf501
SlimRoms/vendor_slim:
2013-12-22: push to 1.9 <@Lars Greiss>
Code:
Change-Id: I4c4aab6fbd8440cda3649b1d77351aa0563dd15c
2013-12-22: push to 1.8 for weekly <@Lars Greiss>
Code:
waiting for feedback on last patches then we start jenkins
Change-Id: I1b8f5dcb6f8620506dfc4399b75c56802a3bd8e1
Older logs:
2013-12-22: clean up: movefiles.sh is no longer needed... <@Meticulus>
2013-12-22: overlay: SlimCenter overlay for ota. <@Meticulus>
Code:
-I've found that with just a few small adjustments you can redirect
SlimCenter to another url to check for updates.
2013-12-22: overlay: BOARD_USE_LEGACY_TOUCHSCREEN device tree flag. <@Meticulus>
Code:
-Everytime I repo sync my framework base commit to fix the touch screen
gets wiped out. In order to preserve it, I'm putting it in the overlay.
2013-12-20: ota: testing <@Meticulus>
2013-12-20: LVMv2: phase out the use of mmcblk0p14 as extra space. <@Meticulus>
Code:
-With the implementation of LVMv2, we don't need to use mmcblk0p14
(/vendor, /system/vendor) as extra space.
-mmcblk0p14 is now in the logical volume group "lvpool" along with
mmcblk0p13 and mmcblk0p16.
2013-12-20: ota: change device name from venturi to YP-G70 <@Meticulus>
2013-12-20: ota: removed beginning and ending spaces.. <@Meticulus>
2013-12-20: ota: ota update manifest. <@Meticulus>
Code:
-Initial commit of the ota manifest.
2013-12-19: slim.mk: build type switch. <@Meticulus>
Code:
-Switch from common full tablet to common full hybrid...
2013-12-19: init.venturi.rc: fix a small typo.. <@Meticulus>
2013-12-19: LVMv2: add lvm services to init.venturi.rc. <@Meticulus>
Code:
-This was left out of my initial commit here:
https://github.com/Meticulus/slim_device_samsung_venturi/commit/7ccd47c874f9a00c0397c8e8f17f3faaf72e256b
-This is absolutly neccessary for LVM...
2013-12-19: twrp: Correct screen resolution. <@Meticulus>
2013-12-18: LVMv2: initial implementation system(600M) <@Meticulus>
Code:
-Logical Volume Management
-The YP-G70 only has a 290m /system partition and this is not enough
to accomodate KitKat + full gapps. So, I'm implementing LVM so that
we can get dynamic volume resizing without having to change the under-
lying partitions.
-Partitions in Logical Group (Aprox 2.1G)
-- /dev/block/mmcblk0p13 (normally /system)
-- /dev/block/mmcblk0p16 (normally /data
-Logical volumes
-- /dev/lvpool/system (600M)
-- /dev/lvpool/data (100% remaining, aprox 1.5G)
-Installation Notes
--On the first flash, if the system logical volume is not present or
is less than 600M there is an assert error. This is so that if anyone
needs to backup information contained in /data, they can. In order to
proceed with the installation, the zip must be flashed a 2nd time.
--During the 2nd flash partitions in the logical group are wiped and
the logical volumes are created and formated then the /etc/fstab and
/etc/recovery.fstab are switched so that, when we hand everything off
to the normal rom installer, the new logical volumes are mounted.
-Reverting to a PRE-LVM ROM
--In the YP-G70 the "recovery", be it CWM or TWRP and in the kernel's
recovery-ramdisk. So in order to get a different recovery you just
flash a different kernel. So to get back to a PRE-LVM ROM, you just:
1. Reboot to recovery like normal.
2. Flash your PRE-LVM ROM like normal.
-- Note: All we really care about at this point is that the kernel
(boot.img) gets flashed. Ignore any other errors!
3. After the flash, Power off.
4. Hold volume up and power on, till you get to recovery.
5. Full wipe, including /system
6. Flash ROM + Gapps like normal
-Future Considerations
--LVMv2 allows us to quickly change the size of the system partition
as Android grows in size without having to manually repartition.
Manually repartitioning might cause unforseen problems with legacy
software.
-Meticulus
2013-12-17: recovery init: adb without /system <@Meticulus>
Code:
This allows "adb shell" to function when /system partition is not mounted
or for any reason /system/bin/sh is unavailable.
When /system IS mounted then adb uses mksh is used via /system/bin/sh
When /system IS NOT mounted then adb uses busybox via /sbin/sh
2013-12-14: Removed torch from build. <@Meticulus>
Code:
Torch isn't working at the moment anyways. May readd later!
2013-12-14: twrp: defined custom power key and fixed screen timeout problem. <@Meticulus>
2013-12-14: Initial commit <@Meticulus>
Super mine again!
BAH!! y u release while i'm at work....
Gonna test when i get home....
Flashy flashy, its like Christmas but better! no wrapping paper to clean up or relatives to dispose of.
Somehow I knew I would come on today to find KitKat available. Trying it now, will update later.
EDIT: No options for hardware buttons?
Very nice. How did u solve the dalvik cache issue?
Sent from my Nexus 7 using Tapatalk
iurnait said:
Very nice. How did u solve the dalvik cache issue?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I didn't really solve it, per say. I put in a cheap hack to change the permission of the directory: in the init.venturi.rc. I'll got some clean up to do, but I'll be pushing my device tree tomorrow and submitting some changes to yours so we can get CM11.
Hello! Thanks for your work! I tested this rom, it's pretty nice. The only bug (except known) is that TWRP is not working on INTL kernel.
i'm having problems getting super user access, anyone else got this?
Lorddemonrage said:
i'm having problems getting super user access, anyone else got this?
Click to expand...
Click to collapse
My SU access is ok.
had sometime to mess with it. my sd card is not showing up, lost super user access. other than that almost everything works fine.
elaborating, i can see sd card in file manager, but connecting to windows does not show sd card accessible, just the galaxy players internal memory
Does it need a wipe if coming from 4.3
Sent from my zx spectrum
mr_ggcstop said:
Hello! Thanks for your work! I tested this rom, it's pretty nice. The only bug (except known) is that TWRP is not working on INTL kernel.
Click to expand...
Click to collapse
TWRP is a "known issue", if you read the OP. (workin' on it)
Lorddemonrage said:
had sometime to mess with it. my sd card is not showing up, lost super user access. other than that almost everything works fine.
elaborating, i can see sd card in file manager, but connecting to windows does not show sd card accessible, just the galaxy players internal memory
Click to expand...
Click to collapse
I am aware of the "2 cards in mass storage issue", but for the su problem, haven't had any issues .... developer-options-> root (or something like that)
joemhewitt said:
Does it need a wipe if coming from 4.3
Sent from my zx spectrum
Click to expand...
Click to collapse
yes including system:good:
iurnait said:
Very nice. How did u solve the dalvik cache issue?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Will you be making a stock cm11 ROM in the upcoming weeks?
I would love to play with this ROM for the time being ^_^
aznflawless said:
Will you be making a stock cm11 ROM in the upcoming weeks?
I would love to play with this ROM for the time being ^_^
Click to expand...
Click to collapse
No I am not. I can't maintain 2 Roms... I submitted patches to get CM11 working but someone else is going to have to build it...
@iurnait ???
Sent from my M470BSA using Tapatalk
When will the TWRP fix be released? My US player now, after the flash using Clockworkmod, will not be recognized in odin when in download mode. I love kitkat but i want to go back to my cm10.2 build. And the only way to do that as i know is to go to gingerbread and upgrade from there. but because of this issue i am stuck with TWRP and no os on my USA galaxy player 5.0. Please advise!!!!
bassbrick15 said:
When will the TWRP fix be released? My US player now, after the flash using Clockworkmod, will not be recognized in odin when in download mode. I love kitkat but i want to go back to my cm10.2 build. And the only way to do that as i know is to go to gingerbread and upgrade from there. but because of this issue i am stuck with TWRP and no os on my USA galaxy player 5.0. Please advise!!!!
Click to expand...
Click to collapse
Do not ask for ETA's!
READ THE OP BEFORE FLASHING!!! THE OP CLEARLY STATES NOT TO FLASH UNLESS YOU KNOW WHAT YOU ARE DOING BECAUSE TWRP IS NOT WORKING!
Been Waiting For This For Awhile Noe. Thanks Guys, I Guess With Patience Good Things Come. Hopefully The Same Can Be Said About The Rear Camera.
Sent from my YP-G70 using xda app-developers app
Meticulus said:
Do not ask for ETA's!
READ THE OP BEFORE FLASHING!!! THE OP CLEARLY STATES NOT TO FLASH UNLESS YOU KNOW WHAT YOU ARE DOING BECAUSE TWRP IS NOT WORKING!
Click to expand...
Click to collapse
Hi Meticulus!
First, let me thank you for all your time and energy spent in making this mod for an old device! I love my Player 5, but it is show it's age. I'm hoping your SlimKat 4.4.1 will breathe new life into it. (A shame Samsung stopped developing this line).
I have a Galaxy Player 5 running a rootedGingerbread 2.3.5 with CWM v5.0.2.7 (no TWRP)
Do you recommend any special preparation before applying SlimKat 4.4.1?
Since I'm using CWM, will I be able to restore back to Gingerbread using a current backup (just in case)?
As you might have guessed, I am not a frequent "mod"-er so I've fallen behind a bit.
Thank you for taking your time to help me and so many others!

MTCB/MTCC rk3188 (4.4.4) Firmware with an xposed set of MTC apps

Based on latest KITKAT from @dsa8310.
Sharing with you my custom modified rom with KK image.
OPEN GAPS VERSION: DOWNLOAD 1024x600 and 800x480 image
To get root access, you have to type in Factory settings instead of 126 -> *#hct#root# and then ok (just once!).
UPDATE: 11.9.2017
openGaps version:
Lite 1024 x 600 openG version. Need testing!!!
- LITE version of system
- added xposed status bar module for remove status bar items (copy mtc-status bar to external GPS Card)
- new screen saver without null null text (if doesn't show install it manually from: system/app/mtcscreensaver)
- removed all the bloatware callendar, calculator etc...
- added new car launcher AG (trial) for me the best - full version 1€
- back to xposed mtc manager 1.13 module
- screen saver from @Malaysk
LITE VERSION OPTIMIZATIONS:
- kernel tweaks (changed parameters of dalvik vm etc,...)
- better ram management
- faster scrolling
- faster boot
- better responsiveness
- increased performance and app ram management
- better video acceleration
- disable sending android logging stuff
- force gpu&cpu rendering
PREINSTALLED APPS and MODULES:
All these apps and xposed modules are preinstalled and you just have to activate xposed modules you need:
- disable_service
- google-maps-9.2 (you can update it just install as normal apk)
- mtcservice-2.60
- mtcsound-2.0.5 (remove from xposed if you don't have sound mod for better performance)
- mtcxp-1.0
- quickreboot
- RootExplorer
- Titanium_Backup
- xposed-disablefullscreenkeyboard
- xposed-mtc-bt-2.3
- xposed-mtc-keys-5.2 (custom keys for harware buttons)
- xposed-mtc-manager-1.13 (mode button mod and no closing apps when starting the car, etc.)
- xposed-mtc-music-2.8
- xposed-mtc-poweramp-1.4 (working media keys and stopping power amp when mtc app is started)
- xposed-mtc-radio-1.11
- xposed-VolumeBar (replaces original volume bar)
- 7th floor sound mod preinstalled and working
OTHER ADDITIONS: (included in download to copy on external SD (GPS card)
There is also file to copy on SD card (GPS card) that has features for MTCManager:
- hardware mode button can be configured (included in download) as well to switch between apps and auto play them (radio, poweramp, music, pcradio etc)
- mtc screen clock
- mtc status bar
DISABLING THE SCREEN SAVER OR CHANGING TIME:
Edit on external SD/ GPS-Card : Mtc.Manager/settings.ini
# the inclusion of an alternative screen saver, when you specify false will work full-time mechanism:
screenClock=false or true to activate
# Time off the screen if you do not set out full-time settings will be used in sec:
screenTimeout=300
# The name of the screensaver program package
screenPackage=com.microntek.screenclock
# Name Activiti screensaver
screenClass=MainActivity
# If the name of the package and Activiti is not specified, it will use a standard screensaver
MTC MANAGER CAPABILITIES:
capabilities
All configuration files must be on the external map in the mtc-manager directory.
1. The module carries the functionality of xposed-mcu , which does not allow the radio to go to sleep during the scrolling of the starter.
- when receiving a signal to turn off the module delays for 5 seconds, if at that moment the power reappears, nothing happens, in the absence of power, the radio recovers into sleep.
Due to the features of the implementation of the inclusion in our MCU, the screen goes out for the time of voltage failure.
This functionality can be disabled in settings.ini:
Settings.ini
Mcu_power = false
2. The module has a white list of applications that does not allow the system to close necessary services and applications when going to sleep and when pressing the "Acceleration" button in the blind. Thus, the module allows to refuse from using mtc-wakeup-service .
Filename with exceptions whitelist.ini
The file name of the white list application packages must be listed.
#
example
3. Accelerated start of user services. The services are started when the system kernel is loaded.
The list of services should be on the external map in the mtc-manager directory, the file name start_services.ini
each line should contain the service name in the format package name / full service name,
#
example
4. An alternative screensaver with a list of exceptions, running in any (even a non-standard application). The standard screen saver mechanism is activated.
It may not work on all firmware.
Settings in the settings.ini file.
Settings.ini
# Inclusion of an alternative screensaver, if false, the standard mechanism will work:
screenClock = true
# screen off time, if not specified, the value from the
default settings will be used: screenTimeout = 60
# screen saver program name
screenPackage = com.microntek.screenclock
# screen saver activation name
ScreenClass = MainActivity
# if the package name and activations are not specified, then the standard screensaver will be used
The exception list is located in the ss_exceptions.ini file - the package names must be listed, for example:
Ss_exceptions.ini
com.microntek.music
ru.yandex.yandexmaps
Also the screensaver will not start when talking on the phone, the rear view camera, navigation and turning off the radio.
If instead of a beautiful clock MTCSreenClock.apk a screensaver with a standard digital clock on a black background is called, you need to make sure that the MTCScreenClock application is installed.
If the application is installed, you can try setting screenPackage and screenClass parameters in settings.ini
5. Also in the module there is a "backup" for correct sound adjustment in MTC-Volume and MTC-Service .
#
The adjustment of sound in firmware on Android 4.4.4
6. Re-designation of OBD-device bluetooth.
Device names must be listed in the settings.ini file in obd_device parameter, separated by commas, in the form in which they are visible in the standard hands-free application. You can specify not names, but parts of names, for example:
Settings.ini
Obd_device = OBD, DUAL-SPP
7. Set the list of programs that are switched by the MODE button,
In settings.ini, set
Settings.ini
ModeSwitch = true
Programs are switched sequentially one after the other.
For correct sound switching, the applications used must be managed (play / pause) programmatically via intents. If the player does not support the start and stop playback of external intents, then you have to manually switch the sound.
When you click on the MODE button, the active application is searched for in the running list. Next, the application is sent a command (configurable in mode.ini) to close or pause the audio stream. After that, the default activation for the next application is launched and the application is sent a command to start playback (also configured in mode.ini)
#
Mode.ini
8. Disable the launch of the last running program.
Settings.ini
Clear_last_app = true
9. GPS time synchronization.
Settings.ini
Sync_gps_time = true
10. Turn on w-fi at startup.
Settings.ini
Wifi.on = true
Thank you Johnny! Love to see a lollipop version!
Hi Johny,
thx for sharing your custom Rom
Is this the openG or microG Version ?
Best regards
jun81 said:
Thank you Johnny! Love to see a lollipop version!
Click to expand...
Click to collapse
Working on it.
Do you guys prefer kikat or lollipop?
EagleSoldier said:
Hi Johny,
thx for sharing your custom Rom
Is this the openG or microG Version ?
Best regards
Click to expand...
Click to collapse
It's open gaps version because kitkat doesn't need micro g with 1 gb of ram. If someone else will be interested in MicroG I will give a try
personally lollipop works better..
jun81 said:
personally lollipop works better..
Click to expand...
Click to collapse
Done it, check the new thread.
thank you! gonna check it out!
I am waiting for the 800 x 480 Version to test it
EagleSoldier said:
I am waiting for the 800 x 480 Version to test it
Click to expand...
Click to collapse
Done, check it and report if screen saver is working
Johny DJ said:
Done, check it and report if screen saver is working
Click to expand...
Click to collapse
Awesome thanks
Will test it and report
Best regards
@Johny DJ
I've tested the ROM and everything is working well.
Screensaver don't work, I've activate the modules and placed the folders on GPS Card.
But the Screensaver don't appear.
To get root acsees , you have to type in Factorysetings instead of 126 -> *#hct#root# and then ok.
Overall a good ROM with some cool futures, hope you can fix the screensaver issue.
EagleSoldier said:
@Johny DJ
I've tested the ROM and everything is working well.
Screensaver don't work, I've activate the modules and placed the folders on GPS Card.
But the Screensaver don't appear.
To get root acsees , you have to type in Factorysetings instead of 126 -> *#hct#root# and then ok.
Overall a good ROM with some cool futures, hope you can fix the screensaver issue.
Click to expand...
Click to collapse
Yes you have to activate root once that's it.
Check folder mtc-manager on gps card called settings and change
# the inclusion of an alternative screen saver, when you specify false will work full-time mechanism:
screenClock=true
# Time off the screen if you do not set out full-time settings will be used in sec: change this value to lower just to test:
screenTimeout=300
# The name of the screensaver program package
screenPackage=com.microntek.screenclock
# Name Activiti screensaver
screenClass=MainActivity
# If the name of the package and Activiti is not specified, it will use a standard screensaver
how long does it take to boot after initial flash? I been waiting like 20 minutes still on a black screen
Thanks @Johny DJ for sharing this ROM with us!
I installed and tested 800 x 480 version on my RK3188 unit. Most of the functions are working flawlessly. Noticed a couple of things that i wanted to let you know:
1) The bluetooth app appears out of scale on the screen. Number 0 in the dial pad is cut off, and the refresh button on the contacts is also not visible. Please have a look at the screenshots below:
https://ibb.co/cde7NQ
https://ibb.co/hwP7NQ
2) I'm quite new to xposed. I copied the folders to the SD card, but do i need to enable any modules for the screen saver to work properly ? The screensaver appears in the screen, but the speed indicator shows null.
https://ibb.co/bJ3Cp5
https://ibb.co/dL3dU5
Thanks !
gabesir said:
how long does it take to boot after initial flash? I been waiting like 20 minutes still on a black screen
Click to expand...
Click to collapse
same problem 1024x600
re download the file, flash again.. no boot logo just a black screen.
champikasam said:
Thanks @Johny DJ for sharing this ROM with us!
I installed and tested 800 x 480 version on my RK3188 unit. Most of the functions are working flawlessly. Noticed a couple of things that i wanted to let you know:
1) The bluetooth app appears out of scale on the screen. Number 0 in the dial pad is cut off, and the refresh button on the contacts is also not visible. Please have a look at the screenshots below:
https://ibb.co/cde7NQ
https://ibb.co/hwP7NQ
2) I'm quite new to xposed. I copied the folders to the SD card, but do i need to enable any modules for the screen saver to work properly ? The screensaver appears in the screen, but the speed indicator shows null.
https://ibb.co/bJ3Cp5
https://ibb.co/dL3dU5
Thanks !
Click to expand...
Click to collapse
1. Tnx for info, will correct tomorrow and upload update. I don't have 800 x 480 unit so I cannot test.
2. Yes you have to enable all the modules to get screen saver working properly.
gabesir said:
re download the file, flash again.. no boot logo just a black screen.
Click to expand...
Click to collapse
Hm... I didn't have problems on 1024 x 600, will check and update and also add screen saver tomorrow.
Johny DJ said:
Hm... I didn't have problems on 1024 x 600, will check and update and also add screen saver tomorrow.
Click to expand...
Click to collapse
Do you use my files from the firmware? Hmm ... you did not even write about it .... sad. I looked at the screenshots.
Malaysk said:
Do you use my files from the firmware? Hmm ... you did not even write about it .... sad. I looked at the screenshots.
Click to expand...
Click to collapse
I'm sorry yes, I used one, and I didn't write or mentioned yet because it's not working in other update I was planning to write if it will work, but I think it's related to your android settings so will not work on other image because it+s much more complex, that's why I didn't mentioned yet.

[TOOL] Amazfit PACE Tuner (Windows & APK utilities)

I created these utilities to help people complete some tasks faster/easier without having to resort to ADB or other methods. The purpose of these programs is to assist the user fine tune their watch & add functionality.
Amazfit PACE Tuner (Windows)
Amazfit PACE Tuner (Android APP for Watch)
FEATURES
PACE Watch APP
* Display enabled Keyboards on watch
* Switch between Minuum Keyboard & Stock Huami
* Test typing keyboard area
* Control WiFi & Bluetooth
PACE Tuner Windows utility
* Check for ADB devices
* Install Minuum Keyboard on watch
Since I am not the author of the Minuum Keyboard I will not be including it in the package (sorry). You will need to search online (plenty of places to download it from) and download the APK.
Download Minuum-Wear.apk and place it in the same directory as the PACE Windows utility. Make sure the naming of the file is as exactly mentioned earlier in bold.
Click on the "Install Minuum" button in the Windows utility and wait for the install to complete.
* Display PACE watch data (device name & total km's ran)
* Display Watch and paired phone Bluetooth Information
Tweaks
* # Root required # Allow 3rd party software to be installed directly on the watch (you would need a file manager already installed on the watch)
* Toggle between show battery % screen while charging or the watchface (you may have to wake the screen once after making changes to see them)
* # Experimental # Enable find iPhone feature from watch (works by default on Android, so only use for iPhone users)
* # Experimental # Enable Haptic feedback (app needs to support this for it to work)
* Super Brightness - Sets watch to maximum allowed brightness. Manual 'L5' allows for a value of '180' in the settings. By enabling this option your setting will be '255' (maximum allowable).
* You can force restart your watch by double clicking on the PACE watch picture (typically bottom-right)
* Kill all ADB connections (in case Windows get confused or something)
I currently own and test the utilities on a Windows 7 (x64) based machine only and a PACE International version on stock firmware v1.3.6d
Downloads
https://drive.google.com/open?id=1Ho8RK1Fh858zX-aiWlNugNt8hg0B1XRg
File descriptions:
Amazfit PACE Tuner package vx.x [A zipped file that contains both the Windows & PACE apk utilities]
Amazfit PACE Tuner (Windows) vx.x.exe [The Windows utility - It uses ADB commands to perform various tasks on your watch]
AmazfitPACE_Tuner.apk [The PACE/Android utility which will be installed on your watch - USE THE WINDOWS UTILITY ABOVE TO INSTALL - DO NOT TRY TO SIDELOAD!]
Installation
-* Disclaimer *-
I am not responsible for anything bad that happens to your watch, your PC, or anything else bad that happens to you in direct or indirect relation to using this utility package. You are solely responsible for your actions.
Now that we got that out of the way...
PC
==
1. Make sure you only have ONE Android device connected to your PC (the PACE watch) and it is turned on!
2. Make sure you have extracted the following in the same folder:
A. Amazfit PACE Tuner (Windows).exe
B. Amazfit PACE Tuner.apk
C. Amazfit PACE Tuner Release Notes.TXT
2. Run the Amazfit PACE Tuner (Windows) utility
3. Click on the "Check for ADB devices" button and wait to see in the status window for one device to show up. If no devices show up, your watch may not be connected to your PC properly. If you see an error try click the button once more.
4. You can now click on the "Install PACE Tuner" button to install the APK utility on the watch.
@@@ Product Compatibility @@@
Amazfit PACE watch (1612) [Tested]
Amazfit PACE watch (1602) [Possible]
Stratos [Possible]
@@@ Platform compatibility @@@
Vista, W7
### The Windows utility version requires the .NET Framework v4.5 (minimum) to work ###
You may download .NET from here: http://www.microsoft.com/en-au/download/details.aspx?id=30653
RELEASE NOTES
^^^ ANDROID APP ^^^
v1.1
=====
* WiFi and Bluetooth toggle switches package
* Display version at bottom of app
v1.00
=====
* First release
&& Known bugs &&
None
============================================
============================================
^^^ Windows Utility ^^^
v1.2
=====
* Added Legends for Experimental and Rooted features
* Tweaks panel
> Renamed battery status screen to better reflect what it does
> Fixed some Tips descriptions when hovering mouse cursor
> Added Find iPhone feature (experimental) for similar functionality already enabled for Android
> Added Haptic Feedback control (vibrations need to be enabled in app to work)
> Added Super Brightness option (higher than Level 5 on watch)
v1.1
=====
* Optimised UI
* Introduced exception capturing/avoiding in code
* PACE Watch data panel
> Watch name
> Total KM's walked/run
* Bluetooth panel
> Bluetooth MAC address
> BT name
> Paired device's BT MAC address
* Tweaks panel
> Allow 3rd party software installation
> Toggle charging screen while on dock (show clock/watchface instead)
* Added reset ADB button
* Implemented Watch restart on double-click of watch picture (bottom right)
* Disabled Minuum Keyboard button for this version
v1.01
=====
Fixed app overwrite (for upgrades)
v1.00
=====
* First release
&& Known bugs &&
None
Frequently asked questions
Q: I am trying to launch the utility on the watch but I am getting errors/exceptions.
A: You have to use the Windows PACE Tuner utility to install the APK since it elevates privileges required for the app to run properly. If you try to simply sideload it it will fail!
Q: I have some great ideas or need more modifications - can you please do them asap?
A: Unfortunately for you I am not a 'proper' developer. I do this as a hobby on my (limited) spare time, so I can't commit to time or my abilities to be able to do what you imagine. Your ideas are of course welcome - I will do my best, but I will do it at my time.
XDA:DevDB Information
Amazfit PACE Tuner, Tool/Utility for the Smart Watches
Contributors
darkguset, darkguset
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2018-04-08
Created 2018-04-08
Last Updated 2018-04-08
darkguset said:
I created these utilities to help people complete some tasks faster/easier without having to resort to ADB or other methods. The purpose of these programs is to assist the user fine tune their watch & add functionality.
Amazfit PACE Tuner (Windows)
Amazfit PACE Tuner (Android APP for Watch)
FEATURES
PACE Watch APP
* Display enabled Keyboards on watch
* Switch between Minuum Keyboard & Stock Huami
* Test typing keyboard area
* Control WiFi & Bluetooth
PACE Tuner Windows utility
* Check for ADB devices
* Install Minuum Keyboard on watch
Since I am not the author of the Minuum Keyboard I will not be including it in the package (sorry). You will need to search online (plenty of places to download it from) and download the APK.
Download Minuum-Wear.apk and place it in the same directory as the PACE Windows utility. Make sure the naming of the file is as exactly mentioned earlier in bold.
Click on the "Install Minuum" button in the Windows utility and wait for the install to complete.
* Display PACE watch data (device name & total km's ran)
* Display Watch and paired phone Bluetooth Information
Tweaks
* # Root required # Allow 3rd party software to be installed directly on the watch (you would need a file manager already installed on the watch)
* Toggle between show battery % screen while charging or the watchface (you may have to wake the screen once after making changes to see them)
* # Experimental # Enable find iPhone feature from watch (works by default on Android, so only use for iPhone users)
* # Experimental # Enable Haptic feedback (app needs to support this for it to work)
* Super Brightness - Sets watch to maximum allowed brightness. Manual 'L5' allows for a value of '180' in the settings. By enabling this option your setting will be '255' (maximum allowable).
* You can force restart your watch by double clicking on the PACE watch picture (typically bottom-right)
* Kill all ADB connections (in case Windows get confused or something)
I currently own and test the utilities on a Windows 7 (x64) based machine only and a PACE International version on stock firmware v1.3.6d
Downloads
https://drive.google.com/open?id=1Ho8RK1Fh858zX-aiWlNugNt8hg0B1XRg
File descriptions:
Amazfit PACE Tuner package vx.x [A zipped file that contains both the Windows & PACE apk utilities]
Amazfit PACE Tuner (Windows) vx.x.exe [The Windows utility - It uses ADB commands to perform various tasks on your watch]
AmazfitPACE_Tuner.apk [The PACE/Android utility which will be installed on your watch - USE THE WINDOWS UTILITY ABOVE TO INSTALL - DO NOT TRY TO SIDELOAD!]
Installation
-* Disclaimer *-
I am not responsible for anything bad that happens to your watch, your PC, or anything else bad that happens to you in direct or indirect relation to using this utility package. You are solely responsible for your actions.
Now that we got that out of the way...
PC
==
1. Make sure you only have ONE Android device connected to your PC (the PACE watch) and it is turned on!
2. Make sure you have extracted the following in the same folder:
A. Amazfit PACE Tuner (Windows).exe
B. Amazfit PACE Tuner.apk
C. Amazfit PACE Tuner Release Notes.TXT
2. Run the Amazfit PACE Tuner (Windows) utility
3. Click on the "Check for ADB devices" button and wait to see in the status window for one device to show up. If no devices show up, your watch may not be connected to your PC properly. If you see an error try click the button once more.
4. You can now click on the "Install PACE Tuner" button to install the APK utility on the watch.
@@@ Product Compatibility @@@
Amazfit PACE watch (1612) [Tested]
Amazfit PACE watch (1602) [Possible]
Stratos [Possible]
@@@ Platform compatibility @@@
Vista, W7
### The Windows utility version requires the .NET Framework v4.5 (minimum) to work ###
You may download .NET from here: http://www.microsoft.com/en-au/download/details.aspx?id=30653
RELEASE NOTES
^^^ ANDROID APP ^^^
v1.1
=====
* WiFi and Bluetooth toggle switches package
* Display version at bottom of app
v1.00
=====
* First release
&& Known bugs &&
None
============================================
============================================
^^^ Windows Utility ^^^
v1.2
=====
* Added Legends for Experimental and Rooted features
* Tweaks panel
> Renamed battery status screen to better reflect what it does
> Fixed some Tips descriptions when hovering mouse cursor
> Added Find iPhone feature (experimental) for similar functionality already enabled for Android
> Added Haptic Feedback control (vibrations need to be enabled in app to work)
> Added Super Brightness option (higher than Level 5 on watch)
v1.1
=====
* Optimised UI
* Introduced exception capturing/avoiding in code
* PACE Watch data panel
> Watch name
> Total KM's walked/run
* Bluetooth panel
> Bluetooth MAC address
> BT name
> Paired device's BT MAC address
* Tweaks panel
> Allow 3rd party software installation
> Toggle charging screen while on dock (show clock/watchface instead)
* Added reset ADB button
* Implemented Watch restart on double-click of watch picture (bottom right)
* Disabled Minuum Keyboard button for this version
v1.01
=====
Fixed app overwrite (for upgrades)
v1.00
=====
* First release
&& Known bugs &&
None
Frequently asked questions
Q: I am trying to launch the utility on the watch but I am getting errors/exceptions.
A: You have to use the Windows PACE Tuner utility to install the APK since it elevates privileges required for the app to run properly. If you try to simply sideload it it will fail!
Q: I have some great ideas or need more modifications - can you please do them asap?
A: Unfortunately for you I am not a 'proper' developer. I do this as a hobby on my (limited) spare time, so I can't commit to time or my abilities to be able to do what you imagine. Your ideas are of course welcome - I will do my best, but I will do it at my time.
XDA:DevDB Information
Amazfit PACE Tuner, Tool/Utility for the Smart Watches
Contributors
darkguset, darkguset
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2018-04-08
Created 2018-04-08
Last Updated 2018-04-08
Click to expand...
Click to collapse
Nothing happens after clicnkg to check adb...
and adb is working on regular shell
eteles said:
Nothing happens after clicnkg to check adb...
and adb is working on regular shell
Click to expand...
Click to collapse
Could be because another service is already using ADB. Try hitting the big red "RESET ADB" button on the top right, wait a few seconds then try the "Check" again
It doesn't work... And pacefied ROM auto installation doesn't work either... It's probably the same issue...
Don't know why... There's no service running adb... Manual installation works for pacefied Rom, but you do not have a manual procedure...
eteles said:
It doesn't work... And pacefied ROM auto installation doesn't work either... It's probably the same issue...
Don't know why... There's no service running adb... Manual installation works for pacefied Rom, but you do not have a manual procedure...
Click to expand...
Click to collapse
Are you running the app from a folder with a patch that includes spaces, like "c:\users\my name\app"? Try moving the app to C:\ and make sure you have systemwide adb (adb.exe path is includes in $PATH).
lfom said:
Are you running the app from a folder with a patch that includes spaces, like "c:\users\my name\app"? Try moving the app to C:\ and make sure you have systemwide abd (adb.exe path is includes in $PATH).
Click to expand...
Click to collapse
Good point! If you have not declared the paths in Windows, calling adb commands from other folders will not work. Let us know if you need help with the declaration.
I had to move the program to "c:\adb" folder to get it to work. Then it worked fine. Enabling "* # Root required # Allow 3rd party software to be installed directly on the watch (you would need a file manager already installed on the watch)" allowed me to be able to update Watch Droid Assistant through the watch. Thanks for the program!
danbest82 said:
I had to move the program to "c:\adb" folder to get it to work. Then it worked fine. Enabling "* # Root required # Allow 3rd party software to be installed directly on the watch (you would need a file manager already installed on the watch)" allowed me to be able to update Watch Droid Assistant through the watch. Thanks for the program!
Click to expand...
Click to collapse
You are welcome!

Categories

Resources