Related
Just curious since CM has this function... Being a new Amon-Ra user this seems like something that would make the users life much easier. I previously has all my custom things in a folder on my sd called EvoDev and roms in one folder, zip mods in another, etc.... I now must leave all my stuff on root of sd or move back and forth with a file manager if I want to do anything.
I'm not mad or anything, just curious as to why Amon-Ra doesn't have this ability. Anyone know?
P.S. - Sorry if this is wrong section but I didn't view it as a general Q&A... It was more specific to a function of a program that is used daily in development so I thought this would be the appropriate place to ask.
leenypost said:
Just curious since CM has this function... Being a new Amon-Ra user this seems like something that would make the users life much easier. I previously has all my custom things in a folder on my sd called EvoDev and roms in one folder, zip mods in another, etc.... I now must leave all my stuff on root of sd or move back and forth with a file manager if I want to do anything.
I'm not mad or anything, just curious as to why Amon-Ra doesn't have this ability. Anyone know?
Click to expand...
Click to collapse
i wish it had this funcion. this is the only reason why i do not use it.
because he hasn't implemented, 2.0 is on the horizon, there is potential its going to be implemented, however something so simple can easliy be worked around
2.0 can but amon-ra hasn't ported it over to the evo yet.
Sent from my PC36100 using XDA App
xlGmanlx said:
however something so simple can easliy be worked around
Click to expand...
Click to collapse
Are you saying there is a way to make it see past the root? I can't figure it out. Please elaborate..
If you are just saying it is easy to work around as in it is easy to just move my files to root of sd.... Well sure, it isn't hard to do..... but it does take more time.... And say you are doing something complicated requiring flashing a few things one after the other... Well... That becomes a bit of a PITA if you ask me... Especially after using CM for so long....
I like Amon-Ra better actually... Aside from the lack of seeing past root of SD...
As I said, I'm not mad, just wanted to know if maybe a change was in the works or if anyone knew a way to force seeing further.
no way around it, but if you are by a computer, enabling USB mode allows you to mount the SD card and manage it while in recovery.
leenypost said:
Are you saying there is a way to make it see past the root? I can't figure it out. Please elaborate..
If you are just saying it is easy to work around as in it is easy to just move my files to root of sd.... Well sure, it isn't hard to do..... but it does take more time.... And say you are doing something complicated requiring flashing a few things one after the other... Well... That becomes a bit of a PITA if you ask me... Especially after using CM for so long....
I like Amon-Ra better actually... Aside from the lack of seeing past root of SD...
As I said, I'm not mad, just wanted to know if maybe a change was in the works or if anyone knew a way to force seeing further.
Click to expand...
Click to collapse
david279 said:
2.0 can but amon-ra hasn't ported it over to the evo yet.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thank you. Do you know if he has stated that he plans to port it over at some point?
xlGmanlx said:
no way around it, but if you are by a computer, enabling USB mode allows you to mount the SD card and manage it while in recovery.
Click to expand...
Click to collapse
Ahhh, see I didn't know that since I just started using. Is that what that first option line is for? I think it has 2 letters then a dash and two more letters?
Thanks for the info.
yup, whatever says usb, you hit it, connect up your phone and its just like hard drive mode when your phone is on, life saver especially if you jack up something or wipe everything but forgot to move a ROM to the root of your HD
leenypost said:
Ahhh, see I didn't know that since I just started using. Is that what that first option line is for? I think it has 2 letters then a dash and two more letters?
Thanks for the info.
Click to expand...
Click to collapse
xlGmanlx said:
yup, whatever says usb, you hit it, connect up your phone and its just like hard drive mode when your phone is on, life saver especially if you jack up something or wipe everything but forgot to move a ROM to the root of your HD
Click to expand...
Click to collapse
Cool, thank you. That's a really great feature to have!!
your welcome, glad i could help you learn something about AMON
leenypost said:
Cool, thank you. That's a really great feature to have!!
Click to expand...
Click to collapse
Yep, I always use usb-ms mode when I do some flashes/updates since it's quick and easy. The file explorer would be a bonus, but amon ra is great the way it is. As long as I have my nandroid backup includes my 4G RSA keys then that's all that matters.
mizzos4 said:
Yep, I always use usb-ms mode when I do some flashes/updates since it's quick and easy. The file explorer would be a bonus, but amon ra is great the way it is. As long as I have my nandroid backup includes my 4G RSA keys then that's all that matters.
Click to expand...
Click to collapse
Does it back upo 4G-RSA keys automatically or do I have to do a separate backup for that?
i'm sure it will be implemented in the evo build soon. just be patient.
not to sound anal but unless it involves added 400 extra lines of code why not ad this basic feature from the get go?
I mean my sd was nicegly organized, now i have all they files jammed into the root of my sc card. Making trying to find one to flash out of gillions very hard
im not sure how to describe it. i guess the pixels mess up.. like you see a blur of colors than they go away. is this a problem? it never did this before.
yes it will show some rainbowish colors lol. then you will see the htc evo 4g splash screen
davidc23 said:
yes it will show some rainbowish colors lol. then you will see the htc evo 4g splash screen
Click to expand...
Click to collapse
is this a bad thing? it never did this before. my phone is just acting werid all over. the usb connects than disconnects. idk whats the problem...
Does that. Known issue, it is an AOSP-based recovery. The color is harmless
Sent from my PC36100 using xda premium
tropicalbrit said:
Does that. Known issue, it is an AOSP-based recovery. The color is harmless
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
i dont like it.. it scares me.. makes me think something is wrong with my phone.. like i said before it never happened until i rerooted my phone.
There's no problem, I thought the same thing. Now, I just accept it lol. No OCD for me.
World peace with no regard for human life.
It's not a problem. Just a bug in Recovery when you exit that causes brief screen tearing. Ignore it
hotboyray said:
im not sure how to describe it. i guess the pixels mess up.. like you see a blur of colors than they go away. is this a problem? it never did this before.
Click to expand...
Click to collapse
If your in Amon_RA recory? Search the creator name and you can hear it from him, unkown bug that he has not had the time to fix it yet, the pixelated gets worst as you flash newer ROMS.
Trying a updated version Recovery can help, but make sure what you chane it too is compatible with the ROM's and always double check OP's for updated material.
Flash/Installed ten Roms already and still going on Amon_RA, but I don't have proof that the ROM nor the recovery is the cause of some issues on the whole system to aact irracticaly.
Last but not least, you have not done a full search? Use the search bar makes it easier for you to find answers already asked?
Happens everytime i exit recovery. Amon-ra, clockwork, twrp. Its no big deal. In my 8 months of flashing it has never not happened. Its not a problem
Sent from my PC36100 using XDA App
Tekn010933 said:
If your in Amon_RA recory? Search the creator name and you can hear it from him, unkown bug that he has not had the time to fix it yet, the pixelated gets worst as you flash newer ROMS.
Trying a updated version Recovery can help, but make sure what you chane it too is compatible with the ROM's and always double check OP's for updated material.
Flash/Installed ten Roms already and still going on Amon_RA, but I don't have proof that the ROM nor the recovery is the cause of some issues on the whole system to aact irracticaly.
Last but not least, you have not done a full search? Use the search bar makes it easier for you to find answers already asked?
Click to expand...
Click to collapse
If you dont want to see it look for Amon's 2.2.1 recovery. That one did not have the issue. As a matter of fact here it is for you OCD based individuals out there. Remember to re-do all your nandroids as this will not restore any nandroids made with a newer version of Amon. You do know how to flash this right. Place on sdcard and rename to PC36IMG.zip
View attachment PC36IMG-Amon-V2.2.1.zip
This is gonna be the thread where I post the CWM I've been working on
First things first, here comes a newb question
Its my first time working with CWM, do i need the entire android source to compile it ? or just the source from koushs github. Also here is my nifty solution for navigation
The linux kernel has a few different types of events, the main two that CWM uses are
EV_KEY which is key event
and
EV_REL which is the trackball usually
the trackball even reads the movement and past a certain threshold fakes an up or down key event.
what I'm doing is adding in EV_ABS (touch event) to the input thread so that when it reads a screen touch it will fake a down key event similar to how the EV_REL works.
Now this is just the initial idea, in the future I want to make the touch event work like the trackball so to go up/down you swipe up/down, but this will do for now.
Controls will be as such
Tap = Move Down
Power = Select
Also once navigation is workin im going to be modifying it to set bootmode before exiting recovery so as to get rid of the current problem of not being able to exit recovery.
correct me if im wrong but here are the bootmodes i need
idme bootmode 0x4000 (normal boot)
idme bootmode 0x5001 (reboot recovery)
update 12/16 9pm
working on fixing some bugs with touch input and fixing rebooting from recovery
system is recognizing touch input properly and recovery boots properly, and when bootmode value is set to normal also boots the system correct.
Update 2
Got Reboot Working correctly from recovery and still workin out some touch nav bugs, will finish up tomorrow hopefully
UPDATE 12/17
Havent had time today t work on it like i planned, still issues with the touch input moving the cursor too far. Working on it now
UPDATE 12/18 1:30am
Touch Icons are drawn and in the correct position, working on mapping to correct functions
update 10:50pm
For some reason cannot get the touch coordinates to line up with the icons, even though the icons should be right over them.....not sure whats going on =/ gonna have to redo a few things to see what might be happening and why a key event isnt being injected
UPDATE 12/19
ReWriting the the input get for my touch controls to simplify it and make it easier to debug. Got work though till 4 so its gonna have to wait
awesome, I was sitting stuck in recovery on my mytouch today and using the trackball thinking of this as well. bravo my friend. seems very feesable
Sent from my HTC Glacier using xda premium
smirkis said:
awesome, I was sitting stuck in recovery on my mytouch today and using the trackball thinking of this as well. bravo my friend. seems very feesable
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Thats the idea, and though there are other touch recovery in development, I've been using CWM for a long time and like and trust its (at least for me) reliability
You have to have the full android source code. it goes in the bootable directory.
death2all110 said:
You have to have the full android source code. it goes in the bootable directory.
Click to expand...
Click to collapse
i figured...syncing now...will let you guys know the progress when there is some.
idme bootmode 4002 is fastboot
Sent from my SPH-D710 using xda premium
If you got questions ask koush he is always on twitter , but you can always go to CyanogenMOD irc on freenode
Sent from my SPH-D710 using xda premium
My understanding is that you need the whole source, but you can build just the recovery by typing: make recoveryimage.
There is a guide here:
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Hope you get farther then I did. I must have missed a step somewhere because I cant get it to build.
tecookie whats the issue you're having?
ok guys....touch recovery working...let me work out the kinks then we are good =]
It's weird. Seems like yesterday I was getting a different error.
# make recoveryimage
build/core/product_config.mk:196: *** device/amazon_kindl_fire/boot.img/device_boot.img.mk: PRODUCT_NAME must be a valid C identifier, not "full_boot.img". Stop.
Click to expand...
Click to collapse
I was following this guide and everything seemed to be going well up to the "build/tools/device/mkvendor.sh..." point. I got the "Done" output from that command but also a bunch of other stuff, some of which looked like they might have been errors.
I think I might just re-sync and try again.
---------- Post added at 06:22 PM ---------- Previous post was at 06:17 PM ----------
ECOTOX said:
ok guys....touch recovery working...let me work out the kinks then we are good =]
Click to expand...
Click to collapse
Wo! Awesome! Looking forward to it.
ECOTOX said:
ok guys....touch recovery working...let me work out the kinks then we are good =]
Click to expand...
Click to collapse
WHAT?! This is great news! I'm very excited to hear this! I don't even have a kindle fire yet, but plan on getting one for christmas and I was worried I might not be able to hack it as well as other devices without a usable recovery. But this is great news! Glad to see many talented devs working on the fire, just makes that 200$ a great investment
TWRP
dubt17 said:
WHAT?! This is great news! I'm very excited to hear this! I don't even have a kindle fire yet, but plan on getting one for christmas and I was worried I might not be able to hack it as well as other devices without a usable recovery. But this is great news! Glad to see many talented devs working on the fire, just makes that 200$ a great investment
Click to expand...
Click to collapse
you should check the TWRP it is a more basic recovery that works just like clockworkrecovery and its all touch its been in development but now i balive it is now fully working its just not up yet, you should check it out http://forum.xda-developers.com/showthread.php?t=1356425
Poler166 said:
you should check the TWRP it is a more basic recovery that works just like clockworkrecovery and its all touch its been in development but now i balive it is now fully working its just not up yet, you should check it out http://forum.xda-developers.com/showthread.php?t=1356425
Click to expand...
Click to collapse
I know, I'm not doing this just for a recovery, i want to see if i can do it =P Also I like CWM
ECOTOX said:
I know, I'm not doing this just for a recovery, i want to see if i can do it =P Also I like CWM
Click to expand...
Click to collapse
Any estimates when it'll be ready for release?
Sent from my Kindle Fire using xda premium
Earliest tomorrow
Sent from my Nexus S 4G using Tapatalk
ECOTOX said:
Earliest tomorrow
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
I can help you out if you want?
Poler166 said:
you should check the TWRP it is a more basic recovery that works just like clockworkrecovery and its all touch its been in development but now i balive it is now fully working its just not up yet, you should check it out http://forum.xda-developers.com/showthread.php?t=1356425
Click to expand...
Click to collapse
TWRP is a little better choice in recovery for tablets, but it never helps to have several options
death2all110 said:
I can help you out if you want?
Click to expand...
Click to collapse
Nah, thanks though, you've been alot of help already. I'm exhausted and need to sleep, so when I wake up i'm guessing around 4 more hours work and the initial release will be ready
Sent from my Nexus S 4G using Tapatalk
brett10 said:
TWRP is a little better choice in recovery for tablets, but it never helps to have several options
Click to expand...
Click to collapse
u mean never hurts? how can u claim twrp is a better choice when its not out. cwm is known by many and some just feel comfortable using it. stop trolling, development is development. even if they both got released the same day, people with choice will choose whatever recovery they wanna use. I personally like cwm, but would use whatever is available to our devices that's stable.
Congrats on the progress, can't wait to test it out.
Sent from my HTC Glacier using xda premium
When it was released it was not, I looked around but couldn't find anything recent pertaining to CWM touch specifically on the Galaxy Nexus. Can anyone confirm that it is fully functional? Thanks in advance!
Yup fully functional.
Sent From My Sprint Galaxy Nexus
Thank you sir! Already reached my limit of 8 but I will be back to properly thank you.
No problem. Just flash the .img with fastboot. Otherwise the touch version from ROM manager is 2$ or so.
Sent From My Sprint Galaxy Nexus
ÜBER™ said:
No problem. Just flash the .img with fastboot. Otherwise the touch version from ROM manager is 2$ or so.
Sent From My Sprint Galaxy Nexus
Click to expand...
Click to collapse
As soon as I got your confirmation I purchased it through ROM Manager, I like to support the devs when I have the funds available. I instantly like it, I dont have the best eyes so the larger text really helps me out. Thanks again, I won't forget to come back and thank you proper. :good:
Edit: Wow its so much faster than using the buttons!
WiredPirate said:
As soon as I got your confirmation I purchased it through ROM Manager, I like to support the devs when I have the funds available. I instantly like it, I dont have the best eyes so the larger text really helps me out. Thanks again, I won't forget to come back and thank you proper. :good:
Edit: Wow its so much faster than using the buttons!
Click to expand...
Click to collapse
The thing i hated with the regular CWM is there is like kinetic scrolling so it's really hard to select the one I wanted but with CWM Touch that isn't an issue
AshtonTS said:
The thing i hated with the regular CWM is there is like kinetic scrolling so it's really hard to select the one I wanted but with CWM Touch that isn't an issue
Click to expand...
Click to collapse
I agree, for me it would frequently skip up/down more than one notch. The other problem was the "back menu button disabled" causing the power button to turn the screen off/on instead of selecting the option. I finally learned you have to scroll past the first menu option 3x to enable it again.
Dont have those problems anymore! Definitely worth the $2.
Yeah, works brilliantly for me!
TWRP 2.2 is touch and is better. And they don't try to charge you.
It's very functional.
Thanks to Über, I've got to try it out for free and learn Something.
And because of his help, I've actually started making an app called app density. ^__^
------------------------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^
jesusice said:
TWRP 2.2 is touch and is better. And they don't try to charge you.
Click to expand...
Click to collapse
I know of TWRP but never had any reason to try it, plus I think it looks ugly. Can you elaborate on why you think it's better?
WiredPirate said:
I know of TWRP but never had any reason to try it, plus I think it looks ugly. Can you elaborate on why you think it's better?
Click to expand...
Click to collapse
It's the little things, like being able to see battery and time in recovery. Plus, it now has a keyboard so you can name nandroids in recovery or rename files since it's also got a file manager. It supports backing up partition sizes greater than 2GB which CWM doesn't. You can compress backups to save space. You can queue multiple zips to flash in sequence. If you use Tasker you can make automated, scheduled nandroids. I find it easier to navigate, like it was actually a recovery made to be touch and not just a recovery that had touch added. Swiping to flash gives me confidence I'm not gonna do anything stupid accidentily. Also, while in recovery pressing the power button will lock it so you have to swipe to unlock for those times when you're in recovery but need to put your phone in your pocket. Probably other things I'm missing.
jesusice said:
It's the little things, like being able to see battery and time in recovery. Plus, it now has a keyboard so you can name nandroids in recovery or rename files since it's also got a file manager. It supports backing up partition sizes greater than 2GB which CWM doesn't. You can compress backups to save space. You can queue multiple zips to flash in sequence. If you use Tasker you can make automated, scheduled nandroids. I find it easier to navigate, like it was actually a recovery made to be touch and not just a recovery that had touch added. Swiping to flash gives me confidence I'm not gonna do anything stupid accidentily. Also, while in recovery pressing the power button will lock it so you have to swipe to unlock for those times when you're in recovery but need to put your phone in your pocket. Probably other things I'm missing.
Click to expand...
Click to collapse
Thank you that was very informative, another post I will be back to thank.
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.