Related
we all owe a hell of a thanks to Isaacj87 for getting miui over to the triumph.
i take no credit for [email protected]#$%^&*() i am just posting this link so people who dont go to android forums can find this!
to flash this you will also need issacj87's CWM custom made for the triumph.
here you go guys and again be sure to thank isaacj87 for all his hard work!!!!!!!!!!!!!
DISCLAIMER: I am not responsible for any damages (bricking/phone ruining) occurred while flashing or using this ROM. By using this ROM, you understand that that I am not liable for any or all consequences of using this ROM. If you don't know what you're doing, DON'T TRY IT. Use at your own risk!
SPECIAL NOTE: These builds are not being built from source (only partially). This port is technically a port of a port of a port (DHD-CN --> DHD-EN --> MI410 --> Triumph). I can only account for the changes I made personally. There are no records on what was changed up to this point from elsewhere. This is something to consider.
Also, since I don't have the source for this ROM, it's being worked on with a take-it-or-leave-it attitude. If I can manage to fix something, it'll get fix. Since it was originally in Chinese, some of the language translations will be strange. I'm using code from CM7, building said code, and cramming it into MIUI. Since MIUI and CM7 share a lot of the same code, this has been working fine so far. But remember: I can't stress how much I don't want complaints and bug reports. I'm doing this for my own amusement and I'm just sharing what I've got.
I'd like to put up the the changes I've made to this ROM, but, basically, it would be useless. I used whatever tools I could find to decompile the various aspects and apply changes, but I wasn't able to save any of the decompiled stuff in any readable form. However, the changes to kernel I made will always be available. You can view those changes on my Github: http://github.com/ikarosdev
Overall, everything has been working quite well and I hope your happy with the results.
What works:
BOLD=NEW
RIL/3G/1xRTT
Audio/Call recording
WIFI
USB Tethering
Bluetooh
Keymapping
2D/3D/EGL/GPU
LED (dual-mode)
Capacitive button lights
Screen rotate/orientation
Touchscreen with multitouch/screen rotate capable
USB mounting
CRT screen off animation
Proximity sensor
Camera (front and rear) [see next section below]
GPS
HD 720P video recording/FFC video recording
MMS [see next section below]
Torch
Google Talk with video/voice chat
Wired headse
What partially works:
Camera (FFC output during video calling and snapshots is not mirrored.)
MMS (I can send, but not receive. Always comes back complaining about something.)
What doesn't work:
Ambient light sensors
WIFI hotspot (DON'T ASK, WON'T FIX)
720p video recording (Doesn't work in MIUI camera app. I've heard reports this works with a 3rd-party app)
HDMI out/mirroring (I don't have any way of testing this. Maybe it does work.
Known issues:
These builds, as mentioned, are not being built from source. As such, measures were taken to get everything working. Don't be surprised if you get a FC or eleven. Furthermore, these are development builds (a.k.a not stable). Some of you may be able to live with it, some won't.
Being similar to CM7 (at the core), the proximity sensor goes wonky during phone calls.
Recovery:
I also have my own CWM port for the Triumph. Since I got everything working, it's been running like a champ. I've themed it a bit to make it unique, but it's still Clockwork recovery at its core. I've currently put this up (minus the custom colors and graphics) for review to be included in ROM Manager. You can watch its progress here: http://github.com/koush/ROMManagerManifest/issues/311
The keymapping in my recovery is:
- Volume up/down to navigate
- Menu to select
- Back to go backwards
Downloads:
Recovery:
NOTE: tjstyle's recovery (4.0.0.9) will not work. You have to use a recovery for the Triumph.
NOTE: You must use a recovery with EXT4 capabilities. The one below should be just fine. If you're already using a recovery with such features, you don't have to change it.
ROM
NEWhttp://www.mediafire.com/?0m5rm6l5sl6samc
OLDhttp://www.mediafire.com/?u80w31lrkeoj05f
CWM
NEWhttp://www.mediafire.com/?y10vq724nr7al8p
OLDhttp://www.mediafire.com/?0h8uph17x1w30e8
**Instructions on how to install isaacj87's CWM**
1. download the recover img listed above
2. unzip the file using winrar or any other unzipping program
3.turn your triumph all the way off
4. unplug the usb cable for your triumph
5. hold the volume down+power button on your MT
6. the screen should come up as black with small white text in the top right hand corner. the text will keep repeating but dont worry this is normal.
7. plug the usb cable into your MT and computer and let the drivers install.
8. once they are finished installing, go to computer and you should see a new device called mobile. click on it then click on the image folder.
9. there you will see the recovery.img file. take this and make a back up of it on your desktop or in a safe place where you wont lose it.
10. next drag issacj87's recovery.img to the folder and copy and replace the current recovery.img. once this is finished you can eject your MT and the only way to get it out of bootloader mode is to do a battery pull.
11. after the phone is off hold both volume keys and also the power button and it will boot into isaacj87's cwm 4.0.1.5 recovery =)
12. from there do a full wipe of the system and D cache and user data and then you can flash MIUI!!!!!
Enjoy!!!!!!!
THANK YOU AGAIN ISACCJ87!!!!!!!!!!!!!!!!!!!!!
original thread at android forums
http://androidforums.com/triumph-al...1-10-7-triumph-10132011-1-gb-2-3-5-based.html
hmm no mms. i will wait. thanks for the heads up
Could you, I don't know.......post a link to the original thread? Whats working, whats not, features, change log, screenshots, ect. Elaborate a little.
there is that better?
platypuss94 said:
there is that better?
Click to expand...
Click to collapse
Yes sir Thank you. I went ahead and flashed a little while ago, and this is a nice miui build. Needs to be overclocked. But other then that, its nice.
Wait, this ROM requires a /data wipe? That's different.
crxmax said:
hmm no mms. i will wait. thanks for the heads up
Click to expand...
Click to collapse
MMS is my least favorite smartphone feature by far... try GO SMS (it comes with built-in uploading) or just use URLy to put files online. Since we all know how lousy Virgin Mobile's MMS system is already.
I kind of use it for work. Need to be able to send and receive. Its easiest to send to a phone number for some customers
Sent from my Triumph using XDA App
couldnt resist...seems like wifi locks up my screen tho =/
Data is horrible with this and cm7. Constantly having to toggle mobile data off then on to get it to work.
Sent from my MOTWX435KT using xda premium
Will Isaac's kernel that works on cm7 work on this?
Sent from my Triumph using MIUI
dimasp6 said:
Will Isaac's kernel that works on cm7 work on this?
Sent from my Triumph using MIUI
Click to expand...
Click to collapse
No. It'll only work on CM7.
isaacj87 said:
No. It'll only work on CM7.
Click to expand...
Click to collapse
Alright, thanks.
Sent from my Triumph using xda premium
rom has been updated. it would be nice if the original poster would keep up with the updates.
crxmax said:
rom has been updated. it would be nice if the original poster would keep up with the updates.
Click to expand...
Click to collapse
yeah. the link to the "original" thread on android forums doesnt work. i want update!
Here you go.
http://androidforums.com/triumph-al...1-10-7-triumph-10132011-1-gb-2-3-5-based.html
Anyone else have data problems with miui? Its super solid with the exception that my data drops constantly.
Sent from my Motorola Triumph using xda premium
i use juice defender. it cuts off data when the screen is off and restarts it when you turn the screen back on. thus resetting your 3g every time. not an actual "fix" but it makes the rom that much more usable
MMS has been fixed. I've been sending and receiving all day today. Clean pics, I might add.
I've also went ahead and bumped us up to 1.10.14. It will be released soon.
I've been investigating some fixes for the data drop issue. I think I may have found something that might work. I'm going to try it first in CM7 and if it works, it should be applicable to MIUI as well.
Happy MIUI-ing guys.
P.S. I would make an "official" thread here, but it seems most Triumph users frequent Android Forums. I'll make an effort to keep an eye out here as well.
crxmax said:
i use juice defender. it cuts off data when the screen is off and restarts it when you turn the screen back on. thus resetting your 3g every time. not an actual "fix" but it makes the rom that much more usable
Click to expand...
Click to collapse
I found something that might fix this problem (i.e. a real solution). Tickerguy also worked on a solution that seems to be working. He's going to test it for a couple days to confirm, but so far it looks good.
Once he shares his fix, I'll try and "code" (smali) it into MIUI.
i cant wait for this next update.
On the sensation is it possible to configure the LEDs to blink until you read the txt message for example. I think it is currently set to blink for about a minute. On the HD2 I was able to make registery changes to do this.
I am on a stock 1.50 rom with stock kernel.
I think faux has changed the led blink time, you'll have to look at his kernel. It requires a change in the kernel.
Sent from my HTC Sensation 4G
Show's kernel also does this.
Just spotted this post from Faux. Exactly what I am looking for just need to find out how to do it now
Originally Posted by faux123
Ah crap.. forgot about that...
BTW, it's not clean to hack the LED driver... much cleaner to hack the ROM... ask your ROM devs to hack the LED timer since it is SET by the ROM and kernel only does the blinking part....
So as you can see, by hacking the blinking part, it is an Ugly hax.. Just have the ROM tell the kernel to blink for longer...
Does anybody know how to tweak the rom to get the leds blinking continiously?
Any ideas?
This might do the trick http://forum.xda-developers.com/showthread.php?t=1407403&highlight=phone+notifier
I currently use noLed. Our led is crap IMO lol...
https://market.android.com/details?...lt#?t=W251bGwsMSwxLDEsImNvbS5sZWQubm90aWZ5Il0.
Works fine for me. I set it where it shuts off in 5 mins though.
Here is BLN control
https://market.android.com/details?id=neldar.bln.control.free&feature=search_result
I tried it using the stock kernel and it was a no go. I think I'll play with kernels to see if any work for our phones. Anyone else have a go at this app yet?
Those arnt quite what I am looking for. Faux123 suggested that you should be able to edit a file in the rom its self to control the time of the leds. I think you can make it stay on by setting it to 0. I just cant remember what file to edit.
As far as I know the kernel only defines the colour of the led and the time between each flash, not the actual length of time it flashes for. It is the rom that defines that. I am continuing to look and see if I can find the file.
i think this is default from htc sense o.0
otherwise - with miui you can set however you want
GhostXSeries said:
Those arnt quite what I am looking for. Faux123 suggested that you should be able to edit a file in the rom its self to control the time of the leds. I think you can make it stay on by setting it to 0. I just cant remember what file to edit.
As far as I know the kernel only defines the colour of the led and the time between each flash, not the actual length of time it flashes for. It is the rom that defines that. I am continuing to look and see if I can find the file.
Click to expand...
Click to collapse
Bricked kernel will keep your led flashing till you read your messages or emails.
Sent from my HTC Sensation 4G using XDA App
Hey all, I'm trying to figure out how to get some brightness settings for the touch key brightness to stick. I've used LG 2x Notifications and O2x Touch Key Brightness, and they both work up until the point where i put the phone to sleep by tapping the power button. As soon as I wake it up, the brightness goes straight to zero unless i head back to the app and raise it up again. And if i uninstall the apps, the brightness on my keys stay off until i re-flash or reinstall the app again. Help!
My issue is a little different but similar. It worked fine for me on every basic gingerbread rom, but when I switched to a cm7 based rom the lights change with the brightness of the screen. I turned off all the light notifications but it did not help.
If anyone has any ideas, I'd love to hear them.
What rom?
Sent from my LG-P999 using XDA
redmonke255 said:
What rom?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
On SinghUI but it doesn't have built-in LED notifications, if that's what you're getting at.
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
xBIGREDDx said:
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
Click to expand...
Click to collapse
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
rrroach said:
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
Click to expand...
Click to collapse
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
xBIGREDDx said:
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
Click to expand...
Click to collapse
Thanks for the link. It turns out that the ROM does have led notifications. However, disabling them didn't help the problem. :/ the g2x has just been an awful experience for me! :/
Guys, does Lightflow simply not work with CM 10.1.3? I have tried every setting known to man and no LEDs come on. Even doing the "All enabled LEDs test" flashes nada. If its a known not working issue, does anyone know of a Lightflow like app that works with CM 10.1? Thanks.
Looked harder and found that notification light under system was actually not enabled. Once check, all was well.
Guess i spoke too soon. Regular corporate email works but Gmail led notifications do not work despite being set in Light flow and enabled in Gmail itself. I still get the sound just no LED. Anyone have this working on their end?
I'm using LightFlow on 10.1.3 (stable, from September 23) and it seems to work ok I have unique colors for almost every single app, so I'd definitely know if the light wasn't working. There seems to be no difference on CM 10.1.3 vs stock in my case. I'm using the paid version of LightFlow, and the only option I have enabled is "Reset Color Before Change".
Make sure you've enabled LightFlow under accessibility -- that's usually a culprit. I've also enabled the developer options in the OS itself, but I don't see how that would impact LightFlow.
Cpudan80 said:
I'm using LightFlow on 10.1.3 (stable, from September 23) and it seems to work ok I have unique colors for almost every single app, so I'd definitely know if the light wasn't working. There seems to be no difference on CM 10.1.3 vs stock in my case. I'm using the paid version of LightFlow, and the only option I have enabled is "Reset Color Before Change".
Make sure you've enabled LightFlow under accessibility -- that's usually a culprit. I've also enabled the developer options in the OS itself, but I don't see how that would impact LightFlow.
Click to expand...
Click to collapse
My settings seem correct as everything works except Gmail LED. I have the free version of Light flow so i don't know if that is somehow limited though it worked perfectly when i was on stock.
famac! said:
My settings seem correct as everything works except Gmail LED. I have the free version of Light flow so i don't know if that is somehow limited though it worked perfectly when i was on stock.
Click to expand...
Click to collapse
The new gmail has alerts for specific labels and stuff (at least in pro) -- are you sure you're attached to the right label? Also, not all of the colors work, but I think if the color doesn't work it just uses the closest color. I know the following work (although some of the colors aren't the exact shade you'd expect.):
Green
Red
Blue
Purple
Cyan
White
Yellow
FYI: When you quoted me I got an E-mail + LightFlow generated sound notification & light.
^^ Yeah the labels are set up correctly. I had it working perfectly when i was stock up until a few days ago. Even a reboot of the phone has still not fixed it. I am stumped.
First things first: Hey everyone. Some of you may know me from other devices or because of some Moderator related business. Anyways, I recently thought I needed a tablet upgrade and so decided to order a shield tablet. I have been going through some threads, and was actually kinda surprised that this nice piece of technology doesn't have more development going on, especially regarding kernels.
After a few days of getting to know the tablet I noticed one very useful feature missing: sweep2wake, or at least doubletap2wake.
Unfortunately, though, Nvidia did not yet release the kernel sources for their marshmallow kernel, so I can't add it myself that easily. Which is why I had to make a detour adding s2w to the kernel using a module. This, however, has the downside that I cannot prevent the touchscreen driver from suspending, nor get the information whether the screen is turned on or off. Therefore I need a dedicated background service to retrieve exactly this information and reenable the touchscreen driver.
Requirements
Android Marshmallow
Root
Both the kernel module and my app
Installation
Download the latest kernel module and app
Install the app
Push the kernel module to your internal storage (/sdcard/sweep2wake.ko)
Usage
Open the app and press "insmod"
--> this will load the module but also set selinux to permissive
--> S2W is now up and running, but can only be used to turn the screen off
Press "start" to start the background service
--> This will reenable the touchscreen driver when the screen got turned off and also tell S2W that the screen is turned off
--> S2w will now work perfectly fine as long as the tablet is plugged in or another app holds a wakelock. If this is not the case and the tablet is in deep sleep, you will not be able to wake the device and touch input might not work after turning the screen on manually. If this is the case, just turn the screen off and back on and it will work as usual again.
--> In order to wake the device at all times, start the service with the "enforcing" switch turned on. This will make the service hold a wakelock while the screen is off. However, your battery will drain rather rapidly as the tablet cannot go into deep sleep
To stop the service again, simply press "stop"
Keeping in mind that this is still in a rather early stage, I did not add a "enable on boot" option for the service.
I really hope that Nvidia releases the M sources soon, so I can add S2W and DT2W to the kernel properly.
This module should be compatible with all (current) Marshmallow firmwares, on both the old and new shield.
XDA:DevDB Information
Sweep2Wake Module, Kernel for the Nvidia Shield Tablet
Contributors
laufersteppenwolf
Source Code: https://github.com/laufersteppenwolf/android_kernel_nvidia_shieldtablet_modules
Kernel Special Features: Sweep2Wake
Version Information
Status: Beta
Created 2016-01-16
Last Updated 2016-01-22
They've got a new repository up, which is not yet listed on their web page. Haven't checked, but these should be the marshmellow sources.
repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r7-partner -m tlk/shieldtablet.xml
repo sync -j5
njhuiz said:
They've got a new repository up, which is not yet listed on their web page. Haven't checked, but these should be the marshmellow sources.
repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r7-partner -m tlk/shieldtablet.xml
repo sync -j5
Click to expand...
Click to collapse
Nope, it's not the MM kernel. these sources are actually what my module is based on
laufersteppenwolf said:
Nope, it's not the MM kernel. these sources are actually what my module is based on
Click to expand...
Click to collapse
First of all, thnx for your work and bring this expected feature.
About sources, we are using rel-24-sb-r1-partner branch from Nvidia for CM-13.0 and Bliss6. This seems to be latest code for latest K1 MM OTA. Have you explored it ?
Very nice, thanks for starting work on the tablet. I've got requests for adding this to my CM builds, but I don't have the kernel experience to add it myself. Once I've gotten both roth and shieldtablet stable on cm-13.0 and pushed to official, I will want to look into pulling this in for both. It should port to the M kernel pretty directly. Maybe a difference in the mach-tegra file, but that should be it. The touch failing to re-enable sounds very familiar... Custom ROMs had the issue for a while, caused by blobbing the powerhal. It was mitigated for a while, but after we started compiling the powerhal, we haven't seen it since. I'd be interested to know if this was compiled into the kernel (not as a module) for a custom ROM if the problem still occurs.
Did you upload the code for the apk somewhere? I'm kinda curious how you are triggering touch enable/disable. By writing to the sysfs file like the powerhal does?
Are there any other obvious features missing in the kernel? The one that bugs me a bit is volume/button controls on headphones. Seems that needs kernel support and Nvidia didn't write that in.
BitOBSessiOn said:
First of all, thnx for your work and bring this expected feature.
About sources, we are using rel-24-sb-r1-partner branch from Nvidia for CM-13.0 and Bliss6. This seems to be latest code for latest K1 MM OTA. Have you explored it ?
Click to expand...
Click to collapse
No, I did not. I will look into it, though, as I definitely need a better kernel than the stock one I am running ATM
If you need a hand some time, feel free to drop me a PM and I will see what I can do
Steel01 said:
Very nice, thanks for starting work on the tablet. I've got requests for adding this to my CM builds, but I don't have the kernel experience to add it myself. Once I've gotten both roth and shieldtablet stable on cm-13.0 and pushed to official, I will want to look into pulling this in for both. It should port to the M kernel pretty directly. Maybe a difference in the mach-tegra file, but that should be it. The touch failing to re-enable sounds very familiar... Custom ROMs had the issue for a while, caused by blobbing the powerhal. It was mitigated for a while, but after we started compiling the powerhal, we haven't seen it since. I'd be interested to know if this was compiled into the kernel (not as a module) for a custom ROM if the problem still occurs.
Did you upload the code for the apk somewhere? I'm kinda curious how you are triggering touch enable/disable. By writing to the sysfs file like the powerhal does?
Are there any other obvious features missing in the kernel? The one that bugs me a bit is volume/button controls on headphones. Seems that needs kernel support and Nvidia didn't write that in.
Click to expand...
Click to collapse
First off, no, you cannot just cherry-pick this patch into another kernel. This is made to be working as a kernel module only. It'll most likely cause the kernel not to boot anymore when cherry-picked.
It should be rather easy to implement this directly into a kernel, though.
No, I did not upload the app's sources yet, I can, though, if you want me to. And yes, I do enable the ts driver by writing to the sysfs node.
Well, TBH, there's a lot that can be done to the kernel, it just depends on what one thinks is really necessary
Volume control is not kernel related, though. The kernel only passes the information "vol up pressed" on to the Android system, everything else is handled by Android's framework.
laufersteppenwolf said:
First off, no, you cannot just cherry-pick this patch into another kernel. This is made to be working as a kernel module only. It'll most likely cause the kernel not to boot anymore when cherry-picked.
It should be rather easy to implement this directly into a kernel, though.
Click to expand...
Click to collapse
I just glanced through the commit, but nothing stood out to me as working only for 'm' vs. 'y'. What in particular would cause a problem?
laufersteppenwolf said:
Well, TBH, there's a lot that can be done to the kernel, it just depends on what one thinks is really necessary
Volume control is not kernel related, though. The kernel only passes the information "vol up pressed" on to the Android system, everything else is handled by Android's framework.
Click to expand...
Click to collapse
I looked into the volume control thing a little while back. The code to detect the inaudible tone used by the headset buttons wasn't implemented in the stock kernel at that time. I haven't looked at the M kernel yet, but I expect it's the same.
I'm not one for extravagant features in a kernel, especially for the official CM devices I maintain. But when there are features missing that people expect as standard these days, I'll make an exception. D2W is one (not that I'd use it personally, but enough people expect it), and headset volume is another.
Steel01 said:
I just glanced through the commit, but nothing stood out to me as working only for 'm' vs. 'y'. What in particular would cause a problem?
I looked into the volume control thing a little while back. The code to detect the inaudible tone used by the headset buttons wasn't implemented in the stock kernel at that time. I haven't looked at the M kernel yet, but I expect it's the same.
I'm not one for extravagant features in a kernel, especially for the official CM devices I maintain. But when there are features missing that people expect as standard these days, I'll make an exception. D2W is one (not that I'd use it personally, but enough people expect it), and headset volume is another.
Click to expand...
Click to collapse
well, the general implementation including the modification of some other files (makefile, scripts,..)
But good news is I got the 3.10.67 kernel booting, which means it's time for yet another werewolf kernel S2W and DT2W is already implemented, but not yet properly working. Needs some more work.
My bad, I thought you were referring to the device's volume buttons and the "keep pressed for skip" feature
Haven't looked into that either TBH.
Hey man! Thanks for this feature! I used your kernel on LG Optimus 4X HD hope you can give us more rom development. Best of luck!
Enviado do meu wx_na_wf através de Tapatalk