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!
Q&A for [ROM][GT-I9305][KitKat][4.4.4] CyanogenMod 11.0 Official
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
GT-i9305 CM11 known issues (or DONE/TODO lists)
Hi all,
I'm interested on CM11 in GT-i9305 (I own gt-i9305, I'm running running CM10 and I would have some new features included in CM11 (i.e.: LowEnergy Bluetooth). Btw I'm afraid about it because CM11 has not a stable release, maybe it will never has a stable(/RC) release... So I'd like to know what features are running and what else is not running... because I'd like to have new (CM11) features but I want my phone to not lose what is ok in CM10...
Looking at Known Issues page (wiki - Known_Issues_page_for_i9305) I see CM10.1 and CM10.2 related issues... but not CM11 ones...
There are any lists that users can see to make a conscious chose? I want to assess what features I'm going to lose upgrading to CM11 (camera was working in CM10... it doesn't work in CM11, I suppose).
I know gt-i9305 CM11 official thread... btw it's more than 100 pages, so Its not useful.
My revious phone was Motorola-Defy (MB525) and CM thread (first message) spoke about features, installing procedure, TODO list, know issues... GT-i9305 CM11 official thread doesn't include TODO (not running list)
Thanks in advance
LOW MICROPHONE VOLUME (videorec - whatsapp...)
how to fix this problem????
low volume on call
Hi,
Can anyone help with the problem of a very low speaker volume during call?
I have read here about changing the numerical values somewhere to increase the volume.
in addition, ther's the problem of low microphon rec.
i run nighitly 11-20141031.
(step-by-step would be much appreciated )
Well from what I have seen. Not sure if its true just yet but maclaw who works on s3 mini and other devices is ready to clone the lollipop repo when it gets released by google
Sent from my GT-N7105 using XDA Free mobile app
---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------
CNerone said:
Hi all,
I'm interested on CM11 in GT-i9305 (I own gt-i9305, I'm running running CM10 and I would have some new features included in CM11 (i.e.: LowEnergy Bluetooth). Btw I'm afraid about it because CM11 has not a stable release, maybe it will never has a stable(/RC) release... So I'd like to know what features are running and what else is not running... because I'd like to have new (CM11) features but I want my phone to not lose what is ok in CM10...
Looking at Known Issues page (wiki - Known_Issues_page_for_i9305) I see CM10.1 and CM10.2 related issues... but not CM11 ones...
There are any lists that users can see to make a conscious chose? I want to assess what features I'm going to lose upgrading to CM11 (camera was working in CM10... it doesn't work in CM11, I suppose).
I know gt-i9305 CM11 official thread... btw it's more than 100 pages, so Its not useful.
My revious phone was Motorola-Defy (MB525) and CM thread (first message) spoke about features, installing procedure, TODO list, know issues... GT-i9305 CM11 official thread doesn't include TODO (not running list)
Thanks in advance
Click to expand...
Click to collapse
I have been running cm11 since first release. And its been getting better with each release.. The latest nightly with Agni kernel is a good daily driver. I haven't found any problems.
Sent from my GT-N7105 using XDA Free mobile app
Does anybody faces problem with missing calender in latest nightly?
All I got is "missing calendar storage"
guide me
hello sir.,
help me and guide me to update kitkat 4.4.4.
i have samsung galaxy s3 I9305 LTE
AP: I9305XXUEMKC
CP: I9305CCUEMK1
CSC: I9305VDIEMK2
(in my phone i have vodafone applications may be it is vodafone carrier .i have bought in UAE ( dubai) ).
Is there any chance to update kitkat 4.4.4 germany (DBT) official update to my s3 LTE.
if i update to germany 4.4.4 kitkat .any thing will going to brick my s3 LTE.
please suggest me i am kindly waiting for your replay.....
if there is no problem to update kitkat 4.4.4 .please provide perfect procedure sir...
Has anyone started compiling cm12 for the i9305 yet???
Sent from my GT-N7105 using XDA Free mobile app
Moving on...
Just wanted to say thanks for the last years with cyanogenmod for i9305.
Im moving on to the Sony parts of XDA.
Trying to catch a burglar last week resulted in a broken samsung, and I thought I would try something new.
cm12
does anyone know when the CM12 will be available ?
thanks for this awesome rom
no future updates?
Does this mean that there will be no CM11 update for I9305?
Cm11 - any way to turn of charging led notification when screen is on
Hi, is there any way to disable charging led notification light when the screen is on? i have tried many apps from play store but none have option to disable when the screen is on. Even no xposed modules are helpful in this regard.
Secondly please guide me the way to fix led light turns green at reaching 90%, this issue was previously solved in CM10.
Thank you.
please help
please help!
noteespirit said:
Hi, is there any way to disable charging led notification light when the screen is on? i have tried many apps from play store but none have option to disable when the screen is on. Even no xposed modules are helpful in this regard.
Secondly please guide me the way to fix led light turns green at reaching 90%, this issue was previously solved in CM10.
Thank you.
Click to expand...
Click to collapse
WiFi Power Saving Mode
Is there anyway to turn off WiFi power saving mode on CM11, Beacuse i cannot connect to WiFi in any other way for some reason and when i try to it just says (saved and secured > authenticating and then it just goes back and says saved and secured)
And sorry im very new to CM11 and forums in general!
Power off charging animation stuck.
The charging animation on my phone gets stuck when I turn my phone off. Are there any fixes?
Thanks
Samsung I9305 Dock Audio with Cyanogenmod 11 fix
Since installing Cyanogenmod KitKat4.4.4, 11-20150105-NIGHTLY-i9305, the main issue I had was I could no longer use my Samsung Desktop Dock EDD-D200BE to output audio, with the help of TKMAS on the Cyanogenmod Forum, I found there was an issue with the "audio_policy.conf" file, located in system/etc, it was missing a line of text in the devices line under "audio_hw_modules" just adding to the end of the line the following
|AUDIO_DEVICE_OUT_DGTL_DOCK_HEADSET
and saving the file, rebooted my phone and audio now comes out of the dock, I found the audio_policy.conf info here https://android.googlesource.com/device/samsung/manta/+/jb-mr1-dev/audio_policy.conf
CM WiFi power saving mode
Yes. Just go to Settings->Wi-Fi and then click on Menu->Advanced. You'll find here useful options such as "Keep Wi-Fi on during sleep", "Wi-Fi optimization" and "Avoid poor connections"
RunamukOG said:
Is there anyway to turn off WiFi power saving mode on CM11, Beacuse i cannot connect to WiFi in any other way for some reason and when i try to it just says (saved and secured > authenticating and then it just goes back and says saved and secured)
And sorry im very new to CM11 and forums in general!
Click to expand...
Click to collapse
same problem here
Just had my stint with the latest two official nightlies, 0406 and 0412, and the camera is even worse when I first tried this rom in january. FCs, cant connents, even freezes up and reboots the phone, on a few days old, fresh wiped install. The so called "fix" just removed my camera as a whole, even other apps (Insta, Google camera), and full factory reset didnt work after that. I had to reflash from zip.
idk if this is the right thread to ask but...
what is this camera problem, and if there was a fix, why isnt this integrated in CM ages ago?
whats the point of compiling official CM nightlies till its camera is not working flawlessly out of the box? completely useless this way.
how come theres nothing in the developement thread, when almost every week a new compile comes out?
and foremost, who compiles these official nightlies when the OP behind it declared out of the project..???
sorry if im noob, but someone can explain this to me? CM is a huge disappointment for me, as I waited eagerly to put it up as my phone warranty expires. I never thought Id say stock TWiz is much better then this.
but im willing to give another try if someone helps who to get this working properly out of the box, because I liked the speed and simplicity. thx...
---------- Post added at 01:48 PM ---------- Previous post was at 01:41 PM ----------
chrizza710 said:
thanks for this awesome rom
Click to expand...
Click to collapse
sorry to ask, but You still use this rom? Is the camera worked OK for you? What nightly was that then, when you wrote this post, and you still use that, or updated it? thx.
I just flashed a new ROM, the simple asop (I think). Now when I play a video from Netflix, Hulu, or Facebook, I get the sound but no video. I sometimes get the image of the thumbnail, or the channel logo from Hulu, but nothing else. I'm new to android so I'm sure there is something I messed up, I just don't know what it is.
It's a custom ROM issue, try another custom ROM that is more stable.
Videos are known to not be working 100% stable on custom ROMs.
If it was cm12 it is a known problem. To fix disable HWOverlay in developer options.
It's simpleasop is there a known problem with it?
DjPhly said:
It's simpleasop is there a known problem with it?
Click to expand...
Click to collapse
Yes... see the latest pages in the ROM thread, there is a test build with this fixed.