yashsingh1/xdaforums huggingface dataset:
[Samsung Captivate Glide] Lisali:
Hi all,

Is there a way to activate haptic feedback/vibration for home/menu/search keys?

Thanks!
[Samsung Captivate Glide] scottbot95:
I have worked out a patch to get the keyboard backlights working again. It actually integrates with the android controling of the backlights on the action keys. As soon as I get home, I will push the fix to The-Covenant's repo. I hope dman will approve it shortly after that.

Edit:

FYI, I get home from school around 3:30. So you'll just have to wait till then :P

Sent form my SGH-i927 running dman's cm10.1
[Samsung Captivate Glide] Lisali:
Hi all,

I have been testing the ROM and although it's fab to use JB, finally, I am having some issues:

- No haptic feedback on soft menu keys

- No option to have backlight always ON for soft menu keys (they go off TOO quickly)

- No keyboard backlight

- No way to turn off CRT animation for screen off

- Screen on slow - takes 2-3 seconds, whereas in ParanoidAndroid it's almost instant

- Notification issues - Whatsapp, Gmail and others will sometimes NOT push notifications until you go an manually start the app

- Keyboar issues - apart from the knows issue with built-in keyboard, even Swiftkey and Kii are having problems. Kii is crashing and Swiftkey Flow is having issues with the flow - no trail is visible

Is there any chance these will be fixed soon? Or is it too early for JB?

Many thanks!:good:
[Samsung Captivate Glide] dman3285:
Its doubtful.. as those are not issues. They're preferences.
[Samsung Captivate Glide] scottbot95:
I only see those last two as even close to issues. Like I just posted, I have worked a patch that I will test and publish when I get home.

I have noticed some weirdness with notifications, but that seems like a problem with JB itself and I don't think any of us want to try to fix that.

You have a physical keyboard, you know. I find it to me much quicker than any soft keyboard.

Sent form my SGH-i927 running dman's cm10.1
[Samsung Captivate Glide] szulco:
I've noticed that just right after installation internal memory is mounted under /emmc not /sdcard causing gallery, camera not to work properly.

Running manual script does the trick.

Is it rom or kernel problem?
[Samsung Captivate Glide] scottbot95:
That would probably just be a problem with the fstab. So a rom issue.

Sent form my SGH-i927 running dman's cm10.1
[Samsung Captivate Glide] szulco:
Oh, ofc.. Thanks!
[Samsung Captivate Glide] scottbot95:
Wait... nvm guys. My "patch" caused other weirdnesses.
[Samsung Captivate Glide] thegreatergood:
could you get me this "patch" ... maybe it can be made to work properly
[Samsung Captivate Glide] mrk2815:
d man will you be updating the CM 10.1with updated fixes. Just wondering will this be beta 3 or something like that. hoping that all roms will be closer to RC phases as CM 10 and the vanilla 4.1.2 rom from what i can tell are close to that . the only two roms that need more emphasis are the CM 10.1 and the AOKP 4.2.1 roms. Hoping that these two roms aalso get the TLC that the other version 4.1.2 roms have been getting. thanks for all of the great work that D man and the entire team does as to getting 100% working roms.
[Samsung Captivate Glide] scottbot95:
Basically all I did was edit device/samsung/i927/liblights/lights.c so that when you called the function to turn on the backlights for the action keys, it also called the function to turn on the keyboard backlights. But it just did weird things on my phone....

---------- Post added at 02:40 AM ---------- Previous post was at 02:33 AM ----------

Also, if anyone knows where the function is called to turn on the action key backlights, that would be fantastic. Not the function itself, I know where that is (I think), I need to know where it's getting called.

Sent form my SGH-i927 running dman's cm10.1
[Samsung Captivate Glide] Roeni:
so you have script which fixes this? could you provide it?
[Samsung Captivate Glide] rvalentin913:
If I remember from looking through my moms phone since i updated it to cm10.1 dman did this with build.prop setting so you can change it within there and it should work as before

---------- Post added at 10:33 PM ---------- Previous post was at 09:53 PM ----------

Add the following to build.prop for backlight home keys.

# Force button lights on when screen is on

ro.mot.buttonlight.timeout=0

You could try this for CRT animation off but not sure if it will work as my mom doesn't like me messing with her phone at night ;)

#Toggle CRT Anim 0=off 1=on

debug.sf.hw=0
[Samsung Captivate Glide] roothorick:
Won't this disable hardware assistance for a bunch of stuff and possibly cause performance issues?
[Samsung Captivate Glide] dman3285:
Yes it will.. CRT is part of the os. If it ain't broke don't fix it.
[Samsung Captivate Glide] rvalentin913:
Didn't know that was just giving suggestions to that guy.

I personally like the CRT animation.
[Samsung Captivate Glide] dman3285:
New build up, enjoy, all i have time for atm.
[Samsung Captivate Glide] lorddavid:
thanks :D

ammm what are the changes? :P noob question i know :)
[Samsung Captivate Glide] dman3285:
Just upstream commits.. I have a lot of real life issues going on. Don't have time to implement the few fixes there are. Thegreatergood is doing good work. As soon as I can I'll be back on it wide open.
[Samsung Captivate Glide] lorddavid:
ok, :) thanks. Take your time. And thanks for the rom, you are great :D
[Samsung Captivate Glide] szulco:
Big thanks Dman!
[Samsung Captivate Glide] bobbinthreadbare:
Still dirty flashing. Update went well here.:highfive:
[Samsung Captivate Glide] dman3285:
Just FYI. If there is an issue your experiencing, post it here and or general section. Do not pm me! I have over 2000 pms I can't get to. Only covenant team members or devs pm me. Thanks.
[Samsung Captivate Glide] terinfire:
I finally made the jump after thegreatergood confirmed a few things for me.

WOW! Coming from CM10 -> CM10.1 is just amazing. If anyone else hasn't done it yet, do it now. Great work as usual, d!
[Samsung Captivate Glide] scottbot95:
Sweet Baby-Jesus, I've got the keyboard backlights working!!!! It was as simple as a permissions problem. Well, and a little tweaking of lights.c... I have forked The-Covenant's device tree and have uploaded my revisions here. It's not that pretty, but it works. I'm gonna work on making android call it by itself instead of this weirdness.
[Samsung Captivate Glide] phatryan69:
just gonna say this... DAMN! Rom is amazing... i had to step away from using my android for a few and just installed the latest update and im blown away! Amazing work Dman!
[Samsung Captivate Glide] ninthsense:
Goodjob on this.... though it seems weird but its built in code. If I understand it correctly you are passing the values 0 & 1 to the keyboard_file. What I don't understand is that the code is under the light_button function rather than the light_keyboard func.
[Samsung Captivate Glide] scottbot95:
The reason I put it there is because the os doesn't seem to be calling the light_keyboard function, so I just linked them together. I'm currently working on trying to get the os to call the light_keyboard func directly.

Sent form my SGH-i927 running dman's cm10.1
[Samsung Captivate Glide] thegreatergood:
Exellent work :D ... i had already found the permissions issue and tryed tweaking the lights but couldnt get it to work .. :)
[Samsung Captivate Glide] scottbot95:
I noticed that init.rc was changing the permissions of the buttons, and they worked so I added a light to change the permissions on the keyboard too.

Sent form my SGH-i927 running dman's cm10.1
[Samsung Captivate Glide] thegreatergood:
exactly ... I went through EVERYTHING to make sure i hadnt missed anything... lol
[Samsung Captivate Glide] scottbot95:
Nice. Do you have any idea where the light_button function is getting called by the system? If i could figure that out, I could make the code more elegant.
[Samsung Captivate Glide] joshua_tam:
Hi all, I found something that maybe useful:

1. The sym button on keyboard is not yet functioning.

2. The toggle button of notification drawer is shifted right, I guess it was related to open keyboard issue.

3. I can still get calls even the signal icon is fully gray, is it normal?

Again, really thanks for you all hard work to make JB on glide :)
[Samsung Captivate Glide] AzraelsKiss:
#1... Known issue that's been talked about forever on multiple threads and many, many people have been working on forever.

#2... Another issue that is known.

#3... The signal icon turns blue when the phone is communicating with the google servers. It is not an indication on if you can make or receive calls. I believe the icon for no signal is a circle with a diagonal line, but I haven't been out of coverage area for a while, so I can't rightly remember.
[Samsung Captivate Glide] thegreatergood:
Keyboard lights fix confirmed working ... will apply changes to github tomorrow cause the code is decent and adds functionallity that 4.2 for all we know will never give with current code...
[Samsung Captivate Glide] joshua_tam:
I see, sorry for my dulplicate response, just want to contribute something to the glide community.
[Samsung Captivate Glide] scottbot95:
Is there any chance at all that I could be put on the list of contributors? Or at least set up gerrit for The-Covenant?

Sent form my SGH-i927 running dman's cm10.1
[Samsung Captivate Glide] thegreatergood:
ask dman
[Samsung Captivate Glide] scottbot95:
Dman, same question?

Sent form my SGH-i927 running dman's cm10.1
[Samsung Captivate Glide] soadzoor:
Camera says: "insert an sd card before using camera" so I can't use it. Gallery doesn't see my pictures either. Also the external sd's name has changed to storage0, or something, what did I do wrong, what should I do now?
[Samsung Captivate Glide] dman3285:
You did something seriously wrong. Not had those issues.
[Samsung Captivate Glide] thegreatergood:
he's using litekernel... storage is set up differently...
[Samsung Captivate Glide] szulco:
Something similar happened to me after installing beta2 - internal memory was mounted under /emmc not /sdcard causing camera and gallery not to work at all. So I made a script in rom toolbox to remount internal storage under /sdcard and now under gallery each folder is displayed twice but it works :) Not sure if it's fixed in beta3 since before update from beta2 I wiped cache and dalvik cache only.

Anyway, CM10.1 is sick! I'll never go back to older releases but please, fix keyboard lights :)

Keep it good work!
[Samsung Captivate Glide] soadzoor:
That's right, I'm using litekernel, so what should I do? or everyone who uses it has no working camera? :\
[Samsung Captivate Glide] thegreatergood:
just downloaded cm10.1 ... ill make it compatible
[Samsung Captivate Glide] dman3285:
Besides Bluetooth, its as fixed as I'm going to do.. remember, devs build ROMs as they like them and then share.. this us how I run it. And its flawless. Now other members make a patch for u, that's cool. But its good besides bt
[Samsung Captivate Glide] szulco:
God bless You Dman! :good:
[Samsung Captivate Glide] elban:
Sorry to tell you but I have the same issues. Internal and external storage are swapped, leading to those problems. I can live with it though.

May it depend on something related to the minisd, how it is formatted or partitioned? This would explain why it doesn't work for some.
[Samsung Captivate Glide] thegreatergood:
try the kernel below and let me know ...

also try the keyboard light patch here
[Samsung Captivate Glide] bobbinthreadbare:
My storages are swapped as well. I asked about it a few pages back but didn't see an answer. I figured it was just a mistake that was overlooked. Kind of a pain since I have to redownload the SwiftKey language pack upon every boot but it isn't a big deal considering how well everything else runs.
[Samsung Captivate Glide] vistmarckh:
will download this and test later :fingers-crossed:
[Samsung Captivate Glide] QuickSilverAWD:
Are the USB Drivers working? Has anyone tried GVoice or GTalk with it?
[Samsung Captivate Glide] soadzoor:
Godlike. the kernel works flawlessly, thanks! the lights works too but in the way I told u about (its on when keyboard is closed as well) therefore I wont use it til this is fixed, it would drain my battery in an hour or so.. but its a big progress, you're amazing :)
[Samsung Captivate Glide] dman3285:
The keyboard lights do not need to be pushed to my device tree. As I don't use it ever. It needs to be a separate patch. And storage is not swapped at all. That is CM new mounting directories.. it works fine. All keyboard fixes need to be patches supplied here. I do not want it screwing my tree up for something I have never used. Thanks
[Samsung Captivate Glide] scottbot95:
I'll get to working on a fix for that lights on when closed thing.

Sent form my SGH-i927 running dman's cm10.1
[Samsung Captivate Glide] scottbot95:
I think I've found the file that controls, or at least is an intermidiate step in controlling, the turning on of the backlights for the menu keys and keyboard. InputReader.cpp if anyone's interested. Small problem, it's 6800+ lines. Hopefully I'll be able to fix that lights on when closed thing. And the fact that the softkeys don't have haptic feedback. I'm super ultra busy right now, though. I'll get my patch out asap

Sent form my SGH-i927 running dman's cm10.1
[Samsung Captivate Glide] vistmarckh:
confirmed working:good:
[Samsung Captivate Glide] terinfire:
Has anyone had any weird issues where the phone locks up from deep sleep? Thankfully my girlfriend is a bit more attentive to time and checked her phone -- but my alarm failed to go off this morning because my phone froze sometime last night. First time it has EVER happened -- and we'll just make sure we set alarms on both of our phones from now on. I had to do a battery pull to get it to reboot.

And yes, I'm aware of the fact that CM voids my warranty and are not to be held responsible for broken alarms, missing work, etc. :o
[Samsung Captivate Glide] taiber2000:
i disgree with you dman, the lack of working lights in the keyboad is a bug, its a minor one but still makes the ROM flawed.

ofcurse you can say that you won't adress that as you made a goal for what you want the rom to do and what bugs you want to adress and the ones you don't want to adress.

i think that you still have on more bug that is important to fix then the keyboard light and its the use of voice ouside of making calls.

you can record sound for videos/sound recorder/skype and other apps that need to use the mic ouside the dailer and yes this is a major bug.

maybe its a bug connected to the bluetooth bug.

dont think i'm saing here that you must fix every bug but you need as a dev to acconalage that there is bugs that you wont want to adress.
[Samsung Captivate Glide] mrk2815:
so d man will the blue tooth issue be fixed . if you are saying that you have fixed most issues that you think are important for the rom , so can you list issues that you would not resolve prior to an RC candidate. Jus wondering if the rom will be 100% working or you will just wait until google release code for the next release and you will then begin work on CM 11 for the next release of android. just wondering as i cant figure this development thing out.
[Samsung Captivate Glide] scottbot95:
Dude, dman is suoer busy. And he did acknowledge that it doesn't work, but he said it's not important, which is true. He has many things to work on in this ROM alone, and he's developing many ROMs and has a job and real-life to deal with. There are other people out there, such as myself, working on the minor bugs because we enjoy those small things.

We don't need to start a flame war, but know that we want only constructive comments here. Anything else is not helpful and not welcome.

Sent form my SGH-i927 running dman's cm10.1
[Samsung Captivate Glide] Evil Alex:
What was already said previously, and also consider the following:

Disagree with it all you like, but the devs here build and supply the ROMs 'as is' and for free, and without any guarantees. They put in a lot of hours without asking or expecting any payment. They do it for the love of the device, or the developing in itself.

If you want them to address every bug, then you'd better start paying them a full salary.

Just be grateful the stuff is here, and that it's high quality, too! Besides, plenty of others around who will gladly patch things like this.
[Samsung Captivate Glide] pm2gonzales:
I really don't think he meant any offense. EVERYONE here knows dmans contributions. I think he was just saying it's one thing to say it isn't a big and it doesnt need to work. It is a bug, but not one that requires immediate attention or is phone-breaking or that even stops it from being a DD. Dman said it's not a bug for him, so it's not an immediate concern. I think everyone is blowing things out of proportion.

Regardless, there are patches in these forums that address these issues greatly or are being worked on.
[Samsung Captivate Glide] gtmaster303:
I will attempt to make a summary post of all the patches once I read through the whole thread so that everything is easier to find.

Unless dman beats me to it and adds them to the OP

(is there a lot of them? reading through the thread now...)
[Samsung Captivate Glide] thegreatergood:
http://xdaforums.com/showthread.php?t=2067954
[Samsung Captivate Glide] gtmaster303:
lol never mind
[Samsung Captivate Glide] mrk2815:
i was listening to a podcast on android yesterday. blue tooth issues are bug in 4.2.1 and google will be releasing 4.2.2 to address the blue tooth issue as well as other bugs. So if d man and the rest of the developers can be on top of this and when google releases that source code then it can be implemented in all the roms that are being worked on for samsung SGH i927 captivate glide. That way when google fixes it will make things more easier on developers like D mann and the rest of the team. Keep up the great work so far. thanks for all the roms that have been developed so far .
[Samsung Captivate Glide] taiber2000:
it's seems you can't create a dialog here cos if you critsize a dev than people jump on you.

i didnt say he must do what we, as users, want. i said that in my orginal post.

what i'm saing is the if you go by the road of apple "it's not a bug it's a feture" then whats the diffrent between our community and the IOS ones?

the other thing i don't understand is way can't fixes creted by others, like the greatergood, be intgrate to the main tree.

is the main tree is a general one that suppose to be fordman's other devices that he works on?

if this a sepcific tree for our device so it need to incoprate all the fxies that are made to it unless it brakes other stuff in the device.

as we are open source communety i'm buffled by the idea that a source is so sacfred that only one man can change it.

yea, this is dmans build and he is the head of the dev for this current build, but still we should come togther to imporve on others work, no?
[Samsung Captivate Glide] AzraelsKiss:
As dman said, devs make their ROMs to conform to what they see is important. He doesn't see the keyboard lights as being important, so he's not incorporating the workaround into his source. That is his decision. If you want to use the workaround, a patch has been made available to use. Also, if another dev decides that the keyboard lights are a critical feature and the workaround should be added to a full ROM project, there is no reason that the dev could not build their own ROM using the existing sources, as long as they credit the proper sources. To imply that devs have a responsibility to squash every bug that we perceive is selfish. If you don't like a dev's final project, your only recourse is to find one that you do like, and it is up to the dev on whether this is enough motivation to desire to appease the users' requests. Besides... If someone figures out an actual fix to the keyboard lights that don't compromise existing functionality, dman could still decide to add it to the source... As of right now, that has not been accomplished.
[Samsung Captivate Glide] scottbot95:
I've almost figured that out, just fyi. I've been too busy to fully test and incorporate it, though.

Sent form my SGH-i927 running dman's cm10.1
[Samsung Captivate Glide] terinfire:
Has anyone found any workarounds for the voice search, or do we just assume that is dead in the water?
[Samsung Captivate Glide] yivkhar:
Am I the only one having problems with MMS not working?
[Samsung Captivate Glide] terinfire:
Mine works flawlessly.

Are you on another carrier besides AT&T? If so, you may need to update your APN's to get it working correctly. I'm on StraightTalk and I know that MMS will NOT work if I don't have my APN selected/setup. Also, are you using the stock Messaging app?
[Samsung Captivate Glide] yivkhar:
I'm also on StraightTalk and I updated my APN and triple checked it. I'm using Go SMS
[Samsung Captivate Glide] terinfire:
So, if your MMS stops working on Straight Talk (it does sometimes), I think it's because the settings get all messed up.

What I do, is temporarily stop/cancel all MMS' being sent. You can do this by turning on Airplane mode. Go to your APN's and set it to something else. Then reboot. Then, open APN's again and open the Straight Talk one. Confirm that the settings are all correct in the APN -- I've noticed a few of them sometimes have some weird entries... Once you're good, change the APN and use that as your default. Then un-Airplane your mode, if it's not. Give it a few minutes, then try to send an MMS.

I've had this issue a few times and it fixed this way. I've also had service on ST fail for a few hours completely and had some weird issues. Turned off the phone, pulled the battery for a few minutes, etc -- still had the same issues (I think any web calls had a "You are not authorized" webpage show up). The only thing to fix that was giving it time.

I'd say give those two things a shot and hopefully it will work. There's nothing wrong with the ROM, though, in terms of APN, but I think there may be some weird issue with APN-usage in Android itself.
[Samsung Captivate Glide] yivkhar:
Doesn't seem to work but the strange thing is that it was working before I flashed this rom and I flashed the Nexus One version on my brothers nexus and his MMS seems to have stopped working too but he's with a different carrier
[Samsung Captivate Glide] phatryan69:
OK is it just me or when u plug ur phone into a source that reads the SD card isn't the menu supposed to pop in the notification menu
[Samsung Captivate Glide] scottbot95:
I think that's gone in 4.2

Sent form my SGH-i927 running dman's cm10.1
[Samsung Captivate Glide] phatryan69:
Then how am I able to listen to my music via USB connection?
[Samsung Captivate Glide] yivkhar:
So I figured out my own problem with a little common sense (used stock messaging app)...But I'm still stumped because Go Sms worked with every rom I've ever had but this....It's confusing I guess somethings different with this rom that makes it not go sms friendly, Is anybody else having issues sending or receiving mms while using go sms or any other messaging app besides stock?
[Samsung Captivate Glide] dman3285:
The greatergood will be taking over development of my cm10 and cm10.1 as I am tired of the drama and Devs that don't know what they're doing developing for a device they don't own. Plus with real life taking precedence, I just don't have time right now. You guys are great and thanks for all your support..:thumbup: