Credits goes to st.matt, he gets full credit for the programming. He seemed a little busy, so I thought I'd spread the news so you guys can implement into your builds.
st.matt said:
Also just a run-down of how it works for anyone that is interested:
I use three different elements to get it working. Firstly, I use a small addition to surfaceflinger to set a system property (sys.orientation.landscape) to 1 when it is in landscape mode (either 90 or 270 degrees rotation) and 0 when it is in portrait mode (0 degrees rotation).
When this is set an init service will start depending on the value of sys.orientation.landscape, which in turn starts a script (/system/etc/rotate_lights.sh) which takes the brightness value from the expected led class (ie. if it's changing to landscape it will look at /sys/class/leds/button-backlight-portrait/brightness) and then set this to the new orientation's led class.
The third part is a small modification to the lights lib which also checks that system property when making changes to the button backlight brightness so that it sets it to the correct class.
Click to expand...
Click to collapse
The necessary files/code are on Virtuous' ICS vivo repository: https://github.com/vivo-ICS/android_device_htc_vivo, and you will also need the patched proprietary libsurfaceflinger.so that references to the changes.
Any way to make this backward compatible with cm7.2?
Un1c0de said:
Any way to make this backward compatible with cm7.2?
Click to expand...
Click to collapse
made a CM7.2 kang for you Inc2 users.
All I did was put in the latest commits as of March 03 2012 and added the rotating softkeys. I can't really test it because I don't have an Inc2, so back up your data in case you are not sure if it will work.
You can flash this without wiping if you are on 7.x already.
For the IncS, I know the rotating buttons for them are not perfect. Sometimes you have to toggle the brightness to get it working. Other times it might take a few seconds to rotate instead of immediately. This is because this script was originally written for ICS roms in mind, but it's backwards compatible with GB.
http://www.mediafire.com/?lggqggdx1m4n656
Wow thanks Kaijura. Downloading now, will post back with results
Sent from my Incredible 2 using xda premium
Thanks Kaijura for posting the info, and the CM7 build. Appreciate it a lot
Is this rom dependent? It will only work on cm 7.2? has anyone tried it on miui? Or any other roms?
Sent from my Incredible 2 using xda premium
Ihatepullups said:
Is this rom dependent? It will only work on cm 7.2? has anyone tried it on miui? Or any other roms?
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
knipp21 said:
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Ah, that blows would have been cool... Hey if someone points me in the right direction, I'll try: I know how to use adb and the sdk and I'm an experienced ROM'aholic
Sent from my Incredible 2 using xda premium
Awesome. Hopefully I have time tonight to check it out. Thanks
knipp21 said:
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Ihatepullups said:
Ah, that blows would have been cool... Hey if someone points me in the right direction, I'll try: I know how to use adb and the sdk and I'm an experienced ROM'aholic
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
its different for miui, because we dont build it from source and cant cherry pick commits
miui is more like a sense rom port that uses cm9 or another aosp rom as a "base"
any significant changes have to be done in smali, which is more involved than java source....i k nowwhat has to be changed (or at least part of it) and where for rotating buttons in miui by diffing the builds from aerovan before and after it was implemented but it was a no go on my part...and didnt seem worth the effort to keep pursuing it atm
I tried this yesterday. My phone wouldn't get past the HTC boot screen. I ended up having to pull the battery and reflash my current ROM.
zohner said:
I tried this yesterday. My phone wouldn't get past the HTC boot screen. I ended up having to pull the battery and reflash my current ROM.
Click to expand...
Click to collapse
Hmm, well I guess that didn't work. If you push /system/lib/libsurfaceflinger.so from an earlier working build you should probably be able to boot.
I just copied the file over from the vivo build which seems that it doesn't work with the vivow.
Guess the vivow surfaceflinger is done differently.
kaijura said:
made a CM7.2 kang for you Inc2 users.
All I did was put in the latest commits as of March 03 2012 and added the rotating softkeys. I can't really test it because I don't have an Inc2, so back up your data in case you are not sure if it will work.
You can flash this without wiping if you are on 7.x already.
For the IncS, I know the rotating buttons for them are not perfect. Sometimes you have to toggle the brightness to get it working. Other times it might take a few seconds to rotate instead of immediately. This is because this script was originally written for ICS roms in mind, but it's backwards compatible with GB.
http://www.mediafire.com/?lggqggdx1m4n656
Click to expand...
Click to collapse
Just tried a flash over but didnt work for me. I guess I can always try a wipe and install.
This wouldn't be hard to add to Miui -- as long as they have no weird additions to libsurfaceflinger. You just need the patched liblights, patched libsurfaceflinger (built for CM), script in /system/etc and changes to init.vivo.rc (or init.vivow.rc for Inc2).
Requires no changes to smali or framework.
The other thing is that if someone wants to clean it up and submit it to CM then the MIUI team will pick it up themselves (someone already did this but didn't seem to have to skill / couldn't be bothered to clean it up to their standards and also didn't really submit it correctly).
I would do this but I don't really have the time these days.
Also: I suspect the problem with the lights not working sometimes could be solved just by adding the conditional I have that checks first to see if the brightness is zero to both orientations (in rotate_lights.sh). I will have a quick look at this soon.
just wanted to share a slight modification in the script. When the brightness level is set to the least the leds turn off completely. The attached script makes sure the leds do not turn off completely at this instance. Unzip the file and replace the file in your /etc/ folder. You may want to make a backup of your existing rotate_lights.sh just in case. Ensure the permissions on the file are the same as before after copying.
Just realized that the settings work only the first time when the phone is rotated. I guess I need a better fix. Sorry, remove the attachment as it has undesired issues. Fix No damn good.
Related
Given the recent explosion of nightly users, there is a need for a place to discuss them, and/or ask if other users are having similar issues as you...this is that place
DO NOT: Post to the bug tracker
DO NOT: Open another thread (Please)
DO NOT: Think of this as official forum support; this thread will be strictly user to user support. Don't expect CM-dev help.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
Download: link
Google Apps addon:
Mirror: link
Mirror: linkChangelog: @cmsrc
These threads are coming along nicely, love it, absolutely love it. Great work.
sent from my incarcerated Incredible 2
I'd have to agree with my bud above me here. Good job on organization!!
Sent from my Incredible 2 using XDA Premium App.
I'm really not trying to be a ****, but aren't nightly's specifically for soak testing new releases and squashing bugs. I had a d1 and used cm7, but not the nightly's. I always thought they were for testing. But apparently not. So, could someone explain their purpose to me? I'm honestly curious.
Sent from my Incredible 2 with Xda app
devator22 said:
I'm really not trying to be a ****, but aren't nightly's specifically for soak testing new releases and squashing bugs. I had a d1 and used cm7, but not the nightly's. I always thought they were for testing. But apparently not. So, could someone explain their purpose to me? I'm honestly curious.
Sent from my Incredible 2 with Xda app
Click to expand...
Click to collapse
The purpose is to enjoy the progress. They don't want bug reports because we are all aware of the fact that there are bugs, that's the nature of the beast. Today's build will have different bugs than tomorrow's, if we posted every lit bug that we experience then, well there would be no time to build, the team would just read bug reports all day. Over the course of time the team fixes bugs that recur and when enough things have been worked out they release an RC.
So....enjoy!
Thunderbolt!
So we don't have nightlies yet, and this thread is in anticipation of the merge?
devator22 said:
I'm really not trying to be a ****, but aren't nightly's specifically for soak testing new releases and squashing bugs. I had a d1 and used cm7, but not the nightly's. I always thought they were for testing. But apparently not. So, could someone explain their purpose to me? I'm honestly curious.
Sent from my Incredible 2 with Xda app
Click to expand...
Click to collapse
They are nightly build tests - nothing more. It tests the current state of the code repository, to make sure the build isn't broken. Users wanted to see them, so we share them.
xgunther said:
So we don't have nightlies yet, and this thread is in anticipation of the merge?
Click to expand...
Click to collapse
No. Merge was done a few days ago. Nightly build started last night.
attn1 said:
No. Merge was done a few days ago. Nightly build started last night.
Click to expand...
Click to collapse
So will they be posted here, or?
EDIT: disregard.
Sent from my Incredible 2 using Tapatalk
Is cmsrc twitter not being updated? 0 nightly already great. Only issue I have seem is in call volume is quite low
Sent from my Incredible 2 using Tapatalk
I didn't know we had a nightly build section or I would of been posting here.
I am currently running full-3 and I have been having issues with using the phone overseas. I am in japan on softbank and it is not picking up any signal.
The signal is wcdma and on the stock rom I could set it to that and get phone/sms but no data. I added the correct apn (after trying to get it to work properly) and I am still not getting anywhere.
Another thing I am worried about is the whole activate your phone part. When I flash it, it always has the activate screen and no matter what it will not activate so I don't know if that has anything to do with it. I hope not since I am not in the states so I can't just hop on the network and do it.
I'm on build 3 and my compass flips north and south in the maps application anyone else having this? I know it was in the stock rom but its fixed in the gb leak.
Sent from my Incredible 2 using Tapatalk
cheifkeiff said:
I'm on build 3 and my compass flips north and south in the maps application anyone else having this? I know it was in the stock rom but its fixed in the gb leak.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
I can confirm this.
Sent from my Incredible 2 using Tapatalk
Anyone else having any of the following issues?
- Home button does nothing at all (even holding it down)
- Volume buttons wake device (even though the setting for this is disabled in CM Settings)
- Cannot seem to enable the standard lockscreen at all (even when I enable a password or pattern lock - it just wakes up at the home screen or wherever I left off)
I'm running nightly #3, but I also had these issues with the beta.
xgunther said:
I can confirm this.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
I too have the reversed compass on maps. Strangely, the compass app on market seems to be correct.
megarek said:
I too have the reversed compass on maps. Strangely, the compass app on market seems to be correct.
Click to expand...
Click to collapse
Yep same thing happened to me on the stock rom and this one, compass app shows direction fine though. Also gps seems to lock quickly just the compass is just not showing the correct direction.
cheifkeiff said:
Yep same thing happened to me on the stock rom and this one, compass app shows direction fine though. Also gps seems to lock quickly just the compass is just not showing the correct direction.
Click to expand...
Click to collapse
Yep, known issue on stock rom: http://community.vzw.com/t5/DROID-I...-Maps-Google-Sky-and-Google-Earth/td-p/530726
I hope this can be fixed in CM7.
mturco said:
Anyone else having any of the following issues?
- Home button does nothing at all (even holding it down)
- Volume buttons wake device (even though the setting for this is disabled in CM Settings)
- Cannot seem to enable the standard lockscreen at all (even when I enable a password or pattern lock - it just wakes up at the home screen or wherever I left off)
I'm running nightly #3, but I also had these issues with the beta.
Click to expand...
Click to collapse
Sounds like a bad wipe. Wipe wipe wipe data/cache/dalvik-cache, then try again.
xgunther said:
Sounds like a bad wipe. Wipe wipe wipe data/cache/dalvik-cache, then try again.
Click to expand...
Click to collapse
Hmm well that sucks to do all of it over again. But I guess it's worth it. I'll try it and report back.
Sent from my Incredible 2 using XDA App
Never done nightlys...do I need to do a wipe before I flash these? Or can I install over the cm7 I currently have?
sent from my incredibly awesome incredible 2 with cm7
My apologies to those who were waiting for me to post a super-clean build. I've been doing absolutely nothing with the Continuum for the last 2+ weeks.
I've finally come across the solution to one of the fixes I've been really wanting for this phone, and one of the primary reasons that come September 20th, I'm ordering a new phone with my wife's free new-every-2.
I want to see USB debugging enabled by default, without timing out. To do so, the default.prop file needs to be edited, which is located in the boot image. I've taken a look at posts like http://forum.xda-developers.com/showthread.php?t=443994, but I don't know where to start. If anyone could point me in the right direction, it would be a great addition to custom roms.
What all do you want the kernel to do/have?
imnuts said:
What all do you want the kernel to do/have?
Click to expand...
Click to collapse
maybe compatibility with CM builds.. gingerbread support maybe or some porting of already completed fascinate builds.
Is it feasible/conceivable to build a kernel with BLN mod in it?
That's about the only thing I miss from the Fascinate world.
Sent from my SCH-I400 using XDA App
we have tried before on eclair to get it working, but with no success... The fact that our soft keys are built into the screen makes it probably impossible...... Sorry for the bad news :l
Sent from my SCH-I400 using xda premium
Yeah, that makes sense. I hadn't thought about the soft keys being part of one display. Oh well, that makes the 5th or 6th app I've purchased that I'll never use again.
Sent from my SCH-I400 using XDA App
imnuts said:
What all do you want the kernel to do/have?
Click to expand...
Click to collapse
I want to have adb enabled by default, and have the persist flag enabled as well. I get so damn annoyed when usb debugging disables itself. I want to usb tether my phone for internet access when I'm traveling, but the phones default settings make this impossible
EDIT: I just realized that Josh's EC07 ROM includes the necessary edits to the defaults.prop file. From what I had read elsewhere, the file was located in a boot image that required extraction and editing, and repacking. So as far as this thread is concerned, my problem is solved, or at least it appears to be.
EDIT: Damn I hate Samsung! Just another 10 days and I can order my DInc2 for free from Wirefly. I just tested whether or not USB debugging would auto-disable after a few minutes. Sure enough, after being tethered for about 5 minutes with EasyTether, USB debugging turns off. Problem NOT solved.
This build was edited by me (mainly for my personal use), based off of Zips Creamed Glacier's 3.11 release, but contains fixes I pulled from IceColdInsomnia 6.2.1.
I don't normally start dev threads, so bare with me (I'm no dev)
What's new:
- Practically everything that's included in Zips Creamed Glacier 3.11 - includes, FFC unlock, Working games (Draw Something does work!), mdj's kernel and so forth.
- I fixed the weather/geolocation issues found in 3.11
- I fixed the USB mount issue in 3.11 (you couldn't mount as a mass storage device while the phone was on [gave you two options that didn't work])
- I fixed the full signal bars issue (reported full bars at all times you'd have service)
- Also included the romcontrol.apk from IceColdInsomnia 6.2.1 and the settings.apk (for those who wanted ROM control settings but had to use the widget shortcuts to use them, you no longer have to as it's included in the settings)
- Replaced the systemui.apk with IceColdInsomnia 6.2.1's (you can haz 4g icons!)
- Replaced Trebuchet with Apex Launcher (This was part of my personal liking, Apex Launcher is the best ICS launcher IMO, try it out)
- May be forgetting something else...
All of the fixes mentioned above were fixed by pulling their respective files from IceColdInsomnia 6.2.1
* Don't ask any of the devs for wifi calling, as it's assumed to not work until T-Mo updates wifi calling for ICS (which should be whenever a T-Mo phone officially has ICS) or unless a dev performs some sort of magic ritual and get it working and stable
------edit------
As of 3/29, 9:07 PM (Lol)
This is what I've got, thanks to one of our fellow users that found me on twitter and showed me this (I don't know what his user name is on XDA)
http://forum.xda-developers.com/showpost.php?p=24210094&postcount=932
My thanks goes to:
- zipsnet - his 3.11 build was used as a base, that's why games work and etc. (ICS thread link here: http://forum.xda-developers.com/showthread.php?t=1555574)
- blackwing182 - for certain files from his build to fix usb and location issues and the AOKP files for ROM control (will post which ones they were specifically later) (ICS thread link here: http://forum.xda-developers.com/showthread.php?t=1551456)
and those also to those mentioned in their thanks lists (tell me who I forgot to mention and I'll add you here)
Enjoy!
Downloads:
Original (From my minus account, lol): taken down for the time being...
kingsteve032's upload (should be faster to DL!): taken down for the time being...
Also:
- Here's the flashable low mic fix by lincore: http://forum.xda-developers.com/showpost.php?p=24008900&postcount=531
- Don't use the DSPManager that comes with the ROM and complain about volume levels. I'm not sure if this info is correct, but after snooping around in other device forums, like always, a dev put in his OP that the DSPManager isn't really configured for ICS but instead for CM7. I'm not sure if this is true or not, but I don't use the DSPManager anyways so
And:
- Check out this dev's new awesome and useful app: http://forum.xda-developers.com/showthread.php?t=1559185
Reserved...
Just in case...
I dont see the DL link!
There it is
And, did you include fixes such as Low-mic volume? And did you include the Mail app or does it need to be flashed?
Just posted it! I had to look for them, lol
linknight said:
I dont see the DL link!
There it is
And, did you include fixes such as Low-mic volume? And did you include the Mail app or does it need to be flashed?
Click to expand...
Click to collapse
Basically all that you would find in zips' build, I think the only app I took out was trebuchet and the only app I added was apexlauncher. If not, I can fix them later.
For the low mic issues, I didn't put those in my zip, but I can post the link to the fix in my OP.
I love this version of Zip's rom. Very stable. Daily driver. Thank you.
Excellent job! Let's hope the "OMG, you can't combine two different open source projects, that's disrespect!" trolls don't crap up this thread.
Sizzlechest said:
Excellent job! Let's hope the "OMG, you can't combine two different open source projects, that's disrespect!" trolls don't crap up this thread.
Click to expand...
Click to collapse
I was actually wondering why this wasn't done sooner, but since I know so little about how development works, I kept my mouth shut. It seemed like such a logical thing to do.
systemui.apk gives you the 4G icon
BUMP^^^
Downloading now will report, thank you
Update: working well smooth no fcs yet, face unlock works sometimes.
linknight said:
I was actually wondering why this wasn't done sooner, but since I know so little about how development works, I kept my mouth shut. It seemed like such a logical thing to do.
Click to expand...
Click to collapse
Lol, I started on this as soon as zips released 3.11 cause I wanted to fix games and try face unlock but he had the issue with the full signal bars and stuff.
blackwing182 said:
systemui.apk gives you the 4G icon
Click to expand...
Click to collapse
Haha, my bad. I don't remember which one it was that did it, but I did include both.
-edit-
I fixed it with my ninja edit skillz yo. Lol
Maybe I'm missing something... But I don't see a link
Sent from my MyTouch 4G using Tapatalk
cool! your own thread!
were you able to get wifi calling working?
Good job. Are you using mdj's kernel on this?
Sent from my HTC Glacier using Tapatalk
sckboy78 said:
Good job. Are you using mdj's kernel on this?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Yep, maybe I should add that in the post.
-edit-
I put it in there.
0.0 said:
cool! your own thread!
were you able to get wifi calling working?
Click to expand...
Click to collapse
No cause you didn't reply to my question!!! Lol
ringnutz said:
Maybe I'm missing something... But I don't see a link
Sent from my MyTouch 4G using Tapatalk
Click to expand...
Click to collapse
It's near the bottom of the OP...?
I2IEAILiiTY said:
It's near the bottom of the OP...?
Click to expand...
Click to collapse
Yezzir. Are you currently using tapatalk?, I'm guessing from your sig.
I2IEAILiiTY said:
No cause you didn't reply to my question!!! Lol
Click to expand...
Click to collapse
oh crud...skimmed over it haha. well, it went past the enabling screen. it actually connected, so i assume it worked. i never actually made a call on it tbh...
Someone please please PLEASE tell me if there is a way to tell the captive touchkeys to stay on when the screen backlight is on. I may be in the minority but I can't stand the lights going out while I'm using the phone. Sounds simple but I REALLY hate them going off. There wasnt an issue with the unofficial CM10 alpha 5(?). At one time I had a rom that allowed me to set a timeout in seconds OR to match the backlight. That would be perfect in my mind. It would be great if the keyboard backlights were on any time the keyboard is open (IMO). If I'm in the minority then someone please tell me where I can set it at the OS level for just me. If I can't find a solution then I will have to go back to alpha 5 and stay there.
I have googled everything I can think of. I keep getting pages about a "great" new beature of CM9 that allows you to disable the backlight altogether. Great for some maybe but not me. I bring that up to say that I have tried to find the answer on my own first.
Is your capacitive lights feature unchecked in the advanced settings? I think the majority of people who have used samsung phones don't need the lights, so that's why this feature has been implemated.
Sent from my SPH-D700 using xda app-developers app
It is unchecked. I have no problem with the ability to disable but would love to have the option to have them stay on (JB Default) when the screen is on. I don't like having to guess where the buttons are when it's dark out. It's petty I know but it really does bother me enough to not use the rom If I can't change it.
Please post questions in Q&A
Thread moved
Thanks
FNM
FWIW - I'd like to see this as an option, too. It's an annoyance, but not a show stopper. I'm actually getting pretty good at guessing where the capacitive keys actually are, but sometimes get ticked at fumbling for them.
Al
Bump (he said sheepishly)
Can any of the kernel or ROM devs provide some words of wisdom here? On Epic TW-based ROMs, there's definitely a setting to have the capacitive key backlighting timeout match either the screen timeout or the keyboard lighting timeout (I don't remember which).
Thanks.
Al
arschend said:
Bump (he said sheepishly)
Can any of the kernel or ROM devs provide some words of wisdom here? On Epic TW-based ROMs, there's definitely a setting to have the capacitive key backlighting timeout match either the screen timeout or the keyboard lighting timeout (I don't remember which).
Thanks.
Al
Click to expand...
Click to collapse
This functionality would have to be added to the CM framework. The framework is what controls the 6 second timeout and a configurable timeout setting has not been coded. Anyone is free to work that out and submit it to the CM gerrit system
Sent from my SPH-D700 using xda app-developers app
I am a programmer but don't have the slightest clue where to even begin. To be honest, it's not worth it if I have to work for months to get up to speed to do it myself. I'll have to look at other roms. Sad because I love this rom except for this one thing.
Sent from my SPH-D700 using Tapatalk 2
reiter01 said:
I am a programmer but don't have the slightest clue where to even begin. To be honest, it's not worth it if I have to work for months to get up to speed to do it myself. I'll have to look at other roms. Sad because I love this rom except for this one thing.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Understandable, because that's no easy task. But another alternative is to build your own kernel, and revert this patch which is how I fixed the capacitive lights in the 3.0 kernel. You could effectively break them again. Don't worry, they will still go off when you turn off the screen, they just won't timeout after 6 seconds.
I finally got brave
bbelos said:
Understandable, because that's no easy task. But another alternative is to build your own kernel, and revert this patch which is how I fixed the capacitive lights in the 3.0 kernel. You could effectively break them again. Don't worry, they will still go off when you turn off the screen, they just won't timeout after 6 seconds.
Click to expand...
Click to collapse
A year has passed. Updates have come and gone. I even switched to another phone and back to the Epic4G. Same thing bugged me as always. I took the leap and set up a virtual machine so I could compile CM 10.1. I did a test compile and came out fine. I then made the changes you mentioned (that made more sense once I got used to the built process) and it WORKED!
I now have CM 10.1 fully working with the button backlight staying on as long as the screen backlight. I LOVE IT.
Thank you so much (a year late).
reiter01 said:
I now have CM 10.1 fully working with the button backlight staying on as long as the screen backlight. I LOVE IT.
Click to expand...
Click to collapse
I've had my Epic for a week, running CM 10.1, and this bugs the snot out of me too. Any chance you could PM me a link to your build? :laugh:
Sure
I'll try to figure out where to upload it. Keep in mind I know nothing about coding for Android. It's simply CM 10.1 (newest) for EpicMTD with 2 numbers changed and then compiled. I do like that the ability to control the brightness of the buttons still works. I don't like them super bright but I do want them always on.
Download
Here is a download of the rom I compiled. Use at your own risk.
http://d-h.st/iuU
reiter01 said:
Here is a download of the rom I compiled. Use at your own risk.
http://d-h.st/iuU
Click to expand...
Click to collapse
Understood, and thank you good sir. :highfive:
UPDATE: Loaded, booted, and is running without a hitch. You have solved my one major gripe with CM on my Epic. Thankyouthankyouthankyouthankyou!
Glad I could help someone else. CM10.1 is so near perfect in every way, it was frustrating to have such an annoying "flaw". In the older version of CM they didn't have the ability to adjust the brightness of the buttons so I can understand some people wanting them off or fast timeout. If I ever have some spare time I will try to add this as a feature to the menu but I doubt it will ever happen.
@bbelos
Any way I can get my hands on your most recent 4.4 build source so I can build it with the bug put back in?
reiter01 said:
@bbelos
Any way I can get my hands on your most recent 4.4 build source so I can build it with the bug put back in?
Click to expand...
Click to collapse
Well,
device: https://github.com/cyanogenmod/android_device_samsung_epicmtd/tree/cm-11.0
kernel: https://github.com/cyanogenmod/android_kernel_samsung_epicmtd/tree/cm-11.0
whatever is in here: http://review.cyanogenmod.org/#/q/epicmtd+status:open+branch:cm-11.0,n,z
Patch
bbelos said:
Well,
device: https://github.com/cyanogenmod/android_device_samsung_epicmtd/tree/cm-11.0
kernel: https://github.com/cyanogenmod/android_kernel_samsung_epicmtd/tree/cm-11.0
whatever is in here: http://review.cyanogenmod.org/#/q/epicmtd+status:open+branch:cm-11.0,n,z
Click to expand...
Click to collapse
Thank you very much. I am running your build now but would love to make my 1 edit. Is it possible, without total rebuild or large headache, to make a patch for the one file?
reiter01 said:
Thank you very much. I am running your build now but would love to make my 1 edit. Is it possible, without total rebuild or large headache, to make a patch for the one file?
Click to expand...
Click to collapse
One other thing that might make things easier, go to Settings->Buttons->Backlight, and set the timeout for "Don't turn off" and see if that behaves to your satisfaction.
Sent from my SPH-D700 using xda app-developers app
Awesome
bbelos said:
One other thing that might make things easier, go to Settings->Buttons->Backlight, and set the timeout for "Don't turn off" and see if that behaves to your satisfaction.
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
I installed your cm11 but havent gone through and tweaked it out. Looks like that might do the trick. I have found a couple bugs (to be expected).
1. If on a call and hit home, there is no way to get back to hang up. Have to power off.
2. While on home screen. Hitting the "menu" button at the bottom and choosing "settings" brings up the launcher3 settings. Used to be the android settings...maybe it's a change. Not a deal breaker but I prefer the old way.
Thank you for all your work. I wish there was some way I could help you out.
Does anyone know if there is a working app mod or hack to enable the incredible2 to have nexus-like on-screen buttons and disabling the lights and functions of the hardware buttons like on ParanoidAndroid has it?
cowboyv said:
Does anyone know if there is a working app mod or hack to enable the incredible2 to have nexus-like on-screen buttons and disabling the lights and functions of the hardware buttons like on ParanoidAndroid has it?
Click to expand...
Click to collapse
This is the main reason I stick with PA. If someone can mod the framework of the rom you are using, it may be option, but most of the roms don't have that built in. You might mention it in the thread of the rom you use and see if someone can hook you up.
Yeah, I'm wondering if maybe you can copy and paste the frameworks folder from PA rom to the other rom and if that would activate the on screen buttons.
I doubt that would be a good idea, but I'm not the one to answer that one.
Sent from my Incredible 2 using xda premium
cowboyv said:
Yeah, I'm wondering if maybe you can copy and paste the frameworks folder from PA rom to the other rom and if that would activate the on screen buttons.
Click to expand...
Click to collapse
Just a warning, that very well may put your phone into a boot loop, if you decide to try it......BACKUP first
Sent from my Incredible 2 using xda app-developers app
@Phantom: according to this thread it's just a matter of decompiling framework-res.apk, making some changes and then recompiling the whole thing, which is why I'm thinking maybe it is as simple as copying/pasting the apk.
@Tricsuit: Yeah, I know. I already learned my lesson and before attempting stupid ideas like this one, I run a full back up of the rim, settings, apparently and data, and then make sure to save the back up file in my box to be able to retrieve it from my computer just in case something else hiccups.
cowboyv said:
@Phantom: according to this thread it's just a matter of decompiling framework-res.apk, making some changes and then recompiling the whole thing, which is why I'm thinking maybe it is as simple as copying/pasting the apk.
@Tricsuit: Yeah, I know. I already learned my lesson and before attempting stupid ideas like this one, I run a full back up of the rim, settings, apparently and data, and then make sure to save the back up file in my box to be able to retrieve it from my computer just in case something else hiccups.
Click to expand...
Click to collapse
Thanks for the share m8, I will try to look into this one more over the weekend. If you decide to give it a go with a copy and past let me know how it works out.
Yeah, I'm on call for the next couple of days so I won't be able to play with the rom, but if I'm able to make it work I'll post it here. :beer:
Welp, I began to toiler around with this, succeed in decompiling res-framework.apk, changing the bools, arrays and dimens values and added the menu images, basically all the way down to step 5, but I can't seem to recompile it back into .apk... uhm... a little help guys? ^^;