Related
I've had this issue since the update to ED01 (or maybe before, I can't remember). Anyway it's darn annoying. I froze the screenshot apk to keep the screenshots from happening but there is still the issue with random back/return button presses. Sometimes it's the home key. Sometimes the search key will long-press and cause voice search to come up. It's mostly the return/back key.
I've had this problem on two Fascinates (the modem died on my first one and was replaced about a month ago). It happened with ED05 and it is now happening (although less frequently) with PWGB EH09 ROM v2.0b3 running ED05 modem. My daughters fascinate was having the same problem on stock ED05.
I've searched through several forums and it seems that lots of people have the same or similar symptoms with the fascinate/captivate as well as with the Nexus S.
I see that google tracked it as a problem earlier in the year and claimed to be working the issue and had a fix that was supposed to be rolled out. Never happened.
I think I've narrowed it down to only happening when the phone is using 3G data.
I'd like to locate and fix the problem but I could use some help getting started. For starters, I'd like to get a development environment set up and running so that I can build and test kernels. I can do this on my own but if someone could guide me so that I don't have to go through that learning curve, it would be appreciated.
My first thought is that it's a driver issue. In the source code there's a folder under src/kernel/drivers named "input" that has a bunch of drivers. Does anyone know which driver is used for this phone?
Thanks,
Dale
UPDATE: 15 Mar 2012:
I added a 100pf capacitor to the interrupt line on the cypress touchkey chip today. Everything works fine now. dmesg shows that I'm no longer getting any false interrupts. I downloaded a 6meg file over 3G and had zero false interrupts. Without the cap there would have been at least a couple of hundred (I use dmesg to check for false interrupts since I have printk statements in my code). I'll keep testing but I think this is it. I'll try to get some pics of the tack on showing where I added the cap. It's some tiny sh-t to work on. I had to do the soldering under a microscope. It was not easy. The cap I put on is a 100pf 50v X7R I bought from Digikey. Digikey part number 445-6856-1-ND. I got a 100 of them for <$6 with shipping.
I'll go back to the driver and remove the software fixes to see if the hardware fix takes care of the problem completely.
The parts are $0.028 each if you buy a hundred. They're less than a penny if you buy thousands. Seems a shame that Samsung couldn't pony up an extra penny to keep this problem from happening in the first place.
For those of you who don't want to crack your phone open, there's still the software (read: duct tape) fix.
Here's a link to the thread showing the hardware mod http://forum.xda-developers.com/showthread.php?p=23725671#post23725671
Yeah a lot of people have tried to fix this but nothing has ever worked. It's a well-known issue.
sageDieu said:
Yeah a lot of people have tried to fix this but nothing has ever worked. It's a well-known issue.
Click to expand...
Click to collapse
Yeah, that's why I'd like to try to fix the problem. Not to dismiss the skills of the other people who have tried, but I'm pretty good at finding bugs in hardware.
Well more power to ya, if you fix it then you will make a LOT of people very happy. You should absolutely get in contact with some developers of kernels (jt1134, sixstringsg, Tk-Glitch, sswek2, etc) if you have any ideas or get anything fixed. I'm sure they will be glad to help you out with the issue and use any of your changes in their kernels.
i have a SGS I9000. my problem is phantom presses of menu and back button. tried flashing to stock firmware etr (original was xeu). installed ics. all with no result. FINALLY found that it occurs only when using packet data (edge) we dont have 3g yet. i ve tried disabling packet data and using wi-fi and there is no preblem.
the diagnosis finally comes to this - problem related with packet data and may be (most probably be) related to software bug in the touch button firmware.
It only seems to happen to me at my house, which is in a low signal area. I'm betting it is buried somewhere in the tower switching code, as my phone switches towers constantly at home.
Sent from my SCH-I500
Yes the problem only seems to occur for me when on 3g and not wifi. I've verified this with the three other fascinates in my house. I'm digging through the interrupt routines now using the kgb kernel source.
Does anyone know which interrupt line on the processor the cypress touchkey device is connected to?
I'm almost ready to break open the phone and start probing with an o'scope.
electric bill said:
Yes the problem only seems to occur for me when on 3g and not wifi. I've verified this with the three other fascinates in my house. I'm digging through the interrupt routines now using the kgb kernel source.
Does anyone know which interrupt line on the processor the cypress touchkey device is connected to?
I'm almost ready to break open the phone and start probing with an o'scope.
Click to expand...
Click to collapse
Hey Bill (I'm also a Bill, heh) :
You'll probably want to check out the changes I did for the V13.1 Glitch kernel. They seem to have at least severely limited the phantom keypresses. I did find some GPIO pins that were configured differently by the dpram driver and the mach-aries.c gpio (and gpio while sleeping) settings, and making those match up seemed to help a lot.
I'm an embedded guy, but more on the software side. I don't particularly want to tear my phone apart and hit it with a scope, but hey .. if you do that and find anything, go for it!
FYI, I was able to determine that the IRQ number used for the cypress-touchkey driver, and the one that's firing during the phantom key events, is IRQ 334 (0x14E). Without having a schematic to look at, though, I wasn't able to figure out what might be causing it to fire, nor even begin to guess why it has something to do with poor signal strength.
Anyway .. I've been beating my head against this problem for a long time .. so if there's anything else you'd like to pick my brain about, let me know.
Downgrade
I have found that the only thing that works is to downgrade. I am however through uscellular so my phone is the mesmerize. I tried talking to a representative about my problem but all they would say is to upgrade. After multiple tries and different methods I downgraded to DI14 from EH09 and I have not had one problem since. Besides one with random menu flashes but it turned out to be the application Zedge. Hope this helps. If not at least I can say I tried.
ssewk2x said:
Hey Bill (I'm also a Bill, heh) :
You'll probably want to check out the changes I did for the V13.1 Glitch kernel. They seem to have at least severely limited the phantom keypresses. I did find some GPIO pins that were configured differently by the dpram driver and the mach-aries.c gpio (and gpio while sleeping) settings, and making those match up seemed to help a lot.
I'm an embedded guy, but more on the software side. I don't particularly want to tear my phone apart and hit it with a scope, but hey .. if you do that and find anything, go for it!
FYI, I was able to determine that the IRQ number used for the cypress-touchkey driver, and the one that's firing during the phantom key events, is IRQ 334 (0x14E). Without having a schematic to look at, though, I wasn't able to figure out what might be causing it to fire, nor even begin to guess why it has something to do with poor signal strength.
Anyway .. I've been beating my head against this problem for a long time .. so if there's anything else you'd like to pick my brain about, let me know.
Click to expand...
Click to collapse
What? _I_ found out that it is interrupt 334! )
Sent from my SCH-I500 using Tapatalk
electric bill said:
What? _I_ found out that it is interrupt 334! )
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Yes, yes you did, lol. And you're probably going to end up fixing the whole thing before i get a chance to look at it again, lol.
ssewk2x said:
Yes, yes you did, lol. And you're probably going to end up fixing the whole thing before i get a chance to look at it again, lol.
Click to expand...
Click to collapse
I've been testing the code for about a day. I added the int test to the interrupt handler just now and I'll test for awhile. I'll prob also put it on my daughters phone since she uses hers about 10x what I do.
Excellent. You're welcome to drop by the glitch kernel thread, btw. I've got some folks testing there with good results so far.
Superclean Rom has screenshot removed. Also Geewiz 2.4.2 has a mod to remove the screenshot, just flash this in recovery:
http://db.tt/xERensX3
It happens when you have a low signal. It's was so annoying but no longer have that issue.
Keep me Fascinated.
It's not just the screenshot that's annoying. When using navigation, the phone will keep saying "this will end the navigation" as if the back button keeps getting pressed. Sometimes the menu comes up as well. Really annoying and kind of dangerous to have to keep hitting cancel while driving. Removing the screenshot app will not fix this. I'm really hoping someone finds a true fix for this. Otherwise I'm getting a new phone soon.
Sent from my SCH-I500 using XDA App
SnrSuave said:
It's not just the screenshot that's annoying. When using navigation, the phone will keep saying "this will end the navigation" as if the back button keeps getting pressed. Sometimes the menu comes up as well. Really annoying and kind of dangerous to have to keep hitting cancel while driving. Removing the screenshot app will not fix this. I'm really hoping someone finds a true fix for this. Otherwise I'm getting a new phone soon.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I actually just re-enabled screenshot on my phone. The glitch kernel ( http://forum.xda-developers.com/showthread.php?t=1252871 ) has a fix that they're testing that seems to work pretty good. I'm not sure if it's in their release or just in testing. I think comradesven is putting the code into the kgb kernel too http://forum.xda-developers.com/showthread.php?t=1364912
I've been running my own butchered up kgb kernel for a few days with the fix and it seems to help quite a bit.
electric bill said:
I've had this issue since the update to ED01 (or maybe before, I can't remember). Anyway it's darn annoying. I froze the screenshot apk to keep the screenshots from happening but there is still the issue with random back/return button presses. Sometimes it's the home key. Sometimes the search key will long-press and cause voice search to come up. It's mostly the return/back key.
I've had this problem on two Fascinates (the modem died on my first one and was replaced about a month ago). It happened with ED05 and it is now happening (although less frequently) with PWGB EH09 ROM v2.0b3 running ED05 modem. My daughters fascinate was having the same problem on stock ED05.
I've searched through several forums and it seems that lots of people have the same or similar symptoms with the fascinate/captivate as well as with the Nexus S.
I see that google tracked it as a problem earlier in the year and claimed to be working the issue and had a fix that was supposed to be rolled out. Never happened.
I think I've narrowed it down to only happening when the phone is using 3G data.
I'd like to locate and fix the problem but I could use some help getting started. For starters, I'd like to get a development environment set up and running so that I can build and test kernels. I can do this on my own but if someone could guide me so that I don't have to go through that learning curve, it would be appreciated.
My first thought is that it's a driver issue. In the source code there's a folder under src/kernel/drivers named "input" that has a bunch of drivers. Does anyone know which driver is used for this phone?
Thanks,
Dale
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
I had the same problem...I went to big red and exchanged my phone...well they actually sent me a refurb... this was last week
electric bill said:
I actually just re-enabled screenshot on my phone. The glitch kernel ( http://forum.xda-developers.com/showthread.php?t=1252871 ) has a fix that they're testing that seems to work pretty good. I'm not sure if it's in their release or just in testing. I think comradesven is putting the code into the kgb kernel too http://forum.xda-developers.com/showthread.php?t=1364912
I've been running my own butchered up kgb kernel for a few days with the fix and it seems to help quite a bit.
Click to expand...
Click to collapse
Thanks all u guys. I 'd really appreciate if u could find a standalone fix for this issue i.e. no modded kernel only the touchkey fix. Thanks again.
th3b3 said:
Sent from my SCH-I500 using XDA App
I had the same problem...I went to big red and exchanged my phone...well they actually sent me a refurb... this was last week
Click to expand...
Click to collapse
yeah, I'm on my third phone. there's been some speculation that phones built early (ie when they just started making them) don't have the problem. the data code on mine is 08/05/2011.
dff_jx said:
Thanks all u guys. I 'd really appreciate if u could find a standalone fix for this issue i.e. no modded kernel only the touchkey fix. Thanks again.
Click to expand...
Click to collapse
technically if we change the driver code, which is in the kernel then it's been modded...
If you want to run fully stock ROM and see this problem go away then I think you can add a 120pf cap from the interrupt pin on the cypress chip to ground. I haven't tried it yet but I'm going to as soon as I get done testing the s/w fixes.
Hi, _n0p_ i have tested DSC 0.7b1 and a few minutes ago installed 0.7b2;
there is not a problem about wifi or bluetooth (i have never seen a problem about bluetooth with any of the DSC roms).
Both of them are very stable and the battery life is enough.
I am using Launcher Pro,i am not using any app for wifi (except wifi reassociate coming with DSC roms,but never use or activate it)
Thank you for everything.
it's great news mate but don't open a new thread every time, it will add a lot of unnecessary clutter to the forum.. reply in the dsc's thread or via PM if need be
He's got less than ten posts as of when I write this so he can't post in the DSC thread.
_n0p_
Led activation in 0.7b2 DSConfig Tool doesn't work.
Thank you, fixed.
Thank you Sergei,i installed immediately and i am testing now.
Hi Sergei,there is not bluetooth problem with DSC roms starting from 0.6b, i constantly use bluetooth headphone with DSC roms.
I also cannot post in the development thread.
My question is, is it possible to remove the vibration from reboot/shut down system menu? I noticed I have no vibration when using reboot from the latest dsconfig app.
I find the vibrate often disturbs my other half when fiddling with my streak in the middle of the night.
pjg_pigeon said:
I also cannot post in the development thread.
My question is, is it possible to remove the vibration from reboot/shut down system menu? I noticed I have no vibration when using reboot from the latest dsconfig app.
I find the vibrate often disturbs my other half when fiddling with my streak in the middle of the night.
Click to expand...
Click to collapse
Funny my wife says the same thing.
Sent from my Dell Streak using xda premium
No probs, i'll remove it. But it will affect shutdown too.
In reply to your question in dev forum.
"Also, i've found a method that can keep buttons lit even in screen-off state, but will require slightly more battery (1-5%). Do you need it?"
-----------
I find that your current version already has this facility, you can either leave buttons on or off by how you turn your screen off?
Current script cannot really keep buttons lit in screen-off state, it's just a side effect.
Anyway, I plan to release pre-3 tomorrow, and wanna hear about apps in rom to me non-system.
_n0p_ said:
Thank you, fixed.
Click to expand...
Click to collapse
please is ussd working on this rom
No. USSD doesn't work on any Gingerbread ROM, not even stock 407. To the best of my recollection, the code for USSD support simply isn't present in the ROM because Olleh KT doesn't use USSD codes.
How stable is this Rom because i am yet to install it
DSC The most stable gingerbread rom for streak
Sent from the SuperStreak! ;-)
DSC is simply the best!
ussd code not working unfortunately...i cant recharge my acc or activate my internet plans
hi there _n0p_
DSC is one great development i had for the streak, but while using the NextVid app, none of the videos play... but i never had this issue on other custom streak roms...
godson2000 said:
ussd code not working unfortunately...i cant recharge my acc or activate my internet plans
Click to expand...
Click to collapse
This is a common issue for all the Gingerbread ROMs, including the stock ROM. If you want USSD codes, for now you have to go back to a Froyo ROM.
CyanogenMod 7 for Motorola Sage
Status CyanogenMod 7.2 RC0 (17.03.2012)
Changelogs:
Code:
[B]2012.05.26[/B]
fixed the GPS icon in the statebar
added some moudle to fixed some error
replace the radio,and test for the 3G problem,only test now,it may not work
OC fixed,you may need the touch bootmenu to open it
some other problem that I may not remember
[B]2012.04.09[/B]
fixed the LED
fixed the camera
fixed the GPS but still not show the icon in the statebar
fixed the keyboard lights
fixed some small bugs
The 3G problem I may not know how to fixed,because the 800/1900 in China is EDGE.My phone worked on EDGE well.
[B]2012.03.17[/B]
fixed the sensors problem,the ProximitySensor and LightsSensor now can worked!
fixed the audio player problem
add the H.264 endoced,now it can play 720P without OC
The GPS can not work because it miss the location provider
The camera can work well but the video must turn to "Low" to work
Keyboard Light must setup in "Setting-CMSetting"to turn on
any other problem that i may not remenber
INSTRUCTIONS:
1. Copy *.zip to sdcard
2. Reboot your device in BootMenu/ClockWork
3. WIPE (wipe data/factory reset + wipe cache partition)
4. Install the *zip
5. Reboot
Sources on github:
https://github.com/MagicDevTeam
Download:
http://www.591fan.com/thread-6633-1-1.html
http://115.com/file/bej5e6oa#
Latest Google APPS
Sorry for my poor English!
Well... I'd try it... but the language barrier is just too much for me
Sent from my MB508 using Tapatalk
http://115.com/file/bew8lehp#
Filpside_CM7预览版.zip
This is the download link.you will like it.
ok... your download link works... but it only gets thru about 30% before it drops off
so i can't test it if i can't get it downloaded
it is just a test rom and i testing it for other people in China.you will download it soon when i fixed the sensors and the MP3 player,also the camera.
Nice work! I think I'm going to give up on being a ROM dev haha... nothing wants to work for me
Maybe I'll play around with ICS on it to keep me busy
I dropped in my sensors.sage.so into your ROM and the sensors worked great (I think.. rotation worked)
I used the libsensors that came in the jordan (Defy) device tree if that helps.. (had to change LOCAL_MODULE from sensors.jordan to sensors.sage in Android.mk for it to build)
If you're OK with it, I can upload it to a more world-friendly site (probably MediaFire )
Hi!
Thanks WinSuk for take time to test and help, please dont give up at all with the testing process, so, not many of us may have enough knowledge to really help with this, and also many of us, we are sure and gratefull, that Laidaxin is kind doing it best according with the time that he kind may offer to develop, for all people that use the FlipSide, the CM7 version that for sure it the BIGGEST new that may happen to the FlipSide Forum in long long time...
So, Thanks to Laidaxin, WinSuk, ringfool and any other one that may join to help to make the first ROM for FlipSide a success and tested.
Best Regards to all and please keep the good work!
WinSuk said:
Nice work! I think I'm going to give up on being a ROM dev haha... nothing wants to work for me
Maybe I'll play around with ICS on it to keep me busy
I dropped in my sensors.sage.so into your ROM and the sensors worked great (I think.. rotation worked)
I used the libsensors that came in the jordan (Defy) device tree if that helps.. (had to change LOCAL_MODULE from sensors.jordan to sensors.sage in Android.mk for it to build)
If you're OK with it, I can upload it to a more world-friendly site (probably MediaFire )
Click to expand...
Click to collapse
Of couse!
We should built it together for filpside,one man can not do it well for this job.the other man that i want to say thanks is the wanggjghost,he help me to do it well.
if you upload you file,i will soon to fixed it .
So... i finally got the 2nd init installer to work...
and i got cm7 installed...
my findings are... the accelerometer does not work... meaning the screen doesn't change orientation when you turn the phone...
and
the telephone dials out... or rings when called... however... when it attempts to connect... it reboots the phone...
and
the camera is still broken
and since i don't really know that much about it... i don't know how to fix it...
hopefully one of you guys that are better at this than me can come up with a fix...
i did get wifi to find my network... though i couldn't connect cuz i don't know the password (i use the push button method normally)
it looks so pretty... and runs so smooth...
if there is anything i can do to make your lives easier on this... just lemme know...
my phone... even though its my only one... is ready for testing...
i don't care about sbf flashes... i do them once in a while just cuz i am a glutton for punishment
ok, this seems fine by now... well I am not a dev so could not direct help, but try by post several threads in other forums in order to try to call other FlipSide users and may be Devs that may help to set this Rom to full.
Hope that lucky we may get some additional help to come.
Best regards and please keep the good work.
Well... I tried your new release...
And everything works... except the phone for me
I can't call out... nor can I receive phone calls...
When I try... it reboots the phone...
That is the only thing keeping this from being my everyday ROM
Sent from my MB508 using Tapatalk
rignfool said:
Well... I tried your new release...
And everything works... except the phone for me
I can't call out... nor can I receive phone calls...
When I try... it reboots the phone...
That is the only thing keeping this from being my everyday ROM
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
i was having the same problem as well, mine included the market place too since i installed gapps... i kept messing around with different settings and finally found a solution...
in the settings under wireless and networks go to mobile network settings and change the network preferences to "gsm only" for some reason this beta version doesnt like wcdma yet... which kinda sucks cause you can only get edge that way and no hspda or 3g.. but i was able to make phone calls and download apps after changing that setting..
on another note everything works AWESOME the only problem other than that that ive had is when i changed my ringtones from the default to a custom mp3 or something other than what it comes set at default it doesnt ring anymore when i receive texts or calls... but vibrate mode works just fine which doesnt bother me for now! I'm just so excited to finally see some development on such a neglected device.. i was started ti lose hope and was just gonna let the phone meet the brick wall... i always thought it was odd that nothing was going on with this phone when its more powerful than the original Motorola Droid which was my first android device and its seeing ICS ports... hmm.. ICS ports just something for you guys to chew on.. i will keep playing with stuff on this beta and let you guys know if i find any other bugs!!!!
KEEP UP THE AWESOME WORK!!!!!!
I have been in contact with laidaxin via pm... he says he knows what's wrong and is working on it...
Now if we could only get CWM to unmount system....
Sent from my MB508 using Tapatalk
Is it bad that I obsessively check this forum for laidaxin's next release?
Sent from my MB508 using Tapatalk
rignfool said:
Is it bad that I obsessively check this forum for laidaxin's next release?
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
lmao no.. i've been doing the exact same thing... im OBSESSED
You guys aren't the only ones... The lack of dev support is honestly the only thing I dislike about the flipside, and it seems like we're well on the way to having a usable rom.
Lol!!!... :-D
Yep... You are not alone, same by me.... I evolve to really appreciate my Flip, since by now is long time that it is serving me faithfully.... really wish and deserve a much better rom for so reliable hardware.
Best regards!
To hell with it...
I'm gonna stick with CM7 for now...
Let's see how many reboots I get today
Sent from my Filpside using Tapatalk
rignfool said:
To hell with it...
I'm gonna stick with CM7 for now...
Let's see how many reboots I get today
Sent from my Filpside using Tapatalk
Click to expand...
Click to collapse
If you change the settings how I mentioned prior you won't have any reboots
so...even though op says it's finished...it's not quite there yet, right? No 3g..? Hmmm....
I recently wiped all of my phone (factory+cache) and installed the latest 4.0.3 official update from SAMSUNG.
I also enabled the FULL DISK ENCRYPTION while doing this.
I am now waiting to decrypt it to see if this problem persits if I turn the encryption off.
The problem is that if I leave my phone locked for a few hours/minutes it randomly won't turn on the screen again, when I press the power button.
A hard reboot (holding) fixes this everytime. But this is not a fix, we all know.
It never happened on Gingerbread 2.3.5.
I am beginning to suspect there's a bug in the ICS firmware, although it's 4.0.3, it could slip through.
It's hard to say what's causing the trouble. I have connected the phone to USB now. Waiting for the symptom to show again. I assume I can get a good logcat.
adb shell logcat > logcat.txt
So I'm waiting for an error / event of POWER button at this moment, and will keep logging till it produces the same error again.
Regards,
That's called the black screen of death. It's an ICS bug. For now, rebooting seems to be the only solution ice seen on xda.
Sent from my GT-I9100 using xda premium
a67543210 said:
That's called the black screen of death. It's an ICS bug. For now, rebooting seems to be the only solution ice seen on xda.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I can't believe this ! Is this a SAMSUNG or an Android/ICS problem ?
My version is:
4.0.3
IM74K.XXLPQ
Any custom ROMs addressed this issue or how can you avoid this on ICS? Is the only solution to go back to Gingerbread ?
Hi guys, hope your well.
I am having a similar issue too. I am on Hydrogen AOKP Rom, and I get exactly the same. However, apart from just the blank screen, my phone gets extremely hot too.The only way to get it back on is to remove the battery. Very annoying!!
I cant seem to figure what it is. I have tried to search here on XDA for the resolution but to no avail. Could it be the Kernal? The Modem? Tweaking via SetCPU? or a combination of all? Atleast if I could get pointed to the right direction that'll be a start! lol
Are you guys getting the overheating problem too?
Its a bit like continual posting in the wrong forum nobody knows why ??
jje
rumz82 said:
Hi guys, hope your well.
I am having a similar issue too. I am on Hydrogen AOKP Rom, and I get exactly the same. However, apart from just the blank screen, my phone gets extremely hot too.The only way to get it back on is to remove the battery. Very annoying!!
I cant seem to figure what it is. I have tried to search here on XDA for the resolution but to no avail. Could it be the Kernal? The Modem? Tweaking via SetCPU? or a combination of all? Atleast if I could get pointed to the right direction that'll be a start! lol
Are you guys getting the overheating problem too?
Click to expand...
Click to collapse
No overheating (yet) you can help if you can keep logcatting through usb cable till it lock/standby freezes and your screen won't come on when pressing power ..
Install SDK + Drivers, write in commandprompt:
adb shell logcat > save.txt
Wait for the error / freeze where screen won't come on.
Then paste here or upload somewhere might contain a lead to a solution!
Double - sry - galaxy forgot login
It's a kernel issue. I had exactly the same problem. Flash the latest siyah kernel that should sort it out. I went through 10 different Roms till I worked it out
Sent from my GT-I9100 using XDA
thedadio said:
It's a kernel issue. I had exactly the same problem. Flash the latest siyah kernel that should sort it out. I went through 10 different Roms till I worked it out
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nah!
It's there on all the kernels. I myself am a Siyah user.
I moved back to GB for this weird and terribly serious issue, but that time i didn't know it was a common problem.
This is ICS' best feature for sure.
I really CAN NOT believe how this issue is NOT yet known well and haven't brought in to front line. Google knows about it and yet I haven't seen any official statements about it. How ****in unbelievable or not perhaps? Google way?? Well **** it.
Utter Nonsense. What i wonder is, really, does any Android user actually use the phone but show off only??
I can almost reliably reproduce this problem.
I'm on ICS LP7 stock XEU version. When I have downloads running with Ttorrent, there's an almost 50% chance that the screen will not turn on once it goes to sleep. The phone is not frozen as my downloads continue to run; just that nothing is being shown on the display. If you hold the volume down button you will feel the phone vibrate to tell you it went into silent mode, which means the phone didn't freeze. After about a minute or so if I try again everything will work as normal, until I put the screen to sleep again.
gtcardwhere said:
I can almost reliably reproduce this problem.
I'm on ICS LP7 stock XEU version. When I have downloads running with Ttorrent, there's an almost 50% chance that the screen will not turn on once it goes to sleep. The phone is not frozen as my downloads continue to run; just that nothing is being shown on the display. If you hold the volume down button you will feel the phone vibrate to tell you it went into silent mode, which means the phone didn't freeze. After about a minute or so if I try again everything will work as normal, until I put the screen to sleep again.
Click to expand...
Click to collapse
Do the logcat as I provided the correct command to extract it to a file.
Then do your torrent thing, and make it crash- so we can debug !
Used to happen, since I installed latest hydrog3n-ICS rom (13-05) never had those again!
have you uv your phone so much?
i tried to uv my phone so much, and it can't turn on screen when i lockscreen about 1min
sunshean said:
have you uv your phone so much?
i tried to uv my phone so much, and it can't turn on screen when i lockscreen about 1min
Click to expand...
Click to collapse
uv?
ultra-violet ? is my phone in danger of skincancer ?
dezzadk said:
I recently wiped all of my phone (factory+cache) and installed the latest 4.0.3 official update from SAMSUNG.
I also enabled the FULL DISK ENCRYPTION while doing this.
I am now waiting to decrypt it to see if this problem persits if I turn the encryption off.
The problem is that if I leave my phone locked for a few hours/minutes it randomly won't turn on the screen again, when I press the power button.
A hard reboot (holding) fixes this everytime. But this is not a fix, we all know.
It never happened on Gingerbread 2.3.5.
I am beginning to suspect there's a bug in the ICS firmware, although it's 4.0.3, it could slip through.
It's hard to say what's causing the trouble. I have connected the phone to USB now. Waiting for the symptom to show again. I assume I can get a good logcat.
adb shell logcat > logcat.txt
So I'm waiting for an error / event of POWER button at this moment, and will keep logging till it produces the same error again.
Regards,
Click to expand...
Click to collapse
Hi,
It happened to me as well after the ICS update and I tried to plug the AC charger to see what happens, and surprise...the screen turned on .
It's not a fix (especially when away with no accessories) but it's better than nothing, hope this helps; also you should try plugging the USB cable. Tell me if it helps.
Thanks,
dezzadk said:
uv?
ultra-violet ? is my phone in danger of skincancer ?
Click to expand...
Click to collapse
Haaaaahahah! He means under volting. I don't know if you was serious lol but just saying. I'm on cm9 but don't have this problem :-/.
Sent from my GT-I9100 using xda premium
Yep,I mean under volting, you need to look your kernel, and I think it doesn't work fine because your kernel has under volting so much.
Sent from my GT-I9100 using Tapatalk
Reading around and installing load monitor from play store should fix this until a better solution is found
Sent from my GT-I9100 using Tapatalk 2
Best solution is to stay on GB because is more stable, until ICS gets better cooked!
So I switched to GB from WM65 and found it's pretty slow but usable. I don't have time to switch back to WM65 so I'll stick with GB.
Now, one big issue I have is the phone app (not wifi app, just plain phone). When I dial a number, the screen goes black to prevent pressing the wrong button with your ear etc. Problem is, I can't get back to the screen, meaning I don't have access to the dialpad. Annoying when you're on queue and you need to press a key to get to a menu... like repeat a message on your messagebank for instance.
Second issue, is after the call, the phone is frozen for about a minute or two. Nothing responds. Then it comes back alive.
I haven't found any threads on this, though users seem to complain about wifi calling, which is not my case.
Anyone has seen this ?
Txs.
Can you please tell us which ROM that is?
I know that this issue was fixed, but maybe your ROM is just too old. Or maybe the developer didn't include the fix.
I had this problem with almost every gingerbread build on my HD2.
Im not sure what's causing it, but i fixed this issue by installing screebl lite from play store. While this app enabled, phone would wake up normally after a call in 99.9% of the cases. You should try the same.
Strangely, i don't have any issues on ICS or JB roms.
Marvlesz said:
Can you please tell us which ROM that is?
I know that this issue was fixed, but maybe your ROM is just too old. Or maybe the developer didn't include the fix.
Click to expand...
Click to collapse
Android Version 2.3.7
Baseband Version 15.42.50.11U_2.15.50.14
Kernel Version 2.6.32.15_tytung_gb_r16 [email protected] #292
Build nr GWK74 (nexusHD-Gingerbread V3.3a) DataOnEXT
Got it from this dude http://forum.xda-developers.com/showthread.php?t=905060
So there is a patch ?
Boags said:
Android Version 2.3.7
Baseband Version 15.42.50.11U_2.15.50.14
Kernel Version 2.6.32.15_tytung_gb_r16 [email protected] #292
Build nr GWK74 (nexusHD-Gingerbread V3.3a) DataOnEXT
Got it from this dude http://forum.xda-developers.com/showthread.php?t=905060
So there is a patch ?
Click to expand...
Click to collapse
Okay, I have looked throughout that thread's pages, and it seems that you're not the only one with that problem. So apparently the ROM doesn't have the fix (which is weird, because tytung almost always fixes everything in a rom before moving onto another one).
You're better off changing the ROM, or maybe trying to figure out what is wrong with your device and those who're facing the same issue.
Marvlesz said:
Okay, I have looked throughout that thread's pages, and it seems that you're not the only one with that problem. So apparently the ROM doesn't have the fix (which is weird, because tytung almost always fixes everything in a rom before moving onto another one).
You're better off changing the ROM, or maybe trying to figure out what is wrong with your device and those who're facing the same issue.
Click to expand...
Click to collapse
Thanks Marv, so...no hotfix ? no patch ? just change ROM ? this is silly :|
Boags said:
Thanks Marv, so...no hotfix ? no patch ? just change ROM ? this is silly :|
Click to expand...
Click to collapse
Well, the fix wasn't a flashable zip, it was implemented. It was a problem with the proximity sensor if I recall correctly. And since I don't use this ROM, I can't really help you much.
I tried googling the problem (it's fun, you should try it) and this came up : http://forum.xda-developers.com/showthread.php?t=1376251
Your sensor/screen could be dirty making it hard for the proximity to detect. You can try another non-GB ROM and see if the problem is still present.
I am sorry I can't help.
Marvlesz said:
Well, the fix wasn't a flashable zip, it was implemented. It was a problem with the proximity sensor if I recall correctly. And since I don't use this ROM, I can't really help you much.
I tried googling the problem (it's fun, you should try it) and this came up : http://forum.xda-developers.com/showthread.php?t=1376251
Your sensor/screen could be dirty making it hard for the proximity to detect. You can try another non-GB ROM and see if the problem is still present.
I am sorry I can't help.
Click to expand...
Click to collapse
Right, I'll go with the hypothesis that a dirty screen hinders proximity sensors. That should affect a black screen DURING a call (issue I'm also facing) but that should not affect the phone once the call is terminated, should it ? What I mean is, in my case, when I hang up a call, I can't use my phone for a couple of minutes, until it comes back to life. I will get a new "screen protector" and see what happens in the meantime though.
As for a hotfix, seems odd there is none out there. Thanks for trying.