Related
Nytefire MIUI Gingerbread 1.4.29
-------------------------------------------------------
Hello all, this is my first attempt at a ROM. I usually downloaded option's work and flashed it, but I didn't feel like waiting this time. :] If anyone wants to give it a shot, I've flashed it now on three separate myTouch 4Gs without any problems. Of course, if you run into any problems, brick your device, or otherwise cause some type of calamity in your mobile world - this is no fault of mine.
For a list of changes from the previous build, check the MIUI website.
This ROM contains the latest Desire Z port of MIUI as well as the Langage Pack.
I've also included Faux123's GB kernel 2.5.2-137 LV kernel. If anyone has trouble with the LV kernel, feel free to flash over the SV version immediately after ROM flash. I'm afraid I can't do much bug fixing if there is any to be done - as this is all taken care of by the MIUI team. I've simply ported over their latest build for everyone to enjoy. If there's anything I need to change for the Glacier, let me know. :]
Edit:
I suggest doing wipes as you had been doing previously with Option's MIUI builds.
Thanks,
Nytefire
[] [] [] Download Link [] [] [] []
http://www.megaupload.com/?d=2D8JWQVO [Fixed from previous version, I somehow had botched su.]
Been waiting for this to drop, thanks
wheeeeee more ROM chefs
Variety is the spice of life! Also my "666" thank you mark
Hm.
Uh oh, due to not testing I've botched (and just now noticed) SU in this ROM. I'll post a fix shortly, as soon as I get home to do the edits. Sorry about this everyone, I'll have it fixed as soon as possible for you all.
Thanks for that catch, just getting it installed. I'll wait for that.
Could you also, in the next update, change the phone model to MT4G?
Home now, made the necessary changes and in the process of uploading.
Wireless tether not working anymore
Sent from my T-Mobile myTouch 4G using XDA Premium App
Not sure if this is a miui problem or a port problem, the buttons at the bottom of the device, e.g. home menu back, do not light up. Also, long pressing the genius button does nothing.
kyuza said:
Not sure if this is a miui problem or a port problem, the buttons at the bottom of the device, e.g. home menu back, do not light up. Also, long pressing the genius button does nothing.
Click to expand...
Click to collapse
does your home button work, and does normal pressing your search button work?
i had this problem before on one of options builds. Just wipe and reflash and you should be set. May take a few tries and retries of wiping and flashing (took me two times) but it fixed the issue
WIFI does not start for me, and third party access for phone calls is not working, even though it is enabled in the Call settings, and Google Voice is set to Always Ask how i want to make a call. Instead of asking if i want to make a call with my Google Voice number, it uses the real cell phone number.
I've tried wipeing and reflashing 4 times. Each time, the translation pack never installed. The buttons still didn't light up, and the genius button did nothing. I flashed on top of a fresh install, and the translation worked. However, the buttons still don't light up, and the genius button doesn't do anything. Also, can't change the brightness in the drop down menu or in settings. The slider/auto brightness does nothing.
To answer VibrantOwnr, the home button does work as it should, just doesn't light up.
kyuza said:
I've tried wipeing and reflashing 4 times. Each time, the translation pack never installed. The buttons still didn't light up, and the genius button did nothing. I flashed on top of a fresh install, and the translation worked. However, the buttons still don't light up, and the genius button doesn't do anything. Also, can't change the brightness in the drop down menu or in settings. The slider/auto brightness does nothing.
To answer VibrantOwnr, the home button does work as it should, just doesn't light up.
Click to expand...
Click to collapse
Um the genius button remap to search is pretty easy you need to go to the system/ usr/ key layout edit the glacier
keys
key 102 HOME
key 139 MENU
key 158 BACK
key 231 CALL
key 211 FOCUS
key 212 CAMERA
key 217 SEARCH
key 183 SEARCH
key 107 ENDCALL WAKE_DROPPED
key 116 POWER WAKE_DROPPED
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
I'm on cm7 but it should be roughly the same
Sent from my HTC Glacier using XDA Premium App
DarkNytefire said:
I've flashed it now on three separate myTouch 4Gs without any problems. Of course, if you run into any problems, brick your device, or otherwise cause some type of calamity in your mobile world - this is no fault of mine.
Click to expand...
Click to collapse
Not for nothing, i'm not sure what kind of testing you did, but this port is incomplete. I understand that this is your frist attempt @ porting a rom, but maybe you should do a little more research before hand.. I'm not trying to be a d*ck here, but this shouldnt of been released to general public. anyone who flashes this rom is essentially flashing a rom for the vision with a modified build.prop.. I would say use this @ your own risk, but dont be surprised when things r broken...
The key lay out is vision you need to add the files from the glacier. I haven't flashed this rom yet but use options rom as a base for your Rom. Since it for the glacier. A lot of the system files are visions.
Sent from my HTC Glacier using XDA Premium App
Killbynature said:
The key lay out is vision you need to add the files from the glacier. I haven't flashed this rom yet but use options rom as a base for your Rom. Since it for the glacier. A lot of the system files are visions.
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
he is missing the correct files from and not limited to:
/system/usr/keychars
/system/usr/keylayout
/system/lib/hw
/system/etc/firmware
not to mention a total unorthodox way to create/flash a rom???
Hey, don't blame him, he's trying. I'm even thinking of creating a crazily modified version of Cyanogenmod 7. He may not be great, but a least he's making an effort.
But as said before... Warning: ROM may have minimal to serious problems.
This is a message to the op next time you decide to make a rom share with friends people that will appreciate your effort not xda this community is very self centered most of time its either there way or no way the devs are great just the public always has something to say
No one is blaming him for anything he made an incomplete port it not that big of a deal but since true s off. We can literally flash any rom. He didn't change any files in this Rom except for a few. All the files are a vision files almost. We don't mean for him to take it. As bad advice. If he would of had a vision radio we would have bricks going back and forth. Then every one would be blaming him.
Sent from my HTC Glacier using XDA Premium App
GazaIan said:
Hey, don't blame him, he's trying. I'm even thinking of creating a crazily modified version of Cyanogenmod 7. He may not be great, but a least he's making an effort.
But as said before... Warning: ROM may have minimal to serious problems.
Click to expand...
Click to collapse
Don't blame him? I don't even understand what that means? There is no blame only telling how it is.. The port is incomplete and i do believe that anyone that is thinking of flashing this ROM would like to know that information, i know i would... I even went a step further and specified folder locations for of the files he need to replace with the correct ones.. So I was helping him out by giving him a little advice since he didnt want to do the research first...
daprince047 said:
This is a message to the op next time you decide to make a rom share with friends people that will appreciate your effort not xda this community is very self centered most of time its either there way or no way the devs are great just the public always has something to say
Click to expand...
Click to collapse
first off punctuation is always nice :] Quite a leap by calling the entire XDA community "self-centered" and i do not believe it was my way or no way, I really think thats an over reaction. Hey i do have to agree with you, the public does always have something to say...
Killbynature said:
No one is blaming him for anything he made an incomplete port it not that big of a deal but since true s off. We can literally flash any rom. He didn't change any files in this Rom except for a few. All the files are a vision files almost. We don't mean for him to take it. As bad advice. If he would of had a vision radio we would have bricks going back and forth. Then every one would be blaming him.
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Thank you! I am glad that someone gets it the main reason the rom boots is thanks to our great friend Faux123
Freedom of speech needs to be revoked, same talk just happened at teampokerface just now, maybe I'm wrong everyone should argue and trash talk and then go out and kill each other this way we can have more English teacher's :-D
Sent from my HTC Glacier using XDA App
My girlfriend just bought a refurbished A100. It arrived with ICS 2 days before the OTA was due. At first I was like GREAT! but upon further investigation I found it had the camera and speaker bugs reported in earlier leaked versions. So I looked at the build number and sure enough its an old build (.002).
Now my dilemma is do I wait for the OTA in a couple of days or do I use the stock ICS (.014) downloaded in the Dev section.
Now my girlfriend has watched me live through the agony and ecstasy of flashing roms and kernels on my Galaxy Tab and Revolution and does not want me to root her Acer.
I have searched the A100 forums and it appears you can flash this w/out root through stock recovery. Please correct me if I am wrong.
I can't seem to find very clear cut directions but here is what I think I need to do someone please tell me if I understand correctly.
1.rename downloaded zip to update.zip
2. put on root of external sd card (anywhere in particular)
3. turn tab off
4. turn tab back on by holding power and volume down
5. let go of power button and continue to hold volume down
6. let go of volume down when Android w/ gears icon appears
7. let it do it's thing
8.profit!
I'm a noob to Acer but not Android in general. Please any advice would be appreciated as I REALLY don't want to F-Up my Girlfriends new baby.
I know you feel buddy, my girlfriend inherited my old HTC Desire, which she loves but, doesn't love it when I say "I have a new ROM for you!" She loves having ICS though so go figure!
Yeah you've got it all right, it might take a few times to get into the stock recovery, it drove me mad ha ha, no harm done though just a bit fiddly to get the button combo every time.
the .014 release is the ICS to flash as it has full touch support with games.
toyface said:
I know you feel buddy, my girlfriend inherited my old HTC Desire, which she loves but, doesn't love it when I say "I have a new ROM for you!" She loves having ICS though so go figure!
Yeah you've got it all right, it might take a few times to get into the stock recovery, it drove me mad ha ha, no harm done though just a bit fiddly to get the button combo every time.
the .014 release is the ICS to flash as it has full touch support with games.
Click to expand...
Click to collapse
Thank you for your quick reply toyface. Just another quick couple of questions.
Does the screen lock button need to be in any particular position when doing the stock recovery flash?
Is there any particular folder or place on the sdcard that I have to put the update.zip?
If I decide to wait on the OTA, will it go right over the old ICS build or will having the old ICS interfere with that?
Thanks again.
The stock rom in the development section is the same as the ota update, so your tab won't find a new update as it will already be installed. As for flashing, your steps are correct, but make sure you hold the volume button closest to the power button and you should be good. Hope this helps!
Sent from my PC36100 using XDA
Everything went smooth as silk. I have now have a happy girlfriend with a happy tablet, therefore I am a happy man. Thanks for the help!
******NOOB WARNING*****'
I've been searching for a few days and haven't come up with anything. I'm trying to remap my search key to have it launch my camera instead. I just rarely use it and very much miss my dedicate camera hard key. I've tried the button remapper on one of these threads to no avail there seems to be one dedicate to Galaxy S phones but when I launched that one it said I wasn't using a supported device ( I've got a Samsung Galaxy S2 SGH-T989), and when I downloaded the other button remapper it launched just fine but when I changed the command for the search key to camera it did nothing. Next I went into my root explorer and copied all .kl files with the 217 search key that I was lead to believe was the one I needed to edit and put them on my external sd and then preceded to modify the originals from "SEARCH" to "CAMERA." But that attempt failed as well. All that did was disable my search key all together. Not sure if I was on the right track here and just missed something or if that's just a completely idiotic attempt. Either way I've just Typically failed at my noobish attempt at Remapping my search key. If anyone can help this sad and disgraced noob please let me know.
Thanks!
P.S. My phone is rooted and I'm just running plain ole ICS 4.0.3 and I'm gonna post a screens of "about phone" section incase that helps at all. Sorry if I sound like an idiot but I'm very new to all this. Just rooted my first phone a few weeks ago. So if you could keep that in mind when you reply it would be much appreciated. Thanks again
jalight27 said:
******NOOB WARNING*****'
I've been searching for a few days and haven't come up with anything. I'm trying to remap my search key to have it launch my camera instead. I just rarely use it and very much miss my dedicate camera hard key. I've tried the button remapper on one of these threads to no avail there seems to be one dedicate to Galaxy S phones but when I launched that one it said I wasn't using a supported device ( I've got a Samsung Galaxy S2 SGH-T989), and when I downloaded the other button remapper it launched just fine but when I changed the command for the search key to camera it did nothing. Next I went into my root explorer and copied all .kl files with the 217 search key that I was lead to believe was the one I needed to edit and put them on my external sd and then preceded to modify the originals from "SEARCH" to "CAMERA." But that attempt failed as well. All that did was disable my search key all together. Not sure if I was on the right track here and just missed something or if that's just a completely idiotic attempt. Either way I've just Typically failed at my noobish attempt at Remapping my search key. If anyone can help this sad and disgraced noob please let me know.
Thanks!
P.S. My phone is rooted and I'm just running plain ole ICS 4.0.3 and I'm gonna post a screens of "about phone" section incase that helps at all. Sorry if I sound like an idiot but I'm very new to all this. Just rooted my first phone a few weeks ago. So if you could keep that in mind when you reply it would be much appreciated. Thanks again
Click to expand...
Click to collapse
If you have clockworkmod recovery, or any custom recovery, flash attached file via recovery.
Did I do something wrong here?
elesbb said:
If you have clockworkmod recovery, or any custom recovery, flash attached file via recovery.
Click to expand...
Click to collapse
Ok, well let me start out by saying I'm a moron. Below I posted and the whole recovery thing went way over my head. Lets just say the scapegoat there was not enough sleep and being way over worked. But anyway after writing that I realized how stupid I was. So I immediately pulled my head but of my but and went into recovery mode and installed your zip from there, reported, and still nothing for my search key. Is it because I screwed the pooh on my first attempt? Read the dribble I posted first and please lemme know:
First off, thank you very much for taking the time to reply and do all this for me. After reading your post I went out and got clockwork Rom manager which also lead me to download clockwork recovery. I then preceded to click on the zip file you provided and when it completed downloading I opened it. I took a snapshot of the screen that popped up. I clicked yes leaving the box checked that the program had checked for me (just as it is in the screen shot). Afterthat the phone preceded to do it's thing and a few minutes later the phone rebooted and now if I hit the search key it vibrates but doesn't actually do anything. Did I do something wrong along the way? Again, I really do appreciate you taking the time out for me and I'll be awaiting your response. Thanks!"
Stupid, I know. But I'll assume that that's probably the problem. If I can find some time tomorrow I'll try revolving the copy of the Rom I made before I killed my search key and then do it properly, and hopefully that'll be that and I'll FINALLY have my search key camera. Thanks again!
jalight27 said:
Ok, well let me start out by saying I'm a moron. Below I posted and the whole recovery thing went way over my head. Lets just say the scapegoat there was not enough sleep and being way over worked. But anyway after writing that I realized how stupid I was. So I immediately pulled my head but of my but and went into recovery mode and installed your zip from there, reported, and still nothing for my search key. Is it because I screwed the pooh on my first attempt? Read the dribble I posted first and please lemme know:
First off, thank you very much for taking the time to reply and do all this for me. After reading your post I went out and got clockwork Rom manager which also lead me to download clockwork recovery. I then preceded to click on the zip file you provided and when it completed downloading I opened it. I took a snapshot of the screen that popped up. I clicked yes leaving the box checked that the program had checked for me (just as it is in the screen shot). Afterthat the phone preceded to do it's thing and a few minutes later the phone rebooted and now if I hit the search key it vibrates but doesn't actually do anything. Did I do something wrong along the way? Again, I really do appreciate you taking the time out for me and I'll be awaiting your response. Thanks!"
Stupid, I know. But I'll assume that that's probably the problem. If I can find some time tomorrow I'll try revolving the copy of the Rom I made before I killed my search key and then do it properly, and hopefully that'll be that and I'll FINALLY have my search key camera. Thanks again!
Click to expand...
Click to collapse
That happened to me as well. I then opened up my camera and pressed the search key while my camera was open. It took a picture. And booted, after that, pressing the search key then launched the camera. So try that.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
---------- Post added at 02:29 PM ---------- Previous post was at 02:22 PM ----------
elesbb said:
That happened to me as well. I then opened up my camera and pressed the search key while my camera was open. It took a picture. And booted, after that, pressing the search key then launched the camera. So try that.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Alright what I just did now, launch whatever camera app you use. Press the back button. Press and hold the search button. Should work.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Beautiful
elesbb said:
That happened to me as well. I then opened up my camera and pressed the search key while my camera was open. It took a picture. And booted, after that, pressing the search key then launched the camera. So try that.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
---------- Post added at 02:29 PM ---------- Previous post was at 02:22 PM ----------
Alright what I just did now, launch whatever camera app you use. Press the back button. Press and hold the search button. Should work.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Beautiful. Just did what you said and works perfectly. Might have even been working before I just didn't hold the button when I was doing it yesterday. Thank you so much. Was kinda sceptical when I posted that I would just get a bunch of condescending remarks, but very happy to see this site isn't like some others I've been too. Anyway though, thanks a million. This is gonna be awesome for my twins. I keep missing good photos cuz it takes that extra few seconds to find my camera. Now I'll be able to get to it in a flash. Thanks again. You're awesome.
jalight27 said:
Beautiful. Just did what you said and works perfectly. Might have even been working before I just didn't hold the button when I was doing it yesterday. Thank you so much. Was kinda sceptical when I posted that I would just get a bunch of condescending remarks, but very happy to see this site isn't like some others I've been too. Anyway though, thanks a million. This is gonna be awesome for my twins. I keep missing good photos cuz it takes that extra few seconds to find my camera. Now I'll be able to get to it in a flash. Thanks again. You're awesome.
Click to expand...
Click to collapse
Not a problem! I have my camera set to a short cut on the lockscreen and a gesture when I'm in my phone lol. But that's a good idea to just assign it to another button
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
Not a problem! I have my camera set to a short cut on the lockscreen and a gesture when I'm in my phone lol. But that's a good idea to just assign it to another button
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Hello again. I just download my first new ROM, Jedi mind trick, and I obviously lost my search button camera. Since I'm not running the stock ROM will the zip file you sent me previously still work to replace my search key with launching the camera? Thanks in advance!
The keymap files are at /system/usr/keylayout/
Different ROMs probably have different files, but I guess you can find the file(s) you need to change from "SEARCH" to "CAMERA"
Keep in mind, do a backup before change anything.
angellsl said:
The keymap files are at /system/usr/keylayout/
Different ROMs probably have different files, but I guess you can find the file(s) you need to change from "SEARCH" to "CAMERA"
Keep in mind, do a backup before change anything.
Click to expand...
Click to collapse
Right, always sure to do that. I made a backup of all the files I edited last time. Edited all the keylayout files last time though and didn't do anything. Maybe I missed one though. I'll give it a try and edit it when I'm do though. Thanks for the info!
---EDIT---Totally worked. Actually I think I had it set the first time I did this on my stock ICS Cruz when I pressed the search key once in camera it took a pic but the problem I was having all along was I just wasn't holding it down. Typical noob right? Oh well, learned my lesson. Try absolutely EVERYTHING before posting and sounding like a moron, lol. Anhway, elessb, would it be possible for you to instruct me on how to get to my camera on my lock screen like you have it. That would just be beyond amazing.
jalight27 said:
Right, always sure to do that. I made a backup of all the files I edited last time. Edited all the keylayout files last time though and didn't do anything. Maybe I missed one though. I'll give it a try and edit it when I'm do though. Thanks for the info!
---EDIT---Totally worked. Actually I think I had it set the first time I did this on my stock ICS Cruz when I pressed the search key once in camera it took a pic but the problem I was having all along was I just wasn't holding it down. Typical noob right? Oh well, learned my lesson. Try absolutely EVERYTHING before posting and sounding like a moron, lol. Anhway, elessb, would it be possible for you to instruct me on how to get to my camera on my lock screen like you have it. That would just be beyond amazing.
Click to expand...
Click to collapse
Which ROM are you on? The cm ROMs have custom shortcuts so that's how I got it there.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
Which ROM are you on? The cm ROMs have custom shortcuts so that's how I got it there.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I've got Jedi Mind Trick running right now. Its blazing fast but its kinda buggy. Was in love with it at first, but the longer I have it, the more it's annoying me. Programs seem to freeze up quite often and stall out the phone for 30 seconds or so, and it seems to be doing it at least 3/4 times a day. I've heard good things about the cm ROMs. I know its kinda off topic, well maybe not all that much since I'm interested in the camera shortcut, but is there a specific ROM you'd reccomend concerning the camera shortcut, and of course with overall functionality in mind as well.
Thanks!
jalight27 said:
I've got Jedi Mind Trick running right now. Its blazing fast but its kinda buggy. Was in love with it at first, but the longer I have it, the more it's annoying me. Programs seem to freeze up quite often and stall out the phone for 30 seconds or so, and it seems to be doing it at least 3/4 times a day. I've heard good things about the cm ROMs. I know its kinda off topic, well maybe not all that much since I'm interested in the camera shortcut, but is there a specific ROM you'd reccomend concerning the camera shortcut, and of course with overall functionality in mind as well.
Thanks!
Click to expand...
Click to collapse
The latest jelly bean nightly from either Erick or binaryBishop is amazing. It's better than my official nightly from cyanoGen mod on my s3
Sent from my SGH-T999 using Tapatalk 2
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.
RENOVATE, why don't you stick with the "If it ain't broken, don't fix it!" principle?
I'm referring to the RENOVATE team's decision to do away the input method notification from the notification bar. Yes, monolinguals may not change their keyboard for their whole life, but multi-linguals like me speak and write 4 languages and change keyboard many times a day! This newly introduced "feature" (read: bug) is so irritating that I have to flash another ROM. The input method notification is there for a reason! If it ain't broken, don't ever fix it! The RENOVATE team can feel free to disable it by default if they like, but not give people options to enable it?
Quote:
Originally Posted by thedan55 View Post
I've just noticed that there's no input selection when entering text in the notification bar, I'm running with sense but I'm using nova. Was that done deliberately?
Also unofficial 1 used to kill with the back button and final doesn't.
Just mentioning it, in case it's been over looked
Sent from my HTC One X using Tapatalk 2
Yep it was! Imo it's pointless, we don't change keyboards every 5 minutes so why have it there!
Kill apps is working fine here mate, have you flashed and mods containing an android.policy.jar?
Sent from my HTC One X using xda premium
For now, try another rom
For this problem, you'd better write to the leader of the team, because you can't write in Renovate's Thread..
Re: RENOVATE, why don't you stick with the "If it ain't broken, don't fix it!" princi
Why don't you just download a free app called 'input method' from the play store??
Arkangel786 said:
Why don't you just download a free app called 'input method' from the play store??
Click to expand...
Click to collapse
Thank you mate. The app works. For the time being I think it's the best solution.
But still, AOSP has a built-in feature that works just fine and then someone decided that the users can't use it because they don't use it, and now I have to download an app to do what I used to be able to do. It is just not right. I'm very disappointed at this kind of attitude.
Re: RENOVATE, why don't you stick with the "If it ain't broken, don't fix it!" princi
Top be honest mate you can't please all the people all the time and you might not like it but others will do unless you're going to build your own Rom then your bang out of luck.
Sent from a Blunt smoker
Well, considering we do this for free... and most of us use SwiftKey anyways it's our choice in the end whether we want to include that function or not.
terry8471 said:
I'm referring to the RENOVATE team's decision to do away the input method notification from the notification bar. Yes, monolinguals may not change their keyboard for their whole life, but multi-linguals like me speak and write 4 languages and change keyboard many times a day! This newly introduced "feature" (read: bug) is so irritating that I have to flash another ROM. The input method notification is there for a reason! If it ain't broken, don't ever fix it! The RENOVATE team can feel free to disable it by default if they like, but not give people options to enable it?
Quote:
Originally Posted by thedan55 View Post
I've just noticed that there's no input selection when entering text in the notification bar, I'm running with sense but I'm using nova. Was that done deliberately?
Also unofficial 1 used to kill with the back button and final doesn't.
Just mentioning it, in case it's been over looked
Sent from my HTC One X using Tapatalk 2
Yep it was! Imo it's pointless, we don't change keyboards every 5 minutes so why have it there!
Kill apps is working fine here mate, have you flashed and mods containing an android.policy.jar?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Well i didnt know we had so many multi language speaking users! For most people, they set up a keyboard, then they won't ever change it, therefore the notification coming up every time you write something gets really annoying. If it's such a big deal i'll add the keyboard switcher back in.
Wouldnt it of been a lot easier to just ask nicely in thread and not create a thread about it?
and long press to kill apps is 100% working how it should be.
mwilky said:
Wouldnt it of been a lot easier to just ask nicely in thread and not create a thread about it?
Click to expand...
Click to collapse
He can't post in Development threads since he's a new user mate.
IceColdJelly (or AOKP, not sure) has the option to disable the keyboard popping up in the notification bar - i disabled it my self. It should atleast be a user choice. On the other hand, if it can be revived by a simple app, the devs may remove it if they wish, its their project, and its done free of charge in spare time