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
Related
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
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
Q&A for [ROM][CM12.0] Official CM12.0 for E970
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][CM12.0] Official CM12.0 for E970. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
wkobaint said:
Could this versions working on e975?
Click to expand...
Click to collapse
Nope, but if you choose you model from device list below, it will works.
So I dirty flashed this over my cm11 and Google play has stopped working. Won't connect at all. Any help is appreciated
Volstagg.The.Valiant said:
So I dirty flashed this over my cm11 and Google play has stopped working. Won't connect at all. Any help is appreciated
Click to expand...
Click to collapse
Did you flash 5.0 gapps?
dandrumheller said:
Did you flash 5.0 gapps?
Click to expand...
Click to collapse
Nope. Could find only old gapps
terribly sorry about the brain fart. whole problem arose because i didnt flash the correct gapps . got the gapps from xda and now its working well. but i am getting a pop up saying that google play services have not been installed on your computer etc...
will this problem go away if i just install the google play services apk?
edit : after flashing the proper gapps, an update from the play store solved everything. Now running smoothly.
since i updated to cm12,go power master has not been able to turn data off when the screen turns off. this was working flawlessly in kitkat. even the go power master widget is not working. thought there might be a problem with root,so flashed supersu 2.40 from recovery. but still it isnt working. any idea what the problem might be?
Volstagg.The.Valiant said:
since i updated to cm12,go power master has not been able to turn data off when the screen turns off. this was working flawlessly in kitkat. even the go power master widget is not working. thought there might be a problem with root,so flashed supersu 2.40 from recovery. but still it isnt working. any idea what the problem might be?
Click to expand...
Click to collapse
Has the app been updated to support LP? At times in the past, access for 3rd party apps to stuff like data connection, which requires root, sometimes changes functionality with version upgrades. Don't know if that's the case in this circumstance, but it's something to look into.
Performance drop
Flashed this rom with fulll wipe. Works well, but sometimes performance *drops* happens. It becomes VERY slow, like CPU speed drops down to 128mhz. I had the same problem on cm 11.
Who knows how to fix it?
Looking great and functions great but I am getting terrible battery life due to "miscellaneous" or "Cellular Standby" according to battery stats.
E970
1/15/2015 nightly (problem persists from previous nightly)
Same problem on stock and Solid_GEEB Kernel
PA 5.0 GAPPS
Lucky to get 12 hours of battery under normal use. Any suggestions?
Thanks,
-Nick
Any ideas how to fix my issue with the BT mac address being changed to "00:00:00:00:5A:AD"? I had the wrong address on CM11 also but it was a different incorrect address and I was able to fix it. I've posted details in my thread for fixing the issue on CM11. http://forum.xda-developers.com/showthread.php?t=2759056#post58131969<br/>
Video call issue
Video call isn't working in both skype and viber. Skype app is crashing as soon as I turn video on. Viber just doesn't turn on the video transmission. Can please somebody report about this issue to CyanogenMod team. I use video calling really often, so this is kind of issue keeps me away from using official CM12 builds. CM11 builds had this issue too and it hasn't got fixed till now.
azatheadfi said:
Video call isn't working in both skype and viber. Skype app is crashing as soon as I turn video on. Viber just doesn't turn on the video transmission. Can please somebody report about this issue to CyanogenMod team. I use video calling really often, so this is kind of issue keeps me away from using official CM12 builds. CM11 builds had this issue too and it hasn't got fixed till now.
Click to expand...
Click to collapse
Post a logcat of it happening.
Sent from my LG-ls990 using XDA Free mobile app
CM Updates
Settings - About phone - CyanogenMod updates indicates no new updates found despite new updates posted at http://download.cyanogenmod.org/?device=e970. I switched from unofficial CM12 to official CM12 several updates ago. I'm using the gapps posted here https://s.basketbuild.com/gapps. Is there a setting I need to revise to begin seeing the CM updates on my phone. It's no big deal since I can go to the CM device list and download directly.
alliance1975 said:
Settings - About phone - CyanogenMod updates indicates no new updates found despite new updates posted at http://download.cyanogenmod.org/?device=e970. I switched from unofficial CM12 to official CM12 several updates ago. I'm using the gapps posted here https://s.basketbuild.com/gapps. Is there a setting I need to revise to begin seeing the CM updates on my phone. It's no big deal since I can go to the CM device list and download directly.
Click to expand...
Click to collapse
The 1/27 update was detected and installed. I do not know what if anything i did to make it work.
Shelnutt2 said:
Post a logcat of it happening.
Sent from my LG-ls990 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry for late answer. I was too busy to post logcats earlier. I hope issues will get fixed.
I installed CM12.0 (1/27 build) but any 5.0 gapps I try fails to flash on the official TWRP 2.8.3.0 for the e970. I've tried bpear, PA, and one other. I can get the ROM to boot, then it gives FC's for every Google App, and the apps are all named by their com. ... name, and say "app not installed" when clicked. I have loaded the zip files over wifi, through adb push, via usb, and through straight download to the device. I've also run them from the external SD and the internal storage.
Is there a different recovery I should be using with this? Will a Nexus 4 recovery work on the e970?
thunder2132 said:
I installed CM12.0 (1/27 build) but any 5.0 gapps I try fails to flash on the official TWRP 2.8.3.0 for the e970. I've tried bpear, PA, and one other. I can get the ROM to boot, then it gives FC's for every Google App, and the apps are all named by their com. ... name, and say "app not installed" when clicked. I have loaded the zip files over wifi, through adb push, via usb, and through straight download to the device. I've also run them from the external SD and the internal storage.
Is there a different recovery I should be using with this? Will a Nexus 4 recovery work on the e970?
Click to expand...
Click to collapse
I'm using TWRP 2.8.4.0 recovery. I initially installed the CM12 unofficial rom along with this gapps:
https://s.basketbuild.com/gapps
and had no problem. I switched to official CM12 when announced by Shelnutt2 and have made no changes to gapps. Perhaps give that gapps a try.
Audio calls problem
Hi,
I recently updated my OS from LG's Official 4.1.2 to CM12. Everything seems to be working fine but for making/receiving calls. I am not able to hear or speak over the microphone and speaker outlet unless or until I use a headphones in which case both work properly. Can anyone please help?
Details on my upgrade:
I had backed up my data and downloaded the CM12 zip files with Gapps and SuperUser into my SD card. Once they were ready, I restarted my mobile in Recovery mode and wiped the user data and installed CM12.zip followed by Gapps followed by SuperUser. Then rebooted my mobile and check everything for the working condition. It was working perfectly except for the fact that when I receive phone calls or when I make a phone call once I attend the call, I would not be able to speak to the person or hear the person in normal mode nor in speaker mode. The only way it works is if I use my headphones.
I had installed CM12 01/26/2015 version. And have tried later versions until 01/30 but I do not find that to be fixing. It would be of great help if anyone could help me.
Thanks,
Arun
arun.rama said:
Hi,
I recently updated my OS from LG's Official 4.1.2 to CM12. Everything seems to be working fine but for making/receiving calls. I am not able to hear or speak over the microphone and speaker outlet unless or until I use a headphones in which case both work properly. Can anyone please help?
Details on my upgrade:
I had backed up my data and downloaded the CM12 zip files with Gapps and SuperUser into my SD card. Once they were ready, I restarted my mobile in Recovery mode and wiped the user data and installed CM12.zip followed by Gapps followed by SuperUser. Then rebooted my mobile and check everything for the working condition. It was working perfectly except for the fact that when I receive phone calls or when I make a phone call once I attend the call, I would not be able to speak to the person or hear the person in normal mode nor in speaker mode. The only way it works is if I use my headphones.
I had installed CM12 01/26/2015 version. And have tried later versions until 01/30 but I do not find that to be fixing. It would be of great help if anyone could help me.
Thanks,
Arun
Click to expand...
Click to collapse
Make a clean flash (in TWRP wipe system, data, cache, dalvik cache and after install cm12 and gapps) and install 84/27 hybrid modem during same recovery session, after reboot to system. Modem issues with e970 are really whimsical. I hope this will help.
P.S. Find modem image in this thread:
http://forum.xda-developers.com/showthread.php?t=2584981
azatheadfi said:
Make a clean flash (in TWRP wipe system, data, cache, dalvik cache and after install cm12 and gapps) and install 84/27 hybrid modem during same recovery session, after reboot to system. Modem issues with e970 are really whimsical. I hope this will help.
P.S. Find modem image in this thread:
http://forum.xda-developers.com/showthread.php?t=2584981
Click to expand...
Click to collapse
Hey, I just tried the steps you had mentioned and it worked like a gem. Thanks a lot for your solution. I really appreciate your help. Have a great weekend.
Arun
Hi, I'm sorry for my bad English, I'm with 1 Moto And first generation that after being looped I was able to unblock and install TWP, and put the Lolipop Rom 5.1, installed without errors, but when I started the android, I set it up and then when I restarted it Device it enters that white screen that appears that the bootloader was unlocked and falls straight into TWRP, does not start Android at all, could they help me? thanks
Nikakz said:
Hi, I'm sorry for my bad English, I'm with 1 Moto And first generation that after being looped I was able to unblock and install TWP, and put the Lolipop Rom 5.1, installed without errors, but when I started the android, I set it up and then when I restarted it Device it enters that white screen that appears that the bootloader was unlocked and falls straight into TWRP, does not start Android at all, could they help me? thanks
Click to expand...
Click to collapse
1. Flash stock lollipop
2. Reboot bootloader
3. Volume up select, Normal powerup
Rajendran Rasa said:
1. Flash stock lollipop
2. Reboot bootloader
3. Volume up select, Normal powerup
Click to expand...
Click to collapse
Guy
Ok, thanks I'll try
Nikakz said:
Guy
Ok, thanks I'll try
Click to expand...
Click to collapse
I tried, accept the installation of Rom, but it is on the screen of the logo starting and it does not leave, I do not know what to do to work.
Nikakz said:
I tried, accept the installation of Rom, but it is on the screen of the logo starting and it does not leave, I do not know what to do to work.
Click to expand...
Click to collapse
Sometimes a new flash takes nearly half an hour to boot. I faced once.. Did u wait for sometime?
vyshak.sk said:
Sometimes a new flash takes nearly half an hour to boot. I faced once.. Did u wait for sometime?
Click to expand...
Click to collapse
Yes, I waited more than 24 hours and nothing and no other flash I tried installs only this one and does not leave the startup logo, very strange this device, I needed a solution.
Nikakz said:
Yes, I waited more than 24 hours and nothing and no other flash I tried installs only this one and does not leave the startup logo, very strange this device, I needed a solution.
Click to expand...
Click to collapse
Flash latest twrp 3.x. You can find it from official lineage os thread under original development section.
Then flash any stable marshmallow custom rom.
_sushan_ said:
Flash latest twrp 3.x. You can find it from official lineage os thread under original development section.
Then flash any stable marshmallow custom rom.
Click to expand...
Click to collapse
Hello everyone, I put a CM13 and she accepted the installation and updated the TWRP also, I put the gaps, I did everything, Android starts, but continues with the problem of falling straight into recovery and going to TWRP and something else when I can do it Start it is not with network signal, recohece the chip, but does not give network signal. I do not know what to do with this device anymore. Could you try to install lolipop on it? Which version could I put? Would it be because of being in 6? I installed this rom cm-13.0-20161022-NIGHTLY-condor only installed it right. thanks
Nikakz said:
Hello everyone, I put a CM13 and she accepted the installation and updated the TWRP also, I put the gaps, I did everything, Android starts, but continues with the problem of falling straight into recovery and going to TWRP and something else when I can do it Start it is not with network signal, recohece the chip, but does not give network signal. I do not know what to do with this device anymore. Could you try to install lolipop on it? Which version could I put? Would it be because of being in 6? I installed this rom cm-13.0-20161022-NIGHTLY-condor only installed it right. thanks
Click to expand...
Click to collapse
Looks like you are using a very old cm 13 build.
Try this one. https://www.androidfilehost.com/?fid=385035244224413102
This is cm 13 snapshot build by @Andersonmends.
Clean install is recommended ie wipe cache data internal and then flash this with pico gapps
Nikakz said:
Hello everyone, I put a CM13 and she accepted the installation and updated the TWRP also, I put the gaps, I did everything, Android starts, but continues with the problem of falling straight into recovery and going to TWRP and something else when I can do it Start it is not with network signal, recohece the chip, but does not give network signal. I do not know what to do with this device anymore. Could you try to install lolipop on it? Which version could I put? Would it be because of being in 6? I installed this rom cm-13.0-20161022-NIGHTLY-condor only installed it right. thanks
Click to expand...
Click to collapse
You flashed latest twrp inside old twrp recovery itself?right?
Rajendran Rasa said:
You flashed latest twrp inside old twrp recovery itself?right?
Click to expand...
Click to collapse
Yes. Out the problem now with the network signal that is not picking up, it recognizes the chip, but it is without signal.
Nikakz said:
Yes. Out the problem now with the network signal that is not picking up, it recognizes the chip, but it is without signal.
Click to expand...
Click to collapse
Flash radio files. Google it for ur device.
_sushan_ said:
Looks like you are using a very old cm 13 build.
Try this one. https://www.androidfilehost.com/?fid=385035244224413102
This is cm 13 snapshot build by @Andersonmends.
Clean install is recommended ie wipe cache data internal and then flash this with pico gapps
Click to expand...
Click to collapse
Hello everyone, I installed Rom CM that the forum colleague indicated and the gapps and installed, everything went well in the installation and initialized Android, was very good in relation to the previous problems, nor know how to thank you. Just when I call it goes to the screen of the fastboot direct and I do not know how to make it not happen, but at least when the motorola logo appears it starts Android. I only notice a certain oscillation in the signal of the network of the operator and I did not find any file to download and to solve this problem of the signal of the network (or radio as you say) if they know where under some that can be installed for that Rom I thank you. I'll leave it for now and see if it's fixing. Thank you very much, ah, I would like to know if I should install the CM updates that appear on the device, it was so good that I'm afraid to accept it and thunder to give it a problem. Another thing he had TV, how to install this Rom? thanks
Hello everyone, I installed Rom CM that the forum colleague indicated and the gapps and installed, everything went well in the installation and initialized Android, was very good in relation to the previous problems, nor know how to thank you. Just when I call it goes to the screen of the fastboot direct and I do not know how to make it not happen, but at least when the motorola logo appears it starts Android. I only notice a certain oscillation in the signal of the network of the operator and I did not find any file to download and to solve this problem of the signal of the network (or radio as you say) if they know where under some that can be installed for that Rom I thank you. I'll leave it for now and see if it's fixing. Thank you very much, ah, I would like to know if I should install the CM updates that appear on the device, it was so good that I'm afraid to accept it and thunder to give it a problem. Another thing he had TV, how to install this Rom? thanks
Nikakz said:
Hello everyone, I installed Rom CM that the forum colleague indicated and the gapps and installed, everything went well in the installation and initialized Android, was very good in relation to the previous problems, nor know how to thank you. Just when I call it goes to the screen of the fastboot direct and I do not know how to make it not happen, but at least when the motorola logo appears it starts Android. I only notice a certain oscillation in the signal of the network of the operator and I did not find any file to download and to solve this problem of the signal of the network (or radio as you say) if they know where under some that can be installed for that Rom I thank you. I'll leave it for now and see if it's fixing. Thank you very much, ah, I would like to know if I should install the CM updates that appear on the device, it was so good that I'm afraid to accept it and thunder to give it a problem. Another thing he had TV, how to install this Rom? thanks
Click to expand...
Click to collapse
You can try flashing radio files.
Find one for your device from this thread : https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
I m not sure why ur device is rebooting in fastboot. Generally the most common cause for reboot in moto e is faulty lock button. But that jst reboots the phone. You can try using the phone without pressing the lock button. Use volume key wake up option and double tap to status bar to lock.
Also did you wipe cache data internal before flashing ?
And regarding the updates it depends on you. The updates you are for sering are for cm 14 / lineage os. I personally believe that nougat is still not stable enough and features are still missing hence i advised you for mashmallow roms. But if you want to try u can visit the various threads in android development and android development sections and will find nougat roms.
For installing / flashing instructions read guides in general section.
_sushan_ said:
You can try flashing radio files.
Find one for your device from this thread : https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
I m not sure why ur device is rebooting in fastboot. Generally the most common cause for reboot in moto e is faulty lock button. But that jst reboots the phone. You can try using the phone without pressing the lock button. Use volume key wake up option and double tap to status bar to lock.
Also did you wipe cache data internal before flashing ?
And regarding the updates it depends on you. The updates you are for sering are for cm 14 / lineage os. I personally believe that nougat is still not stable enough and features are still missing hence i advised you for mashmallow roms. But if you want to try u can visit the various threads in android development and android development sections and will find nougat roms.
For installing / flashing instructions read guides in general section.
Click to expand...
Click to collapse
Okay, thank you, it stabilized the signal from the network operator. I will leave as is and will not make updates at the moment. I just want to know how to make the TV function work. Thanks everyone for the help and I do not know how to mark a topic as closed in the forum.
Before I go willy-nilly downloading things does this solution actually work??
https://forum.xda-developers.com/gal...s-sim-t3640689
It's basic, libsec-ril.so is for sim card.
If your sim card is working before download Lineage OS you simply no need to download baseband/upgrade modem.
1.Need Root device
Example Magisk, SuperSU
2.Need Root File Manager
Example Root Explorer
3.Replace this file
Root/System/Lib/libsec-ril.so
0.How to get working sim card libsec-ril.so ?
-Find Lineage OS previous version that can make your sim card exist in your phone.
-Flash rom to that old version.
-Go to Root/System/Lib/ and backup libsec-ril.so
-Flash rom to new version and go to step 3 to replace file
-Turn Airplane mode on off, if not working reboot.
Or you can use this link to download libsec-ril.so
drive.google.com/file/d/0B8Z3Yq1NlXEfeEVlaFcxSGVXR0U/view?usp=drivesdk
Im sure file in that link is working for all note3 hlte if not please go to step 0
Well I solved the problem by loading a build adapted for Sprint users.. I am no way connected to this project but wanted to update my own question
[ROM][10.0.0_r33] SuperiorOS - Phoenix [OFFICIAL][HLTE/CHN/KOR/TMO]
https://forum.xda-developers.com/galaxy-note-3/development/rom-superioros-phoenix-t4086515
I can receive calls and text but cant send them on my Sprint note 3 (flashed to assurance wireless service *I dont have a sim card never did*) any advice?
SurageBook said:
I can receive calls and text but cant send them on my Sprint note 3 (flashed to assurance wireless service *I dont have a sim card never did*) any advice?
Click to expand...
Click to collapse
I suspect it is a problem with using the Assurance Service.. What ROM are you using?
Im trying to use SuperiorOS - Phoenix
I'm also having issues. Can't send or receive calls/texts and can't access "carrier settings" and most of the dialer codes for hidden menus don't work (SuperiorOS)
I know Sprint is weird because it did not use a SIM card so the ROM has to be compiled in such a way that it can be pre-set with the Sprint onboard chip. I know it worked with Superior OS with my Sprint phone on a Sprint account.
Other than that I am not sure what else I can add to this. I actually returned back to Lineage running Pie since it is configured for Sprint..
Unidave199 said:
I suspect it is a problem with using the Assurance Service.. What ROM are you using?
Click to expand...
Click to collapse
Unidave199 said:
I know Sprint is weird because it did not use a SIM card so the ROM has to be compiled in such a way that it can be pre-set with the Sprint onboard chip. I know it worked with Superior OS with my Sprint phone on a Sprint account.
Other than that I am not sure what else I can add to this. I actually returned back to Lineage running Pie since it is configured for Sprint..
Click to expand...
Click to collapse
What twrp version did you use and what ROM did you have before flashing? Just asking because back in December I was using some ROM and took be about 3 days to get it work where I had the simmiluar issues that was fixed by trying different versions of twrp, wiping, and flashing in different orders I think
SurageBook said:
What twrp version did you use and what ROM did you have before flashing? Just asking because back in December I was using some ROM and took be about 3 days to get it work where I had the simmiluar issues that was fixed by trying different versions of twrp, wiping, and flashing in different orders I think
Click to expand...
Click to collapse
Thats a tricky one... Let me see... I was using a Resurrection Remix Nougat for quite some time.... but then jumped over to Resurrection Remix Pie. I have toyed with Superior OS but waiting for them to fix a few things before I go to it permenantly.
Really the biggest thing is when you jump past Nougat, the Bluetooth just gets unreliable. Bouts of not working, FC's and disconnects abound. But I have been running a automatic script to keep the bluetooth reconnecting if it gets dropped.
I was using TWRP 2.8.7.0 but you will have to move up to TWRP 3.0 and beyond if you want to run Pie or Android 10.
Hope that answers your question!
Dave
Unidave199 said:
Thats a tricky one... Let me see... I was using a Resurrection Remix Nougat for quite some time.... but then jumped over to Resurrection Remix Pie. I have toyed with Superior OS but waiting for them to fix a few things before I go to it permenantly.
Really the biggest thing is when you jump past Nougat, the Bluetooth just gets unreliable. Bouts of not working, FC's and disconnects abound. But I have been running a automatic script to keep the bluetooth reconnecting if it gets dropped.
I was using TWRP 2.8.7.0 but you will have to move up to TWRP 3.0 and beyond if you want to run Pie or Android 10.
Hope that answers your question!
Dave
Click to expand...
Click to collapse
Thanks! I think im on nougat.. Bootanimation is a pink unicorn on steroids. I'll give superior another shot in a few days when I don't feel like talking to anyone