Hi,
i got strange problem about my lenovo A850, i have force closes of all of my apps, i tried formatting lenovo with setting/recovery.. , try uninstalling apps, flash new rom with flashtool, but e.g. i uninstall candy crush saga, and after restart, i have candy crush saga again installed.. this happens about formats as well, i cant format/reinstall it at all..
A850 storage lock?
I have a very similar issue. The A850 I have is from China and came with a customer ROM loaded. When I try to factory reset either in recovery or from Android settings the unit remains unchanged. I have also tried to flash a new ROM with SP Flash with the same result.
Can anyone confirm if there is a way the Lenovo device could have been write protected from supplier?
RASTAS12 said:
I have a very similar issue. The A850 I have is from China and came with a customer ROM loaded. When I try to factory reset either in recovery or from Android settings the unit remains unchanged. I have also tried to flash a new ROM with SP Flash with the same result.
Can anyone confirm if there is a way the Lenovo device could have been write protected from supplier?
Click to expand...
Click to collapse
Same problem Here!
And it started this month... I own this phone since december 2013 and never had any problem.
I was using stock s123 rom (never flashed this phone before).
It started closing all apps and process, so I turned it off and on again. After boot the problem continues.
Tried wiping emmc via recovery and have no success.
Then I try flashing few different roms and the problem persist.
It´s like the phone is "Read Only" !!
As I see I´m not the only one with this problem, and never seen it before. We all started with the problem this month... very strange.
Perhaps it was an update from an app?
The problem started one morning after snooze the alarm. I found the phone was closing all apps and process.
I was using "Alarm Clock Plus". I also have "Clean Master" Installed.
Let´s see if we can find a solution, good luck!
Hahah...yep...
Now that swarm has finally arrived. The swarms of ****ty Lenovo phones...
Don't get it? As rumoured there will be a batch of Lenovo phones from an unauthorized Chinese manufacturer spreading throughout the world including Malaysia (received biggest impact), and I think you are the affected ones. For gods sake that phones are total... failure.:thumbdown:
Not really different from what I'm using right now, it's a CN firmware out of the box, but it's good (the kernel sucked, can't flash third-party recovery).
Have you tried root? Root unlocks features and you can troubleshoot better with root access. How? Framaroot. Risks? Well depend on the phone's architecture. If it's stable then it shouldn't be a problem.
How's that phone acting? You can still try many ways to troubleshoot, like using the Lenovo phone PC suite. If it still can react with the PC suite then there's chance. If it reaches to the extent of "The computer can't find your device" or "wrong phone" or worse, "Your device is not supported or invalid", boop(!) dead end, blame the Chinese, you've been fraud.
That's all I can help.
This was sent from my fully-Xposed-modded Lenovo A850 rooted stock ROM via XDA mobile app.
Lenovo A850
hi i am new bird in here, same situation happen to my lenovo a850 too.
any new info related to this? my lenovo a850 also have the same condition as other user, READ ONLY status.
i have tried many rom version, even ROW version, TWRP, CWM, but it still not sucess.
appreaciate if any have new info related.
thank you very much.
regads,
Hi guys,
My girlfriend purchased a brand new Xperia Z3 D6653 not too long ago (about 2 months ago?). I flashed the 5.1.1 pre-rooted firmware for her and it's working fine and all but it does a random reboot every day or so, at random times, with random applications.
I have tried 2 different pre-rooted 5.1.1 firmwares already (yes, the correct model D6653 as well) and it still does it. The System Incident reports don't really say much (in fact you only see details about when it crashed, nothing else), and it seems like Google Play Services is the only thing mentioned in the Application Report.
The same thing also happened (more frequently) when she was on the 5.0 pre-rooted firmware. I'm not sure why, I haven't unlocked the bootloader or anything, it's just stock pre-rooted ROM, that's it. I haven't flashed any other ROMs other than the official pre-rooted ones.
Furthermore, before I flashed the 5.0 and 5.1 firmware for her, the phone came with Android 4.4.4. She used it for a month and reported several crashes as well, so that's with the original factory firmware, unrooted, unmodified etc.
She doesn't run any dodgy or random apps, she's just a typical girl that use Facebook and texting, that's pretty much it. I've done a lot of research on this issue and it seems to be quite common, however there isn't really a solution to this. The same apps she currently use never caused any issues on her older phones.
Also in case anyone asks, the only reason I flashed the pre-rooted 5.1.1 firmware for her is because it makes it easier for me to manage her phone (with Teamviewer, you can remote into the phone as long as it's rooted). Also, I get to backup her phone and do tests etc, makes it easier for me.
Also, I'm not using any custom kernels or overclocking the CPU etc. Everything is just stock but rooted.
Could this be caused by a hardware fault in the phone? I'm not sure what else I can do and would appreciate some suggestions.
Nobody have this issue??
Well, how about you try to flash a full, clean, stock ROM, don't root it, don't install any unnecessary app and see where it goes? If the issue persists, try getting a logcat from the phone and we can take a look at it. If it works fine after returning to stock, there might be a problem with the ROM or some apps you are using.
If it really is Gapps that are causing all the trouble, go to APKMirror and download the latest apps available (Play Services, etc) and see where it goes.
As mentioned already, prior to flashing anything, my girlfriend was running a completely stock, factory version of the phone. It came with Android 4.4.
I could flash a completely stock 5.1 ROM but was hoping that someone would share their experiences or a potential solution to this, considering this is quite commonly asked. I would also like to avoid doing this if possible, because if I were to go back to rooting the device, I'd have to downgrade to v4.4 pre-rooted, then flash to 5.1 rooted with custom recovery. It's just a lot of work for a simple testing that could be answered by others if possible.
Anyway, she didn't have any apps installed other than Facebook and Whatsapp, that's it. I might test with GAPPS and see how it goes, but I thought I'd ask here in case someone knows it's definitely a hardware issue or something else.
i would definitely give a pure stock 5.1.1 a go. I used to get the random reboots on the previous versions but i no longer have such issue.. Make sure you do a clean wipe and do it a few times.
Hi all, it's been a while but I thought I'd post an update and share what I've found/learned so far....
Basically, I'm still getting the frequent random reboots. I've tried reflashing the ROM and also tested out the latest .232 pre-rooted stock ROM, still getting the same issue. I've noticed that other than Google Play Services, sometimes Gapps will crash as well. But most of the time, there's nothing reported in the system or application crash logs. I've tested with everything running as stock, no additional apps installed. I then decided to flash the Minimal GAPPS 5.1.x and that sort of made the phone a bit more stable, but still reboots randomly every now and then.
Later on, I decided to try a custom ROM that still works on a locked bootloader. I found this here:
http://forum.xda-developers.com/z3/development/d6603-23-1-1-28-t3102271
The chef has provided a .232 firmware for you to flash in recovery, as well as the ROM base for the D6603 model. Mine is a D6653, but luckily the chef has also provided a D6653 patch for you to flash as well. I've flashed the ROM like so:
1. Wipe everything except my external microSD in TWRP. So basically, wipe system, data, cache, dalvik, internal storage etc.
2. Install .232 firmware.
3. Install v10.5
4. Install v12.0
5. Install D6653 v5 patch
It boots up fine but after using it for a while, I still get the random reboots. What's interesting is that I've also tried without flashing the D6653 patch, which essentially means I'm running just the D6603 base ROM on my D6653. It works, but still crashes as well. I just found it quite surprising that a D6653 could run a D6603 ROM, but it does make sense considering the main differences is just the baseband/frequencies.
Anyway, I later on decided to flash the pure 5.1.1 stock ROM, still getting the crash. Again, everything is tested on pure stock, no additional apps etc installed.
I'm starting to think perhaps this is a hardware issue on my phone?? I noticed that sometimes, my screen will show a bit of tearing and then it'll crash not long after. BUT, I also know that as soon as gapps or google play services crash, the phone will crash not long after as well.....
In fact, I later on used Titanium Backup to convert Google Play Services from a System to a User app, the phone will just boot into the lockscreen and then restart every time. This is a bit ridiculous because I've done this several times on other phones before and they never had such an issue. Of course, I'm not saying I always run Google Play Services as a User app, but that was just for testing and I honestly don't think it should cause a bootloop just because of that. I've also cleared dalvik and cache by the way, so it doesn't make sense that the phone boots into the lockscreen and then just restarts randomly.
I haven't tried uninstalling Google Play Services completely, but at this point I'm back to square one as I've exhausted pretty much all my options and it's been a complete waste of time. I'm beginning to hate this phone more and more. The only thing left is to unlock bootloader and play with other custom ROMs. But yeah, flashing the .232 firmware didn't fix it, AND flashing pure stock 5.1.1 Android didn't fix it either...
Just wondering if others have the same issue and any ideas what could be causing it? If I provide some Logcat logs, would someone be kind enough to look into this for me?
Update:
I'm still getting the random reboots and I think it's very likely to be hardware related. But sometimes also a bit related to software, specifically with Google Play services. I've had more time to test out a few things since my last update, they are as follows:
- Tested complete stock 4.4 ROM without root. Still crashes every now and then, but not as much compared to 5.0 and 6.0 (doesn't matter if it's stock or custom ROM).
- Finally gave in and unlocked bootloader (backed up my DRM keys of course). I thought perhaps that the stock Sony roms (and even the stock-based Sony custom roms) have issues for some reason. They are all the same base, so I thought I'd do a fair test by trying a completely different based rom, such as AOSP. I've used CM 1.2.1 nightly here:
forum.xda-developers.com/z3/development/rom-cyanogenmod-12-nightlies-xperia-z3-t3010201/page117
And yes, I know that nightly have bugs, but the nightly build as of 2016-03-03 seemed pretty stable according to most users. I've tried various other AOSP based roms and stock based Sony roms (for unlocked bootloaders) and they all produce crashes.
I've flashed custom kernels as well and updated my recovery to TWRP 3.0, but all the same results. On all of the custom ROMs I've flashed, the only thing I've done was setup my Google account (so I have my contacts and Gmail) and that was it. No other apps installed. I wanted to limit the environment down to just the stock setup of the ROM itself, as this helps me rule out any potential bugs caused by 3rd party apps.
Having done all of the above and still resulting in crashes, it's safe to assume that this is most likely unrelated to the software, but hardware. I've noticed that sometimes when I scroll a page too fast and move it up and down with my thumb, the screen will freeze and restart.
However, sometimes I will get crashes related to Google Play Services. Anything that relies on Google Play Services will crash randomly. If you re-open the apps, it just crashes again. If you force stop the app and open it, still crashes. The ONLY fix is to restart the phone. I have tried flashing different GaPPs, starting with the pico and nano versions, as well as the ones recommended by the ROM chefs. Still the same result.
So the conclusion is, I haven't really gotten anywhere with this annoying issue. There's definitely an issue with the phone somewhere, maybe a bit of software related, but mostly hardware.
Please help me,
How to root freetel kiwami samurai and custom rom for it!
It is use android 6.0 not good
Any updates?
Kingo and kingroot work, but no custom roms. No twrp or any recovery for it either.
Would like to know if anyone has any ideas or news on this.
I'm looking at one of these on ebay right now, leaning towards buying it. I'd almost certainly buy it if I knew there were custom ROMs available.
For the price, definitely an amazing phone. It really sucks that there is nearly zero support for it anywhere.
For $120 I decided to grab it to replace my constant headache with our note 4 here.
The main camera, very, very nice.
The speed seems alright. The feel, the build is great.
The battery seems to drain kinda quick, but that might be my imagination.
I'm comparing it to our Y6Max and phab2 plus.
I used Kingo root on it initially, then went to and currently have kingroot on it. Kingo had annoying floating ads.. Kingroot seems decent but I'm suspecting that it has something to do with the battery drain.
Worst part for me at the moment, trying to work around not having twrp+xposed on it.
(the nav/status bar is taking up too much of the nice 6" screen)
If anyone has any way of getting twrp or something similar on it.... Please let me know - help us all out.
After some fighting with Kingo and kingroot, back and forth, I managed to get supersu to take over, install binaries and update... Now no more Kingo or kingroot. Tempted to try installing xposed, but I'll wait for now.
Found a command to enter in terminal to use full immersive mode all the time...
Adjusted dpi as well
Now the phone is looking nice.
Just gotta wait and wish for someone kind enough to help out with getting a custom recovery on these phones.
Really loving this phone
Stock rom for freetel kiwami FTJ152D
Hi all, I need stock rom or worked rom for my freetel kiwami FTJ152D.
Can someone upload this or what is the link to download this ?
I bricked my phone after flashing custum rom MM6.0 published on needrom. No touchscreen, very bad display, no imei, no root.
Please, help me.
meteor37 said:
Please help me,
How to root freetel kiwami samurai and custom rom for it!
It is use android 6.0 not good
Click to expand...
Click to collapse
Hi, I used kingoroot online and mine was rooted. (Freetel samurai kuwami FTJ152D stock rom 5.1)
But now, I have a big issues, I flashed it with a MM6.0 publshed on needrom and now there's no touchscreen, screen display very bad, no imei (impossible to put imei and root with few known method) and no root.
Could you please upload your worked rom ? Stock rom or custum but work fine.
Or where can I find link to download it ?
Please help me.
Myloverboy said:
Hi, I used kingoroot online and mine was rooted. (Freetel samurai kuwami FTJ152D stock rom 5.1)
But now, I have a big issues, I flashed it with a MM6.0 publshed on needrom and now there's no touchscreen, screen display very bad, no imei (impossible to put imei and root with few known method) and no root.
Could you please upload your worked rom ? Stock rom or custum but work fine.
Or where can I find link to download it ?
Please help me.
Click to expand...
Click to collapse
Seems like the rom on needrom was for a slightly different phone. However the phone is so cheap now its almost disposable ($100)
I have been able to get recovery but it is in microscopic Japanese Kanji, showing off the high resolution of the screen, but I can't read Japanese.
That is actually a diagnostic menu in chinese you went into (Google Translate FTW lol). For the stock rom recovery, you can turn the phone off, hold volume up button and plug in the usb cable that is connected to a computer. You can also hold volume up and power and let go of power as soon as freetel logo comes on. You will enter stock recovery that is in english but it is useless because you cannot use stock recovery to undo what you have done to your phone since there is no place online you can find a stock rom of this phone model (I have searched for many many hours online).
I am working on getting stock rom dump off my phone using sp flash tool but biggest headache for me has been the scatter file so far. Without it, I can't use the 'read back' option to extract an image dump of working stock rom. Only scatter file i found is from extracting the needrom MM 6.0 which is for the samurai FTJ152D.
I am unable to make a scatter file using MTK Droid tools since MTK Droid tools do not work for 64-bit mtk processors like the one in Kiwami. Scatter files are CPU specific but they are further modified based on the model of the phone and the android version of the rom, so the scatter file from MM 6.0 for FTJ152D is very close to what we need for FTU152D but even a slight variation will result in a rom dump that will not work. If any of you are willing to try, I can use the scatter file from MM 6.0 (FTJ152D) on my phone that is FTU152D to extract a rom dump, but keep in mind that this will probably not work and might make matters worse for your phone. Scatter files are sort of like 'Table of Contents', and if the page numbers are wrong you end up reading wrong chapter... (you get the idea).
I haven't found any other way of making a scatter file. If anyone knows how to get a scatter file from a phone running 64-bit processor such as MT6795, please help us out. Thanks.
Just an update, while trying to make a 'read back' dump using sp flash tool, I accidentally started a download of the FTJ152D MM firmware I was using the scatter file from... Needless to say now I have the demo version of marshmallow and have lost my IMEI info from phone. I did make a 'read back' dump of the phone before i messed up, using the guide from syserr about "Dump Full Rom" at
https://forum.xda-developers.com/showthread.php?t=2540400.
NOTE: If you are still on stock rom that the phone shipped with, DO NOT try upgrade using SP flash tool, at the very least you will loose IMEI information for both sim slots. For me, the phone connects with sim but I can only get 2g data speeds and make phone calls.
I am hoping that the following information can help others:
1) Most Important: If you root, do not use SUPERSU 2.79 or above versions or phone will be stuck in bootloader. Even if you make a backup of boot.img, sideloading it from ADB did not work for me, it kept failing. I am not sure if earlier SuperSU versions work or not, if they do work, make sure you disable auto update for SuperSU in Google Play Store.
2) Even if you make a backup of nvram.bin using sp flashtool, it will NOT restore your imei information in the phone because from what I researched so far, this information is populated using the BPLG and AP databases that are included with the stock firmware as separate files and quite possibly with 64-bit mtk processors, this information is protected and encrypted. Other possibility is that the nvram.bin i recovered from my whole rom dump is for lollipop and since phone is running on marshmallow, this bin file is invalid? I did try flashing two different nvram.bin (one i recovered from the stock dump i made when phone worked, another i downloaded from internet) using flashtool and it made the matters worse, all baseband info disappeared and both sim slots just totally greyed out in settings. If it greys out for you, just format the whole flash and flash the MM firmware again without any nvram partition. Just leave default settings for nvram in scatter file alone.
3) Currently, there is no way to root this phone when on marshmallow. Do not try the chinese one-click or other software such as miracle box, all the ones i downloaded and/or tried or not tried, were flagged by Anti-Virus as trojans and viruses.
4) Be very careful when trying to flash software on this phone, make sure you use the correct Preloader.bin file. The marshmallow firmware on needrom website has a preloader.bin file in it and it works fine. Do not attempt to try preloader from other similar phones or you will brick this phone permanently.
5) ADB and Fastboot commands do not help because the phone is not rooted anymore once you upgrade to marshmallow using the FTJ152D marshmallow firmware from needrom.
6) I have tried combinations of boot.img, and system.img from Priori 3 (it is also dual sim and rom on needrom website is android 5.1), was hoping for a miracle but no luck.
7) MTK Droid Tools works partially with this phone. Most options in the tool require root or do not work with mt67xx processors. I found mtk droid tools useful to enter recovery directly when usb debugging was enabled or to go to ADB terminal to try sideload or reboot bootloader to enter fastboot.
8) Even if you enable oem unlock in developers, the option (volume+up) in Fastboot menu to unlock the bootloader doesn't work. It seems that many MTK processors have this option disabled by the manufacturer.
9) TWRP custom recovery will not work with this phone because the 'boot script' (not bootloader) before actual recovery in the recovery partition has the touch disabled. I was able to get CWM to work by directly flashing it instead of stock recovery but installation of any zip files through recovery fail still.
10) I can confirm that the scatter file in marshmallow rom for FTJ152D available at needrom website has the right entries and address locations for our phone (FTU152D) because I was able to use that scatter file and a Hex Editor program (search for HxD on download.cnet.com) to carve out almost all the partitions from the 2gig partial rom dump I had of my phone in working state. When carving partitions from the dump, some trimming for certain folders is required because cutting the partition by size and making it a .bin or .image file will give errors in SP Flash Tool otherwise. The marshmallow rom or a Priori 3 lollipop rom, both can be used as a reference when cutting out the extra bytes.
If you are like me and have upgraded to marshmallow using the FTJ152D software, there are not many options. I haven't given up yet though, I backtracked my steps trying to make a backup of the phone in its current state using SP Flash Tool full rom dump and it was successful. If I could get my hands on full rom dump of 5 gigabytes of a working phone with lollipop software, I am confident I can restore my phone back to lollipop. This may not fix the IMEI problem but once the phone is running lollipop, it is possible to root it again using kingroot or towelroot and then use one of the imei repair apps or a program to rebuild nvram folder using the BPLG and AP databases and use root explorer to place it in the phone.
Phew... a long write but hope this helps others, and if anyone can help by sharing any thoughts or uploading their stock rom dump if own same phone (can read syserr's method of using 'read back' in SP flash tool to make one big partition dump for the whole rom instead of making seperate partitions which is a painstaking process.
Finally, some very good news for people like me who are stuck, figured out a way to root and install Xposed both Please give credit to Magisk and Xposed developers listed below.
Root:
Root this phone while it is running the FTJ152D marshmallow stock rom using the Magisk guide here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Follow the "Via Magisk Manager (Only support v14.0+): ... " method to install the magisk manager and the .zip file right through it. It patches the boot and makes a patched boot image that you can transfer to your computer and then rename it to boot.img and replace the original boot.img in the FTJ152D MM rom folder. Then use the SP Flash tool, load the scatter file in the rom folder and the 'Format all + Download' option in download tab (it will give you PMT error if you try to just flash the new boot.img alone). Hit the download button, turn the phone off, and connect it to the computer via usb. Everything else should be straightforward but if any issues, ask here, and I will try help if I can.
Xposed:
There is no touch support to make custom recovery work on this phone yet and the only custom recovery i got to work was an old version of CWM which behaved same like stock recovery and refused to let me flash zip files. The workaround I found that worked was 'Flashify' on Play Store. Now that root is working, flashify seems to work (tried Flashfire too but it just hangs and phone freezes). Follow the steps below:
1) Download and install the latest Xposed Installer Apk from their page.
2) Download the appropriate xposed zip file (SDK23 ARM-64), version 89 worked for me. Use Flashify to flash the zip file. If any issues come up, ask here and I will try help.
Official Xposed post is here:
https://forum.xda-developers.com/showthread.php?t=3034811
This post is also very helpful:
https://forum.xda-developers.com/showpost.php?p=67696847&postcount=2
All credits go to the respective developers for their work, including @topjohnwu, @rovo89, @mGforCe, @SolarWarez, @MaArCiN074 and others. Don't forget to thank them.
I also have been able to replace the demo mode logo with logo that was in the partial stock rom dump and will share it soon.
IMEI issue:
After gaining root and installing Xposed, a number of apps can help to at least temporarily get the IMEI written to the phone, that lasts till factory reset. One issue that people like me who installed the FTJ152D MM rom is that the bands in the phone are now based on the Japan region and almost all the frequencies and bands needed for phone to get 3g and 4g signal are disabled in the phone. From researching about this issue I found out (I may be wrong but that's the only information I could find and the bands that are enabled seem to confirm this), is that the latest mediatek chips come with all 41 bands and the phone manufacturers and operators disable or enable bands based on their regions and preferences, so that this phone, FTU152D is probably the exact same hardware as the FTJ152D and the only difference is the software which disables and enables the bands based on the baseband version of the rom. This is a problem for ppl like me living here in U.S but the enabled bands may be fine elsewhere. There is no way to change the bands as they are greyed out when you go to modem information though 'Phone Information' section (apps like 'Advanced Signal Status' can help access it). It doesn't allow me to select and enable band 4 and 12 as these are greyed out (but these worked before with stock rom, so I know the hardware supports them just the baseband version is wrong now).
Anyone know or can help get the right bands working, or have any hints to point me in the right direction, please post here. Thanks.
I was able to finish dicing up the raw dump to make back a working FTU152D stock rom with good baseband. Here is the link for instructions and download link:
https://forum.xda-developers.com/general/general/kiwami-samurai-ftu152d-stock-lollipop-5-t3750068
I have a question for any and all kiwami samurai owners /users. Is it just me, or does your WiFi seem to cut off regularly? I have been fighting with this from pretty much day one. When I'm using a sim card in the phone, I don't notice anything because the mobile data from the sim is working. But, I have 2 of these samurai phones now, and I bought a blackberry passport for my main phone and now both samurai phones are usually only using WiFi. Funnier thing... They both seem to have WiFi issues at the same time. How I know?... Well, I use an app on all of our phones and devices here - Zello. When the connection is lost, Zello sounds an alarm and lets me know. So if the phones are acting up, we'll hear this all day, disconnecting and reconnecting. I got one more for you, the disconnects seem much worse when I use the phones compared to just having them there sitting around. I even went as far to install many WiFi watching, locking, reconnecting apps to try and force the connection to stay on and alive. They have their work cut out for them seeing as when these phones decide they want to drop the WiFi connection, they will fight these apps to maintain WiFi connection until these apps pretty much give up. I have these as back up phones basically, so it doesn't matter so much but of course, this is extremely annoying and a huge inconvenience at times. Any one else out there experiencing this? The only thing I did do that may have a place in all this... Rooted the phones, and also I removed every google app. I have a note 2, note 4, doogee y6 Max, Lenovo phab 2 plus, tab s and an HTC one m8 that are all the same... Rooted and google removed. Playstore play services all that stuff - gone. Those phones don't act up anywhere close to as bad as these samurai phones. Many times I fight the WiFi off because doze and all that power save crap but these samurai phones are tough to figure out. Anyone have any ideas? I also froze and deleted a bunch of system apps(I know, I know) but that was only after I noticed the WiFi issue on the phone and was trying to see if possibly one of the system apps had anything to do with the WiFi disconnects or any power save features or control. So anyone.... Ideas?
J&G said:
I have a question for any and all kiwami samurai owners /users. Is it just me, or does your WiFi seem to cut off regularly? I have been fighting with this from pretty much day one. When I'm using a sim card in the phone, I don't notice anything because the mobile data from the sim is working. But, I have 2 of these samurai phones now, and I bought a blackberry passport for my main phone and now both samurai phones are usually only using WiFi. Funnier thing... They both seem to have WiFi issues at the same time. How I know?... Well, I use an app on all of our phones and devices here - Zello. When the connection is lost, Zello sounds an alarm and lets me know. So if the phones are acting up, we'll hear this all day, disconnecting and reconnecting. I got one more for you, the disconnects seem much worse when I use the phones compared to just having them there sitting around. I even went as far to install many WiFi watching, locking, reconnecting apps to try and force the connection to stay on and alive. They have their work cut out for them seeing as when these phones decide they want to drop the WiFi connection, they will fight these apps to maintain WiFi connection until these apps pretty much give up. I have these as back up phones basically, so it doesn't matter so much but of course, this is extremely annoying and a huge inconvenience at times. Any one else out there experiencing this? The only thing I did do that may have a place in all this... Rooted the phones, and also I removed every google app. I have a note 2, note 4, doogee y6 Max, Lenovo phab 2 plus, tab s and an HTC one m8 that are all the same... Rooted and google removed. Playstore play services all that stuff - gone. Those phones don't act up anywhere close to as bad as these samurai phones. Many times I fight the WiFi off because doze and all that power save crap but these samurai phones are tough to figure out. Anyone have any ideas? I also froze and deleted a bunch of system apps(I know, I know) but that was only after I noticed the WiFi issue on the phone and was trying to see if possibly one of the system apps had anything to do with the WiFi disconnects or any power save features or control. So anyone.... Ideas?
Click to expand...
Click to collapse
There are a lot of variables that could be causing your WiFi issues. Since it is happening on two identical phones, have you installed Zello on a different phone to notice if it happens on that phone at the same time as well? It is possible that it is your WiFi causing the issue more than the phones themselves. How far from the wireless router are you when this happens? It could be that the radio/antenna range on the Samurai phones is lower than other phones and when WiFi signal is weaker, these phones just disconnect. Also, in WiFi settings if you have changed 'Keep Wi-Fi on during sleep' from 'Always' setting to another setting? Another possibility is that 'Scanning always available' setting, if turned on, and you have uninstalled Google or system app(s) that interact with this setting, it could cause a bug where network is disconnected momentarily (see if this setting is on, turn it off).
How strong, how many bars does your WiFi signal show? Mine shows full bars up to 30 feet from gateway and at least half strength in my bedroom and WiFi is not affected or dropped even at half strength. Are you using 2.4Ghz or 5.0Ghz frequency? Try using 2.4Ghz as 5.0Ghz although faster, has a much lower range and if signal is weaker it does disconnect the phone to save battery life.
You could also check WiFi settings using the *#*#4636#*#* if it shows any issues in there.
Android# said:
There are a lot of variables that could be causing your WiFi issues. Since it is happening on two identical phones, have you installed Zello on a different phone to notice if it happens on that phone at the same time as well? It is possible that it is your WiFi causing the issue more than the phones themselves. How far from the wireless router are you when this happens? It could be that the radio/antenna range on the Samurai phones is lower than other phones and when WiFi signal is weaker, these phones just disconnect. Also, in WiFi settings if you have changed 'Keep Wi-Fi on during sleep' from 'Always' setting to another setting? Another possibility is that 'Scanning always available' setting, if turned on, and you have uninstalled Google or system app(s) that interact with this setting, it could cause a bug where network is disconnected momentarily (see if this setting is on, turn it off).
How strong, how many bars does your WiFi signal show? Mine shows full bars up to 30 feet from gateway and at least half strength in my bedroom and WiFi is not affected or dropped even at half strength. Are you using 2.4Ghz or 5.0Ghz frequency? Try using 2.4Ghz as 5.0Ghz although faster, has a much lower range and if signal is weaker it does disconnect the phone to save battery life.
You could also check WiFi settings using the *#*#4636#*#* if it shows any issues in there.
Click to expand...
Click to collapse
Thanks very much for the help....
so, the other phones( we have many) are mostly all set up the same way, all have zello...and no, they don't have the same issue disconnecting at the same time the freetels do.
The router here probably needs to be replaced but, cant get around to that for now.
a little update to this problem... I didn't want to try installing xposed before, because I didn't have recovery installed...got it done using flashfire. this got me xposed and I did this just for the hell of it since i didn't care so much about the phones since they were just being pains. However, after doing this, i also decided to install Lspeed. I remembered that I checked this app out before and i seen that It had some settings in it for tweaking wifi and Lnet. Not even sure what these would do, I started to mess around in there and toggled a few things on...just to see what would happen. also, i just happened to see something in xposed to download "Wifi regional problem solver". again, not sure what this would do, or if it would do anything, i said lets do it...installed it. and believe it or not, haven't had any issues like before with wifi since. Now, not sure what actually fixed the problem or if the problem is actually fixed or if it just took a break from driving me mad, but yeah...it's actually not a bad phone now.
as for Lspeed....using version 1.4.27(like this more than the latest for some reason) and I set up most things in the app to "balanced". not performance , not for battery. Under LNET Optimizer .... NET buffers : BIG. RIL tweaks enabled. NET TCP tweaks enabled. NET speed+ enabled. wifi scanning ...while i've always had off on all devices for as long as i can remember having androids...here in Lspeed i toggled on and set supplicant scan interval to 15secs and wifi idle ms to 1. left google dns off.
just if anyone wanted to know or cares ....and hey, maybe someone knows what any of that stuff means and might be able to say..hey, none of that would've changed anything so it's worthless....or maybe explain what each means or does and why it might have helped.
thanks again.