Help turning off long press on keyboard - Samsung Captivate Glide

Ok so a run down of the problem
My Mother has recently gotten the glide as she has a mobility disorder that makes using a touch screen keyboard very difficult.
The trouble is that with the glides hardware keyboard if you long press the keys, e.g. The A key, it comes up with ASCII characters aka accents.
So what I am looking for is a way to turn off long press on the hardware keyboard or at the very least set it to a 5 second delay so as to not conflict with my my Moms typing.
I have changed the tap and hold delay in the accessibility option but this has had little to no effect.
I would rather not root or load custom ROM if it all possible
Thanks in advance of any help.

If you are using ICS+ (4.04+) Try settings>accessibility>touch and hold delay>(select your prefrence)
I don't remember if its on stock but let me know if it is as im using cm 10.2!
Edit: sorry realized that your on stock :/ this overrides everything in cm 10.2 (jb 4.3) if you change your mind about flashing let me know (you don't loose any data while flashing)

stormdude124 said:
If you are using ICS+ (4.04+) Try settings>accessibility>touch and hold delay>(select your prefrence)
I don't remember if its on stock but let me know if it is as im using cm 10.2!
Edit: sorry realized that your on stock :/ this overrides everything in cm 10.2 (jb 4.3) if you change your mind about flashing let me know (you don't loose any data while flashing)
Click to expand...
Click to collapse
I actually have already tried changing the accessibility setting to increase the delay but i think this only applies to the touch screen not the physical keyboard.
I am not against flashing a custom ROM just would like to avoid it if at all possible.

Related

[ROM] Nytefire-MIUI-Gingerbread-1.4.29

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

Disable Volume Buttons Wake-Up?

Hey guys. I haven't been able to find any information regarding modifying the functionality of the hard buttons on the GNex, all my searches just turn up mods to the soft buttons. On my phone, the two volume buttons on the left wake up the screen. I would like to disable this, since the buttons are fairly well placed to cause lots of accidental and in-pocket presses. Its well documented that the screen is the single most battery-intensive hardware component on this device, plus I generally like to keep my lockscreen disabled.
I know similar mods exist for other devices, since I had one for my old phone (the DroidX), and I found one for the Galaxy S II
http://forum.xda-developers.com/showthread.php?t=1086526
I will be hunting for the files that control this, but figured I could potentially speed up my search with a point in the right direction. Will look into it once I get my SSH and rsync stuff up and running.
While writing this post I DID find this:
http://source.android.com/tech/input/key-layout-files.html
Looks like it may not be too tough to parse out what can and cannot be modified on the Gnex
What ROM are you on? I am sure you can just ask the rom dev to give you a zip file to disable it.. does it do this on stock? I haven't had stock in so long but I don't believe it does..
How To Disable Volume Wake
I'm having the same problem, I flashed "Rooted,De-odexed,Zip-aligned ROM With Stock Insecure Boot Image And New Radios & Bootloader" to get to 4.0.4 and now my phone wakes whenever I use the volume keys. Anyone know how to disable this? While I'm at it, anyway to disable wake when plugging/unplugging from charger too? Thanks!
Sorry for a noob comment..am I missing something here...when I lock the phone..it doesn't wake when I press volume buttons...I'm on stock rom
Sent from my Galaxy Nexus using Tapatalk
What ROM are you using? As far as I know, this is not how stock ICS runs. Never did when I was on it. Certain ROMS (codename android and AOKP for example) have this as an option in the settings. If you are on a custom ROM, check your settings.
Sent from my Galaxy Nexus using XDA App
Yeah no, doesn't do it on Stock, I'm on IMM30B...

Touchkeys on CM10

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.

HTC Desire JB by Vijendrah - Track Pad problem

Hi,
I do not have the access to post in that forum, so I want to just do a check here, does anyone have this similar problem.
ROM : http://forum.xda-developers.com/showthread.php?t=1945441
Problem: Trackpad no longer works in latest v3.0
V3.0 is all and good, the OS I have been waiting for my desire (for 3 years I dare say) However, the track pad is not working. Anyone have this similar problem or is there something I don't know about that I should be doing.
Thanks!
Hi anybody with the above mentioned rom care to chime in? The ROM is great FYI I have been using it for months. Been thinking about getting another HTC desire to flash it to this rom for my mom.
I don't usually use the track pad, but just tested and it seems ok
Sent from my HTC Desire using Tapatalk 2
frosty68 said:
I don't usually use the track pad, but just tested and it seems ok
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
ah ok thanks, no wonder nobody was complaining in the forum thread... now i'm at a lost what to do. you flashed version 3.0 right? i haven't had this issue until 3.0
whimsywhimsy said:
ah ok thanks, no wonder nobody was complaining in the forum thread... now i'm at a lost what to do. you flashed version 3.0 right? i haven't had this issue until 3.0
Click to expand...
Click to collapse
I just verified this and trackpad is working fine here. Am on v3.0 as well. Did you do a full wipe before flashing?
led notification not work in desire on miui 4.1
whimsywhimsy said:
Hi,
I do not have the access to post in that forum, so I want to just do a check here, does anyone have this similar problem.
ROM : http://forum.xda-developers.com/showthread.php?t=1945441
Problem: Trackpad no longer works in latest v3.0
V3.0 is all and good, the OS I have been waiting for my desire (for 3 years I dare say) However, the track pad is not working. Anyone have this similar problem or is there something I don't know about that I should be doing.
Thanks!
Click to expand...
Click to collapse
i have benn using this rom for about three weeks.i don't have this problem or u reflash the rom.
vijendrahs have new work for htc desire: http://forum.xda-developers.com/showthread.php?t=2070704
dvsk69 said:
I just verified this and trackpad is working fine here. Am on v3.0 as well. Did you do a full wipe before flashing?
Click to expand...
Click to collapse
Sorry was busy for a few days, forgot about this thread, yeah I always do full wipe, not sure what I did but unchecking custom actions and then reboot... suddenly the track pad works again. I tried to recreate the problem by checking the custom actions, couldn't reproduce it... maybe it's just my track pad being dirty after 3 years? dunno. Anyway it works again, thanks for taking time to notify me.
Also... the link to the new work... I think I cannot test alpha builds... I really need my phone. but I will donate again if I move to new version haha, his work is great!
p/s anyone kind enough to explain what is the main difference at least between this new work and existing one? I'm kind of a noob and the last time I tried to read a cyanogenmod nightly changelog I almost fainted. Incremental builds from VJ I can understand, the rest... are totally alien to me, even finding the CM changelog was a challenge!
Just FYI I decided to try out the install a2sd from terminal with the Y Y Y command, and then when I tried to revert it back to the Y N Y setting, all my settings/sms/data was gone. So caveat emptor... or maybe you guys already know this, I for one did not.
Anyway now it's my HOME button that has lost functionality, the trackpad is ok... bummer... I didn't know how much I used it until it was gone. Even the settings under System > Hardware keys > Enable Custom Actions did now show a Home Key button (just has a Home key (long press) option)
er... help? I have restarted a few times... doggone it. I want my home button back!
whimsywhimsy said:
Just FYI I decided to try out the install a2sd from terminal with the Y Y Y command, and then when I tried to revert it back to the Y N Y setting, all my settings/sms/data was gone. So caveat emptor... or maybe you guys already know this, I for one did not.
Anyway now it's my HOME button that has lost functionality, the trackpad is ok... bummer... I didn't know how much I used it until it was gone. Even the settings under System > Hardware keys > Enable Custom Actions did now show a Home Key button (just has a Home key (long press) option)
er... help? I have restarted a few times... doggone it. I want my home button back!
Click to expand...
Click to collapse
I reflashed the ROM everything works now, I guess I was lucky never hard this experience before. I guess next time I should have a nandroid back up.
For anyone that just want an idea of what's the difference VJ has posted it himself. Please find notes below ty.
For actual differences between 4.1.2 and 4.2.1 google yourself.
But the improvements from my CM10 v3.0 to CM10.1 v4.2.1 is that:
1. The games which was not able to play in either any of the Jelly Bean version is playing now and better than GB ROM's.
2. Notification lights works
3. FM Works
4. Much Smoother
5. Video play back is very good (No more flickering)
6. Improved HWA
and find out yourself....
What's not working yet?
Same as Evervolv 4.2.1 (We fixed Bluetooth, Notification lights before them)
for me trackpad works fine

Help with Recent Applications Issue?

With some roms, I have this issue where when I click the recent apps, theres an animation flicker/lag when there shouldn't be one. After a very, very brief moment, it disappears though.
I don't know what could be causing this in one version of the rom, the issue is not there and then in another version, it is present.
I thought this might have been something on my phone that was cleared properly so today I did a clean instal of the rom (after I went back to stock for a few minutes), but it is still there.
Does anyone have insight to how to get rid of this? I *think* that some people have it and others dont
I had this for the longest time, and I'm pretty sure I've tried every fix imaginable. The only thing that works for me is pressing home before pressing recents. If you always press recents from your home screen, and not from within an app, the animation bug never seems to occur.
Sent from my Mahjong Nexus
tritonesub said:
I had this for the longest time, and I'm pretty sure I've tried every fix imaginable. The only thing that works for me is pressing home before pressing recents. If you always press recents from your home screen, and not from within an app, the animation bug never seems to occur.
Sent from my Mahjong Nexus
Click to expand...
Click to collapse
Before, I was able to do a reboot and it would be fixed for a while but now it doesnt go away. And thank you, I'll try pressing home first!
I thought it was my rom so I did a clean flash 3x. It was so tedious
moomingstarz said:
Before, I was able to do a reboot and it would be fixed for a while but now it doesnt go away. And thank you, I'll try pressing home first!
I thought it was my rom so I did a clean flash 3x. It was so tedious
Click to expand...
Click to collapse
Are you on toroplus? It seems most people that get this are toroplus.
Sent from my Mahjong Nexus
tritonesub said:
Are you on toroplus? It seems most people that get this are toroplus.
Sent from my Mahjong Nexus
Click to expand...
Click to collapse
No, I'm on maguro.
Its weird because I used to be able to reboot and it'd get rid of the problem but now I cant.
I actually rooted my brothers phone yesterday and put on the same rom (but he has the nexus 4-mako) and the issue is there as well! I originally thought it was my phone only.
I was on liquid 2.1 stable (and the issue wasn't there) but on 2.1 official it is, and it is on 2.2 official as well.
When I was on xylon, there were versions where it wasnt there and then versions where it is there
I think it might be a feature that all of these roms added (perhaps from one source) but I'm not a developer so this is probably just gibberish!
The roms that I've tried and seen it on is Xylon, Xenon HD and AOKP. The only rom where I consistently never had this issue is CM (M2) but the CM series don't have enough customizations for my taste, unfortunately.
Which rom(s) do you have this issue with?
Carbon,Xylon and Paranoid are ROMs that I know that doesnt have any lag in recents
Godra said:
Carbon,Xylon and Paranoid are ROMs that I know that doesnt have any lag in recents
Click to expand...
Click to collapse
What version on Xylon? I switched roms because xylon (for me) was acting up and I had that issue on the last update I tried (which is 2.3).
I might give carbon or Paranoid a try though! Thanks for the recommendations!!
Also! Does paranoid have 4-row toggles? I have quite a bit of toggles so its much more convenient to have 4 per row then 3 per row!

Categories

Resources