Hello all.
I've searched these forums for a bit now, looking for someone in a similar situation; after around 10 pages of 'wrong country' and a loooot of Googling, I can't seem to identify the issue I'm having.
The problem is as follows: I own a Galaxy Express 2 (a rather unpopular device judging by what I've seen across the Interwebs). It came with a stock 4.2.2 ROM when I bought it some time ago. It was rooted within a couple of days - no problems whatsoever. Then the 4.4.2 update came out and I downloaded and subsequently flashed (via ODIN) the one for Vodafone Spain (as it was the only currently available ROM that was Kit Kat). I had noticed a few problems: certain items like LED flashing as notification in Accesibility settings were missing, others didn't work (Smart stay, tap to answer). Not really a problem, but it did raise a red flag. No other problems with the ROM itself, it was very stable.
Attempting to correct this issue, I had flashed 4.4.2 meant for Vodafone Romania (the carrier for where I live seemed the most obvious choice, I was hoping the aforementioned settings might work). They still did not. A few days ago, I got a rather annoying problem where Play Store would crash every single time it attempted to update any app. Naturally, I googled a few fixes, tried those, nothing worked. I had pondered flashing a recent Google Apps pack (like the ones you'd get when flashing CM), but was unsure if I'd do more damage - figured they might not play well if flashed forcefully over the pre-existing stock apps.
I then flashed CM (the release available for Galaxy Express 2, just out of curiosity, and Google Play worked flawlessly, even when updated to the latest version).
TL;DR: Stock 4.2.2 -> Stock 4.4.2 (Spain) (first language appeared as spanish) -> Stock 4.4.2 (Romania) (first language appeared as croatian) -> CM build currently out for Express 2 -> Emergency recovery via KIES 3 flashed another 4.4.2 it seems (but also loaded in Croatian)
The issues I'm currently having:
1) Ever since the Romania Vodafone 4.4.2 install (that would be the second stock ROM I've flashed), the first language I encounter is Croatian and it installs typical bloatware in another language (which I would also imagine would lead me to download incorrect applications from the Market, so I figure if I fix the phone's localization problem, the market will follow)
2) Ghost tapping on the keyboard (not noticed before, was not present on CM, hence I've ruled out a hardware issue, or on any installation previous to CM)
I have tried various fixes: via CWM recovery, tried wiping data/cache/dalvik, formatting /system and /boot before flashing a 4.4.2 for Romania (still loaded in Croatian), via ODIN. I'm fairly certain there's something residual I've mucked up on my phone, because the device identification when I connect it to my laptop via USB is from the previous install (now it has a different name).
IMEI number is fine (read about potential corruption of EFS). Currently, I was going to attempt flashing the stock ROM (4.2.2) from Sammobile, but after so many attempts (and hairs pulled out), I'm not holding out hope that that will fix it.
CSC is fine (correctly identified as CNX, which is the appropriate code for Vodafone, Romania), as confirmed by connecting to KIES.
Eventually, I would like to have 4.4.2 on it, if at all possible. I have a basic understanding of these things - but I can't understand why the phone would be fooled into thinking it's in another country. My assumption is that such information is stored somewhere that isn't wiped between flashing.
Really clueless at the mo'. I wanna try flashing stock, but I fear doing so will fix nothing, and my last hair will fall out - I feel that the problem would affect all installations.
(I wouldn't mind using CM, but it's a big buggy, and I need stability above all else).
It does in fact seem that my problem lies in the CSC. Samsung Kies, being what it is, seems to have incorrectly indicated where I am.
An appstore app has identified my CSC as being VIP (which is one from Croatia). I will attempt to correct this issue via whatever method I can find, and see what happens.
Update: As it happens, I've successfully flashed stock ROM (4.2.2), corrected CSC (and verified it with root explorer, to confirm it's the right one), flashed 4.4.2, it installed all the proper Vodafone apps (in English).
However the odd ghost tapping problem remains: even when holding my finger on the touchscreen, it behaves as if I were tapped eratically everywhere near the original tapping point.
The device name is still read as incorrect when plugged into USB. I am certain this is software related now, or rather, some freakin' leftovers I can't seem to find and clean.
Hi,
This is from the S4 section, so don't use any files from here, but the advice may help perhaps..
http://forum.xda-developers.com/showthread.php?t=2611340
Other than that, I can't find anything relevant on XDA for your device. It could be hardware if flashing stock firmware didn't help. You can ask about it here if you wish,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!
I own the boost mobile XT1031 model and finally decided to unlock the bootloader and root the device. Everything was going fine. But not Google search and chrome wont work. Search crashes and gives me an option to report it. Chrome and chrome beta fail to connect to the Internet even though other apps such as Facebook, REddit and other Google apps connect just fine. When i go to enable now cars it says that i need to check my Internet connection. The only other thing that has changed is the font is different for some reason. I did install a few xposed modules to change the look and feel, such as Gravitybox, Android L Theme, and tinted status bar. They seemed to have no effect on the device in a negative way. I also had greenify but i only had it hibernating apps i hardly used. If anyone knows what to do to fix this it would be very appreciated.
I would like to add that the issues are still persistent even after factory reseting the phone. I am running stock rom, Would it be possible to get rid of these problems by reflashing the original rom or flashing a custom rom? I am also using TWRP. I do have a backup of before the issues started but that is on my laptop which i won't be near until Wednesday. Thank you again in advance.
I would try flashing back to stock or your original recovery and try the different xposed modules one by one to see which (if any) are causing the issues. Have you tried installing a custom rom?
Onion Grease said:
I would try flashing back to stock or your original recovery and try the different xposed modules one by one to see which (if any) are causing the issues. Have you tried installing a custom rom?
Click to expand...
Click to collapse
No custom ROM yet, I was thinking about flashing CM11 but so far have no other plans. I have a backup saved on my computer from before i installed the different modules, would that fix the issue of the crashing apps and font?
PV.Srg said:
No custom ROM yet, I was thinking about flashing CM11 but so far have no other plans. I have a backup saved on my computer from before i installed the different modules, would that fix the issue of the crashing apps and font?
Click to expand...
Click to collapse
It should, but you may want to update your apps to current versions as well after the restore. I don't know how old your backup is, but updating may solve some your issues.
I would definitely resist the urge to try any lollipop roms on the xt1031, as their are numerous connectivity issues at this point for cdma. But there are some great KitKat Roms (CM11 is one of them) available. I'm currently using PA.
Onion Grease said:
It should, but you may want to update your apps to current versions as well after the restore. I don't know how old your backup is, but updating may solve some your issues.
I would definitely resist the urge to try any lollipop roms on the xt1031, as their are numerous connectivity issues at this point for cdma. But there are some great KitKat Roms (CM11 is one of them) available. I'm currently using PA.
Click to expand...
Click to collapse
Thank you, I resisted the urge and now there is a soak test zip so ill be doing that soon.
I restored the backup, it was 2 days old, and everything is working fine now. Adaway for youtube was the cause of the crashing, as for the font change, i'm not sure.
hi,
I have a nexus 5 with lollipop 5.0.1, xposed (gravity box, amplify and greenify activated) and franco kernel.
My problem is that in the wifi settings i dont see any wifi available, my phone just connects to the few wify that i had already saved.
I donwload a third party app (wifi manager) and from the app i can see every connection available near me, so the problem must be rom related, not hardware related.
I tried flashing system and boot from 5.0 image, but that didnt solve the problem (i tought that going back to stock kernel and deactivating xposed would have helped). So i tried to flash 5.1 (i'm actually still with 5.0.1 because i want to use xposed), i flashed boot system radio and bootloader and that solved the problem, without wiping any data or app.
Since that solved the problem i thought that maybe bootloader or radio had something to do with it, ann i flashed again 5.0.1 with the new bootloader and the new radio but the bug was still there, nothing changed.
Is this a common bug?i searched in the forum and trough google but i couldnt find anyone with my exact problem, do you think you can help me?
If you need any log i'll post it here, just tell me what you need!
Thanks in advamce
AtField said:
hi,
I have a nexus 5 with lollipop 5.0.1, xposed (gravity box, amplify and greenify activated) and franco kernel.
My problem is that in the wifi settings i dont see any wifi available, my phone just connects to the few wify that i had already saved.
I donwload a third party app (wifi manager) and from the app i can see every connection available near me, so the problem must be rom related, not hardware related.
I tried flashing system and boot from 5.0 image, but that didnt solve the problem (i tought that going back to stock kernel and deactivating xposed would have helped). So i tried to flash 5.1 (i'm actually still with 5.0.1 because i want to use xposed), i flashed boot system radio and bootloader and that solved the problem, without wiping any data or app.
Since that solved the problem i thought that maybe bootloader or radio had something to do with it, ann i flashed again 5.0.1 with the new bootloader and the new radio but the bug was still there, nothing changed.
Is this a common bug?i searched in the forum and trough google but i couldnt find anyone with my exact problem, do you think you can help me?
If you need any log i'll post it here, just tell me what you need!
Thanks in advamce
Click to expand...
Click to collapse
http://forum.xda-developers.com/google-nexus-5/help/wifi-stuck-t2721643
beekay201 said:
http://forum.xda-developers.com/google-nexus-5/help/wifi-stuck-t2721643
Click to expand...
Click to collapse
Thanks for the answer but my WiFi actually turns on without any problem, and also connect to the few WiFi that I already had saved! And with a third party app i actually have no problem, It works as it should
Anyone?
Bump! I still have this problem
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.
After updated to Lineage 17.1 i am facing problems with Wifi. In Lineage 17.1 everything works fine (except wifi-calling and volte). When flashing back to Stock (via Oreo-RUU or TWRP Restore) i don't get any wifi-connection. If turning on wifi, system turns off immediately. In settings I found, that mac address is 02:00:00:00:00:00... searching this problem, i found out, that this problem happened often via update from android 5 -> 6. Flashing Stock ROMs didn't help, restore of prior LeeDroid Backup neither.
Did anybody face this problem in former times? Does anybody know where MAC is stored / what the problem may be?
masi79 said:
After updated to Lineage 17.1 i am facing problems with Wifi. In Lineage 17.1 everything works fine (except wifi-calling and volte). When flashing back to Stock (via Oreo-RUU or TWRP Restore) i don't get any wifi-connection. If turning on wifi, system turns off immediately. In settings I found, that mac address is 02:00:00:00:00:00... searching this problem, i found out, that this problem happened often via update from android 5 -> 6. Flashing Stock ROMs didn't help, restore of prior LeeDroid Backup neither.
Did anybody face this problem in former times? Does anybody know where MAC is stored / what the problem may be?
Click to expand...
Click to collapse
I am experiencing the exact same issue. Same MAC address, same wifi issue. I tried flashing to stock Oreo, same issue. I'm going to try flashing stock Nougat, but I have doubts about that working. I also tried clean flashing the RR-P 7.0.2 ROM, and the same issue happens there too. I could not fin a way to restore the MAC address. I was able to look up the original address from my router's device log . . .
My HTC is the US T-Mobile version. @Golv can you help us with this new issue?
-UPDATE-
So far, going to stock Nougat INSTANTLY works. Right on the setup menus, all the wifi networks show up. Odd how stock Oreo gave us issues, but Nougat didn't. Will be going to RR-P 7.0.2 and seeing if the fix sticks I removed the SIM card when I put the phone back to Nouagt BTW if that affects anything.
-UPDATE 2-
Flashed stock Oreo after flashing Nougat, and in the setup menus, the wifi networks are showing up in STOCK OREO. Still with SIM removed. Now to flash the RR-P rom and see if I'm all set.
-FINAL UPDATE-
Flashed RR-P 7.0.2. Everything is back to normal.
Ikarbb said:
I am experiencing the exact same issue. Same MAC address, same wifi issue. I tried flashing to stock Oreo, same issue. I'm going to try flashing stock Nougat, but I have doubts about that working. I also tried clean flashing the RR-P 7.0.2 ROM, and the same issue happens there too. I could not fin a way to restore the MAC address. I was able to look up the original address from my router's device log . . .
My HTC is the US T-Mobile version. @Golv can you help us with this new issue?
-UPDATE-
So far, going to stock Nougat INSTANTLY works. Right on the setup menus, all the wifi networks show up. Odd how stock Oreo gave us issues, but Nougat didn't. Will be going to RR-P 7.0.2 and seeing if the fix sticks I removed the SIM card when I put the phone back to Nouagt BTW if that affects anything.
-UPDATE 2-
Flashed stock Oreo after flashing Nougat, and in the setup menus, the wifi networks are showing up in STOCK OREO. Still with SIM removed. Now to flash the RR-P rom and see if I'm all set.
-FINAL UPDATE-
Flashed RR-P 7.0.2. Everything is back to normal.
Click to expand...
Click to collapse
Thank you very much! I checked whether the sim card has an effect, removed it and flashed Stock Oreo -> problem still exists. Then i flashed Nougat an experienced the same effect: Wifi worked right on the setup menu.
@Golv do you have any idea why this happens? I think, this problem should affect anybody, who wants to go back to prior versions.
masi79 said:
Thank you very much! I checked whether the sim card has an effect, removed it and flashed Stock Oreo -> problem still exists. Then i flashed Nougat an experienced the same effect: Wifi worked right on the setup menu.
@Golv do you have any idea why this happens? I think, this problem should affect anybody, who wants to go back to prior versions.
Click to expand...
Click to collapse
I believe it is related to the hosd_signed.img file that likely writes over the persist partition. By downgrading, we are overwriting the hosd and the nougat ruu then formats and rewrites a new MAC address. It was interesting to see this happening, but I'm glad I found a workaround.
Sorry for the delay in reply. For some reason notifications stopped coming to me ...
Most likely you should change Mac address setting from random to device’s Mac address before switching to stock (Settings - Network - Wifi - Network details - Advanced - Privacy - USE DEVICE MAC).
Golv said:
Sorry for the delay in reply. For some reason notifications stopped coming to me ...
Most likely you should change Mac address setting from random to device’s Mac address before switching to stock (Settings - Network - Wifi - Network details - Advanced - Privacy - USE DEVICE MAC).
Click to expand...
Click to collapse
Hi Glov,
cant find these steps in U11 Leedroid. can you throw some more light please.