Related
3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.
if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.
The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems
if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband
thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot
Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App
thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone
Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine
damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated
I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....
maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.
lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?
Hi
Having a lot of grief trying to connect to WIFI with HC 3.1
Is it possible to go back to 3.0 and how?
thanks
mario7777 said:
Hi
Having a lot of grief trying to connect to WIFI with HC 3.1
Is it possible to go back to 3.0 and how?
thanks
Click to expand...
Click to collapse
That depends... Did you take the official OTA update, or did you use a ROM on here?
If you used a ROM on here, did you backup?
If yes, you can restore your backup. If no, there are OTA updates here you can use to go back to an old version if you wish BUT, there's an Acer proscribed "fix" for this wifi issue. Press the reset button on the side of the device to factory reset it. Once it's restarted and sitting on the home screen, press it again. It should be fixed after the 2nd wipe.
It was an OTA update, where do I find the updates?
thanks
mario7777 said:
It was an OTA update, where do I find the updates?
thanks
Click to expand...
Click to collapse
There are several threads in the dev section with multiple versions, not the custom ones. Go through the threads and read them properly. All the info you need to reflash is in there.
However, DO try the double reset fix first.
also try deleting the dhcp lease file under /data/misc/dhcp
I have deleted the file in /dhcp a number of times. and also tried the double and triple reset. All these fixes are very short term. I am sick and tired of dealing
with this sorry product. If I could I would have returned it ASAP. But I
am stuck with this product. All I know is that HC 3.0 worked OK.
When I upgraded to 3.1 all these WIFI issues began.
Until I get a patch from Acer, I want to go back to 3.0
I don't know how or where to get the files and info I need.
Please someone who knows let me know.
thanks again
mario7777 said:
I have deleted the file in /dhcp a number of times. and also tried the double and triple reset. All these fixes are very short term. I am sick and tired of dealing
with this sorry product. If I could I would have returned it ASAP. But I
am stuck with this product. All I know is that HC 3.0 worked OK.
When I upgraded to 3.1 all these WIFI issues began.
Until I get a patch from Acer, I want to go back to 3.0
I don't know how or where to get the files and info I need.
Please someone who knows let me know.
thanks again
Click to expand...
Click to collapse
I've already told you where to go and what to do. If you can't be bothered to go into the dev section and do some reading, that's your issue. I'm not going to spoonfeed you, put some effort into it and LEARN something.
There is a FULL TUTORIAL thread in there on backing up and restoring the OTA function for getting the 3.1 update. If you bother to read it, you'll see that it takes you all the way back to 3.0.
Short and simple:
http://forum.xda-developers.com/showthread.php?t=1155664
i would also check if you wifi/router firmware is up to date, also check if you have all frequencies available as per your region, f.i. add channel 12 and 13 for europ.
frequencies might be another problem due to interferences. check if you have automatique selection of frequencies selected on the router, because before anything goes on, the router and the equipment is negociating channels?
eventually try different channels to find out which works best.
and last but not least check if you have set the correct password for your wifi connection.
you need a dolorean and go at 65MPH... I don't see any solution.
mario7777 said:
Hi
Having a lot of grief trying to connect to WIFI with HC 3.1
Is it possible to go back to 3.0 and how?
thanks
Click to expand...
Click to collapse
Although we don't practice this, after every firmware update we are SUPPOSED to factory reset. Especially with a drastic update. This is considered drastic as we've gone from a .0 release to a .1 release.
A factory reset generally wipes the old settings out completely as well as the cache so the system can start "fresh". We're just very lazy and so the majority of us (I'm guilty as well), update and if it works, we run with it....so this has become the 'norm'.
Before you do something as drastic as go back to the old OS, how about you try a factory reset first.
If that doesn't work - then you can attempt going back.
I personally would do several things:
1a. Check router firmware to see if I'm on the newest
OR
1b. At least reboot the router. This clears upnp and any bottlenecking that's happening....and it does happen. If upnp is enabled and you have lots of PCs there can easily be thousands of ports added and open in the router and this can gum up new ip leases, etc.
2. Factory reset the device. This clears away the possibility that there's either some software creating the issue, or funky settings corrupted somehow because of the upgrade.
Good Luck.
Beat goes on
Neoprimal said:
Although we don't practice this, after every firmware update we are SUPPOSED to factory reset. Especially with a drastic update. This is considered drastic as we've gone from a .0 release to a .1 release.
A factory reset generally wipes the old settings out completely as well as the cache so the system can start "fresh". We're just very lazy and so the majority of us (I'm guilty as well), update and if it works, we run with it....so this has become the 'norm'.
Before you do something as drastic as go back to the old OS, how about you try a factory reset first.
If that doesn't work - then you can attempt going back.
I personally would do several things:
1a. Check router firmware to see if I'm on the newest
OR
1b. At least reboot the router. This clears upnp and any bottlenecking that's happening....and it does happen. If upnp is enabled and you have lots of PCs there can easily be thousands of ports added and open in the router and this can gum up new ip leases, etc.
2. Factory reset the device. This clears away the possibility that there's either some software creating the issue, or funky settings corrupted somehow because of the upgrade.
Good Luck.
Click to expand...
Click to collapse
1a. Check router firmware to see if I'm on the newest
OR
Done...............
1b. At least reboot the router. This clears upnp and any bottlenecking that's happening....and it does happen. If upnp is enabled and you have lots of PCs there can easily be thousands of ports added and open in the router and this can gum up new ip leases, etc.
REBOOTED Router
2. Factory reset the device. This clears away the possibility that there's either some software creating the issue, or funky settings corrupted somehow because of the upgrade.
Factory reset....lost it all.........
Still no connection...
Set up a static IP and this works...........
I will have to delay further action as I don't have the time right now.
I am leaning towards flashing a ROM, but I need to do more research.
Hopefully Acer will come up with a fix.
All I hear from Tier 2 is the endless reset until it works.
Tired of their bull.
This no way to repair a major problem like this.
Thanks for your advice
Q&A for [ROM][4.4.4]VanirAOSP[OFFICIAL][Samsung X Cover 2-GT-S7710]
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
hi , installed this rom but i still haven't network connection
Double boot when starting phone
Hello all together.
Yesterday I flashed the latest rom on my skomer.
So far everything runs smooth but I recognized one weird thing.
During boot (doesn't matter if a warm or cold start), the phone boots twice.
Means I see the Pin entry screen and after approx. 15s I see the boot animation again.
It does not matter if I enter the pin or not, it boots a second time at all.
After the second boot everything is OK.
This was a clean flash from theboegls prerooted image with normal pa gapps flashed.
Does anyone have a solution for this issue!
Thanks a lot,
Kubunter
Just installed the new nightly(4.4.4.101014) Everything is running smooth. Just wondering if there is a radio for android 4.4.4 and how do i get it if there is?
---------- Post added at 10:10 PM ---------- Previous post was at 09:55 PM ----------
ManuelBiancolilla said:
hi , installed this rom but i still haven't network connection
Click to expand...
Click to collapse
I read the forum and tried this code and it worked for me.
run this code in your terminal if you cant find terminal get if from playstore using wifi.
adb shell
su
find /efs/|while read s; do chown radio:system $s; done;
find /modemfs/|while read s; do chown radio:system $s; done;
chmod -R 777 /efs/
chmod -R 777 /modemfs/
reboot
After reboot your mobile data should be working
Camera not working
Thank you for your great work, hopefully devs are reading this subthread, too.
It would be nice, if following message would be referred on the first message, since many people have issues with network. I managed only to find all the information by very inconvenient googling:
http://forum.xda-developers.com/showpost.php?p=55354795&postcount=414
This post is the Theboegl's relevant one:
http://forum.xda-developers.com/show...3&postcount=43
After the newest nightly, camera stopped working. I will downgrade, but here are some details:
Model:
GT-S7710
Incremental version:
eng.nuclearmistake_20141012.042853
Running apps:
Nothing extraordinary
Exception class name:
java.lang.NullPointerException
Source file:
PhotoModule.java
Source Method:
initializeFocusManager
Line number:
1997
Start trace:
PhotoModule.java: 1997, 1835, 96 and 234
Cleaned cache+camera data. I was using SIM-card as my memory.
ManuelBiancolilla said:
hi , installed this rom but i still haven't network connection
Click to expand...
Click to collapse
Did you use the right clockworkmod mentioned on the main post? Also your firmware might be too new, therefore flashing this one might help:
http://forum.xda-developers.com/showpost.php?p=40232503&postcount=43]
If I got it right it must be
- install odin and get cwm on pc
- get supersu and cm on your sd card
- reboot in download mode
- flash cwm on phone
- reboot in Recovery
- well i think you can backup already
- root with supersu
- reboot in Recovery
- wipe data/factory
- install
- reboot
I use 1010114
wifi and camera work here, but sim card seems not to be accepted
good use of hardware buttons after reflashing (this had issues before)
[did not install GApps, but that should not be a problem..?]
tried 10.2 from flxo and had the same problem with SIM
Double Boot
Hello all together,
I have a logcat of the problem, saved at pastebin.
As I´m a new user, I´m not allowed to post a outside link.
Is it possible that I will send someone who is able to post a link a PM?
The second boot happens around 22:44:54 o´clock
Something with a android process seems to be wrong.
Is anyone able to help?
Thanks a lot,
Kubunter
Android Lollipop?
Pushed fix for streaming YouTube should now work next nightly. Downloading source now to build recovery image. Thanks for waiting. I will try to solve the problems we have but I can't guarantee anything due to lack of device. I'm going to discontinue my work for ste devices soon. As long as it builds I will try my best to keep supporting them but fixing problems etc I can no longer continue.
Click to expand...
Click to collapse
@Unjustified Dev, will you made Android 5.0 for xcover 2? (Because you discontinue development)
andrew551 said:
@Unjustified Dev, will you made Android 5.0 for xcover 2? (Because you discontinue development)
Click to expand...
Click to collapse
There are still STE developers and I'm sure this one will get lollipop working if he can't I doubt we will see it , but lollipop might be a large merge and roms might have to rebase or start from scratch porting hardware workarounds and eventually bring back features.
intermittent network signal
Guys please help. I tried this ROM and it looks great but I'm loosing network signal almost every time I'm starting up navigation (Sygic) and I use it a lot. I don't loose it immediately, sometimes after a few minutes, sometimes after 20 min. but the signal triangle finally goes black and doesn't come back after switching off navigation. This makes it unusable to me. I've seen people reporting problems with network signal so I guess it's not the app. issue. Sometimes it looks like I just loose data transfer (it shows no internet) but the signal bar shows that I have network. Some other time I was not moving at all but the signal bar was going up and down from max. to min. within 3 sek. After few minutes it stabilized. Something seems to be wrong with the antenna or modem, whatever is responsible for network signal.
And another thing, that looks to be related, I don't have any arrows and network type sign (2G/3G) showing if I do or don't have internet connection.
There were some posts talking about a fix for network problem by typing some commands somewhere but could someone explain it step by step how to apply it, if it is a working fix.
Thanks!
After a reboot the home button doesn't work until I enter my pin code, which comes like half an hour after boot! How do I fix it and does anyone else have this problem!?
I was about to throw this piece of **** phone away but i gave it a last chance with Vanir. It took me nearly 2 hours to flash the Rom , but i got it working.
First of I want to thank the dev for the work, I realy apreciate it. You managed to make this phone usable again, I hate Samsung so much for this crap Software they used for the Xcover2.
After using Vanir for one week (using not testing), here is what is not working for me:
-maximum volume for every call
-stock photo app crashes
-Location is very inaccurate, my guess is the cell tower fix is working and the GPS is not
-sometimes i cant shut off the phone, it freezes and i have to pull the battery
-phone is sometimes not going to sleep mode, i have to restart it
Everything else is working perfectly, this is thousand times better then the Samsung bull****. Oh, my carrier is Telekom(Germany).
No radio/SIM with GT-7710 XCover 2 on CM11
The forum forces me to open a new thread, apologies.
I gave the Vanir Skomer 4.4.4.101714 nightly a try but my broadband (S7710XXAND2)/IMEI is gone after reboot. Big difference to most reports I've read is that once I return to stock ROM all is fine again. In other words: the SIM was not damaged. Also the chmod/chown and move-files-from-stock trick doesn't improve anything. No idea what else I should try. I'm currently back on stock Android.
This is what I've done:
- Use Odin 3.09 to apply 20140112_cwm-6.0.4.6_skomer_fixed.tar.md5
- Boot into CWM
- Update to CWM 6.0.4.7 via cwm_skomer_test2.zip
- Wipe/Factory + Dalvik reset
- Install vanir_skomer_4.4.4.101714.zip (also tried 20131231_cm_11.0_skomer-ota-eng.flx.zip)
- Install pa_gapps-modular-pico-4.4.4-20141019-signed.zip
- Wipe/Factory + Dalvik reset
+ Copied {efs,modemfs} from stock to vanir (removed vanir's folder contents before)
+ Fixed file perms to 666, folders to 777, owner to radio:system
I couldn't find TWRP for Skomer or a more recent clockwork recovery. Just mentioning this because I've read a post that mentioned recovery is responsible for setting radio related stuff.
Ideas?
Network connection doest work for me to. I like this rom too and like to be it get worked! (Y)
Never mind, fixed my radio issue. See http://forum.xda-developers.com/showpost.php?p=56293409&postcount=37
vanir_skomer_4.4.4.101714
I got that one and currently it's syncing but I have no mobile networks. I'm from Finland and I'd like to know what data I should post to help fix it. (I could recompile and all if I get instructions)
__
Your's Mikko A. Liukkonen
Kiil said:
After the newest nightly, camera stopped working. I will downgrade, but here are some details:]
Click to expand...
Click to collapse
Just wanted to confirm with my Vanir nightly of 101714, my camera app crashes too. No problems with radio or networking though.
Cant call, says my phone is currently airplane mode
hello, just installed the latest (vanir_skomer_4.4.4.102814) and now my phone can't find network and says that airplane mode is on when i try to call. Airplane mode button says it's off and kills the bt and wifi if i turn it on, aka goes to real airplane mode.
Fix for this would be more than welcome.
itsesaatana said:
hello, just installed the latest (vanir_skomer_4.4.4.102814) and now my phone can't find network and says that airplane mode is on when i try to call. Airplane mode button says it's off and kills the bt and wifi if i turn it on, aka goes to real airplane mode.
Fix for this would be more than welcome.
Click to expand...
Click to collapse
What's the latest stock update because we are having incompatible installation due to my kernel being based on older release and blobs
Unjustified Dev said:
What's the latest stock update because we are having incompatible installation due to my kernel being based on older release and blobs
Click to expand...
Click to collapse
What do you mean by stock update?
Edit:
Seems like it's working again, it woke up after an hour. Sorry for the trouble.
Please I need your help guys.
My OnePlus2 recently started behaving weird. The Bluetooth, WiFi and External speaker just stopped working for no apparent reason. Every other thing is working. 3G works just fine. I am able to make calls through the normal speaker (i.e. by putting the phone to the ear), but if I decide to switch the calls to the loudspeaker, I can't hear anything. Also, if I play music to the external speaker I can't hear anything unless I connect a wired earphone through the jack. When I try to turn ON the Bluetooth and Wifi, they just turn themselves back OFF, so they have become useless.
Please has anyone experienced anything like these before; if yes, please how did you solve it.
isadeiza said:
Please I need your help guys.
My OnePlus2 recently started behaving weird. The Bluetooth, WiFi and External speaker just stopped working for no apparent reason. Every other thing is working. 3G works just fine. I am able to make calls through the normal speaker (i.e. by putting the phone to the ear), but if I decide to switch the calls to the loudspeaker, I can't hear anything. Also, if I play music to the external speaker I can't hear anything unless I connect a wired earphone through the jack. When I try to turn ON the Bluetooth and Wifi, they just turn themselves back OFF, so they have become useless.
Please has anyone experienced anything like these before; if yes, please how did you solve it.
Click to expand...
Click to collapse
Not too sure about the External Speaker issue, but generally whenever I get Bluetooth and WiFi issues exactly like yours in the past - a reset solved the problem.
But I only ever had issues like that if I'm using a Custom ROM.....
Is your 1+2 using OxygenOS by any chance?
LogicalJunkie549 said:
Not too sure about the External Speaker issue, but generally whenever I get Bluetooth and WiFi issues exactly like yours in the past - a reset solved the problem.
But I only ever had issues like that if I'm using a Custom ROM.....
Is your 1+2 using OxygenOS by any chance?
Click to expand...
Click to collapse
Thank you for your help.
What I mean by the External Speaker is the speaker at the bottom of the phone next to the charging port that enable you listen to the audio, either call or music, without putting the phone to your ear.
Yes, I am on the stock Oxygen 2.1.0. I have also restarted and wipe data and cache more than five times but nothing different has happened so far.
Ahh so the loudspeaker is faulty? The loudspeaker and the wireless module are quite separate hardware, so we've got to hope that it's a software fault - rather than both multiple prices of hardware being faulty.
At this stage do a nandroid backup, then Clean Install OxygenOS 2.2.0. If that doesn't solve the issue, just let us know. (If you need specific instructions on how to do the nandroid backup & clean install, just let us know as well).
LogicalJunkie549 said:
Ahh so the loudspeaker is faulty? The loudspeaker and the wireless module are quite separate hardware, so we've got to hope that it's a software fault - rather than both multiple prices of hardware being faulty.
At this stage do a nandroid backup, then Clean Install OxygenOS 2.2.0. If that doesn't solve the issue, just let us know. (If you need specific instructions on how to do the nandroid backup & clean install, just let us know as well).
Click to expand...
Click to collapse
Thanks for your support.
I did a nandroid backup as advised and I downloaded and clean install the Oxygen 2.2.0.
The situation didn't change. Its as if the modules are just not present.
For example, when I try to activate the WiFi or Bluetooth, they are animate as if to turn ON; but after a couple of minutes it simply turn back OFF and grey-out.
I even installed the unofficial CM 13 hoping this might solve the problem, but it remains the same.
Do you think this may in any way be connected with the kernel?
isadeiza said:
Thanks for your support.
I did a nandroid backup as advised and I downloaded and clean install the Oxygen 2.2.0.
The situation didn't change. Its as if the modules are just not present.
For example, when I try to activate the WiFi or Bluetooth, they are animate as if to turn ON; but after a couple of minutes it simply turn back OFF and grey-out.
I even installed the unofficial CM 13 hoping this might solve the problem, but it remains the same.
Do you think this may in any way be connected with the kernel?
Click to expand...
Click to collapse
Hmm no it shouldn't since you clean installed OOS (that should have flashed the stock kernel too).
Give it a try anyway, try flashing @Lord Boeffla kernel for OOS http://www.boeffla-kernel.de/
Just make sure you download the .md5 as well (ensure the download isn't corrupted).
If that fails, try the stock kernel as well http://boeffla.df-kunde.de/oneplus2/stock-kernel/.
If the above doesn't happen, can you do this check for me?
Shake the phone, tap the phone on a desk (aim around the sim card area), be gentle though, all we need is to ascertain if the signal flex cable is loose.....
Once you shaked and tapped the phone, check if the wifi/bluetooth is working? (if not, give it a reset and try again).....
LogicalJunkie549 said:
Hmm no it shouldn't since you clean installed OOS (that should have flashed the stock kernel too).
Give it a try anyway, try flashing @Lord Boeffla kernel for OOS http://www.boeffla-kernel.de/
Just make sure you download the .md5 as well (ensure the download isn't corrupted).
If that fails, try the stock kernel as well http://boeffla.df-kunde.de/oneplus2/stock-kernel/.
If the above doesn't happen, can you do this check for me?
Shake the phone, tap the phone on a desk (aim around the sim card area), be gentle though, all we need is to ascertain if the signal flex cable is loose.....
Once you shaked and tapped the phone, check if the wifi/bluetooth is working? (if not, give it a reset and try again).....
Click to expand...
Click to collapse
Thank you very much for your time @LogicalJunkie549.
I will download the kernel as advised and install it.
I will come with the update after the installation.
LogicalJunkie549 said:
Hmm no it shouldn't since you clean installed OOS (that should have flashed the stock kernel too).
Give it a try anyway, try flashing @Lord Boeffla kernel for OOS http://www.boeffla-kernel.de/
Just make sure you download the .md5 as well (ensure the download isn't corrupted).
If that fails, try the stock kernel as well http://boeffla.df-kunde.de/oneplus2/stock-kernel/.
If the above doesn't happen, can you do this check for me?
Shake the phone, tap the phone on a desk (aim around the sim card area), be gentle though, all we need is to ascertain if the signal flex cable is loose.....
Once you shaked and tapped the phone, check if the wifi/bluetooth is working? (if not, give it a reset and try again).....
Click to expand...
Click to collapse
I have done the suggested steps.
The phone remains the same.
Please see attached the screen shots.
It looks as if these modules/chips just went dead
Flash Oxygen OS Zip via Stock Recovery & Wipe Cache & Data
isadeiza said:
I have done the suggested steps.
The phone remains the same.
Please see attached the screen shots.
It looks as if these modules/chips just went dead
Click to expand...
Click to collapse
For your speakerphone issue, I can bet it is related to the modem/ radio.
Please update to the latest modem/ radio (via fastboot) for your device.
Then test calling again and report back.
Note that this issue and solution is not specific to Oneplus. It is applicable to CM 13 on all devices across manufacturers.
Hit the 'Thanks' button if this solution works for you.
Where can I get the OnePlus 2 Modem/Radio File
s_u_n said:
For your speakerphone issue, I can bet it is related to the modem/ radio.
Please update to the latest modem/ radio (via fastboot) for your device.
Then test calling again and report back.
Note that this issue and solution is not specific to Oneplus. It is applicable to CM 13 on all devices across manufacturers.
Hit the 'Thanks' button if this solution works for you.
Click to expand...
Click to collapse
Thank you for your support.
Please any idea where I can get Modem/Radio file to download.
A link will help, because I have been searching for it but no luck so far.
isadeiza said:
Thank you for your support.
Please any idea where I can get Modem/Radio file to download.
A link will help, because I have been searching for it but no luck so far.
Click to expand...
Click to collapse
Hi Isadeiza, try this modem first (its the 'modem' for MM which might solve the issue finally). https://www.androidfilehost.com/?fid=24415232478675280.
Also try dirty flashing it first, if that doesn't work... Take nandroid then Clean flashing it.
What OxygenOS are you in now btw? As of right now we're up to 2.2.1....
LogicalJunkie549 said:
Hi Isadeiza, try this modem first (its the 'modem' for MM which might solve the issue finally). https://www.androidfilehost.com/?fid=24415232478675280.
Also try dirty flashing it first, if that doesn't work... Take nandroid then Clean flashing it.
What OxygenOS are you in now btw? As of right now we're up to 2.2.1....
Click to expand...
Click to collapse
Thank you. I am currently on OxygenOS 2.2.1
I will try your suggestions and revert back asap.
LogicalJunkie549 said:
Hi Isadeiza, try this modem first (its the 'modem' for MM which might solve the issue finally). https://www.androidfilehost.com/?fid=24415232478675280.
Also try dirty flashing it first, if that doesn't work... Take nandroid then Clean flashing it.
What OxygenOS are you in now btw? As of right now we're up to 2.2.1....
Click to expand...
Click to collapse
Thank you @localjunkie549.
I have tried installing the modem and bluetooth files in the downloaded file in the link.
I am afraid the phone response remains the same.
I even tried installing the new OxygenOS 3.0, still the same.
Speaker working Now. But BT and WiFi still down.
LogicalJunkie549 said:
Hi Isadeiza, try this modem first (its the 'modem' for MM which might solve the issue finally). https://www.androidfilehost.com/?fid=24415232478675280.
Also try dirty flashing it first, if that doesn't work... Take nandroid then Clean flashing it.
What OxygenOS are you in now btw? As of right now we're up to 2.2.1....
Click to expand...
Click to collapse
Hi guys, thank you all for your support.
After a long time, my experience are as below.
After upgrading to OxygenOS 3.0, the behavior of the phone did not change. No sound from loudspeaker, no Bluetooth and no WiFi.
Well I stopped using it until my other phone started heating up so I came back to the OnePlus Two again. One day, I was surprised when the phone started ringing loudly as someone called my line. It worked for about 3 - 4 hours and stopped again. After about 5 days, it came up again for some 4 hours and stopped working again. It does this for over 6 cycles and about 3 days ago it kept working without stopping since.
So I am still observing it for the past three days and it seems to have repented, holding my hopes up high that it will continue to work without hitches again; though I cannot say now what happened, why it stopped working and why it started working now.
The problem of the Bluetooth and WiFi still persist and I still can't use the BT and WiFi. It just behave as if the modules are not present. My fingers crossed expecting them to "miraculously" come back to functional state just as the loudspeaker did on its own.
Thank you all guys for your support.
Just as the title says, after flashing the bootstack, rom and gapps countless times, i still dont have auto rotate or auto brighness. all the sensors seem to be dead except for wifi, gps and mobile network. did anyone else experience this? how did you resolve it??? please help!!
I had the same problem after dirty flashing from 13.1. I did a factory reset and reflashed and all was well.
whoiswes said:
I had the same problem after dirty flashing from 13.1. I did a factory reset and reflashed and all was well.
Click to expand...
Click to collapse
thanks for the reply. i did a clean flash. didnt work.
i flashed the boostack, rebooted back to recovery, flashed the rom and gapps, wiped cache and rebooted. it boots fine. but then i still dont have auto rotate. seems like the drivers werent installed or something
Obvious questions, but did you check the rotation settings inside the display menu? Also, is Adaptive brightness toggled on?
MiMtnBiker said:
Obvious questions, but did you check the rotation settings inside the display menu? Also, is Adaptive brightness toggled on?
Click to expand...
Click to collapse
i did. i installed an app that checks the phones sensors. they are all undetected. i think its a driver issue. i'm at my wits end
crazynitro said:
i did. i installed an app that checks the phones sensors. they are all undetected. i think its a driver issue. i'm at my wits end
Click to expand...
Click to collapse
Check the md5 on your download to make sure it is not bad Install twrp 3.0.4.0 you could also move everything you want to keep to a sdcard so you can do a total wipe. Now install rom and gapps only and check to see how everything works before adding root or apps.
crazynitro said:
Just as the title says, after flashing the bootstack, rom and gapps countless times, i still dont have auto rotate or auto brighness. all the sensors seem to be dead except for wifi, gps and mobile network. did anyone else experience this? how did you resolve it??? please help!!
Click to expand...
Click to collapse
This is an old thread, but I am hoping you found a fix for these issues. I am having the same issue. If you have a solution to share I would greatly appreciate it.
lkiefer said:
This is an old thread, but I am hoping you found a fix for these issues. I am having the same issue. If you have a solution to share I would greatly appreciate it.
Click to expand...
Click to collapse
I lost my phone so i currently have another one. i can t remember what i did to fix it though
crazynitro said:
I lost my phone so i currently have another one. i can t remember what i did to fix it though
Click to expand...
Click to collapse
That's a drag. Thanks for the quick response though.
Hello, I also have an issue with the accelerometer (and by consequence the auto rotate function).
I am on full stock Nougat B09 (no root) and the issue was also present on B06.
Rebooting the device solve the issue, and factory reset does not make this bug disappear.
That being said, I think I located the root cause.
The magnetometer seems to be never working, even after a reboot. When an app wants to use the magnetometer (like Google map, or the compass), it make the accelerometer crash....
Anyone else having this issue ?
Does you magnetometer works flawlessly ?
Thanks.
@arachneon,
Hi, you can change it in the tools---compass, and in that compass you can waggle the phone in the way of "8", if all that cannot fixed you can also seek help in the nearby ZTE after sales service repair center. Thanks!