Hey.
I'm having difficulties with new cyanogenmod 7.1
I Followed different tutorials and none of them helped me.
I started with stock 2.1 rom and did all the unlocking bootlader stuff , then installed custom kernel and managed to install cyanogenmod 7.1 but then occurred a funny thing . There was only FreeXperia logo showing up, nothing else, and it rebooted all the time. Then I flashed stock rom again and tried to understand what's wrong and tried to use different kernels and nothing.
So my question is. Is there anything I'm missing here?
Henri.
Full wipe after you install rom.
Dot forget to make backups first.
about that...
i always do full wipe after installing roms, so it has to be something else.
Thnks anyway..
But after browsing several topics in XDA forum I saw that I'm not only one with the problem.
If anybody has had the problems like I do and got the solutions, every kind of tips are welcome.
Thread closed
I got it all working, but I don't know what was the reason, because, I just did the whole thing again about three or four times, and then it just booted and worked.
I never could install Cyanogenmod in my phone... could you?
Hey!!!
I could write a total working tutorial how I managed to get to work everything, but it takes time, so if you want tutorial send me private message , so I create it for you.
Henri
Does wifi and/or 3G work for you longer then 15 minutes?
No, but at the moment I'm using RC1 flawlessly.
Sent from my E15i using XDA App
coffee-break said:
I could write a total working tutorial how I managed to get to work everything, but it takes time, so if you want tutorial send me private message , so I create it for you.
Henri
Click to expand...
Click to collapse
umm..why not post it publicly man ? It will be useful for everyone including myself.
Would also like that tutorial
ok,
i'm gonna post it here after finishing it.
So, the wanted tutorial is here!
Firstly it's for xperia x8(E15i) to be superclear.
I'm gonna put that tutorial into steps.
STEP 1
You need to have stock 2.1 rom with baseband XXX015 , if you don't have it, then go to Sony Ericsson's webpage and download the upload service and flash it back into your phone.
STEP 2
You phone has to be rooted. Easieset way is using Superoneclick(sorry, i'm not gonna provide the link, because it's just google-ing thing to you who need rooting program)
STEP 3
Now, everything comes to the unlocking process for bootloader. there is also tutorial how to succeed when using s1tool and msm7227 (if you have problem, then I don't know). Try to undestand the tutorial of doing it.
S1tool is for identifying if your phone is unlocked or not.
and msm7227 is for unlocking
tut is here - LINK
I wish luck, don't brick your phone, but it's not so hard to understand tutorials if you have right phone and right tutorial.
STEP 4
I totally suggest to install stable rom. The reason is that released 7.1 has bugs and incompatibility with some phones and i haven't got wifi and 3g working , but tried different roms and kernels.
I provide links i got from deani77, big thanks to him.
You can try this link for FXP028 ROM - http://www.multiupload.com/IIWIPG1ALH
For FXP030 kernel try this link - http://hotfile.com/dl/132650338/7b17...USTOM.ftf.html
(that release is RC1 of Cyanogenmod 7.1 but I think it's the best at the moment!)
and you download all the files as usual. Rom zip package should be in the SD card's root folder, so you can easily install it after flashing kernel
STEP 5
installing is quite simple actually. You need to use flashtool that is provided with rom(link in step 3)
firstly you flash kernel. Kernel file is the one you downloaded .ftf file. You have to put that file(X8_custom.ftf) into firmware folder which is inside of flashtool folder.
Then you open flash tool and you click FLASH, then appears little window and you click ok and then you need to plug in your phone into usb while holding down back button. Your phone has to be off when you are doing that. Then flashtool identifies your phone and will flash the kernel into your phone. when everything comes smooth then you now have fxp custom kernel. it has clockworkmod recovery and you need to click several times back button when FreeXperia logo appears.
STEP 6
You have to do factory reset and format, also i suggest from advanced menu using format system.
Then you select from the recovery menu install custom zip... and you browse your rom .zip file and if everything is OK then it should display "installing update or smth" if it's done then good for you, you reboot and it should work.
IF YOU WANT GOOGLE APPS , then google the link and install it same way you did with the rom. You can do it any time.
..
So if anything is not understandable then ask. I'm not an expert or anything, I just did things like I described.
Best,
Henri.
i have still had problems with bootloop and passing md5 checksum any idea on how to fix this?
mm.. at the moment I don't know but what that md5 checksum means?
I fixed my bootloop issue when I flashed back to stock rom, then I just did all the steps I describe again (not unlocking bootloader because it was unlocked already) .. but I don't know what's really does the bootlooping thing. I just got lucky. It took me like billion hours until I got it working...
I am stuck after porting the LG G 2 ROM into Nexus 4everything goes fine till I go to boot where I get stuck at the Google logo install fine but then upon reboot get stuck at the Google logo I have taken in copied over the three lib files as suggested in mini tutorialany help would be greatly appreciated
streetmedic said:
I am stuck after porting the LG G 2 ROM into Nexus 4everything goes fine till I go to boot where I get stuck at the Google logo install fine but then upon reboot get stuck at the Google logo I have taken in copied over the three lib files as suggested in mini tutorialany help would be greatly appreciated
Click to expand...
Click to collapse
You do know that porting a ROM involves much more than following an "Easy port" tutorial, don't you? Drivers, kernels, framework, libs etc. have to be ported too.
Does adb work? If yes, try getting a logcat.
abaaaabbbb63 said:
You do know that porting a ROM involves much more than following an "Easy port" tutorial, don't you? Drivers, kernels, framework, libs etc. have to be ported too.
Does adb work? If yes, try getting a logcat.
Click to expand...
Click to collapse
Yes I'll grab that and yes I'm aware that I'll need to do some modding of files . I'll post those in a bit once kids are off my computer. Both bases I used are 4.22 and are both made for T-Mobile. I let you know.
I am keeping eye on this thread. Thanks.
Sent from my Nexus 4 using Tapatalk
I tried to get a log but if I am correct it won't log due to its a fresh install and it does not boot past Google logo. If I am mistaken please show me where I have gone wrong. Help is most welcome and always appreciated.
streetmedic said:
I tried to get a log but if I am correct it won't log due to its a fresh install and it does not boot past Google logo. If I am mistaken please show me where I have gone wrong. Help is most welcome and always appreciated.
Click to expand...
Click to collapse
you will need drivers for it to boot, among other things. most likely you would will have to write your own, since they are closed source. its not as easy as just making the rom fit the n4, its everything else that goes with it that makes it hard.
I can help you maybe
Add me on skype i can help you maybe skype:vova50006:good:
Okay, so I finally decided that ICS wasn't enough for me any more, and that I needed to go with a custom ROM. Unfortunately, it seems most tutorials for the A500 were created over a year ago, and they were full of broken links and information that wasn't relevant. So, I combined a few different tutorials and was pumped when I got Cyanogenmod up and running, and then heartbroken when it started giving me some message about cyanogenmod.account stopping working. Threads on XDA suggested a reflash, and I did so, and now I have even worse problems.
The same ROM when flashed takes me to the Cyanogenmod load screen and stays there for seemingly forever (left it for 20 min before moving on). I tried flashing another Cyanogenmod ROM and it won't go past the custom bootloader's startup screen.
Now, I am very new to this, and if I've been a total noob, let me know where I went wrong.
-I rooted my tab months ago, using an .exe I downloaded that did most of the work for me.
-I installed a custom recovery/unlocked bootloader (V8-Thor 1.7.3) which works wonderfully, lots of nice features.
-Then flashed an unofficial Cyanogenmod 10.2 ROM with some GApps according to instructions from this guide (http://forum.xda-developers.com/showthread.php?t=1622425)
-tried just about everything I can think of short of asking for help, so that's why I'm here.
Please let me know if I've missed something, or if you need any more information, I'm looking to get this working, and just generally much around with my tab (maybe try and run ubuntu, or other roms, but I'd REALLY like to CM 10.2 running first).
I'm putting my tabs future in your hands, please help me!
CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs
I flashed this but I didn't get the custom boot logo.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine
Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo
mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0
Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.
The app downloaded from f-droid worked for me as well, many thanks!
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.
Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.