Related
version 1.9
Hi, Following the requests here, I've wrote this application. Basically the application blinks the device LED every few seconds. The idea is to have some notification that the device is still alive. The application blinks differently depending on the status of the device.
Main features:
Including sequences for normal, low battery, no-signal, new message (Voice/SMS/MMS/EMail), Missed calls, appointments, wireless status (bluetooth and wifi), GPS status and charging level.
Almost all sequences can be configured via the settings application.
Sequences may include blinking the green and orange LEDs (in HD2 - may be configured in other devices), the keypad LED, vibration and playing a wav file.
If the radio is turned off or there is no signal, another orange blink occurs (in addition to the regular one).
When the phone is charging the orange LED lights constantly, every few seconds a sequence of green blinks according to the batter level occurs (20-40% - 1 blink, 40-60% - 2 blinks, 60-80% - 3 blinks and 80-100% - 4 blinks). If the battery is fully charged - the green led lights constantly.
Blink interval and length can be set via the registry. Different blink interval for idle mode and when notification exists (new message/missed call).
Running the link once starts the application, on blink sequence occurs. Running the link again runs the settings application from which the service can be closed.
Click to expand...
Click to collapse
Known issues
Custom LED id's are not saved to the registry in ver. 1.5.
It seems that there are some issues running "Dusk taskbar" or "SDKCERTS" along with Blinker.
Sometimes when the device is locked, the application stops working (until the device wakes up). After a soft-reset the application returns to behave as expected. I really don't know what instigates the problem or how to solve it... If anyone has a clue please leave me a message. Not solved, but might be better in ver. 1.1.
Update(16/4/2011): setting [HKCU\Software\Blinker\AllowUnattendedMode] to 0. Solved this issue for some. Also enabling "Don't suspend power" in S2U2 (under the advanced category) seems to help.
Update(14/5/2011): In ver. 1.4 a possibility to periodically wake the device, it seems that this solution might work around the issue.
gpobernardo may have found a solution to the problem.
[*]Non at the moment (I'm sure some will pop soon... )
System Requirements
.Net Compact Framework 3.5
Tested successfully on: HTC HD2 (Leo), HTC TD2 (Topaz), HTC Touch HD (Blackstone), HTC Touch2 (Mega).
But might work on other devices (please let me know if it works on other devices as well...)
ChangeLog
07/12/11 (v1.9) - from post #198
Fixed issue where service could not be started from the settings application.
07/12/11 (v1.8) - from post #196
Added GPS status support.
04/09/11 (v1.7) - from post #180
Fixed issue where Blinker halts at midnight (thanks gpobernardo).
20/08/11 (v1.6) - from post #177
Fixed issue where custom LED id's where not saved.
13/08/11 (v1.5) - from post #173
Added a notifications check when power state changes.
Added 3 more custom LEDs.
Shortcut link now point to the settings application instead of the service itself.
14/05/11 (v1.4) - from post #151
Rewrote the service project in c++ (Now the service requires significantly less memory when running).
Added ability to vibrate (see second post for further information).
Added ability to play a wav file in the sequence (see second post for further information).
Added sequences for "Appointment" and "New MMS".
Blinker now uses only the WM notification method.
Removed the "Use WM Notification" as it is no longer required.
Removed the "SMS Store" setting as it is no longer required.
Fixed issue where in lower resolution devices a scroll bar did not appear in the settings application.
Added "Advanced" tab in the settings application.
Added a "Wakeup notification" - this option will force the device to wake every couple of seconds. This should solve the "unattended issue" - but might affect the battery drain. This feature can be turned on under the "advanced" tab in the settings application.
Hibernates when no blinking is required.
Changed "AllowUnattendedMode" to "ForceUnattendedMode" and added a checkbox to control this value under the "advanced" tab.
06/04/11 (v1.3) - from post #101
Blinker can now use the notification system instead of directly check the Stores (thanks peterpan911 for the tip). This can be configured in the setting, under "Use WM Notifications".
Blinker can be configured to load on startup from the settings window.
Improved performance (thanks p50kombi)
Some minor interface improvement to the settings dialog.
10/02/11 (v1.2) - from post #77
Added possibility to set the green/orange LED id.
Added possibility to set the SMS store name.
Improved error handling in case SMS store is not found.
03/12/10 (v1.1) - from post #62
Added notifications for new message (SMS/EMail/Voice), missed calls and wireless status.
Added possibility to blink the keypad light as-well.
Added separate delay interval on new message or missed call.
Tweaked the unattended mode. The halting problem still exists, but it seems better now.
Added a configuration utility. To run it press the Blinker shortcut again (after blinker is already running).
06/11/10 (v1.0) - Initial release
Downloads
current version
Blinker V1.9
Previous versions:
Blinker V1.8
Blinker V1.7
Blinker V1.6
Blinker V1.5
Blinker V1.4
Blinker V1.3
Blinker V1.2
Blinker V1.1
Blinker V1.0
namwollem configuration tool (mortscript is required for this tool), more info can be found here
Click to expand...
Click to collapse
Acknowledgements
NetRipper and his LeoExtendedNotifications for the code to control the keypad light.
rwt33 and Pocket PC and SmartPhone 99% .NET MAPI for the code to access the SMS repository.
Power modes (code for unattended mode) from Shake'N'Wake by zzattack
htcjordi and his LedNotifications for the code to control the HD2 LEDs (and p50kombi for reminding me about this project).
lesscro for the logo.
Any suggestions or remarks are welcome
Z.
Configuration
Configuration
Blink Sequences
The blink sequences for the different situations can be customized. The blink sequences can be edited in the settings application under the "sequences" tab or by directly editing the correspnding registry key. A blink sequence is composed of blocks separated by comas (white space is not allowed). The following commands are allowed:
G<#> Blink the green led for a duration of # msec.
O<#> Blink the orange led for a duration of # msec.
P<#> Blink the pad light for a duration of # msec.
C<x><#> Blink a custom LED (x=a,b or c) for a duration of # msec.
Pl<WAV file> Play the specified WAV file.
V<#> Vibrate for a duration of # msec.
S<#> Sleep for a duration of # msec.
L<#> Loop over the following sequence (until the "E" block or to the end of the sequence) # times.
E Mark the end of the sequence to loop over.
example:
G100,O100,L10,G25,O25,E,S100,O100,Pl\Storage Card\My Documents\SomeFile.wav
This sequence will do the following:
Blink the green LED for 100msec, blink orange one for 100msec, then it will repeatedly (10 times) blink the green LED (25msec) and the orange LED (25msec). then it will pause for 100msec and finally turn the orange LED for 100msec. At the end it will play the file "\Storage Card\My Documents\SomeFile.wav".
Click to expand...
Click to collapse
Configuration
All the configuration can be performed via the settings application. All settings are saved to the registry, under "HKCU\Software\Blinker". The following keys are available:
ForceUnattendedMode (DWORD), (0 = Don't change anything, any non-zero value = force unattended mode), (default = 1)
Allows unattended mode (another try to solve the unattended issue).
GreenLed (DWORD), (default = 1)
The LED id to use for the green LED.
OrangeLed (DWORD), (default = 2)
The LED id to use for the orange LED.
VibrationLed (DWORD) (default = 1)
Sets the ID of the vibration LED.
CustomLed# (DWORD) (default = 0)
Allows to define 3 more LED IDs accessed as Ca, Cb and Cc from the sequences.
WakeupNotification (DWORD), (0 = off , any non-zero value = on), (default = 1)
Periodically wakeup the device (another try to solve the unattended issue).
ACNotifications (DWORD), (0 = disabled, any non-zero value = enabled), (default = 1)
Controls weather Blinker shows notifications when the device is plugged to power source.
BatteryThreshold (DWORD), (default = 50)
Sets the threshold (in percent) for the "low battery" status. When the battery level falls below this value Blinker will use the "LowBatterySequence" (see below). When the battery level is above the threshold the "NormalSequence" (see below) is used.
BlinkByNotification (DWORD), (1 = enabled, any other value = disabled) (default = 0)
Controls weather Blinker should blink according WM notifications, or should check the state of the different stores. When enabled Blinker checks the WM notifications state.
BlinkDelay (DWORD), (default = 10000)
The period between blinks (in msec).
NotificationBlinkDelay (DWORD), (default = 3000)
The period between blinks (in msec) when there's a new notification (unread message/missed call).
AppointmentSequence (STRING), (default = "P500,L4,S100,P100,E,S200")
The blink sequence (see below) to use when there is an active appointment notification.
BluetoothSequence (STRING), (default = "S100,G25")
The blink sequence (see below) to use when the bluetooth is turned on.
FullPowerSequence (STRING), (default = "O25")
The blink sequence (see below) to use when on AC power and battery is full.
GPSSequence (STRING), (default = "S100,O25,G25,O25")
The blink sequence (see below) to use when GPS receiver is turned on.
LowBatterySequence (STRING), (default = "O25")
The blink sequence (see below) to use when the battery is below the BatteryThreshold (see above).
MissedCallsSequence (STRING), (default = "P500,S200")
The blink sequence (see below) to use when after a missed call.
NewMailSequence (STRING), (default = "P500,L1,S100,P100,E,S200")
The blink sequence (see below) to use when there is an unread email message.
NewMMSSequence (STRING), (default = "P500,L2,S100,P100,E,S200")
The blink sequence (see below) to use when there is an unread MMS message.
NewSMSSequence (STRING), (default = "P500,L2,S100,P100,E,S200")
The blink sequence (see below) to use when there is an unread SMS message.
NewVoiceMessageSequence (STRING), (default = "P500,L3,S100,P100,E,S200")
The blink sequence (see below) to use when there is a new voice mail message.
NormalSequence (STRING), (default = "G25")
The blink sequence (see below) to use when the battery is above the BatteryThreshold (see above).
NoSignalSequence (STRING), (default = "S100,O25")
The blink sequence (see below) to use when there is no signal. This sequence is played after the NormalSequence/LowBatterySequence.
OffSequence (STRING), (default = "L5,O25,G25,S25,E,O500")
The blink sequence (see below) to use when the application shuts down.
OnSequence (STRING), (default = "L5,O25,G25,S25,E,G500")
The blink sequence (see below) to use when the application starts.
WifiSequence (STRING), (default = "S100,O25")
The blink sequence (see below) to use when the WIFI is turned on.
Click to expand...
Click to collapse
Z.
fantastic^^
Nice work!
Nice work chap!
I have installed it on my HD2, and so far seems to be running fine!
---------------------------------------------------
If the original author doesn't mind, I have made a small addition for those of us with Mortscript!
PLEASE NOTE: The first version I posted of this script had a small error, which wrote the registry entries as a STRING rather than a DWORD. This caused "Blinker" not to launch - due to an invalid data entry. I APOLOGISE for this - the joys of writing scripts after a long day at work. This is NOW FIXED, and tested on two different HD2s, and working fine.
View attachment Blinker.zip
This .ZIP file contains two files.....
blinker.ini -- a simple settings file that explains where (and how) to adjust the various settings for...
Notifications when connected to AC
LED colour change when battery level falls below a certain threshold %age
Time delay between "blinks"
Length of time of each "blink"
It also allows you to set the various "blink patterns" for...
Low Battery Blink Pattern
Normal Blink Pattern
No Service Pattern
Off Pattern (When "blink" is shut down)
On Pattern (When "blink" is turned on)
blinker_v1.mscr -- a script file that reads data from the .ini file, displays the settings, and writes them to the registry. It then restarts Blinker with your new settings activated!
At present I have assumed that you have installed the app into Device Memory, so you'll have to copy the two files into DEVICE/Program Files/Blinker
Have a play and see what you think!
A very big thank you to Zevele - and I hope you don't mind me making this little MOD for it already!!
Very nice program
If I turned flight-Mudus on / telephone off, another orange blink occurs (in addition to the regular one) as described
But, if there is suddenly no signal, it don't will be shown in anyway
(I simulated it with the death-grip->iPhone4
->....or there is no signal, another orange blink occurs
I have HTD HD2 with Official 1.72 WWE ROM.
I installed this cab and when I tried to launch, it crashed:
Blinker.exe
KeyNotFoundException
at
System.ThrowHelper.ThrowKeyNotFoundException()
at
System.Collections.Generic.Dictionary'1.
get_item(SequenceTypeKey)
at Blinker.CBliner..ctor()
ar Blinker.Program.Main(String args)
Any ideas?
Net Compact Framework 3.5 installed?
I have the 1.72 Vodafone, too...
Yep .net3.5 is installed.
I have checked, and I also have a large number of apps/mods that require .net3.5 to be installed, they all work.
namwollem said:
...and I hope you don't mind me making this little MOD for it already!!
Click to expand...
Click to collapse
Not at all, I'm glad that people show interest. I might add a configuration utility later, similar to the one you made.
Thanks for the mod.
kajos said:
...But, if there is suddenly no signal, it don't will be shown in anyway
(I simulated it with the death-grip->iPhone4
Click to expand...
Click to collapse
I didn't know the HD2 had a "death grip", how do you do it? I could use it to debug this feature.
hgalanos said:
I installed this cab and when I tried to launch, it crashed...
Click to expand...
Click to collapse
Is this the full log? If not, can you please post the full one. At the moment I have no idea why this error occurs, I'll need more clues to solve it...
thanks
Z.
Oops!
namwollem said:
PLEASE NOTE: The last version I posted of this script had a small error, which wrote the registry entries as a STRING rather than a DWORD. This caused "Blinker" not to launch - due to an invalid data entry. I APOLOGISE for this - the joys of writing scripts after a long day at work. This is NOW FIXED, and tested on two different HD2s, and working fine.
Click to expand...
Click to collapse
Mortscript fixed now! Please RE-DOWNLOAD from my original post.
Sorry for anyone who did used and suffered with problems!
Got it working.
I uninstalled, rebooted, reinstall, nothing. Still crashed with the erroe log I posted before.
Anyways, I decided to change my taskbar, so I uninstalled the Dusk taskbar, and SDKSert2015 (this was required for dust taskbar to work).
I rebooted.
I then reinstall 'blinker', launched, perfect. It works.
Very odd, but I don't care.
A job VERY well done, good work which is very handy and as you will see, more and more people will download and use it.
Great job, thank you.
Just though I would share the following:
I change the blink duration to '100', an the blink intervals to '5000'.
I might even change the duration to be '60'.
I found this better as you can't mistake it for an SMS, Email or missed call notification. The longer duration makes it clear that it is simply the phone being alive.
This is not criticism, simple personal taste. Without our your app, none of this would be possible.
Well done V.
hgalanos said:
Anyways, I decided to change my taskbar, so I uninstalled the Dusk taskbar, and SDKSert2015 (this was required for dust taskbar to work).
Click to expand...
Click to collapse
Dusk taskbar looks very nice, why did you ditch it? what are you using now?
I rebooted.
I then reinstall 'blinker', launched, perfect. It works.
Click to expand...
Click to collapse
I'm glad to hear that it works now...
Thanks,
Z.
Yes it is very nice, but luckily just by chance, it fixed this app.
I reverted back to what I had before dusk. Brians Black & White. The text is more legible than dusk.
hgalanos said:
I change the blink duration to '100'...
I might even change the duration to be '60'...
Click to expand...
Click to collapse
The blink duration was left by mistake... It does't affect anything... if you want to change the duration of the blink you need to edit it's sequence, if you want a blink of 60ms, change "NormalSequence" to "G60" and "LowBatterySequence" to "O60".
for detailed explanation on the configuration you can check the second post.
BTW, you can use a more complicated sequences other than just orange and green, this would make it even easier to differentiate from the normal (sms/email/missed calls) notifications...
Thanks,
Z.
zevele said:
The blink duration was left by mistake... It does't affect anything... if you want to change the duration of the blink you need to edit it's sequence, if you want a blink of 60ms, change "NormalSequence" to "G60" and "LowBatterySequence" to "O60".
for detailed explanation on the configuration you can check the second post.
BTW, you can use a more complicated sequences other than just orange and green, this would make it even easier to differentiate from the normal (sms/email/missed calls) notifications...
Thanks,
Z.
Click to expand...
Click to collapse
You are correct (of course) it did nothing when I changed it. I made changes as per post 2. Thank you.
New Version!
I have updated my mortscript so that ALL of the settings can now be changed from the .INI file!
You can now set custom "blink" patterns without having to use the registry! (I appreciate that its not a problem for most of us, but some ppl do not like to trawl thru the registry, so this makes life easier for those folks!)
Please see POST # 4 which has now been updated with a new .INI file, and a new v1.0 of the MORTSCRIPT file!
Enjoy!
And thanks again to Zevele for making this possible!
namwollem said:
I have updated my mortscript...
Click to expand...
Click to collapse
namwollem, thanks for the effort...
Z.
Fantastic addition to my phone,many thanx for this.
One question though,is there a way to have this Auto start rather than having to
go to Start menu and activating it ?
Shortcut
Marct77 said:
Fantastic addition to my phone,many thanx for this.
One question though,is there a way to have this Auto start rather than having to
go to Start menu and activating it ?
Click to expand...
Click to collapse
If you use File Explorer and COPY the executable (blinker.exe) from "PROGRAM FILES/BLINKER" and then PASTE SHORTCUT in "WINDOWS/STARTUP/" this will "autorun" the app each restart!
We are proud to announce our new Android App: "Gps Protector".
(Link to Android Market)
https://market.android.com/details?id=gps.trial&feature=search_result#?t=W251[/url] bGwsMSwxLDEsImdwcy50cmlhbCJd
Among the more than 30 functions, it has several innovative and totally new funcionalities (all included in an unique screen)
-Anti-Sleep function: Our phone will be our best friend while driving, avoiding you get asleep
-sos-SMS function: in case you suffer an accident, your phone will send a SMS up to 4 numbers, including your position.
-Safe and Brake distance and time
-Light on/off: your phone will detect if you should swich on your lights.
-Resting function: You'll be advertised if driving while estipulated time.
-G-Force
-Frontal and lateral inclination.
Others:
-Central Display: Shows travel statistical parameters such as average speed, maximum speed, maximum altitude, minimum altitude, departure time, and if happen, also shows 4 Alert functions: speed, height, resting advertisment and alarm function.
-Latitude
-Longitude
-Number of satellites available (in use)
-Number of satellites in view (not yet in use)
-Graphical representation of all satellites with their quality of reception, both available (green) and the view (in gray)
-Error in the precision of the satellite signal in meters
-Distance traveled in kilometers.
-Trip chronometer showing hours, minutes and seconds.
-Speaker + warning lights, to listen to messages from antisleep function
-Speed in km/h or miles/h. If we select a speed limit on the menu, then, if exceeding it, that area will blink red and shows visual and acoustic limit alert
-Altitude, in meters above sea level. Also flash red and visual and acoustic warning limit, if it exceeds the limit set by us in the menu.
-Clock. Function AM and PM. Flashes red if we drive for more of the time specified by us on the menu.
-Compass, indicating north by red hand, and indicating the distance in degrees from it.
-Route recording.
-Battery level.
I've posted this before, but it got buried and other people have asked about it so I figured I'd put it in its own thread. I find the notification light very annoying at night, but the only way I could find to shut off the notifications was buggy at best. This way will allow you to pick whatever triggers you have access too in tasker to control whether the light is allowed to turn on or not.
Some background: when a notification comes in, the system sets the file led_pattern in /sys/devices/virtual/sec/led to something non-zero. 3 is a slow blinking blue light, 1 is solid red, I forget what the others are now. When the screen is turned on, this is reset to zero, and when the screen is turned off, if the notification bar hasn't been opened (and the program with the notification hasn't been opened) the value is reset to something non-zero. So, I created a simple task to change the value back to zero:
Create a new task, then select Script>Shell. Enter the following command:
echo 0 > /sys/devices/virtual/sec/led/led_pattern
Check the 'Use Root' box
Then your task is done. Try it once to make sure you have accepted whatever superuser popups (you'll need to always allow this for it to work on its own).
Now create a profile, and for the context select Event>UI>Notification. You may need to check tasker on the accessibility menu if you haven't already (it will prompt you if necessary). Add whatever other contexts you want (I have a variable that's set when I turn on my nighttime menu that I check for so the light will blink during the day but not at night). You could easily just pick a block of time to turn it off instead. If you don't add other contexts this will always block your light, so make sure you've done some check to block it only at night. Add the task you created to this profile.
Next create another profile with the context State>Display>Display State set to Off, and add in the other secondary (ie night time) contexts. Call the same task you created above. This will prevent the light coming back on if you turn the display on and off at night after receiving a notification.
The only quirk I've found so far is that if you receive a google voice text, the light instantly turns purplish/pink normally. On my phone it will come on for a split second before tasker can kill it.
If you have any issues with this please let me know and I'll see what I can figure out.
I turn my phone over so the light and screen are face down. Case has a lip on it so screen doesn't touch the table. Problem solved.
-Hai guise don't feel like looking at 5 pages but I haz problems on the pre-alpha release and I don't know why.
joshindc said:
I've posted this before, but it got buried and other people have asked about it so I figured I'd put it in its own thread. I find the notification light very annoying at night, but the only way I could find to shut off the notifications was buggy at best. This way will allow you to pick whatever triggers you have access too in tasker to control whether the light is allowed to turn on or not.
Some background: when a notification comes in, the system sets the file led_pattern in /sys/devices/virtual/sec/led to something non-zero. 3 is a slow blinking blue light, 1 is solid red, I forget what the others are now. When the screen is turned on, this is reset to zero, and when the screen is turned off, if the notification bar hasn't been opened (and the program with the notification hasn't been opened) the value is reset to something non-zero. So, I created a simple task to change the value back to zero:
Create a new task, then select Script>Shell. Enter the following command:
echo 0 > /sys/devices/virtual/sec/led/led_pattern
Check the 'Use Root' box
Then your task is done. Try it once to make sure you have accepted whatever superuser popups (you'll need to always allow this for it to work on its own).
Now create a profile, and for the context select Event>UI>Notification. You may need to check tasker on the accessibility menu if you haven't already (it will prompt you if necessary). Add whatever other contexts you want (I have a variable that's set when I turn on my nighttime menu that I check for so the light will blink during the day but not at night). You could easily just pick a block of time to turn it off instead. If you don't add other contexts this will always block your light, so make sure you've done some check to block it only at night. Add the task you created to this profile.
Next create another profile with the context State>Display>Display State set to Off, and add in the other secondary (ie night time) contexts. Call the same task you created above. This will prevent the light coming back on if you turn the display on and off at night after receiving a notification.
The only quirk I've found so far is that if you receive a google voice text, the light instantly turns purplish/pink normally. On my phone it will come on for a split second before tasker can kill it.
If you have any issues with this please let me know and I'll see what I can figure out.
Click to expand...
Click to collapse
Tasker is a confusing app to me. I've tried to enter this in a few times but can't seem to get it to work. Is there any chance you could help me out and let me know more of a step by step? This guide seems to jump around a bit (it could be my extreme lack of experience with Tasker). This sounds like it is exactly what I am looking for though. The led on the GS3 is so freaking bright it lights up my whole room when it is charging at night. I *could* turn it over as suggested above but I have two problems with that:
A) We are better than our phones, aren't we? We should be able to get them to bend however we want! Why compromise?
B) I use my phone as my alarm clock and I don't want to fumble around to flip it over before I can silence it while I'm still mostly asleep.
Thanks for the guide. I will have to give this a try. I tried something else but it didn't seem to have any effect. Any idea where to find the other codes to make the LED turn on differently when you want?
---------- Post added at 06:29 PM ---------- Previous post was at 06:24 PM ----------
Relentless D said:
Tasker is a confusing app to me. I've tried to enter this in a few times but can't seem to get it to work. Is there any chance you could help me out and let me know more of a step by step? This guide seems to jump around a bit (it could be my extreme lack of experience with Tasker). This sounds like it is exactly what I am looking for though. The led on the GS3 is so freaking bright it lights up my whole room when it is charging at night. I *could* turn it over as suggested above but I have two problems with that:
A) We are better than our phones, aren't we? We should be able to get them to bend however we want! Why compromise?
B) I use my phone as my alarm clock and I don't want to fumble around to flip it over before I can silence it while I'm still mostly asleep.
Click to expand...
Click to collapse
Don't know if you are aware or not, but you can turn off the LED while charging using the build in settings. Go to Settings -> LED indicator and uncheck Charging. It shouldn't light up at all until you get some kind of notification.
ADC_112358132134 said:
Thanks for the guide. I will have to give this a try. I tried something else but it didn't seem to have any effect. Any idea where to find the other codes to make the LED turn on differently when you want?
---------- Post added at 06:29 PM ---------- Previous post was at 06:24 PM ----------
Don't know if you are aware or not, but you can turn off the LED while charging using the build in settings. Go to Settings -> LED indicator and uncheck Charging. It shouldn't light up at all until you get some kind of notification.
Click to expand...
Click to collapse
Yea I know. The thing is that I would like it to light up while charging (and change color when charged) just not between 11PM and 7AM
So, I haven't tested it for this (although I am now...) because I just have the charging LED setting turned off. I think this should work fine, although if you've killed the battery full notification you might get the green light coming on once charging completes (which you can probably deal with with an additional profile). Here's a more detailed description of the task setup:
1) Open Tasker and go to the 'Tasks' tab at the top of the screen.
2) Click on the green [+] at the bottom of the page to create a new task. Then name it something (LED kill?) and tap the green check button.
3) Click the [+] in the lower right hand corner to add an Action to your task.
4) Select 'Script', then 'Run Shell' from the Menus that pop up.
5) Under 'Command' type "echo 0 > /sys/devices/virtual/sec/led/led_pattern" without the quotes
6) Check the 'Use Root' box, then click the green check at the bottom of the window.
7) Now you should see the Task Edit window. Click the blue 'play' button at the bottom right of the window to run the task now. If you get a Superuser popup make sure you've checked the box to remember your selection, and accept the SU request. Now tap the green check box to save the task.
* Now you have a task that can turn off the light, but you need a way to trigger it. In tasker you do this by setting up profiles, which you can think of as triggers that will call the task. We want to trigger it to kill the LED whenever the phone turns it on. The phone will turn on or change the light at 2 different times:
A) When you receive a notification
B) When you turn off the screen (This will 'reset' the led if you turn on the screen and then turn it back off without clearing the notification) It will also turn on the led if the phone is charging and you've left that setting checked.
So, lets proceed:
8) Tap the 'Profiles' Tab at the top of the screen.
9) Tap the green [+] to create a new profile. Name it something like "Notification Kill" and click the green check box.
10) Select 'Event', then 'UI', then 'Notification' from the menus that pop up. Click the green check at the bottom of the Notification window that pops up (all the default settings are fine).
10a) At this point I think I was prompted the first time I did this to add Tasker to the accessibility permissions. If this happens, scroll down in the accessibility settings window that pops up and check the box next to Tasker. Then hit the back button to go back to Tasker.
11) Now select the task you just created (LED Kill) from the Task Selection window that pops up
* Now if you leave Tasker you should be blocking all notification LED lights. But you only want to turn them off at night! So you need to add another Context to this profile.
12) Long press on the Context (left hand side of the profile you just created where it says 'Notification *,*' and has a Orange ! triangle)
13) Select 'Add' from the popup, then select 'Time'
14) Pick the time range that you want the LED turned *OFF*. In your case you should pick From: 23:00 and To: 07:00.
15) Click the green Check and you're done with this profile.
* Now you've taken care of the (A) reason for the light coming on. But you need to take care of (B) as well, in case you check your phone during the 'night' hours, or if it's plugged in.
16) Repeat step (9), but name it 'ScreenOffLEDKill' or something easier to type.
17) Select 'State', then 'Display', then 'Display State' from the popup menus.
18) Make sure 'Off' is selected from the 'Is' dropdown menu, and click the green check box.
19) Select the task you created earlier again (LED Kill)
20) Repeat Steps 12-15 for this profile (Long press on 'Display State Off'...)
Now you should be set! If this still isn't working let me know and I'll try and troubleshoot it with you.
Relentless D said:
Yea I know. The thing is that I would like it to light up while charging (and change color when charged) just not between 11PM and 7AM
Click to expand...
Click to collapse
ADC_112358132134 said:
Thanks for the guide. I will have to give this a try. I tried something else but it didn't seem to have any effect. Any idea where to find the other codes to make the LED turn on differently when you want?
Click to expand...
Click to collapse
Just try different numbers. You can test it out and actually make the lights come on with the screen on from terminal emulator/adb or play with the tasker shell options. Try the following commands after getting superuser rights (by typing 'su' in the terminal emulator):
echo 7 > /sys/devices/virtual/sec/led/led_pattern
You get a slightly pulsing blue led. Substitute other numbers for the 7 and play around. You can turn off the LED by setting it to 0. You can also try echoing a value to led_b, led_g, or led_r, which will turn on the blue, green, and red leds (probably 255 is the maximum value). From what I've seen, whatever you set last overwrites whatever else you've done. So, if you set pattern to 7, then led_b to 255, the led will switch to solid blue from the pulsing light. If you then set led_r to 100, it will switch to dim red, but it won't maintain the led_b setting. I don't really have any interest in further customizing the led so I haven't played around with it much more. I haven't really figured out how to use led_blink either. If you find out more post here!
Josh
joshindc said:
Now you should be set! If this still isn't working let me know and I'll try and troubleshoot it with you.
Click to expand...
Click to collapse
Beautiful! I'll punch this in tomorrow at work. Thank you so much for helping me out!
Thank you so much for this post. Your method works perfectly. This is exactly something that I was trying to do but couldn't figure out. Great job! :good:
Just FYI, when Tasker updates from the market, it appears that sometimes the update disables the tasker accessibility service. If that happens this technique will no longer work. So, make sure to check that the accessibility service is still enabled after a Tasker update.
Thought I add a mapping of the colors to save some time to the next person...
Code:
0 = Disabled
1 = Static Red
2 = Blinking red (fast)
3 = Blinking blue (slow)
4 = Blinking red (slow)
5 = Green
6 = Static blue
7 = Static pulsing blue
Awesome, informative thread! Giving it a bump for those who want more, better information. Could anybody post the XML code in color-coded format? It helps me understand how to set it up exactly. Thanks to you for the hard work!
joshindc said:
I haven't really figured out how to use led_blink either. If you find out more post here!
Click to expand...
Click to collapse
This is a bit off topic, but since you went there I'll share some of my findings on led_blink. It turns out you can use it to create any color, but I haven't figured out how to make it... uh... blink.
At first, since led_blink usually contains 0 0 0, I thought it was simply the rgb colors with values up to 255 (just like with led_r, led_g, led_b). But, after a lot of trial-and-error, I found that it's actually hex. But that's not all. You also have to send led_blink additional information. Let me try to explain.
If you echo a string of numbers to led_blink, it seems to ignore the first two. The next two are red, then green, then blue (spaces are interpreted as zero, it seems). So, if you sent:
echo 00ff0000 > /sys/devices/virtual/sec/led/led_blink
you'd get a solid bright red light. But, here's the thing... led_blink would only contain "ff 0 0", since the first two numbers don't seem to stick. If you tried to send green the way you would intuitively think ("0 255 0"), you'd get led_blink set to "25 50 0" - which, to be fair, is still mostly green. Using the hex values plus the leading two digits, you can make the led any solid color you want.
So, what's left to figure out is:
What do the first two numbers mean, if anything? It doesn't seem to matter what they are.
How do you make it blink?
I swear, at one point when I was messing around with numbers (I wrote a Tasker task to make it easier to write to and read from led_blink) that I saw it rapidly blinking, but I don't know how I got there.
If someone can figure out how to get it blinking, Tasker would become a serious Light Flow alternative.
LightFlow can handle this and all notification aspects so much easier and with 1 button click (versus Tasker).
I use the hell out of Tasker, but I use LightFlow for ALL notifications - lights, sounds, vibrations, pop-up windows, etc. And you can set it to kill any notifications of any type you set by time of day. At 10:30pm all my lights stop flashing and come back on at 6:30am for example.
Does it work on any device? Or it is only for Galaxy S3
Sent from my GT-I9300 using Tapatalk 2
iirc led control from the play store has "night time" setting that will disable the led during times you specify
I'm using this command to turn off the led for specific Whatsapp groups, using specific contexts.
Sent from my GT-I9300 using Tapatalk 2
joshindc said:
So, I haven't tested it for this (although I am now...) because I just have the charging LED setting turned off. I think this should work fine, although if you've killed the battery full notification you might get the green light coming on once charging completes (which you can probably deal with with an additional profile). Here's a more detailed description of the task setup:
1) Open Tasker and go to the 'Tasks' tab at the top of the screen.
2) Click on the green [+] at the bottom of the page to create a new task. Then name it something (LED kill?) and tap the green check button.
3) Click the [+] in the lower right hand corner to add an Action to your task.
4) Select 'Script', then 'Run Shell' from the Menus that pop up.
5) Under 'Command' type "echo 0 > /sys/devices/virtual/sec/led/led_pattern" without the quotes
6) Check the 'Use Root' box, then click the green check at the bottom of the window.
7) Now you should see the Task Edit window. Click the blue 'play' button at the bottom right of the window to run the task now. If you get a Superuser popup make sure you've checked the box to remember your selection, and accept the SU request. Now tap the green check box to save the task.
* Now you have a task that can turn off the light, but you need a way to trigger it. In tasker you do this by setting up profiles, which you can think of as triggers that will call the task. We want to trigger it to kill the LED whenever the phone turns it on. The phone will turn on or change the light at 2 different times:
A) When you receive a notification
B) When you turn off the screen (This will 'reset' the led if you turn on the screen and then turn it back off without clearing the notification) It will also turn on the led if the phone is charging and you've left that setting checked.
So, lets proceed:
8) Tap the 'Profiles' Tab at the top of the screen.
9) Tap the green [+] to create a new profile. Name it something like "Notification Kill" and click the green check box.
10) Select 'Event', then 'UI', then 'Notification' from the menus that pop up. Click the green check at the bottom of the Notification window that pops up (all the default settings are fine).
10a) At this point I think I was prompted the first time I did this to add Tasker to the accessibility permissions. If this happens, scroll down in the accessibility settings window that pops up and check the box next to Tasker. Then hit the back button to go back to Tasker.
11) Now select the task you just created (LED Kill) from the Task Selection window that pops up
* Now if you leave Tasker you should be blocking all notification LED lights. But you only want to turn them off at night! So you need to add another Context to this profile.
12) Long press on the Context (left hand side of the profile you just created where it says 'Notification *,*' and has a Orange ! triangle)
13) Select 'Add' from the popup, then select 'Time'
14) Pick the time range that you want the LED turned *OFF*. In your case you should pick From: 23:00 and To: 07:00.
15) Click the green Check and you're done with this profile.
* Now you've taken care of the (A) reason for the light coming on. But you need to take care of (B) as well, in case you check your phone during the 'night' hours, or if it's plugged in.
16) Repeat step (9), but name it 'ScreenOffLEDKill' or something easier to type.
17) Select 'State', then 'Display', then 'Display State' from the popup menus.
18) Make sure 'Off' is selected from the 'Is' dropdown menu, and click the green check box.
19) Select the task you created earlier again (LED Kill)
20) Repeat Steps 12-15 for this profile (Long press on 'Display State Off'...)
Now you should be set! If this still isn't working let me know and I'll try and troubleshoot it with you.
Click to expand...
Click to collapse
I have à Sony xperia Z with jelly bean.
Do you know where i can find the folder there?
In the folder sys/devices/virtual there is no folder sec....
I can't find where i can turn off the charging led at night.
Thanks @joshindc! You are the man. I've been looking for something like this forever. This LED Profile works great! Thanks again. :highfive:
Cheers.
joshindc said:
So, I haven't tested it for this (although I am now...) because I just have the charging LED setting turned off. I think this should work fine, although if you've killed the battery full notification you might get the green light coming on once charging completes (which you can probably deal with with an additional profile). Here's a more detailed description of the task setup:
1) Open Tasker and go to the 'Tasks' tab at the top of the screen.
2) Click on the green [+] at the bottom of the page to create a new task. Then name it something (LED kill?) and tap the green check button.
3) Click the [+] in the lower right hand corner to add an Action to your task.
4) Select 'Script', then 'Run Shell' from the Menus that pop up.
5) Under 'Command' type "echo 0 > /sys/devices/virtual/sec/led/led_pattern" without the quotes
6) Check the 'Use Root' box, then click the green check at the bottom of the window.
7) Now you should see the Task Edit window. Click the blue 'play' button at the bottom right of the window to run the task now. If you get a Superuser popup make sure you've checked the box to remember your selection, and accept the SU request. Now tap the green check box to save the task.
* Now you have a task that can turn off the light, but you need a way to trigger it. In tasker you do this by setting up profiles, which you can think of as triggers that will call the task. We want to trigger it to kill the LED whenever the phone turns it on. The phone will turn on or change the light at 2 different times:
A) When you receive a notification
B) When you turn off the screen (This will 'reset' the led if you turn on the screen and then turn it back off without clearing the notification) It will also turn on the led if the phone is charging and you've left that setting checked.
So, lets proceed:
8) Tap the 'Profiles' Tab at the top of the screen.
9) Tap the green [+] to create a new profile. Name it something like "Notification Kill" and click the green check box.
10) Select 'Event', then 'UI', then 'Notification' from the menus that pop up. Click the green check at the bottom of the Notification window that pops up (all the default settings are fine).
10a) At this point I think I was prompted the first time I did this to add Tasker to the accessibility permissions. If this happens, scroll down in the accessibility settings window that pops up and check the box next to Tasker. Then hit the back button to go back to Tasker.
11) Now select the task you just created (LED Kill) from the Task Selection window that pops up
* Now if you leave Tasker you should be blocking all notification LED lights. But you only want to turn them off at night! So you need to add another Context to this profile.
12) Long press on the Context (left hand side of the profile you just created where it says 'Notification *,*' and has a Orange ! triangle)
13) Select 'Add' from the popup, then select 'Time'
14) Pick the time range that you want the LED turned *OFF*. In your case you should pick From: 23:00 and To: 07:00.
15) Click the green Check and you're done with this profile.
* Now you've taken care of the (A) reason for the light coming on. But you need to take care of (B) as well, in case you check your phone during the 'night' hours, or if it's plugged in.
16) Repeat step (9), but name it 'ScreenOffLEDKill' or something easier to type.
17) Select 'State', then 'Display', then 'Display State' from the popup menus.
18) Make sure 'Off' is selected from the 'Is' dropdown menu, and click the green check box.
19) Select the task you created earlier again (LED Kill)
20) Repeat Steps 12-15 for this profile (Long press on 'Display State Off'...)
Now you should be set! If this still isn't working let me know and I'll try and troubleshoot it with you.
Click to expand...
Click to collapse
Seems cool. Will try out
I stumbled upon a Tasker plugin from BlackDino that lets you change the Galaxy S3 LED settings. It might be a bit easier to use and gives some extra functionality.
http://forum.xda-developers.com/showthread.php?t=2117829
Hi all,
I am using LG Optimus Black, but my question is generic, about the navigation app Zanavi.
That's why I am posting this question here in "General" forum.
I have extensively searched the Internet, and also checked this forum thoroughly, but could not find the answer.
Question: How to interpret the Zanavi display?
I know that-
1. The green ring shows the current location (in Navigation mode, it is replaced by an arrowhead)
2. I can use the red pin (at right) to pin down (fix) the map.
When pinned, the map is centered on the current position (ring/arrowhead); and cannot be scrolled around.
3. To define the destination, I have to scroll the map to a new location, and then long-press on the destination place.
A balloon pops up. To set the destination, I should touch the X in the left half of the balloon.
This cretes a red bull's eye at that spot, and Zanavi calculates the route from the current location till this red bull's eye.
4. At the left side bottom of the screen, two things are displayed:
(a) Icon that shows a stylized arrow for the next turn, and (b) below that, distance to that turn.
I know this much, but need guidance for the rest:
5. In the middle-bottom part of the screen, a distance is shown.
Is this the total distance or from the current location to the destination?
6. Just above this distance, another text box shows some figure. What is this- ETA or duration of travel?
7. At the right-side bottom of the screen, a circle is shown like a clockface; with three "hands": red, green and black radial lines.
What does this display show?
8. Below this "clockface", there is yet another text box with another distance. What is this?
****
I also cannot work out the other usage-related doubts:
(a) Can I change the route laid out by Zanavi? If yes, how?
(e.g. The Google maps allows the user to drag a marker, which changes the route line also.
Is there a similar feature in Zanavi app for Android?)
(b) I can insert multiple POIs in the route (where one POI is red, and the rest are blue).
I am not clear if there is a method to change their order, so that I can travel in the correct sequence.
(e.g. A girl may want to go first to the hairdresser, and then to a party...)
Zanavi may be trying to re-calculate the entire route to cover all POIs in least-possible distance.
The user would not want that.
Thanks in advance!
maybe i can answer some of your questions:
5. this is the distance you need to drive on the road
6. it is the ETA (the time displayed on your watch when you arrive at your destination)
7. the red hand shows NORTH, the green hand shows the straight direction to the TARGET
8. this is the straight line distance (just a line straight through the air to your target)
(a) no. you can not change the route. but if you start to drive a different route, the app will adjust to your new route choice.
(b) you cant change the order of your waypoints
This version is deprecated. The new version is here
MCU version: MTCD_ХХХХ, MTCE_ХХХХ, MTCP_ХХХХ
Firmware version: 4.0.0 (01.02.2020)
Version of the latest OTA update: 4.2.2 (06.02.2022)
About firmware:
Firmware for car head units on the MTCD-MTCE platform with Rockchip PX5 (rk3368), PX6 (rk3399), PX30 (rk3326) processors and a screen resolution of 800x480, 1024x600 or 1280x720 based on Android 9 .
This is a further development of the Hal9k Mod v3 based on Android 8.
# Thanks AndroidAutoShop for the equipment provided for development.
The basic version of the firmware, in the form in which it is posted here, is distributed free of charge for private use and has no performance limitations
Commercial use of firmware or its parts and algorithms is prohibited
Any change to the firmware of the head unit is a potentially dangerous operation. Therefore, the Mod is provided on an “as is” basis. The author is not responsible for any possible negative consequences.
The main advantages of this firmware:
Stock design
High stability
Advanced functionality
Correction of existing errors and deficiencies in stock firmware
Customizability. All additions and modifications can be customized to your taste.
Changes are made directly in the application code, without using the Xposed framework
Increased responsiveness compared to the stock + the ability to independently improve this indicator
System requirements ( Settings> System> About device (About tablet) )
The model starts with px5 (rk3368) or px6 (rk3399) or px30 (rk3326_mid)
Android version starts with 9 or 8.0 or 6.0
The MCU version starts with MTCD or MTCE . Further there can be any letters, two, three, four - it does not matter.
"About device" screen samples
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It is also necessary to be able to enter the recovery mode.
Firmware Reviews:
Video review by Alex's Android Radio (English)
Video review by Alex's Android Radio (Deutsch)
Video review by ES. (Русский)
List of changes:
4.2.2 OTA-package (06.02.2022)
Fix for OK Google - App removed
Version 5 Notification
4.2.1 OTA-package (10.03.2021)
Minor bug fixes
Updated translations
4.2.0 OTA-package (06.09.2020)
Updated base firmware to version 202005
Minor bug fixes
Updated translations
4.1.0 OTA-package (25.07.2020)
Updated base firmware to version 201912
Changed rules for distributing processes by processor cores
This had a positive effect both on the system as a whole and on the GPS.
GPS starts working normally about a minute after waking up from prolonged (night) sleep
Added screen filter for additional screen dimming in night mode
For the convenience of controlling the brightness level in this mode, a slider has been added next to the daytime brightness
Added the ability to adjust the volume from third-party applications
Added configurable autostart of packages or activities and services after starting the OS
A new way to install additional launchers included in the firmware.
They are now installed as updates to the built-in launcher. The widgets are working fine.
If there are widgets in the folder with the launcher, then first you need to install them, and then the launcher
Replaced KGL and ZH launchers with HA and HA2. Added exclusive launcher from Alex's Android Radio
Other launchers not included in the firmware are located here
Fixed a bug with getting covers from some players and the Radio application
Added display of radio station logos on the widget in the built-in launcher
Added the ability to disable the display of pop-up messages over the launcher
Fixed a bug of restarting third-party applications that worked before going to sleep
Fixed image mirroring bug when switching from front to rear camera
Pressing the Fcam button again now closes the front camera app
Added the ability to disable the device shutdown message
Tap on the clock widget in the built-in launcher now starts the screensaver instead of the clock
Added GPS chip reset to factory defaults when GPS receiver advanced setting is disabled. Relevant for PX30
Updated ViPER4Android FX and GPS Test Plus apps
Updated translations
4.0.2 OTA-package (05.04.2020)
Added to "Advanced GPS receiver setup":
Possibility of a choice of frequency of measurements for the GPS receiver: 1,2,5 and 10 Hz
Ability to use BeiDou satellites instead of Glonass (only for PX5 and PX6)
The Navi button now switches between the navigation application and the last launched player, which is included in the "List of media players that should not work together"
Third-party applications can now set the time zone on the device. Tested on the latest version of Navitel 9.12.58
If the application has already been installed, then to enable this mode, you must reinstall it
Especially for BMW car owners, the function "Replacing key codes" from Mod v3 is returned
Added the ability to send media information from embedded applications to third-party widgets
Added the ability to control embedded media applications from third-party widgets
Added the ability to display logos of radio stations on the screen saver and in media widgets for the embedded radio app
Files with logos should be located in the Pictures/Radio folder created on the device’s internal memory
Format: PNG, JPG. Image sizes up to 320x320
File names: 10250.png (102.50 MHz) for the default group of radio stations. A10340.png, B10340.jpg, etc. (103.40 MHz) for other groups
A new design of pop-up messages with media information has been made
Added the ability to adjust the duration of the display of such messages
Added default album art for embedded media applications. You can replace them with yours in the settings.
Added the ability to include packages without a launcher in the white list
Fixed display of screen saver on devices where large font is selected in the settings
New in screen saver:
You can swap the indicators on the left and right
Added ability to select text color for indicators
In addition to Yandex.Weather, the temperature can be taken from Accuweather and Yahoo.Weather notifications
You can remove information about the track number from pop-up messages. This also affects the screen saver
Temperature and voltage now appear on the screen saver immediately after it starts
Fixed a bug in the rear view camera application, due to which the application crashed if you turn on the navigation bar
Pause for third-party media players when making a call or pressing the Mute button
4.0.1 OTA-package (09.01.2020)
Advanced configuration of the GPS receiver chip, which includes:
Use of Galileo and IMES satellite navigation systems in addition to existing ones. The number of visible satellites increased by about a third
Frequency of measurements of geolocation increased by 10 times. Navigation apps respond faster to changes in course or speed
The lag of the marker from the real position is reduced to the minimum, which means that navigation applications report faster about the upcoming maneuver
Enabled positioning acceleration AssistNow Autonomous. A cold start of the GPS receiver takes about one minute.
A dynamic navigation model is set - for cars, not for phones, as set by default
Any differential correction satellites are used
Unfortunately, not all of this works for PX30 devices, since they have a less functional GPS receiver chip
Updated GPS Test Plus application (see screenshot). The satellites marked in circles are GPS on the left of the screen and Galileo on the right
Ability to configure the speed of the USB OTG port (USB 2.0 or USB 1.1). This allows you to remove clicks that interfere with listening to music via USB DAC.
Ability to set default TTL in the range from 63 to 65
Ability to disable the Ethernet interface for using Wi-Fi without physically disconnecting the USB modem. Ability to configure Ethernet interface parameters
The ability to mirror the image from the front view camera by default. Useful for those who put a rear view camera on the front of the car.
Color selection for dynamic parking lines
The ability not to turn off the sound from other applications after launching the applications AV input and DVR
Gesture control and background playback enabled for the Video application
The ability to disable option "Mute button pauses playback"
Added a black list of applications that do not allow to start the screen saver. Now you can make the screen saver always run, except when the applications in the list are on the screen
The z-link application should work
Bugs fixed in the default launcher:
Now you can create widgets "Direct dial" and "Direct message". Both widgets will launch a phone call to the selected number
The radio frequency on the widget is not reset after changing the theme
Updated script from b-max for reconnecting freezing USB hubs
4.0.0 (24.11.2019)
Full root access is preinstalled (Magisk v20.1)
It is possible to write to system partitions, control access to applications, hide root from some applications, and install additional modules
The built-in update does not work on Rockchip devices.
Firmware is completely reodexed with optimization for the processor. This gives some increase in system speed.
Scrolling a long name in the phone book
Equalizer call button in Radio, Music and Video
New actions for buttons on the steering wheel, including double actions (example: the "Back" button will hang up when there is an active call)
All elements of the status bar are in the same style and change their color depending on the background color. All items can be disabled
Removed restriction on 4 icons in the status bar
Navi and F-Cam tiles added
Players added to the "List of media players that should not work together" no longer close when going to sleep
An alternative Equalizer has been added to OEM. It is installed as an update of the built-in Equalizer using the ApkInstaller application.
The interface shown in the screenshot appears only on devices with DSP !
Return to the stock version by removing updates in the properties of the "Amplifier" application
New screensavers
In applications, translation into different languages has been fixed and added (now 12 languages have been changed).
Thanks to our translation team:
de maus05, Toto1365, Ati_gangster
el grigoris_a
it mrgiaco, DanveRt
cs Bugscze
hr dankec2000
hu didu73
nl ZeroZorro
fr mykerinos1
sv kupa
es segu45
pl tomkam
ua DanveRt
Inherited from previous versions:
Added the ability to receive OTA updates via the Internet
Added Lada logo
Added support for init.d
You can put your scripts in the /etc/init.d folder and they will be launched at system startup
New default settings:
English language and date format, time zone CET
Screen saver timeout - 2 minutes, options added: 10 and 30 minutes
Watching video while driving - enabled
GPS time update - enabled
Navigation sound mode - mixing
Navigation mixing ratio - 2
Prohibition of connection to data services in roaming
Rreversing volume - 4
Screen brightness at night - 20%
Added the ability to adjust the speed at which the video will be disabled
Added auto tuning APN for Tele2
Deleted applications: System Tests and EasyConnected
Gmail, Google Speech Synthesizer, Google Maps and YouTube transferred from system applications to third-party
Now they can be simply deleted in Settings if they are not needed.
Added the latest Russian voice package for Google Speech Synthesizer. Speech synthesis works without a network connection
The latest Russian language pack for offline speech recognition is preinstalled
Added synchronization of Contacts and Calendar with Google account
Time zones updated to the latest version
Preinstalled ViPER4Android
Added the ability to change the ringtone to any of the ringtones in the folder (not for all Bluetooth modules)
Added the ability to change the default TTL to bypass restrictions on the distribution of the Internet from mobile devices
Added script from b-max for reconnecting freezing USB hubs
By default it is turned off, it can be turned on in the Mod Settings
Added ability to disable full-screen keyboard
Added the ability to transfer the status bar to the bottom of the screen (Experimental option)
A list of applications that have access to USB devices has been made
Allows you to get rid of the annoying request for access
In Launcher, the date is displayed in the format corresponding to the setting in the "Date and Time" menu
Added background for messages from CanBus app
Contacts application turned on
Contacts and Google applications now call via MTCDialer without additional settings
A list of applications that allow to start the screen saver has been made
You can add, for example, a third-party launcher or player
Added a white list of applications that do not close when going to sleep, with the ability to configure
A list of media players that restart after sleep has been made
I have included a PCRadio player on this list. Now it starts playback correctly after waking up from sleep, if it was started while going to sleep
In its settings, you must enable the switch "Resume playback when the application starts." You also need to remove it from the white list, if it was added to it.
Added the ability to disable restarting applications that worked before going to sleep
Made a list of navigational apps that muffle other sounds when playing voice prompts.
The list should include all navigation applications, including the one that is set by default to the Navi button.
Added the ability to assign the last launched navigation application to the Navi button, to switch between navigation and player
A separate list of navigation applications using the Speech Synthesizer has been made to muffle other sounds when playing voice prompts
To use it, you need to add the navigation application to the "List of navigational applications using TTS that muffle other sounds" and select "Text-to-speech engine that muffle other sounds"
Added volume control in the style typical of AV equipment from the 7floor module
Added the ability to display the volume control on top, in the middle or at the bottom of the screen
Added the ability to adjust the time during which the volume control remains on the screen after changing the volume value
A list of media players that should not work together has been made. This list is an addition to the corresponding system list.
If one of the players included in this list is launched, then the rest are closed
Added the ability to edit the list of applications that are switched by the Mode button
Added the ability to select applications that will run instead of stock apps. You can start your player with a button on the steering wheel
The size of the number on the volume control is increased and made white
Added items to Settings: Home app (launcher selection), Navigation bar (located on the left in some firmwares), Start navigation after boot, Mobile network and For developers
In Settings - About device, an item with system information has been added
An on-screen power button has been made in the status bar.
Single tap - start the screen saver.
Double tap - take a screenshot.
Triple tap - kill the active application.
Long press - shutdown menu.
Added items to the shutdown menu: Restart, Safe mode, Recovery mode
Added the ability to disable all elements of the status bar
Disabled by default: Home button, Storage icons, Volume and Screen brightness icons. The Back button is moved from right to left. All items are customizable
Added the ability to lock the device as on regular Android system
The lock is turned on after the device reboots or wakes up from sleep
You can also turn on the lock after starting the Android screensaver or manually from the shutdown menu
Added volume control depending on speed
Added display of pop-up messages with media information from third-party media players.
Third-party media players must be added to the appropriate list.
Added list of applications that will work in full screen mode (immersive mode)
In the Bluetooth application, the name field in the phone book is expanded
During a call, if you minimize the notification, the lower part of the screen remains clickable
Also, the notification does not overlap the status bar, if it is below
Added display of pop-up messages with information about the track played through A2DP
It is possible to adjust the size and color of the font and the duration of the message
In the Video application, the playlist is expanded and the replay is disabled by default
Sorting in alphabetical order, not case sensitive for lists of folders and tracks
In the Music application, the playlist is expanded and the replay is disabled by default
Added downloading lyrics from the network
The player is paused when an incoming call or pressing the Mute button
Sorted in alphabetical order, not case sensitive for lists of folders and tracks
Added display of pop-up messages with information about the track being played. It is possible to adjust the size and color of the font and the duration of the message
Skipped to the next folder in the list after playing the last track in the current folder in sequential playback mode
Added the transition to the previous/next folders by the buttons of the steering wheel seekdown/seekup and by a long tap on the screen buttons prev/next
Radio - the moving RDS text has been removed from the buttons of the saved stations. Added the ability to assign names to saved radio stations
If the name for the stored frequency has not been previously set, text from RDS is proposed.
Added display of pop-up messages with information about the radio station. It is possible to adjust the size and color of the font and the duration of the message
Added the ability to select a group of radio stations
If you are going to another place where other radio stations work, you can select another group and tune the stations again, and upon returning home, select the default group again and your settings will be restored
Added custom parking lines. Thanks for Incognito+
The functionality of Screensavers (Daydream) is included. This allows you to install any screensaver from the Play Market
In order for the Android screensaver to work, it must be turned on in the Mod Settings
A new screensaver has been added, which displays the time and date, information from players (not only stock ones), volume level, speed, as well as temperature and voltage if this data is available
To display the real temperature you need a CAN adapter and the presence of temperature in the status bar, and to display the voltage - MCU 2.93 and higher
It is possible to customize the appearance of the screen saver: colors, background image, maximum value for the speed indicator
There is a display of covers for most third-party players and radio station icons for PCRadio
For correct operation, I recommend adding your players to the "List of media players that should not work together"
There is a display of recommendations when moving along the route for Yandex.Navigator, Yandex.Maps, Google Maps, Sygic GPS Navigation & Maps
There is a temperature display from Yandex.Weather notification, if temperature data does not come from the CAN adapter
During the screen saver’s operation, the volume control is not shown
Added the ability to select from 12 regular screen savers
6 launchers and their widgets (AY, GS, HCT2, HCT3, KGL, ZH) have been added to OEM.
For Tasker fans, the ability to assign the numbers 1-9, 0, and the symbols * and # to the steering wheel buttons has been added.
Intent = "com.microntek.report.event"
Extra "type" = "key"
Extra "value" = button code.
Other changes aimed at improving stability and usability.
A lot of work has been done to provide support for new Android 9 firmware, although this is not visible from the outside.
The ideas of some improvements are taken from the module xposed-mtce-utils and other modules with permission of the author, MVG-V70. Thank him very much for that.
But implemented without using the Xposed framework.
Installation:
When switching from any other firmware, user data will be cleared automatically!
When upgrading from a previous version, wipe data is not required. But it is recommended if there are any problems.
For stable operation of the device, it is recommended to update the MCU firmware to the latest: 3.40 and higher, or to the latest version available for your device
You can obtain the MCU firmware from the seller of your HU or search in cs-x collection
Update from Android 9:
The installation is similar to a regular firmware update
Copy the firmware file update.zip to a USB flash drive / SD memory card formatted in FAT32
Insert a USB flash drive / SD memory card into the device
In the window that appears, click "Install"
After installation, the device will automatically restart one more time to complete the installation of Magisk.
When installing from a SD memory card, installation may take longer!
Update from Android 6, 8:
Requires updating the recovery version to Android 9
Simple and safe way: Use the application ModInstaller Pro (link to the application in the readme.txt file, which is located in the archive with the firmware or in my signature at the bottom of this post)
Complicated and unsafe way: look for information in this thread
Update from Android 8 with saving data:
Only for PX5 devices!
The archive contains 2 special packages that can be used to switch from Android 8 without data loss
Connect to the HU with Android 8 firmware (Mod v3.x) one USB flash drive formatted in FAT32.
There should be enough free space on the flash drive to save the device’s internal storage
Install the package update.zip from the folder backup8 from the same flash drive or from the SD card
A multivolume archive with your data (userdata*) will be created on the USB flash drive.
Install mod v4.x by the method above
After the full installation of Android 9, connect a USB flash drive with archive to the HU
Install the package update.zip from the folder restore9 from the same flash drive or from the SD card
Reboot the HU.
The first boot of Android 9 after restoring the archive from Android 8 may last longer than usual. The system needs time to convert data
This method does not guarantee full functionality of all third-party applications that were installed in Android 8.
If you encounter any problems - reset device to factory settings
Additions:
EasyConnected from stock firmware
Automatic backlight control for PX5-based head units
Internet speed in status bar
Autostart applications
FAQ:
Q: How to get OTA updates?
A: Information is on my site. You will find the link in the archive with firmware or in my signature at the bottom of this post
Q: How to automatically install my applications after installing the firmware?
A: Create the hct folder on the flash drive with the firmware, the apk folder in it and put your apk in it. They will be automatically installed after the installing the firmware.
Q: How to connect the OBD adapter?
A: This can be done both from the Bluetooth application, and from the Bluetooth item in the settings. The main thing - before you click on the adapter found, you must wait until the scan finished. Wait until the spinning circle disappears in the Bluetooth application or until the inscription "Search..." changes to the inscription "Refresh" in Settings. Then pairing goes smoothly. If the phone is already connected, you will need to temporarily disconnect it.
Q: How to start any application from a button on the steering wheel?
A: Mod settings - Manage applications - Applications that run instead of the stock . Assign any of the six applications that you don’t use to the button, then choose a replacement for it in the form of some kind of player, for example. This button will start your player
Q: Bluetooth MD725 does not work, although everything worked in Android 6!
A: If the MD725 type 2 Bluetooth module is installed in your HU, then it will not work in Android 9. The reason is that its driver was removed from Android 9.
Q: How do I know if I have such a Bluetooth module?
A: On the first page of the factory settings, in item BT, MD725 is selected. The getprop bt.md725.type command executed in the terminal answers "2"
Solution: replace the module with type 1
Q: Bluetooth SD-968 does not work, although everything worked in Android 8!
A: If the SD-968 Bluetooth module with firmware made in March 2017 or earlier is installed in your HU, then it works in Android 8, but does not work in Android 9.
Solution: replace the module driver /system/bin/sdsdk968 with the old version. Do not forget to set permissions 755 on the file.
Or replace the module with another type
Known Issues:
Mod is a modified factory firmware.
I can only be responsible for the changes in the device that I made. All of them are listed in the "List of changes" section.
Everything else, both good and bad, is inherited from the factory firmware.
I try to fix bugs found in the stock, but this I can’t always do it.
If you do not agree with this, do not install this firmware.
On some devices with a PX5 processor, the screen backlight sometimes does not turn on after exiting sleep mode.
After rebooting the device with the RST button or turning off the ignition for about 20-30 seconds, it continues to work.
The same problem exists on the stock and on newer version of the stock
Download:
PX5: Google Drive
PX6: Google Drive
PX30: Google Drive
If you want to help translate Mod into your language, please open this folder.
When you decide to place your translation in this folder, send me a personal message with your Google email. I will give you access.
If you think we need to translate other applications, write to me about it. I will add resources to the folder.
Version 4.0 screenshots
Version 4.0 screenshots
4.0.2 - 4.1.0 screenshots
Nice to see a dedicated English thread for this ROM here.Been waiting for this for a long time.
In regard to the ROM, nothing to say because it´s amazing. Been using this since Dec and have only had a black screen twice till date. With the stock Rom, i have this every week. So this is an improvement.
the only issue i have is my default music player 50% of the time dont automatically continue playing after waking up from sleep.
Good job Hal9k
Congratulations @Hal9k_ for this fantastic ROM....glad to know the english thread finally is here..
Enviado desde mi SM-G975F mediante Tapatalk
Thanks for starting new thread for Mod 4
Like to give some infos and suggestions about the newest Mod 4. My headunit is a PX5 from Dasaita with 4GB/32GB. Originally bought with Android 8. Installed in a Honda HRV 2016.
Until now I've found some issues in this rom. Generally it's working really well.
radio app: the field for the RDS text is imho too small. No chance to get any info from this tiny scrolling text while driving. Better redesign the app and place the RDS text below the frequency band with full width (see screenshot).
radio app: in night mode the additional settings (stereo, local, FMx..) in the right circle, where the frequeny or channel name is visible, cannot be seen because the fontcolor doesn't change with day/night mode. It's the same darkgrey like in day mode (see screenshot).
screen saver: the font for speed and volume looks very digitally ugly (old style) and is hard to read. Better use the same font like for the time.
sleep mode. I used the auto sleep mode to get the fast boot up. But now I had to replace a 10 month old battery of the car. Seems the rom takes to much energy while sleeping? Can you check this to be sure it's no problem in the rom? In the moment I'm using the complete shutdown to avoid problems. Also other people mentioned this topic.
Hal9k_ said:
Firmware version: 4.0.0 (01.02.2020) rebuild
MCU version: MTCD_ХХХХ, MTCE_ХХХХ
About firmware:
Firmware for car head units on the MTCD-MTCE platform with Rockchip PX5 (rk3368), PX6 (rk3399), PX30 (rk3326) processors and a screen resolution of 800x480, 1024x600 or 1280x720 based on Android 9 .
This is a further development of the Hal9k Mod v3 based on Android 8.
# Thanks AndroidAutoShop for the equipment provided for development.
The basic version of the firmware, in the form in which it is posted here, is distributed free of charge for private use and has no performance limitations
Commercial use of firmware or its parts and algorithms is prohibited
Any change to the firmware of the head unit is a potentially dangerous operation. Therefore, the Mod is provided on an “as is” basis. The author is not responsible for any possible negative consequences.
The main advantages of this firmware:
Stock design
High stability
Advanced functionality
Correction of existing errors and deficiencies in stock firmware
Customizability. All additions and modifications can be customized to your taste.
Changes are made directly in the application code, without using the Xposed framework
Increased responsiveness compared to the stock + the ability to independently improve this indicator
System requirements ( Settings> System> About device (About tablet) )
The model starts with px5 (rk3368) or px6 (rk3399) or px30 (rk3326_mid)
Android version starts with 9 or 8.0 or 6.0
The MCU version starts with MTCD or MTCE . Further there can be any letters, two, three, four - it does not matter.
"About device" screen samples
View attachment 4943947View attachment 4943949View attachment 4943951
It is also necessary to be able to enter the recovery mode.
Firmware Reviews:
Video review by Alex's Android Radio (English)
Video review by Alex's Android Radio (Deutsch)
Video review by ES. (Русский)
List of changes:
4.0.1 OTA-package (09.01.2020)
Advanced configuration of the GPS receiver chip, which includes:
Use of Galileo and IMES satellite navigation systems in addition to existing ones. The number of visible satellites increased by about a third
Frequency of measurements of geolocation increased by 10 times. Navigation apps respond faster to changes in course or speed
The lag of the marker from the real position is reduced to the minimum, which means that navigation applications report faster about the upcoming maneuver
Enabled positioning acceleration AssistNow Autonomous. A cold start of the GPS receiver takes about one minute.
A dynamic navigation model is set - for cars, not for phones, as set by default
Any differential correction satellites are used
Unfortunately, not all of this works for PX30 devices, since they have a less functional GPS receiver chip
Updated GPS Test Plus application (see screenshot). The satellites marked in circles are GPS on the left of the screen and Galileo on the right
Ability to configure the speed of the USB OTG port (USB 2.0 or USB 1.1). This allows you to remove clicks that interfere with listening to music via USB DAC.
Ability to set default TTL in the range from 63 to 65
Ability to disable the Ethernet interface for using Wi-Fi without physically disconnecting the USB modem. Ability to configure Ethernet interface parameters
The ability to mirror the image from the front view camera by default. Useful for those who put a rear view camera on the front of the car.
Color selection for dynamic parking lines
The ability not to turn off the sound from other applications after launching the applications AV input and DVR
Gesture control and background playback enabled for the Video application
The ability to disable option "Mute button pauses playback"
Added a black list of applications that do not allow to start the screen saver. Now you can make the screen saver always run, except when the applications in the list are on the screen
The z-link application should work
Bugs fixed in the default launcher:
Now you can create widgets "Direct dial" and "Direct message". Both widgets will launch a phone call to the selected number
The radio frequency on the widget is not reset after changing the theme
Updated script from b-max for reconnecting freezing USB hubs
4.0.0 (24.11.2019)
Full root access is preinstalled (Magisk v20.1)
It is possible to write to system partitions, control access to applications, hide root from some applications, and install additional modules
Firmware is completely reodexed with optimization for the processor. This gives some increase in system speed.
Scrolling a long name in the phone book
Equalizer call button in Radio, Music and Video
New actions for buttons on the steering wheel, including double actions (example: the "Back" button will hang up when there is an active call)
All elements of the status bar are in the same style and change their color depending on the background color. All items can be disabled
Removed restriction on 4 icons in the status bar
Navi and F-Cam tiles added
Players added to the "List of media players that should not work together" no longer close when going to sleep
An alternative Equalizer has been added to OEM. It is installed as an update of the built-in Equalizer using the ApkInstaller application.
Return to the stock version by removing updates in the properties of the "Amplifier" application
New screensavers
In applications, translation into different languages has been fixed and added (now 12 languages have been changed).
Thanks to our translation team:
de maus05, Toto1365, Ati_gangster
el grigoris_a
it mrgiaco, DanveRt
cs Bugscze
hr dankec2000
hu didu73
nl ZeroZorro
fr mykerinos1
sv kupa
es segu45
pl tomkam
ua DanveRt
Inherited from previous versions:
Added the ability to receive OTA updates via the Internet
Added Lada logo
Added support for init.d
You can put your scripts in the /etc/init.d folder and they will be launched at system startup
New default settings:
English language and date format, time zone CET
Screen saver timeout - 2 minutes, options added: 10 and 30 minutes
Watching video while driving - enabled
GPS time update - enabled
Navigation sound mode - mixing
Navigation mixing ratio - 2
Prohibition of connection to data services in roaming
Rreversing volume - 4
Screen brightness at night - 20%
Added the ability to adjust the speed at which the video will be disabled
Added auto tuning APN for Tele2
Deleted applications: System Tests and EasyConnected
Gmail, Google Speech Synthesizer, Google Maps and YouTube transferred from system applications to third-party
Now they can be simply deleted in Settings if they are not needed.
Added the latest Russian voice package for Google Speech Synthesizer. Speech synthesis works without a network connection
The latest Russian language pack for offline speech recognition is preinstalled
Added synchronization of Contacts and Calendar with Google account
Time zones updated to the latest version
Preinstalled ViPER4Android
Added the ability to change the ringtone to any of the ringtones in the folder (not for all Bluetooth modules)
Added the ability to change the default TTL to bypass restrictions on the distribution of the Internet from mobile devices
Added script from b-max for reconnecting freezing USB hubs
By default it is turned off, it can be turned on in the Mod Settings
Added ability to disable full-screen keyboard
Added the ability to transfer the status bar to the bottom of the screen (Experimental option)
A list of applications that have access to USB devices has been made
Allows you to get rid of the annoying request for access
In Launcher, the date is displayed in the format corresponding to the setting in the "Date and Time" menu
Added background for messages from CanBus app
Contacts application turned on
Contacts and Google applications now call via MTCDialer without additional settings
A list of applications that allow to start the screen saver has been made
You can add, for example, a third-party launcher or player
Added a white list of applications that do not close when going to sleep, with the ability to configure
A list of media players that restart after sleep has been made
I have included a PCRadio player on this list. Now it starts playback correctly after waking up from sleep, if it was started while going to sleep
In its settings, you must enable the switch "Resume playback when the application starts." You also need to remove it from the white list, if it was added to it.
Added the ability to disable restarting applications that worked before going to sleep
Made a list of navigational apps that muffle other sounds when playing voice prompts.
The list should include all navigation applications, including the one that is set by default to the Navi button.
Added the ability to assign the last launched navigation application to the Navi button, to switch between navigation and player
A separate list of navigation applications using the Speech Synthesizer has been made to muffle other sounds when playing voice prompts
To use it, you need to add the navigation application to the "List of navigational applications using TTS that muffle other sounds" and select "Text-to-speech engine that muffle other sounds"
Added volume control in the style typical of AV equipment from the 7floor module
Added the ability to display the volume control on top, in the middle or at the bottom of the screen
Added the ability to adjust the time during which the volume control remains on the screen after changing the volume value
A list of media players that should not work together has been made. This list is an addition to the corresponding system list.
If one of the players included in this list is launched, then the rest are closed
Added the ability to edit the list of applications that are switched by the Mode button
Added the ability to select applications that will run instead of stock apps. You can start your player with a button on the steering wheel
The size of the number on the volume control is increased and made white
Added items to Settings: Home app (launcher selection), Navigation bar (located on the left in some firmwares), Start navigation after boot, Mobile network and For developers
In Settings - About device, an item with system information has been added
An on-screen power button has been made in the status bar.
Single tap - start the screen saver.
Double tap - take a screenshot.
Triple tap - kill the active application.
Long press - shutdown menu.
Added items to the shutdown menu: Restart, Safe mode, Recovery mode
Added the ability to disable all elements of the status bar
Disabled by default: Home button, Storage icons, Volume and Screen brightness icons. The Back button is moved from right to left. All items are customizable
Added the ability to lock the device as on regular Android system
The lock is turned on after the device reboots or wakes up from sleep
You can also turn on the lock after starting the Android screensaver or manually from the shutdown menu
Added volume control depending on speed
Added display of pop-up messages with media information from third-party media players.
Third-party media players must be added to the appropriate list.
Added list of applications that will work in full screen mode (immersive mode)
In the Bluetooth application, the name field in the phone book is expanded
During a call, if you minimize the notification, the lower part of the screen remains clickable
Also, the notification does not overlap the status bar, if it is below
Added display of pop-up messages with information about the track played through A2DP
It is possible to adjust the size and color of the font and the duration of the message
In the Video application, the playlist is expanded and the replay is disabled by default
Sorting in alphabetical order, not case sensitive for lists of folders and tracks
In the Music application, the playlist is expanded and the replay is disabled by default
Added downloading lyrics from the network
The player is paused when an incoming call or pressing the Mute button
Sorted in alphabetical order, not case sensitive for lists of folders and tracks
Added display of pop-up messages with information about the track being played. It is possible to adjust the size and color of the font and the duration of the message
Skipped to the next folder in the list after playing the last track in the current folder in sequential playback mode
Added the transition to the previous/next folders by the buttons of the steering wheel seekdown/seekup and by a long tap on the screen buttons prev/next
Radio - the moving RDS text has been removed from the buttons of the saved stations. Added the ability to assign names to saved radio stations
If the name for the stored frequency has not been previously set, text from RDS is proposed.
Added display of pop-up messages with information about the radio station. It is possible to adjust the size and color of the font and the duration of the message
Added the ability to select a group of radio stations
If you are going to another place where other radio stations work, you can select another group and tune the stations again, and upon returning home, select the default group again and your settings will be restored
Added custom parking lines. Thanks for Incognito+
The functionality of Screensavers (Daydream) is included. This allows you to install any screensaver from the Play Market
In order for the Android screensaver to work, it must be turned on in the Mod Settings
A new screensaver has been added, which displays the time and date, information from players (not only stock ones), volume level, speed, as well as temperature and voltage if this data is available
To display the real temperature you need a CAN adapter and the presence of temperature in the status bar, and to display the voltage - MCU 2.93 and higher
It is possible to customize the appearance of the screen saver: colors, background image, maximum value for the speed indicator
There is a display of covers for most third-party players and radio station icons for PCRadio
For correct operation, I recommend adding your players to the "List of media players that should not work together"
There is a display of recommendations when moving along the route for Yandex.Navigator, Yandex.Maps, Google Maps, Sygic GPS Navigation & Maps
There is a temperature display from Yandex.Weather, if temperature data does not come from the CAN adapter
During the screen saver’s operation, the volume control is not shown
Added the ability to select from 12 regular screen savers
6 launchers and their widgets (AY, GS, HCT2, HCT3, KGL, ZH) have been added to OEM.
To install the launcher:
Run the ApkInstaller application, Install - OEM - Launcher code (for example, AY) - install .apk file
Press Home - the request "Use LaucherXX as Home" appears
Select the installed launcher and click "Just once" or "Always."
In the latter case, this question will no longer appear, a new launcher will always be used.
To install launcher widgets, you must:
Install .apk widgets and launcher
Add any widget to your desktop
Give permission (see screenshot).
Delete the launcher and reinstall (or clear the launcher data)
For Tasker fans, the ability to assign the numbers 1-9, 0, and the symbols * and # to the steering wheel buttons has been added.
Intent = "com.microntek.report.event"
Extra "type" = "key"
Extra "value" = button code.
Other changes aimed at improving stability and usability.
A lot of work has been done to provide support for new Android 9 firmware, although this is not visible from the outside.
The ideas of some improvements are taken from the module xposed-mtce-utils and other modules with permission of the author, MVG-V70. Thank him very much for that.
But implemented without using the Xposed framework.
Installation:
When switching from any other firmware, user data will be cleared automatically!
When upgrading from a previous version, wipe data is not required. But it is recommended if there are any problems.
For stable operation of the device, it is recommended to update the MCU firmware to the latest: 3.40 and higher, or to the latest version available for your device
You can obtain the MCU firmware from the seller of your HU or search in cs-x collection
Update from Android 9:
The installation is similar to a regular firmware update
Copy the firmware file update.zip to a USB flash drive / SD memory card formatted in FAT32
Insert a USB flash drive / SD memory card into the device
In the window that appears, click "Install"
After installation, the device will automatically restart one more time to complete the installation of Magisk.
When installing from a SD memory card, installation may take longer!
Update from Android 6, 8:
Requires updating the recovery version to Android 9
Simple and safe way: Use the application ModInstaller Pro (link to the application in the readme.txt file, which is located in the archive with the firmware or in my signature at the bottom of this post)
Complicated and unsafe way: look for information in this thread
Update from Android 8 with saving data:
Only for PX5 devices!
The archive contains 2 special packages that can be used to switch from Android 8 without data loss
Connect to the HU with Android 8 firmware (Mod v3.x) one USB flash drive formatted in FAT32.
There should be enough free space on the flash drive to save the device’s internal storage
Install the package update.zip from the folder backup8 from the same flash drive or from the SD card
A multivolume archive with your data (userdata*) will be created on the USB flash drive.
Install mod v4.x by the method above
After the full installation of Android 9, connect a USB flash drive with archive to the HU
Install the package update.zip from the folder restore9 from the same flash drive or from the SD card
Reboot the HU.
The first boot of Android 9 after restoring the archive from Android 8 may last longer than usual. The system needs time to convert data
This method does not guarantee full functionality of all third-party applications that were installed in Android 8.
If you encounter any problems - reset device to factory settings
Additions:
EasyConnected from stock firmware
Automatic backlight control for PX5-based head units
Internet speed in status bar
Autostart applications
FAQ:
Q: How to get OTA updates?
A: Information is on my site. You will find the link in the archive with firmware or in my signature at the bottom of this post
Q: How to automatically install my applications after installing the firmware?
A: Create the hct folder on the flash drive with the firmware, the apk folder in it and put your apk in it. They will be automatically installed after the installing the firmware.
Q: How to connect the OBD adapter?
A: This can be done both from the Bluetooth application, and from the Bluetooth item in the settings. The main thing - before you click on the adapter found, you must wait until the scan finished. Wait until the spinning circle disappears in the Bluetooth application or until the inscription "Search..." changes to the inscription "Refresh" in Settings. Then pairing goes smoothly. If the phone is already connected, you will need to temporarily disconnect it.
Q: How to start any application from a button on the steering wheel?
A: Mod settings - Manage applications - Applications that run instead of the stock . Assign any of the six applications that you don’t use to the button, then choose a replacement for it in the form of some kind of player, for example. This button will start your player
Q: Bluetooth MD725 does not work, although everything worked in Android 6!
A: If the MD725 type 2 Bluetooth module is installed in your HU, then it will not work in Android 9. The reason is that its driver was removed from Android 9.
Q: How do I know if I have such a Bluetooth module?
A: On the first page of the factory settings, in item BT, MD725 is selected. The [color = darkblue] getprop bt.md725.type [/color] command executed in the terminal answers "2"
Solution: replace the module with type 1
Q: Bluetooth SD-968 does not work, although everything worked in Android 8!
A: If the SD-968 Bluetooth module with firmware made in March 2017 or earlier is installed in your HU, then it works in Android 8, but does not work in Android 9.
Solution: replace the module driver /system/bin/sdsdk968 with the old version. Do not forget to set permissions 755 on the file.
Or replace the module with another type
Known Issues:
Mod is a modified factory firmware.
I can only be responsible for the changes in the device that I made. All of them are listed in the "List of changes" section.
Everything else, both good and bad, is inherited from the factory firmware.
I try to fix bugs found in the stock, but this I can’t always do it.
If you do not agree with this, do not install this firmware.
On some devices with a PX5 processor, the screen backlight sometimes does not turn on after exiting sleep mode.
After rebooting the device with the RST button or turning off the ignition for about 20-30 seconds, it continues to work.
The same problem exists on the stock and on newer version of the stock
Download:
PX5: Google Drive
PX6: Google Drive
PX30: Google Drive
Version 4.0 screenshots
Click to expand...
Click to collapse
Fantastic work @Hal9k_
I've just had a look at your website and saw the below, which seems to suggest that this base version is free, but to receive updates, you must pay; that is all (OTA) updates are paid for - is that correct? Or will you be releasing updates here, without payment? Please clarify.
Hal9k_ said:
If you want to support my project and receive timely online updates (OTA), subscribe to them here. This is the only way to get updates for the current version.
To do this, pay the indicated amount using one of the methods below.
Click to expand...
Click to collapse
I could be wrong, but are you saying the only way to get version v4.0.1 is to pay to receive the update via OTA? How about all future updates, those too paid?
Manfred.62 said:
Thanks for starting new thread for Mod 4
radio app: the field for the RDS text is imho too small. No chance to get any info from this tiny scrolling text while driving. Better redesign the app and place the RDS text below the frequency band with full width (see screenshot).
radio app: in night mode the additional settings (stereo, local, FMx..) in the right circle, where the frequeny or channel name is visible, cannot be seen because the fontcolor doesn't change with day/night mode. It's the same darkgrey like in day mode (see screenshot).
Click to expand...
Click to collapse
I agree in 100%. The radio player is a definite failure. I did not think that there could be a worse radio application than the one I had pre-installed, and it seems that it could be worse. In addition, the whole due to the low contrast between panels / fonts gives the impression as if it was created in low resolution.
marchnz said:
Fantastic work @Hal9k_
I've just had a look at your website and saw the below, which seems to suggest that this base version is free, but to receive updates, you must pay; that is all (OTA) updates are paid for - is that correct?
Or will you be releasing updates here, without payment? Please clarify.
I could be wrong, but are you saying the only way to get version v4.0.1 is to pay to receive the update via OTA? How about all future updates, those too paid?
Click to expand...
Click to collapse
On the russian forum is clear. This thread is just a replica of the russsian one ...but in english.
Only 4.0.0 version is free.
All the upgrades will be in form of OTA updates and only paying the 10usd (one unique payment) you can be able to get them.
If major update (like android 10) comes...I suppose he will create a mod 5.0.0 for free and OTA updates again by the same previous subscription (no other payment for 5.x.x upgrades if you were subscribed to 4.x.x)
Am I correct?
Enviado desde mi SM-G975F mediante Tapatalk
I am fine with paykng for support. I already sent serial number and paid just reading how to upgrade to 4.0 I have latest 3 hal9 is that andriod 8 don't care about keeping settings apps ect so I flash via sd card and I am done? It's will come auto after that?
Love this program has kept the px5 alive and looking forward to more
---------- Post added at 04:12 AM ---------- Previous post was at 03:55 AM ----------
Mod pro paid to oh well didn't want to save info anyways. How do I know my it will work sent payment no confirmation or anything sent via mail?
Hi everyone I ask you a little help. I tried to install on my erisin px5 modinstaller bro purchased from Hal. after installing the recovery with the Android 9 option the display remains black and the illuminated keys and the radio no longer starts. Can anyone tell me how to solve? thank you
Sorry for english
Right, i think it was 10 Dollars, then you get a serial wich you have to set to get OTA-updates.
I have payd both, Malaysk an Hal9k_ because both have deserved it.
Regards
Manfred.62 said:
sleep mode. I used the auto sleep mode to get the fast boot up. But now I had to replace a 10 month old battery of the car. Seems the rom takes to much energy while sleeping? Can you check this to be sure it's no problem in the rom? In the moment I'm using the complete shutdown to avoid problems. Also other people mentioned this topic.
Click to expand...
Click to collapse
This will be coincidence rather than cause. Was the battery flat at any time? Can leave my car sitting idle for weeks with auto sleep mode and the battery holds just fine. Auto sleep mode hardly consumes power.
Thank you very much for opening a thread where the px6 is included with this Rom, I have installed the full version and so far it is luxurious, until now and since I put it on, I have not observed any fault attributable to the Hal9k, I have a fault but it is hardware already that for a while and for no apparent reason, it crashes when starting, it remains in the cameras without any speed stuck in the car, then it returns with normal operation and occasionally the camera comes out again.
As I have been able to verify, it gives me that it is the motherboard, I have already spoken with the Chinese and, in guarantee, it sends it to me.
With respect to hal9k, as I said, everything is correct, right now without failures.
Many thanks to hal9k for making a good rom and to @ segu45 in this case for their Spanish translations.
Sorry for my English
Greetings.
---------- Post added at 01:11 PM ---------- Previous post was at 01:00 PM ----------
ikerg said:
On the russian forum is clear. This thread is just a replica of the russsian one ...but in english.
Only 4.0.0 version is free.
All the upgrades will be in form of OTA updates and only paying the 10usd (one unique payment) you can be able to get them.
If major update (like android 10) comes...I suppose he will create a mod 5.0.0 for free and OTA updates again by the same previous subscription (no other payment for 5.x.x upgrades if you were subscribed to 4.x.x)
Am I correct?
Enviado desde mi SM-G975F mediante Tapatalk
Click to expand...
Click to collapse
Well, as I understand it, it is as you indicate, you pay € 10 and the updates that come will no longer have to make any more payments.
I do not know if when I can Android 10 if it is possible, we will have to pay again since I understand that it will be a full Rom and not a mod.
However, as far as I know, with that one payment, for the moment everything that is going out, is coming via OTA to all those who have paid.
Greetings.
With version 4.0.1, I can continue to play audio even when switching to AV In. However, when I get out of AV In my SWC for skipping songs no longer works. Only restarting the unit fixes the problem. I'm on a PX6 unit for reference
@Manfred.62
I'll think about the Radio app
I didn't change anything about sleep mode.
@marchnz
There, on the site, it is written:
The code will continue to work all the time while I make updates for this version of the Mod.
"this version" is Mod v4.
Perhaps in the future a new free version will be released with all the changes that will be made by then, if a new version of the stock firmware appears and I decide to do it. But I can’t promise it for sure.
@ikerg
The thread is dedicated to Mod v4. Won't look that far.
@scoote2014
I usually reply to emails in the evening, Moscow time.
@mrtony95
Tony, I read in my email that you've already done everything yourself. Is that so ?
@Realistichat
I couldn't reproduce it. Make a video
I have a problem with the installation of the update. I have a px5 MTCE device, unfortunately it throws out an error as in the picture.
Does anyone have any idea how to solve it?
MCU
Hi, i have this model of PX5:
https://pl.aliexpress.com/item/32848518906.html?spm=a2g0s.9042311.0.0.27425c0fAao1In
Wich MCU should I install? MTCE GS 3.4? Actually I have Mtcd_gs_v2.9c
ModInstaller Pro
Hello, good afternoon, I made the donation but I don't know how to get ModInstaller Pro for updating my equipment.
can you help me
thanks
tricz said:
I have a problem with the installation of the update. I have a px5 MTCE device, unfortunately it throws out an error as in the picture.
Does anyone have any idea how to solve it?
Click to expand...
Click to collapse
Hi,,
"rk3368" is PX6... so you have downloaded the mod for PX6-Devices, but you own a PX5-Device. Download the right package, copy it to your USB or SD ans install
Yours
Markus
---------- Post added at 05:45 PM ---------- Previous post was at 05:43 PM ----------
j-miguelr said:
Hello, good afternoon, I made the donation but I don't know how to get ModInstaller Pro for updating my equipment.
can you help me
thanks
Click to expand...
Click to collapse
Hi,
you will get a mail from hal9k with a link to your personal modinstaller-apk. Download, move it to your device (USB / S-Card) and install...