pac man rom phone - Sprint Samsung Galaxy Note 3

hey im not sure why but when i call some one while having the pac man rom or any of the aosp roms i cant get my screen to turn back on while in a phone call and wanted to know if theres any one that knows whats wrong with it

epicdumdum said:
hey im not sure why but when i call some one while having the pac man rom or any of the aosp roms i cant get my screen to turn back on while in a phone call and wanted to know if theres any one that knows whats wrong with it
Click to expand...
Click to collapse
Hey if you might try this. Go to settings/device/call and uncheck " Turn off screen during calls" the screen will stay on during calls, or is supposed to. You might test your proximity sensor, here is a link to Galaxy Tools app http://forum.xda-developers.com/not.../app-one-click-hotspot-enabler-menus-t2816159 the download is a zip file so put it on your PC desktop. Just change it to an apk file (bring it up with 7zip or WinRAR and rename it) and in stall on your device. Now click Testing/Phone Info then test the proximity sensor, if ok then something in the rom, if not, the phone screen will not turn on and off during calls.

No issues here
I've been running Pac-Man 4.4.4 pretty much since it was made available.
I haven't had that issue.
Make sure you're wiping everything and not restoring any data. Except maybe texts and like call logs.

normally i dont have issues but its just been with the aosp roms that it wont work right im not sure if i should clear oout my dalvik and everything as well and the reinstall the rom

epicdumdum said:
normally i dont have issues but its just been with the aosp roms that it wont work right im not sure if i should clear oout my dalvik and everything as well and the reinstall the rom
Click to expand...
Click to collapse
Yes, when you flash a ROM you should wipe partition and dalvik cache. As well as doing a factory data reset.
Also, are you running the latest version? There was a version during its beta process where that issue did come up. Since pretty much all AOSP ROMs are based on CM11 they'd all exhibit the same issue being that CM11 is upstream.
Good luck

yeah i am running the latest version of it but it just doesnt seem to work properly also would the recovery mess with the ROM at all??

epicdumdum said:
yeah i am running the latest version of it but it just doesnt seem to work properly also would the recovery mess with the ROM at all??
Click to expand...
Click to collapse
It has been known that some recoveries work better for some roms. I'd check around and see what others may be using. See what the rom developer recommends for flashing the rom . Also maybe try an older more stable version of the rom your running.

Yeah I'd love to but I c can't post on that website

Related

Argghhh

Okay, I have gotten so blasted close with getting a custom rom on this phone. I can get them installed now and they are wonderful I tried gummy and aokp but for the life of me I can not get data to work I can not make or recieve phone calls. I am in roaming all the time too. I have gone through all settings and scoured the forum and I can not find an answer anywhere. Am I missing something totally obvious here? Does anyone maybe have any suggestion? Thank you guys for your help. It's just frustrating that I am so close.
debinnv said:
Okay, I have gotten so blasted close with getting a custom rom on this phone. I can get them installed now and they are wonderful I tried gummy and aokp but for the life of me I can not get data to work I can not make or recieve phone calls. I am in roaming all the time too. I have gone through all settings and scoured the forum and I can not find an answer anywhere. Am I missing something totally obvious here? Does anyone maybe have any suggestion? Thank you guys for your help. It's just frustrating that I am so close.
Click to expand...
Click to collapse
What is the status of your Photon currently? Assuming it is rooted and unlocked, running what rom? Please provide info on what rom you are on now, which one you flashed from, and what process you used to get where you are. The more info provided the easier it will be to help.
Well lets see, currently I am back on stock, but here is what I did. I rooted, unlocked, installed CWM 5.0.2.7 I also flashed jokers recoveryv3 ( I follow QB's videos) So then I installed the gummy rom using this process. Format system, format data, format cache, wipe cache then dalvik cache. flash rom, flash rom again ( now I did not reboot into recovery after I flashed the rom the first time) I just went straight to install rom again. flash gapps, fix permissions. Reboot up and good loving it all. Waited 15 min then rebooted again. That's it. So I am at a loss. Thanks for help if you need any other info please let me know.
Oh I am on 2.3.4 with 198_7 also
In your system settings did you have "home only" or "automatic" selected for your roaming settings? For a lot of these roms, "automatic" is forced roam. And then if you didn't have roaming data enabled, that would explain why you were constantly roaming with no data.
Sent from my MB855 using XDA
Thanks so much .
I did have automatic checked but I did have roaming data enabled also. I flipped it around too with home only. I am truly beginning to think my phone is just plain "off " who knows. It's a shame though, I mean not that stock is bad on this phone but the custom roms are so much better imo. This is the first phone I have ever had a problem with. I have been flashing phones for years. Think I started with a HTC Mogul. That was a solid phone LOL
Does CM7 work for you? If it does then I reckon flashing that and setting it up, then instead of doing a full wipe keep your data and flash CM9 based rom over it, fix permissions and take it from there.
I have not tried CM7 but I can, sure can't hurt to try at this point. Thanks, I will give that a try tomorrow.
Have you tried *#*#4636#*#*? Sometimes flashing changes the radio in that menu. Be careful though, changing something can really Bork your phone. It should be on cdma prl I think
sent from my CM7 MoPho
Deb, my photon has never been kind to me with the 'flash twice' method. It always results in no data. Try cm9 again, but this time wipe cache, system, data, and dalvik, install version 3.1 of cm9, boot into it, reboot to recovery, wipe cache and dalv, then install the latest cm9 version. Always works for me. Good luck
Sent from my MB855 using XDA
Morning all, your all are great. Okay so I am ready to start again. I'm at stock right now so I need to get her all set up again. (Yes my phone is a she) Acvice, I am going to try your method first will let you know in a bit.
Looks like joker's site may be down so I need to try and find the 2 cm9 roms
I have this rom saved already on my computer
beta-0.6.9.1-cm-9.0.0-RC0-sunfire-UNOFFICIAL-signed.zip
Wonder if I should try that one or just wait
After I install CWM 5.2.0.7 do I also need to flash joker's v3 recovery?
debinnv said:
After I install CWM 5.2.0.7 do I also need to flash joker's v3 recovery?
Click to expand...
Click to collapse
You don't have to, but I recommend it.
Sent from my MB855 using XDA
I think th3bill has 0.3.1 in his fixes thread
http://www.mediafire.com/?y7no1r460d4o8zf
sent from my CM7 MoPho
Thanks, will also do jokers and thanks for the link bullfrog. dl'ng now
debinnv said:
Thanks, will also do jokers and thanks for the link bullfrog. dl'ng now
Click to expand...
Click to collapse
Glad someone provided you with that 3.1 link. Looking forward to see if it works out for ya.
By the way, you will know it worked if when you boot up in 3.1 you have working data. Flashing the newer version after that will essentially just update everything.
Deb, I take it the flash of 0.3.1 didn't work? Did you have data and then lose it when you flashed 0.6.9.3? What were your exact steps. I just rooted/unlocked and flashed my f-in-law's new photon and it worked just fine. Lemme know what you did and maybe I can help more
sent from my CM7 MoPho
Thanks bullfrog that's nice of you but honestly I'm good now As you know.
I didn't even try to install 0.3.1. I kept thinking about it, seeing I had no luck with 2 others previously so I decided to go the MIUI route and I'm a happy camper with that one. I am a flashaholic for sure, as we all are here. I am thinking though, I am gonna just be happy with where I am at for now. Of course I will most likely decide to give another rom a try at some point.
Of course I am already eyeing a few Samsung Epic touch's on ebay. I hear that one can be a brick just waiting to happen....weeeee I am having way too much fun
I'm glad you made it to MIUI. if you ever want to try cm9 or and of the similar ones (aokp, gummy, paranoid) I would suggest flashing that 0.3.1 first, then updating to the latest cm9, then flashing the variant
sent from my CM7 MoPho

Cm 9-20121028

Today I updated to the CM 9-20121028-nightly-haida. Since then I have no more wireless. The whole point is greyed out and when I go into the settings in the Wi-Fi, he veruscht to activate all the time. Is this a known bug? Is that still the case with several? Is there a workaround? Previously, I had the cm-9-20121014-NIGHTLY-haida because everything worked.
nuiler said:
Today I updated to the CM 9-20121028-nightly-haida. Since then I have no more wireless. The whole point is greyed out and when I go into the settings in the Wi-Fi, he veruscht to activate all the time. Is this a known bug? Is that still the case with several? Is there a workaround? Previously, I had the cm-9-20121014-NIGHTLY-haida because everything worked.
Click to expand...
Click to collapse
did you flashed new kernel. did you wiped cache and dalvik cache?
in your thread is no question. its not quite good to open new threads like this - furthermore you could have found the answer in CM9.1 thread..youst to mention..
best regards
I have no installed the cm-9-20121021-NIGHTLY. With this version, I can use WIFI. Is the kernel different from this to cm-9-20121028-NIGHTLY?
nuiler said:
I have no installed the cm-9-20121021-NIGHTLY. With this version, I can use WIFI. Is the kernel different from this to cm-9-20121028-NIGHTLY?
Click to expand...
Click to collapse
cant tell in which way the kernel differs-read changelog for information. but since your wifi doesnt works i suggest to flash new kernel and wipe. and if kernel is provided with rom update i would always recommend to flash it!

[Q] Problematic s4 (4.4.2)

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

slimkat 4.4.3 working (almost) after official 4.3 update

I was using slimkat 4.4.2 and restored the official samsung rom 4.3 to try a mhl cable. The result as you may know is that I couldn't install any custom rom that wasn't based on samsung's after that.
Searching here in the forums I found some people saying that it was because of a layout change on partitions, others because of knox, or the update in bootloader...
I installed the twrp-2.7.1.0 recovery and tried to install omni rom with pa_gapps, cm11 etc and I always get an error for gapps (couldn't find build.prop or something...). Tried Omega v58 (based on sam) and it worked, then I tried slimkat 4.4.3 weekly and slim_AIO_gapps (advanced wipe, everything but extsd, format data) and it installed everything fine.
It's almost perfect but now I have only a small problem... when I plug the headset the audio is really bad and sometimes I can't hear anything ... I tried another kernel with the same result. Tried slimkat 4.4.2 stable, same.
Does it make any sense to anyone here? any sugestions on how to fix? flash something somewhere maybe :x
and what is the real problem after the 4.3 official update? if slimkat is working maybe we can make other roms work too.
Thank you in advance
Do a full wipe, all your previous issues were due to files left over from other firmware.
On the headset, go back to stock firmware after a full wipe. If still the same then it is hardware.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Do a full wipe, all your previous issues were due to files left over from other firmware.
Click to expand...
Click to collapse
I still can't install most roms even with full wipe (gapps error) after the 4.3 official update but I'm happy with slimkat. I think maybe it works because it just copies the gapps files to android without doing other checks, maybe editing the scripts we can "force" the install of other roms too. If anyone have any info, please tell me.
boomboomer said:
On the headset, go back to stock firmware after a full wipe. If still the same then it is hardware.
Click to expand...
Click to collapse
Oh, I think it was just a series of bad coincidences. Tried the stock firmware and the headset did not work. Seems like my headset broke the same day all that stuff happened, and I tried the one I use on PC but it didn't connect firmly on s3 so the sound was bad too... just tried a new phone headset and it's working fine.. thank you

Can someone here help me for God's sake, pls?

Sorry about that kinda title, but m desperate here. An issue that's been driving me nuts.
Even willing to pay for this mess to get over (Pls don't get me wrong for this). I have a moto 360 2nd gen. It pairs fine with the phone and gets all the notifications alright, however when I try to answer or reject calls or even silent them from the watch, nothing happens on the phone, it just keeps ringing.
I have tried the following ROMS on my Oneplus One:
I) Resurrection remix with android 6.0.1
2) CM 13, snapshot as well as nightly.
3) Darkobas failed cos unable to switch on Bluetooth on that
4) CM 12.1 snapshot.
5) Paranoid Android
Have tried all sorts of Gapp apps as well, stock, pico, micro, slim. Watch has been reset an equal no. of times too.
Watch works fine with other phones with their android versions.
Last attempt resulted in answering, rejecting and silencing calls only when the phone screen was unlocked and awake, as soon as the phone locks, the problem comes back again.
Once again, pls help.
vineet296 said:
Sorry about that kinda title, but m desperate here. An issue that's been driving me nuts.
Even willing to pay for this mess to get over (Pls don't get me wrong for this). I have a moto 360 2nd gen. It pairs fine with the phone and gets all the notifications alright, however when I try to answer or reject calls or even silent them from the watch, nothing happens on the phone, it just keeps ringing.
I have tried the following ROMS on my Oneplus One:
I) Resurrection remix with android 6.0.1
2) CM 13, snapshot as well as nightly.
3) Darkobas failed cos unable to switch on Bluetooth on that
4) CM 12.1 snapshot.
5) Paranoid Android
Have tried all sorts of Gapp apps as well, stock, pico, micro, slim. Watch has been reset an equal no. of times too.
Watch works fine with other phones with their android versions.
Last attempt resulted in answering, rejecting and silencing calls only when the phone screen was unlocked and awake, as soon as the phone locks, the problem comes back again.
Once again, pls help.
Click to expand...
Click to collapse
Somebody, anybody pls. ??
Have you tried with stock, oxygen os? If it works there, then you have a "file shortage" on your current ROM, you'll need to copy some files over from there.
Tried MIUI ROM based on KitKat and that works, didn't attempt oxygen OS cos that would require moving to a different recovery other than TWRP n I then wudnt be able to attempt all these ROMS without it. Can I somehow try and copy these missing files over onto my current ROM ? N wud u be kind enough to tell me how n which ones to copy?
vineet296 said:
Tried MIUI ROM based on KitKat and that works, didn't attempt oxygen OS cos that would require moving to a different recovery other than TWRP n I then wudnt be able to attempt all these ROMS without it. Can I somehow try and copy these missing files over onto my current ROM ? N wud u be kind enough to tell me how n which ones to copy?
Click to expand...
Click to collapse
Well, you said something about the watch using Bluetooth right? I'll see what I can do, right now I am at the airport about to board a 5hr flight so I'll see tomorrow what I can do.
Sent using a ks01lte (gt-i9506) running cm 13
Jee that wud be great, hoping to hear from u soon. N a safe journey ahead.
vineet296 said:
Jee that wud be great, hoping to hear from u soon. N a safe journey ahead.
Click to expand...
Click to collapse
Thanks! Made it safely and I looked it up and in your ROM that works, copy all fils that have the name bluetooth in it from /system/lib to the ROM that doesn't work and report back to me.
Hi again, as suggested I looked for all files that had the name Bluetooth in the system/Lib folder in MIUI ROM (KitKat based) and found only one by the name Bluetooth.default.so, I copied that over and replaced it in the current Resurrection ROM (Marshmallow) on my phone at the same location. Now Bluetooth won't switch on and keeps switching back off immediately. Tried to undo the process but still unable to switch on the Bluetooth now. What should we try next?
vineet296 said:
Hi again, as suggested I looked for all files that had the name Bluetooth in the system/Lib folder in MIUI ROM (KitKat based) and found only one by the name Bluetooth.default.so, I copied that over and replaced it in the current Resurrection ROM (Marshmallow) on my phone at the same location. Now Bluetooth won't switch on and keeps switching back off immediately. Tried to undo the process but still unable to switch on the Bluetooth now. What should we try next?
Click to expand...
Click to collapse
There is a directory called "/etc/bluetooth", copy it to your ROM and report please , I am feeling that we are getting closer to solving the issue.
Did so, still the Bluetooth wudnt switch on. next is?
vineet296 said:
Did so, still the Bluetooth wudnt switch on. next is?
Click to expand...
Click to collapse
Was bluetooth on while you were copying the files?
Might have been, can't say for sure but I guess it was switched off, but yet again not sure.
vineet296 said:
Might have been, can't say for sure but I guess it was switched off, but yet again not sure.
Click to expand...
Click to collapse
Well, f***, it needs to be off otherwise that happens.
Ohk. Now is there some way we can do something or I'd hv to wipe and install the entire ROM before we can try once again?
vineet296 said:
Ohk. Now is there some way we can do something or I'd hv to wipe and install the entire ROM before we can try once again?
Click to expand...
Click to collapse
I think you will have to wipe everything (system, data, cache, dalvik, preload) and start over again.
Alright, as u say, I'll make an attempt once again today and copy the files over as u said ensuring that Bluetooth is switched off during the entire process and then report back to u. N m thankful u walking me thru this.
vineet296 said:
Alright, as u say, I'll make an attempt once again today and copy the files over as u said ensuring that Bluetooth is switched off during the entire process and then report back to u. N m thankful u walking me thru this.
Click to expand...
Click to collapse
Yea, if that doesn't work, we'll have to dig way deeper, but since you said that it worked on the other ROM this should be it. I know how hard it is to be stuck in a problem that there is no info about on the internet.
It is, I was like how come m the only one facing this, nobody else in the whole wide world of Google. Ok before I do this, just to recap, fresh install the Resurrection Remix ROM, n before I even switch on the Bluetooth, copy all the Bluetooth files over from those two locations of the working ROM which u told me about and then try the Bluetooth, right?
vineet296 said:
It is, I was like how come m the only one facing this, nobody else in the whole wide world of Google. Ok before I do this, just to recap, fresh install the Resurrection Remix ROM, n before I even switch on the Bluetooth, copy all the Bluetooth files over from those two locations of the working ROM which u told me about and then try the Bluetooth, right?
Click to expand...
Click to collapse
Affirm sir, crossing my fingers hoping it will work .
RAZERZDAHACKER said:
Affirm sir, crossing my fingers hoping it will work .
Click to expand...
Click to collapse
Tried, did it while Bluetooth was switched off, copied the Bluetooth.default.so file from system/lib of the working ROM along with the entire Bluetooth folder from etc/ to the same location of the non functional ROM, but just as last time, now not able to switch on Bluetooth all together. Back to Base unfortunately

Categories

Resources