Related
i changed to omnirom kitkat on my s3 a few weeks ago, and i just want to know if i should be downloading the latest versions?
thanks in advance, glenn.
gdaley1 said:
i changed to omnirom kitkat on my s3 a few weeks ago, and i just want to know if i should be downloading the latest versions?
thanks in advance, glenn.
Click to expand...
Click to collapse
It would be interesting to know other people's views on this too.
Well things usually get an update to be better ^^. So i'd say always. If you look around the forum you'll see there are still some (minor?) issues left which might or might not be important for you. If you stop updating you'll also miss out on potential new features and you can't contribute by filing bug reports ect.
Sent from my Find 5 using XDA Premium 4 mobile app
I usually go on omnirom's changelog to find any patches that pertain to me. Just the other week active display was not working. I updated immediately when next active display patch came out. I also update when there is a new feature I want.
Since even minor updates often have big impact (on battery life for example) I update on every nightly. But I keep a backup in case a weird bug entered the image.
I hope the build-in flash in my S2 is not the cheapest one since Samsung itself only updated once half a year or so - so I am (at least a little, little bit) worried that it someday will be worn out. Does anybody know if this is really an issue?
I update when I'm bored and happen to remember. Maybe twice or three a week. I usually check g+, device thread, or here for any update problems, though.
there's been a handful of times where I thought "ok I'm done fooling around with my phone... I'm pleased enough," but I'll update afterwards.
I've been updating on every nightly and then there was the data/wifi issue with the s3 i9305 and since then my phone just has not worked as it should at all safe to say the next nightly I find that seems to have no data/wifi issues I'll be sitting tight on. I know my friend has a system where he updates to the second newest nightly only, never the newest that way you're always up to date eventually but you get to see the feedback about the nightly first from everyone else having used it before you flash it, thus saving the issue of flashing a nightly that stuffs up pretty bad.
Also does anyone know when flashing a nightly it's OTA, if you want to go back to the previous nightly can you just flash it and it should work? Before I was having wifi/data issues I had the nightly on my SD card, then I flashed the new nightly, got data issues so I flashed the previous nightly that worked and still had the data/wifi issues...
In my opinion, you're rolling the dice with any upgrade. A nightly is just that, whatever was up that night. It might be better, it might be worse. Thankfully the OmniROM maintainers are generally pretty good about things and I haven't yet gotten a broken build. But it will happen. Invariably the night before you really, really need your phone to be working.
A cautious approach would be to maintain recent backups and only flash when you see something come up that you know you want. I like to flash on days when there hasn't been a change for a day or two -- let someone else find out that the "latest and greatest" isn't as great as they had hoped.
Yes, flash memory has a finite lifespan. If you look at the physical device layer, you'll see it. A good physical-to-logical block management layer ("wear leveling") keeps the cells reasonably evenly used and hides the failed cells from you. It might be in the device itself (microSD cards, for example), or in the driver/filesystem. You probably don't have to worry too much about flashing on a daily basis (as far as "wear" goes) as long as your device devs have made reasonable choices on how to put files onto the hardware of your device.
Being in the time zone that I am, the nightlies usually post when I am sleeping. Each morning, I check the change logs and newest comments. If there are a lot of early problem reports I pass on the build. If things look reasonably clear I download and flash.
Usually I update once or twice a week.
Now my device (SGS2) is with nightly 06/03/2014. This nightly working so well and is so battery friendly that I will keep it for a while longer.
And now the camera already has the option to choose where to save photos and videos (internal memory or external SD card).
Hi guys!
So I'm probably not as good with phones as you, but I learned to install a ROM, I've tried many of them but then returned to CyanogenMod ROM that was offered on their site. The performance is not that good, it lags often and battery life is too bad! The questions I want to ask you are:
1. Which ROM do you think is the most stable and would be a better alternative to Jelly Bean CyanogenMod?
2. What ROM are you using and why? Experiences etc.
Thank you!
Kind of in the same boat, just three meters further out. Have been putting off buying a new pho.... embiggened touch-pad device with phone capability and less battery life, that should in a reasonable world come with a carrying case with a shoulder-strap, and a stock portfolio for the handset maker... for a few years. But finally caved in, and bought something on sale with a really good screen, a replaceable battery, and a 3,5mm jack not made exclusively out of conductive rubber.
But. Now that I had a new phone pad, I wouldn't have to worry about bricking my old phone. All that much. So I went through a bunch of excruciating testing and failing yesterday to get something without ram-crippling bloatware and google applications that essentially force the 4x to run constantly at max speed.
What I seemed to be running into was two types of problems: a lot of the roms (custom firmware) were made by someone who was simply testing something new at the time, experimented a lot, and then left the project behind (or simply focused on other handsets). That's not necessarily a problem, but it can mean that you have stability issues you might not expect, and that has not been tested or reported while the project was active. And that might actually stop you from getting far enough to install some app that changes cpu-governor, ram-handling, and so on (even things like the standard keyboard/language variant.. kind of essential that that works). Install instructions also tend to link to outdated bootloaders, or have workaround suggestions that worked at the time, but now are obsoleted completely. The second problem was the OpenGapps - some of the core apps conflict with the builds' own apps.
And then there's the fact that the kernel in these roms tend to be from when the project was last maintained. I can't seem to decipher exactly what's going on, but I think a lot of the early roms were based on an old kernel with inserts (like the original one from LG). While the older builds on new kernel branches tend to have better support, but then have certain types of functionality simply gone completely. I don't know why that is, but the experience with this on linux laptops and android devices is what made me hold off until I had something that could replace the 4x before starting to try out some of the experiment builds people have.
So I went through getting the bootloader unlocked, trying a billion different methods before realizing they were all workarounds for the non-eu handsets - just use the oem-unlock method with fastboot. It's really as simple as it sounds. Use the "all in one" thing on the forum, set up the drivers, get root, and things like that - and then install a new, updated bootloader. I think after one of the official LG updates, everyone can actually use the oem-unlock.
Then I chose the wrong bootloader, apparently.. the cwm touch thing - superb bootloader. But apparently has some quirks that prevents it from installing certain firmware packages. I think it has something to do with consistency checking. I liked the idea of a multiboot, and didn't see why that wouldn't be extremely easy on android (with a storage size vs. cfw package being basically infinite to naught). But apparently what you want(need) is the twrp bootloader, and it has to be the last version. I don't know why that is, but you really don't want to be stuck - after basically wrecking your only boot - with an uninstallable image on your sdcard. So if you try something else than the "best one", just be prepared for an exit strategy with a backup and things like that before trying to install new images. There's also no way on these bootloaders to simply run a test first, nor is there a very easy way to partition the on-phone storage without having to start configuring install packages, so this is kind of awful if you're not actually deep into the development toolchains already.
I'd really love it if some of the tutorials said things like: our build really doesn't need a thorough wipe, and you can happily choose the file system you'd like, and the one that actually makes sense. For example. Or "for this cfw, you can just install gapps later on, that's going to work perfectly - don't force the install before you get through our own intro stage", etc. Alas.
Then I went through slimkat, an aosp lineage based rom, an old 4.1 rom, a new 5.1 rom, which all had different game-breaking problems. One refused to install gapps (note: you'll need the gapps that fit with the android version - but some packages simply won't install, period), another build had no sound other than on the speaker. One hanged randomly, another didn't scale the processor cores.
The good news is that this isn't really a problem - once you're set up you can just keep wiping and installing new ones. But it might be a really good idea to make a backup of your initial rom/custom firmware, just in case (i.e., you root, install the bootloader, and once you're in the bootloader, you make a backup of your current "rom" that is installed now. Then you can just revert to that without any problems later. I obviously didn't do that, because I was just fumbling around).
Some of the issues I ran into also might have workarounds, but I don't know - how would I, there's no way to actually tell what the problem is, or what it's related to. The most useful ones in the end seemed to be Vanir 6.0-based, and the one I ended up with, something called Euphoria on lollipop/5.1. That one seems to have all the hardware functions and benefitting a lot from a later kernel. I haven't done incredible amounts of testing on it yet, but it seems to work a lot better than the original firmware ever did.
And when you choose a gapps package, just go with the pico version. You can install everything you need after that from the store (and it takes less time than pre-installing the infinite amounts of crap in the stock package).
In sum - while you can get pretty far with the 4x on just rooting it and uninstalling some of the infinitely memory-hogging google crap, along with installing a new governor for the cpu and things like that. You can actually get something extremely neat by installing a new "rom"/cfw, that doesn't necessarily have the "oh, but you just have to forgo feature X, Y and Z because open source" problems.
I'm sure a cfw-developer is going to see this one day and roll their eyes back in their heads. And will have some very sharp words about the kind of effort that went into making a specific kernel, insert and build combination to even boot. But the later kernels seem to work really well.
And thanks to that Euphoria thing, I'm probably not going to use my new padphone-thing as much as I would. Because that one is over the "just testing stuff, getting it to work" stage. There's things with the home-button bar lighting up when there's notifications, things like that, that kind of show someone who used the handset was maintaining the build.
Anyway - I really recommend that you try out some different types to find these really good roms that works well. I'm sure there are lots of unknown cfw packages out there that work.. you know, for the 300 people who use it every day. That might be some of the early cfw variants with old kernels. And it might clearly also be some of the new ones, which I really didn't expect. Honestly, was kind of expecting stripes across the screen and hangs, but that didn't happen.
Optionally, a dev who actually knows what they're talking about could maybe suggest a list of cfw that have the later kernels that work, or the same kernels that Euphoria has Really, trying to search the net now, and find possible candidates was not easy.
My Razer Phone 2 has, I believe, a bad battery. It shuts down without any warning whatsoever, often with as much as 40-50% remaining battery power (according to the battery indicator in the status bar). When plugged in, it operates completely normally.
I opened a support case with Razer. They initially told me, based on my serial number, that my phone was under warranty (I didn't think it was, as I bought it more than a year prior). Now, they're telling me it's not, and want me to pay a $99 diagnostic fee, and if the battery is bad, there'll be an ADDITIONAL charge (I'm guesstimating at least $200) for parts and labor. Rather than pay all that (and, on top of everything else, they're EXTREMELY slow in responding to me, often taking more than a week!), I found someone selling an OEM Razer battery for a Phone 2 on eBay, that they describe as "open box" (whatever that means), for roughly $100. I found a Razer Phone 2 tear-down video on YouTube, which makes getting to the battery seem not too terribly difficult, so I bought the battery and will attempt to replace it myself.
Anyway, once I do that, I want to re-flash the software onto my phone, and start from scratch with it. I have this app on my phone called Font Changer Lite, which I use to change the font system-wide on my phone (it requires root). Lately, it's been informing me, if I attempt to open it, that it requires system write access, which it doesn't have, and so it immediately closes. It worked fine when I first got the phone and rooted it, and I'm not sure what happened. I'm thinking it might be a result of my phone having Android 9 on it, now. When I rooted it, it was running 8.1, and I don't remember how it got 9 on it (it won't take OTA updates, since it's rooted) - give me a break; I'm old here, LOL! ? I did install TWRP, so maybe it got on there that way (it's been a while, and I don't remember exactly what procedure I followed to install TWRP).
Anyway, can I flash 8.1 from Razer's factory images, without bricking the phone (considering it's running 9, now)? I had a Nexus 6 that I somehow temporarily bricked by flashing an older version of Android (I was able to eventually recover it), and I don't want to do the same to my Razer Phone 2! I'm thinking (hoping?) that my Font Changer Lite app will work OK running on 8.1.
Thanks.
Welp, apparently there's no downgrading from Android 9 to 8.1, on these phones. I was able to replace my battery (it really wasn't difficult, at all), and now the phone operates just fine, exactly like when it was new.
However, I tried to flash the newest 8.1 release, and the phone just wouldn't boot up - it was just stuck forever at the swirling energy screen. I then flashed the most recent Android 9 release from Razer's factory images page, and it booted right up! So, I'm on Android 9, now, rooted and with TWRP.
Of course, my Font Changer Lite app is again complaining it doesn't have write access to the system partition, and it the closes, rendering it useless (it's an old app the developer stopped supporting years ago). So, I deleted it, but I'm able to use Root Explorer to change the font system-wide, by simply renaming copies of my preferred font (FuturaHandwritten) to whatever font I want to replace in System/Fonts, and it seems to be working perfectly.
One question I do have is, my phone is now again alerting me there's a system update, but it won't take (I'm sure because I'm rooted, or have TWRP as a custom recovery). It's relatively small (it was either 80 or 800 MB in size - I don't remember which; far smaller than a full system update), and said it contained security updates through July, 2020.
Is there any way to take or apply this update, without flashing back to stock, and then having to re-root/flash TWRP, and then having to go through and completely set my phone up, again (there's a LOT of time-consuming customization I perform on my phone, like changing the fonts)? I really don't want to have to do that!
Thanks.
dmw_4814 said:
Welp, apparently there's no downgrading from Android 9 to 8.1, on these phones. I was able to replace my battery (it really wasn't difficult, at all), and now the phone operates just fine, exactly like when it was new.
However, I tried to flash the newest 8.1 release, and the phone just wouldn't boot up - it was just stuck forever at the swirling energy screen. I then flashed the most recent Android 9 release from Razer's factory images page, and it booted right up! So, I'm on Android 9, now, rooted and with TWRP.
Of course, my Font Changer Lite app is again complaining it doesn't have write access to the system partition, and it the closes, rendering it useless (it's an old app the developer stopped supporting years ago). So, I deleted it, but I'm able to use Root Explorer to change the font system-wide, by simply renaming copies of my preferred font (FuturaHandwritten) to whatever font I want to replace in System/Fonts, and it seems to be working perfectly.
One question I do have is, my phone is now again alerting me there's a system update, but it won't take (I'm sure because I'm rooted, or have TWRP as a custom recovery). It's relatively small (it was either 80 or 800 MB in size - I don't remember which; far smaller than a full system update), and said it contained security updates through July, 2020.
Is there any way to take or apply this update, without flashing back to stock, and then having to re-root/flash TWRP, and then having to go through and completely set my phone up, again (there's a LOT of time-consuming customization I perform on my phone, like changing the fonts)? I really don't want to have to do that!
Thanks.
Click to expand...
Click to collapse
so i have att unlocked razer phone 2 and have camera issue ( when you start camera app screen is black for about 40seconds and then camera starts but autofocus is not working, back camera functions normal) and most annoying sometimes while in call people cant hear me well. on roms site theres only 2 roms for att. 8.1 and 9 tried 8.1 and stuck on powered by android screen. then installed 9 and it worked but my issues still there...
what if I flash rom for global version? will it brick?
or maybe any other suggestions on how to fix this issues?
I have been running LineageOS+MicroG on my last 3 phones but am mostly a novice. LineageOS just packages things well enough that getting it installed is pretty easy. Most recently, I updated to 17.1 on my Payton device, and voila, I've got a problem where the phone reboots after powering on. Happens much faster with the radios on, much slower with safe mode and airplane mode on. So the obvious answer is usually "flash back to stock and try again". Here come my questions... Please keep in mind I also run Linux.
1. When people talk about going back to stock, doesn't this always entail losing your data? How do those of you who use your phone as a daily driver manage this? I've not heard great things about doing TWRP backups, and the amount of configuration I have to do at new-install time is crazy.
2. While running LineageOS or other such custom ROMs... How do you get "hardware updates": upgrades to things like modem/radio firmware that are outside the realm of the OS (if there is such a thing). I've had a few problems (including the current one) that I _suspect_ are related to running old "firmware" as I would normally call it. The solutions that I _think_ I've seen for this look like they are Windows-specific and also require going back to stock or losing your data. It's puzzling to me why updating hardware would require going back to stock, unless you need to let the stock OTA updates install in order to actually GET that firmware.
1) To my knowledge and at least for me, 'we' are using Android 9 firmware with Android 10 OS. I do not expect any further firmware updates.
2) I've been told that LOS is running slower on X4 compared to other ROMs such as Pixel Experience, but I can't speak for either as I use HAVOC. I can't speak for the rebooting issue though, I haven't looked at the X4 LOS thread much.
*3) LOS to my knowledge woln't work with MicroG because it doesn't allow for spoofing. HAVOC does, and personally I was using Android 9 w/ HAVOC and MicroG so I could use the GCam but due to personal reasons I had to install GPlay and so at the same time I also upgraded to Android 10. One point at least in my experience, the phone was getting more and more difficult to use over time but rebooting the phone fixed it completely. I almost never rebooted my phone back on 9 so it caught me off guard personally.
It sounds like you might be trying to go down a more privacy centered phone like I was until recently. Personally, I liked the Android 9 w/ HAVOC and MicroG. I can give you my list of apps I used but you probably know most of them (Simple Mobile Tools, OSMAND, K9, Fennec, NewPipe, VLC ect.) The launcher would get a little buggy (context menus would stop working after a while on app icons) and for some reason the audio would start for a split second, pause, for a sec, then continue. Other than that, it was great. I used that config setup for a year.
On a completely unrelated note, AT&T will most likely not work with the unlocked X4 after a couple of years, doesn't affect me but just a heads up.
today i've bought my new zenfone 8, i was leaving a xiaomi mi 10 because of proximity sensor problems and miui instability.
read lots of reviews about zenfone 8 and all were enthusiasts... today after buying it i found a first post about ramdump, since today afternoon i've read lots of posts....
i've seen my phone is 04/21 MFD....
will it die? are there people wich had this phone (04/21 batch) without problems? searching around in forums seems that anyone sooner or later had the problem... so the phone is in the box and i don't know if i will return it or keep it... give me a little trust in this phone
Do you like to play Russian Roulette?
If you open the box you will have to.
I have phone of same batch 04/2021 and had ramdump once. But I easilly quit it with keys combo. I do not know why it works for some but not for others.
so there are people who never had problems?
cause i could see 30 people having problems, but i'd like to know if are 30 people on 50 or 30 people on 1000, it would be a big difference
Mine is mfd 04/2021 and I still have no problems
There is 35 confirmed cases of this issue and it might not be the same issue as Ramdump is just something zenfone 8 falls back to when there is a problem with the phone. Who knows how many (tens of thousands) people are there without any issues.
I would say relax and enjoy your phone. Don't unlock the bootloader so you don't lose the warranty, but other than that just use it normally.
I just checked and I also have MFD 04.2021. I never had any problems (not that I am aware of) so I never bothered to check before. Does the problem only happen on certain devices? I have the basic version with 8 GB RAM and 128 GB ROM. Happy customer so far.
EDIT: I am running stock firmware, if that matters. Haven't altered anything (yet).
Used it for more than 4 months without problems (bootloader unlocked).
With Lineage 18.1, it worked great for a day, maybe even less. Now I get at least a couple ramdumps every day.
How do one check MFD?
[email protected] said:
How do one check MFD?
Click to expand...
Click to collapse
It is written on the box
Undead_Son said:
Used it for more than 4 months without problems (bootloader unlocked).
With Lineage 18.1, it worked great for a day, maybe even less. Now I get at least a couple ramdumps every day.
Click to expand...
Click to collapse
The problem in the official forum is a "one time" thing, if you get the "waiting for flashing full ramdump", its bricked and you can't do a thing, beside sending it in.
On my brand new ZenPhone 8 running Lineage for Microg 8.1 October 7th version I'm getting the ramdump screen, but only under specific circumstances:
1. not connected to wifi/wifi off
2. on a call
3. have headphones plugged in to the jack
it almost always crashes within 20 seconds. If any of those conditions are not met it works fine (or at least appears to so far). I've tested this ~8 times in a row with all other (known) variables remaining constant.
When it crashes, pressing power for ~15 seconds shuts it down, and it can then be started normally. I hope this helps anyone else e countering the same problem.
Someone had this ramdump issue on unlocked bl but on stock rom? Especially with at least some magisk mods?
MasterWoju said:
Someone had this ramdump issue on unlocked bl but on stock rom? Especially with at least some magisk mods?
Click to expand...
Click to collapse
Yes! My first time with this issue. Never before.
I'm on the lastest Android 12 stock rom (UL-ASUS_I006D-ASUS-31.1010.0410.72-1.1.25-2204-user).
- Unlocked BL
- Rooted with Magisk 23
- Kirisakura_Sake_S_2.0.1 flashed with EXKM
- Only one Magisk module (Font_Manager-v5_6_4-117)
I was playing a game (Zombie Tsunami ). I got my screen freezing, ... dark screen and ramdump issue.
Edit: My MFD is 05.2021
I have too MF 4.2021 - using since 5-2021. I'm very happy with this phone. For all this time I'v got only landscape bug on video - fixed with OTA update.
I'm using stock soft - Android 12 31.1010.0410.72