Related
I'm not sure exactly where this goes, but I think it belongs here and I haven't been able to find any other threads about this issue.
It's going to seem like a WinMo issue, but I'm pretty sure it's Android related.
I have a ATT Tilt2 with a stock ROM (I think with Sense 2.5) that I recently (last week) installed FRX06 on top of an older BLAZN install that I hadn't tried in months.
Today, I shut down Android (properly) and turned the phone on to return to WinMo. On the 4 digit numeric PIN screen (I Activesync with Exchange at work and this is part of the security requirement; it's not the SIM or GSM PIN), I enter my pin and ... I get an error message that I've entered the wrong PIN and I just used 1 of 8 turns. I tried carefully to enter the PIN to make sure I didn't fat finger the button - strike 2. So, I open the keyboard to try using that, and still no dice. Now I'm worried about getting my device wiped and starting from scratch.
The reason I think this is Android related is that this has happened to me one other time. This problem was the main reason I stopped using BLAZN about 6 months ago. In the almost 2 years that I've had this phone, this hasn't happened when rebooting from WinMo back into WinMo.
Any suggestions or ideas about what's going on? I don't even want to touch my phone without having a plan of attack. My contacts are backed up (first thing I did before I installed FRX06), but would rather not have to re-install stuff if I don't have to.
By the way, until this little incident, Android had been running great - it's been a big improvement over where it was 6 months ago.
Thanks in advance for any help.
-David
LeStone08 said:
I have a ATT Tilt2 with a stock ROM (I think with Sense 2.5) that I recently (last week) installed FRX06 on top of an older BLAZN install that I hadn't tried in months.
Thanks in advance for any help.
-David
Click to expand...
Click to collapse
I think you need to rename/delete your data.img.
But first you need a real fresh start so don't install FRX06 on top of BLAZN. Delete the old and download the FRX06 package from the thread
Thanks for the reply. Those are some good suggestions in general, but doesn't address my immediate need: Is there any way to get past the PIN check now (maybe the PIN was reset to some default)? Or is there an explanation for what is going on? AS it is, there's nothing I can do with the phone if I don't get the PIN correct (can't reboot into Android).
Also, in order to get FRX06 to work, I did delete the data.img file, so that is fresh. Also, the first time a few months ago, I ran into this problem was on my original (clean) install of BLAZN. Until this problem happened, Android had been working great in most other respects.
You're not supposed to use PIN auth in WinMo if you want to use Android.
Although, that type of PIN should work, I wouldn't use it. So if your work requires it, I'd say don't use Android.
I wish I could help more, my company uses GroupWise and only allows BB's to connect...
arrrghhh said:
You're not supposed to use PIN auth in WinMo if you want to use Android.
Although, that type of PIN should work, I wouldn't use it. So if your work requires it, I'd say don't use Android.
I wish I could help more, my company uses GroupWise and only allows BB's to connect...
Click to expand...
Click to collapse
I don't know why PIN auth in WinMo would have anything to do with Android, and I know I never had any problems with my WinMo pin while running android. While I can't say for certain that Android wouldn't do anything to your WinMo PIN, I would put the likelyhood at .0000001%. It simply doesn't touch the built in storage. Android is run straight from the SD card, and WinMo doesn't store your PIN on the SD card, so the chance of any funny business between the two is very low. Someone who knows the ins and outs of the NAND better than I would probably tell you it is impossible for Android to write to NAND, seeing as how there was so much work that went into the NAND testing.
Long story short, it wasn't Android. Maybe someone is playing a joke on you.
rpierce99 said:
I don't know why PIN auth in WinMo would have anything to do with Android, and I know I never had any problems with my WinMo pin while running android. While I can't say for certain that Android wouldn't do anything to your WinMo PIN, I would put the likelyhood at .0000001%. It simply doesn't touch the built in storage. Android is run straight from the SD card, and WinMo doesn't store your PIN on the SD card, so the chance of any funny business between the two is very low. Someone who knows the ins and outs of the NAND better than I would probably tell you it is impossible for Android to write to NAND, seeing as how there was so much work that went into the NAND testing.
Long story short, it wasn't Android. Maybe someone is playing a joke on you.
Click to expand...
Click to collapse
Normally, I wouldn't think Android would impact my winMo setup. But this has only happened to my twice and both times occured after shutting down Android and rebooting the phone.
No one else has access to my phone - so I can't blame anyone else.
I did install the trial version of Touchdown in my Android installation, but I don't think that's part of the problem (the last time it happened, I used the standard Exchange functionality of Android).
Could the policies enforced by Exchange cause my WinMo PIN to reset when I registered the new Android connectivity? When I set up Touchdown, I used the same PIN that I set for WinMO.
Thanks for the comments. Looking for any suggestions to get the phone up without getting it wiped (any default PINS that I can try?).
LeStone08 said:
Could the policies enforced by Exchange cause my WinMo PIN to reset when I registered the new Android connectivity? When I set up Touchdown, I used the same PIN that I set for WinMO.
Thanks for the comments. Looking for any suggestions to get the phone up without getting it wiped (any default PINS that I can try?).
Click to expand...
Click to collapse
These are questions for your IT dept I would think...
rpierce99 said:
I don't know why PIN auth in WinMo would have anything to do with Android, and I know I never had any problems with my WinMo pin while running android. While I can't say for certain that Android wouldn't do anything to your WinMo PIN, I would put the likelyhood at .0000001%. It simply doesn't touch the built in storage. Android is run straight from the SD card, and WinMo doesn't store your PIN on the SD card, so the chance of any funny business between the two is very low. Someone who knows the ins and outs of the NAND better than I would probably tell you it is impossible for Android to write to NAND, seeing as how there was so much work that went into the NAND testing.
Long story short, it wasn't Android. Maybe someone is playing a joke on you.
Click to expand...
Click to collapse
I would agree with rpierce99. I use MS Exchange (2007) on both wm & frx06 with password policy enforced and never experienced this issue. I chose to use a 6 digit numeric pin on both OS.
I remember having this issue. Pissed me off beyond belief. Same thing happened, booted out of android, when I tried unlocking, it kept saying the password was incorrect. For some reason I can't remember what I did to fix it... I think I just did a forced hard reset (click reset button, hold send key + end key + power key all at once). I know it's not what you want to hear but hard reset might be the only/quickest fix.
If it's asking for a SIM PIN, then this isn't related to Android, and it's not a Win-Mo issue either. It's the PIN for your SIM card as it's always been - or someone's changed it on you (they need to know your old one first)
3? Wrong guesses on a PIN and you get a PUK lock. (Pin Unblock Key)
The PUK is provided to you from your mobile provider. 10 wrong goes of this and you brick your SIM permanently, and you'll need a new one.
PIN and PUK aren't supported in Android to my knowledge, and Win-Mo will only allow you to change the PIN if you knew the old one as I said. I don't know of any "hacks" that can up-and-change it.
Lastly, there's good old device "lock". I had this corrupt on my TP2 end of last year causing me a huge headache and a hard reset. I was NOT using Android at this time.
Hope that helps in some way.
Raa_1 said:
If it's asking for a SIM PIN, then this isn't related to Android, and it's not a Win-Mo issue either. It's the PIN for your SIM card as it's always been - or someone's changed it on you (they need to know your old one first)
3? Wrong guesses on a PIN and you get a PUK lock. (Pin Unblock Key)
The PUK is provided to you from your mobile provider. 10 wrong goes of this and you brick your SIM permanently, and you'll need a new one.
PIN and PUK aren't supported in Android to my knowledge, and Win-Mo will only allow you to change the PIN if you knew the old one as I said. I don't know of any "hacks" that can up-and-change it.
Lastly, there's good old device "lock". I had this corrupt on my TP2 end of last year causing me a huge headache and a hard reset. I was NOT using Android at this time.
Hope that helps in some way.
Click to expand...
Click to collapse
Nah, his first post specifies it wasn't a SIM or GSM lock. I believe he had the Winmo lock go crazy on him like me. You say you had it too but not with android... I think my battery was very low at the time, I have no idea if that has anything to do with it. Was your battery fairly low/close to dying?
Nah not at the time. But I ran a tweak program and set a setting that botched it - I think. I was never tempted to try again to find out though.
Also on a side note, just tested the latest updates today, "PIN incorrect" when trying to unlock in Android. Works in WinMo. Removing PIN on startup again until it's fixed. (bummer!)
slapshot30 said:
Nah, his first post specifies it wasn't a SIM or GSM lock. I believe he had the Winmo lock go crazy on him like me. You say you had it too but not with android... I think my battery was very low at the time, I have no idea if that has anything to do with it. Was your battery fairly low/close to dying?
Click to expand...
Click to collapse
You're right, it wasn't my SIM lock that was causing the problem. I don't remember if my battery was low or dying. I do know that the last thing I had running was the Youtube app that was having problems with buffering a video, then it started getting non-responsive, which was why I decided to shut down my phone and reboot.
I checked with our IT department and besides them trying not to support it because it's not an eye-phone, there were no known MS Exchange changes at our company that would have caused the problem. I did find out that the webmail client for Exchange now shows the clients that connected - I could see a listing for my WinMo install and a couple for my Android install (my original install from 6 months ago, and my current install - the different builds had different system names). There is a feature to request a recovery PIN there, but my HTC Sense simple PIN entry screen didn't have a recovery pin option that's needed - or I didn't see it in the last try I had to get my PIN correct. Maybe I'll play with that more if I start using WinMo again.
My phone did get wiped and so far, I haven't loaded anything back into WinMo - I've been running off my Android install (didn't reinstall - since my SD Card didn't get wiped) for the last 1.5 weeks.
I know it's not a large sample size, but the two times this has happened in the almost 2 year time period that I've had this phone occurred when booting out of Android. I'm glad to hear that I'm not the only one with this issue, but it would be nice to have the problem diagnosed.
I'm hoping that one of the brains doing all of this cool stuff will find the root cause and show us (at least me and Slapshot) how to avoid the problem.
Thanks. I'm still really happy about the state of the Rhodium projects.
Raa_1 said:
Nah not at the time. But I ran a tweak program and set a setting that botched it - I think. I was never tempted to try again to find out though.
Also on a side note, just tested the latest updates today, "PIN incorrect" when trying to unlock in Android. Works in WinMo. Removing PIN on startup again until it's fixed. (bummer!)
Click to expand...
Click to collapse
I've never set any type of PIN on my Android phones. What are you setting?
On any phone you can set it to "Request PIN on startup" and it will ask you for the SIM's PIN. (This is SIM dependant, I don't know if it works for CDMA).
Traditionally, it would boot up the phone fine, but won't activate the SIM until the PIN is entered, once that's entered and the SIM unlocks, it'll logon to the 3G network and work normally.
In XDAndroid, if I try to enter my PIN, it says it's incorrect (works fine in WinMo), but I did read somewhere that it wasn't supported, and it has to be left off. I don't like doing this, but no choice really!
Want to troubleshoot this issue too?
Raa_1 said:
On any phone you can set it to "Request PIN on startup" and it will ask you for the SIM's PIN. (This is SIM dependant, I don't know if it works for CDMA).
Traditionally, it would boot up the phone fine, but won't activate the SIM until the PIN is entered, once that's entered and the SIM unlocks, it'll logon to the 3G network and work normally.
In XDAndroid, if I try to enter my PIN, it says it's incorrect (works fine in WinMo), but I did read somewhere that it wasn't supported, and it has to be left off. I don't like doing this, but no choice really!
Want to troubleshoot this issue too?
Click to expand...
Click to collapse
I'll take your word on the SIM PIN business, as I've never actually set my SIM pin. I wouldn't do this in general, but also especially knowing that there's a conflict between SIM pins and the XDAndroid projects.
In WinMo (I believe there's a way to do this an Android also, but not quite sure), there are two ways that I know of to set up a startup PIN on your phone (at least on my Tilt2):
1) You can go into Settings, Security, Phone Lock: here you can set up your phone to lock itself after a set amount of time. You can use either a Simple PIN or a strong alpha-numeric PIN. Whenever your phone is idle for a time period exceeding the threshold you have set, the phone will lock itself so that you have to enter your PIN to access the phone again. Again, this is not the SIM pin.
2) Some of us work at companies that use this little email package called Exchange by a company called Microsoft . In order to protect employee's and (mostly) company data, some of these companies will leverage security features in Exchange to mandatorily set policies on any mobile devices that want to access the corporate email system. If you want access to the system, you have to accept whatever policies the company chooses to enforce. Some of these policies include: 1) Requiring a PIN (not a SIM pin) on your device; 2) requiring a max idle time before the phone locks itself; 3) requiring a phone reset (including data wipe) after a certain number of missed passwords; 4) allowing a phone wipe/clear on demand in case of theft; etc. My company requires all of these - there are more, but I'm not familiar with all of the options.
When I boot into Windows Mobile, Exchange sees my phone as one device and sets the policies accordingly (basically the email software has to be able to receive the policies and interpret them). When I boot into XDAndroid, Exchange sees my phone as a different device and sends the same set of polices. For my original problem, I set the PIN to be the same for both instances to make like easy for my tiny little brain.
I reiterate that this is not a SIM pin issue. I want to make it clear so we can keep this thread on topic in case anyone else has some insights into the problem. I don't want it to be derailed into a SIM PIN discussion since I'm sure there are lots of threads about that. (Now, I've probably polluted the index with that term and anyone looking for that will find this instead )
I would love to know if anyone gets any insights here.
Thanks for reading.
David
Yes I see what you mean now, and my issue is a different one (SIM not device PIN).
Since your work is issuing device policies, my thought would be it's a policy issue, and quite honestly, I wouldn't try and mess around with a device that's under I.T. direction.
Having said that, i'd likely say your problem is a corrupted WinMo password as Android has nothing whatsever to do with WinMo's side of things. And as mentioned before, it can happen with varying (mainly unknown - grr) reasons why.
Is this possible. I've tried everything the fingerprint scanner doesn't work unless you have a secure lock screen. I have used knock code since I got the V10 along with fingerprint so I can use the fingerprint, but I don't want to have to put a knock code in if my fingerprint doesn't work or its on the table...
Anyone got a workaround? I'm still searching.
Matt
Does no one know how I can do this?
Matt
I'd like to know the same thing. I know LastPass just added fingerprint support (for marshmallow) and I'd love to be able to use my fingerprint to unlock that (when marshmallow comes) without having to have a secure lockscreen. I don't really care if someone can get into my phone. I just don't want to have to type in my password to use lastpass
I've searched around everywhere for this option .... I just don't think it exists.
So just don't use any lock to get into the phone now. I've got the stuff I want secure in locked files/apps section. Makes using and accessing the main functions of the phone much more accessible. Only doing this for a few days now as a test, but I think it'll be the way I keep it.
My Two Lock Screens Worth
I've addressed the issue another way. I added several more "trusted" places, devices, and connections as well as "trust while moving" which means as long as the phone senses it's on me, I'm at home, connected to Bluetooth devices I know, and more, there's no secure lock but fingerprint still unlocks it. Perfect. Still testing it
Matt
Hello!
I recently switched to the m4 from my trusty LG OG, an it is perfect except for one thing... it doesn't ring.
I have tried all Sony-solutions, including PC software repair, etc... but no joy. My wife also has an M4 and has the same problem.
It is worked-around by using a 3rd party lockscreen (I use Hi-Locker), which is awesome.. but not ideal due to security problems, most notably Android Pay.
My question?
Can I replace the lockscreen at the ROM level? Can I replace the basic function with maybe a lockscreen from the Z5?
Unless someone knows how to fix this
I have never compiled my own rom, but I have a reasonable level of tech-savvy. I can flash ROMS and do work in Linux.
I have rooted and unlocked my bootloader, and I am using Stock Sony ROM
I have the latest firmware
Kernel 3.10.49
build 26.1.A.2.99
I have NOT tried using an old firmware- or an alternate ROM. I probably will, but my wife doesn't love the idea for her. Thus, I would like to work out a precision fix.
My thoughts?
Idea 1. find where the stock lockscreen/security module lives.. and try and replace with something from a different phone.
Possible?
Thank you for reading.. I know some other people have these problems, as I read them in threads here.. but I didn't find much in the way of fixing.
just for reference- THIS is the problem.
just for reference- THIS is the problem.
Mustang243 said:
My phone doesn't ring when it 's locked. If phone is unlocked ringtone rings and vibrates. When it's locked no sound or vibrate. Whatsapp messages vibrate but they have no notification sound. I have checked all the settings, volume is up. Last resort is factory reset but i'm not there yet. I don't wanna lose all my settings.
E: Okay I used Sony PC Companion and used the Fix phone/tablet -thing and it downloaded the firmware and installed it so I think it reset my phone. Still my phone doesn't ring if its locked. If I press the power button when someone is calling to me, I can see the lockscreen notification on the screen but it doesn't ring or vibrate. FFS. Any ideas guys?
E2: I guess I find a solutions. Or a temporary solution. I noticed that if I disabled the screen lock, my phone would ring and vibrate normally. So I decided to try and download "Next" lockscreen app. Guess what. When I use it, my phone works perfectly. I don't know why it stopped ringing because there wasn't any new updates from Sony but it's clearly problem in Sony's software.
Click to expand...
Click to collapse
Mustang243 said:
I still have the "silent phone" issue with this update. I have to use third party lock screen app. If I use Sony's lock pattern or pin code and use my gf's phone to call my phone: screen doesn't wake, no ringtone can be heard and no vibration. When I press power-button I can see that someone's trying to call me. Anyone else experiencing this problem? I hope you understand what I tried to say, the issue is kinda hard to explain.
Click to expand...
Click to collapse
Yeah this is a huge problem and we're not the only ones suffering from it. Now I use CM Locker because Next drained my battery. I also noticed that my phone works fine if I boot on safe-mode. Still haven't figured it out which app causes the problem. Gotta wait for the 6.0 update and hope that fixes things.
Same issue with out-of-the box...
Well, have M4 'out of the box' - meaning - no custom software installed, no customized ROM, no custom lock-screen... and well - to make the ring work back I have to restart phone every few days (as soon as realize that it's not working) - oh Sony, what should I say ....
Can anyone confirm that smart lock is working on there device? Have been trying to use it for a while now with very little luck. On body detection works but only within a matter of seconds, trusted places doesn't work at all and i can't unlock my phone with okay Google ( but i have read some devices don't support this feature). Just after some reference points, they could be all the same.
Works fine for me. In stock as for custom ROM. I don't use on body detection but location works fine. Make sure you have enabled great accuracy for location services.
It works fine on my p9000, but I am on Eragon ROM .. Smart lock works as it should and I can use the command ok google to unlock.
However having tried other ROMs I know that what options appear in Security >> Smart Lock vary - as an example when I tried Lineage ROM I couldn't unlock device with my voice, nor could I use voice commands from any screen. Unfortunately I haven't really sued Stock for a little while so I am unsure what actual options are available for the Stock ROM. I would of assumed though the standard Smart Lock options of On Body Detection / Trusted Places / Trusted Devices should be standard (I have 2 other options Trusted face & trusted voice on Eragon)
Going on a long shot, i run a launcher so I'm going to run without for a day or two and see how it works out. Wouldn't have thought it would make a difference but worth a try.
Sent from my P9000 using Tapatalk
Think I nailed it, i use a gesture to lock my screen on Nova launcher. When i lock with the power button it's fine but when i use a gesture smart lock doesn't work, just incase anyone else ever has a similar problem.
Hi all,
Recently got myself a Ulefone Armor 2. The device is not too bad so far. I switched to it after cracking my Power2's screen multiple times. It comes with a stupidly basic Android 7. So I just wanted to start a thread to see if anyone's got their hands on it and started hacking around. See the bookmarks below for all things customisation.
I've edited this first post multiple times to reflect the recent developments. Some people got root & Magisk working see links after my first remarks:
About the latest Software Update (aka 20180224_s21v57c2k_gq_fp or S21 GQ3037LF2 Ulefone V12 20171009-Update 20180224):
alpsayin said:
Nope, it's not the same. Something is fundamentally off with this ROM. Accessibility services get turned off automatically every time screen goes off. Half the background apps are killed every time screen stays off for a minute too. I've already reverted back to what I had before. I suggest stay away from this build.
Click to expand...
Click to collapse
If you've updated your phone to latest ROM use the below instructions to revert back but use https://www.needrom.com/wp-content/uploads/2017/11/S21_GQ3037LF2_Ulefone_V12_20171009.zip instead of the latest one:
[/U]https://forum.xda-developers.com/showpost.php?p=74294320&postcount=31
First remarks:
-Some people and I are having problems with USB-C headphone adapter (https://forum.xda-developers.com/android/help/ulefone-armor-2-t3684566/post74367962#post74367962)
-Device bluetooth volume level is separate from the headset's volume. (EDIT: fixed with recent ROM update)
-Adaptive brightness might be a tad bit aggressive in my opinion so I switched it off. (EDIT: less aggressive with recent ROM update)
-Android Pay does NOT work. It says device is not verified (which is sad, I really wanted this to work). (EDIT: works now with also recent ROM update).
-Camera button launches a camera app if you press for 5 seconds only. Useful to trigger underwater.
-SOS button needs 5 seconds push to start calling emergency contacts, but even then it causes a lot of pocket dialling.
-PTT button only works inside the Zello app. Kinda wish these buttons could be reassigned for other things (EDIT: see this reply https://forum.xda-developers.com/showpost.php?p=74451451&postcount=78).
-Generally buttons are easy to push, i change the volume every time I put the phone in my pocket, then again i might just need to get used to having a brick with 4g.
-Speakers are not great, but it's indeed waterproof. Took it into shower and gave it a good abuse.
-Fingerprint sensor is a bit annoying at times but I believe this might be because I was sent a phone with improperly attached screen protector. (EDIT: it was the badly aligned screen protector)
-Power menu doesn't have the shortcut to the power saving mode that I like so much
-Be gentle with your USB-C cap, mine broke. It's still waterproof, but now it's pretty easy to lose the cap.
-If you wanna save some serious battery, disable Google App data backup (App backup&restore).
-Sports mode in battery settings will make the phone "snappier" probably at the expense of battery life.
BOOKMARKS:
ROM Stuff (some need TWRP)
See this reply for instructions to update to recent ROM:
https://forum.xda-developers.com/showpost.php?p=74294320&postcount=31
TWRP Flashable Stock ROM with Magisk Root (Android Pay working, Buttons disabled, needs opengapps)
https://forum.xda-developers.com/showpost.php?p=74749806&postcount=174
Restore or write IMEI numbers:
https://forum.xda-developers.com/showpost.php?p=74450547&postcount=76
TWRP
See these replies for root and TWRP (v1, legacy):
https://forum.xda-developers.com/showpost.php?p=74399450&postcount=60
https://forum.xda-developers.com/showpost.php?p=74429860&postcount=68
See these replies for TWRP without OTG and root (v2, now also legacy):
https://forum.xda-developers.com/showpost.php?p=74488885&postcount=96
https://forum.xda-developers.com/showpost.php?p=74490010&postcount=97
English TWRP in zip and img formats, also something about Forced Encryption (v3, but also follow instructions from v2)
https://forum.xda-developers.com/showpost.php?p=75544568&postcount=281
Magisk and Root
Summary of SuperSU, Magisk, Xposed and Android Pay compatibilities:
https://forum.xda-developers.com/showpost.php?p=74580626&postcount=135
Magisk Installation (legacy, but use it for instructions):
https://forum.xda-developers.com/showpost.php?p=74472235&postcount=89
Latest Magisk (permissive, hidelist persists, allowing module installation, yay!):
https://forum.xda-developers.com/showpost.php?p=75803660&postcount=299
Re-flashing STOCK ROM and/or updating Magisk while keeping data (requires TWRP)
https://forum.xda-developers.com/showpost.php?p=75064226&postcount=223
Audio Issues
Fix for Armor 2 Bluetooth Disconnect Issue
https://forum.xda-developers.com/showpost.php?p=75461843&postcount=279
Audio not routing through or unstable USB-C headphone jack?
https://forum.xda-developers.com/android/help/ulefone-armor-2-t3684566/post74621805#post74621805
Tweaks (Buttons, Persistent Notifications)
How to disable default PTT & SOS functions and replace functionalities (requires ROOT):
https://forum.xda-developers.com/showpost.php?p=74445439&postcount=72
How to get rid of Persistent NFC notification
https://forum.xda-developers.com/showpost.php?p=75049379&postcount=216
Fingerprint scanner is NOT SECURE
https://forum.xda-developers.com/showpost.php?p=75796254&postcount=297
Credits: @sumec100 @djvinniev77 @enzovic @Sebastl @jemmini (? from 4pda.ru) @TuksOID @sargon__
Have you had any software issues and can you assign anything else other than emergency contacts to the SOS button? I have an LG X Power with a cracked screen and have been looking into this phone because the doogee s60 and bv8000 pro both show problems and I don't feel like spending 600 for a cat s60 or s41
Sent from my LG-K450 using XDA-Developers Legacy app
Wish there was a way I could disable the sos button on my doogee s60
Hi,
i got mine a week ago, and i think this phone is really great so far. Only thing i'm missing is a way to root it, i have tried everything i could find, but nothing has worked so far.
Tommy
I really wanted to like this phone, but Bluetooth is essencial to me, and I cant keep a Bluetooth audio connection constant with out disconnects and connects randomly, is very frustrating, I was expecting a better quality of the audio of the internal speaker when making calls, the holes of the back speaker one is a dummy the is no sound from it, and battery is good but not so good for the capacity, I was expecting more, and the camera is really sub par with a slow auto focus. I why didn't they make the screws of the sim compartment flush with case, was so simple.
fluis70 said:
I really wanted to like this phone, but Bluetooth is essencial to me, and I cant keep a Bluetooth audio connection constant with out disconnects and connects randomly, is very frustrating, I was expecting a better quality of the audio of the internal speaker when making calls, the holes of the back speaker one is a dummy the is no sound from it, and battery is good but not so good for the capacity, I was expecting more, and the camera is really sub par with a slow auto focus. I why didn't they make the screws of the sim compartment flush with case, was so simple.
Click to expand...
Click to collapse
I just tested the Bluetooth on a speaker, i had no issues with it. As for the battery, there is a lot of settings you can tweak, and turn off all of the Google draining apps. I have installed Greenify too.
Camera is not the best, but it does the job. We get what we pay for, and for that price i cannot expect to get a better phone, that probably would survive a nuclear war lol
tmiland said:
I just tested the Bluetooth on a speaker, i had no issues with it. As for the battery, there is a lot of settings you can tweak, and turn off all of the Google draining apps. I have installed Greenify too.
Camera is not the best, but it does the job. We get what we pay for, and for that price i cannot expect to get a better phone, that probably would survive a nuclear war lol
Click to expand...
Click to collapse
I'm glad that you having a better experience with Bluetooth, I do hope that I can solve my problems with it.
I also just bought an Armor 2, and I also want to be able to configure the ptt and sos buttons in a better way. I hope people who know about this give us a hand. regards
I can assign emergency contacts to SOS button. Multiple ones in fact; if first person doesn't answer automatically calls the next one and so on. I was just curious to give them other functionalities, such as launching apps.
tony442 said:
Have you had any software issues and can you assign anything else other than emergency contacts to the SOS button? I have an LG X Power with a cracked screen and have been looking into this phone because the doogee s60 and bv8000 pro both show problems and I don't feel like spending 600 for a cat s60 or s41
Sent from my LG-K450 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did anyone manage to get Android Pay working? Android Pay doesn't verify the android, I was really looking forward to being able to use it...
I just got mine, love it for the price but unfortunately didn't read about android pay. I just tried and yep, no good to add payment cards. If you have a banking app that accepts card integration, it works that way, so it's just android pay/Google security.
Now, has anyone tried downloading the latest official ROM from needrom? They cite one from 10/9, I tried to install after ensuring the device is properly detected and the process fails. Something about Brom incompatible.
Not sure if anyone here has had successes with flashing MediaTek based devices, any tips?
djvinniev77 said:
I just got mine, love it for the price but unfortunately didn't read about android pay. I just tried and yep, no good to add payment cards. If you have a banking app that accepts card integration, it works that way, so it's just android pay/Google security.
Now, has anyone tried downloading the latest official ROM from needrom? They cite one from 10/9, I tried to install after ensuring the device is properly detected and the process fails. Something about Brom incompatible.
Not sure if anyone here has had successes with flashing MediaTek based devices, any tips?
Click to expand...
Click to collapse
Well, I was using a ulefone power 2 before this one. SP Flash tool version >5 works great. You just need to make sure device is fully powered off and connect usb cable. It might get into a bootloop, but if you start the flashing process while it's off it will get off of the bootloop and flash it. Hopefully at least.
I am using TSB, Santander, and nationwide. I guess none of them has card integration?
I'm searching a custom-Rom (lineageOS) for Armor 2. This Link ( rootmygalaxy[dot]net/lineage-os-15-for-ulefone-armor-2/) says "download it", but I can't found the Rom.
If I would self-compile it. Where I can find the driver for Armor 2?
With regards to android pay, I emailed ulefone support and they noted that they are working on it, need to get the keys to fix. They asked for device IMEI and will try to make the update via OTA. You can email them from their website. Looking at 3 weeks but I'm not counting on it. At least someone replied right away.
djvinniev77 said:
I just got mine, love it for the price but unfortunately didn't read about android pay. I just tried and yep, no good to add payment cards. If you have a banking app that accepts card integration, it works that way, so it's just android pay/Google security.
Now, has anyone tried downloading the latest official ROM from needrom? They cite one from 10/9, I tried to install after ensuring the device is properly detected and the process fails. Something about Brom incompatible.
Not sure if anyone here has had successes with flashing MediaTek based devices, any tips?
Click to expand...
Click to collapse
i installed the last room (nedroom) yesterday and was ok ok, i had a problem with connecting the usb (did not want to run the download process), helped "volume up" ON , the phone off, and then connect the usb to the pc and when I started process the "volume up" OFF , it started Mint 18.2 cinnamon 64-bit, SP_Flash_Tool_v5.1728_Linux - run as root , the MTKxxxx driver setting, for linux is here on XDA.
I would also be happy for recovery and root for armor 2.
with greetings of sumec.
sumec100 said:
i installed the last room (nedroom) yesterday and was ok ok, i had a problem with connecting the usb (did not want to run the download process), helped "volume up" ON , the phone off, and then connect the usb to the pc and when I started process the "volume up" OFF , it started Mint 18.2 cinnamon 64-bit, SP_Flash_Tool_v5.1728_Linux - run as root , the MTKxxxx driver setting, for linux is here on XDA.
I would also be happy for recovery and root for armor 2.
with greetings of sumec.
Click to expand...
Click to collapse
Nice. Did you wipe everything or was it an in place update that retained your data?
djvinniev77 said:
Nice. Did you wipe everything or was it an in place update that retained your data?
Click to expand...
Click to collapse
I deleted everything like a new phone. If you have a backup date so when you start offering a recovery from a backup or as a new phone. Every update to rom through flashtool makes full wipe data, so it's a good root and recovery.
Is there any way of disabling that wretched camera button ? I am fed up with clicking noises from my pocket as it takes shots, and deleting them all afterwards....
Gnubi said:
Wish there was a way I could disable the sos button on my doogee s60
Click to expand...
Click to collapse
I use the APP "Button Mapper" Ver: 0.54 Free
You can reconfigure PTT and SOS buttons to open your desired Apps.
You can also disable operation with the Lock-screen
My actual configuration for PTT button is:
Short press: Nothing,
Long press WhatsApp,
Double press: switch between DND, Vibrate and Outdoor sound mode
and for SOS:
Short press: Nothing,
Long press: PayPal
Double press: Shazam
wilkofife said:
Is there any way of disabling that wretched camera button ? I am fed up with clicking noises from my pocket as it takes shots, and deleting them all afterwards....
Click to expand...
Click to collapse
Camera button requires pro version, but I can live without it :good:
I noticed today that my USB-C to headphone jack cable is not working. Anyone else had that problem?
Also, ButtonMapper works great but sometimes it causes a soft reboot...