hi guys i am wondering about that unexplained problem:
some times my SGS I9000 is shutting down!?! i don't know why, by the way my device is "unlocked to work in Algeria" and it was on firmware 2.3.3 BUJVB and now i use 2.3.6 XXJVU
*my device shuts down "sometimes" when i:
-make or answer phone call
-video recording for a time "more then 10 minutes"
-some times just itself
also my device does not want to move apps to USB storage, and is being hot when i use it for a long time "like playing games"
ThAnk you guys, always you are the best in all
trust me bro the ICS that not from sammy it's more stable than sammy rom
give it a try u will really like it and will fined it smoother than sammy rom and faster and now there is more support from dev to ICS
try AOKP with devil kernel very stable and u will never look back to sammy GB
samhawk said:
hi guys i am wondering about that unexplained problem:
some times my SGS I9000 is shutting down!?! i don't know why, by the way my device is "unlocked to work in Algeria" and it was on firmware 2.3.3 BUJVB and now i use 2.3.6 XXJVU
*my device shuts down "sometimes" when i:
-make or answer phone call
-video recording for a time "more then 10 minutes"
-some times just itself
also my device does not want to move apps to USB storage, and is being hot when i use it for a long time "like playing games"
ThAnk you guys, always you are the best in all
Click to expand...
Click to collapse
Only certain apps can be moved to SD. Most apps cannot be. It's up to the developer.
All computers get hot when you run heavy programs on them.
No idea about the shut down problem unfortunately. Typically a factory reset should fix the problem, but that's rather drastic. When did this problem start? Did you install something before it all began?
yahyoh said:
trust me bro the ICS that not from sammy it's more stable than sammy rom
give it a try u will really like it and will fined it smoother than sammy rom and faster and now there is more support from dev to ICS
try AOKP with devil kernel very stable and u will never look back to sammy GB
Click to expand...
Click to collapse
thank you bro
-but i am on JVU 2.3.6 how to get good base befor get in ICS?
-or how to get away from this shet of XXJVU and get in stable ICS?
thank you again
snapper.fishes said:
Only certain apps can be moved to SD. Most apps cannot be. It's up to the developer.
All computers get hot when you run heavy programs on them.
No idea about the shut down problem unfortunately. Typically a factory reset should fix the problem, but that's rather drastic. When did this problem start? Did you install something before it all began?
Click to expand...
Click to collapse
thank you man
i have used 2.3.3 BUJVB for 2 or 3 days and i didn't see any problem, i guess it showed up after i get on JVU 2.3.6. do you think it's going to be a material kinde problems
Hi Guys
I have this problem when i instal different kernel than basic. I can't watch my recorded videos in gallery, but they stops in first second and gallery stops working too.
I still do cache partition, dalwik cache, and than i'm installing kernel
With CM9 and other roms i haven't this problem, but I want this rom without this bug
Thanks, and sorry for my poor english
Edit: I tryed fix, but didn't help
the break of 720 video is always described in the kernel ... read the description of the kernel carefully
I know that's described in versions with bigger mem., but i didn't know that can happen in normal version.. when i asked in other forum, people had no problems with combo Slim ICS+ Semaphore 1.2.2
Yes this is a kernel "feature". The 720p breaking comes free with all bigmem kernels (i think).
I however am running slim 3.9 with devil2 kernel (Devil2_0.94_i9000_CFS_BLN_CMC_20120524)
720p is no problem....
That's i told about. Nobody has problem like me... I don't underestand
the problem is in the kernel....change the kernel and take one that support 720 recording....
i tryed semaphore, devil, mnics, and it didn't work..I don't know which one could work good
And record works good, but i can't play recorded video
you can download the mod that is fixing the 720P break...
http://forum.xda-developers.com/showthread.php?t=1575485
I dont know if it helps, but on my phone with Devil2_0.94 with default settings, playback was broken too. The video opened but after a second or so whatever video app I used, it would just stop.
As I like this kernel very much I didn't want to change.
In this version, Devil2 kernel comes default with standard RAM (378MB) and somehow this was breaking playback.
As usual I went to xl mem setting (391 MB), now everything is fine!
If you're using Devil2 kernel, read the second post of that thread and you will see how to change that setting.
You can download "Scripter" from market and paste the commands into the app to make things easy.
Read the kernel instructions....you need to instal the "s" version!
+ 1
slaphead20 said:
Read the kernel instructions....you need to instal the "s" version!
Click to expand...
Click to collapse
Thank You so much!
I was finding reason everywhere, but i'm blind apparently
Hi guys
A friend of mine has a problem: his Galaxy keeps restarting randomly for no reason, many times in a day while using it.
What is weird: the phone hasn't ever been rooted/flashed with a custom rom, neither updated, always been 100% original. Just a normal usage!
I'm not much into this phone, so i don't know if it's a known issue or what.. but it sounds strange to me, possible hardware problem? Needs to be flashed or rooted? Other?
I've already done a factory reset and now i took off the sd-card to see if it could be it, but i'd appreciate some advices!
Thanks
Try updating it with kies, might help but can't guarantee
if random reboots happens while using too much mobile resources then its normal for galaxy mini like phone
Random Reboots might be device specific or not , It depends.
But you may want to visit the samsung care center in your vicinity area just to be sure about the latter .
Else just flash a new stock Rom via ODIN (not that it would leave your device impure as rooting does ).
yackovsky said:
Try updating it with kies, might help but can't guarantee
Click to expand...
Click to collapse
thousandecibels said:
Random Reboots might be device specific or not , It depends.
But you may want to visit the samsung care center in your vicinity area just to be sure about the latter .
Else just flash a new stock Rom via ODIN (not that it would leave your device impure as rooting does ).
Click to expand...
Click to collapse
Is Froyo the last "official" release or was a Gingerbread leaked/official firmware released? I'll probably try flashing something, don't know yet if a custom rom could solve the problem but still it's a possibility
dheeraj (dhlalit11) said:
if random reboots happens while using too much mobile resources then its normal for galaxy mini like phone
Click to expand...
Click to collapse
With mobile resources you mean 3G/wifi or RAM? By the way in both the cases i don't think it's the problem, since there aren't many apps in background and the only one using internet connection is whatsapp!
Thanks for the replies :good:
Niscap said:
Is Froyo the last "official" release or was a Gingerbread leaked/official firmware released? I'll probably try flashing something, don't know yet if a custom rom could solve the problem but still it's a possibility
With mobile resources you mean 3G/wifi or RAM? By the way in both the cases i don't think it's the problem, since there aren't many apps in background and the only one using internet connection is whatsapp!
Thanks for the replies :good:
Click to expand...
Click to collapse
The last official android update for for sgm was gingerbread based api.
Try flashing the stock gingerbread on the device via odin (google it if you don't know how to.) and then try custom roms.
Also the thing about resources, you already know about our sgm aka lil'g . Its not that powerful as most quad core latest devices boosted by plenty much RAM. So multitask on it wisely.
thousandecibels said:
The last official android update for for sgm was gingerbread based api.
Try flashing the stock gingerbread on the device via odin (google it if you don't know how to.) and then try custom roms.
Also the thing about resources, you already know about our sgm aka lil'g . Its not that powerful as most quad core latest devices boosted by plenty much RAM. So multitask on it wisely.
Click to expand...
Click to collapse
I'll try with gingerbread when i see my friend, thanks! I own a i9000 and flashed pretty much so i know odin and similar stuff, no problem
And yes i tried the mini many times, doesn't have a bunch of ram but still i think it can't be a ram-lack problem since it did the same also after the factory reset, with few apps installed!
Thanks again for the help :good:
Oh, was forgetting: how does the cyano run on the mini? Smooth? Battery killer or ok for everyday use?
Try cm7 by mebitek. Despite its source code is old and official cm7 is way more ahead of it, the mebitek's cm7 relays on battery & performance like a pro..
by resources I mean more ram and CPU usage
background apps ( they don't play big role as they get closed automatically)
running big games (HD one)
etc.
if you have many apps, cut the .android_secure folder and paste it on your computer.. i had this problem with the stock GB 2.3.6.. reboots reboots and reboots!! i pasted the folder in my comp, delete unnecessarily used apps and VOILA! it was running smooth again.. but now i'm using cm7..
I updated to official gingerbread release, then after putting all the (few) apps into phone storage i removed every android-secure file!
I'll see how it goes with this, if the problem remains i'll try a cyano or go directly to the service center
Thanks again for the tips!
There's a known problem for a little amount of Samsung Galaxy S GT-I9000 devices that are getting bluish screen after flashing AOSP Ice Cream Sandwich (4.0.x) and above.
By bluish screen I mean that there's a dark blue color - a blue tint / hue all over the screen.
This bluish screen appears everywhere in the ROM, in the recovery, and even when charging the phone while it's off.
There are videos and screenshots which demonstrates this issue here.
According to @DerTeufel1980 and @pawitp, this issue is caused by the updated framebuffer driver of the Nexus S in the CyanogenMod 9 kernels, and the actual problem is that some devices contain incorrect calibration data.
In this thread I'd like to share the ROMs and apps that I tried in search for the newest and most stable working ROM for problematic devices, and to list useful posts, threads and links.
I hope this thread will help ones with problematic devices, and that it will save them time and effort.
Edit: this issue is fixed by detecting the invalid calibration data and setting sane default values instead.
While this fix is implemented by @pawitp in CyanogenMod 11 ROMs from the cm-11-20140214-NIGHTLY-galaxysmtd.zip ROM and above, not all of the developers implemented it in their ROMs yet.
To know which ROMs we can flash please look at this list.
Ones who are interested might find more information about the fix of this issue here:
This issue is fixed by detecting the invalid calibration data in the CyanogenMod's aries kernel, and setting sane default values instead.
This fix was implemented in the android_kernel_samsung_aries/drivers/video/samsung/s3cfb_tl2796.c file.
The fixed source code can be viewed in:
CyanogenMod's Gerrit Code Review
CyanogenMod's GitHub
In addition, here is a link to the fix subject page in CyanogenMod's Gerrit Code Review.
Note that there was a previous fix, but it caused yellowish screen to users who didn't have the bluish screen.
More information about it can be found in CyanogenMod's Gerrit Code Review in the fixed build subject page and in it's revert page.
I'd like to appreciate @pawitp for being willing to help and solve this issue and for his truly tremendous effort to the community.
If someone is interested to see what ROMs and apps I tried before the fix, and interested in a list useful posts, threads and links that are connected to this issue:
ROMs that I tried (and didn't worked)
stock
Gingerbread 2.3.6 I9000XXJVU with CFROOT 4.3 by @xsenman - working good for us.
Gingerbread 2.3.6 I9000JHJVG# - working good for us.
Gingerbread 2.3.6 I9000XWJWB - working good for us.
AOSP
CyanogenMod
CyanogenMod 7.2.0 (Gingerbread 2.3.7) by @codeworkx - working good for us.
CyanogenMod 9.x (Ice Cream Sandwich 4.0.x) by @pawitp
CyanogenMod 10.x (Jelly Bean 4.1.x and 4.2.x) by @pawitp (links to 10.0.0, 10.1.x, 10.2.x)
Paranoid Android (AOSPA) by @SferaDev
Paranoid Android 3.69 (AOSPA 4.2.2 - JellyBean)
Paranoid Android 3.99 (AOSPA 4.3 - JellyBean)
Paranoid Android 4 beta 3 (AOSPA 4.4.2 - KitKat)
AOSP Jelly Bean 4.2.1 by @pawitp
Google play apps that I tried in order to control the bluish screen (and didn't worked good enough)
Screen Adjuster
Screen Filter
Filter Your Screen - Free!
Related posts and thread by this forum's users who are having the same issue
By @MrCabana
[Q] Samsung Galaxy S i9000B blue screen problem
[Q] Samsung Galaxy S (B) blue screen
[Q] Samsung Galaxy S blue screen error by @kssthomas
[NIGHTLY][ROM][4.0.4][IMM76I] CyanogenMod 9 for Samsung Galaxy S by @HaTeNL
Color Calibration ( Blue tint fix ) - Needs some work though by @-Yaya-
bluish screen? by @djr83
Best CM Colour Settings For Yellow Tinted Screens and Normal Screens by @alb3rtt
YouTube videos which demonstrates this issue
Additional links
Related topics in CyanogenMod Forum
Everything Is Blue
My topics: link 1, link 2
stock ROMs
In this forum
[Tutorial] How to Unbrick, Flash, Downgrade, Root, Update i9000 from Froyo to Kit Kat by @xsenman
[FULL GUIDE][UNBRICK][Root] Flash custom or stock ROMs or kernels [i9000][VIDEO] by @tetakpatak
[Firmwares]Official I9000/I9000M Firmwares collection [Latest: XWJWB, XWJW8, DDJVB] by @[Ramad]
[ROM/KERNEL/MODEM] GT-I9000 - Latest Stock Firmwares - Direct Links - Torrents by @IWillExplain
In external sites
SamMobile
Samsung Updates
modified stock ROMs list @ [GUIDE] Unsure which rom to choose? by @Soryuu
Summarization (note that this was written before there was a fix)
People who are having this issue can use stock ROMs (Gingerbread 2.3.6), CyanogenMod 7.2.0 (Gingerbread 2.3.7), and any AOSP Gingerbread 2.3.7 and below without been affected by this issue.
Replacing the screen digitizer might solve this issue. That did it for @MrCabana as posted here
If you know something that is not summarized here and might solve this issue or help to it somehow, please post it here
Thread's change log
18.02.2014
Added information about the fix of the bluish screen issue.
Changed the thread's topic to [Solved] bluish / blueish screen (blue tint / hue) after flashing AOSP ICS + on I9000.
17.02.2014
Removed invalid link.
15.02.2014
Added tag to the thread's title (there is not enough place for [Solved]).
[*]Updated in the thread that this issue is fixed.
[*]Added a link to videos and screenshots which demonstrates this issue.
[*]Converted profile links with mentions so users will be notified and will be able to comment if they'd like to.
[*]Added proper YouTube tags the the videos can be played directly from the thread.
13.02.2014
Added tag to the thread's title (there is not enough place for [Solved]).
[*]Removed tag from the thread's title since the solution may be temporarily.
[*]Added a note that this issue is being inspected.
[*][*]Added a link to the second fix issue subject page in CyanogenMod's Gerrit Code Review.
12.02.2014
Modified the topic's content.
Added a credit to pawitp for fixing the bluish screen issue.
Added a link to the ROM's build parameters page in CyanogenMod's Dashboard [Jenkins]
Removed tag from the thread's title since the solution caused problems for other devices.
[*]Added a link to the fix revert subject page in CyanogenMod's Gerrit Code Review
11.02.2014
This issue is solved.
Added tag to the thread's title (there is not enough place for [Solved]).
[*]Added information and link to the solution in this main post.
[*]Added links to related topics in CyanogenMod forum.
[*]Added a link to list of ROMs that we can use.
[*]Added a link to the fix subject page in CyanogenMod's Gerrit Code Review.
[*]Modifications
10.02.2014
Created this thread.
Modified the summarization section.
videos and screenshots which demonstrates the bluish / blueish screen issuse
reserved for videos and screenshots which demonstrates this issue.
In the meantime,
YouTube videos which demonstrates this issue
Screenshots that I posted in another post.
List of ROMs that we can flash on I9000 devices with the bluish / blueish screen
AOSP (Android Open Source Project)
CyanogenMod
CyanogenMod 7.2.0 (Gingerbread 2.3.7)
CyanogenMod 11.x (Kit Kat 4.4.x) as long as it's cm-11-20140214-NIGHTLY-galaxysmtd.zip or newer.
Any AOSP ROM based on Gingerbread (2.3.7) and below
Any AOSP ROM in which the bluish screen issue, the s3cfb: tl2796: detect invalid factory calibration data, is fixed.
stock ROMs
In this forum
[Tutorial] How to Unbrick, Flash, Downgrade, Root, Update i9000 from Froyo to Kit Kat by @xsenman
[FULL GUIDE][UNBRICK][Root] Flash custom or stock ROMs or kernels [i9000][VIDEO] by @tetakpatak
By @[Ramad]:
[Firmwares]Official I9000/I9000M Firmwares collection [Latest: XWJWB, XWJW8, DDJVB]
[CWM and Odin][Latest ROM: ZSJW4, XWJW7, XWJW6] Deodexed stock firmware collection
[ROM/KERNEL/MODEM] GT-I9000 - Latest Stock Firmwares - Direct Links - Torrents by @IWillExplain
In external sites
SamMobile
Samsung Updates
modified stock ROMs
[GUIDE] Unsure which rom to choose? by @Soryuu
[FULL GUIDE][UNBRICK][Root] Flash custom or stock ROMs or kernels [i9000][VIDEO] by @tetakpatak
[17.06.2013][INDEX] of all CR`s and Kernels -- JB - ICS - GB - MIUI -- by @driodmaster92
[ROM LIST] Galaxy S I9000 Custom ROM List [06.05.2011] by @splish2010
Notes
@Soryuu posted a great thread which helps choosing a ROM.
@SferaDev announced that he will patch all of the future releases of his ROMs (OmniROM, Paranoid Android and Nameless), so we'll have other great ROMs to flash.
Although the bluish screen issue was fixed by @pawitp in CyanogenMod 11 ROMs, not all of the developers implemented the fix in their ROMs yet.
Therefore if you want to flash a ROM that is not on this list, make sure this issue is fixed in it.
For an easy reference, ask the ROM's developer if he implemented the s3cfb: tl2796: detect invalid factory calibration data fix in his kernel. More information about this fix is available in the first post. If the ROM is indeed suitable for us, please update me so I'll update this ROM in the above list.
Users who know other ROMs who can work for devices with this bluish screen issue, and wish to add them to this list - please notify me (here or in PM) and I'll gladly add them.
Post's change log
08.03.2014
Added information about the bluish screen issue so users will be able to ask specific ROM's developer if the ROM is compatible for us.
Added a note that any AOSP ROM in which the bluish screen issue is fixed is appropriate for us.
18.02.2014
Changed the post's topic to List of ROMs that we can flash on I9000 devices with the bluish / blueish screen.
16.02.2014
Added modified stock ROMs.
Added a note about ROMs that are not on the list.
Added the note about the first CyanogenMod 11 build that we can flash, so we'll know to flash only it or newer.
15.02.2014
Modified CyanogenMod 11 link to link to the official thread.
Converted profile links with mentions so users will be notified and will be able to comment if they'd like to.
Added notes.
12.02.2014
Added a link to SferaDev thread.
Modified this post.
Added AOSP ROMs.
Added modified stock ROMs
Added stock ROMs
11.02.2014
Created this post.
Added a note from SferaDev.
Modified CyanogenMod 11.x link so it'll refer to the information needed to flash it until a newer version will be uploaded.
I saw pawitps commit on gerrit, I'll add it right now. Should be solved on OmniROM, Paranoid Android and Nameless future builds.
See you!
SferaDev said:
I saw pawitps commit on gerrit, I'll add it right now. Should be solved on OmniROM, Paranoid Android and Nameless future builds.
See you!
Click to expand...
Click to collapse
Cool!
Thanks a lot for your great contribution!
Please let us know so I'll update the ROMs list that we can use, so we'll know we have other great ROMs to flash.
List of ROMs that I9000 devices with the blue screen (blue tint/hue) issue can flash
The list of ROMs that I9000 devices with the blue screen (blue tint/hue) issue can flash moved to here.
grrrrrrrrrrrr
Too bad I didn't find this useful post in time before I broke my "uncalibrated screen" and replaced it with a new one.
Glad to know it was NOT a hardware problem, that means my first guess was right.
Thank you very much for the great work, guys !!!!
MrCabana said:
grrrrrrrrrrrr
Too bad I didn't find this useful post in time before I broke my "uncalibrated screen" and replaced it with a new one.
Glad to know it was NOT a hardware problem, that means my first guess was right.
Thank you very much for the great work, guys !!!!
Click to expand...
Click to collapse
Well brother, a lot of credit goes to you since I got a lot of information from you, and it was you who got me realizing that this is a program issue and not a hardware one.
You got me motivated to keep trying and reading and researching, and I'm so glad that pawitp was, and is, willing to help solving this issue.
Thanks a lot!
need4steer said:
Well brother, a lot of credit goes to you since I got a lot of information from you, and it was you who got me realizing that this is a program issue and not a hardware one.
You got me motivated to keep trying and reading and researching, and I'm so glad that pawitp was, and is, willing to help solving this issue.
Thanks a lot!
Click to expand...
Click to collapse
I am glad I was of help for others who face this same problem in the future.
If it's not asking too much, since I got some brain's attention for this device, I have another problem/question to report (I can start another thread if you guys think is necessary).
The problem is ... after replacing the "uncalibrated screen" with a brand new one, the battery indicator stopped working. That means the phone will always report it as 100% charged and won't allow the cable to charge it. I have to wait until it shuts down with no more power and charge it outside the device with a spare charger.
Secondly, the back camera stopped working while front camera is perfect. Both of them are attached with the same connectors to the MOBO, making them just 1 single part. How can one work perfect and the other one just go dead like that?
Thirdly, the USB connection is hard to be stablished with the computer. Even in service mode (i.e. to use odin). It does connect sometimes, but then it freezes even during a ROM update. This is making it impossible for me to mess with it and roll back to Froyo if things go wrong.
Again, those 3 problems CAN be due to malfunctioning hardware, but I believe it 's too much of a coincidence for these 3 unrelated things to happen right after the screen replacement, followed by an update to a nightly build of CyanogenMOD (don't remember exactly which one).
Any help would be greatly appreciated.
MrCabana said:
If it's not asking too much, since I got some brain's attention for this device, I have another problem/question to report (I can start another thread if you guys think is necessary).
Click to expand...
Click to collapse
While I and some other might help you here, it's better for you to open a new thread with appropriate title so others will be able to see your issue and help solve it. In this thread you'll see people who are interested in the bluish screen.
Anyway here are my comment for your device's issues:
MrCabana said:
The problem is ... after replacing the "uncalibrated screen" with a brand new one, the battery indicator stopped working. That means the phone will always report it as 100% charged and won't allow the cable to charge it. I have to wait until it shuts down with no more power and charge it outside the device with a spare charger.
Click to expand...
Click to collapse
Did you try another battery?
Did you tried different ROMs?
What's happening in recovery mode?
MrCabana said:
Secondly, the back camera stopped working while front camera is perfect. Both of them are attached with the same connectors to the MOBO, making them just 1 single part. How can one work perfect and the other one just go dead like that?
Click to expand...
Click to collapse
Perhaps one of the pins in the connector is bad?
Is the connector looking okay for you?
Did you tried different ROMs?
MrCabana said:
Thirdly, the USB connection is hard to be stablished with the computer. Even in service mode (i.e. to use odin). It does connect sometimes, but then it freezes even during a ROM update. This is making it impossible for me to mess with it and roll back to Froyo if things go wrong.
Click to expand...
Click to collapse
Is it happening in the same USB port in your computer?
Is the USB port connected directly to the motherboard, or is it one that is connected to the chassis, and from there to the motherboard?
MrCabana said:
Again, those 3 problems CAN be due to malfunctioning hardware, but I believe it 's too much of a coincidence for these 3 unrelated things to happen right after the screen replacement, followed by an update to a nightly build of CyanogenMOD (don't remember exactly which one).
Click to expand...
Click to collapse
The problems occurred only after the update? If so, revert. (I know that you don't have a USB connection, but you can take your sdcard to another device and copy to it the latest stable ROM)
If not, then if you ask me - it might be a hardware issue. It's very probable since before it you had no issues with the same ROM.
need4steer said:
Did you try another battery?
Did you tried different ROMs?
What's happening in recovery mode?
Click to expand...
Click to collapse
I don't have another battery nor different ROM's. I tried to revert to Froyo, but since USB is malfunctioning, I gave up on it. Recovery mode also reports battery as 100% even if it's nearly dead.
need4steer said:
Perhaps one of the pins in the connector is bad?
Is the connector looking okay for you?
Did you tried different ROMs?
Click to expand...
Click to collapse
Yes, the connector is looking okay to me. I removed it myself very carefully while replacing the digitizer. I'm almost sure it is NOT a hardware problem.
need4steer said:
Is it happening in the same USB port in your computer?
Is the USB port connected directly to the motherboard, or is it one that is connected to the chassis, and from there to the motherboard?
Click to expand...
Click to collapse
I tried many different cables and USB ports. Both chassis front and rear mobo. Even different PC's. Same results. 1 every 30 tries will let me use ODIN, and 1 every 30 tries, ODIN will complete uploading. That's frustrating.
need4steer said:
The problems occurred only after the update? If so, revert. (I no that you don't have a USB connection, but you can take you sdcard to another device and copy to it the latest stable ROM)
If not, then if you ask me - it might be a hardware issue. It's very probable since before it you had no issues with the same ROM.
Click to expand...
Click to collapse
[/QUOTE]
The problems occurred right after replacing the digitizer. Since I had Android 4.2.2 already installed, I didn't insist on trying different ROM's or rolling back to Froyo.
Thanks for the quick reply.
MrCabana said:
The problems occurred right after replacing the digitizer. Since I had Android 4.2.2 already installed, I didn't insist on trying different ROM's or rolling back to Froyo.
Click to expand...
Click to collapse
I must admit that it's not looking good since it's probably a hardware issue. If not, why these 3 things stopped working right after you replaced the digitizer?
However, if you want my advice, do open a new thread with appropriate topic name and include all this information so others will see it. Maybe someone will suggest something that we didn't think of.
In addition, while Android 4.2.2 is already installed in your device, don't forget that you can continue updating to newer versions:
need4steer said:
I know that you don't have a USB connection, but you can take your sdcard to another device and copy to it the latest stable ROM
Click to expand...
Click to collapse
need4steer said:
I must admit that it's not looking good since it's probably a hardware issue. If not, why these 3 things stopped working right after you replaced the digitizer?
However, if you want my advice, do open a new thread with appropriate topic name and include all this information so others will see it. Maybe someone will suggest something that we didn't think of.
In addition, while Android 4.2.2 is already installed in your device, don't forget that you can continue updating to newer versions:
Click to expand...
Click to collapse
Alright, I willl try to update version and see what happens.
Thank you.
need4steer said:
I must admit that it's not looking good since it's probably a hardware issue. If not, why these 3 things stopped working right after you replaced the digitizer?
However, if you want my advice, do open a new thread with appropriate topic name and include all this information so others will see it. Maybe someone will suggest something that we didn't think of.
In addition, while Android 4.2.2 is already installed in your device, don't forget that you can continue updating to newer versions:
Click to expand...
Click to collapse
I just updated to the newest nightly version, Android 4.4. Despite I now have neat KK, the problems persist.
Anyway, thanks for your help and I will follow your advice of opening a new thread.
MrCabana said:
I just updated to the newest nightly version, Android 4.4. Despite I now have neat KK, the problems persist.
Anyway, thanks for your help and I will follow your advice of opening a new thread.
Click to expand...
Click to collapse
First of all, congratulation! I had no doubt you'll do it easily.
These 3 problems will persist in this and in any ROM, since unfortunately it seems like a hardware problem.
However, I might be wrong (hopefully), and posting a dedicated thread for these problems will make them exposed to others so you might get some good solutions for them.
Good luck!
Great effort, @need4steer thank you for announcing so clearly the solution for blueish-screen-bug!
Many people have been reporting this problem in the past, this thread is most welcome!
Thanks
need4steer said:
reserved for videos and screenshots which demonstrates this issue.
In the meantime,
YouTube videos which demonstrates this issue
Screenshots that I posted in another post.
Click to expand...
Click to collapse
Thanks for the help, I thought I will never be a new software!
tetakpatak said:
Great effort, @need4steer thank you for announcing so clearly the solution for blueish-screen-bug!
Many people have been reporting this problem in the past, this thread is most welcome!
Click to expand...
Click to collapse
kssthomas said:
Thanks for the help, I thought I will never be a new software!
Click to expand...
Click to collapse
Thanks a lot for both of you for your appreciation!
I'm glad that I'm able to help others.
Galaxy S i9000 display issue
Oops, Sorry need4steer for sending a PM to you.. I don't know I can post on this thread..
By the way.. I figured what my problem is.. It's Screen Burn In.. That problem on screen I encountered was not only happening when playing flappy bird, it's noticeable on bright displays, tried some apps that can remove it.. I tried the "Screen Burn-In Tool" Tried it for 8 hours of non-stop color switching, but nothing changes at all.. Any remedies to remove the screen burn ins in my Galaxy S GT-I9000?
Thanks for the help!
gameguard025 said:
Oops, Sorry need4steer for sending a PM to you.. I don't know I can post on this thread..
By the way.. I figured what my problem is.. It's Screen Burn In.. That problem on screen I encountered was not only happening when playing flappy bird, it's noticeable on bright displays, tried some apps that can remove it.. I tried the "Screen Burn-In Tool" Tried it for 8 hours of non-stop color switching, but nothing changes at all.. Any remedies to remove the screen burn ins in my Galaxy S GT-I9000?
Thanks for the help!
Click to expand...
Click to collapse
Hi
I'm not familiar with the screen burn in issue.
However, a Google search for i9000 screen burn in site:forum.xda-developers.com or i9000 screen burn in on top site:forum.xda-developers.com shows a lot of interesting threads in this forum.
In addition, since this thread is dealing with the bluish screen issue and not with the burn in issue, I think it'll be the best if you'll post a new thread in this forum so your problem will be exposed to others and they'll be able to give additional and more appropriate solutions.
BTW, it's always better to post screenshots, so be sure to include the ones you sent me in PM.
If you need any help whatsoever please notify me and I'll do my best
Good luck!
Hi,
I just wanted to create a centralized thread for all the discussion surrounding the work of fixing the softkeys.
Many users are reporting, including myself, about the softkeys not working properly after some time on the ICS roms.
My 25 cents:
Is it a kernel issue? ROM issue? I have tried multiple ROMs but none have fixed the issue.
Multiple kernels tried too, to no avail. I suspect it is a software issue though. It's as if the buttons go into some state of sleep mode in the software, and after a few minutes come back for a few milliseconds. Just my thoughts into it.
-
Sergio
After facing the issue, i smartflashed gingerbread, there also softkeys not worked.
It is a kernel issue for sure. Worked great on GB, but I think they messed up the driver in ICS. Have you tried my blue kernel already? Dont know if I fixed it there, but it is worth a try. Or compile your own kernel, but use the GB Softkey files. Should work just fine with some mods here and there
Sent from my XT1052 using XDA Free mobile app
Has anyone successfully fixed this issue?
I am facing the same problem after flashing ICS on my OB.
i fixed it by replacing the digitizer, i had to order 2 cause the first arrived with the same problem.
Maybe
hackerse7en said:
i fixed it by replacing the digitizer, i had to order 2 cause the first arrived with the same problem.
Click to expand...
Click to collapse
I don't know about that though, mine works excellent through the CM key test. Just fails in the OS. And I can't use the kernel by Nooby, I'm on Nameless KK. But before that I tried IZS, GB, 2.1, etc to no avail.
I'm gonna research this and try and fix it in the Aeroi Kernel