I seem to be having an issue with the proximity sensor on CM7 build 116. It was working perfectly. Suddenly, whenever in a call, the screen on my SGS2 would turn off as it was supposed to but then never turn on again. The only way to get the screen back on was to hard reboot the phone. I installed Z-DeviceTest and sure enough, the proximity sensor reads as constantly a distance of 0 (i.e. something covering the proximity sensor). If anyone knows a way to calibrate the proximity sensor or for a fix for this issue that would be GREATLY appreciated.
Thanks.
Update: Found a post somewhere that said the issue could be fixed by cleaning the screen really well. Took out the old microfibre cloth and voila, proximity sensor works again.
Hi all,
Anyone still got this build, esp 116..... As it appear to be the only one working on i9100 allegedly...
Thanks, Lister
rcfcyl said:
I seem to be having an issue with the proximity sensor on CM7 build 116. It was working perfectly. Suddenly, whenever in a call, the screen on my SGS2 would turn off as it was supposed to but then never turn on again. The only way to get the screen back on was to hard reboot the phone. I installed Z-DeviceTest and sure enough, the proximity sensor reads as constantly a distance of 0 (i.e. something covering the proximity sensor). If anyone knows a way to calibrate the proximity sensor or for a fix for this issue that would be GREATLY appreciated.
Thanks.
Update: Found a post somewhere that said the issue could be fixed by cleaning the screen really well. Took out the old microfibre cloth and voila, proximity sensor works again.
Click to expand...
Click to collapse
Lister Of Smeg said:
Hi all,
Anyone still got this build, esp 116..... As it appear to be the only one working on i9100 allegedly...
Thanks, Lister
Click to expand...
Click to collapse
What about the cm-7-20120722-NIGHTLY?
Hi @gsstudios,
You seem to be the most active person on here, thanks for coming to my support/rescue again...
Yeah, I've tried that one... I've tried that, and a couple of others from that page (all CM7.x releases) and after I've flashed them, they all just bootloop with the Samsung logo....
What's more annoying than it just not booting, is that it appears to remove any kind of recovery... As you can't get back into it, to flash anything else. And so have to enable Download mode and flash a kernel with Odin to be able to wipe and try / start summit else...
I've tried, 'the various solutions'
1) All the normal wipes
2) Flashing the rom twice
3) Returned the phone back to official stock PITs, it's even running stock (Android 4.1.2) OS at moment.
Just can't get it to boot....?? What's odd, I have actually had it running on this phone at some point... When it didn't belong to me. And that's the whole reason I purchased it off my friend, so I can go back to CM7, as well as keep upto date with all the Lollipop jazz...
Very odd, don't know what I did last time that made it work... As I just flashed it normally when the phone didn't belong to me... Didn't do anything fancy....
Also, is there a difference on CM's website between i9100 and galaxys2 listings...? (not that it helps, as one of the branches doesn't even have the files). Just seems odd to have 2x international versions... I can understand if it said i9100G or something, but they both seem the same... Perhaps I downloaded a different CM7 rom at the time...??
Thanks, Lister
gsstudios said:
What about the cm-7-20120722-NIGHTLY?
Click to expand...
Click to collapse
Lister Of Smeg said:
Hi @gsstudios,
You seem to be the most active person on here, thanks for coming to my support/rescue again...
Yeah, I've tried that one... I've tried that, and a couple of others from that page (all CM7.x releases) and after I've flashed them, they all just bootloop with the Samsung logo....
What's more annoying than it just not booting, is that it appears to remove any kind of recovery... As you can't get back into it, to flash anything else. And so have to enable Download mode and flash a kernel with Odin to be able to wipe and try / start summit else...
I've tried, 'the various solutions'
1) All the normal wipes
2) Flashing the rom twice
3) Returned the phone back to official stock PITs, it's even running stock (Android 4.1.2) OS at moment.
Just can't get it to boot....?? What's odd, I have actually had it running on this phone at some point... When it didn't belong to me. And that's the whole reason I purchased it off my friend, so I can go back to CM7, as well as keep upto date with all the Lollipop jazz...
Very odd, don't know what I did last time that made it work... As I just flashed it normally when the phone didn't belong to me... Didn't do anything fancy....
Also, is there a difference on CM's website between i9100 and galaxys2 listings...? (not that it helps, as one of the branches doesn't even have the files). Just seems odd to have 2x international versions... I can understand if it said i9100G or something, but they both seem the same... Perhaps I downloaded a different CM7 rom at the time...??
Thanks, Lister
Click to expand...
Click to collapse
Galaxys2 was the old name used for our device by cm. Now its i9100 which is the actual name for our phone. Galaxys2 has all of the old builds of cm, while i9100 has all of the newer builds. Other than that, its for the same device.
Sorry. I can't help you with the cm 7 build you are trying to find.
Hi @gsstudios,
Ah I see, I did wonder why there was 2x seperate branches for the same device... I could understand if one was for the HD or the LTE version, but I guess they already have their own variant name in CM already... Just thought it was odd to have 2x i9100 builds going on together.... lol
Anyway, regarding CM7.... I've finally managed to get it to work!!!! YIPPIE!!!!!!! Finally... Although I swear it wasn't as hard as this when the phone DIDN'T belong to me, and I did it as a test for my mate... But anyway, got it installed and loving it... It's nice to go back once in a while to where it all began (well, for me anyway.... My first device came with Android eClair, I think Android 2.1 or summit??) But CM7.x was my first custom OS ever installed on ZTE Blade.
It would seem all the CM7 builds that I can find, both on CM site, and other hosts are all BORKED (broken) and that they lack Boot info, hence the BootLoops... and that all their recoveries are broken, as not a single one would go back into recovery after flash, had to Odin it back to life with a PC. Not cool if ya gone out for the day... lol So basically I found some random GB kernel, and flashed that after CM7 + GApps + Recovery.... and thank the lord, it all boots again...
I'd just like to THANK YOU, for always consistently and continually coming to my support needs..... Your help/advice has been extremely helpful.... thanks
Lister
gsstudios said:
Galaxys2 was the old name used for our device by cm. Now its i9100 which is the actual name for our phone. Galaxys2 has all of the old builds of cm, while i9100 has all of the newer builds. Other than that, its for the same device.
Sorry. I can't help you with the cm 7 build you are trying to find.
Click to expand...
Click to collapse
Related
So, I recently got my S2 (YAY!).
I flashed the latest SlimICS (at the time), which was the one before 4.1...
I also flashed Siyah Kernal.
Since I updated to the latest SlimICS version, I am getting issues with Data & Tethering. If I enable them both, data starts jamming (only on the up arrow), and it won't work. I turn off data, and the tether turns off aswell!
I turn them all back on, but the same happens.
It must take me like, 6 tries to make it work correctly
Any ideas? I don't think this was happening on the old SlimICS!
Hello there,
All of those Slim ROM-s are lightened by removing that components because it taking so many room.
Try with some nonSlim ROM...
Cheers
tomasher said:
Hello there,
All of those Slim ROM-s are lightened by removing that components because it taking so many room.
Try with some nonSlim ROM...
Cheers
Click to expand...
Click to collapse
Like a cm Rom? Will do
EDIT: Ok, did the same on the CM9 rom, so I was thinking - maybe it is a kernel bug? So, I re-flashed SlimICS zip, (to override the SiyahKernal), and SHAZAM! It seems to be working again :/
lol well good to see you got it working again... but maybe next time you try asking in the Slim Rom thread (because most users don't check in here).
That goes for any rom -- it's best to ask in their thread for more help and answers (most users don't look into here - I do once in a blue moon).
Hi,
We have 2 Vibrant phones. 1 is on Paranoid Android 2.54 (via stock eclair, ICS Passion, Slim Bean 2.9 & 3.0) and works perfectly.
The second one was on ICS Passion for a long time and I have finally got around to (trying LOL) to update it.
Here is where the weirdness begins - Flashed PA 2.54 no problems, flashed and booted up, but no wi-fi, well no wi-fi icon, and it can find a couple of wi-fi networks belonging to my neighbours, but won't find my network, 2 rooms away. The network is obviously all good, I am sending this from my laptop through said network.
Obviously I need an internet connection to get through the phone setup, so I power down, throw the SIM back in and boot up only to find no cell data either.
Skip the google account setup and get to the home screen to check things further and I find:
Calls in/out work, and most things are running, but wi-fi won't co-operate, and nothing in the APN list? Baseband and IMEI all look normal, too.
Try to flash Slim Bean 2.9 as I put the zip on the phone at the same time as a fallback and I get EXACTLY the same thing...
Anyone able to shed any light on what would cause this? Anything else worth trying? I'd like to avoid Odin as it honestly scares me reading all the problems people on here have with it...
At this point I've tried flashing both ROMs a few times with exactly the same results, I also can't go back to the ICS nandroid as the partition setup has changed and the restore doesn't work...
Thanks in advance for any help anyone can give.
Cheers...
I ended up flashing a 4.2 ROM (slim 4.2 beta 1) and it made the problem go away, I'm guessing something in the 4.1 base was broken and not getting overwritten on new installs?
ROM seems pretty sorted for a beta, few minor things not working, but hopefully it gives us a clean upgrade path...
Thanks.
I had the same issue with Slim 4.2 Beta 2. If anyone has a solution other than flashing the modem, please post.
Weird. The phone I was having this problem with now has that ROM on it and is working 100%.
I have a suspicion that flashing a ROM that uses a different kernel is what fixed it for us. I guess it just overwrites/replaces more stuff?
Maybe try hellybean 4.2 and see if it makes a difference, and if it does flash back to slim 4.2 and see if the problem comes back?
I have installed slim and other ROMs but not had this issue. Currently on jellybam
Sent from my GT-I9300 using xda premium
wendleburger said:
Weird. The phone I was having this problem with now has that ROM on it and is working 100%.
I have a suspicion that flashing a ROM that uses a different kernel is what fixed it for us. I guess it just overwrites/replaces more stuff?
Maybe try hellybean 4.2 and see if it makes a difference, and if it does flash back to slim 4.2 and see if the problem comes back?
Click to expand...
Click to collapse
The weird part is that every other Slim Bean has worked great. I'll keep my fingers crossed for beta 3.
Hello XDA! I have been a keen follower of this forum for long, but this is my first post, 'cause well... this is the first time I pretty stuck at something.
I have a Xperia Mini Pro (SK17i) and I have been using it for quite a while, around 2 years I presume. I have rooted and unlocked the bootloader by the end of the first year, and have been trying out several custom roms, until stopping at CM10.1 of LegacyXperia. (the amazing creation of Mike for our 2011-line of devices!) However, as of a month back, my touchscreen kinda broke - it wouldn't respond along with the capacitive buttons. I tried the methods mentioned in the general section, but no avail - it simply wouldn't work at all. There's a thin small strip that appears around the screen during pulling out the hardware keyboard, and I guess that somewhat suggests that the touchscreen is invalid by hardware means.
However, that's merely a background to the problem I'm facing. Recently, after the launch of CM11, I thought of giving it a swing, seeing how I have been an avid-fan of the pure look of CM. I tried flashing the kernel using flashtool and start the phone, but the only thing that takes place is just a vibration and a black screen. The screen remains black for like ever, until I pull out the battery. I tried flashing the kernel thrice, and the same problem persisted all through. I reverted back to the stock ICS then and it worked like a charm, and the same goes for FXP CM10 and the last CM10.1 I used... there's no problem whatsoever, save for the broken touchscreen.
Any suggestion one might give about my problem? Thanks a ton for reading out everything!
psychoticdemon said:
Hello XDA! I have been a keen follower of this forum for long, but this is my first post, 'cause well... this is the first time I pretty stuck at something.
I have a Xperia Mini Pro (SK17i) and I have been using it for quite a while, around 2 years I presume. I have rooted and unlocked the bootloader by the end of the first year, and have been trying out several custom roms, until stopping at CM10.1 of LegacyXperia. (the amazing creation of Mike for our 2011-line of devices!) However, as of a month back, my touchscreen kinda broke - it wouldn't respond along with the capacitive buttons. I tried the methods mentioned in the general section, but no avail - it simply wouldn't work at all. There's a thin small strip that appears around the screen during pulling out the hardware keyboard, and I guess that somewhat suggests that the touchscreen is invalid by hardware means.
However, that's merely a background to the problem I'm facing. Recently, after the launch of CM11, I thought of giving it a swing, seeing how I have been an avid-fan of the pure look of CM. I tried flashing the kernel using flashtool and start the phone, but the only thing that takes place is just a vibration and a black screen. The screen remains black for like ever, until I pull out the battery. I tried flashing the kernel thrice, and the same problem persisted all through. I reverted back to the stock ICS then and it worked like a charm, and the same goes for FXP CM10 and the last CM10.1 I used... there's no problem whatsoever, save for the broken touchscreen.
Any suggestion one might give about my problem? Thanks a ton for reading out everything!
Click to expand...
Click to collapse
The kernel is incompatible with your phone.
Care to explain a little more? I have flashed the kernel provided within the rom zip itself (as suggested time and time again), and I have double checked its for the correct device - i.e. mango.
psychoticdemon said:
Care to explain a little more? I have flashed the kernel provided within the rom zip itself (as suggested time and time again), and I have double checked its for the correct device - i.e. mango.
Click to expand...
Click to collapse
kernel is for mango??unofficial port right...can you provide the rom link once.....??
http://forum.xda-developers.com/showthread.php?t=2545367
This is the one - LegacyXperia CM11 by mikeioannina.
psychoticdemon said:
http://forum.xda-developers.com/showthread.php?t=2545367
This is the one - LegacyXperia CM11 by mikeioannina.
Click to expand...
Click to collapse
yeah i though so...was going through the post...did you try this..
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
As the rom requires a new partition table and maybe system and userdata is conflicting...
Dark Wraith said:
yeah i though so...was going through the post...did you try this..
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
As the rom requires a new partition table and maybe system and userdata is conflicting...
Click to expand...
Click to collapse
Thanks a lot for pointing it out, mate! Usually the roms I tried didn't require such a thing, but this might be it. I'll provide feedback if the steps works.
I tried the steps advised, but the problem seems to still persist to some extent. The capacitive lights are lit and the screen is lit as well (as could be understood from the viewing angles - it's brighter and powered up). Nothing seems to appear on the screen though - no boot logo or anything - and trying to enter recovery fails as well (through power + vol up shortcut). I have tried it twice already, kept the phone switched on for five minutes or so, but no avail. I had to pull battery out every time to shut down the device. Anyone have any other advice?
psychoticdemon said:
I tried the steps advised, but the problem seems to still persist to some extent. The capacitive lights are lit and the screen is lit as well (as could be understood from the viewing angles - it's brighter and powered up). Nothing seems to appear on the screen though - no boot logo or anything - and trying to enter recovery fails as well (through power + vol up shortcut). I have tried it twice already, kept the phone switched on for five minutes or so, but no avail. I had to pull battery out every time to shut down the device. Anyone have any other advice?
Click to expand...
Click to collapse
try this.....Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
then see if device powers up...
once it does...go for the next steps........
Dark Wraith said:
try this.....Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
then see if device powers up...
once it does...go for the next steps........
Click to expand...
Click to collapse
Thanks for the quick response, but I tried that too. Unfortunately, the problem still seems to persist.
psychoticdemon said:
Thanks for the quick response, but I tried that too. Unfortunately, the problem still seems to persist.
Click to expand...
Click to collapse
I wonder if its a hardware related issue...you said in your op that there is some problem with your screen and capacitive buttons...Got any friend with sk17i???? I had one before it was stolen......Every other rom apart from CM11 is working right..Is there any other Kitkat based ROM for sk17i..if its there you may try that out and see if you have the same problem...otherwise..wait for a kitkat based rom to come up and try before flashing this...Try one more time from scratch...flash stock ICS 4.1.B.0.587 full ftf..reboot....once its working...fastboot flash boot.img...then better to fastboot erase system and fastboot erase userdata and then before it boots enter recovery and wipe data cache everything...flash update.zip..wipe cache,data,dalvik cache again...and boot..if it doesnt boot up then there is no option but to wait..
Dark Wraith said:
I wonder if its a hardware related issue...you said in your op that there is some problem with your screen and capacitive buttons...Got any friend with sk17i???? I had one before it was stolen......Every other rom apart from CM11 is working right..Is there any other Kitkat based ROM for sk17i..if its there you may try that out and see if you have the same problem...otherwise..wait for a kitkat based rom to come up and try before flashing this...Try one more time from scratch...flash stock ICS 4.1.B.0.587 full ftf..reboot....once its working...fastboot flash boot.img...then better to fastboot erase system and fastboot erase userdata and then before it boots enter recovery and wipe data cache everything...flash update.zip..wipe cache,data,dalvik cache again...and boot..if it doesnt boot up then there is no option but to wait..
Click to expand...
Click to collapse
Exactly. That's the whole reason why I posed this thread - to know if it was a hardware related problem right off the bat, or there was really something that I was doing wrong. I'll rather leave this one open to see if anyone have any other opinion about the matter. I really want to see what Kitkat looks like seeing how it's not available for my current device. (Micromax A210)
Also, about trying out other 4.4 roms... I guess I can try that route. But seeing how this problem is induced by the kernel itself and every other rom out there is mainly based off the LX 3.4 kernel, I doubt if that will work. I'll try the option anyway and see if it works.
psychoticdemon said:
Exactly. That's the whole reason why I posed this thread - to know if it was a hardware related problem right off the bat, or there was really something that I was doing wrong. I'll rather leave this one open to see if anyone have any other opinion about the matter. I really want to see what Kitkat looks like seeing how it's not available for my current device. (Micromax A210)
Also, about trying out other 4.4 roms... I guess I can try that route. But seeing how this problem is induced by the kernel itself and every other rom out there is mainly based off the LX 3.4 kernel, I doubt if that will work. I'll try the option anyway and see if it works.
Click to expand...
Click to collapse
Yeah.....waiting for other roms wont work.....cz they are all based on 3.4.x kernel.......Umm can you check your baseband after flashing full ftf...baseband should be : 8x55A-AAABQOAZM-203028G-77..every other rom based on 3.4.x kernel works right???...btw if you want to see how it looks just download a kitkat launcher from playstore....
Yes, the baseband is .77 after flashing the ICS 4.1.0.B.587. I used 3.4.x kernel with CM10.1, but never really tried CM10.2 to that extent. Maybe I'll try downloading that and see if it works... or even the EOL CM10.1.
And sure, the launcher would give in the feel, but I want the full experience possible really.
Hello first of all I would like to thank all the great developers for the great ROMs out there.
Second I would like to warn everyone that this is a "first world problem rant" that I'm about to write up with a legit frustration I have.
I have a rooted Samsung Galaxy S4 from ATT and the only reason I got this phone over any other Android phone is the great camera and the screen.
I absolutely hate TouchWiz. It's bloated, slow and painfully ugly (to me). For this reason I decided to try out Flashing roms.
For the last couple of weeks (months maybe?) I have been using Cyanogenmod 10.1 stable with not many problems. Mostly camera issues but no biggie.
My frustration is the following: CyanogenMod has had two stable updates for my phone to go from 10.1 to 10.2 and, though it flashes perfectly, every time I reboot the phone the phone gets stuck on the "Samsung Custom (lock)" screen and I am forced to go into TWRP and reflash 10.1+Gapp from my SD carfd.. This happens EVERY TIME. With CM10.1 I can restart the phone just fine by the way. It's 10.2 and other Roms that make get stuck on the Samsung Custom (lock) screen.
So i decided to try out Gummy ROM because Kit Kat
I put the ROM in my SD card, Formated, Wiped and Installed. Worked like a charm until the camera wasnt working that well. I read the forums and said to restart to fix the camera.. Guess what?...AGAIN....Stuck on Samsung Custom (lock) screen.
My frustrations is that pretty much EVERY Rom that I have tried minus CM10.1 has done this to me and I have no idea what I'm doing wrong.
I have tried battery pulls, waiting 30 seconds, wiped dalvik, cache, etc. Fixed Permissions....everything and I have to reflash the ROMs almost 99% of the time unless I use CM10.1. I am tired of reading forums to fix this so here I am asking for your help.
/endrant
I have no idea what else to do so any help would be great.
INFO:
Current ROM: Gummy 1.1-11-21-13-UNOFFICIAL
Android 4.4
Baseband version
I3377UCUAMDL
Kernel Version
3.4 g0-Elite-Kernel-ga719cb
Build Number:
KRT16S
Google Apps:
Gapps-Kk-20131113.Zip
TWRP Version
I have no idea and I'm not about to restart phone and go through the pain of reflashing the ROM again as I just did. I will punch so many babies if I have to do this again!'
Thanks for listening.
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
9859834534
prsterero said:
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
Click to expand...
Click to collapse
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Speedsterspeed277 said:
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Click to expand...
Click to collapse
It could be. There have been people that get weird issues with twrp so you may want to test out a different recovery to see if the issue persists.
prshosting.org
Hi. I've got a challenge for the experts
I have a galaxy s4 (i9505) and currently on cyanogenmod 11-20140414-nightly so its running on 4.4.2
The minute i got my phone, i put foxhound rom and was on4.2.2 that time and everything was fine. It was about june last year. A couple of weeks ago, i decided to have a go at other roms or update to 4.4.2 so i tried foxhound rom that ran on4.4.2. This is when the problems started. The first problem was the signal was greatly affected that i could not get any signal indoors. So i tried several other roms like omega rom, cyanogenmod, wanamlite, wicked, virgin rom and several others but none of them perfectly worked. I always cleared cache and restore factory settings but still there were problems. On some roms the camera wont work as if there is another app using it. On others, i cant get any signal even though im in an area where i used to get strong signals. Another big problem is that i cant make a call! The screen goes black and can't do anything until the call gets disconnected. I can't use voice services like skype, ym, everything that uses the mic as if there is an app or service using it. When i put the jack to use the headset, i dont get the notification that im on headset unlike before.
So i decided to use stock rom on 4.3. Now i have even bigger problems. In addition to the previous problems stated, the wifi won't turn on but i can get a signal outside. Even though i have already removed the microsd card and wiped cache and restore to factory settings, the phone still says that the device was modified so i can't really return it even though it is still under warranty.
So now i decided to root it again and temporarily use cyanogenmod since the wifi works, texts and the internet works.
Btw, youtube doesnt work also. It doesnt play.
Sorry for the vrry long post but i just want to give much info as possible..
Thanks so much
Noypi14 said:
Hi. I've got a challenge for the experts
I have a galaxy s4 (i9505) and currently on cyanogenmod 11-20140414-nightly so its running on 4.4.2
The minute i got my phone, i put foxhound rom and was on4.2.2 that time and everything was fine. It was about june last year. A couple of weeks ago, i decided to have a go at other roms or update to 4.4.2 so i tried foxhound rom that ran on4.4.2. This is when the problems started. The first problem was the signal was greatly affected that i could not get any signal indoors. So i tried several other roms like omega rom, cyanogenmod, wanamlite, wicked, virgin rom and several others but none of them perfectly worked. I always cleared cache and restore factory settings but still there were problems. On some roms the camera wont work as if there is another app using it. On others, i cant get any signal even though im in an area where i used to get strong signals. Another big problem is that i cant make a call! The screen goes black and can't do anything until the call gets disconnected. I can't use voice services like skype, ym, everything that uses the mic as if there is an app or service using it. When i put the jack to use the headset, i dont get the notification that im on headset unlike before.
So i decided to use stock rom on 4.3. Now i have even bigger problems. In addition to the previous problems stated, the wifi won't turn on but i can get a signal outside. Even though i have already removed the microsd card and wiped cache and restore to factory settings, the phone still says that the device was modified so i can't really return it even though it is still under warranty.
So now i decided to root it again and temporarily use cyanogenmod since the wifi works, texts and the internet works.
Btw, youtube doesnt work also. It doesnt play.
Sorry for the vrry long post but i just want to give much info as possible..
Thanks so much
Click to expand...
Click to collapse
So, which type of rom do you want to be on, assuming most of the things work properly? I don't want to try to address all those issues because there are different ones for the different setups and would take forever. Most likely signal issues are from not using a matched modem with the firmware / rom you are running. Do you know the original carrier / region the phone is from so we can make sure you get the right stuff installed?
Please provide details on the the currently installed baseband version. Also, what is the last official version of Samsung's software that you installed via Odin or OTA (not via custom rom)?
es0tericcha0s said:
So, which type of rom do you want to be on, assuming most of the things work properly? I don't want to try to address all those issues because there are different ones for the different setups and would take forever. Most likely signal issues are from not using a matched modem with the firmware / rom you are running. Do you know the original carrier / region the phone is from so we can make sure you get the right stuff installed?
Please provide details on the the currently installed baseband version. Also, what is the last official version of Samsung's software that you installed via Odin or OTA (not via custom rom)?
Click to expand...
Click to collapse
Thanks for your reply.
The current cyanogenmod is fine although i prefer the virgin rom. but i can go back to virgin once the problems have been rectified.
I agree that the signal issue has something to do with the modem so i tried different modems using odin but the XXUBMEA wouldnt change despite trying several modems and several times.
The phone is on three network (uk) with its current baseband 19505XXUBMEA.
The official rom i tried was on 4.3 and kies said it was the latest
Thanks again
Alright, I'm with ya so far. I'll look into the rom situation when I get back in front of the PC, but the trick with updating the modem is you gotta flash it twice in a row before you reboot unless you flash official firmware.
es0tericcha0s said:
Alright, I'm with ya so far. I'll look into the rom situation when I get back in front of the PC, but the trick with updating the modem is you gotta flash it twice in a row before you reboot unless you flash official firmware.
Click to expand...
Click to collapse
Thanks again for replying.
What i havent actually tried (which i'm reading at the moment) is the formatting of data under the advanced options on twrp. I dunno if it will make a difference say i try a new rom. I don't mind trying and starting from scratch. Like format data then install a new rom. Do u think this will make a difference? (will this be similar to formatting a dard drive on a pc before installing windows?)
What i suspect is there is nothing wrong with the roms i've tried but something in the installation got messed up and remains there even after wiping the data.
I think i have tried doing it twice only to find out that it didnt change the modem despite odin saying pass.
Should i format data then install a fresh rom?
Hard
but challeng refused
Ok, so there is something odd here. If you had flashed the official 4.3 via Odin, your modem would have changed to a newer one. The one you have is still a 4.2.2 one. Or were you referring to the last stock rom that you loaded with a custom recovery? Also, which recovery are you using?
Try this modem via Odin:
http://d-h.st/Kwv
Install Guide:
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Reference thread: http://forum.xda-developers.com/showthread.php?t=2192025
Let's see if that doesn't help anything and go from there.
If you have issues with wifi, there is a wifi fix to be had in the reference thread. Remember to flash that through the Phone slot if needed.
thanks again.
i can't exactly remember what modem i had when i flashed it with the official 4.3 using odin. but my guess would be the XXUBMEA. most of the custom roms i've tried had this modem anyway. some had no problems with 3g signal.
i am using twrp.
i don't want to play around with the modem yet as the 3g and wifi signals are working fine on cyanogenmod. its the call and video that's not working that i want to sort out.
do u think if i reflash by formatting data would clear out the problems i specified earlier? i don't mind trying this if u think it will make a difference.. tthanks.
es0tericcha0s said:
Ok, so there is something odd here. If you had flashed the official 4.3 via Odin, your modem would have changed to a newer one. The one you have is still a 4.2.2 one. Or were you referring to the last stock rom that you loaded with a custom recovery? Also, which recovery are you using?
Try this modem via Odin:
http://d-h.st/Kwv
Install Guide:
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Reference thread: http://forum.xda-developers.com/showthread.php?t=2192025
Let's see if that doesn't help anything and go from there.
If you have issues with wifi, there is a wifi fix to be had in the reference thread. Remember to flash that through the Phone slot if needed.
Click to expand...
Click to collapse
Noypi14 said:
thanks again.
i can't exactly remember what modem i had when i flashed it with the official 4.3 using odin. but my guess would be the XXUBMEA. most of the custom roms i've tried had this modem anyway. some had no problems with 3g signal.
i am using twrp.
i don't want to play around with the modem yet as the 3g and wifi signals are working fine on cyanogenmod. its the call and video that's not working that i want to sort out.
do u think if i reflash by formatting data would clear out the problems i specified earlier? i don't mind trying this if u think it will make a difference.. tthanks.
Click to expand...
Click to collapse
The custom roms you've been using don't install a modem with them, so that would be why you've been on the same one for a bit. Often times the stock rom is a little more picky about which modem it likes best, though this varies by phone and update. What call issues are you having? There were so many issues listed for various things on the first post that I had trouble sorting which problem for which rom (not criticizing, just making sure we're on the same page). And as far as videos go, is it just YouTube that isn't working right or any type of video playback? If it is just YouTube - is it force closing, not loading searches or videos, or some other problem?
es0tericcha0s said:
The custom roms you've been using don't install a modem with them, so that would be why you've been on the same one for a bit. Often times the stock rom is a little more picky about which modem it likes best, though this varies by phone and update. What call issues are you having? There were so many issues listed for various things on the first post that I had trouble sorting which problem for which rom (not criticizing, just making sure we're on the same page). And as far as videos go, is it just YouTube that isn't working right or any type of video playback? If it is just YouTube - is it force closing, not loading searches or videos, or some other problem?
Click to expand...
Click to collapse
thanks again for your interest.
the issue about the modem is somehow clear. thanks for clearing that up.
i think it is better to tackle the problems i have in my current setup rather than the previous problems. so, as previously mentioned, i am on cyanogenmod 11 (on 4.4.2). here are some of the problems i am aware of or rather, those that i have experienced:
1. calls - whenever i dial a number, the screen goes black as if the phone is next to my ear (could there be something wrong with the proximity sensor? i haven't done anything to rectify this yet though. when this happens, i can't do anything as the seems to hang although i could see the call timer working. during that call however, i can't hear a sound nor the person i just rang. same thing happens when someone calls me. my phone vibrates (because there is another problem with the sound which i will discuss next) and when i answer it, i hear no sound and the screen goes black and i couldn't do anything with the phone. i have to wait till the caller disconnects before the phone becomes useable again.
i tried calling using viber and the same thing happens.
2. sound - phone is muted even though all the volume controls are midway or almost 100%. i tried changing the ringing tone but i don't hear any sound at all. normally, when i switch to a different ringtone, it should give me a preview of what the chosen sound is like.
3. videos - it doesn't work. when i go to youtube, it opens up the site, opens the selected youtube clip, tries to play it but pauses then tries to play again then pauses until i get a message saying "there was a problem while playing. touch to retry."
so far these are the problems i have faced.
sorry for the long post again.
Hmm. Seems weird that you are having so many issues that most others aren't having, at least not since some of the earlier builds. During the install of CM, did you wipe /system? If not, I definitely would just start fresh. Install the most up to date modem. Wipe everything (system, data, cache, dalvik). Use the most up to date CWM (I like TWRP most of the time, but since CM says you should try CWM before reporting issues, it's one of those things...) Some Samsung proximity sensors aren't that accurate and really don't work well with CM. Other users reported that issue i the main CM thread for your phone, but was definitely not prevalent. I had a Samsung phone that I couldn't use a tempered glass screen protector with as they had an app to install to test to see how sensitive it was and mine didn't pass the test, though it worked for everything else.
As far as the video bug. It affected some earlier builds and other roms based off of CM but I hadn't seen anyone commenting about it for a bit so can't imagine it still being a common issue as that's a deal breaker for most. It might just be easier at this stage to either go back to stable CM 10.2 or try another rom altogether, such as Slim.
es0tericcha0s said:
Hmm. Seems weird that you are having so many issues that most others aren't having, at least not since some of the earlier builds. During the install of CM, did you wipe /system? If not, I definitely would just start fresh. Install the most up to date modem. Wipe everything (system, data, cache, dalvik). Use the most up to date CWM (I like TWRP most of the time, but since CM says you should try CWM before reporting issues, it's one of those things...) Some Samsung proximity sensors aren't that accurate and really don't work well with CM. Other users reported that issue i the main CM thread for your phone, but was definitely not prevalent. I had a Samsung phone that I couldn't use a tempered glass screen protector with as they had an app to install to test to see how sensitive it was and mine didn't pass the test, though it worked for everything else.
As far as the video bug. It affected some earlier builds and other roms based off of CM but I hadn't seen anyone commenting about it for a bit so can't imagine it still being a common issue as that's a deal breaker for most. It might just be easier at this stage to either go back to stable CM 10.2 or try another rom altogether, such as Slim.
Click to expand...
Click to collapse
i know. i don't really want to blame these issues i've mentioned to the rom i am using or have tried. perhaps there was something i did not do or overdid that messed it all up. the cynagenmod 10 (the stable version for my s4 model) had similar issues as the cm11. so i suspect the problem i've created still lingers within my phone that messes up a lot of things.
during installation, i did wipe the system, data, cache and dalvik which i found in the advanced menu.
the thing is, everything else worked fine when i was on 4.2.2 (like the proximity sensors, videos, sounds, etc) so as i said earlier, i don't want to blame it on the roms.
i might have another go on the slim rom tonight but use CWM instead of TWRP.
thanks again for your interest and help
Noypi14 said:
i know. i don't really want to blame these issues i've mentioned to the rom i am using or have tried. perhaps there was something i did not do or overdid that messed it all up. the cynagenmod 10 (the stable version for my s4 model) had similar issues as the cm11. so i suspect the problem i've created still lingers within my phone that messes up a lot of things.
during installation, i did wipe the system, data, cache and dalvik which i found in the advanced menu.
the thing is, everything else worked fine when i was on 4.2.2 (like the proximity sensors, videos, sounds, etc) so as i said earlier, i don't want to blame it on the roms.
i might have another go on the slim rom tonight but use CWM instead of TWRP.
thanks again for your interest and help
Click to expand...
Click to collapse
Do you have a screen protector or anything like that? Sometimes if it isn't laying on the screen right or dirt gets around it, it can cause issues. There's also a way to pop out the actual proximity sensor and clean between the part and the little piece of clear glass on the back of the front piece of glass that can help too if it ends up being hardware related.
es0tericcha0s said:
Do you have a screen protector or anything like that? Sometimes if it isn't laying on the screen right or dirt gets around it, it can cause issues. There's also a way to pop out the actual proximity sensor and clean between the part and the little piece of clear glass on the back of the front piece of glass that can help too if it ends up being hardware related.
Click to expand...
Click to collapse
I put the screen protector when i got the phone and i don't see any visible dirt so i wouldn't want to blame it either. Although i did read about the screen protectors causing problems. But the thing is, even youtube or any videos do not play. Even any sound.
I've tried the slimkat rom by following the developers' instructions and still no youtube, no sound, can't make a call as i can't hear the person i'm calling nor can that person hear me.
Any other suggestions on what to do? I don't mind going back to stock as long as i get all the features back. I went to official 4.3 before but had more severe issues. Or perhaps i did it wrong?
Thanks..
Videos are another issue, but I still think the call problems and such are modem related. What I would do would be to wipe everything, then use Odin to install official Kit Kat, then test this stuff out and see if it works. If so, then you can do a nandroid and redo recovery and try the roms again, then if they still have that issue then your phone just doesn't cooperate with CM roms or something weird like that. If it doesn't work even after official 4.4.2, then there's probably something else going on, possibly hardware related.
es0tericcha0s said:
Videos are another issue, but I still think the call problems and such are modem related. What I would do would be to wipe everything, then use Odin to install official Kit Kat, then test this stuff out and see if it works. If so, then you can do a nandroid and redo recovery and try the roms again, then if they still have that issue then your phone just doesn't cooperate with CM roms or something weird like that. If it doesn't work even after official 4.4.2, then there's probably something else going on, possibly hardware related.
Click to expand...
Click to collapse
Thanks.
Got hold of the official 4.4.2 and flashed it via odin. Failed. But tried again and now working fine. Sound is back, video is back as well as calls. Just the annoying google search failing all the time.
The baseband it has is I9505XXUFNC9. i didn't install any modem in odin though. Just flashed in the pda section the tar file
Now i don't know whether to root this again and try custom roms or leave it as it is. I saw knox by the way but haven't installed it. Or is it pre installed? I have little knowledge about knox