I'm on TMO version converted to intl.
How do I update to latest image?
I'm still on DE2117_11_c.15.
I'm rooted.
I have not tried this, just throwing it out there. There is a app called Oxygen Updater on the play store. Might be worth checking out.
UPDATE: so it looks like this app supports both full and incremental updates on the n200. If you are rooted, however, the incremental updates wont work. As far as supporting one of these frankenstein n200's, uncharted waters my friend.
Yes, I can't do the incremental update. What a pain in the asss...
I removed root and updated. Will reroot later.
radekmazur said:
I removed root and updated. Will reroot later.
Click to expand...
Click to collapse
I always post the latest DE2117 masgisk patched boot.img file in this thread. To take partial updates, you do have to be unrooted/clean os to get to C_18 now.
I decided to install lineage. Want to see how it does on this phone.
Lineage actually runs worlds away better than the vanilla 12 rom. It does have a couple of issues currently that I couldnt find a work around for, so went back to stock. Many thanks to scanman0 for the stock\patched boot images; hes saving many people countless hours dealing with getting these images how he is.
the.real.p3y0t3 said:
Lineage actually runs worlds away better than the vanilla 12 rom. It does have a couple of issues currently that I couldnt find a work around for, so went back to stock. Many thanks to scanman0 for the stock\patched boot images; hes saving many people countless hours dealing with getting these images how he is.
Click to expand...
Click to collapse
What kinds of issues are u having with lineage?
Ok well this is going to probably sound petty, and would not have an effect on most users I believe, but yeah I can't get a couple of games to load. Heres the thing: the games are Netflix android games... And something tells me its a DRM\Webkit\etc issue and not really Lineages fault. I DID have magisk installed, however that never had any effect on Netflix for me; It just always worked without issue.
There were a couple of other little annoyances, but no show stopper errors or crashes and it ran buttery smooth without any of the hiccups it seems like stock roms had\have.
Metconnect2000 said:
What kinds of issues are u having with lineage?
Click to expand...
Click to collapse
Only issue I had was (mostly) with a game. While playing Pokemon GO the display would just go all black for a couple seconds as if it were disconnected, then come back. It would happen randomly and several times in a row in quick succession. Never figured out what was causing it so went back to stock.
Link575 said:
Only issue I had was (mostly) with a game. While playing Pokemon GO the display would just go all black for a couple seconds as if it were disconnected, then come back. It would happen randomly and several times in a row in quick succession. Never figured out what was causing it so went back to stock.
Click to expand...
Click to collapse
Ah.. good to know. Thanks
radekmazur said:
I removed root and updated. Will reroot later.
Click to expand...
Click to collapse
do you use magisk?
if yes, go to magisk app, then press uninstall, then press restore images.
if you get the message "stock image backup not found", then you can't do it this way.
do not reboot.
go to oxygen updater then download the incremental
after that, go to the oneplus software update app which lets you do local upgrade and then press install on the .zip file
do not reboot yet, go to magisk and press install, then install to inactive slot
after that, press the reboot button in magisk.
Related
Cyanogenmod 12.0 Semi-Official
HTC Evo 4G LTE ( jewel )
Basic Overview
Source built Cyanogenmod 12.0 hot off the server. No changes at all to anything. Sync and build.
This has not been officially released as of yet. Still very early code, there will be random bugs, and missing features still. They are coming.
Please refrain from reporting bugs because of this. Thank you.
Besides that It seems good enough for a "Daily Driver". No major malfunctions, just the random glitches as the code evolves as normal.
Requirements:
S-Off, HBOOT 2.10+ & 4.13.651.4 Firmware Update to function correctly. @Captain_Throwback's TWRP 2.7.1.0b , 2.8.0.x, 2.8.1.x recoveries recommended.
NPL recovery though. That's the only catch here.
Installation...
Wipe, reboot recovery.
Install CM-12.0, reboot.
One it finishes booting, reboot to recovery.
Install gapps, wipe dalvik & cache, reboot.
Profit
ROM Source: https://github.com/CyanogenMod/android/tree/cm-12.0
Original Kernel Source: https://github.com/CyanogenMod/android_kernel_htc_msm8960/tree/cm-12.0
Bugs...
Superuser settings cause Settings to FC currently. But remains functional.
Previous Release:
https://www.androidfilehost.com/?fid=95832962473395998
Current Release:
https://www.androidfilehost.com/?fid=95832962473397836
Current Release Gapps:
https://www.androidfilehost.com/?fid=95832962473397837
Partner Builds & Sub-projects
Partner Builds:
11-29-2014 Build: https://www.androidfilehost.com/?fid=95832962473394878 by @fizbanrapper
And it begins...
First Android 5.0 ROM for Jewel that works... And based off of one of the best Android 4.4.4 ROMs there was for Jewel as well. Enjoy everyone. Much more to come.
Cool. Sounds good. I may give it a try, just to say that I have 5.0. But I would like to have the camera working... But it is probably something that I can live with.
I've tried a flash, for the first time I experienced stuck in the boot, after I restarted again and then succeed, what becomes of bugs on camera?I have tried to take a picture with my camera and it worked fine, but I want to report that when opening the case of mobile networks in settings force close , thanks for dev , sorry for my bad english
ermariio said:
I've tried a flash, for the first time I experienced stuck in the boot, after I restarted again and then succeed, what becomes of bugs on camera?I have tried to take a picture with my camera and it worked fine, but I want to report that when opening the case of mobile networks in settings force close , thanks for dev , sorry for my bad english
Click to expand...
Click to collapse
First off, great work beating me to the punch on this. I was tinkering with CM 12 code all month.
Secondly, I can repeat what was said previously. I got a bootloop the first time, but after I turned it off, it booted up fine.
ocarinaz64 said:
First off, great work beating me to the punch on this. I was tinkering with CM 12 code all month.
Secondly, I can repeat what was said previously. I got a bootloop the first time, but after I turned it off, it booted up fine.
Click to expand...
Click to collapse
same here but it is running great so far
Ok. Camera bugs. I don't know. I just cut what lines out the compiler broke because of. And I have no cam. Idk why. My mobile network seems fine.. But come on guys. This is early code, so there's going to be bugs I have no control over. That would be more CMs thing. I just am basically doing what LSX64 did. No boot loop for me either. Weird...
I was saying this rom is running great thanks for the hard work. :good: I didn't expect to see a 5.0 rom for this phone. so thanks again for this rom.
jarheadusmc67 said:
I was saying this rom is running great thanks for the hard work. :good: I didn't expect to see a 5.0 rom for this phone. so thanks again for this rom.
Click to expand...
Click to collapse
Ok. No worries. I didn't either. So when I got it to even fire up.. I knew what I had to do. 5.0 for everyone, and making it a UnityROM, just a bonus
Does LTE work?
Psycario said:
Does LTE work?
Click to expand...
Click to collapse
I have no idea. I think so.. I have no LTE where I live
jarheadusmc67 said:
I was saying this rom is running great thanks for the hard work. :good: I didn't expect to see a 5.0 rom for this phone. so thanks again for this rom.
Click to expand...
Click to collapse
I can say that as long as I've got my Jewel, and as long as the code works, I'll be cranking things out. I'm really partial to Slim series ROMs, but I was super eager to try out L so I flashed this one. Also, it looks like CM is going to continue to support this thing for the foreseeable future. Once they start their nightly builds, it should be available there, too. Though, without the extra butter.
Thanks for the work and the build.
ocarinaz64 said:
I can say that as long as I've got my Jewel, and as long as the code works, I'll be cranking things out. I'm really partial to Slim series ROMs, but I was super eager to try out L so I flashed this one. Also, it looks like CM is going to continue to support this thing for the foreseeable future. Once they start their nightly builds, it should be available there, too. Though, without the extra butter.
Thanks for the work and the build.
Click to expand...
Click to collapse
No problems there man I know you do your thing. But.. Do you happen to know how to do that dark ui button
ZX64 said:
Ok. Camera bugs. I don't know. I just cut what lines out the compiler broke because of. And I have no cam. Idk why. My mobile network seems fine.. But come on guys. This is early code, so there's going to be bugs I have no control over. That would be more CMs thing. I just am basically doing what LSX64 did. No boot loop for me either. Weird...
Click to expand...
Click to collapse
Well done! Glad to have you back!
This is working surprisingly well for a first build. The first KitKat builds were total garbage, comparatively.
I'm using it as a daily driver for now. The latest Beta SuperSU will get you properly rooted on LP too. I'll post the link when a bit later (have to find it again), but Google will get you there for now.
Issues (none of which are controllable by the OP) and fixes
Issue one - keyboard doesn't always pop up like it's supposed to. So far I've been able to fix it every time by simply turning my phone sideways, then back.
Issue two - Sometimes not all choices are viewable in pop up boxes. I was able to get around this by changing screen density to 280.
Issue 3 - APN menu doesn't do anything of value. To change apn settings, download sql editor. Open telephony.db which is located at data/data/android.providers.telephony/databases. Then locate the 310120 lines and edit the values as you normally would for your carrier. Your phone will now use the desired APN settings.
Is it possible to turn off your modem like it was in 4.4? I don't see any option for that anywhere. The reason being is that I don't like my phone downloading things when I don't tell it to. It wastes my data, and gets annoying.
ocarinaz64 said:
Is it possible to turn off your modem like it was in 4.4? I don't see any option for that anywhere. The reason being is that I don't like my phone downloading things when I don't tell it to. It wastes my data, and gets annoying.
Click to expand...
Click to collapse
Does this help?
http://forum.xda-developers.com/showthread.php?p=56866237
fizbanrapper said:
Does this help?
http://forum.xda-developers.com/showthread.php?p=56866237
Click to expand...
Click to collapse
Theoretically that is what I was looking for. But now that I'm testing my phone, I realized that I'm not able to actually make or receive calls. Idk if that was because of the widget or what. It might also be a carrier problem.
EDIT - It was a carrier problem, but caused by what, I can't say.
fizbanrapper said:
Well done! Glad to have you back!
This is working surprisingly well for a first build. The first KitKat builds were total garbage, comparatively.
I'm using it as a daily driver for now. The latest Beta SuperSU will get you properly rooted on LP too. I'll post the link when a bit later (have to find it again), but Google will get you there for now.
Issues (none of which are controllable by the OP) and fixes
Issue one - keyboard doesn't always pop up like it's supposed to. So far I've been able to fix it every time by simply turning my phone sideways, then back.
Issue two - Sometimes not all choices are viewable in pop up boxes. I was able to get around this by changing screen density to 280.
Issue 3 - APN menu doesn't do anything of value. To change apn settings, download sql editor. Open telephony.db which is located at data/data/android.providers.telephony/databases. Then locate the 310120 lines and edit the values as you normally would for your carrier. Your phone will now use the desired APN settings.
Click to expand...
Click to collapse
Yeah kk was garbage for the first few months even. So LP way better so far in that way. Glad to have me back? I was here before?
Ok so next build I'll set to 280 and see about that. I have no idea on the KB lol I just used google KB cause it has a dark ui option.
But properly rooted... Big must have there. That I want fixed lol.
I have tried this rom full day, very nice, I just restart sometimes problematic when there is no data connection and GPS is not accurate,
Welcome to SlimLP for the Jewel!
NOTE: This ROM requires the new HBOOT 2.10+ partition table. I may provide links later on how to get that if you aren't up to speed yet. You will also want to use the newest recovery from Captain_Throwback.
Downloads:
Slim-Jewel-LP-5.1.1
Slim Gapps
My older Slim Builds are still available.
Install Process:
Flash the .zip, Gapps, & SuperSU, then reboot. It will dirty flash fine for future 5.1 builds. Make sure you do a clean wipe from other ROMs, or from 5.0 builds.
Word of warning - Let it take some time on the first boot. As much as 4+ minutes, but it's good after that.
Not working - Nothing that I know of yet...
Special thanks to Slim team for all your work, and for guiding me through the new build process.
Also thanks to Captain_Throwback, Fizbanrapper, Tolipohs and ZX64 for your personal help to me along the way.
Sources:
ROM:
https://github.com/SlimRoms (lp5.1)
Kernel:
https://github.com/CyanogenMod/android_device_htc_jewel/tree/cm-12.1
XDA:DevDB Information
SlimLP 5.1.1 for Jewel, ROM for the Sprint HTC EVO 4G LTE
Contributors
ocarinaz64
Source Code: https://github.com/slimroms
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 2.10+ Firmware
Based On: SlimLP
Version Information
Status: Alpha
Created 2014-12-16
Last Updated 2015-06-07
Reserved
I'll take a look when I get the time. Glad you got it working. I'm happy to see some lollipop ROMs popping up.
Sent from my BN NookHD+ using Tapatalk
One of my favorites. Thanks for bringing it forward. I'll try and install tonight when I'm bored at work.
I installed it tonight. It behaved oddly. I first flashed the ROM and booted it up without gapps as is my habit. I tried to set up wifi and it gave me "authentication error" and never connected (to either of the 2 hot spots I have access to) I also didn't have any network access but didn't worry about it to much yet
I booted back into recovery and flashed gapps as well as a file of commonly used apps I keep so I don't have to download them every time. Anyway once I booted back I still couldn't get WiFi working, and the crazy thing was that it would not even give me a home page, like there wasn't even a launcher installed. So I could get nowhere except for the settings. I decided to restore a nandroid I had, and will give this a try again later with a different build.
Sent from my BN NookHD+ using Tapatalk
Similar experience to mine. I was having trouble with WiFi turning on. It never did fully. It just said "scanning."
bpaulien said:
I installed it tonight. It behaved oddly. I first flashed the ROM and booted it up without gapps as is my habit. I tried to set up wifi and it gave me "authentication error" and never connected (to either of the 2 hot spots I have access to) I also didn't have any network access but didn't worry about it to much yet
I booted back into recovery and flashed gapps as well as a file of commonly used apps I keep so I don't have to download them every time. Anyway once I booted back I still couldn't get WiFi working, and the crazy thing was that it would not even give me a home page, like there wasn't even a launcher installed. So I could get nowhere except for the settings. I decided to restore a nandroid I had, and will give this a try again later with a different build.
Sent from my BN NookHD+ using Tapatalk
Click to expand...
Click to collapse
Boy, that's confusing. Mine worked great. I installed the same way that you did. Well, the only thing I can think of is that, since I'm not S-OFF, I first flash the .zip, and then I go into the bootloader and flash the kernel. Then, after I booted up, I went back to the recovery and flashed Slim Gapps and SU. That shouldn't have any difference in the end result though. Then again, it shouldn't be working for me and giving you problems.
I will say this the only lollipop rom which i have been able to send and recieve mms with no issues. Im s-off and i have zero issues right now. wifi works perfect i can even change apns from the celluar network settings. Great work on this one, i do have a request though, could you incorporate the butttons menu to change double tap and long press actions aswell as the long press back to kill current app?
ocarinaz64 said:
Boy, that's confusing. Mine worked great. I installed the same way that you did. Well, the only thing I can think of is that, since I'm not S-OFF, I first flash the .zip, and then I go into the bootloader and flash the kernel. Then, after I booted up, I went back to the recovery and flashed Slim Gapps and SU. That shouldn't have any difference in the end result though. Then again, it shouldn't be working for me and giving you problems.
Click to expand...
Click to collapse
Strange. Well, I may give it another try. I just realized, I didn't clear cache/dalvik after I flashed the zip of apps I installed... I wonder if that's what gave me issues?
bpaulien said:
I installed it tonight. It behaved oddly. I first flashed the ROM and booted it up without gapps as is my habit. I tried to set up wifi and it gave me "authentication error" and never connected (to either of the 2 hot spots I have access to) I also didn't have any network access but didn't worry about it to much yet
I booted back into recovery and flashed gapps as well as a file of commonly used apps I keep so I don't have to download them every time. Anyway once I booted back I still couldn't get WiFi working, and the crazy thing was that it would not even give me a home page, like there wasn't even a launcher installed. So I could get nowhere except for the settings. I decided to restore a nandroid I had, and will give this a try again later with a different build.
Sent from my BN NookHD+ using Tapatalk
Click to expand...
Click to collapse
I had the same issue with the launcher not working. Took me a while, but figured out you have to pick a launcher in the HOME settings.
Other than that, this rom hasn't given me any issues. So far everything I've tried works good.
I do agree with rontonomo though. A button menu would be nice.
Well, I have it another try last night. I didn't have the issue with the launcher this time. But I still can't use Swiftkey. Every time I try to change the keyboard it just shows a grey block where the keyboard should be.
I read in another thread that some visibility issues could be solved by setting the GPU rendering option in developer options. But that didn't seem to help with the keyboard issue. Unless I did it wrong.
Anyway, seems pretty stable to me so far.
bpaulien said:
Well, I have it another try last night. I didn't have the issue with the launcher this time. But I still can't use Swiftkey. Every time I try to change the keyboard it just shows a grey block where the keyboard should be.
I read in another thread that some visibility issues could be solved by setting the GPU rendering option in developer options. But that didn't seem to help with the keyboard issue. Unless I did it wrong.
Anyway, seems pretty stable to me so far.
Click to expand...
Click to collapse
You are correct. You need to enable developer options, and then force GPU rendering. That's what did it for me.
I posted a new build. Give it a shot. Word of warning: I feel like it took quite a while on the first boot. So give it a fair chance before you assume there is a bootloop issue or something.
ocarinaz64 said:
I posted a new build. Give it a shot. Word of warning: I feel like it took quite a while on the first boot. So give it a fair chance before you assume there is a bootloop issue or something.
Click to expand...
Click to collapse
I'll give it a try. Just a comment on the previous build, though. I wasn't able to get 3rd party keyboard working, even when I turned on the Force GPU rendering option. So I wonder if there's something else in addition to that, or I just have bad luck?
anyway, at least it works with the built in keyboard, so even if it's not my favorite, at least it's not keeping me from using it.
bpaulien said:
I'll give it a try. Just a comment on the previous build, though. I wasn't able to get 3rd party keyboard working, even when I turned on the Force GPU rendering option. So I wonder if there's something else in addition to that, or I just have bad luck?
anyway, at least it works with the built in keyboard, so even if it's not my favorite, at least it's not keeping me from using it.
Click to expand...
Click to collapse
I use Google keyboard. You might give that a shot if you don't want to use AOSP keyboard.
ocarinaz64 said:
I use Google keyboard. You might give that a shot if you don't want to use AOSP keyboard.
Click to expand...
Click to collapse
I may give it a try. I have used SwiftKey for a while and like it, but might be willing to give Google keyboard a try at least until this issue is resolved.
One question I had was is there any good third party apps that you know of and would recommend for capturing screen shots? I'm used to having that option on the quick settings pull down, but since that isn't configurable right now, I'm looking for an alternative.
EDIT: Never mind. I was just reminded that if you hit power and volume-down it will take a screen shot. Thanks.
rontonomo said:
I will say this the only lollipop rom which i have been able to send and recieve mms with no issues. Im s-off and i have zero issues right now. wifi works perfect i can even change apns from the celluar network settings. Great work on this one, i do have a request though, could you incorporate the butttons menu to change double tap and long press actions aswell as the long press back to kill current app?
Click to expand...
Click to collapse
I'm not very good with doing stuff like that unless I have pretty specific instructions on how to do it. If you are looking for a ROM with more features than Slim, you can try my new AICP build.
newest build 5.0.2 just bootloops over and over
rontonomo said:
newest build 5.0.2 just bootloops over and over
Click to expand...
Click to collapse
Thanks for the review. I hadn't actually tested it yet. I'll get right on it.
EDIT - I rebuilt it and I can say it takes a LONG time (over 3 minutes) to boot the first time. But it isn't caught in a bootloop. I posted the newest build for you to use just a minute ago.
Tried the previous build
Thank you for bringing Lolipop to Slim.
I tried your previous build and it looked stable. I had issues with blue tooth. It would pair with my speakers, head set but sound does not come through. It said "play back error" on the phone.
I have had my Z5C E5823 since January, and was pretty happy with it - It would occasionally crash (maybe once a month?) which I was fine with - I figure nothings perfect.
I recently got the update for 6.0.1 pushed to my device and downloaded/installed it without issue. I started noticing right away that it would crash on random apps multiple times a day. I can be writing a text, borwsing the store, and get an error similar to:
"Unfortunately messaging has stopped"
"System UI has stopped"
"Google Play Store has stopped"
etc.
It doesnt seem isolated to one app, or to any one function as far as I can tell, but it is pretty frustrating to have this problem 3-4 times a day.
My carrier is T-Mobile, and I dont have many apps installed. None of the apps have changed since I updated to the newest software.
Has anyone else had this issue and know of a fix? This is borderline unusable, and I am almost ready to void my warranty and root the device to fix it...
I suggest trying a factory restore first.
pelago said:
I suggest trying a factory restore first.
Click to expand...
Click to collapse
Did the factory reset, and its been ok for a few days, but I got the same messaging has stopped and System UI has stopped error and had to restart again yesterday.
I have been getting the SystemUI error many many times lately. I am rooted and using XPower with androplus kernel with xposed so I figure some there is messing me up.
Although, I distinctly remember sometimes being prompted to enter my pin when trying my fingerprint (a sign that systemui has restarted) long before I rooted so maybe something else is causing this issue.
eng3 said:
I have been getting the SystemUI error many many times lately. I am rooted and using XPower with androplus kernel with xposed so I figure some there is messing me up.
Although, I distinctly remember sometimes being prompted to enter my pin when trying my fingerprint (a sign that systemui has restarted) long before I rooted so maybe something else is causing this issue.
Click to expand...
Click to collapse
I am not rooted, but with all the issues I am considering it - although in my experience rooting leads to LESS stability, not more...
On the other hand, maybe there is some stock Sony app that is causing all my issues that I can't get rid of (What's New, etc.).
Its a bummer because I love so much about the phone - only cons are these system UI shutdowns and a slow camera shutter (not that big a deal for me).
Has anyone had any luck with a stable ROM? something to push me over the edge to rooting it?
Don't root, don't unlock your bootloader.
Download flashtool and the latest firmware release, clear everything (You will lose all your data) and reinstall fresh, see how the results are.
That should do the trick, if not you can consider BL unlock.
harry_turtle said:
Don't root, don't unlock your bootloader.
Download flashtool and the latest firmware release, clear everything (You will lose all your data) and reinstall fresh, see how the results are.
That should do the trick, if not you can consider BL unlock.
Click to expand...
Click to collapse
This is exactly what I did, and results are better, but still not stable...My phone still crashes once a day or so.
mangoose736 said:
This is exactly what I did, and results are better, but still not stable...My phone still crashes once a day or so.
Click to expand...
Click to collapse
Did you try another firmware version?
If you have the same results **** it and send it back for warranty, my z5c never crashes.
harry_turtle said:
Did you try another firmware version?
If you have the same results **** it and send it back for warranty, my z5c never crashes.
Click to expand...
Click to collapse
Yep I agree. It's not supposed to crash
Sent from my E5803 using XDA-Developers mobile app
Sadman Khan said:
Yep I agree. It's not supposed to crash
Sent from my E5803 using XDA-Developers mobile app
Click to expand...
Click to collapse
Quick update, I did a factory reset first, that didnt seem to help, but then did a factory reset immediately followed by a software repair, and the phone has worked well for about 2 weeks with no shutdowns - fingers crossed this good fortune continues.
FINALLY
Wouldn't this ota file work on all N950U1 devices?
22jk said:
Wouldn't this ota file work on all N950U1 devices?
Click to expand...
Click to collapse
I wouldn't know
:good:
22jk said:
Wouldn't this ota file work on all N950U1 devices?
Click to expand...
Click to collapse
gabesir said:
It should.
---------- Post added at 08:08 AM ---------- Previous post was at 08:08 AM ----------
gronimo21 - does the super slow mo option still in the camera?
Click to expand...
Click to collapse
The update is for carrier devices, not U1 devices. Your have to ODIN to N950U firmware then apply the OTA.
Mr. Orange 645 said:
The update is for carrier devices, not U1 devices. Your have to ODIN to N950U firmware then apply the OTA.
Click to expand...
Click to collapse
My device is a carrier device on stock nougat. It is a Verizon Note 8.
Hey guys, I just got the OTA update on my Sprint Galaxy Note 8 as well, and so far I'm loving it! But I'm experiencing a Google Play error, "DF-DFERH-01, error retrieving information from server"
So I went ahead and cleared cache and data, uninstalled Google Play updates, and did the same thing to Google Play Services. I went as far as factory resetting my device, and I'm still recieving the same error. It wasn't like this before I installed the update 2 hours ago.
I wanted to know if anyone else was experiencing the same thing?
Edit: Just like magic, Google Play seems to be working again. Finally to enjoy Android Pie at last!
SkyblueX said:
Hey guys, I just got the OTA update on my Sprint Galaxy Note 8 as well, and so far I'm loving it! But I'm experiencing a Google Play error, "DF-DFERH-01, error retrieving information from server"
So I went ahead and cleared cache and data, uninstalled Google Play updates, and did the same thing to Google Play Services. I went as far as factory resetting my device, and I'm still recieving the same error. It wasn't like this before I installed the update 2 hours ago.
I wanted to know if anyone else was experiencing the same thing?
Click to expand...
Click to collapse
^^ Also had / have same issue as well. Mine however is a carrier unlocked Galaxy Note 8 and using Sprint service (not rooted). I did clear cache, have not tried factory reset but thank you for informing me as I've been trying to determine the next course of action. Also, my menu / ui / settings / colors (font / backgrounds / forms) have partially inverted, so that all titles are almost close to #000 (solid black) with form boxes inverted to white, (making this close to impossible without some guess work what invisible text says) and it seems like there's an error with the themes (now back to complete stock and it does not change the colors at all from the inverted manner nor will it allow me to even switch to dark mode). However, I just got this installed maybe 15 minutes ago, so I will continue trying to figure this out and test to see if any other functions are not working properly. Have you found any other others yourself and or a way to fix the Google Play error?
SkyblueX said:
Hey guys, I just got the OTA update on my Sprint Galaxy Note 8 as well, and so far I'm loving it! But I'm experiencing a Google Play error, "DF-DFERH-01, error retrieving information from server"
So I went ahead and cleared cache and data, uninstalled Google Play updates, and did the same thing to Google Play Services. I went as far as factory resetting my device, and I'm still recieving the same error. It wasn't like this before I installed the update 2 hours ago.
I wanted to know if anyone else was experiencing the same thing?
Edit: Just like magic, Google Play seems to be working again. Finally to enjoy Android Pie at last!
Click to expand...
Click to collapse
Mine did too, I went to eat dinner, came back and it was fine ?
Not liking this update..... Like wtf did u do to the status bar icons and pulldown shortcuts...... My theme looks stupid AF now too. Hey Samsung, if your going to **** with **** like this, give us the option in settings to change it the **** back.
NothingIsPerfect said:
^^ Also had / have same issue as well. Mine however is a carrier unlocked Galaxy Note 8 and using Sprint service (not rooted). I did clear cache, have not tried factory reset but thank you for informing me as I've been trying to determine the next course of action. Also, my menu / ui / settings / colors (font / backgrounds / forms) have partially inverted, so that all titles are almost close to #000 (solid black) with form boxes inverted to white, (making this close to impossible without some guess work what invisible text says) and it seems like there's an error with the themes (now back to complete stock and it does not change the colors at all from the inverted manner nor will it allow me to even switch to dark mode). However, I just got this installed maybe 15 minutes ago, so I will continue trying to figure this out and test to see if any other functions are not working properly. Have you found any other others yourself and or a way to fix the Google Play error?
Click to expand...
Click to collapse
Ah, that sounds odd. As far as I know, Samsung made changes to the way themes work on the Android Pie update, so I'd guess it might be possible that your themes were screwed up in the process. Is it also like that on the default theme? Everything seems to be working normal on my end, I'm still using the default theme
As for the Google Play error, I didn't really do anything else after I had cleared cache and data, and uninstalled app updates. I went off to continue setting up my Note 8, came back 25 minutes later, and Google Play worked normally as if nothing had happened.
SkyblueX said:
Ah, that sounds odd. As far as I know, Samsung made changes to the way themes work on the Android Pie update, so I'd guess it might be possible that your themes were screwed up in the process. Is it also like that on the default theme? Everything seems to be working normal on my end, I'm still using the default theme
As for the Google Play error, I didn't really do anything else after I had cleared cache and data, and uninstalled app updates. I went off to continue setting up my Note 8, came back 25 minutes later, and Google Play worked normally as if nothing had happened.
Click to expand...
Click to collapse
So what I learned from a couple of quick experiments, to ANYONE downloading & installing Pie for the first time, I highly advise uninstalling all forms of themes, launchers, roms, etc. that are not stock as with the theme changes in Pie, that is what seems to mess it up and I am going to test to see what can be used with it after. The Google Play thing lasted me a few hours since it was earlier today.... but makes me wonder if they did a silent correction as I've heard others that didn't get that error after mine seemed to magically work again too.
22jk said:
My device is a carrier device on stock nougat. It is a Verizon Note 8.
Click to expand...
Click to collapse
I see. In your first post you asked about N950U1 devices, which is the unbranded factory unlocked model.
Yes this update will work on your device. But you can't apply it directly over your current build. You'll have to update to whatever the current Oreo build was first.
For context, I'm running lineage (19-20220824-NIGHTLY-dre) and this issue happens on every single camera app I've tried.
If I record a video let's say like a 2 second recording and then go to open that video the clip suddenly is an hour long with basically the entire hour being a single frame and the last 2 seconds being the 2 seconds I recorded. What's even weirder is the audio from the video plays during the first two seconds and then doesn't for the remaining time. Overall really weird and frustrating and I've spent hours trying to figure out what would cause this to no avail. Additional most gallery apps won't even open the videos recording and no pc can open them either. Any ideas?
Have you tried update Lineage? It's most recent update is 9/21 it looks like your about 4 updates behind. Not sure if it'll fix your issue though as I did not use camera while using Lineage and have since gone back to stock due to a display bug.
Edit: If you do want to update it SHOULD be fairly simple. You just go to settings>system>update and it should pull whatever the newest update it and install in the background. Note that even though it shouldn't cause any errors, there's always the chance it will so just be aware and ready.
Link575 said:
Have you tried update Lineage? It's most recent update is 9/21 it looks like your about 4 updates behind. Not sure if it'll fix your issue though as I did not use camera while using Lineage and have since gone back to stock due to a display bug.
Click to expand...
Click to collapse
Yup just updated to the most recent version, still same issue
Looeelooee said:
Yup just updated to the most recent version, still same issue
Click to expand...
Click to collapse
Ah ok, sorry that's all I got. You could always submit a bug report on the Lineage gitlabs and hopefully someone gets to it.
This is why I stick to US OEM Stock rom.
I can de-bloat it and EVERYTHING works.
scanman0 said:
This is why I stick to US OEM Stock rom.
I can de-bloat it and EVERYTHING works.
Click to expand...
Click to collapse
You got a debloat list or something you follow? I could go for that see if smooths stock a little when playing pokemon go.
I have the latest LIneage, with the same problem, and am completely lost with what it could be. Recording videos in Snapchat works normally, but the stock camera, GCAM, and the GrapheneOS camera all have this issue, probably because they all use the Camera2 API.
I encountered this problem today but the uploads on Google photos came out correct (when I 'free up space' )
I am having this issue as well, just checking to see if anybody might have discovered anything