Vibrate intensity is more stronger in stock rom. but in CM it is weak. i cant feel in my pocket when it is ringing. mostly i dont want to use CM cos of it. is there any solution to make vibrate intensity strong as stock one? (mod, change somethin... etc)
Note: in CM last version there is a setting vibrate weak-strong, i set most strong, not be enough again as stock one..
i hope i could tell with my bad English
join_23 said:
Vibrate intensity is more stronger in stock rom. but in CM it is weak. i cant feel in my pocket when it is ringing. mostly i dont want to use CM cos of it. is there any solution to make vibrate intensity strong as stock one? (mod, change somethin... etc)
Note: in CM last version there is a setting vibrate weak-strong, i set most strong, not be enough again as stock one..
i hope i could tell with my bad English
Click to expand...
Click to collapse
Did you try Iodak kernel? http://forum.xda-developers.com/showthread.php?t=2270308
There is a setting for vibrator control.
bilbo75 said:
Did you try Iodak kernel? http://forum.xda-developers.com/showthread.php?t=2270308
There is a setting for vibrator control.
Click to expand...
Click to collapse
i had read it, but i dint try, i will do
Here you can find a guide how to create a boot script http://forum.cyanogenmod.com/topic/41447-run-shell-script-at-boot/
Remember to recreate it everytime you upgrade or change rom
bilbo75 said:
Here you can find a guide how to create a boot script http://forum.cyanogenmod.com/topic/41447-run-shell-script-at-boot/
Remember to recreate it everytime you upgrade or change rom
Click to expand...
Click to collapse
thanx for your interest, i frigured it out. but not enough strong for me in maximum intensity. there should be other thing to do. i cant really feel in my pocket. if there is no solution, never you mind
join_23 said:
thanx for your interest, i frigured it out. but not enough strong for me in maximum intensity. there should be other thing to do. i cant really feel in my pocket. if there is no solution, never you mind
Click to expand...
Click to collapse
Very odd ,Iodak's kernel is based on LG sources.It should have the same behavior....
Related
ever since i flashed cyan6 ive been getting super battery problems and im starting to think its my phone and i should call htc. so before you ask questions lemme tell you what ive done. ive changed my setcpu to ondemand 998 to 245, 384 to 225 when the screens off. ive used auto brightness instead of my own custom brightness. ive also tried the HTC battery calibration process and that didnt do much either. on cm6 under about phone>battery use my display is always the highest percentage by far. for example its been 93 percent with 8 minutes on. ive also flashed wildmonks kernel to save battery and saw low results. any help would be super appreciated
Don't call HTC about problems with custom roms. Flash back to stock and see if the problems persist. I have no problems with the current nightly builds.
Don't use setCPU the way you are using it because it interrupts those values which are in the kernel already. setCUP is only for overclocking, that is it.
evilkorn said:
Don't call HTC about problems with custom roms. Flash back to stock and see if the problems persist. I have no problems with the current nightly builds.
Don't use setCPU the way you are using it because it interrupts those values which are in the kernel already. setCUP is only for overclocking, that is it.
Click to expand...
Click to collapse
really? so dont underclock at all. just overclock. and your saying i should flash back to stock froyo?
Just uninstall setCPU for the sake testing. All values should remain as default in that application except for the max high-end value if you want to over-clock, but even then it's such a small difference I view it as more of a show-off point rather than a practice use state.
Flash one of the newest nightly builds, see if your battery problem goes away.
Don't bother HTC if you have problems with custom roms only about problems with the stock rom.
evilkorn said:
Just uninstall setCPU for the sake testing. All values should remain as default in that application except for the max high-end value if you want to over-clock, but even then it's such a small difference I view it as more of a show-off point rather than a practice use state.
Flash one of the newest nightly builds, see if your battery problem goes away.
Don't bother HTC if you have problems with custom roms only about problems with the stock rom.
Click to expand...
Click to collapse
ok ill definately that now. ill letchu know later thanks. any more help is appreciated
So you have battery problems with a custom ROM, and you think it's HTC's fault.... wat?
Sure, send it in. $245 later, they'll send you a stock Nexus One with a new motherboard.
khaytsus said:
So you have battery problems with a custom ROM, and you think it's HTC's fault.... wat?
Sure, send it in. $245 later, they'll send you a stock Nexus One with a new motherboard.
Click to expand...
Click to collapse
yea ok not what i meant. i dont think the problem is gonna vary on which rom im using. i think its my phone. i heard the suggestion of a logcat but ive never used it before.
b33zy682 said:
yea ok not what i meant. i dont think the problem is gonna vary on which rom im using. i think its my phone. i heard the suggestion of a logcat but ive never used it before.
Click to expand...
Click to collapse
Install OS monitor. Open the app, go to the right tab messages. Now hit menu, options, scroll down to dmesg, filter tag, and type in the 4 letters batt. Now go out of settings and to the right tab messages and see your numbers. When you find data you want to keep for comparison, click export.
RogerPodacter said:
Install OS monitor. Open the app, go to the right tab messages. Now hit menu, options, scroll down to dmesg, filter tag, and type in the 4 letters batt. Now go out of settings and to the right tab messages and see your numbers. When you find data you want to keep for comparison, click export.
Click to expand...
Click to collapse
idk what this does but i did it and i have 0 messages now. nothings popping up anywhere
Hi Guys,
i updated my OB three days ago and all fine
but i noticed now that haptic feedback doesn't work
and i already checked it in settings !!!!
it was working good in froyo.
another Q,
how i put OB silent when it rings for a phone
call ???
is there OTA update for OB ??
Does your phone vibrate on any other occasions?
To mute your phone when somebody calls you, you have to press the volume down button.
yes it viprate normally when phone call and
message and go keyboard vibrate feedback .
Well I guess you could try reinstalling the update, but first double check your settings.
And if you feel brave and are prepared to move to something better you could root your phone and install a custom ROM.
i think the haptic feedback is working well
but it is very very weak feedback not like
before when froyo is installed !!
can i controll it to high it up ??!!
For me it has always been weak.
I have never seen a setting in custom ROMs or stock for haptic feedback strength, but I believe that there might be a possibility to set it's strength somewhere in the ROM configuration files.
a_alex_1993 said:
but I believe that there might be a possibility to set it's strength somewhere in the ROM configuration files.
Click to expand...
Click to collapse
where ????!!!!
and where is the OTA update in GB 2.3.4 in OB ??!!
my friemd has galaxy mini and has it on GB too !!
hatem 5000 said:
where ????!!!!
Click to expand...
Click to collapse
I'm sorry but that I do not know.
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?
Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.
sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values
Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk
I was using a nightly version of Cyanogenmod 11 for a while, and after one of the nightly updates, my vibration intensity has basically gone to nothing. I can still feel it very slightly but it's almost imperceptible. To try and fix it, I've gone as far as restoring to stock everything (including stock recovery etc.) to see if that would fix it, but still the same issue. Is there any chance this is still a software problem, or is it probably an issue with the vibration motors themselves?
superadamwo said:
I was using a nightly version of Cyanogenmod 11 for a while, and after one of the nightly updates, my vibration intensity has basically gone to nothing. I can still feel it very slightly but it's almost imperceptible. To try and fix it, I've gone as far as restoring to stock everything (including stock recovery etc.) to see if that would fix it, but still the same issue. Is there any chance this is still a software problem, or is it probably an issue with the vibration motors themselves?
Click to expand...
Click to collapse
cm based roms normally have a vibration strength that it set very low. Download trickster mod from the playstore and go to the fourth page (specific), you can set the vibrator strength there. Stock HTC One Sense is 2700.
Bhavpreet said:
cm based roms normally have a vibration strength that it set very low. Download trickster mod from the playstore and go to the fourth page (specific), you can set the vibrator strength there. Stock HTC One Sense is 2700.
Click to expand...
Click to collapse
Yeah I tried that, I set it to the highest value and was still imperceptible. Hardware issue?
superadamwo said:
Yeah I tried that, I set it to the highest value and was still imperceptible. Hardware issue?
Click to expand...
Click to collapse
only plausible explanation remaining
I just got my Nexus 6 yesterday and love it, but i REALLY hate how some of the volume controls works.
I can't figure out a way to stop the sound from playing when I put my phone on the wireless charger at night. how can i do this with the volume settings?
i can't even see a way to do it with an xposed module
any help is appreciated.
knives of ice said:
I just got my Nexus 6 yesterday and love it, but i REALLY hate how some of the volume controls works.
I can't figure out a way to stop the sound from playing when I put my phone on the wireless charger at night. how can i do this with the volume settings?
i can't even see a way to do it with an xposed module
any help is appreciated.
Click to expand...
Click to collapse
Not sure. The fix has been mentioned here somewhere before. My guess would have to disable that .ogg file by renaming (add bak to end). That would also require root as I believe it is in system/media.
Removing the ogg won't help. You have to replace it with a silent ogg of the same name.
Edit, here's mine...
https://www.dropbox.com/s/6p0s75dj7a9sjn0/WirelessChargingStarted.ogg?dl=0
danarama said:
Removing the ogg won't help. You have to replace it with a silent ogg of the same name.
Edit, here's mine...
https://www.dropbox.com/s/6p0s75dj7a9sjn0/WirelessChargingStarted.ogg?dl=0
Click to expand...
Click to collapse
thanks. that works.
man, i can't believe how dumb it is that even if i'm on silent mode system sounds are still made and we don't have that option anymore
which system sounds? i havent enabled any, so i dont have any. anyways, on m its all fixed.
simms22 said:
which system sounds? i havent enabled any, so i dont have any. anyways, on m its all fixed.
Click to expand...
Click to collapse
Thought that was a fix in M but haven't tried it. Use my phone in Healthcare environment so can't run buggy previews. Lol
prdog1 said:
Thought that was a fix in M but haven't tried it.
Click to expand...
Click to collapse
yea, sounds are fixed in m. and i really like the fact that you dont get any sound notifications when your screen is on :good:
simms22 said:
yea, sounds are fixed in m. and i really like the fact that you dont get any sound notifications when your screen is on :good:
Click to expand...
Click to collapse
Once M is stable I will flash it. Being a Nurse can't take chances on my device. That why I run basic stock rooted with mods I need hard coded.
prdog1 said:
Once M is stable I will flash it. Being a Nurse can't take chances on my device. That why I run basic stock rooted with mods I need hard coded.
Click to expand...
Click to collapse
im just rather good about making nandroid backups.. when it becomes unstable, and crashes, i just restore a fresh nandroid backup. then im back up and running within minutes