Hi,
Got a strange issue on my i9505. Evrything working fine at boot until i lock the screen (or until it lock by himself).
Then touch screen become irresponsive.
other roms , factory reset nothing works ...strange because seems to be driver related.
I was about to odin flash a samsung rom ...
Has anybody ever experienced such behaviour ?
Z
Problem solved by reflashing samsung firmware than soin all he road again .
Suppose bl related.
zapatt said:
Problem solved by reflashing samsung firmware than soin all he road again .
Suppose bl related.
Click to expand...
Click to collapse
Hello!
I know that reviving dead threads is not very popular but would you please tell me what you wanted to say in your post? I presume that some auto complete function garbled your text. Which revision of Samsung firmware did you flash to solve the problem?
I have exactly the same problem. Moreover, it prevents me from installing Optimized CM13 since I don't have touch in AROMA installer.
eTaurus said:
Hello!
I know that reviving dead threads is not very popular but would you please tell me what you wanted to say in your post? I presume that some auto complete function garbled your text. Which revision of Samsung firmware did you flash to solve the problem?
I have exactly the same problem. Moreover, it prevents me from installing Optimized CM13 since I don't have touch in AROMA installer.
Click to expand...
Click to collapse
Hi Taurus,
I m not sure we got the same issue. My touchscreen become irresponsive After being Locked, either in twrp or in Android. As far as I Can remember, it Was related to custom kernel, i have to reflash à Samsung kernel. I think i Was underground jdc lollipop rom.
We have exactly the same problem, actually. It prevents me from installing a custom ROM which sucks!
Related
I have an s4 from rogers (Canadian model) and initially had cyanogen mod as my rom but I realized that I was missing nearly 5 GB of storage on my phone. I read that to fix this I had to go back to stock using Odin. I went back to stock 4.2.2 using Odin, but then my WiFi stopped working. I couldn't turn WiFi on or search for networks. I then rooted my phone and installed a rom and my WiFi problem was fixed, but now I cant make calls. Every time I try to call someone my screen goes black and the recipient cannot hear me and I cannot hear them. Also, the sound on my phone does not work. I have flashed multiple roms and still get the same problem. Does anyone know any possible solution. I have looked around and many people have had the same problem, but no solution. Any help would be appreciated.
It's because you flashed an old rom (4.2.2) on a newer bootloader. That doesn't work. Flash the latest rom available for you phone.
Lennyz1988 said:
It's because you flashed an old rom (4.2.2) on a newer bootloader. That doesn't work. Flash the latest rom available for you phone.
Click to expand...
Click to collapse
I have flashed multiple roms and most of them were the latest ones (4.4.4). This still did not fix the problem. Is this what you mean?
neogamma said:
I have flashed multiple roms and most of them were the latest ones (4.4.4). This still did not fix the problem. Is this what you mean?
Click to expand...
Click to collapse
I'm sorry, I gave some wrong advice.
It's probably because you are on the old bootloader but you are using a new modem. That's the cause for the problems on our s4. You have a different s4 and there is a different section for your device.
You have to be in this section:
http://forum.xda-developers.com/galaxy-s4-att
They should be able to help you further there.
Hello everybody,
i just put the a custom rom for the first time and i am actually really happy with this rom.
My friend called me 1h ago, so i noticed that i am hearing my friend fine, but the problem is that he cant hear me.
I tested it with the audio capture and it just sound messy.
Here are all the information:
Omega v33 - XXUGNF1
Android Version 4.4.2
Modellnummer: GT-19505 Black Edition
Basisbandversion I9505XXUGNF1
Kernel:3.4.0-talexop-2+-gb4fe160-dirty
[email protected]#4
I just tried it with the 3.4.0-Adam-2.3, but it is not working, too.
Did i install something wrong?
So which kernel is the right one for me to get the sound problem fixed?
varity said:
Hello everybody,
i just put the a custom rom for the first time and i am actually really happy with this rom.
My friend called me 1h ago, so i noticed that i am hearing my friend fine, but the problem is that he cant hear me.
I tested it with the audio capture and it just sound messy.
Here are all the information:
Omega v33 - XXUGNF1
Android Version 4.4.2
Modellnummer: GT-19505 Black Edition
Basisbandversion I9505XXUGNF1
Kernel:3.4.0-talexop-2+-gb4fe160-dirty
[email protected]#4
I just tried it with the 3.4.0-Adam-2.3, but it is not working, too.
Did i install something wrong?
So which kernel is the right one for me to get the sound problem fixed?
Click to expand...
Click to collapse
Hi ,
That problem most of the times is modem related , go Omega files /modem flash the same one again or upgrade it to the newest , follow instructions to do it
As shown in OP of Omega V33
Installation:
1. Backup your device (nadroid backup, titanium backup, efs backup ... etc) and save the backup to a safe place.
2. Flash the new bootloder and modems with odin
Bootloader -> BL_I9505XXUFNAD_481100_REV06_user_low_ship_MULTI_C ERT.tar.md5
If you already have the new Kit Kat bootloader there is no need to flash it again.
Modems XXUFNC9 -> I9505XXUFNC9_GSM_LTE_Modems.tar
Power off device completely, then boot to download mode and flash bootloader (if needed) and modems with odin
Then boot to android and check if the new modem XXUFNC9 flashed ok (if wifi is not working is normal)
3. Boot to Recovery --recommended TWRP, get the latest version from here -> http://teamw.in/project/twrp2/182--
and flash Omega and then boot to android.
You can flash without full wipe if you are coming from a previous Omega Kit Kat version, if not then flash with full wipe
PLEASE FOLLOW THE EASY INSTALLATION INSTRUCTIONS ELSE YOU WILL HAVE VARIOUS ISSUES!
BACKUP FIRST !!
I flashed the LTE_Modem_I9595XXUGNF1 again, but it is still the same problem.
Can i test an older one without any problems, or do you know anything else to solve my problem?
varity said:
I flashed the LTE_Modem_I9595XXUGNF1 again, but it is still the same problem.
Can i test an older one without any problems, or do you know anything else to solve my problem?
Click to expand...
Click to collapse
Mate ,
You have a I9505 or a I9595??
MAX 404 said:
Mate ,
You have a I9505 or a I9595??
Click to expand...
Click to collapse
pardon mistyped. I9505 is the right one.
varity said:
pardon mistyped. I9505 is the right one.
Click to expand...
Click to collapse
You can try with an older one if you wish and see if it helps , did you flash the GSM modem also?
MAX 404 said:
You can try with an older one if you wish and see if it helps , did you flash the GSM modem also?
Click to expand...
Click to collapse
Yes i installed both. I will try some of the LTE/GSM modems now.
I still have the microphone issue.
I Updated the baseband (GSM+LTE) to the newest I9505XXUGNF1, but i cant fix this microphone problem. It sounds like it is raining or something like the television where u cant get a programm.
I searched now about 5hours, but this is something i cant get fixed.
Please anyone here who can help with this issue?
Hey everybody,
I've been having an issue lately. Since I upgraded to Android Lollipop, I have not been able to get a GPS lock anymore. This issue only applies when I'm on a Lollipop ROM. As soon as I flash back to a kitkat TW ROM, everything works again. When I go back to a Lollipop ROM, the issue returns again.. No GPS lock. This is not ROM specific, but just related to Lollipop in my experience.
I have not seen anyone else yet with this issue, so I find this very strange. I'm currently on the latest version of GPE5 by @Danvdh if this helps. But like I mentioned before, the issue exists on every Lollipop ROM.
If someone could please help me, this would be very much appreciated! Thanks!
Anyone? ?
Me Gusta!
It seems to be a Lollipop thing.
I have the same issue with my Find 7 since installing Lollipop.
See this discussion:
https://code.google.com/p/android/issues/detail?id=81140
Me Gusta said:
Anyone?
Me Gusta!
Click to expand...
Click to collapse
mate, flash official firmaware and reset /set up your original csc with samsung phone info+ app from google play , worked on 3 phones until now this solution , be carefully csc reset gonna wipe your internal storage
thanks, i will try it
Hi,
I have just booted my phone into the Download-Mode, and studied that lines of text up left. And the Device-Name was GT-I9300I. But my Stock-firmware is the I9301I. Do you know why? Yeah, I flashed some Custom Roms and Kernels, if you need this information.
And no, there aren't any bugs recently. No bootloops or crashes.
It's a small bug, all I9301I have it. But you can't install I9300I firmwares, only I9301I.
Mine is i9301i and in download mode it shows i9301i , maybe a wrong stock firmware, because i9300i/i9301i have the same motherboard
ziad311 said:
Mine is i9301i and in download mode it shows i9301i , maybe a wrong stock firmware, because i9300i/i9301i have the same motherboard
Click to expand...
Click to collapse
Well, I saw on some post a guy asking about it too, and that was only a little bug and another guys has it too... well, the mine is I9300I, then I can't say much
From the first release date of this device, in dl mode is simple grammatical error. May be only in first released devices. Nothing special. Keep going
Jhnsn said:
Hi,
I have just booted my phone into the Download-Mode, and studied that lines of text up left. And the Device-Name was GT-I9300I. But my Stock-firmware is the I9301I. Do you know why? Yeah, I flashed some Custom Roms and Kernels, if you need this information.
And no, there aren't any bugs recently. No bootloops or crashes.
Click to expand...
Click to collapse
Only flash firmware so as per info of hardware Samsung sticker behind the battery.
Hello All,
I have a small problem. if anyone can help me out please help.
Recently I cracked my screen and hence went to a local shop to get it replaced. Once replaced my phone was not booting. I thought it maybe a software issue. Later I realized this happens due to hardware and maybe some connection is not made, like the headphone jack.
I opened my nexus and checked. Turns out that guy dropped my light sensor which is close to the front camera. There is no light sensor now in the phone. I cannot go back to him.
Can anyone please suggest me some ROM which skips this hardware test? or any other solution please?
From what i remember, proximity sensor causes such issue on Nexus 4. The solution was to downgrade modem to the very first one (from 4.2.2 factory image) and then flash either 4.2.2 or 4.3 stock firmware. Switching modem to a newer one causes bootloop on 4.3 and up. Try this, then it's possible that some more current custom ROM will work with an old modem as well, but that's something you'll have to check on your own.
THANK YOU!
Sir,
Thanks A LOT!
I cannot thank you enough. I have search everywhere, and your solution worked. I installed 4..2.2 radio then pre rooted factory image. Worked like charm
I am really grateful. Thank you.
KrzychuG said:
From what i remember, proximity sensor causes such issue on Nexus 4. The solution was to downgrade modem to the very first one (from 4.2.2 factory image) and then flash either 4.2.2 or 4.3 stock firmware. Switching modem to a newer one causes bootloop on 4.3 and up. Try this, then it's possible that some more current custom ROM will work with an old modem as well, but that's something you'll have to check on your own.
Click to expand...
Click to collapse