Related
Hello guys,
Did you receive an ota update today?
Its 30.02 MB. Mine is unbranded.
Sent from my SM-N9005 using xda app-developers app
After seeing your post I checked for an update and sure enough there it was. I too have an unbranded handset.
EDIT: Improved stability apparently according to the very brief description
Yea stability improved and thats it. I tried to get some info from sammobile or adam but nothing so far. Only what I found its Korean version (korea got that first, dunno).
Did you got push service update too?
Sent from my SM-N9005 using xda app-developers app
One handed operation seems to work with accessibility services, i havent tested them all though
Got update too. 36MB
SM-N900 Octa Core
No update available for mine, checked FOTA and KIES. Mine is unbranded too!
I got the Samsung Push update earlier though.
Mine N900 - Vietnam
Sent from my SM-N900 using Tapatalk 4
30.02 update doing it now
Android is updating 137 items
Got mine - Sim Free UK
What is the change log?
Change-Log
Hi
please check Change-logs, kernel date/version, and etc.
thnx
:good:
Getting mine now (CPW unlocked, uk). Hoping it will resolve the 'unable to reconnect to network after signal drop' and the 'knox hammers the cpu 24/7 even when not used' issues... we shall see...
g
uvaman said:
Yea stability improved and thats it. I tried to get some info from sammobile or adam but nothing so far. Only what I found its Korean version (korea got that first, dunno).
Did you got push service update too?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Yeah I got the push service update too
Sent from my SM-N9005 using XDA Premium 4 mobile app
Hopefully is will fix the BOOTLOOPS for some users too!
Funny, I actually checked for an update this morning completely randomly and there was nothing. This was at about 7AM UK time 7/10/13 however after reading this post I checked and sure enough there is a 30MB update! Downloading now.
emin1507 said:
What is the change log?
Click to expand...
Click to collapse
Same as usually, NONE...
deny_winarto said:
One handed operation seems to work with accessibility services, i havent tested them all though
Click to expand...
Click to collapse
Can anyone with one handed operation issue verify this?
In other thread somebody found out turning on accessibility service(s) disables one handed operation.
But i'm unsure which service blocks it.
This update might fix this problem...
Edit : Problem's still there.. In my case it's Martian watch's accessibility service
Oh well hope they fix it soon
x102x96x said:
hi
please check change-logs, kernel date/version, and etc.
Thnx
:good:
Click to expand...
Click to collapse
baseband: N9005xxubmj1
kernel: 3.4.0-1628120
october 1
build: Jss15j.n9005xxubmj1
---------- Post added at 12:57 PM ---------- Previous post was at 12:52 PM ----------
henklbr said:
Hopefully is will fix the BOOTLOOPS for some users too!
Click to expand...
Click to collapse
Boot looping still present for me unfortunately
Knox and not logging onto network NOT fixed for me either
I think this update fixed the scrapbook issue with YouTube
Sent from my SM-N9005 using Tapatalk 4
Are anyone else using a QX-device with Z1? The performance wasn't good with KitKat to start with, but now with Lollipop it is almost not usable, the preview keeps freezing. Anyone with the same problems? Any solutions for making PlayMemories work better?
No connection between Xperia Z1 Android 5.0 and QX10 with PlayMemories Mobile
Hi,
Since upgrading my Xperia Z1 to Android 5.0 and PlayMemories Mobile 5.2.3 (PMM) I have not been able to establish a connection between the Z1 and my Sony QX10 lens. The QX10 is detected in PMM, but every connection attempt is eventually abandoned. Any suggestions of how to fix this will be gratefully received!
Additional comments:
a) I carried out the "upgrade" from Android 4.4 to 5.0 by installing Sony's update when it became available.
b) Since publishing my post above, I deinstalled and reinstalled PMM (v. 5.2.4), but it did not make any difference.
c) My language preference on my Z1 (model C6903) was set to German, but even after changing it to English (UK), the problem persists
d) As soon as PMM detects the QX10 lens, it tries to connect automatically, but after 30 sec. it gives up.
I have had problems when using NFC for first time connection. For me it has been faster using regular WiFi direct and enter the QX's passcode.
No problems for me, qx10 and z1 lollipop...
Did you just updated to LL or full wipe before?
Sent from my TF300T using XDA Free mobile app
benben972 said:
Did you just updated to LL or full wipe before?
Sent from my TF300T using XDA Free mobile app
Click to expand...
Click to collapse
I flashed the prerooted LP rom to update to lollipop
hasn4179 said:
I flashed the prerooted LP rom to update to lollipop
Click to expand...
Click to collapse
It's a major Android update. Full wipe bro
Sent from my C6903 using XDA Free mobile app
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
I have no bug with my QX10 after full wipe.
Sent from my C6903 using XDA Free mobile app
benben972 said:
It's a major Android update. Full wipe bro
Sent from my C6903 using XDA Free mobile app
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
I have no bug with my QX10 after full wipe.
Sent from my C6903 using XDA Free mobile app
Click to expand...
Click to collapse
-----------
Thank you, I understand from your comments that one should not rely on Sony's upgrade / full install routine, but needs to do a manual full wipe of the the Z1 and then a manual istall of LP - is that right?
benben972 said:
It's a major Android update. Full wipe bro
Sent from my C6903 using XDA Free mobile app
Click to expand...
Click to collapse
I am sorry, I am having no problems with pmm. I thought you were asking me
mobilab said:
-----------
Thank you, I understand from your comments that one should not rely on Sony's upgrade / full install routine, but needs to do a manual full wipe of the the Z1 and then a manual istall of LP - is that right?
Click to expand...
Click to collapse
Yes, even though sony is generous enough to not wipe our data mercilessly when doing software upgrade, but full wipe after backing up your important data is the best way to enjoy the upgrade experience
I am not sure about stock but all CM and AOSP roms seem to have no issues.
mobilab said:
Hi,
Since upgrading my Xperia Z1 to Android 5.0 and PlayMemories Mobile 5.2.3 (PMM) I have not been able to establish a connection between the Z1 and my Sony QX10 lens. The QX10 is detected in PMM, but every connection attempt is eventually abandoned. Any suggestions of how to fix this will be gratefully received!
Additional comments:
a) I carried out the "upgrade" from Android 4.4 to 5.0 by installing Sony's update when it became available.
b) Since publishing my post above, I deinstalled and reinstalled PMM (v. 5.2.4), but it did not make any difference.
c) My language preference on my Z1 (model C6903) was set to German, but even after changing it to English (UK), the problem persists
d) As soon as PMM detects the QX10 lens, it tries to connect automatically, but after 30 sec. it gives up.
Click to expand...
Click to collapse
Thanks to all who replied to my post. The problem is now resolved. Instead of trying to connect to the QX10 lens via PMM, I allowed the Z1 to connect to the lens before opening PMM. That worked.
Hi everyone.
I recently flashed the latest Indian ROM from sammobile. Everything worked fine until recently I started facing these random color and display problems. Please help me.
I have also attached pics.
Hi screenshot 1 and 3 are also in the list of problems I faced, also other then that I had a black triangle appearing on the right side of the screen which is a problem you haven't mentioned or faced maybe.
I have a new N900 Indian Version.
Since you are facing the same problems as well then it is safe to assume that this is a software bug and should be addresse by a software update, I was a little worried and thought that there might be problem in hardware.
If you also faced the issue where the screen turned black from a side of phone then please do mention.
These problems happenend twice and I had to restart everytime.
Sent from my SM-N900 using Tapatalk
Root your phone
Install philz recovery
Then install resurrection remix
Everything working fine
Sent from my SM-N9005 using Tapatalk
NEERO said:
Hi screenshot 1 and 3 are also in the list of problems I faced, also other then that I had a black triangle appearing on the right side of the screen which is a problem you haven't mentioned or faced maybe.
I have a new N900 Indian Version.
Since you are facing the same problems as well then it is safe to assume that this is a software bug and should be addresse by a software update, I was a little worried and thought that there might be problem in hardware.
If you also faced the issue where the screen turned black from a side of phone then please do mention.
These problems happenend twice and I had to restart everytime.
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
I forgot to take a screenshot but my Google now widget turned blue and my avast antivirus widget turned to black..... but after a restart everything returned to normal.
ilyasmandli said:
Root your phone
Install philz recovery
Then install resurrection remix
Everything working fine
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
will try it. Thanks
musmas said:
I forgot to take a screenshot but my Google now widget turned blue and my avast antivirus widget turned to black..... but after a restart everything returned to normal.
Click to expand...
Click to collapse
I will keep updating if I face any more problems, my device is still under return period, but since this is a software issue I will keep it.
You also please keep updating.
Sent from my SM-N900 using Tapatalk
Could someone please suggest to me an alternative which is similar to the official samsung lollipop rom?
musmas said:
will try it. Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3030058
Sent from my SM-N9005 using Tapatalk
My simple question is going from marshmallow to the developer preview 5, currently I am at work and cannot backup my data I am full stock, so does the ota for the beta wipe my data?
Sent from my Nexus 6P using XDA-Developers mobile app
No it doesn't. Well, at least the other builds didn't.
For some reason, my phone won't grab dp5. It says I'm up to date. Anyone else have this issue?
Sent from my Nexus 6P using XDA-Developers mobile app
I'm in the same situation: my Nexus 6P doesn't seem to find the update.
On the developper preview page, it says it might take 24hrs to get it, but we're past that now.
I guess I'll just have to be patient!
I downloaded the ota zip file from the internet and just flashed it. Something interesting is happening. The Clock app is there but it isn't. I can't actually open it, but when I try to install it from the Play Store (there is a green box allowing the download, it doesn't say "update" or "open" btw) it says it's unable to install. Downloading and installing the apk from the internet returns an error that says theres a package already on my phone with by the same name. Looking through the system apps and my own user apps, the clock app is nowhere to be found.
So that's an issue I'm having, but I clean installed dev preview 5, I didn't take an update or anything
Rippley05 said:
For some reason, my phone won't grab dp5. It says I'm up to date. Anyone else have this issue? XDA-Developers mobile app
Click to expand...
Click to collapse
adubpak said:
I'm in the same situation: my Nexus 6P doesn't seem to find the update.
Click to expand...
Click to collapse
Same boat. Quite annoying. Going on 48 hours now, I think...
crackmulah said:
Same boat. Quite annoying. Going on 48 hours now, I think...
Click to expand...
Click to collapse
for me I opted in for the beta and I got the DP5 beta straight away now im stuck with another issue went home from work to backup my data and now my windows 7 computer is not finding my device first it came up as unknown device no updates for driver. After uninstalling all relevant drivers my device is not being found at all with the mtp selected. I may have to reinstall the sdk and check if adb picks it up if so I may have to reconfigure my windows 7 drivers if not ill check on a netbook to see if my cable or my charger port is malfunctioning.
Still on marshmallow if any advice please feel free to reply
thank you
From what I read there are some issues with dp5 specifically for the 6p they are working on it. That is why we haven't gotten the OTA. I would not side load as you will have issues with it. If you did sidload I would go back to 4 or else opt out of the dev program and roll back to marshmallow and wait till the issue is fixed and opt back in to get dp5.
---------- Post added at 06:21 AM ---------- Previous post was at 06:17 AM ----------
Aamir.Badat said:
for me I opted in for the beta and I got the DP5 beta straight away now im stuck with another issue went home from work to backup my data and now my windows 7 computer is not finding my device first it came up as unknown device no updates for driver. After uninstalling all relevant drivers my device is not being found at all with the mtp selected. I may have to reinstall the sdk and check if adb picks it up if so I may have to reconfigure my windows 7 drivers if not ill check on a netbook to see if my cable or my charger port is malfunctioning.
Still on marshmallow if any advice please feel free to reply
thank you
Click to expand...
Click to collapse
So you did not install the dp5 yet? Don't I hear there are issues with it. That is why it hasn't come to other peoples phone yet. And did you try different USB ports? I sometimes have a problem with one but not the others and it changes like USB ports are moody or something
mojorisin7178 said:
From what I read there are some issues with dp5 specifically for the 6p they are working on it. That is why we haven't gotten the OTA. I would not side load as you will have issues with it. If you did sidload I would go back to 4 or else opt out of the dev program and roll back to marshmallow and wait till the issue is fixed and opt back in to get dp5.
---------- Post added at 06:21 AM ---------- Previous post was at 06:17 AM ----------
So you did not install the dp5 yet? Don't I hear there are issues with it. That is why it hasn't come to other peoples phone yet. And did you try different USB ports? I sometimes have a problem with one but not the others and it changes like USB ports are moody or something
Click to expand...
Click to collapse
What issues are they having with dp5 should I flash it or wait untill I can backup my data or should I just scratch it and unroll for the beta? Because I need to backup my data first. Also the issue with it not connecting could be just a Driver issue so I'll have to double check it when I get home
Sent from my Nexus 6P using XDA-Developers mobile app
I don't know what the issues are I was reading a post about dp5 being available and in the comments section a few people were saying they didn't get it for the 6p and a few people said there was issues with it so that's why Google hasn't sent it out over the air yet. I think there is a way to delete the OTA you downloaded. Then just wait for it to come back when they send it out. Also if you got it right away it may actually be dp4 since dp5 is not over the air yet. Again I read this on the comment section of a post so how true it all is I do not know I was going to side load but before I did I wanted to know why it wasn't here yet and that's what I found out so I will just wait for it to come OTA. As for your USB problem maybe try reinstalling the Google drivers.
Recovery
anton22_99 said:
I installed DP5 and everything went fine.
Only one thing isn't working, recovery. When I select Recovery I get the Android passed out with a red exclamation mark on it's belly. "No command" is displayed.
I installed twrp-3.0.2-0-angler.img, but this one got stuck in the TWRP home screen.
gr. Antonie
---------- Post added at 01:52 PM ---------- Previous post was at 01:41 PM ----------
and I found the answer....... http://forum.xda-developers.com/showpost.php?p=66959810&postcount=7
Click to expand...
Click to collapse
Okay I cheered to early, thats the solution for stock recovery, I still can't enter TWRP after flashing it.
Same here haven't got it yet.
Sent from my Nexus 6P using Tapatalk
Aamir.Badat said:
What issues are they having with dp5 should I flash it or wait untill I can backup my data or should I just scratch it and unroll for the beta? Because I need to backup my data first. Also the issue with it not connecting could be just a Driver issue so I'll have to double check it when I get home
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
I just read that someone opted in after dp5 was out and they received dp4 so if you want to update you can you should get dp4 then when 5 is sent out you will get an update for that too. Dp4 is very stable I have been on it since it was out and have almost no problems whatsoever.
mojorisin7178 said:
I just read that someone opted in after dp5 was out and they received dp4 so if you want to update you can you should get dp4 then when 5 is sent out you will get an update for that too. Dp4 is very stable I have been on it since it was out and have almost no problems whatsoever.
Click to expand...
Click to collapse
Thank you also someone mentioned Google drivers where from? Does he mean the SDK itself?
Sent from my Nexus 6P using XDA-Developers mobile app
Aamir.Badat said:
Thank you also someone mentioned Google drivers where from? Does he mean the SDK itself?
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Check out this link it should tell you somewhere in there.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I think it is in developer tools.
---------- Post added at 12:49 PM ---------- Previous post was at 12:48 PM ----------
mojorisin7178 said:
Check out this link it should tell you somewhere in there.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I think it is in developer tools.
Click to expand...
Click to collapse
If not you can just google it Google drivers for nexus
I've been on dp5 since yesterday. I used the factory image though. Not having a single issue
mojorisin7178 said:
Check out this link it should tell you somewhere in there.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I think it is in developer tools.
---------- Post added at 12:49 PM ---------- Previous post was at 12:48 PM ----------
If not you can just google it Google drivers for nexus
Click to expand...
Click to collapse
Yeah anyway tried two more computers with the drivers and no go it states unknown USB device, I may need a reset ill have to push my files using airdroid check the md5 hash and then push them over to see if there is no corruption. Maybe a factory reset might help that's gna be my first try after backing my data.
Sent from my Nexus 6P using XDA-Developers mobile app
anton22_99 said:
Okay I cheered to early, thats the solution for stock recovery, I still can't enter TWRP after flashing it.
Click to expand...
Click to collapse
Solved,
install twrp-2.8.7.0-angler.img
reboot bootloader,
install twrp-3.0.0-0-angler.img
fastboot format cache
fastboot format userdata
Ok so I rooted 7 days ago from a clean install from odin and did all the trickster/interactive, force gpu etc to make it running smooth. But today I started experiencing apps like soundcloud crashing and giving me notifications it stopped, and then finally google play did it, now I just figured restarting the phone would normally fix it. But no, all it did was reboot, after the carrier sign it just vibrates and keeps vibrating and never boots up even after 15 minutes.
So I decided to just do a clean install and unroot again with my sammobile download. So I rooted AGAIN and shortly after, it started doing it.
Then I did a clean install again and rooted, now it's working fine for now. Anyone experience this? I have 20 days to return the phone, I got it from swappa
Sounds like to me that something in your rom became corrupt which isn't uncommon with rooted and modded roms. I might have wiped the caches before bombing it, typically it's a good practice to make regular complete backups of your phone incase of things like this so you can just flash your backup and keep it moving without starting over. Sorry to hear you had to start over!
Sent from my SAMSUNG-SM-G935A using Tapatalk
kokyleod said:
Sounds like to me that something in your rom became corrupt which isn't uncommon with rooted and modded roms. I might have wiped the caches before bombing it, typically it's a good practice to make regular complete backups of your phone incase of things like this so you can just flash your backup and keep it moving without starting over. Sorry to hear you had to start over!
Sent from my SAMSUNG-SM-G935A using Tapatalk
Click to expand...
Click to collapse
That's the next thing I did, wiped the cache from the recovery. Still had the problem, what I didn't do was force stop google play and wiped the data and cache from the app. But then again, after I rebooted, there was no way of doing that since it would never get past the carrier screen. I would have to do it before rebooting (I didn't actually think this would put me in a bootloop). Redownloading a new firmware from sammobile as we speak just in case it happens again. I'm also gonna have to try and see if it works during stock
btort1 said:
Ok so I rooted 7 days ago from a clean install from odin and did all the trickster/interactive, force gpu etc to make it running smooth. But today I started experiencing apps like soundcloud crashing and giving me notifications it stopped, and then finally google play did it, now I just figured restarting the phone would normally fix it. But no, all it did was reboot, after the carrier sign it just vibrates and keeps vibrating and never boots up even after 15 minutes.
So I decided to just do a clean install and unroot again with my sammobile download. So I rooted AGAIN and shortly after, it started doing it.
Then I did a clean install again and rooted, now it's working fine for now. Anyone experience this? I have 20 days to return the phone, I got it from swappa
Click to expand...
Click to collapse
Same thing happened to me on the S7E. Had the phone powered off for a day while I used another phone. When I turned it back on I couldn't open Google Play at all and was getting other fcs as well. Rebooted and it just stayed at the AT&T logo. Did a factory reset but after going through the device setup again, SuperSU wasn't there, so no root.
It all made no sense. I did nothing different than I ever did before. It seemed completely random.
Sent from my VK815 using XDA-Developers mobile app
Skizzy034 said:
Same thing happened to me on the S7E. Had the phone powered off for a day while I used another phone. When I turned it back on I couldn't open Google Play at all and was getting other fcs as well. Rebooted and it just stayed at the AT&T logo. Did a factory reset but after going through the device setup again, SuperSU wasn't there, so no root.
It all made no sense. I did nothing different than I ever did before. It seemed completely random.
Sent from my VK815 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's weird, I been rooting since my S4 days and nothing like this ever happened to me. I just hope it doesn't happen again, it'll force me to start over and potentially lose some of my data
btort1 said:
It's weird, I been rooting since my S4 days and nothing like this ever happened to me. I just hope it doesn't happen again, it'll force me to start over and potentially lose some of my data
Click to expand...
Click to collapse
its happened to me 3 times on my galaxy s7 at&t model. I'm now on stock until someone figures out this issue.
FreshIce21 said:
its happened to me 3 times on my galaxy s7 at&t model. I'm now on stock until someone figures out this issue.
Click to expand...
Click to collapse
Have you tried clearing the data and cache of the google play store before restarting the s7?
btort1 said:
Have you tried clearing the data and cache of the google play store before restarting the s7?
Click to expand...
Click to collapse
yes, sadly the play store would still not open and the phone still went into a boot loop after i restarted it.
btort1 said:
Have you tried clearing the data and cache of the google play store before restarting the s7?
Click to expand...
Click to collapse
Clearing the cache, data, etc., does nothing.
Sent from my VK815 using XDA-Developers mobile app
Any fix yet?
FreshIce21 said:
Any fix yet?
Click to expand...
Click to collapse
No, this is the 2nd time it happened to me in two weeks. such a bummer, maybe it's force gpu that's causing this? IDK but I just went back to stock and selling this phone. I only need root just to switch around the back button and recent apps anyways...hate how samsung doesn't let you change it to whatever you want...or even on screen buttons
btort1 said:
No, this is the 2nd time it happened to me in two weeks. such a bummer, maybe it's force gpu that's causing this? IDK but I just went back to stock and selling this phone. I only need root just to switch around the back button and recent apps anyways...hate how samsung doesn't let you change it to whatever you want...or even on screen buttons
Click to expand...
Click to collapse
I'm sorry man, its bummer your getting rid of the phone because of this issue but I understand rooting is pretty much neccisary for me too but I'm just gonna wait it out for fix. I wish you the best of luck my friend
Have you guys tried using the U fw? I never had that problem when I was using it. It happened only on the stock rooted fw.
Sent from my VK815 using XDA-Developers mobile app
Skizzy034 said:
Have you guys tried using the U fw? I never had that problem when I was using it. It happened only on the stock rooted fw.
Sent from my VK815 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm gonna try that rn, did you have this problem on the stock root? Or have you never rooted stock and its just not happening on the U firmware?? It could be a phone issue.
---------- Post added at 02:35 AM ---------- Previous post was at 01:38 AM ----------
Skizzy034 said:
Have you guys tried using the U fw? I never had that problem when I was using it. It happened only on the stock rooted fw.
Sent from my VK815 using XDA-Developers mobile app
Click to expand...
Click to collapse
did you install xposed on the g930u fw? if so how? did u use the g930 method?
rooted on g930u firmware with xposed installed, gonna see if my phone holds out. I'm really hoping it will!!
FreshIce21 said:
I'm gonna try that rn, did you have this problem on the stock root? Or have you never rooted stock and its just not happening on the U firmware?? It could be a phone issue.
---------- Post added at 02:35 AM ---------- Previous post was at 01:38 AM ----------
did you install xposed on the g930u fw? if so how? did u use the g930 method?
Click to expand...
Click to collapse
I had this problem on stock when rooted. I didn't have it when rooted on U.
Sent from my VK815 using XDA-Developers mobile app
---------- Post added at 03:39 AM ---------- Previous post was at 03:39 AM ----------
FreshIce21 said:
I'm gonna try that rn, did you have this problem on the stock root? Or have you never rooted stock and its just not happening on the U firmware?? It could be a phone issue.
---------- Post added at 02:35 AM ---------- Previous post was at 01:38 AM ----------
did you install xposed on the g930u fw? if so how? did u use the g930 method?
Click to expand...
Click to collapse
Sorry I have the 935A.
Sent from my VK815 using XDA-Developers mobile app
Skizzy034 said:
I had this problem on stock when rooted. I didn't have it when rooted on U.
Sent from my VK815 using XDA-Developers mobile app
---------- Post added at 03:39 AM ---------- Previous post was at 03:39 AM ----------
Sorry I have the 935A.
Click to expand...
Click to collapse
Alright hoping this will work for me then
I'm glad to hear I'm not the only person having this issue. This is the second time it's happened to me.
I'm going to try flashing that G930UUEU2APEH FW and then try rooting and reinstalling xposed to see if it happens again in the future.
For those of you that tried it, did using the G930A firmware work on your G935A?
Sideways02 said:
I'm glad to hear I'm not the only person having this issue. This is the second time it's happened to me.
I'm going to try flashing that G930UUEU2APEH FW and then try rooting and reinstalling xposed to see if it happens again in the future.
Click to expand...
Click to collapse
I did what you did and so far so good about a week in (knock on wood).
How are you doing? How long has it been and any problems??
Are you noticing the battery life is not as good?