Related
Hi im so sorry for making yet another thread for the camera autofocus noise but it seems devs keep ignoring this.
the camera auto focus on different roms will be worse. sometimes doing it when you turn the phone on when you use flashlight and even sometimes when the card is being read. and im sick of hearing devs blame it on the camera model or that its always been there. my camera never made any noise till i installed miui and ever since it makes noise even when i revert to stock roms. the best its been is on villian rom.
this is obviously a problem with the firmware being used or something else that devs are doing or not doing. can someone please devote some time to get this fixed please. im not the only one who feels this way and i think its wrong for devs to lead us to believe its normal when its clearly not if it effects different on different roms and that obviously the noise wasnt there before. i think its a serious fix needed.
so please please please someone get to the bottom of this
PLEASE NO ONE POST INLESS YOUR HERE TO WORK TOWARDS A FIX
mikeinessex said:
PLEASE NO ONE POST INLESS YOUR HERE TO WORK TOWARDS A FIX
Click to expand...
Click to collapse
Actually i posted to let you know that if you have an OC camera, it's normal. All OC cameras make that noise, no matter what rom you are using
Sp1tfire said:
Actually i posted to let you know that if you have an OC camera, it's normal. All OC cameras make that noise, no matter what rom you are using
Click to expand...
Click to collapse
and like i said before if thats so then mine wouldnt of not made noise then now makes it. so please no comments like that on here please its not getting this problem sorted
mikeinessex said:
and like i said before if thats so then mine wouldnt of not made noise then now makes it. so please no comments like that on here please its not getting this problem sorted
Click to expand...
Click to collapse
Ok, sorry for stating the obvious. Please find somebody with an OC camera that doesn't act like that, be it on stock or custom rom and then we can talk about fixing things. If that's default behavior for OC cameras and looks like it is, no dev can fix it. But i have a fix for you: replace your phone with another SII that doesn't have an OC camera. Easiest fix in the world and you can do it yourself.
Sp1tfire said:
Ok, sorry for stating the obvious. Please find somebody with an OC camera that doesn't act like that, be it on stock or custom rom and then we can talk about fixing things. If that's default behavior for OC cameras and looks like it is, no dev can fix it. But i have a fix for you: replace your phone with another SII that doesn't have an OC camera. Easiest fix in the world and you can do it yourself.
Click to expand...
Click to collapse
i seen people who have had se firmwares and the update gave them oc and visa versa. so obviously the firmware code has no relavence to the camera. if what you say was right then the above wouldnt be possible. check out the camera firmware upgrade thread and see for yourself
I'm checking that thread often, cause i'm interested in a fix myself, but i still don't buy that firmware change, since no one else succeeded in changing an OC camera to a SC one. There's only 1 report of it. Can't really compare 1 report to all the owners with an OC camera that confirmed the clicking noises regardless of roms, firmware updates and everything else. I got no quarrel with you and i really wish you could find someone with an OC camera that doesn't behave like that. I couldn't find any and i investigated both on several forums and in real life with friends who own SII.
P.S. And i'm pretty sure if that guy uploads his apk your phone will say camera already has the latest update and can't install it.
Sp1tfire said:
I'm checking that thread often, cause i'm interested in a fix myself, but i still don't buy that firmware change, since no one else succeeded in changing an OC camera to a SC one. There's only 1 report of it. Can't really compare 1 report to all the owners with an OC camera that confirmed the clicking noises regardless of roms, firmware updates and everything else. I got no quarrel with you and i really wish you could find someone with an OC camera that doesn't behave like that. I couldn't find any and i investigated both on several forums and in real life with friends who own SII.
P.S. And i'm pretty sure if that guy uploads his apk your phone will say camera already has the latest update and can't install it.
Click to expand...
Click to collapse
the apk doesnt work. you cant do it like that i tried. u have to have a firmware upgrade apk or be compiled from scratch. just taking the apk out through root explorer wont make any difference.
Tested all the firmware update apks posted in that thread. None could be applied and my cam remained OC002, even though people reported that they had 002 and it turned to 009, which i highly doubt it can be done just by updating camera, cause 009 is an older version and camera wouldn't let you downgrade to a previous version. My phone has no root, so i don't have any other options than wait for another firmware update from Samsung.
Sp1tfire said:
Tested all the firmware update apks posted in that thread. None could be applied and my cam remained OC002, even though people reported that they had 002 and it turned to 009, which i highly doubt it can be done just by updating camera, cause 009 is an older version and camera wouldn't let you downgrade to a previous version. My phone has no root, so i don't have any other options than wait for another firmware update from Samsung.
Click to expand...
Click to collapse
been speaking to codework. would have to be pushed in through system/ect/firmware and it seems that the roms only come with oc type firmwares. so the roms have never been giving the phone the options for the se type firmwares. things are started to prove my point now. think codework is looking into it more now cause my theory is started to maybe be true
I have OCED11 ver of camera and today I heard that sound when entering camera, and when switching from photo to video mode. I don't remember hearing it before, but if others have it also, then it's nothing abnormal. I bought phone 1 month ago, and didn't install any custom apps and etc.
I have noticed that on the 5 or 6 custom roms I have flash that the auto brightness works great. Although I believe it to be a bit too sensitive causing what I would describe as ever changing brightness almost like a flicker. Has anyone else had this problem or notice it? And is there a fix?
Sent from my PG86100 using XDA App
Mrdiaz09 said:
I have noticed that on the 5 or 6 custom roms I have flash that the auto brightness works great. Although I believe it to be a bit too sensitive causing what I would describe as ever changing brightness almost like a flicker. Has anyone else had this problem or notice it? And is there a fix?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
i'm on a stock rom and i have noticed the auto brightness does seem to work fairly quickly .. but i haven't noticed anything similar to a flicker.
i've noticed when i sometimes put a finger over the light sensor on accident it will adjust and then i remove my finger and it readjusts .. i haven't ever seen it adjust too quickly to cause something like a flicker.
could you give more details on when/how you've seen it be "too sensitive" or have a "flicker"? i would like to see if i can replicate on a stock rom!
I believe its the problem you are talking about. I just did some test and like you said if I put my finger over the sensor it does it super fast as well as anytime I create a shadow while using the phone and it hits the sensor. I would personally like to see if we could somehow change the rate that the sensor registers without adversely affecting anything else
Sent from my PG86100 using XDA App
Would the sensors.shooter.so in /system/libs/hw be the place to start trying something?
Sent from my PG86100 using XDA App
Do the ROMS you use have the CRT shutdown and open animation? If so this MOD does cause some flicker with the autobrightness enabled. Viper ROM thread has a flashable fix but it also removes the CRT animation. Not sure if that will be compatible with your ROM though as it replaces the services.jar.
Mrdiaz09 said:
Would the sensors.shooter.so in /system/libs/hw be the place to start trying something?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
from my understanding any of the .so files in /system/libs/hw are compiled file and might be a bit difficult to sort thru in a decompiler but if you have the time and patience, it is worth a try!
short answer: i would look thru the drivers for the sensor in the kernel code.
longer answer: i remember having an issue on the samsung moment with the light sensor not responding quick enough. from that previous discussion which is now over a year or so old, i remember leaning towards the kernel source code as potentially having some type of timing adjustment for the drivers which control that sensor.
down side is no updated kernel source has been released for 2.3.4 yet, but at least 2.3.3 is available and i'm sure very few changes were made to this area of the kernel so it should be the same when 2.3.4 is released.
ideal answer: the kernel is compiled with sysfs support so the light sensor sensitivity can be adjusted live in userspace! this is of course a dream more than a reality but figured i'd throw it out there as an ideal end goal.
hope that helps! keep us updated if you have a chance to dig deeper!
This weekend I'm going to dig deeper into the so file. As well as trying to switch back to 2.3.3 and mess with the kernel a little that way if I find anything when the kernel source is released for 2.3.4 I could possibly have a fix. I'm not sure if anyone else would like the sensor timing to be lowered just a little like I would. But I will definitely keep everyone informed with my findings
Sent from my PG86100 using XDA App
Mrdiaz09 said:
This weekend I'm going to dig deeper into the so file. As well as trying to switch back to 2.3.3 and mess with the kernel a little that way if I find anything when the kernel source is released for 2.3.4 I could possibly have a fix. I'm not sure if anyone else would like the sensor timing to be lowered just a little like I would. But I will definitely keep everyone informed with my findings
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
i posted the following suggestion and method of research in another thread regarding camera compression and searching thru the kernel source for the settings.
regarding the light sensor timing, i think a similar approach might be helpful. the best source for updated and properly compiling kernel source, in my opinion, https://github.com/toastcfh/htc-8660-kernel . i think most custom kernels on here are forked from his and then modified.
starting with the shooter_defconfig file, i'd search for references to sensors/light sensors and see which one is being included in our specific device. from there, i would grep the kernel source to see where the ifdef calls are at for the driver pieces and work out from there.
hope that makes sense and helps in the research! look forward to seeing anything you're able to put together!
Thanks and yes that did make sense. Sorry about the delay hurricane Irene really hit me hard I finally got power back Wednesday and this has been the last thing on my list. I have found what I think to be a fix, however I'm testing right now to make sure I didn't Bork anything else. Should be out to public mid next week.
Sent from my PG86100 using XDA App
You can decompile the framework-res.apk and edit the arrays in res/values/array.xml.
Just have a look at my sig for the guide, how to do it.
Also interesting post from leedroid:
http://forum.xda-developers.com/showpost.php?p=17220302&postcount=109
If you haven't yet tried kushdeck you should, so far it's the only one with crt that had smooth auto light, but you can also turn off the screen transitions in settings and keep crt, you can also use spare parts to have faster animations and again not lose crt.
Hello,
Firstly sorry for my english, i'm new here that i cant put images from standard method that i must put it in attachments sorry for trouble. That's my problem on every every CM mod when i load "cm-7.1-oc-kernel-2.6.35.7-perf-CL562111.zip"i have problem with touch screen.
(screenshot1 from attachments)
The above screen shows the twirling finger rings. It is very irritating when you look through post office or browse the Internet
But when i put cm-7.1-kernel-2.6.35.7-perf-CL562111.zip everthing is ok. (screenshot2 from attachments)
This is cm-7.1-kernel-2.6.35.7-perf-CL562111.zip: nothing problem with touchscreen
(screenshot3 from attachments))
But when i use OC kernel : i have very big problem witch touchscreen
this problem This problem regards each one CM, CM 7.1 CM 7.2 JAF, Griff, KANG, Icecream Sunday2, BehradGH, GingercruztV2.3. EVERY ONE.
I tried to upload KPB, KS9, KS2, KPY, everything WIPE. Always end the same.
Thank You
Please Help
Then don't use the overclock kernel .
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
Then don't use the overclock kernel .
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Thanks for the very constructive and wise answer. I think that my 5 year old child that could advise me the same thing
icemanhi said:
Thanks for the very constructive and wise answer. I think that my 5 year old child that could advise me the same thing
Click to expand...
Click to collapse
Well , you chose to use the kernel , it's your fault
Sent from my GT-S5830 using XDA App
icemanhi said:
Thanks for the very constructive and wise answer. I think that my 5 year old child that could advise me the same thing
Click to expand...
Click to collapse
I know it's not the most helpful response, but there really isn't a good solution. If you choose to overclock the phone there is a price to pay. Your price unfortunately, is touch screen issues. Others have stability issues and others cannot o/c at all. Personally I think the only reason to use an o/c kernel on the Ace is for the scheduler choices.
Sent from a ZTE Crescent with an app.
Look man,OC is not a thing to play with,in your case it was touchscreen issues,others have other problems.Dont use oc in my opinion
Hey @icemanhi...
Firstly, your english is fine... I can understand you & I'm sure others can too...
Now, lots of people saying "Don't do it" but nobody offers help... Come on guys, give @icemanhi a break... @Prawesome is correct though to a degree... OC'ing is not for everyone but with a little care & patience, you can achieve some significant performance gains...
@icemanhi... There are a couple of things that you can try that may correct this touch screen issue that you have got. It is possible that when you flash @ketut's OC kernel, it corrupts your screen variables or changes them to un-usable values. If you search the SGA development forum you will find several scripts that enhance & tweak your touch screen (response, sensitivity etc)... some of them are flashable via CWM (clockwork Mod manager), some of them you must manually place the script in the correct location within your phone...
I suggest you try one of the flashable versions unless you are savvy to file placement & permission setting...
Flashing the screen Mod will re-callibrate your screen to the new improved variable settings, hopefully correcting any corruption that was left from flashing @ketuts kernel...
Please remember though, that I am not providing a cure, I am just suggesting a method that in theory should do the trick. I can not say I have tried this as I have experienced no problems at all using Ice cream sunday2 by @jusada... On the other hand, I have used the touchscreen tweaks (I am using them now) & they work wonderfully... I barely have to brush my screen & I get a response...hehe
Check below my signature for my Rom & setup...
Stay Breezy n Be Lucky...
Peace...
Notice: Saurom RCV users, there is a fix so that you can flash other kernels. The problem was caused by an incompatible library being flashed over Saurom's RTL modded library. In the future, my kernels will ship without modified libraries, and a cwm zip containing only the libraries will be offered (for those who need them).
For your pleasure, here is a new kernel for the ATT Galaxy Note. This kernel is forked from Da_G's Overclock kernel, so you are still getting all the features of that excellent piece of code.
For those a bit confused as to what 'Ghost thouch' is, and why it is removed:
Samsung added a bit of code to the touchscreen driver on the non-intl version of the note to detect 'ghost' touch input events, similar to the raindrop detection on the original Motorola Atrix (and others). While a nice idea on paper, this had un-intended consequences when trying to perform multi-touch input that continues longer than around 5 seconds; such as playing some games. It is now disabled in this kernel.
Edit: There also seems to be a pleasant side effect that I hadn't noticed... keyboard input is improved. Makes sense I suppose, since now there isn't this constant check for false touches slowing things down. Let me know if you see this on your device.
Please READ:
1. I have only tested this kernel on the ATT Galaxy Note running stock rom
2. This kernel has no option to turn ghost touch detection on and off (I am considering this for version 0.2)
3. I will likely not fix the issues where more than 6 fingers are not reliably detected.... why do you need that many fingers on the screen??
4. As always, you are flashing something on to your expensive phone and it very well could kill you, burn [more] holes in the ozone layer, intoxicate innocent kittens, etc. (oh, and break your phone). You always flash at your own risk.
5. The only change at the moment over Da_G's 0.2 kernel is the touchscreen stated above. As such, all the other good or bad remains the same.
Have fun, Let me know what you think.
Heard from:
Saurom RC4 -- Works fine
Saurom RC5 -- holoNote kernel is bundled already, but if you want to flash a different kernel you must apply a cwm zip containing a RTL modded lib
TPC V2 -- Works fine
Rogers -- Works fine
Kallsyms version of my Kernel is now up (file ending with suffix 'k'). Please confirm that it is working for you guys that use that feature (I do not).
Per request: Version without su/busybox (and install script) is now up. Please NOTE: this kernel does not remove root, just no longer installs root.
An oversight of mine has resulted in android reporting kernel version unavailable. Apps such as cpuspy report correct kernel name/ version.
https://github.com/hololight/sgh-i717-kernel
When you flashed this was it on top of a custom rom or stock? Just trying to decide if I want to flash on top of saurom.
Flashed on Saurom RC4 and it booted fine. It seems I don't have anymore keyboard problems with this kernel either. I can finally type fast again!
Sent from my SGH-I717R using xda premium
As stated above, I have only tested this on stock att rom. That said, as Da_G's kernel works with Saurom, I can not see how this would cause any problems.
As people confirm it works in 'X' situation, I will update the op.
hololight said:
For your pleasure, here is a new kernel for the ATT Galaxy Note. This kernel is forked from Da_G's Overclock kernel, so you are still getting all the features of that excellent piece of code.
For those a bit confused as to what 'Ghost thouch' is, and why it is removed:
Samsung added a bit of code to the touchscreen driver on the non-intl version of the note to detect 'ghost' touch input events, similar to the raindrop detection on the original Motorola Atrix (and others). While a nice idea on paper, this had un-intended consequences when trying to perform multi-touch input that continues longer than around 5 seconds; such as playing some games. It is now disabled in this kernel.
Please READ:
1. I have only tested this kernel on the ATT Galaxy Note running stock rom
2. This kernel has no option to turn ghost touch detection on and off (I am considering this for version 0.2)
3. I will likely not fix the issues where more than 6 fingers are not reliably detected.... why do you need that many fingers on the screen??
4. As always, you are flashing something on to your expensive phone and it very well could kill you, burn [more] holes in the ozone layer, intoxicate innocent kittens, etc. (oh, and break your phone). You always flash at your own risk.
5. The only change at the moment over Da_G's 0.2 kernel is the touchscreen stated above. As such, all the other good or bad remains the same.
Have fun, Let me know what you think.
Any chance of getting this with the kallsysms function that DA_G implemented in one version of his kernel 0.2? Thanks it would allow us more screen improvement with the touchscreentune app available (which works well to re-calibrate the pens offsets btw)?
Heard from:
Saurom RC4 -- Works fine
https://github.com/hololight/sgh-i717-kernel
Click to expand...
Click to collapse
Please hit THANKS button if I help you, I have very low self esteem, and I crave validation! Sent from my Team EOS ICS Xoom
Quick question. Which of the three versions of Da_G's kernel is this from. I'm using his one with the kalysms (so?)
Sent from my SAMSUNG-SGH-I717 using xda premium
I hope to have a version with kallsyms up later today.
Sent from my SAMSUNG-SGH-I717 using XDA
hololight said:
For your pleasure, here is a new kernel for the ATT Galaxy Note. This kernel is forked from Da_G's Overclock kernel, so you are still getting all the features of that excellent piece of code.
For those a bit confused as to what 'Ghost thouch' is, and why it is removed:
Samsung added a bit of code to the touchscreen driver on the non-intl version of the note to detect 'ghost' touch input events, similar to the raindrop detection on the original Motorola Atrix (and others). While a nice idea on paper, this had un-intended consequences when trying to perform multi-touch input that continues longer than around 5 seconds; such as playing some games. It is now disabled in this kernel.
Please READ:
1. I have only tested this kernel on the ATT Galaxy Note running stock rom
2. This kernel has no option to turn ghost touch detection on and off (I am considering this for version 0.2)
3. I will likely not fix the issues where more than 6 fingers are not reliably detected.... why do you need that many fingers on the screen??
4. As always, you are flashing something on to your expensive phone and it very well could kill you, burn [more] holes in the ozone layer, intoxicate innocent kittens, etc. (oh, and break your phone). You always flash at your own risk.
5. The only change at the moment over Da_G's 0.2 kernel is the touchscreen stated above. As such, all the other good or bad remains the same.
Have fun, Let me know what you think.
Heard from:
Saurom RC4 -- Works fine
Kallsyms comming soon.
https://github.com/hololight/sgh-i717-kernel
Click to expand...
Click to collapse
OMG, yesterday i was trying to analyze why my keyboard is missing keypresses when i type quickly and i came to the conclusion that it must be some sort of an accidental touch algorithm that works in the background!
I'm going to check this out!
Thanks!
Op updated with kallsyms support kernel... enjoy.
gonna flash and report back its nice to see another dev here
What's Kallsyms?
lowspeed said:
What's Kallsyms?
Click to expand...
Click to collapse
Da_G has a build of the kernel with this:
Version 0.2 CWM Zip (with KALLSYMS + KALLSYMS_ALL for debugging)
The original request came from someone who wanted to use an app to help fix the spen issues which required this I believe.
hololight said:
Op updated with kallsyms support kernel... enjoy.
Click to expand...
Click to collapse
Thank you! Amazing!
My phone will eat your Apple!
Not discounting your work here - and this is just my opinion.
It might've been better to work with DaG and get him to integrate this into his kernels. do you plan to re-release every time he makes changes to his kernels?
Can i use this on my rogers galaxy note? Will i loose lte on rogers or nfc? Thanks
Sent from my SGH-I717R using Tapatalk
Hrmm... should ignore it? Yeah... ill ignore it.
Sent from my SAMSUNG-SGH-I717 using XDA
Turilo: only tested on att stock. But as nfc and lte are android and modem respectivly, I would guess you should be fine? Let me know how it goes.
Sent from my SAMSUNG-SGH-I717 using XDA
OK tested it out. I don't think it helped.
hololight said:
Hrmm... should ignore it? Yeah... ill ignore it.
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
I wasn't trying to start anything, it was a serious question though. Are you going to release a new one after DaG does changes to his kernel?
hololight said:
Turilo: only tested on att stock. But as nfc and lte are android and modem respectivly, I would guess you should be fine? Let me know how it goes.
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
Ok so far seems fine on my rogers note but when checking kernel in about phone i get unavailable? Grat work by the way
Sent from my SGH-I717R using Tapatalk
To us canadian users stuck on the JB modem's.... pretty much the only problem I have noticed by installing the hybrid modem made my morislee is that the autorotation is inverted...
I was wondering if there was a way to make some other xposed module or patch of sort to invert the inversion ....
Not having autofocus while taking a video really blows ...
So if anyone got ideas... do brainstorm please...
danial.aw said:
To us canadian users stuck on the JB modem's.... pretty much the only problem I have noticed by installing the hybrid modem made my morislee is that the autorotation is inverted...
I was wondering if there was a way to make some other xposed module or patch of sort to invert the inversion ....
Not having autofocus while taking a video really blows ...
So if anyone got ideas... do brainstorm please...
Click to expand...
Click to collapse
I would hit up @morrislee and ask what he needs from you to make your own hybrid variant, he cranked out the ones for us after the mako versions extremely fast, seems like a nice enough dude, and this way you wont need any wacky workarounds.
Ya I did message him... Unfortunately I believe he is busy
[r.]GimP said:
I would hit up @morrislee and ask what he needs from you to make your own hybrid variant, he cranked out the ones for us after the mako versions extremely fast, seems like a nice enough dude, and this way you wont need any wacky workarounds.
Click to expand...
Click to collapse
A hybrid modem will most likely not fix the rotation issues. The issue is with the dsps.* image files in the modem. They are the firmware that is sent to the Hexagon DSP processor, and they are signed, so they most likely cannot be modified. They control sensor function, which includes both rotation and camera autofocus. A userspace patch would be needed to fix autorotation if those firmware files are used.
SnowLeopardJB said:
A hybrid modem will most likely not fix the rotation issues. The issue is with the dsps.* image files in the modem. They are the firmware that is sent to the Hexagon DSP processor, and they are signed, so they most likely cannot be modified. They control sensor function, which includes both rotation and camera autofocus. A userspace patch would be needed to fix autorotation if those firmware files are used.
Click to expand...
Click to collapse
Stuff like this keeps schooling me every day, brain starting to hurt
That being said, I setup an Ubuntu environment earlier today, from one of the guides in chef central, using 12.04 64bit, got all the packages, but i'm terrified to sync a potential 10 gigs of stuff, what exactly should i be syncing to on github for our device, and say for illusion rom to try building from source?
and as I side project today, I nearly got a zte x500 to take a custom rom and recovery from the stock recovery, after noticing ZTE signed their packages with the test keys, just needed to figure out the mmcblk for recovery for the cricket score <edit> I know the syntax that particular updater script needs now, but dont have access to the phone til monday. the person is getting a new phone anyway but it's my pet project to flash a custom rom and recovery from the stock recovery and good practice doing updater-scripts from scratch </edit>
Been a fun day.
danial.aw said:
Ya I did message him... Unfortunately I believe he is busy
Click to expand...
Click to collapse
I am not "busy" haha, just on vacation without my computer out of country
Ahh well hope you have fun and get back to your computer soon times lol
Hey Morris any chance you are back and kicking?
morrislee said:
I am not "busy" haha, just on vacation without my computer out of country
Click to expand...
Click to collapse
Just checking, would it be possible for you to make an inversion patch for your hybrid modem?