Database Users

Custom Kitkat ROM with empasis on battery life?

The only S5 Kitkat ROMs I've found either haven't been updated in over a year, or many users are reporting severe bugs like no camera support, or severe battery drain issues.
I'm just trying to get an app called Winulator running so I can play Starcraft: Broodwar on android, but it isn't working and one user said that is because Lolipop broke it (I'm on 5.1.1 atm). The app is no longer supported so I don't think it will ever run properly on 5.x. If anyone knows of a way to emulate 4.x for just 1 app maybe that would be the best shortcut for me overall here.
Barring that, could someone please recommend a guide to installing a lightweight, power-user-oriented ROM that is 4.x or older and has excellent battery life? I was going to try the official 4.4.4 VanirAOSP release but there are too many reports of poor battery performance in the last 2 pages of that thread for my liking.
I think the first thing I need to do is unlock the bootloader, and I've yet to find a definite answer on the best method of doing this from FOL1 (12/15). It seems I will need Odin on my PC and I have it. I've also started backing up all the data from my phone by manually copying/pasting to my PC.
I guess once everything is finally backed up (it's taking FOREVER, explorer literally been calculating time to copy for 10 minutes now just on the phone/android folder), then I will try and flash the official 4.4.2 VanirAOSP ROM since that one doesn't have any reports of battery issues and possibly only the camera and a few things won't work.
BTW, is there a step specially to unlock the FOL1 bootloader that I am missing, or can I just flash that ROM with Odin straight up? I found a comment stating NOT to flash 5.1.1 with Odin or I'd be stuck on Lollipop until some new bootloader-unlock method comes out. The 5.1.1 I'm running wasn't flashed with odin it was sent OTA and I've never rooted or had custom rom/bootloader, so I should be good on that I guess?
I am actually about to dive into this, if no one has any suggestions for me: http://forum.xda-developers.com/showthread.php?t=2752995

So I'll just pick one at random then? Thanks for the help...

You haven't even listed your model S5 or the ROM it's running now
And of course KK hasn't been updated in over a year, Lollipop and Marshmallow are released, they're not going to keep updating KK when a newer version of Android is released

10 GBs Space missing on MotoX Pure

Hello.
I have a moto x pure running android 6.0 bootloader unlocked and rooted with TWRP recovery.
I keep encountering a problem with my internal storage there are 10 GBs of space missing. I need to wipe my data and reset the phone every couple of months for this issue any idea what's causing it and if there is any soulution other than wipe the device. Attached are some screenshots of the issue with the device info

Same thing was happening to mine and I didn't have a solution. I recently installed a new rom and the data went away, however I never actually found a proper solution. I had 13 GBs taken up by 'system' for seemingly no reason on the stock rom. Sorry I couldn't be more help, just reporting that you are not alone.

Znomon said:
Same thing was happening to mine and I didn't have a solution. I recently installed a new rom and the data went away, however I never actually found a proper solution. I had 13 GBs taken up by 'system' for seemingly no reason on the stock rom. Sorry I couldn't be more help, just reporting that you are not alone.
Click to expand...
Click to collapse
In that case do you know of another custom ROM I could use the has the moto actions from the stock ROM

Mahmoud Jamal said:
In that case do you know of another custom ROM I could use the has the moto actions from the stock ROM
Click to expand...
Click to collapse
Unfortunately I can't suggest anything, I was using this phone from stock since I got it. I just now started to install roms on this device so I don't know all of the options yet. However some people state that LineageOS has the 'chop chop' to turn on the flashlight. However the 'wave your hand over the screen for it to turn on' feature is missing on my rom (crDroid) and I assume any rom that is not stock. I believe that most custom AOSP roms will not include most moto features. You should look for roms that are build off of stock, they will contain all the features of the stock rom as well as 'custom' features from AOSP roms.
Edit: After looking through the roms for this device, it looks like this is the go-to 'stock' custom rom TruPureX If you want all the moto features, but still want extra stuff, this looks like it would be the best bet.

I can't see any problem on the screenshots...
You have
7,94 gb Android OS
5,20 gb Apps
6,75 gb Images
0,95 gb Audio
1,67 gb Other
That summed up gives 22,51 gb off the internal memory
The device shows 22,90 gb used, the 390mb left is caused on cache/dalvik-cache/odex stuff i did not add there
Forget about what i told you, i was wrong on adding the Android OS :silly:

I've never had this problem, mine is working properly (or not, since it shows less than the total sum)

[Help] Back after long time, huge amount of confusion

Hello,
It's been almost a little over a year since I was last really into android customization. Since it's been so long it has become clear to me that my phone is outdated in many ways. I'm still running OxygenOS 2.2.1 with Android 5.1.1. I've been wanting to update up to Android N (7.x.x) for a long time now, but haven't seen any real stable roms or haven't really had the time to look for one. Now I've finally found my self with free time and ready upgrade my rom. I've just faced couple of problems, I can't really find what should I do when upgrading from 5.1.1 to 7.x.x since no-one is really doing that anymore. I remember reading sometime back that if you dont have the right firmwares you'll brick ur phone, and I wouldn't really want to go through that hassle at the moment. Is it still a thing or should it be just fine for me to flash a new rom just on top of this? (Ofc with clearing memory etc) Other question that is in my mind is that is there any critical bugs in Android N roms? It's bit unclear to me since there are such many roms that have their status as work in progress or beta etc, but some roms have status as stable. Are there any roms that I should clearly avoid? Im not new to this so I don't really need any deep info how to do everything etc, just a bit of a oversight on how things are going atm.
Thanks.

first of all is ur device rooted?? If yes then install the latest twrp recovery...then take a backup.. and flash any nougat rom which u like...If at all u would need Volte support then u l have to flash the 3.5.7 firmware..or else the 3.1.0 firmware works fine with most of the nougat roms..some nougat roms i would recommend are AICP, Resurrection Remix and AOSP extended .... In my suggestion u should probably first upgrade the Oxygen Os on ur device through official updates via OTA atleast upto the 3.5.6 firmware

there's no need to update until 3.5.6, unless you aren't going to plan staying with OOS [the only "stable" firmware which provides you VoLTE working, but it's still M-based and not N].
as @mhd athiq said, unlock your bootloader [just in case you still haven't done it before] then update your TWRP recovery to the latest version.
then flash the incrementals OTAs until OOS 3.1.x and you are good to go to flash any custom ROM which is N-based.
to avoid any mistake, please make a EFS backup via terminal [just to have a backup of your modems] and save the files to a safe location.
I don't have a specific ROM to suggest to you, but in my experience I have found the CAF/AOSP-based ones to be the ones with the best battery backup and less bugs then LOS-based ones.
I have used happily for a few months CypherOS version 3.5.1 [not the latest one, I find it quite unstable as the developers tried to implement OMS].
sidenote:
flashing N-based custom ROMs upon OOS 3.5.6 firmwares gives random reboots and unstable network in many cases/scenarios.
so don't update to that OOS version unless you have a mandatory VoLTE feature required [but you'll have to live with random reboots and poor network stability].

Moving to LineageOS worth it (and possible) from Cloudy G2.2?

I've been running Cloudy G2.2 for a year an a half. It's given the phone enough legs to mostly make it through 2017. However, about every other week I have to restore my latest backup when Bluetooth stops working because it saw too many devices. This wouldn't be terrible if it wasn't for Authy refusing to sync my newer 2-Factor auth accounts. I think I've convinced myself that the G6 (US997) is my next phone, but now is a silly time to buy as the price should drop like a rock as the next wave of flagships come out.
I'm hoping to make it another couple months and was wondering anyone's experiences moving from Cloudy G2.2 (or other ROMs) to the latest lineage? From what I've read, it's very stable. However, I'm on Kit Kat bootloader, so it doesn't seem like this will be a straightforward process. I was hoping to get some experiences from people who made the same move before starting.
I currently have:
LG G2 D800
Root using stumproot (I think, it's been a while) with supersu installed
TWRP 2.7.0.0 installed by autorec
Cloudy G2.2 KOT49I

So, after some research, I set off to install LineageOS. In hindsight, this might have been a bad idea since it specifically only mentions the D802 in the title. However, it listed links for D800 builds, though they were crossed out.
I updated TWRP to this version by Blastagator and that was painless. I then wiped the phone, made a fresh backup and flashed the latest nightly of LineageOS, and the latest GApps (Mini) for 7.1. That was disappointing since I got the quick "LG logo" followed by a blank screen, that I later found was mentioned in the same Lineage post. Should've read farther.
I think the issue is that I'm on the wrong bootloader. I thought I was on KitKat which the post requires, but in order to enter recovery, I have to press enter three times (rather than using volume buttons to navigate), which indicates I'm on JellyBean bootloader.
So, this is the scary step that I was hoping to avoid. My big fear is that I run Linux on my desktop, so I can't use the LG Flash Tool. As long as I can keep a working recovery, I have backups, so I'm fairly safe. Following the Blastagator bootloader post, I'm not really sure how you go back and forth between bootloaders so easily as it suggests. Is that really as simple as loading the zip file on the phone and installing it in TWRP?
Is there a safer way to handle this?

From my experience, it is that easy. Simply install the zip file and you have loaded a new boot loader. Also, I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid. However it's not stable and I am considering looking for something else more stable but fast like crDroid.

ernie young said:
I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid
Click to expand...
Click to collapse
When you updated your bootloader, were you still able to run the Cloudy ROM before you switched to crDroid? Once I flash the KitKat bootloader, am I only able to use the Nougat ROMs? My big concern is that there might be something a bit off with my bootloader, so I won't be able to get back to TWRP.
I think there's something a bit off with my bootloader as is, because about a year ago I flashed back to stock Jellybean, and took all the OTA updates. However, when the phone tried to take the KitKat update, it softbricked, and could only be recovered using the LG Update Tool, which I don't have access to anymore. Because of this, I'm a little worried that just dropping on the Blastagator KitKat bootloader may have some atypical issues.

i m using it for a while. u know, on Los you won't be able to use lg features such as qslide, qmemo, plug&pop, knockcode etc. Only worth it if you want your phone to look a little bit fresher and lighter or you need a newer android version for some reason. Else, don't take the risk if you can't use flashtool. You can consider installing another kitkat rom. There are lots and they are nice :]

S YILDIRIM said:
or you need a newer android version for some reason.
Click to expand...
Click to collapse
My primary issue is that KitKat (or whatever Cloudy G2.2 is?) has the old Android bluetooth bug where once it sees too many devices, it stops connecting to anything. I have to make sure to turn off my phone if I go somewhere like an airport, and have been having to restore my clean Cloudy backup about once a month. It's getting pretty frustrating. On the other hand, I'm hoping to upgrade to an LG G6 (US997) in a month or two when the V30 release pushes down on prices. So, if it's a case of potentially hard-bricking my G2 at the worst possible time, I should hold off flashing.

I think you need hybrid bootstack for android 7.

WORF84 said:
I think you need hybrid bootstack for android 7.
Click to expand...
Click to collapse
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.

superlou23 said:
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
Click to expand...
Click to collapse
These questions if this works with that or that are easier to answer for yourself by reading what goes with what.
Just Google LG G2 bootstack and you can probably find the ones you need for any available rom.
I use hybrid on Marshmallow 6.0.1 but I tried Nougat 7.1.2 too, it works.

Want to find a fix to all custom ROM's bootlooping on my SM-J320FN (did not bootloop before)

Want to find a fix to all custom ROM's bootlooping on my SM-J320FN (did not bootloop before)
[
or alternatevly, i was wondering if modifying a some samsung galaxy SM-J320[something] nougat rom, to work on SM-J320FN would be possible (it has only android5.1.1 (lollipop) stock rom as far as im aware and i have searched quite a lot).
]
The thing is, i have the SM-J320FN (twrp and rooted) and for a while i ran various custom roms (based on nougat) on it with no problems. But then about a year ago it bootlooped on resurrection remix (which i had ran with not many problems for 1/2year). Then every custom rom (i tried RR, DotOS, ViperOS and more) began to give me a bootloop, only flashing the stock rom booted.
I wiped and formated everything i could, tried same country stock rom that i had originally and a different country one (thinking maybe the custom roms were not happy with something inside the stock rom that it was flashed after, but logically it does not seem even possible, as before flashing the custom one, the old one is wiped), but custom rom's just did not boot anymore. I could not log the boot either because it had boot animation but nothing showed in adb, i guess it did not get so far that it could connect with adb.
I suspect this may be caused by my camera not working (some hardware part most likely got damaged), because i think wiping my phone completely and flashing stock rom with Odin should restore every software part on the phone thus it would have to be something with hardware that's causing custom roms to bootloop, how else could the problem persist (i obviously might be wrong).
I don't remember when exactly the camera stopped working but i know for a fact that i had a custom rom at the same time, and it did not bootloop (for some time at least) and im also curious why this has not ever stopped the stock rom from booting if it is the case.
So basically what i wish i could do are two things. Firstly find what makes the stock roms able to boot correctly opposed to the custom ones. And secondly implement this to a similar models higher version rom or a custom rom (Nougat). Come to think of this, it seems a useful step to look how did the people that made these Nougat based rom's for SM-J320FN modify the rom so that it could run on it, the source code is open after all.
Why i want to have a higher android version on my phone? Because my countrys corona close contact detection app supports only 6.0 or higher and my banking app recently notified me that they will soon end support for my android version too (this is the real pusher for me as i use it very frequently and there is not really an alternative). And it would be nice to have some other apps too, that not compatible with Lollipop.
And yes, i know, just buying a newer phone would solve all my problems But im a minimalistic (and without money) person. The fact that i own a phone that is still working (or fixable) stops me mentally from buying a new one. Also as one would guess, i like tinkering with this kind of stuff (i study CS currently) and building a rom myself for my phone sounds like a cool and challenging project, as i have not done anything like this before (maybe this will help me: [guide]how to build/modify roms for samsung devices [7.0/6.0.1/maybe more]).
Anyways, i kinda got carried away with this post. But for now im tired and have to sleep so i'll just post this and will come back later to read this over, fix some mistakes (not a native english speaker) and add things i maybe missed.
If anyone read this through, im impressed and if you have the knowledge/time to answer then i Thank You in advance!

i need help i tried to install re dreaux but my phone bootloop on touch wiz custom rom so how can i fix that