Related
Darky Q&A
It seems that a pinned Q&A for Darky is missing here.
I have been using Darky 8.1 and just recently decided to give 9.3 a try. One of the things I have liked about Darky is that that the version of 2.2.1 on it supports bluetooth voice dial. I have a BlueAnt S4 in my car, and although it does not voice dial 100% perfectly, it's still worth using. (the rest of the 2.2.1 roms I have tried that do not support bluetooth handsfree)
Okay, here is my question: on Darky 8.1, going to Settings - Display - Wallpaper -Lock screen wallpaper - Gallery ... would result in->
Sorry!
The application Settings (process com.android.settings) has stopped unexpectedly. Please try again.
[Force close]
I seem to remember the initial update to 9.0 (or 9.1) listed that this was fixed. I just got 9.3 running last night, and this still results in a force close. Does Darky have a forum to post this kind of thing, where the developers might see it?
swype
Okay, Swype just expired.
"Your trial period has ended. Please upgrade your copy of Swype."
I am on Darky 9.3 extreme captivate edition. Any fix?
Bump
moymike said:
Okay, Swype just expired.
"Your trial period has ended. Please upgrade your copy of Swype."
I am on Darky 9.3 extreme captivate edition. Any fix?
Click to expand...
Click to collapse
Bump
moymike said:
Okay, Swype just expired.
"Your trial period has ended. Please upgrade your copy of Swype."
I am on Darky 9.3 extreme captivate edition. Any fix?
Click to expand...
Click to collapse
Same problem here, also on Darky 9.3 extreme cappy. I've tried reflashing the captivate swype file, restoring a previous back up, and installing the newest beta. No dice on all 3 accounts.
This doesn't seem to be a problem with just Darky though, and poking around the site it doesn't look like it is exclusive to the Captivate either.
Darky's 9.3 phone not receiving calls
Once again I would have posted in Darky thread in android development if I could..
Ever since I have installed Darky's my phone has had problems receiving calls and will often say "simcard removed from phone please reboot". Today I got a new simcard because I thought that may be the problem but I tested and it still doesn't work. My friend rung me and as the call comes through my phone loses service and the call gets cut instantly and slightly later it'll pop up saying simcard removed please reboot phone. Is anyone else having this problem? Maybe it's time to go to Cyanogen Mod..
Did you ever restore data with Titanium Backup after you installed Darky's?
Yup I restored everything that was on my old rom Cognition
That's your problem. I used to have the same problem. Your phone settings is different between the two ROMs. You should typically ONLY restore app data. Not the system data.
Try going into back into TiBu, then find 'Phone' and click on 'Wipe data'. Hopefully that'll make your calls work again. If not, you might need to reflash Darky's.
System data backups really don't work well between different ROMs (and even different versions of the same ROM).
P.S. Nice to meet another NZer btw.
Oh I see, yeah that makes sense, I asked a friend if I should restore everything I backed up and he wasn't sure so I just restored them all anyway. Now I'm not sure if I should reflash Darky's or move to Cyanogen Mod.
I would try the 'Wipe data' thing first before I try any flashing though!
Upgrade from 9.2 to 9.3 help
In the dev thread, it says you should flash a captivate kernal and modem before installing 9.3. I was wondering if anyone could point me in the direction of a guide to flashing modems/kernals.
Just kinda worried cause I have read so much about people bricking their phones when putting the wrong kernal/modem combo together. I noticed on the Darky app it has options already there, so do I have to downlad the kernal seperately, or did it come with the app, or does the app download it from somewhere?
I am afraid that if I flash the modem first, then reboot it won't match the kernal and I will get stuck.
Thanks!
DriftinOutlaw said:
In the dev thread, it says you should flash a captivate kernal and modem before installing 9.3. I was wondering if anyone could point me in the direction of a guide to flashing modems/kernals.
Just kinda worried cause I have read so much about people bricking their phones when putting the wrong kernal/modem combo together. I noticed on the Darky app it has options already there, so do I have to downlad the kernal seperately, or did it come with the app, or does the app download it from somewhere?
I am afraid that if I flash the modem first, then reboot it won't match the kernal and I will get stuck.
Thanks!
Click to expand...
Click to collapse
You can flash a Modem in Recovery just like you Flash a ROM or Kernel. If you happen to Flash a wrong Modem it won't cause any problems other than you won't get Cell Service. I am presently using the New znkp1 modem and it doing Great on my Cappy with 9.3 Darky and SuckerPunch/Voodoo Kernel.
moymike said:
Okay, Swype just expired.
"Your trial period has ended. Please upgrade your copy of Swype."
I am on Darky 9.3 extreme captivate edition. Any fix?
Click to expand...
Click to collapse
Hope u got to downloading the latest fix with Swype
DriftinOutlaw said:
In the dev thread, it says you should flash a captivate kernal and modem before installing 9.3. I was wondering if anyone could point me in the direction of a guide to flashing modems/kernals.
Just kinda worried cause I have read so much about people bricking their phones when putting the wrong kernal/modem combo together. I noticed on the Darky app it has options already there, so do I have to downlad the kernal seperately, or did it come with the app, or does the app download it from somewhere?
I am afraid that if I flash the modem first, then reboot it won't match the kernal and I will get stuck.
Thanks!
Click to expand...
Click to collapse
Yeah.. Use No Kernel/No Modem in DarkyRom Configurator app and do as RonH54 said!
Lockscreen Wallpaper
moymike said:
It seems that a pinned Q&A for Darky is missing here.
I have been using Darky 8.1 and just recently decided to give 9.3 a try. One of the things I have liked about Darky is that that the version of 2.2.1 on it supports bluetooth voice dial. I have a BlueAnt S4 in my car, and although it does not voice dial 100% perfectly, it's still worth using. (the rest of the 2.2.1 roms I have tried that do not support bluetooth handsfree)
Okay, here is my question: on Darky 8.1, going to Settings - Display - Wallpaper -Lock screen wallpaper - Gallery ... would result in->
Sorry!
The application Settings (process com.android.settings) has stopped unexpectedly. Please try again.
[Force close]
I seem to remember the initial update to 9.0 (or 9.1) listed that this was fixed. I just got 9.3 running last night, and this still results in a force close. Does Darky have a forum to post this kind of thing, where the developers might see it?
Click to expand...
Click to collapse
Just letting you know that in the Darky Rom Configurator App, if u enable LockScreen Wallpaper, it would use Samsung Gallery which has a battery draining bug. Hence it is an option in the Darky app before flashing.
If you really want to use it, enable it and then flash. Or I'll just work on disabling that menu option.
DriftinOutlaw said:
In the dev thread, it says you should flash a captivate kernal and modem before installing 9.3. I was wondering if anyone could point me in the direction of a guide to flashing modems/kernals.
Click to expand...
Click to collapse
Don't know if I'm too late on this but...the modem/kernel combo included has been working good for me; no need to change it. Like rickysa2000 said, don't select a modem/kernel using Darky's Configurator when you flash 9.3.
My only SMALL issue has been when going into APPS and sometimes they won't scroll for maybe two/three seconds.
But it's still my favorite ROM so far (though it's only my fourth). Especially impressed with the dev's attitude and willingness to help!!!
[ROM] Darkyy's 10.0 Gingerbread!
I was just in the i9000 forum and Darkyy said he will have a flashable rom on friday!!! I hope we can get this ported for the Cappy.
Edit: looks like beta 3 is already available for the i9000. Got so excited I impulse posted...
Sent from my SAMSUNG-SGH-I897 using XDA App
She is a he. That pic is his girlfriend. But thanks for the info.
Sent from my SGH-I897
Ha ha oops edited
Sent from my SAMSUNG-SGH-I897 using XDA App
i do not think the port will be coming anytime soon. Without source you can not have a captivate kernel. You can flash i9000 but no back button, and screen rotation, head phone jack, etc
MIUI
mcord11758 said:
i do not think the port will be coming anytime soon. Without source you can not have a captivate kernel. You can flash i9000 but no back button, and screen rotation, head phone jack, etc
MIUI
Click to expand...
Click to collapse
If its on i9000 it will be on captivate within a day lol
Hi,
just about the time when i flashed JV1, my lightsensor stopped working properly.
It's so annoying when auto-brightness just jumps between low brightness and full brightness.
I thought it might be a bug. But now with JVB it still doesn't work. I checked it with a few sensor test apps and it outputs either 6.0 lux or 5000.0 lux.
Does anynone else have this problem? Is there a possibility to flash the eclair or froyo "lightsensor driver"?
Anyone? 10char
It's not a bug, it's a feature.....blame Samsung.
Yes, everyone has that.
Update to JVB and everything will be fine I dont have any big issues with GB, since I'm using Darkys Rom v10 Just check out his thread.
Und schöne Grüße aus Deutschland
alexx910 said:
Update to JVB and everything will be fine I dont have any big issues with GB, since I'm using Darkys Rom v10 Just check out his thread.
Und schöne Grüße aus Deutschland
Click to expand...
Click to collapse
I have JVB and I have this issue also.
Well, that was only an advice For me it works very well without issues, so I'll stay at JVB till a new Rom will come out with GB, of course by darky.
Same issue here. Refleshing to JVB did not help
sarbe said:
I have JVB and I have this issue also.
Click to expand...
Click to collapse
Same here, downloaded brightness widget from market and keep it on 25% now.
Anybody got any updates on this, or some kind of fix? Really weird, because it seems only some have this problem, but it seems to be the case with a few other phones too.
My galaxy s has been behaving like this always, since I first bought it with stock gingerbread, and there's no difference in Darkys Rom 10.1. Light sensor goes from either 6 lux to 5000 lux in Androsensor, and the proximity sensor behaves the same way (only two values).
Shortly after posting this, I came across
darkyrom.com/community/index.php?threads/brightness-fix-for-jvp-jvq.4019/ <- that tread (apparently I'm not allowed to post links yet).
Even though I am on JVH, and the fix uses files from JVH to apply to JVP/JVQ, it worked wonders on my phone!
This fix worked also for me.
With simple Honey 5.1 on JVS with speedmode kernel.
Thanks a lot..
Is there a fix, or different apk, for the email stock app (not gmail) that will fix the auto capitalization and auto complete? All other apps seem to work fine, but mail.
I am currently on Pinnacle 1.3 for Captivate, but had the same issue on Cognition 5, v1 and v2.
I saw there was a possible fix in the CM7 thread, but I tried to install it with CWM and it failed.
Thank you in advance for help.
Sorry if this post is in the wrong area, but I think I am okay. I have posted this question in the Cog and Pinnacle threads, but got no response.
Is it possible that no one else has this issue? Is it just me? Interesting that I have posted this several times, in different forums, and do not get a response?
Please reply if you do or do not have this issue. Thank you.
I have the same issue with the leaked 2.3.3 GB ROM. I haven't looked for a fix.
It is nice to know I'm not completely alone, but it is still interesting how few responses are here. Not sure what to make of that...
Anyone? Please... I have to get this fixed or I will have to bo back to early releases that didn't have the issue, which I really do not want to do...;-(
I really don't know. Only thing I would try is pulling the email apk from a froyo and using it on your ROM. I don't know if it will work or not.
I've searched a lot for this and haven't come across anyone with the same problem, so I wanted to ask. I've tried flashing different kernels and modems, but it hasn't changed anything. I'll try to flash a different ROM next, but I don't know if that's the issue or not, so I wanted to go ahead and ask the question.
Model: Captivate (SGH-I897)
Android: 4.0.4
Modem: I9000UGKG3
Kernel: 3.0.17-Sepmaphore_ICS_1.2.5sc (#20 PREEMT Jun 20)
Build: 4.0
Mod: Slim_ICS_4.0.4
I have an I9000 modem for Slim, which as far as I can tell is correct since it requires a modem compatible with CM9. I've tried a few different kernels, all of which I found recommended across various Slim discussion forums.
My problem: The GPS logo won't even show up. It is enabled in the config (verified several times). GPS doesn't appear to work at all and won't turn on when suppose to be activated (i.e. with GPS Status, Google Maps, etc.)
From what I understand, the modem has nothing to do with the GPS. What about the kernel? Note that my GPS worked OK on stock Gingerbread. The update to ICS and over to a I9000 settings has killed it, and I can't figure out why.
Is there something obvious I'm missing? I'll flash a different ROM later tonight... the GPS is the only thing that really doesn't work. (I mean, it never worked great, but now it won't even act like it is coming on.) Suggestions?
Take a look in the modems thread in the Development section - follow the link and grab one of the modems specifically for CM7/CM9/MIUI. I don't know that I9000 modems will work properly with ICS roms.
Great, thanks for the help. Not sure what the problem was, but I reflashed with JK4 and now everything is working like it should be again. Thanks for the help!
Link to JK4 (for anyone else who might have this problem): http://forum.xda-developers.com/showpost.php?p=17062675&postcount=182
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!