Related
A small app to switch a wireless devices with additional functions.
In resource you can customize the layout of buttons, background color and the name and font size.
The program supports the launch with the parameters (without displaying the main window)
Sorry for my English, Thank's google translator...
Can you create QVGA version of this application. I tried on my HTCMagician but can't full names of buttons.
Can you post sources for switcher?
For the ones interested in replacing the resources, as that's the fun part of this little app right here.
Super-Quick-Guide
To change the lay out of the Buttons use Resource Hacker.
Resource Hacker won't export the gif's correctly.
Use CFF Explorer and export to raw then add .png
(you can see it in the resource clearly).
Edit the png, flatten all layers save and remove extension, re-import back into CFF explorer.
Rebuild Header and Save, should do the trick.
Resign file.
Attached s Quick example of Modification
Hey Noonski , i could be wrong but your example seems to be a QVGA....why dont you just share it ?
Noonski said:
For the ones interested in replacing the resources, as that's the fun part of this little app right here.
Super-Quick-Guide
To change the lay out of the Buttons use Resource Hacker.
Resource Hacker won't export the gif's correctly.
Use CFF Explorer and export to raw then add .png
(you can see it in the resource clearly).
Edit the png, flatten all layers save and remove extension, re-import back into CFF explorer.
Rebuild Header and Save, should do the trick.
Resign file.
Attached s Quick example of Modification
Click to expand...
Click to collapse
i can only say спасибо xrom for this; i <3 you for this
af974 said:
Hey Noonski , i could be wrong but your example seems to be a QVGA....why don't you just share it ?
Click to expand...
Click to collapse
Sorry it's VGA.
But theoretically you can change the Button Values and the Graphics to fit QVGA.
here the first german version.
Noonski said:
Sorry it's VGA.
But theoretically you can change the Button Values and the Graphics to fit QVGA.
Click to expand...
Click to collapse
Would you mind posting the VGA version? Does it scroll or are the bottom buttons cut-off? Looks great XroM.
mwalt2 said:
Would you mind posting the VGA version? Does it scroll or are the bottom buttons cut-off? Looks great XroM.
Click to expand...
Click to collapse
Buttons where cut of i didn't re position of the Buttons.
Give me a minute.
Unsigned VGA version by popular request.
Just open the exe in http://www.angusj.com/resourcehacker/
on the left side you will find the item where you can change button size.
(Dialog 104)
Code:
104 DIALOG 0, 0, 140, 198
STYLE DS_MODALFRAME | WS_POPUP | WS_CAPTION | WS_SYSMENU
CAPTION "XroM_Switch GUI"
LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US
FONT 8, "System"
{
CONTROL "Toggle WiMax", 1001, BUTTON, BS_OWNERDRAW | BS_MULTILINE | WS_CHILD | WS_VISIBLE, 7, 16, 62, 18
CONTROL "Switch off\n GPRS", 1007, BUTTON, BS_OWNERDRAW | BS_MULTILINE | WS_CHILD | WS_VISIBLE, 70, 16, 62, 18
CONTROL "Toggle WiFi", 1002, BUTTON, BS_OWNERDRAW | BS_MULTILINE | WS_CHILD | WS_VISIBLE, 7, 36, 62, 18
CONTROL "Flight mode", 1008, BUTTON, BS_OWNERDRAW | BS_MULTILINE | WS_CHILD | WS_VISIBLE, 70, 36, 62, 18
CONTROL "Toggle\nBluetooth", 1003, BUTTON, BS_OWNERDRAW | BS_MULTILINE | WS_CHILD | WS_VISIBLE, 7, 55, 62, 18
CONTROL "Reset PPC\nsilent", 1009, BUTTON, BS_OWNERDRAW | BS_MULTILINE | WS_CHILD | WS_VISIBLE, 70, 55, 62, 18
CONTROL "Bluetooth in\nvisible", 1004, BUTTON, BS_OWNERDRAW | BS_MULTILINE | WS_CHILD | WS_VISIBLE, 7, 74, 62, 18
CONTROL "Reset PPC", 1010, BUTTON, BS_OWNERDRAW | BS_MULTILINE | WS_CHILD | WS_VISIBLE, 70, 74, 62, 18
CONTROL "Toggle phone", 1005, BUTTON, BS_OWNERDRAW | BS_MULTILINE | WS_CHILD | WS_VISIBLE, 7, 94, 62, 18
CONTROL "Power Off", 1011, BUTTON, BS_OWNERDRAW | BS_MULTILINE | WS_CHILD | WS_VISIBLE, 70, 94, 62, 18
CONTROL "Disconnect\nGPRS", 1006, BUTTON, BS_OWNERDRAW | BS_MULTILINE | WS_CHILD | WS_VISIBLE, 7, 114, 62, 18
CONTROL "Suspend", 1012, BUTTON, BS_OWNERDRAW | BS_MULTILINE | WS_CHILD | WS_VISIBLE, 70, 114, 62, 18
CONTROL "Restart Manila", 1015, BUTTON, BS_OWNERDRAW | BS_MULTILINE | WS_CHILD | WS_VISIBLE, 7, 132, 62, 18
CONTROL "Lock PPC", 1016, BUTTON, BS_OWNERDRAW | BS_MULTILINE | WS_CHILD | WS_VISIBLE, 70, 132, 62, 18
}
Change the Font in
In (String Data 2502)
Code:
STRINGTABLE
LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US
{
40016, "Tahoma"
40017, "22"
}
New German version incl. new skin.
Can't translate reset confirmation text and shortcut description in "about"!
Hint: Screen capture looks bad, better download
Vibrate toggle would also be good.
QVGA
Noonski said:
Sorry it's VGA.
But theoretically you can change the Button Values and the Graphics to fit QVGA.
Click to expand...
Click to collapse
camoooon ... share also a QVGA version
I'm not so smart with resource hacker and so on....
pleeeease
S-Line said:
Vibrate toggle would also be good.
Click to expand...
Click to collapse
I try to do this...
Thank XroM
It's a great and necessary soft, i need and try to translate to french but some text like before Turn Off in Russian are in hard code with ressouce heacker i don't see these text; can you help me PL?
XroM made the new XroM Switch version for Touch HD. Removed buttons specific for HTC Max devices. I translated the program to English.
Enjoy.
Any feedback is welcome.
Too bad it doesn't have an option for vibrate. That would make it the perfect app for long right press. Yes, this is a feature request.
pizzaman79,
In last version (XroM_Switch_HD_eng) exist option for vibrate.
pizzaman79, version I uploaded vibrates by default
Sorry, i meant an option to disable volume (switch between volume on an vibrate), just like the fourth option from long key press.
Or is that what's included in the latest version?
Hello, good evening,
I often listen to music so I decided to increase (or rather booster) the sound of my Windows Phone Samsung Omnia 7.
And then disaster ... 15/30 above the noise level, the sound crackles ... so I decided to give the level has its original value then:
1 - 1D - 7D - C2 - 22 - 5F - F5 - 12
System Gain Attenuation:
7 / 110 / 0
Gain Attenuation Class
7 / 0 / 0
Device Gain (max / min)
7 / 1200 / -500
It audience.cfg
Click to expand...
Click to collapse
However, even with the return of its parameters (of orgine), the sound crackles to 25/30.
Better than before but still not normal
So I need your help ... What to do? ! : '(
I said that to change its values, I was in:
the Diagnosis Mode on my Omnia 7 (number: # # 634 #).
I was then in the audio settings (number: * # 0002 * 28345 #).
Click to expand...
Click to collapse
However, I noticed that the adjustment was taken into account after reboot but it is only temporary ... Indeed, if I plugged in a headset or make a call, the sound of the phone will reset to sizzle.
I hope you can help me.
PS: I would like a solution without reset please!
I do not want to lose my fi
Thank you in advance.
PS 2: The steps I did to re-set the volume correctly but without success:
Increase Speaker Volume
• Enter the phone dialer
• # # 634 #, tap Call.
• Enter code: * # 0002 * 28346 # or * # 0002 * 28345 #
• Tap: Get, Under the Device Gain (max / min)
• First Box: 7
• Second Box: 16000 to change
• Third Box Set to 0
• Tap: Set
• Be sure to set IS audience.cfg That is
• Tap: Start
• Tap: Home
• Restart your phone.
• After reboot, enter the Same menu tab and just get to verify the settings
Increase Headphone Volume
Note: Make sure your headphones are plugged in first
• Enter the phone dialer
• # # 634 #, tap Call
• Enter code: * # 0002 * 28346 # or * # 0002 * 28345 #
• Tap: Get Under the Device Gain (max / min)
• For "device gain" leave number 5, set in 1100 (max) and -1100 (low)
• Tap: Set
• Verify That AUDIENCE.CFG is ON
• Tap: Start
• Tap Home
• Restart your phone.
• After reboot, enter the Same menu tab and just get to verify the settings
Click to expand...
Click to collapse
Good day / evening
{
"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"
}
Download here : SlimJB
If you get su lost message, just reboot to cwm and again reboot to system. It will fix the problem.
So what is my rom ?
Basically tweaked for performance and battery
Stock based (I love stock UI)
Custom kernel tweaked for balance between performance and battery
Stripped un-needed stuff from the kernel. Small size
Custom SlimJB scripts to further enhance the rom
Comes with OTA update feature
Find out other features..
How to install :
The normal method
Download, place in sdcard. Aroma is self- explanatory..
In cwm, mount all partitions. Somehow the script doesn't do it..
Just make sure you wipe cache and do a factory reset before installation.
In aroma, choose installation method as default
How to use Goo Manager :
Goo Manager will automatically scan for updates on every boot and every 24 hours. You can change this in the app settings.
To update using Goo Manager, just click on the notification. The download will be automatically started. You can also see the changelog in the app.
To manually check for updates, open the app and click on check for updates.
DO NOT INSTALL OPEN RECOVERY. If the app asks you, just choose that you have a recovery installed.
Edit : Since our param driver is bugged, goo manager won't be able to install the update. You will have to manually install it.
( Kernel Features )
fs: CIFS module
fs: Fsync control (Combined dyn fsync control)
fs: Mount noatime and nodiratime by defualt [franciscofranco]
fs/aio: Asynchronous io performance improved
mm: SLUB memory allocator
arm: ThumbEE
arm: Optimzed rwsem algorithm [ezekeel]
arm: Remove old version sha1
arm/vfp: Build with neon
arm/crypto: ARM AES and SHA-1 crypto
arm/topology: Linaro lastest patches
ab8500_asoc: Sound control
ab8500_bm: Charger control
ab8500_chargalg: Charge cycle control
ab8500_chargalg: Real charged notification
lib: Optimzed CRC32 algorithm [ezekeel]
lib: GNU C version memcpy
net: More choices of TCP congestions
rcu: jRCU [Joe Korty]
swap: swap supports
zram:: zram supprots for android
mali: Utilization control
mali: PP scheduler tweakable
mali: PM sampling rate tweakable
mali: L2 cache max reads writable
mali: Disable mali state tracking
block: 8 io schedulers
snvet: Reduce the waketime 6s -> 1s
sched: Enable arch_power by default
sched: ARM multi-core schduler
debug: Remove Samsung debug code [Adi_Pat]
debug: Disable KGDB [Adi_Pat]
debug: Remove frame pointer [Adi_Pat]
debug: Fixed mismatches [Adi_Pat]
debug: Android logger as module (free 4mb RAM)
mxt224e: Sensitivity improved by defualt
mxt224e: Touch booster control
max224e: Touch sensitivity control
bcmdhd: PM_FAST by default
kernel:Lzop compression
ramdisk: Custom bootanimation supports [diego-ch,thank you!]
ramdisk: Lzop compression
ramdisk: Init.d scripts
ramdisk: ClockworkMod Recovery 6.0.2.8 [diego-ch]
ramdisk: T.W.R.P Recovery 2.4.4.0 [TeamWin]
cpufreq: 12 cpu governors
cpuidle: Deeper sleep state
makefile: Useful optimization flags
toolchain: Linaro GCC 4.6.2
How to tweak the kernel furthermore :
In short :
Same as CoCore E
In long :
Here are some intructions/tips about how to play with the kernel.
Terminal is needed.
If you want to change the values,it needs su permission.
If you get 'Permisson denied',you need su permisson.
You can cd to the folder first,then do echos.
( Boot time )
CoCore-E boots faster than stock normally.
How to check boottime?
* TWRP kernel boottime is longer(around 8000ms).Because of that big ramdisk!
( Bootanimation )
Put bootanimation.zip in /system/media/.
Recommend you changing the permission to 0666.
If there is no bootanimation.zip,kernel will show you Samsung's.
( CPU governors )
* OnDemand has been patched cpu idle detection
* PegasusQ is taken from SiyahKernel (new version)
* Personaly,I use PegasusQ/OnDemand(Q)/HotPlug
* To be honest,most of custom governors are based on ondemand/interactive
* OndemandQ is a new governor.It will hotplug cpu when screen turns off only.
* If you mind the battery life time,choose HotPlug.It hotplugs cpu frequently.
* Interactive updated to linux-android-3.4 [Thanks!Aditya!]
* Zzmoove is new version(0.3),i havent tested fully.
( IO schedulers )
* Please choose them by yourself
* Personaly.i use SIO.
( Deepest sleep state )
Stock deepest is 3.Now it is 4 by default.
Deepest supported is 5.
To change:
* PegasusQ(hotplug governors) works badly with 5
* OnDemand works well with 5
* Please note that it wont increase the using time but standby time.
To check the cpuidle state:
( zRAM SWAP )
[zRAM]
zRAM is optimized for Android.
It is not lazy anymore.
Using zRAM will take a little CPU,because it needs to compress/decompress memory.
Setup disksize first: (example: 96mb= 96×1024×1024)
* Lager size more RAM will be compressed.
Enable:
Code:
mkswap /dev/block/zram0
swapon /dev/block/zram0
To check how many does it use:
* You can get other info in its sysfs
[SWAP]
Format/resize your SdCard via computer first.
Enable:
( Init.d script )
Please install busybox in system first
I recommend you install busybox via apps
Create a new folder named 'init.d' in /system/etc
Set the permisson of init.d foler to 0777(rwxrwxrwx) (at least has read and exec permission)
Set the owner to 0.0 (root root)
Put some scripts (any name you like) in init.d folder with permisson 0777 (rwxrwxrwx) (at least has read and exec permission)
Scripts with right permisson will be runned when system boots.
( Charger control )
Please note that this control can damage your battery/phone.
If your battery/phone damaged,read the top of #1 post.
Lower current makes the charging longer,but protects battery.
Too high current can burn your battery!
I recommend you that dont set the max limited current over 900mA.
To change the AC max limited current: (range: 100 - 1100) (default: 600)
To change the USB max limited current: (range: 50 - 1100) (default: 500)
* Your values wont be applied immediately.They will be applied when plug charger.
* I recommend you input some values like 300,350,600...
* The value(s) that is not in range will be reverted to stock default value(s).
* Increase USB current properly can implement USB fast charging
To get the charging current:
When you plug charger:
( Charge cycle control )
To increase the recharge times:
(Default: 3)
* 5 is recommended.If you want more recharging.
* This probably can make phone charge deeper,do it once a month if you want.
( Real charged notification )
Well,please let me call it notification.
To be honest,it needs to check manually.
* You can use Rootexplorer to view this file.
* When it says "First full charging reached",then the UI should show you charged 100%
But it is not the real full charged.
* When it says it is the real full charged,you can unplug the charger.
* When you are charging and do a reboot will reset the counter.
* According to my experiments,it needs 1-2 hours to charge to real full.
( Sound control )
Please note that listening to too high volume music over 1 hour can damage your ears.
Or makes your speaker/headset overload.
(5.0+) Sound control has been enhanced.Please read it carefully.
Switch to sound control folder:
cd /sys/mo*/snd_soc*/p*
Use RootExplorer to view this folder,you will see a lot files.
Sound hacks wont take effects immediately.It depends on powering on/off ab8500 asoc.
Stop music for 5s to let ab8500 asoc shut down fully,then turn on music.
You need to enable XXXXX_con first,then tweak the XXXXX_bit.
After enabling XXXXX_con,it will be applied when codec powers on or it wont.
How do i check whether it has shuted down or not?
dmesg | grep codec
If you get "Disable ab850x",it has been powered off.
I will explain how to calculate the binay values below.
If we echo 0000 to something,system will consider it as 0.
But that doesnt matter.
'(default)' means that is my default setting in sound control.
[AnaGain3] (Headset audio path):
Ana stands for 'analong'.This is analong gain.
To enable control:
To tweak volume: [volume 0(default, +31dB) > 34 > 68(stock) > 85 > 87]
* Most values(except 0,34,68,85) will make the volume lost balance.
* If you hear too much noise with 0,34 is recommended.
* It is nice to use 0 with large speakers(audio output)
[HsXDigGain] (Headset Digital Gain)
HsL means left channel.HsR is the right.
To enable control:
To tweak:
* 0000: +8 dB gain (default)
* 0001: +7 dB gain
* ....: -1 dB step
* 0111: +1 dB gain
* 1000: 0 dB gain
* 1001 to 1111: -inf dB gain (mute)
* If you use +31 dB AnaGain3 + +8 dB DigGain,the result will higher than +39dB!
* Be careful,when the volume is too high,codec will power off automatically.
* Experience the differences between digital gain and analong gain by yourself.
[HsLowPow] (Headset low power mode)
This lowpow mode is enabled by driver normally.
If you want high performance audio instead of LPA(low power audio),
You can disable it.
To enable control:
To tweak:
* 0: Normal Operation (default)
* 1: Hs drivers in Low Power
[HsDacLowPow] (Headset DAC low power mode)
DAC is Digital-to-Analong Converter.
This lowpow mode is enabled by driver normally.
To enable control:
To tweak:
* 00: Normal Operation (default)
* 01: Hs DAC drivers in Low Power
* 10: Hs DAC in Low Power
* 11: Hs DAC and Hs DAC drivers in Low Power
[HsHP] (Headset high pass filter)
This high pass filter is enabled by driver normally.
If you want more low freq sound,disable it.
To enable control:
To tweak:
* 0: Headset high pass filter disabled (defualt)
* 1: Headset high pass filter enabled (offset cancellation enabled)
[ClassDDithHPGain]
ClassD is a kind of amplifier.
According to the documents,our ClassDs only relate to Handsfree(speaker).
To enable control:
To tweak:
* Gain control for the high pass component of dithering filter
* 0000: Minimum gain
* ....:
* 1010: Maximum gain (default)
[ClassDDithWGain]
* Gain control for the white component of dithering filter
* 0000: Minimum gain
* ......:
* 1010: Maximum gain
[ClassDHiVol]
This is a gain of speaker.But +2dB only.
echo 1 > classdhivol_con
Say 1(default) to enable:
* In fact,our speaker is right channel only!
[MicXGain] doesnt work...I will add more in the future.
How to calculate the binary values?
We use HsXDigGain as example.
The gain step is "+1".
In binary: So the values will like these:
0+1 = 1 | 0001: +7 dB
1+1 = 10 | 0010: +6 dB
10+1 = 11 | 0011: +5 dB
11+1 = 100 | 0100: +4 dB
..... | ......
[Experts!]:
This method can work on any ab850x codec platform!
Play music,reduce the volume.
Now we are going to edit the codec registers.
E.G:
AnaGain3:
HsDigGain: (left/right channel)
Disable all lowpow mode:
* These hacks will restore when codec power off.
( Touch Booster control )
What is touch booster?
It can jump the cpufreqs(in fact,not only cpufreqs) to high value when you touch to improve the experience of touching.
Disabling this can save some power.
To disable: (default: enable)
To change the boost freq: (default: 800000) (Vaild: 200000,400000,800000,1000000)
( Touch Sensitivity control )
If you play some games like Temple Run,higher sensitivity might help.
To change: (stock: 22) (default: 17) (range: >0)
* Lower value,higher sensitivity.
* Turn on/off screen to apply the changes
* Parameter "threshold" to check the changes
* When charging,the threshold will be forced replace by threshold_chrg
* With high sensitivity,your touches can be applied even screen coveres something.
( Fsync control )
To disable fsync: (0=disable 1=enable)
* Disabling fsync can improve io performace,
but it can make the data which hasnt been written lose when a sudden poweroff comes.
* Disabling fsync or enabling dyn_fsync will make param driver fail to store data
That means your "reboot recovery" will be failed.
To enable dynamic fsync:
* Dynamic fsync will sync all buffers when screen turns off,
* If there is a heavy io load,the screen might stick for seconds.
* This is an experiment feature.
( WiFi suspend pm control )
To enable: (default: disable)
* Enable=PM_FAST (Faster) Disable=PM_MAX (Powersave)
( Mali GPU )
Mali debug level
Disabling can speed up a bit
* Higher level,more messages will be printed in dmesg,system will slow down
Mali L2 max reads control: (Stock:28kb,Default:48kb(max))
* Some values will slow down graphics
* If not sure,keep default
Mali PM sampling rate: (Default: 1000ms)
Mali PP scheduler tweaks: (Default: disable)
* Enabling this,Some places will over ahead,choose by your self
Mali Utilization sampling rate: (Stock:500ms,Default:1000ms)
How often report a mali utilization.
* Keep this default if unsure.
Mali Utilization control
(Default: low_to_high 192 high_to_low 64)
This probably will relate to the smoothness.
Our driver will report a mali utilization frequently.
This utilization(range: 0~255) means the load of mali.
If utilization is bigger than low_to_high,driver will request higher hardware performance(highest APE/DDR OPP).
If utilization is smaller than high_to_low,the driver will store the requested OPP(uses low OPP).
OPP can be understood as freq simply.
To check mali utilization values:
Then you will see the utilization it reports.
When it says SIGNAL_HIGH,it will request highest OPP.
When it says SIGNAL_LOW,it will request lowest OPP.
Press Ctrl+C to stop printing.
In my Temple Run,it seldom reaches low_to_high(192).
That means you can reduce low_to_high to trigger higher OPP requirement.
For smoothness and less powersaving:
Set low_to_high between 100-192.
( TCP congestions )
Supported:
To check all the available options:
To change to other option:
* I use YeAh
* In fact,every congestion is disigned for different environments.
* Google to learn deeper!
( EGL Driver )
To remove sw egl driver:
Edit /system/lib/egl.cfg
To
* According to my feelings: after removing sw egl driver,UI is faster
( Service Mode )
In dialer, type:
Secret code:*#197328640*# (service mode)
Secret code:*#9900*# (SysDump)
In SysDump:
Disable fastdormancy might help 3G standby time (Depends on your mobile base station)
* Google to learn more
RAM DUMP is a debugger.Most of us wont use it.So disable it. (Tap it,every tap will make a reboot,until it shows you "Disable....",then tap disable,it is disabled)
* Google to learn more about secret code
( Multi-core scheduler )
What is it? How does it work?!
(Default: 2) (Echo 0/1/2)
0 : No power saving load balance.
1 : Fill one thread/core/package first for long running threads.
2 : Also bias task wakeups to semi-idle cpu package for power savings.
( Logcat )
Well,we have made android logger(logcat) as module to free more RAM.
Some guys request logcat.
Now we provide you a workaround:
Create a new init.d script:
Then you can use logcat command.
Almost tweaks will be restored to default after reboots.
So you can make your tweaks as init.d scripts to apply them when boots. :laugh::laugh::laugh:
Kernel How-To's :
( FAQ )
Q: What firmware does this kernel support?
A: All ROM bases on stock firmwares,all stock firmwares.
Q: Why my phone lags a lot!
A: Please check the cpu load.If it always goes very high,some apps are using cpu!And please check that you are not in PowerSaving mode.
Q: Why my phone lags after booting in some minutes?!
A: Media Scanner is running in the background. More media files(especially HD videos),more time it will take
Q: Why my phone cannot go to deep sleep when screen is off!!!
A: Fix it yourself. It is app(s) taking the wakelock. Not kernel.
Q: Do I need to wipe anything when flashing this kernel?
A: NO
Q: My phone rebooted suddenly!!! What can i do?!
A: Give me /proc/last_kmsg and logcat. Will try my best to fix.
Q: Hey!Your kernel has issue!No-fills CPU shows me a wrong freqs!Fix it!
A: This is NOT issue.Every I9070 kernel will have this problem.Because No-fills will show you Dynamic Min/Max scaling freqs,DVFS(dynamic voltage and frequency system) will adjust Min/Max freq according to system load.
Open SetCPU,it shows you real freqs.Or check sysfs directly.
How can i forget the credits...
Cocafe for the Cocore kang
Adi_Pat for misc support
Diego-ch for mental support
R_a_z_v_a_n for testing my script
Frapeti and Fedevd for motivating me
Callmeventus for the idea
Shaaan.. can i flash another kernel with this rom ?
Dikirim dari GT-I9070 memakai XDA Developer app
Great! Thanks for the ROM... List of features?
GaYoung28 said:
Shaaan.. can i flash another kernel with this rom ?
Dikirim dari GT-I9070 memakai XDA Developer app
Click to expand...
Click to collapse
Yeah. You can
Like this rom! Hope I can install it soon! P.s. Is it debloated?
Not really. Some useless apps have been removed though.
Next releases may have the option to select apps as per the user requirements while installing.
Nice! I wanna test!!!!
I'll try it and give you feedback
Does it have "ripple lockscreen mod"? Or can I install on it? Is it deoxeded?
R: [ROM][JB] Slim-JB
Great! Also i love stock ui =D
What about ram usage? Average free ram with 2-3 apps opened?
Thank you!
Inviato dal mio S Advance
Inviato dal mio S Advance
where his kennel
Jacopo97 said:
Does it have "ripple lockscreen mod"? Or can I install on it? Is it deoxeded?
Click to expand...
Click to collapse
Already has the ripple mod..
I do not respond to tech support via PM
Shaaan.. can i flash over other custom rom?
Dikirim dari GT-I9070 memakai XDA Developer app
So... What did u 'develop' in this?
Sent from my GT-I9070 using xda premium
R: [ROM][JB] Slim-JB
sameer4344 said:
So... What did u 'develop' in this?
Sent from my GT-I9070 using xda premium
Click to expand...
Click to collapse
He made a kernel and he tweaked a lot i think
Inviato dal mio GT-I9070 con Tapatalk 2
[size=+2]Discontinued; but the hosts files below are always updated[/size]
This is a recompilation of registry hacks for Interop-unlocked Windows Phone devices.
I have tested this on my freshly hard-resetted Lumia 730; Windows Phone 8.1 GDR1 (Also tried on Win10 v14393.189 as of 2 weeks ago).
I have used CustomPFD to explore the whole WP Registry, I will update this thread if I find something new and unusual.
- Created registry values are tested while there are some that says 'create a value for this key', I did not include it without initial and further testing
- Most WPTweaker tweaks are not here though, I still haven't consulted them for replicating their list of tweaks. All of the tweaks below are the ones I always use/alter on my device.
- Several tweaks might still apply on W10M but I haven't tested it all yet.
- Useful things are in here, I will dig down further to add more to this thread
Credits:
- CustomPFD
- WP10 WPTweaker
- WPTweaker
________________
Code:
HKLM\SYSTEM\ControlSet001\Services
(Start: 4 (Disable), 3 (Manual), 2 (Automatic), 1 (System), 0 (Boot))
- DataCollection
- DiagnosticSvc
- DiagTrack
- dmwappushsvc
- DnsCache → You might want to disable this service if and only if you are using a large hosts file
- FeedbackSvc
- telrepsvc → Telemetry, haven't confirmed yet but somehow breaks clearing of Telemetry files in Storage
- telwatsvc → Telemetry
Code:
HKLM\SYSTEM\ControlSet001\Control
- WaitToKillServiceTimeout
Code:
HKLM\SYSTEM\Maps\Storage
- UseSmallerCache
Code:
HKLM\SOFTWARE\OEM\VolumeLimit
- EnableVolumeLimit
- VolumeLimit
Code:
HKLM\SOFTWARE\OEM\Nokia\Onboarding
(I do not know what this does)
- EnableNokiaCare
Code:
HKLM\SOFTWARE\Microsoft\CommandChannel\Internal
(Testing; Disables Push Notifications?)
- IsWNSEnabled
Code:
HKLM\SOFTWARE\Microsoft\DataCollection\Default\WifiAutoConnectConfig
(Disables Wi-Fi Sense)
- AutoConnectEnabled
Code:
HKLM\SOFTWARE\Microsoft\DeviceEncryption
(Testing; Bitlocker?)
- Enabled
Code:
HKLM\SOFTWARE\Microsoft\Internet Explorer
- Disable Display Inline Images → Enables IE's Show Pictures Automatically option
Code:
HKLM\SOFTWARE\Microsoft\Internet Explorer\GestureNavigation
(Testing; IE Swipe Gesture)
- FlickThreshold
Code:
HKLM\SOFTWARE\Microsoft\Internet Explorer\Main\TabStore
(Testing; Max Tabs? I think this one is the tabs to be kept in memory, or else.. It will be unloaded)
- NumberToKeep
Code:
HKLM\Software\Microsoft\Messaging\GlobalSettings
- ShowSendingStatus → Useful if you want to see the "Sending..." status in your outgoing sms
Code:
HKLM\Software\Microsoft\PolicyManager\current
(Works like Group Policy Editor? Feedback in Settings now says Disabled by policy/administrator or something like that)
- ...\System\AllowTelemetry, it is set to 2. Setting this to 0 disables Telemetry and Feedback.
Code:
HKLM\Software\Microsoft\SEMgr\UI
(NFC Settings)
Code:
HKLM\Software\Microsoft\Shell\CustomHoldDelays
(Contains Hold Delays for touch taps, higher=longer tap to activate)
Code:
HKLM\Software\Microsoft\Shell\NavigationBar
- IsBurnInProtectionEnabled → This is the one that makes your software navigation bar grayish
- IsDoubleTapOffEnabled → This option is hidden in the Navigation Bar settings for Windows Phone 8.1 GDR1 users, double tapping the navbar will lock/turn-off the screen; good for hardware key prolongation
Code:
HKLM\Software\Microsoft\Shell\Start
(Tile Flipping Delay)
- NotificationCycleTimer
Code:
HKLM\Software\Microsoft\SQMClient\Windows
(Windows Customer Experience Improvement program)
- CEIPEnable
Code:
HKLM\Software\Microsoft\Windows\CurrentVersion\Control Panel\Theme
(Use 59, 64, or 75)
- UserPreferenceWidth → 75 in my device gives 5 Quick Settings instead of the usual 4
Code:
HKLM\Software\Microsoft\Windows\CurrentVersion\Audio
(Testing; Allows compressed format like FLAC?)
- AllowCompressedFormatSupport
Code:
HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings
- ReceiveTimeOut
- SendTimeOut
Code:
HKLM\Software\Microsoft\Windows\CurrentVersion\WINEVT\Channels
(Testing; Event Logging)
~ I tried setting Enabled to 0, I do not see/feel any changes though.
Custom Hosts file
hosts sources are now posted here.
THIS MOD IS ONLY FOR THE JOYING / 2GB / Sofia models - It is stable and working well .
Please use V4.1 if you have not upgraded to Marshmallow!
History:
V6.4: Update using code base 9/1/2017 Joying Update ( Android 6.0 ) (updated Oct 7)
Changes:
- Meida keys - Removed support for media keys customization. No longer sent to launcher.sh due to slow response time.
- Media keys - Modified code to only send media keys to the active media player.
- Changed reboot timer from 1/2 second to 2 seconds. Should help eliminate random reboots when coming from standby.
- Updated player_app.txt and navi_app.txt to latest from @surfer63
- Fixed issue with button 33 not working
- Files included:
- V6.4-Sofia-1-C9-Server_NOKILL.zip - Original file with task killer removed
- V6.4-Sofia-1-C9-Server_NOKILL_GVS.zip - Task killer removed, Google Voice Search on 'SRC' key
- V6.4-Custom_Keys-Mods.zip - Complete key modifications ( requires launcher.sh - description below )
V6.3: Update using code base 5/25/2017 Joying Update ( Android 6.0 )
- Files included:
- V6.3-Sofia-1-C9-Server_NOKILL.zip - Original file with task killer removed
- V6.3-Sofia-1-C9-Server_NOKILL_GVS.zip - Task killer removed, Google Voice Search on 'SRC' key
- V6.3-Custom_Keys-Mods.zip - Complete key modifications ( requires launcher.sh - description below )
V6.2: Updated using code base 5/8/2017 Joying Update ( Android 6.0 )
- Added fix for google maps voice output on radio from @xdamember2
V6.1: Updated code base using 5/8/2017 Joying Update ( Android 6.0 )
V6: Updated code base using 4/27/2017 Joying Update ( Android 6.0 )
Android 5.1.1
V4.1 - Fixed issue with "Google Voice Search" not lowering music volume (3/23/2017) - Android 5.1.1
V4: Updated code base using 3/14/2017 Joying ROM
Changes/Added support for:
- MEDIA KEY - hard key on unit
- BAND KEY - hard key on unit
- ACC_ON - Triggers on key on
- Minor changes to example shell scripts to add cases for MEDIA, BAND, ACC_ON ( launcher.sh )
- FIX/UPDATE - Updated list of NAVI APPS in assets/property/navi_app.txt ( allows more applications to speak during radio )
- Many thanks to @surfer63 for navi app radio fix and windows install script
V3 - Rebuilt using latest Joying ROM dated 2/22/2017 - Includes V1 & V2 steering wheel / key modifications.
Changes/Added support for:
- ACC_OFF - Added support for running actions at key off (case 98 )
- Added case 98 to example scripts to perform "PAUSE" - to stop current music player when key off
V2 Removed killAppWhenSleep(); - Eliminates tasks being killed on sleep
Added support for additional keys / Minor changes to example shell script ( launcher.sh )
- HANG - steering wheel softkey
- DVD - hard key on unit (if available)
- EJECT- hard key on unit (if available)
- CALL/BT softkey - Fixed issue where key would not respond after call disconnect.
V1 Initial version
There is little risk with this mod, but please understand what you are doing, and make backup of the original apk file ( in case you want to revert back ). The installer script does make a backup, but will overwrite the backup if installed more than once.
I also added a simpler "launcher_simple.sh" into the zip, which only changes the functionality of the Source (rotates radio, pandora, spotify ) and Call buttons ( google voice command ). These scripts are working examples of what can be done. If you want the simpler version, just rename "launcher_simple.sh" to "launcher.sh" before installing.
---------------------- Original Post -----------------
I have spent quite a bit of time working on being able to customize the steering wheel keys of my Joying 2GB headunit (JY-UL135N2 / 2GB / Sofia unit). I have made some good progress and thought I would share what I have done so far.
The system package /system/app/Sofia-1-C9-Server-V1.0/Sofia-1-C9-Server-V1.0.apk has been modified to intercept the keys sent by the MCU, and thus able to change the behavior of the key presses. The keys listed below are supported, and will launch a "shell" process, so any action that can be done by the command line can be performed. If your not familiar with the Android command line, you might be surprised how powerful it is. As a side note, this works very fast and efficient. From my testing the overhead of the system call and shell script is almost non-existent, and key presses are registered with no delay. In other words, it is working very nicely.
In addition to the steering wheel button mods, also provided is the ability to launch a command or series of commands when a RESUME is received.
Included is my shell script (example) that can be used as a model for your own customization. The example script included performs the following actions:
CALL/BT PHONE(27) - One press is HOME, 2 presses is BACK, 3 presses brings up Google Voice Commands
MODE/SRC(37) - Rotates through music apps: Radio, Pandora, Spotify, Stock Music App - If it has been longer than 1 minute since the last press it will return you to the last selected music app with first press, then continue with the rotation. ( I'm working on a more intelligent way of doing this, that looks at the process list and will post soon)
NAVI(9) - One press is Torque, 2 presses is google maps
PAUSE/PLAY(85*),NEXT(87*), PREVIOUS(88*), FASTBACK(89*), FASTFWD(90*),HOME(3), BACK(4) - Currently set to perform stock functions. They ARE passed to script so they can be assigned other functions if wanted.
ACC_ON(97) - Executes at ignition switch on. Sample script has a 'play' here to restart music player that was paused at key off.
ACC_OFF(98) - Executes at ignition switch off. I suggest you assign "pause" on this case, to stop current music player. Resolves issue of music player advancing for several minutes after key is turned off.
RESUME(99) - Executes on system resume.
Please note the media control keys marked with a (*) are hardcoded to specific functions within the stock Joying applications. They are only passed through to the shell script when you are NOT using a Joying media application. They will ONLY work as the original keys when you are within the Joying media applications.
Remember, the apk is just handing codes to you, what you do with them after that is up to you! I have tried to comment the example script enough to be understandable to someone with basic programming knowledge.
Attached is a zip file with the updated Sofia-1-C9-Server-V1.0.apk, launcher.sh ( my example script), and install script. The launcher.sh script must be placed in the /data directory ( /data/launcher.sh ), as it is hardcoded in the apk file.
The install script is a shell/linux script, but you can easily copy/paste the adb commands if your using windows.
[NOTE: Please update to the latest version of busybox! I found some bugs in the version included by Joying that caused several issues.]
Awesome work. I will mess with this sometime this week. I still need to root my unit. Just installed it last week.
Sent from my SAMSUNG-SM-G935A using Tapatalk
Excellent work, sir! Before I start modifying the script for personal taste, could you help how to find key number for DVD and Eject buttons that currently have no function as the DVD drive is non-existent? Maybe logcat or something?
sonof said:
Excellent work, sir! Before I start modifying the script for personal taste, could you help how to find key number for DVD and Eject buttons that currently have no function as the DVD drive is non-existent? Maybe logcat or something?
Click to expand...
Click to collapse
I see a few references in the code for the DVD/eject button in the common code. My 'best guess' would be to add a system call to the cases listed below, but I seriously doubt the MCU would even send the codes if there is no DVD present.
bsp/FinalBsp.java
public static final int KEY_CODE_DVD = 242;
public static final int KEY_CODE_EJECT = 231;
bsp/HandlerBspKey.java
public static void keyEvent(int paramInt1, int paramInt2)
case 242:
bspKeyDvd(paramInt2);
return;
case 231:
bspKeyEject(paramInt2);
return;
gustden said:
I see a few references in the code for the DVD/eject button in the common code. My 'best guess' would be to add a system call to the cases listed below, but I seriously doubt the MCU would even send the codes if there is no DVD present.
bsp/FinalBsp.java
public static final int KEY_CODE_DVD = 242;
public static final int KEY_CODE_EJECT = 231;
bsp/HandlerBspKey.java
public static void keyEvent(int paramInt1, int paramInt2)
case 242:
bspKeyDvd(paramInt2);
return;
case 231:
bspKeyEject(paramInt2);
return;
Click to expand...
Click to collapse
Seems that MCU does send the codes as seen here.
I will see what I can do but I doubt I am able to do anything as I just installed apktool the first time today and am new with apk's. Thanks for your efforts! Very appreciated.
sonof said:
Excellent work, sir! Before I start modifying the script for personal taste, could you help how to find key number for DVD and Eject buttons that currently have no function as the DVD drive is non-existent? Maybe logcat or something?
Click to expand...
Click to collapse
sonof said:
Seems that MCU does send the codes as seen here.
I will see what I can do but I doubt I am able to do anything as I just installed apktool the first time today and am new with apk's. Thanks for your efforts! Very appreciated.
Click to expand...
Click to collapse
If I create and send you a apk file with additional debug statements, would you be able to install it, and capture the 'logcat' of the buttons being pressed? It makes it much more difficult since I don't have the DVD buttons. Hacking smali code is a LOT of trial and errors. Their code is quite complex, and doesn't decompile into Java very nicely in some critical areas.
gustden said:
If I create and send you a apk file with additional debug statements, would you be able to install it, and capture the 'logcat' of the buttons being pressed? It makes it much more difficult since I don't have the DVD buttons. Hacking smali code is a LOT of trial and errors. Their code is quite complex, and doesn't decompile into Java very nicely in some critical areas.
Click to expand...
Click to collapse
Yes I am capable of doing that!
sonof said:
Excellent work, sir! Before I start modifying the script for personal taste, could you help how to find key number for DVD and Eject buttons that currently have no function as the DVD drive is non-existent? Maybe logcat or something?
Click to expand...
Click to collapse
sonof said:
Yes I am capable of doing that!
Click to expand...
Click to collapse
I put in debugging code that parses the data stream from the MCU and dumps the first 4 bytes of EVERY message that is received from the MCU (skipping checksum info). Simply replace the original file (make a copy first ) and reboot. When looking for the keys, I suggest you do not use the radio, as it sends a constant flood of messages, such as RDS updates.
Even when the radio is off, there are still messages constantly being sent. If you filter on the debug messages MCUKEY in adb, and press the button in question a few times quickly, you should see a consistent pattern. I was able to identify the 'HANG' key in a couple minutes using this method. You should see something like this in the logcat:
D/MCUKEY ( 693): MCUKEYINPUT: B1=1 B2=0 B2=5 B2=224
D/MCUKEY ( 693): MCUKEYINPUT: B1=1 B2=7 B2=16 B2=0
D/MCUKEY ( 693): MCUKEYINPUT: B1=1 B2=0 B2=0 B2=49
D/MCUKEY ( 693): MCUKEYINPUT: B1=1 B2=7 B2=16 B2=0
D/MCUKEY ( 693): MCUKEYINPUT: B1=1 B2=3 B2=34 B2=0
In this case the HANG key is in bold ( 1, 7, 16, 0 ) messages. IF the DVD and eject keys are sent, they should definitely show up here. Not every key is sent by the MCU, if it is not relevant to the current state of the system. For example the media buttons are not sent when the radio is on, since the MCU is in control of the radio, however it does send the results such as a frequency change resulting from the button press.
It is possible that the MCU knows there is no DVD present and suppresses the messages. From looking at the code, it may be the action of a disc being ejected that is sent from the MCU, with the eject button press handled internally by the MCU. Your more likely to find the press of the DVD button than the eject button, but may find both.
When your done searching, you want to put back the original file and reboot. If you find the codes, I can certainly add them to trigger the shell script and you can take whatever action you want with them.
Thank you! I will try this the first thing next week when I get back home from a weekend trip.
Question: if I remove a customization from the script file for a key, the key should then perform its default functions, correct?
vassandrei said:
Question: if I remove a customization from the script file for a key, the key should then perform its default functions, correct?
Click to expand...
Click to collapse
The keys being passed to the shell script (launcher.sh) is hard-coded in the APK file and is just sent to the script. If you remove it from the script, the key would no longer do anything.
If you want to keep the stock functionality of a specific button, it should be fairly easy to duplicate it in the shell script. For example:
BT/CALL button: "am start com.syu.bt/com.syu.bt.BtAct"
NAVI: By default, I think NAVI just toggles between a Navi app, and the previous activity on the stack.
The code below should behave the same as the original for both the NAVI an BTPHONE buttons ( assuming your using google maps )
Code:
case $key in
9) # NAVI
x=`dumpsys activity activities | grep "Run #" | cut -f 13 -d" "| head -1 | grep maps`
if [ "$x" = "" ]
then
$maps
else
am start `dumpsys activity activities | grep "Run #" | cut -f 13 -d" " | grep -v launcher | grep -v systemui | grep -v maps |head -1`
fi
;;
27) # BTPHONE/PTT
am start com.syu.bt/com.syu.bt.BtAct
;;
Play/Pause: you can just remove the 85 case, it would just hit the default case and pass "input keyevent 85" which is identical in functionality.
gustden said:
The keys being passed to the shell script (launcher.sh) is hard-coded in the APK file and is just sent to the script. If you remove it from the script, the key would no longer do anything.
If you want to keep the stock functionality of a specific button, it should be fairly easy to duplicate it in the shell script. For example:
BT/CALL button: "am start com.syu.bt/com.syu.bt.BtAct"
NAVI: By default, I think NAVI just toggles between a Navi app, and the previous activity on the stack.
The code below should behave the same as the original for both the NAVI an BTPHONE buttons ( assuming your using google maps )
Code:
9) # NAVI
x=`dumpsys activity activities | grep "Run #" | cut -f 13 -d" "| grep -v launcher | grep -v systemui | head -1 | grep maps`
if [ "$x" = "" ]
then
$maps
else
am start `dumpsys activity activities | grep "Run #" | cut -f 13 -d" " | grep -v launcher | grep -v systemui | head -2 | tail -1`
fi
;;
27) # BTPHONE/PTT
am start com.syu.bt/com.syu.bt.BtAct
;;
Play/Pause: you can just remove the 85 case, it would just hit the default case and pass "input keyevent 85" which is identical in functionality.
Click to expand...
Click to collapse
brilliant! thank you so much!
Last thing: I want to have viper4android launch on resume (in the background ideally). where can I find the "app identifier" to put in the shell script?
vassandrei said:
Question: if I remove a customization from the script file for a key, the key should then perform its default functions, correct?
Click to expand...
Click to collapse
vassandrei said:
brilliant! thank you so much!
Last thing: I want to have viper4android launch on resume (in the background ideally). where can I find the "app identifier" to put in the shell script?
Click to expand...
Click to collapse
I made a slight change to the 'CODE' section of my previous post, so if you copy it make sure you get the edited version. I tested it and made a couple of changes.
There are several ways to get the package name and activity.
What I typically do is start the application on the unit and do the following in adb:
> adb shell
> dumpsys activity activities | grep "Run #"
This shows you a list of the activities ( package/activity ) in the task list with most recent at the top.
You should be able to pick it out pretty easily. If it is the app that I found with google, this should work to start it.
> am start com.vipercn.viper4android_v2/.activity.ViPER4Android
In most cases, you can just give the package name when using 'am start' with no need for the activity. It will default to the 'LAUNCHER' activity in the package. I usually always give the activity, just to be safe. I would sleep for a couple seconds to give it time to initialize and then $home to take you back to the Home screen. So whole command would look like this. It is easy to test using adb.
am start com.vipercn.viper4android_v2/.activity.ViPER4Android ; sleep 2 ; $home
Thanks for this, it's working great on my Joying (JY-UL135N2 ).
My only issue is that the CALL/BT PHONE (27) button is assigned to my "Pick Up/Call Out" button on my steering wheel. So I can't use it to pick up calls. I actually have another dedicated button on my steering to activate voice commands, so I'd rather assign the CALL/BT PHONE function to that. Do you happen to know how to find out what numbers corresponds to each button press?
akuma148 said:
Thanks for this, it's working great on my Joying (JY-UL135N2 ).
My only issue is that the CALL/BT PHONE (27) button is assigned to my "Pick Up/Call Out" button on my steering wheel. So I can't use it to pick up calls. I actually have another dedicated button on my steering to activate voice commands, so I'd rather assign the CALL/BT PHONE function to that. Do you happen to know how to find out what numbers corresponds to each button press?
Click to expand...
Click to collapse
I make and receive so few voice calls, It wasn't worth having a steering wheel button dedicated for the dialer/call pickup . I just tap the screen to answer and use google voice to make calls.
If you want to have a button answer a call, there *should* be a way to do it given the right command. I will play around with it more. Worse case I can just back out the changes for the (27) , and send you an updated apk.
I used the joying steering wheel control app and switched the dialer/call pickup to my voice button and that works, but my dialer/call pickup doesn't do anything. Please let me know if you want me to test anything. Thank you.
gustden said:
I put in debugging code that parses the data stream from the MCU and dumps the first 4 bytes of EVERY message that is received from the MCU (skipping checksum info). Simply replace the original file (make a copy first ) and reboot. When looking for the keys, I suggest you do not use the radio, as it sends a constant flood of messages, such as RDS updates.
Even when the radio is off, there are still messages constantly being sent. If you filter on the debug messages MCUKEY in adb, and press the button in question a few times quickly, you should see a consistent pattern. I was able to identify the 'HANG' key in a couple minutes using this method. You should see something like this in the logcat:
D/MCUKEY ( 693): MCUKEYINPUT: B1=1 B2=0 B2=5 B2=224
D/MCUKEY ( 693): MCUKEYINPUT: B1=1 B2=7 B2=16 B2=0
D/MCUKEY ( 693): MCUKEYINPUT: B1=1 B2=0 B2=0 B2=49
D/MCUKEY ( 693): MCUKEYINPUT: B1=1 B2=7 B2=16 B2=0
D/MCUKEY ( 693): MCUKEYINPUT: B1=1 B2=3 B2=34 B2=0
In this case the HANG key is in bold ( 1, 7, 16, 0 ) messages. IF the DVD and eject keys are sent, they should definitely show up here. Not every key is sent by the MCU, if it is not relevant to the current state of the system. For example the media buttons are not sent when the radio is on, since the MCU is in control of the radio, however it does send the results such as a frequency change resulting from the button press.
It is possible that the MCU knows there is no DVD present and suppresses the messages. From looking at the code, it may be the action of a disc being ejected that is sent from the MCU, with the eject button press handled internally by the MCU. Your more likely to find the press of the DVD button than the eject button, but may find both.
When your done searching, you want to put back the original file and reboot. If you find the codes, I can certainly add them to trigger the shell script and you can take whatever action you want with them.
Click to expand...
Click to collapse
Luckily the eject key was also found! Here are the codes:
DVD:
D/MCUKEY ( 691): MCUKEYINPUT: B1=1 B2=0 B2=16 B2=80
EJECT:
D/MCUKEY ( 691): MCUKEYINPUT: B1=1 B2=161 B2=2 B2=91
Looking forward to the modified apk. If you happen to take donations I'd be willing to give you a beer. Thank you.
Model number for reference: JY-AL003N2
sonof said:
Luckily the eject key was also found! Here are the codes:
DVD:
D/MCUKEY ( 691): MCUKEYINPUT: B1=1 B2=0 B2=16 B2=80
EJECT:
D/MCUKEY ( 691): MCUKEYINPUT: B1=1 B2=161 B2=2 B2=91
Looking forward to the modified apk. If you happen to take donations I'd be willing to give you a beer. Thank you.
Model number for reference: JY-AL003N2
Click to expand...
Click to collapse
Here is an updated apk file that should catch the code you listed. In the zip there is a file "keys.txt" and also updated APK file. The keys.txt is a complete list button codes for both the soft-keys ( steering wheel ) and hard-keys (on unit ) that the new apk sends to the script. This is a beta of V2.0 which I added:
3 - HOME ( On unit hard key )
4 - BACK ( On unit hard key )
28 - HANG/CALL END ( Steering wheel softkey)
31 - DVD ( On unit hard key )
32 - EJECT ( On unit hard key )
The HOME/BACK keys are sending the keycodes for the home/back actions. You don't need to map them in a script, as long as you have a default that passes keycodes at the end of the script.
*) input keyevent $key
;;
I have used it the last couple of days and it is working fine for me, but can't test the dvd or eject.
Let me know if it registers the keys.
sorry for the dumb question but do you need to root the unit to use this?
Is there a way to run a shell script when I switch ignition off and illumination on or off?