http://forum.xda-developers.com/note-4/help/n910t-touchscreen-registering-touch-t3144309
I was able to fix this issue on stock firmware with that code. However, I updated to this newer custom rom and I am having issues with USSD codes. None of them work. I just get "Connection problem or invalid MMI code".
I've been a user since 2011. Lurking around getting roms, I can't believe I still don't have 10 posts, so I can't post a reply on the main thread for the ROM. :/
If you mean the codes that you enter in the call app, they never work on a custom ROM I believe.
By the way, do you also encounter problems with the fingerprint sensor on Dr. Ketan ROM?
sunniebeta said:
If you mean the codes that you enter in the call app, they never work on a custom ROM I believe.
By the way, do you also encounter problems with the fingerprint sensor on Dr. Ketan ROM?
Click to expand...
Click to collapse
Yes, but the biggest problem is the touch response. I will have to roll back to official, I got a backup but the baseband is different so I would need the 5.0.1 baseband I had before.
Related
So, here I am trying to upgrade my phone to 4.3 and I installed Slimbean, CM 10.2 (or something along those lines) and AvatarROM and every single ROM based on CM (or maybe 4.3 in general) has an issue related to the touchscreen. The touch is basically not working. I've tried a lot of KDZs and none of them seems to do the trick. I've tried Slimbean and the touch isn't working, only the physical keys. I've noticed that if I flash to v10 baseband, I can get the touch to work, but it seems that I cannot use my SIM card. I saw that a lonely few other users cannot get this to work, but this is a problem with the ROM or version in general, it is very common.
So guys, can anyone help me? I've seem to have gotten this modding thing down in general, but this is the first time I'm having issues. I am prepared to give all the nececery data in order for this to be fixed, but that is all I know for now.
TL;DR Newest 4.3 CyanogenMod based ROMs touch not working with v20 baseband, only with v10 baseband. On the other hand with v10 baseband, the SIM isn't working and I don't want to use my phone as a tablet.
Thanks in advance, guys.
EDIT: THE ANSWER IS THAT V10/V20 baseband thing! I can feel it!
Do you flash it with a SIM in it? And with a microSD inserted too?
And first startup with thosse too
yes, indeed I did.
EDIT: One more question that I need answered. Do I need v10 or v20 in order for me to have Slimbean or CM 10.2?
soMVD said:
EDIT: One more question that I need answered. Do I need v10 or v20 in order for me to have Slimbean or CM 10.2?
Click to expand...
Click to collapse
You need v20
Do a boot without flashing gapps... Test and then flash gapps ....
Also did you try lock phone and unlock to test touch?
Sent from my LG-E610 using Tapatalk
I did try without gapps and it didn't help. The touch is still not working. Only the physical buttons are working (volume+, -, power and home). I tried a bunch of different solutions, but none of them seems to work. I have V20 on my phone (updated with the KDZ tool).
After I install the rom, I install v20 baseband and I get the SIM thing to enter the PIN but the touch ain't working. If I flash the V10 baseband after the ROM installation I get the touch working, but I can't use my SIM card and I don't want to use my phone as a tablet.
What is the exact model of yours?
How did you unlock bootloader / install cwm? Did you check that is for YOUR version?
raul338 said:
What is the exact model of yours?
How did you unlock bootloader / install cwm? Did you check that is for YOUR version?
Click to expand...
Click to collapse
on the back of mt phone it says E610/E612F
So, yes. It is for my version.
Hi all,
Since a couple of weeks i'm suffering from the following problem.
On newer roms the signal to my provider is lost upon waking up the phone (from standby/screen off).
A couple of things happened, i switched providers (from T-Mobile to Ziggo), i flashed a wrong modem which caused sound problems (from the omega rom 13.1). Since that moment i've had this problem. I'm not sure if its related to what happened, but that's what i know changed.
I've tried several modem files, though the modem version MI1 which works properly with Echoe v3, gives the same problems on Echoe v6, Omega 13.2 and Phoenix v5. Updating to XXUEMJ7 makes no difference at this point. I'm not quite sure whether its the modem at all due to this, but it seems the most obvious thing to look at when facing connection problems.
When the connection is active its working properly, i have data, i can call, receive SMS messages and everything. But press the off button once to lock the device, press it again to unlock it, and i see the signal status icon change to no connection.
At the moment with Omega 13.2 installed, its reconnecting quickly after i unlock my phone (something that didnt happen on the other roms), but it seems like very weird behavior. I've googled and searched the forums here for people with similar problems, but they've either not been documented yet, or i've been using the wrong keywords to find it.
Does anyone know what's going on, and how i can fix this?
Many thanks,
Amber
Amber-Willow said:
Hi all,
Since a couple of weeks i'm suffering from the following problem.
On newer roms the signal to my provider is lost upon waking up the phone (from standby/screen off).
A couple of things happened, i switched providers (from T-Mobile to Ziggo), i flashed a wrong modem which caused sound problems (from the omega rom 13.1). Since that moment i've had this problem. I'm not sure if its related to what happened, but that's what i know changed.
I've tried several modem files, though the modem version MI1 which works properly with Echoe v3, gives the same problems on Echoe v6, Omega 13.2 and Phoenix v5. Updating to XXUEMJ7 makes no difference at this point. I'm not quite sure whether its the modem at all due to this, but it seems the most obvious thing to look at when facing connection problems.
When the connection is active its working properly, i have data, i can call, receive SMS messages and everything. But press the off button once to lock the device, press it again to unlock it, and i see the signal status icon change to no connection.
At the moment with Omega 13.2 installed, its reconnecting quickly after i unlock my phone (something that didnt happen on the other roms), but it seems like very weird behavior. I've googled and searched the forums here for people with similar problems, but they've either not been documented yet, or i've been using the wrong keywords to find it.
Does anyone know what's going on, and how i can fix this?
Many thanks,
Amber
Click to expand...
Click to collapse
Hello,
Do not use roms based on mj7, use roms based on mj5 or go back to 4.2.2
I have tested all radios many kerneles with many mj7 based roms and always had this problem.
And use radio mj5 with mj5 roms likeecho illusion bobcat, visxii.
Get radio from here:
http://forum.xda-developers.com/showthread.php?p=39176955
Adam
Thank you, switching back now, I'll get back on if it succeeded
greenwitch said:
Hello,
Do not use roms based on mj7, use roms based on mj5 or go back to 4.2.2
I have tested all radios many kerneles with many mj7 based roms and always had this problem.
And use radio mj5 with mj5 roms likeecho illusion bobcat, visxii.
Get radio from here:
http://forum.xda-developers.com/showthread.php?p=39176955
Adam
Click to expand...
Click to collapse
Thanks! that seems to have worked!
Hi guys,
I was given a phone to use after I broke my own phone, but the problem is that its SIM locked to Vodafone IE.
When I got the phone, it was on 4.3. After following the SIM unlock guides, I kept running into problems because some menu items are missing. Specifically "[3]PERSO SHA256 OFF".
I did some Googling and saw a mention of the fact that the newer modem in 4.3 has these options removed. So this led me to try downgrade the ROM. The first thing I did here was TWRP/root/custom ROM, thinking that there might be some added options in a custom ROM. However, the ROM i Chose (Albe95 LolliROM) uses the hard menu button to display running tasks, so I couldnt perform the steps in the SIM Unlock guide. Then I tried other ROMs and an old CyanogenMod 4.2.2 ROM, but I didnt have any success. After more research, I found that the biggest mistake people make is not downgrading the modem. Now, I thought this wasn't possible once you go above a certain level, eg 4.3.
After more Googling, I found a link to an old modem, but the link gave me a 404!
I spent a lot of time on this, and just want the SIM unlocked, so figured I'd just ask the experts here.
So, can anyone just link me to the correct modem version for 4.2.2 and maybe a ROM that is compatible with the guide I linked earlier?
Once unlocked, I'll flash a new ROM so I'm on Lollipop again.
Thanks.
If the 9505 is like the 337m, the free unlock method only works when running a stock Samsung dialler. CM and aosp ROMs do not use a Samsung dialler so don't bother using a custom rom to try and sim unlock the phone. If you buy an unlock code, you will need to be running a stock Samsung dialler in order to enter the unlock code.
eoinzy said:
Hi guys,
I was given a phone to use after I broke my own phone, but the problem is that its SIM locked to Vodafone IE.
When I got the phone, it was on 4.3. After following the SIM unlock guides, I kept running into problems because some menu items are missing. Specifically "[3]PERSO SHA256 OFF".
I did some Googling and saw a mention of the fact that the newer modem in 4.3 has these options removed. So this led me to try downgrade the ROM. The first thing I did here was TWRP/root/custom ROM, thinking that there might be some added options in a custom ROM. However, the ROM i Chose (Albe95 LolliROM) uses the hard menu button to display running tasks, so I couldnt perform the steps in the SIM Unlock guide. Then I tried other ROMs and an old CyanogenMod 4.2.2 ROM, but I didnt have any success. After more research, I found that the biggest mistake people make is not downgrading the modem. Now, I thought this wasn't possible once you go above a certain level, eg 4.3.
After more Googling, I found a link to an old modem, but the link gave me a 404!
I spent a lot of time on this, and just want the SIM unlocked, so figured I'd just ask the experts here.
So, can anyone just link me to the correct modem version for 4.2.2 and maybe a ROM that is compatible with the guide I linked earlier?
Once unlocked, I'll flash a new ROM so I'm on Lollipop again.
Thanks.
Click to expand...
Click to collapse
You need to read the last pages of that thread. All you need to do is in there.
1. Be on a stock rom.
2. Downgrade modem.
3. Unlock sim.
4. Upgrade modem.
OK Thanks,
I managed to unlock!
I installed a stock ROM, downgraded modem to XXUAME2, did the unlock steps, and it worked fine.
I've flashed a custom ROM now and updated the modem to the latest so its all good now!
Cheers.
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!
Please any help would be appreciated! So I'm having some touch screen calibration issues after root and flashing TWRP + LineageOS. I search the forums and find that it can be fixed by dialling *#2663# and updating the firmware, but for whatever reason it doesn't work for my device. I tried other codes and find that none of them work at all on this device?? Do the codes normally stop working after root and will I need to flash back to stock firmware to get them back? The Phone Info App didn't work either. The SPen still works so at least the phone isn't totally unusable but it's still very irritating that nothing seems to fix this. Thanks in advance!
EDIT - I ended up fixing this by flashing stock Samsung firmware (marshmallow 6.0.1) via Odin. The code worked perfectly and I was able flash LineageOS again and it all works fine now! It was a little annoying to basically have to start all over but at least it's all good now lol. Cheers.
That's a Samsung code... you running a Samsung rom?
blackhawk said:
That's a Samsung code... you running a Samsung rom?
Click to expand...
Click to collapse
No, LineageOS rom. In the end I flashed back to stock Samsung firmware and the code worked lol. For future reference, does Lineage have its own secret codes?
aembo said:
No, LineageOS rom. In the end I flashed back to stock Samsung firmware and the code worked lol. For future reference, does Lineage have its own secret codes?
Click to expand...
Click to collapse
I don't know know for sure, but I couldn't easily find any. I leave the firmware alone unless it gets corrupted. In over 12 years that's never happened.
The big thing with Samsung's is never upgrade or update a OS that's fast, stable and fulfilling its mission. Upgrades/updates can and do break things...