Got my i9100 back last night. I sent it away under warranty complaining about 2 issues:
1) Yellow/blue screen tint issue
2) Low call volume when using hands free.
The screen tint appears to be gone. They must have replaced the screen (?) as it seems fairly new however it's definitely the same handset as I checekd the serial number etc. Happy with that anyway.
Not too happy about the call volume. I STILL have to go into the service menu and increase headset volume from 84 to 100 but I have to do this every time I reboot the phone! Can this be fixed at all? It's not an issue if i'm in a quiet room however if i'm at work or even worse, when i'm driving, or in a car, then it's an absolute nightmare trying to make out what the other person is saying.
Also - a side note - i rooted the phone and tried to perform a nandroid restore however my phone got stuck at the boot logo and kept looping. Had to re-flash using stock rom! doh!
Where can i get an ICS firmware for an unbranded i9100 ?!
You will find ics here in general section
CM9 or Samsung ics
Related
So this has been happening randomly on calls for about two weeks now. I'm still on Stock everything and would like to know if this is a known problem, if something is wrong with my phone, or if there is a fix? I'm past the point of returning and getting a new one and plus, I have grown atattched to this phone LOL.
I've tried hitting speaker and then turning it off but that doesn't work. Tried ticking mute and then unticking it, not working either. Reboot doesn't work. Resetting back to stock doesn't change it either.
Thanks to all.
AJ
Sounds like a typical ATT phone call. Would you and the person on the other end both happen to be on speaker phone? I cannot have a call via speaker to my wife if she is on speaker (which see insists on using) - there is too much voxing going on, I only hear every couple of syllables.
T
Sent from my SAMSUNG-SGH-I777 using XDA App
Not a speaker phone call. Seems like it happens mostly when I make calls from speed dial from my homepage screen. I can't conf
irm that last bit though lol.
Another question is this....I just turned my phone completely off and it had 42 % battery. When I turned it back on it now has 22% left.....what in the world is going on lol???
Would I be better off reverting back to 2.3.4? Or just getti
ng another sgs2?
asjdwf said:
Would I be better off reverting back to 2.3.4? Or just getti
ng another sgs2?
Click to expand...
Click to collapse
I need more details to say this for sure, but I THINK you may be having the same issue I had. Not many people seem to have this issue (only seen a handful across a variety of forums). So if you happen to be a fellow sufferer, then welcome to the club!
My problem was:
After the 2.3.6 update (UCKK6), the person on the other line had trouble hearing me because my voice cut in and out frequently, yet randomly. On my end though, they came in nice and clear. I often had to deal with people hanging up on me because they thought my call dropped or that I hung up, or had to deal with a lot of people repeating "hello? hello!? You there!?" as I helplessly tried responding and not being heard.
My Solution(s):
1) keep the 2.3.6 update, but flash just the 2.3.4 (UCKH7) modem. Everything on your phone will work fine, but you will get the following FALSE warnings (FALSE as in the phone says it can't do something, yet everything works fine anyways. These are only based on first-hand experience and may not happen to you.)
a) upon boot (not wake/unlock) there will be an error notification about you not being able to access your external memory card due to security reasons... don't worry, its bull.
b) when using your phone as a mass media storage device, you will get a notification about the mass storage function not being able to work... this message is also bull.
2) Or you can just completely return to 2.3.4 (UCKH7) and either ignore the update prompts or freeze the process until a newer update that hopefully fixes our problem (or ICS) is released.
I did (1) for about 2 weeks then did (2) after reading all the battery complaints blamed on UCKK6. It reverted just to play it safe with battery life (plus they say that "if it ain't broken, don't fix it" and for me, UCKH7 wasn't broken and the update definitely broke it).
Wow, that sounds identical to me except its they can hear me but I can't hear them LOL. I reverted last night with odin one click downloader and the stock kernel for battery life so we will see what's going to happen today. Is this a phone problem physically or is it software?
Thanks
AJ
For me, its a software issue (modem to be specific) because it only happens on UCKK6 (and the leaked UCKJ1, UCKJ2, and UCKJ4) and when on UCKH7, my calls are as clear as a LAN line.
I say that if the problem still exists now, then its hardware. In that case, try contacting Samsung for a replacement if your ATT warranty is up. You could try ATT too because its a defective phone and they may still do something.
So sometime in the last week or 2, my I9300 started randomly freezing up and/or shutting off by itself.
it's usually a while after booting - i'll come to unlock it, and the LED will be showing Blue. Clicking any of the buttons doesn't do anything, nor does waiting a while.
Holding down the power button for a few seconds boot/reboots the phone though, and it works normally when it starts back up again - although after a while it will die again.
Sometimes it runs for hours, sometimes just minutes.
Occasionally, it will freeze up while i'm actually using it - the screen stays on, frozen in place, but the touchscreen and buttons won't do anything (although oddly, multiple clicks of the home button make the colours invert?).
Anyway, i thought this soundsed a bit like this 'Sudden Death' bug, but how do I know? I installed and ran the eMMC check app and it says:
Phone Model: Samsung GT-I9300
eMMC chip: Type VTu00M, Date 05/2012, CID 15010056545530304df1f900755f5f5f, FwRev oxf1
SGS3 Sudden Death? YES. Insane chip.
My question is - what does this mean? Do i have the problem and just need to make sure i run a kernel with the fix, or is the phone now broken and needs replacing/fixing?
If it does need fixing, do i need to revert it to stock ROM and run triangleaway or anything before i send it in, or is it fine how it is?
It's currently running crDroid 11.1 XXELLC, and it was at the time i started noticing the problem. I'm using Siyah 1.8.9, although i was using an earlier version before (can't remember what).
Same problem here... i don´t know what to do... today i make a lot of things to attempt to restore all but everything fail... i decided to talk with samsung and send the phone to repair, in a few days I hope to come to pick up the phone, I have to say that I had to pay 24 € for the shipping and after playing wait month or month and a half. is frustrating but hopefully come good repair.
One read the SDS thread . Two if you think you have the problem or a problem follow the how to revert to stock post and take to a service centre .
Freeze is more likely rom and or kernel .
???????
although oddly, multiple clicks of the home button make the colours invert AS IT SHOULD .
jje
thanks - have read the SDS thread and the stuff people were talking about there didn't really sound like what's happening for me, which is why i posted this thread.
I also thought that it sounded like the ROM or kernel, which is why I have now tried Siyah, tank, and boeffla kernel latest versions, as well as the foxhound, android revolution, and darky roms.
none have made a difference so far
I'm just looking for some ideas on what to do next - should i try reverting back to an Old rom/kernel, should i try a non-sammy based one, is it possible that my SD card is somehow causing the problem?
i didn't know that the multi-click thing inverted the colours - why does it though? it doesn't seem like something i'd want a shortcut to.
Wipe phone flash stock rom .
jje
Fixed it by moving from ELLA modem & wiping.
This thread is your solution : http://forum.xda-developers.com/showthread.php?t=2091045
so i wiped again and installed the MA2 modem - this made the freezing problem even worse so i wiped again and installed the ELKC modem.
this was on Monday and I hadn't had a single freeze until this morning, when it's frozen 4 times in the space of a few hours.
so i guess i'm flashing back to the factory image...
Lear95 said:
Fixed it by moving from ELLA modem & wiping.
Click to expand...
Click to collapse
My international Galaxy S3 started to constantly freeze, lock up and hang. So I decided to factory reset it. Then I figured why wouldn't I also switch to a custom ROM in the process. So I read the tutorials and installed Android Revolution ROM. The freezing problems have become very rare (they didn't completely go away) but this time I got an even worse problem. My phone won't wake up sometimes. It happened again a few minutes ago: The phone would ring (albeit the ringing tone came out laggy), nothing on the screen, I press power button no response, then I take the back cover off and reinsert the battery, boot the phone and look at the call logs but of course it doesn't show who called me. This is getting very frustrating. What seems to be problem?
Which version of Samsung Android were you using before?
You could try to flash official Samsung Android over your CM via Odin: and I mean 4.1.2 which is still more stable and reliable than the new 4.3 (In my opinion).
This should wipe everything on your device, and hopefully repair what's wrong with it.
Hope it helps.
Hi everybody i am asking for advice on trying to repair a phone for a family member the phone is a galaxy alpha F variant UK stock rom, factory unlocked and unrooted the problem started after finishing a call the handset was left un attended and when it was later picked up the screen was black but does not appear broken aywhere and does not appear to respond to touch
i have tried un successfully to get it into recovery or download modes the handset turns on and the blue lights come on and you can hear the start up tone but see nothing on screen, it also charges and i have tried a new battery, odin does recognise a device but as i cant get it into download i cant flash a stock rom which i have already downloaded.
So my question is, is there any software that i can download to diagnose whether or not the screen is dead or whether it is a f/w issue or is there a way around this where i can use a different tool to get into the handset and flash a new stock rom in case the current f/w is corrupted
Thanks in advance for any useful help and advice
Please understand that i am a newb to this so if i have made some mistakes or my questions have been answered elsewhere previously i do apologise
I think it seems pretty obvious that the problem is the display itself
Hi BigHands,
I faced a problem having the exact same symptoms as yours twice in the last few month: screen was staying black but phone reacted to some "external" actions (ON/OFF), blue light.
Not sure what happened exactly, but removing the battery and trying to restart the phone finally brought the device back to life after trying more than than 10 times!!!
So in my case, the display was probably not the (only) root cause.
Really weird however that I needed to reboot the phone >10times to make it work: usually when software is screwed either one single power cycle will bring the device back to life or it will never power up again!
Anyways, a FW issue is still a possibility considering the number of bug this phone has (for the price it was sold, that phone is definitely the worse gadget I ever owned!)... But it seems there is a bunch of FW updates on going on this model accross the world, so there is still a little hope things might improve... Samsumg may have woken up; who knows...
JF
My S22+ suddenly started to have a seriously distorted speaker which meant ringtone and notifications sounded like mud. I thought it might be a software bug, but then realized if I pressed down on the middle of the phone, everything was good! Some quick Google searching showed that I was not the only one having the problem.
Must be a build quality issue for Sammy, but of course they refused to admit there was any issue and wanted me to get it repaired. I've decided to send the phone back instead and get my trusty S20+ back. I just don't have time to be inconvenienced by their problem.
have you tried it in safe mode?
think its been fixed in update ? mine was doing it when fist got it but now seems ok
funny mines started to do it again after few months and latest update but then went back to normal again ????? not even cold so cant blame that