Related
To allow Q&A to be separated from bugs/development - this is the Q&A thread for the I9100 Hellraiser found at http://forum.xda-developers.com/showthread.php?t=1335377
I intend to put FAQs here, along with keeping a list of tested ROMs. Keep general discussion here, and only use the other thread for bug reports and development.
In general: If it's listed as a known issue, and you don't have a fix, keep it out of the development thread. If you're not sure if it's Hellraiser-specific and common to multiple ROMs, keep it out of the development thread. In short, if you ask "Is this a bug?" in that thread, I will report it to the moderators. If you report a bug that is ROM-specific and not a Hellraiser issue, I will report those to the moderators starting tomorrow.
Tested ROMs:
I9100 XXKI3 Based:
SensatioN 1.8 by Crysis21 - Tested by myself with Alpha 0.2.1 - Fully working except 0.2.1 Known Issues, defaults to "good" AT&T APNs except for it has the "Broadband" APN which may cause the Tether Police to nail you if you tether. I suggest deleting that one.
VillainROM 3.0 + JKay Deluxe Themes v12 - Tested by myself with all versions, and my current "testbed"
I9100 XXKI4 Based:
CheckROM Revolution HD 2.0.0 - A few user reports indicate this may have WiFi issues when Hellraised similar to UCKJ2/J4 for I777
I9100 XWKJ2 Based:
CriskeloROM V30 + JKay Deluxe V12.1 - Reported by simpl3lang, seems to be working
If you have a report for a ROM, please indicate which I9100 firmware it is based on (XXKI3, XXKI4, etc.)
Also, I have seen reports that XWKK5 bases (like the latest CheckROM as of 1/8/2012) have the same issues with Bluetooth HID not working as UCKK6 - even when not Hellraised.
If someone posts a good, in-depth review of a ROM, I may link to it from this list. (Time permitting...)
Frequently Asked Questions:
Q: The home button lag is back, why?
A: The ROM has the annoying Vlingo double-tap support. Either smali it out (look for tips in the UnNamed ROM git repos, or look for a fix for that ROM.) - A commonly available fix may be flashing a JKay Deluxe Theme appropriate for the base of your ROM
Q: Home button haptic feedback is not working, why?
This is something that can't be "universally fixed" with Hellraiser. It must be modified in an individual manner for every ROM in android.policy.jar with some smali magic. It was the same deal with I9000 ROM ports to the Captivate.
Q: Where do I find themes/mods?
Look through the I9100 Themes/Apps forum for mods/themes appropriate to your ROM. Nothing I do in the Hellraising process should break any of these compatibility-wise.
i finally jumped on board and installed an i9100 rom. so far so good. im loving it. first install went smooth. root working and all. i dont know about battery life (my phone still plugged in while testing this out).
okay here is the rom ive installed "CriskeloRom V30-S-BAR-12/7-Tog-BLN-CallREC-Overscroll-7Locks-PWR-M-Esxt-(XWKJ2-2.3.5)"
http://forum.xda-developers.com/showthread.php?t=1168836
i have also installed JKAY DELUXE SETTINGS v12.1 <--great addon. lets you have multiple slide to unlock (AOSP lockscreen). option to remove home double tap. option to customize power options (extended). crt off/on animation. overscroll glow. all these options and more on this DELUXE SETTINGS app. http://forum.xda-developers.com/showthread.php?t=1154278
so far im loving it. this will be my rom for now. thanks ENTROPY for the great HELLRAISER.. you the man
edit: alright i have tried wifi tether. its not working. i know its mentioned in the known issues. the workaround doesnt seem to work for me at least ......i enabled changed ssid and password. but once i exit settings, it reverts back to borkness lol. any other workaround? thanks
Edit 2: nevermind i figured it out. I rmmbered i replaced the Settings.apk with one that has a theme i like. That borked wifi tether for me. I returned the settings apk i replaced, rebooted, and all is good
I just wanted to bump this to the top... this thread needs to be stickied! How do I ask a mod to sticky it?
Sent from my GT-I9100 using xda premium
Good question - I know in the Infuse section some ROM Q&As were stickied, but they don't do that in other forums.
Plus at least this is CLEARLY linked to from the main Hellraiser thread.
Hellraiser doesn't seem to work with the new 1.9 sensation update, unless I'm doing something wrong. A popup saying the process com.android.phone has stopped unexpectedly comes up repeatedly as the app restarts. Seems like a modem error, the sim card isn't read properly either. I'm about to try hacking the updater script to remove the kernal and modem changes, is there anything I would need to do other than delete those lines and repack it?
I did reinstall hellraiser after the update.
selfassembled said:
Hellraiser doesn't seem to work with the new 1.9 sensation update, unless I'm doing something wrong. A popup saying the process com.android.phone has stopped unexpectedly comes up repeatedly as the app restarts. Seems like a modem error, the sim card isn't read properly either. I'm about to try hacking the updater script to remove the kernal and modem changes, is there anything I would need to do other than delete those lines and repack it?
I did reinstall hellraiser after the update.
Click to expand...
Click to collapse
You must be doing something wrong... I am running 1.9 and have been since the test build.. I will post some screen shots in a moment
Sent from my GT-I9100 using xda premium
Here are some screen shots... check out my battery life ..
I did have it hooked to a computer while 1.9 downloaded and that's why you see that slight bump...
Sent from my GT-I9100 using xda premium
How did you install specifically?
I can't get it running. I've tried updating 1.8 and doing a fresh install and flashing hell raiser afterwards but the com.android.phone app crashes and signal is lost upon reboot. It actually works until I reboot.
selfassembled said:
How did you install specifically?
I can't get it running. I've tried updating 1.8 and doing a fresh install and flashing hell raiser afterwards but the com.android.phone app crashes and signal is lost upon reboot. It actually works until I reboot.
Click to expand...
Click to collapse
I had 1.8 flashed 1.9 on top without wipe.
Mounted system and data and then flashed hellraiser on top. And haven't had any issues.
Sent from my GT-I9100 using xda premium
An i9100 modem/kernel will NOT work, that's for sure.
In fact some of the behaviors you mention sound kind of like a classic example of accidentally running an I9100 modem. The rest sound like a classic example of not wiping or doing an improper TiBu restore.
I'll try to test tonight.
It may have been titanium backup, I also didn't remount before hell raising. I'll get it working if he did
Hi Entropy, do you have any idea why the tethering settings are not persistant?
I remounted before flashing and still had the problem. When restoring backup I used advanced restore and found that the culprit is in system, not boot. I don't have the time for a full wipe today.
If it works for entropy I'll just do another full wipe and not restore anything. Thanks for your time on this.
amtrakcn said:
Hi Entropy, do you have any idea why the tethering settings are not persistant?
Click to expand...
Click to collapse
Not yet, haven't had time to mess with it yet.
selfassembled said:
I remounted before flashing and still had the problem. When restoring backup I used advanced restore and found that the culprit is in system, not boot. I don't have the time for a full wipe today.
If it works for entropy I'll just do another full wipe and not restore anything. Thanks for your time on this.
Click to expand...
Click to collapse
Titanium backup always give me problems so I just don't use it anymore...
Have you tried a fresh install without titanium backup?
Sent from my SGH-I777 using xda premium
CheckROM RevolutionHD v3.1.1
I tried raisin' hell with CheckROM RevolutionHD 3.1.1 last night. This is an XWJK3 based ROM, and seemed to work fine. I was intrigued with the idea of having a kitchen in the ROM to customize it and wanted to check it out. Everything seemed to run and work ok. Home button lag and lack of haptic feedback were known and expected. There were a couple of things though -
1) The phone ran really hot. Like skin singeing hot. There was another post on the CheckROM thread that talked about the phone running hot. But I noticed the same problem with a hellraised VillainROM as well. So not sure if that is a hellraiser issue or a ROM specific issue. I do know about the media scanner crashing due to incompatible codecs between Samsung derived ROMs and CM7/MIUI, I didn't get a chance to see if getting rid of my media would fix it because of issue 2...
2) The kitchen app while great in theory, isn't quite there in practice yet it seems like. I tried installing a few mods from the kitchen, but a lot of times downloads failed. I tried installing the BlueMonkey theme from the kitchen and it caused the phone to bootloop. There are quite a few people talking about bootloops on the ROM page, so I am leaning towards this being a ROM or kernel incompatibility issue. I have never had bootloops or anything nearly as funky with any of the native I777 ROMs. I had to flash back to bone stock to recover. Thank god for Nandroids
So, I guess it is ok to the add XWJK3 based ROMs to the compatible list if Entropy thinks both of the above two issues are not hellraiser related.
I've never had heat problems on VillainROM hellraised.
I've been starting to hear that CheckROM 3.1.1 has a lot of issues with the kitchen app - as in 3.1.1 has issues in general. I've seen lots of comments about people sticking with 2.0.0 until it matures.
I only tried CheckROM VERY briefly - enough to confirm that wifi worked (as there was a negative report on wifi with CR 2.0.0)
I'll update the list later this week.
GingerMod
Thank you for this awesome tool, Entropy! You can add GingerMod (http://forum.xda-developers.com/showthread.php?t=1220283) to your list of XXKI3 ROMs that work well Hellraised.
I've quickly tested out everything I can think of from a fresh install (wipe everything, format/system) and no problems to report. Wifi tethering has the minor problem of reverting to default settings, but they work, so it's not an issue in the slightest for me. Default APN settings are the same as on UnNamed--ATT Phone and ATT WAP. Home button haptic works out of the box--I didn't do anything.
For those interested, some quick hits about this great ROM:
- Most Samsungyness removed, really convincing AOSP feel. It's not just a theme, it's rebuilt. Just a few niceties such as Camera, Browser, FM Radio remain. You can add back whatever Samsung features you want.
- Small, 1/2 size compared to stock ROMs
- There is no lengthy screen on delay during calls when removing phone from your face (present in UnNamed)
- Customizable via included "Extras" settings and JKay app
- Been stable for awhile. Over at the thread, you won't notice a lot of random issues or people clamoring for "fixes". It's just really complete.
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
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.
Hi, I just recently came back to this forum, pleased to find that we now have CM10 working on Amaze ! (Thank you sportsstar!)
However I did have a couple issues when installing, and seeing as how a lot of people in the CM10 thread asked to redirect questions here, I figured I make a thread.
My problem is that it seems as though no matter what I install, there is always a problem. As far as I know, I am using the basic ICS-Ruby kernel that was dumped 6+ months ago. I installed the CM10 rom using 4EXT, with no issues.
However when I installed the Gapps (gapps-jb-20130301-signed) I constantly had the Android keyboard force close on me. So instead I tried to install the JB-4.2-Gapps-signed. With these, the Android keyboard would not force close but the Google Now search app would force close everytime.
I've also tried installing the DARK GLASS 0.6 ROM by jose, but then the wifi would not turn on. (When I would try to turn it on, it would just hang saying "Turning on Wifi").
It is probably worth mentioning that I did do a full wipe everytime I installed the CM10 rom. I was sure to be very thorough. When I installed DARK GLASS 0.6 ROM, again, I did a full format of partiitions, and a wipe. Still the issues above arise.
Can someone maybe help me out as to what I'm doing wrong? Thanks!
------------------------------------------------------------------------------------------------------------------------------------------------------
EDIT: I just looked at my phone info, and apparently the kernel I'm using is 3.0.53-gd28c6eb. Is this okay or do I need to flash a new kernel ?
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