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.
Related
Hey all,
Searched the forums for this and found a bit of discussion, but not a fix.
I know some people are using swiftkey x and not having display problems, but for me it's borked, no matter what i do. I've tried clearing app data, removing and reinstalling etc - nothing seems to work. Settings pages occupy about 2/3 of the screen real estate, centered horizontally and stuck to the top of the screen vertically, and when the keyboard is in use, it takes up 80% of the screen but mostly with black empty space. For this latter reason, it's pretty much unusable.
My carrier is Orange UK, but my handset is a retail/SIM unlocked stock ROM. It is up to date with OTA updates.
Is there a fix for this? Or am i screwed?
Thanks all, and apologies if this question has already been answered - i did try in earnest to find it.
Sorry but need to ask... Where did you get it from?
I got mine from the Market and all is good and dandy.
Worth every penny I must add.
Sent from my Atrix using Tapatalk
Rayan said:
Sorry but need to ask... Where did you get it from?
I got mine from the Market and all is good and dandy.
Worth every penny I must add.
Sent from my Atrix using Tapatalk
Click to expand...
Click to collapse
must agree, no problems at all........
I'm using the betas and havent seen such a problem, be it on stock, cm7 or customized blur roms. Maybe try spare parts and disable that legacy app fix.
Rayan said:
Sorry but need to ask... Where did you get it from?
I got mine from the Market and all is good and dandy.
Worth every penny I must add.
Sent from my Atrix using Tapatalk
Click to expand...
Click to collapse
No worries The market just like you. In fact i've been a SwiftKey customer for a long long time. My old SwiftKey licence seemed to transfer over to SwiftKey X when it was formally released. I did have the X beta, and at first it was fine, then after one particular update it started with this screen problem, and has been that way ever since, even after the official first release.
crnkoj said:
I'm using the betas and havent seen such a problem, be it on stock, cm7 or customized blur roms. Maybe try spare parts and disable that legacy app fix.
Click to expand...
Click to collapse
This sounds hopeful! I haven't heard of spare parts but im assuming its some sort of tweaking program? I can use it to disable some sort of legacy fix for older, none qHD apps? is that right?
EDIT: I installed spare parts but just have the following options on a settings-style screen:
battery history
battery information
usage stats
window anims
transition anims
fancy input anims
fancy rotation anim
end button behavior
haptic feedback
compatibility mode
wifi sleep policy
activity/process management
brightness mode
font size
show compass in maps
Only one which looks promising is compatibility mode?
EDIT2: Thanks a lot for that crnkoj - got it working! For all who're reading this thread and want to know: use spare parts to disable compatibility mode!
Sure, np. And ye, i meant compatibility fix just didn't remember the correct name.
So...
I have been noticing that when I drag my finger side to side very slowly, the screen initially does not move and then catches up. So it looks like it's lagging a bit. Once it catches up though it's fine..
Maybe I am being a paranoid.. but the screen does not move side to side smoothly.
I am not sure if it's been doing that before I've done anything to it (root, mod, etc).
Is this normal? Any thoughts?
Try getting it to mess up after a fresh reboot and making sure as many programs as possible are *not* running.
If your phone is the I777 and you already have a kernel that allow you to overclock (entropy's) try turning the processor down low and see if it's worse and compare it to the speed turned up high.
If it's the same and definitely lagging there may be some system tweaks needed.
If it's not the I777, well I'm genuinely sorry.
Sent from my SAMSUNG-SGH-I777 using XDA App
My phone is the I777 and it is running entropy's kernel
I went back to the state where it had been only rooted and tried and I've experienced the same thing...
I am not sure what the problem might be...
So I guess there is a problem? and this is not supposed to lag like this?
Also, this is only when I drag it very slowly. It is barely noticeable when I do it as I would normally.
Thanks for your reply
Not sure what could be causing that. I just tried using tw launcher and couldn't seem to get mine to mess up.
Are you talking sliding left and right on your home screen or app drawer?
Sent from my SAMSUNG-SGH-I777 using XDA App
I may see what you're talking about. I think it's ok.
The phone has to figure out if you're pressing to select something on the screen or going to slide back and forth, thus the slight stutter from your finger going slow.
Since it's not noticeable at normal scrolling speeds you should be fine, otherwise you should be able to see it more so there.
Sent from my SAMSUNG-SGH-I777 using XDA App
Cool. I will try not to be so paranoid about this haha.
Thanks for your input!
Additional Question.
I may be wrong, but this may have been after I modified twlauncher with a mod.
Could this be the cause? If so, can it be fixed?
Depends. What did you do to mod it?
Sent from my SAMSUNG-SGH-I777 using XDA App
Here's the link to the mod
[MOD][11/5]Modified AT&T TouchWiz 4|5 icon dock|5 columns in app drawer
http://forum.xda-developers.com/showthread.php?t=1333684
Well you asked for the right thing on that thread to revert. Each of the files that mod replaced will have to be put back.
You can wait and hope someone comes up with a cwm package to revert. Or use a program like root explorer to replace the files one by one from a stock rom.
I usually just go for flashing my entire phone when I'm looking at what you're doing. It's easy and it's quick.
Sent from my SAMSUNG-SGH-I777 using XDA App
oh. so that WAS the problem.
Every time I look into the phone and I notice this first. It's very annoying me
Well I have an access to stock TwLauncher.
Can I just replace the whole TwLauncher? Just copy and paste TwLauncher.apk file into the phone? I think that will be the simplest way rather than looking for what it replaced. Or I might just request a flashable twlauncher and someone might be generous enough to upload it for me..
You could always try reflashing the mod. It may correct the issue. If more people were reporting the problem it wouldn't be as likely.
Sometimes flashes don't 'stick', and nobody is really sure why.
Sent from my SAMSUNG-SGH-I777 using XDA App
I have reflashed the mod several times just to make sure.
It did not seem to help.
I just requested a stock TwLauncher.apk
Hopefully someone will be generous enough to help me out..
Thanks gr8hairy1 for replies and helps!
Please update if you get it fixed. I'll be busy the next couple days. When I get a chance I'll pull everything you need.
Though just flashing back to stock will save you a bit of time. But it's always good to learn new things.
Sent from my SAMSUNG-SGH-I777 using XDA App
so I flashed the stock twlauncher, but still not fixed.
I am thinking of going back to stock and see if that fixes it
back to bonestock.
Still experiencing the same problem. At this point, I am not sure what the problem is..
It seems like this is only for TwLauncher. GoLauncher seems to work better.
is there a way to mod the camera flash so it lets me use it even if the battery is really really low...I want to set the threshhold at 0 percent...sometimes...I just need to take a pic...and 20 percent is more than enough for one quick flash for a pic.
seansk said:
is there a way to mod the camera flash so it lets me use it even if the battery is really really low...I want to set the threshhold at 0 percent...sometimes...I just need to take a pic...and 20 percent is more than enough for one quick flash for a pic.
Click to expand...
Click to collapse
anyone? please???
seansk said:
anyone? please???
Click to expand...
Click to collapse
When does it prevent you from using the flash? I've used mine at less than 20% but have had wifi, gps and data connection turned off. I wonder if unchecking the power saver and efficiency boxes would help?
EDIT: Okay, I see what you mean. I finally got it to say the flash couldn't be used because the battery level is too low. I turned off power saving and it still didn't work. I tried ProCapture which I like a lot because it doesn't compress the images thus better quality. It has a "torch" option on its flash menu so I tried that. The flash stays on continuously in that mode, even with a low battery. I took a shot in total darkness and it didn't seem to work. the flash was on but no picture? Maybe with some light it would work? ProCapture is free to try so you might want to try it to see if that would work under normal night conditions. I guess it won't work in total darkness like the auto flash will.
Another edit: I noticed that the flash was disabled right at 15% so I did some searching and found this: With root explorer (or any rooted file explorer), go to sys/camera_led_status/low_cap_limit. There you will find the number 15 for 15%. I tried to change this to 5 but the file is locked and I don't know enough to unlock it, rename it and then change it through adb. I think I read that you can't do this through root explorer. Maybe someone with knowledge of how to do this will know how to do it. I'm sure it is relatively simple and a zip file could even be written to change it. At least we now know where the setting is!
frodoboy said:
When does it prevent you from using the flash? I've used mine at less than 20% but have had wifi, gps and data connection turned off. I wonder if unchecking the power saver and efficiency boxes would help?
EDIT: Okay, I see what you mean. I finally got it to say the flash couldn't be used because the battery level is too low. I turned off power saving and it still didn't work. I tried ProCapture which I like a lot because it doesn't compress the images thus better quality. It has a "torch" option on its flash menu so I tried that. The flash stays on continuously in that mode, even with a low battery. I took a shot in total darkness and it didn't seem to work. the flash was on but no picture? Maybe with some light it would work? ProCapture is free to try so you might want to try it to see if that would work under normal night conditions. I guess it won't work in total darkness like the auto flash will.
Another edit: I noticed that the flash was disabled right at 15% so I did some searching and found this: With root explorer (or any rooted file explorer), go to sys/camera_led_status/low_cap_limit. There you will find the number 15 for 15%. I tried to change this to 5 but the file is locked and I don't know enough to unlock it, rename it and then change it through adb. I think I read that you can't do this through root explorer. Maybe someone with knowledge of how to do this will know how to do it. I'm sure it is relatively simple and a zip file could even be written to change it. At least we now know where the setting is!
Click to expand...
Click to collapse
Yes thats exactly what I did in root explorer in sys/camera_led_status/low_cap_limit, I set it to 5, 1, 0, did not make any difference. Also Its retarded that you cannot use flash while you're in a call....if you talking to someone and trying to take a picture it says you cannot use flash since you're in a call....wtf does that have to do with the flash!!! There should be a file somewhere in the sense UI system to change these settings, If anyone has found anything please share...or if you can think of something please share as well...
I actually like the dialer and contact aspect of sense UI and how it integerates and automatically finds linked friends, how it updates friends status in facebook and twitter, (although they still need to integrate google plus)...all the other stuff of sense I do not like...I've changed to ADW ex...and widget locker...
I doubt there's a way to get that stuff with a senseless rom since its so integerated into the system...If there is I would flash another rom in a sec and just install that aspect of sense....
so apparently I can't use flash under 20% battery...under a certain temperature and when I'm in a call...So basically don't use flash....lol....I messed around with files under sys/camera_led_status which I believe controls temperature and battery limitations and also /sys/android_camera_awb_cal which I believe limits flash while you're in a call...I backed up deleted the directories and rebooted but they came right back...is this part of the kernel...I believe this requires S-off because I am unable to change this part of the system...or perhaps someone can do a quick kernel mod and take off all those limitations...
I got a better one for you.
Turn on the wireless access point feature, activate the camera and try to use the flash.
Binary100100 said:
I got a better one for you.
Turn on the wireless access point feature, activate the camera and try to use the flash.
Click to expand...
Click to collapse
you gotta be kidding me!!!!
question 1. Are the other roms the same?? I"m unlocked and rooted but on stock rom. do senceless, beastmod or revolution have the same problem...I'm guessing they would since they use the same camera apk...or maybe not, If not i'm flashing to something else RIGHT NOW.
questions 2. are we ever going to see CM9 on the amaze....screw sense I want ICS AOSP asap...
seansk said:
so apparently I can't use flash under 20% battery...under a certain temperature and when I'm in a call...So basically don't use flash....lol....I messed around with files under sys/camera_led_status which I believe controls temperature and battery limitations and also /sys/android_camera_awb_cal which I believe limits flash while you're in a call...I backed up deleted the directories and rebooted but they came right back...is this part of the kernel...I believe this requires S-off because I am unable to change this part of the system...or perhaps someone can do a quick kernel mod and take off all those limitations...
Click to expand...
Click to collapse
As I understand it, you tried to change the value to 0, 1, 5 and it still didn't work. If you looked at the file, it was still set to 15 right? I think you have to unmount the system, then pull it from your phone to your computer, alter the file and then push it back to the phone and remount the system. I have no idea how to do that. Binary is pretty good at writing little zips to do that sort of thing. I don't know if permanently changing that value will do anything though. I do know that root explorer says it changes the file but it doesn't.
frodoboy said:
As I understand it, you tried to change the value to 0, 1, 5 and it still didn't work. If you looked at the file, it was still set to 15 right? I think you have to unmount the system, then pull it from your phone to your computer, alter the file and then push it back to the phone and remount the system. I have no idea how to do that. Binary is pretty good at writing little zips to do that sort of thing. I don't know if permanently changing that value will do anything though. I do know that root explorer says it changes the file but it doesn't.
Click to expand...
Click to collapse
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Binary100100 said:
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Click to expand...
Click to collapse
crap I wish I was a developer!!! instead I had to go and fix teeth and become a dentist!!! but I'm very much into electronics. Is there a book I can read to start developing?
btw where do I post the request? in development or general?
seansk said:
crap I wish I was a developer!!! instead I had to go and fix teeth and become a dentist!!! but I'm very much into electronics. Is there a book I can read to start developing?
btw where do I post the request? in development or general?
Click to expand...
Click to collapse
I would suggest in the forum that consists of the kernel that you are using.
Example:
If you have QuikSense then post the request in the QuikSense forum or PM the developer (in this case xboarder56) directly.
If you use Faux's kernel then post it in that thread.
No need to start a new thread for a request. However if you feel that it is absolutely necessary do it in General because the Development section is not really a section mod requests.
Binary100100 said:
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Click to expand...
Click to collapse
Thanks Binary. You are sooooo smart!!
Flash limitation is controlled by kernel... Not sure why HTC decided to do that, but I can easily change this value in my next release from 20% to 10% or 5%.....
Of course if you decide to use the stock kernel, there's nothing much you can do about it... It is hardcoded in the kernel code.
Happy New Year!
faux123 said:
Flash limitation is controlled by kernel... Not sure why HTC decided to do that, but I can easily change this value in my next release from 20% to 10% or 5%.....
Of course if you decide to use the stock kernel, there's nothing much you can do about it... It is hardcoded in the kernel code.
Happy New Year!
Click to expand...
Click to collapse
Thanks
I think 5 percent is reasonable...also can you change the limitations for temperatureand also take off limitations when making a call and using wifi hotspot...the phone does not allow to take flash while its in low temp, when making a call or when using wifi tethering/hotspot.....thanks faux
seansk said:
Thanks
I think 5 percent is reasonable...also can you change the limitations for temperatureand also take off limitations when making a call and using wifi hotspot...the phone does not allow to take flash while its in low temp, when making a call or when using wifi tethering/hotspot.....thanks faux
Click to expand...
Click to collapse
Yeah that's HTC for you. Always thinking ahead. You never know when your phone might be damaged by taking a picture with the flash activated while using it as a hotspot. In regards to the cold... I live in Detroit, work at night and I've used it a couple of times without issue. How cold does it have to be? I kinda wanna see this! LOL! It's gotten down to about 19F here... can't remember if I had used the camera though.
But I can understand why you wouldn't want to use the flash in cold weather. Might cause an avalanche or wake a bear or something. Yikes! Smart thinking HTC!
Binary100100 said:
Yeah that's HTC for you. Always thinking ahead. You never know when your phone might be damaged by taking a picture with the flash activated while using it as a hotspot. In regards to the cold... I live in Detroit, work at night and I've used it a couple of times without issue. How cold does it have to be? I kinda wanna see this! LOL! It's gotten down to about 19F here... can't remember if I had used the camera though.
But I can understand why you wouldn't want to use the flash in cold weather. Might cause an avalanche or wake a bear or something. Yikes! Smart thinking HTC!
Click to expand...
Click to collapse
lmao....it bothers me that I'm talking to my gf and she wants a picture of something i have to hang up take the picture send then call back wtf!!!!! and don't even get me started on wifi hotspot...how does this make sense????????????????? sense ui should be called retarded ui cause it does not make "sense" no pun intended.
seansk said:
lmao....it bothers me that I'm talking to my gf and she wants a picture of something i have to hang up take the picture send then call back wtf!!!!! and don't even get me started on wifi hotspot...how does this make sense????????????????? sense ui should be called retarded ui cause it does not make "sense" no pun intended.
Click to expand...
Click to collapse
To HTC or to whomever it may concern,
I intend to propose a class action lawsuit pending on verification of an intentional design flaw that prevents the consumer to use the flash on the device while talking on the phone while also using the device as a wifi hotspot in subzero degree weather. I discovered this flaw while taking pictures of Bigfoot eating Santa's raindeer at the North pole just after Christmas. Unfortunately I was unable to take proof of evidence of the situation because of the mentioned designed flaw. While I was on the phone with animal control they demanded photographic evidence of the situation. Because I was not able to comply due to this design flaw the raindeer could not be saved thus there will be no more Christmas. Evidence of the intention for the mentioned limitations is the simple fact that the appropriate error messages are programed into the kernel source. However because you fail to include the wireless drivers, the kernel source cannot be utilized to compile a patch for this flaw.
Shame on you HTC.
I should be a prosecutor.
Binary100100 said:
To HTC or to whomever it may concern,
I intend to propose a class action lawsuit pending on verification of an intentional design flaw that prevents the consumer to use the flash on the device while talking on the phone while also using the device as a wifi hotspot in subzero degree weather. I discovered this flaw while taking pictures of Bigfoot eating Santa's raindeer at the North pole just after Christmas. Unfortunately I was unable to take proof of evidence of the situation because of the mentioned designed flaw. While I was on the phone with animal control they demanded photographic evidence of the situation. Because I was not able to comply due to this design flaw the raindeer could not be saved thus there will be no more Christmas. Evidence of the intention for the mentioned limitations is the simple fact that the appropriate error messages are programed into the kernel source. However because you fail to include the wireless drivers, the kernel source cannot be utilized to compile a patch for this flaw.
Shame on you HTC.
I should be a prosecutor.
Click to expand...
Click to collapse
omg rotflmao........so basically we really can't fix the hotspot issue or the call issue!!....I'm beginning to not like HTC...and I definitely don't like sgs2...I better start designing my own phone....the N1 never had this kind of BS problems....I used it as hotspot...called...took pictures alll the way down to 0 battery and it was made by HTC...what changed??? I still like my N1 better lol...hopefully next year we'll get
new years resolution dream phone:
720p super amoled PLUS "not pentile" screen
8 or more Mega pixel back side illuminated sensor with a f/2.2 or less and a wide lense camera lense with good optics and good audio quality while recording video.
able to use flash without limitations!!!!!!!!!!!!!!!!!!!!!!!!!
no flash bleed into camera sensor that requires 3 rounds of electrical tape
No screen bleed from the soft buttons
10 hour talk talk battery preferably over 2200 mAMp battery
STOCK ICS with custom amazing camera software like that amaze has now.
NO CARRIER BRANDING NO BLOATWARE. is this so much to ask
a phone that can drill and fill my patients teeth, do root canals and make crowns for them...ok maybe this last one is asking too much.
is this so much to ask???
seansk said:
...is this so much to ask
a phone that can drill and fill my patients teeth, do root canals and make crowns for them... is this so much to ask???
Click to expand...
Click to collapse
Ummm... yes. I believe the best you can do is create a phone with a jackhammer for a vibration mode, shove it in the patients mount and keep calling it. But of course some other people would use it for... inappropriate purposes.
Example from one of SassyBoB's reviews: https://market.android.com/details?...t=W251bGwsMSwyLDEsImNlbml4LmFuZHJvaWQudmJyIl0.
All ICS kernel updates can go here. This is for Entropy, LipShitz, Task and any other who is actually working on the ICS kernel.
If you post here, it will be deleted on the spot so just fair warning...
First!
These are always my latest *unsupported* builds:
i9100 Touchwiz Based Roms: http://www.cheatersedge.org/android/i777/TWzImage.tar
AOSP Based Roms: http://www.cheatersedge.org/android/i777/AOKPzImage.tar
Red5 said:
If you post here, it will be deleted on the spot so just fair warning...
Click to expand...
Click to collapse
Come at me bro!
j/k..
Seriously guys.. No fooling around!
Fenny maybe I missed it but do you have a thread to discuss this tw kernel. So far so good. I had already converted OmegaRom 5.1 with everything and was just waiting on a kernel. So far so good. I am gonna look through my notes on how/where to fix the home haptic feedback but other than that all 4 buttons seem to working perfectly. I have sent a pm to the des of OmegaRom to see if they wanted it ported (help porting it to our phones) but i have heard back from them so far. Will continue playing with it with your kernel and test it out. I have run the OmegaRom for about three days already and have had any issues so testing with your kernel is now upon me. Thanks for your work on this. Rich
Fixed: All keys and home haptic working now, though home haptic seems lighter than the other keys.
Sent from my SGH-I777 using xda premium
Until things are cleaned up better, there aren't going to be threads. There's enough to be done and enough things are still not working right that new threads aren't justified yet.
https://github.com/Entropy512/initramfs_galaxys2_ics
https://github.com/Entropy512/kernel_galaxys2_ics
used to build the attached zImage. If you don't know what to do with a raw zImage, this isn't ready for you yet. Simple as that - there is a lot of things missing (like, don't set any profiles in SetCPU with reduced clock frequencies, bad things will happen) - I still haven't tested flashing zips in CWM. nandroid backup/restore seems to work but no guarantees.
You still need to disable Samsung Noise Reduction or use a hacked Phone.apk along with a hacked /system/usr/keylayout/sec_touchkey.kl (see Hellraiser on github) for it to work in a reasonable way. There's probably a large pile of **** still broken. Don't pester me with bug reports - there's a pile of stuff I KNOW I still need to address.
When I tried the attached patch yesterday, it made the screen wake problem significantly worse. Progress in the wrong direction is still progress, as it gives you an idea where to look. I'm going to investigate this further tonight.
It was an attempt to add the missing GPIO definitions that are in the Gingerbread source tree into the ICS kernel.
Entropy, not stating a fact and you KNOW a heck a lot more than I so take this with a grain of salt. I have been playing with lots of different files on a ported/converted i9100 ICS Rom (Omega Rom 5.1) and used these for the usr files and have seen the screen wake issue. http://db.tt/DUe4afdh Maybe it has nothing to do with these though. I have changed many other things like csc folder, csc other files, many other things also. Also I am using the kernel posted by Fenny if that matters or is much different than yours a I have tested it out yet. I only replied here because one of the files I removed was the gpio file completely as other files inside seemed to have the same configurations. Maybe I am WAY off base here. If you want to try the Rom i converted already to see if anything helps let me know and I will send a link to you. Thanks for all your hard work.
Sent From My KickAss ATT SGS2 SPORTING my CobraRom
Sorry.... went to bed and woke up to 50 more pages on other thread.What company shares network with att that has ICS??
Tap-Tap Talking
You know... if this thread is no posting allowed, and not stickied, it is just going to get BURIED.
Sent from my GT-I9100 using XDA
Better off doing how its being done... if use another developers ... you just mirror same issues...if build yourself you know whats what.
Tap-Tap Talking
Entropy512 said:
When I tried the attached patch yesterday, it made the screen wake problem significantly worse. Progress in the wrong direction is still progress, as it gives you an idea where to look. I'm going to investigate this further tonight.
It was an attempt to add the missing GPIO definitions that are in the Gingerbread source tree into the ICS kernel.
Click to expand...
Click to collapse
Isn't 4.0 a total new build from Sammy? Honestly.... from what I'm looking at...I don't see ginger GPIO being compatible..but should be if all they used was duct-tape and staples to parse another kernal together.I'm buying a laptop. You guys use sdk? Entropy..what program are you using for kernal popping? Give me area you want help....will do
Tap-Tap Talking
LipShitz said:
Sorry.... went to bed and woke up to 50 more pages on other thread.What company shares network with att that has ICS??
Tap-Tap Talking
Click to expand...
Click to collapse
AT&T does not share its network with anyone - unless you're thinking of the MVNOs that use their network, which are almost exclusively using low-end prepaid devices.
The I777 is AT&T-unique - no other carrier uses it. Everyone else uses I9100 variants. (Except the Korean carriers, which have the M250S/K/L, and NTT DoCoMo, which has an I9100 variant branded as SC-02 I believe.)
Entropy512 said:
AT&T does not share its network with anyone - unless you're thinking of the MVNOs that use their network, which are almost exclusively using low-end prepaid devices.
The I777 is AT&T-unique - no other carrier uses it. Everyone else uses I9100 variants. (Except the Korean carriers, which have the M250S/K/L, and NTT DoCoMo, which has an I9100 variant branded as SC-02 I believe.)
Click to expand...
Click to collapse
Sc-02-i9100....this is what we have source? I want to run another of att dual core. I made a call to my work for that persons contact info. If I get..(I will) it will help in big way. If you read my first 2 pm's from other day...you know what I mean.
Tap-Tap Talking
Fenny said:
You know... if this thread is no posting allowed, and not stickied, it is just going to get BURIED.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Ill make sure it stays at the top.
LipShitz said:
Sc-02-i9100....this is what we have source? I want to run another of att dual core. I made a call to my work for that persons contact info. If I get..(I will) it will help in big way. If you read my first 2 pm's from other day...you know what I mean.
Tap-Tap Talking
Click to expand...
Click to collapse
I'll catch up on your PMs soon.
I think I've found the screen wake bug: I misread the #ifdefs in the Gingerbread kernel, and realized they unmap the HOME key GPIO.
There was no such unmapping in the ICS kernel - so the GPIO was left mapped to HOME but left floating, which explains both random wakes and spurious HOME presses. It's also why the patch I posted this morning caused guaranteed screen wakes on resume - GPX3(5) is the HOME GPIO and was set to pulldown by that patch - it's an active-low GPIO.
Attached is a test kernel zImage and two patches - if these solve screen wake for those experiencing it, I'll push the patches to github and probably release the first Daily Driver ICS tonight even though I still haven't fixed SetCPU hangs.
This kernel is for Touchwizz firmwares only - if it solves the problem for everyone I'll work with the CM9 maintainers on integrating the attached patches, which apply to the current state of my github repo.
Let me know when you get to test point. Shoot it over if you want.
I have started writing a new program that will enable you to do parcing of 2 total diff Kernals,full factory and custom ROMs., yank out APK's and cook me dinner. What It will prob be 2gig in size..will streamline it. But when done--- WE WILL RULE THE WORLD!.. yea ok.
Tap-Tap Talking
Here is a kernel I compiled to work with MIUIv4 for this weeks update 2.3.23:
http://www.mediafire.com/?5bm1l4t1bmbd8bm
All good... little laggy(prob CPU hang) 200-1200 CPU set? No wake issue yet. I'm on 1.5 hours.
Tap-Tap Talking
I restarted phone and stuck on startup logo(samsung bla bla bla) i need to hook it up to laptop and flash it. Will not go into cwm with power and both volume. Im on my infuse.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Sorry Double Post
Testing done. Source up. Happy picking.
I wrote this for the Sensation and mdeejay did harass me to port it over to the shooteru (I don't own an EVO), well:
Challenge accepted!
Download: Don't click me anymore...
Source: Click me...
I ported my work from the Sensation and modified it quite extensively to work with the atmel driver instead of the cy8c one from the Sensation.
The first version had some problem with the capacitive leds (null pointer dereference ), thanks to the logs of @teihoata this could be fixed.
bricked.de
Hi,
Let me clarify that I am not a DEVELOPER, or LOGGER or TESTER of any sorts
I just want to put forth that a similiar thing called Slide2Wake, which was developed by bponury on our XDA forums was released somewhere ealrier this year. It was actually coded much earlier but wasnt released. I remember coming across it during Kamma's kernel time, which is in October or November 2011.
This is his thread ;
http://forum.ponury.net/viewtopic.php?f=14&t=354&sid=837533d86c47eac9495375908d131899
In his thread, he allowed us to port in certain kernel module, which allows any kernel developer to include. This inclusion will allow us to do "Slide 2 wake"
Once the kernel code is included, users of the HTC EVO3D are to download an app called ;
Ponury Gesture Mod (currently version 1.4)
https://play.google.com/store/apps/details?id=net.ponury.pgm&hl=en
This app allows an interface to configure the "Slide 2 wake" feature, which if you watch his Youtube here;
http://www.youtube.com/watch?v=GswWnvxuCXk
You will find out its the similiar thing with your "Sweep 2 wake" function
However, Ponury's one is kernel module and app, based only for EVO3D.
The app allows you to turn it off, and on, and separately if you only need 1 part of it to work.
Some kernels currently that definitely support it are Leedroid's latest, Anthrax latest and Anryl's latest, while some other kernels like Unity3b by Mdeejay doesnt
I noticed capacitive buttons LED bugs exist, depending on the ROM and the Tweaks.apk settings and Autobrightness, etc. Overall, it works almost most of the time.
What I would like to know is how different is your "Sweep 2 wake" compared to "Slide 2 wake" for us to give this a whirl ?
I remember battery drain issues with screen off present due to the fact that the screen is consistently trying to register touches in a particular fashion, and if you touch the screen for 30 minutes non stop (like I did once in a meeting), these touches are still being recorded and using battery. The screen didnt turn ON (because I was randomly touching everywhere else besides the buttons), yet when I checked some logs and task monitors, it showed that I kept interacting with the kernel and CPU was busy. This did drain battery. The only way it did drain actually.
Apologize in advance for this post if it messes up your thread, and effort.
I can dwell into the testing of this , once some things are clarified
Much thanks for your effort, and Mdeejay of course
jcsy said:
Hi,
Let me clarify that I am not a DEVELOPER, or LOGGER or TESTER of any sorts
I just want to put forth that a similiar thing called Slide2Wake, which was developed by bponury on our XDA forums was released somewhere ealrier this year. It was actually coded much earlier but wasnt released. I remember coming across it during Kamma's kernel time, which is in October or November 2011.
This is his thread ;
http://forum.ponury.net/viewtopic.php?f=14&t=354&sid=837533d86c47eac9495375908d131899
In his thread, he allowed us to port in certain kernel module, which allows any kernel developer to include. This inclusion will allow us to do "Slide 2 wake"
Once the kernel code is included, users of the HTC EVO3D are to download an app called ;
Ponury Gesture Mod (currently version 1.4)
https://play.google.com/store/apps/details?id=net.ponury.pgm&hl=en
This app allows an interface to configure the "Slide 2 wake" feature, which if you watch his Youtube here;
http://www.youtube.com/watch?v=GswWnvxuCXk
You will find out its the similiar thing with your "Sweep 2 wake" function
However, Ponury's one is kernel module and app, based only for EVO3D.
The app allows you to turn it off, and on, and separately if you only need 1 part of it to work.
Some kernels currently that definitely support it are Leedroid's latest, Anthrax latest and Anryl's latest, while some other kernels like Unity3b by Mdeejay doesnt
I noticed capacitive buttons LED bugs exist, depending on the ROM and the Tweaks.apk settings and Autobrightness, etc. Overall, it works almost most of the time.
What I would like to know is how different is your "Sweep 2 wake" compared to "Slide 2 wake" for us to give this a whirl ?
I remember battery drain issues with screen off present due to the fact that the screen is consistently trying to register touches in a particular fashion, and if you touch the screen for 30 minutes non stop (like I did once in a meeting), these touches are still being recorded and using battery. The screen didnt turn ON (because I was randomly touching everywhere else besides the buttons), yet when I checked some logs and task monitors, it showed that I kept interacting with the kernel and CPU was busy. This did drain battery. The only way it did drain actually.
Apologize in advance for this post if it messes up your thread, and effort.
I can dwell into the testing of this , once some things are clarified
Much thanks for your effort, and Mdeejay of course
Click to expand...
Click to collapse
Yes, and since we never saw the source of the slide2wake and it was made into a money making machine, I wrote it myself from scratch and opensource
It completely works with interrupts, meaning: As long as you don't constantly touch your screen with capacitive material (like your finger) there will be no additional battery drain and the phone will sleep as usual.
Additionally this is completely kernel side, so no other apps or anything else "bloating" is required. (and is has a on/off switch)
This also lights up the capacitive buttons as soon as you start sweeping so that you can see the buttons in total darkness. (not shown in the video because it was not in there at that time)
A lot of bugfixes and work went into the sensation version and I don#t expect anything else to be needed here. So it is more than likely that the zImage above will not even work remotely like what I just described.
It's great.
Chad had ported showp's mod to the CDMA evo 3d, but removed it - worked great while it lasted.
Testing done, source is up, op edited. Happy picking.
Awesome work!
How can I test this ? I am using anryl's kernel. Can the zImage be integrated somehow ?. I am not an expert to go into source code territory
sdeft said:
How can I test this ? I am using anryl's kernel. Can the zImage be integrated somehow ?. I am not an expert to go into source code territory
Click to expand...
Click to collapse
Code:
adb reboot-bootloader
fastboot boot C:\Path\to\shooter_sweep2wake_zImage_v2
This will only boot the kernel once, a reboot will reset it to your installed kernel and since there are no modules delivered, wifi will be broken.
is it safe or will brick my phone ?
sdeft said:
is it safe or will brick my phone ?
Click to expand...
Click to collapse
This is a dev thread, though this should be safe there will be no guarantee. Just like any other kernel in the whole Dev section.
I think, this is very them same as slide2wake.
The bad think on slide2wake was, that the touch interface was always online, what resulted in a abnormal battery consumption. I hope this is not so in this Mod...
e3d said:
I think, this is very them same as slide2wake.
The bad think on slide2wake was, that the touch interface was always online, what resulted in a abnormal battery consumption. I hope this is not so in this Mod...
Click to expand...
Click to collapse
Didn't the creator say some stuff about how the screen only woke up when it was pressed?
That didn't really work because if you have chinos on and the phone is in your pocket then the screen just stays on :L
Sent from my HTC EVO 3D X515m using Tapatalk 2
e3d said:
I think, this is very them same as slide2wake.
The bad think on slide2wake was, that the touch interface was always online, what resulted in a abnormal battery consumption. I hope this is not so in this Mod...
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showpost.php?p=24951715&postcount=3
thre3aces said:
Didn't the creator say some stuff about how the screen only woke up when it was pressed?
That didn't really work because if you have chinos on and the phone is in your pocket then the screen just stays on :L
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Touchscreen#Capacitive
As long as the cloth is not so thin that you can look through it and it is made out of a non capacitive material there will be no problem. But who does put his/her smartphone in the trouser-pocket without having it in the phones bag? (or: who does not have a bag for his/her 600 Euro++ phone? )
btw, awesome handy-bags: http://www.fitbag.de/
show-p1984 said:
Code:
adb reboot-bootloader
fastboot boot C:\Path\to\shooter_sweep2wake_zImage_v2
This will only boot the kernel once, a reboot will reset it to your installed kernel and since there are no modules delivered, wifi will be broken.
Click to expand...
Click to collapse
I didn't really understand how to install this, can you explain it one more time? Thanks.
crimmylol said:
I didn't really understand how to install this, can you explain it one more time? Thanks.
Click to expand...
Click to collapse
Connect phone to pc and type those commands in cmd(assuming adb and fastboot are in PATH)
Sent from my HTC EVO 3D X515m using Tapatalk 2
pedja1 said:
Connect phone to pc and type those commands in cmd(assuming adb and fastboot are in PATH)
Sent from my HTC EVO 3D X515m using Tapatalk 2
Click to expand...
Click to collapse
Will it replace my kernel or just integrate some modules in it?
upd. It stucked on HTC logo and thats all.
gonna wait for this till i see a succesfull flash, idea is great tough..
phikal said:
gonna wait for this till i see a succesfull flash, idea is great tough..
Click to expand...
Click to collapse
This is not meant as a release, it was meant as a development post to help getting debug output for a port (since I don't own the device). I gathered enough debug output to fix up the remaining issues, mdeejay confirmed that it works on his phone flawless and I put up the source. Because I don't own an EVO and I only develop for devices I own, I will not maintain a separate kernel. You should be able to get this sweep2wake port @ mdeejays kernels soon.
As long as the cloth is not so thin that you can look through it and it is made out of a non capacitive material there will be no problem. But who does put his/her smartphone in the trouser-pocket without having it in the phones bag? (or: who does not have a bag for his/her 600 Euro++ phone? )
http://www.fitbag.de/[/QUOTE]
I believe most people only have a case rather than a bag. With the case on, the surface of the phone (screen + capacitive buttons) are still exposed. I'm just wondering if the heat in the pocket will still activate the buttons somehow.
I have tried the slide2wake (ponury gesture mod) myself, and it drains battery alot, even when the phone is out of the pocket.