Related
Hullo
I'm looking at grabbing one of these. Seems like a great update to my HTC One M7, especially the camera.
I do, however, like replacing the firmware with something AOSP based, often CM.
I was wondering how serious the impact removing the LG firmware would have on the camera? The impact was noticeable with the HTC One so was curious if it would be the same with this.
Thanks
I've tried using other camera apps but always go back to the LG app. It really is nice.
Perhaps I've misunderstood replacing the firmware, but my understanding was that replacing the firmware also removed whatever camera specific drivers were installed as part of LG's firmware. As AOSP roms are not device specific, they don't have these same drivers to get the most out of the camera. So the camera quality would likely decrease, however this seems to differ between devices.
So I'm curious as to how much the camera is affected, if it's known at this stage.
Orb.P said:
Perhaps I've misunderstood replacing the firmware, but my understanding was that replacing the firmware also removed whatever camera specific drivers were installed as part of LG's firmware. As AOSP roms are not device specific, they don't have these same drivers to get the most out of the camera. So the camera quality would likely decrease, however this seems to differ between devices.
So I'm curious as to how much the camera is affected, if it's known at this stage.
Click to expand...
Click to collapse
Well... no matter what build you have, you still need those hardware specific drivers. That's why devs can't do anything until the sources for the device are released. Those sources are merged with the main AOSP code, compiled, and you get your rom.
What you might lose is carrier stuff...like T-Mobile's Wi-Fi calling.
Luckily, LG has released both the kernel and system sources, so devs can start working. The only problem is that the only version that has an unlocked bootloader is the D851 T-Mobile version.
We'll just have to wait and see now. There aren't any custom roms out yet, just modified stock G3.
The laser focus only works on the LG Camera. So there's that.
LeoRex said:
Well... no matter what build you have, you still need those hardware specific drivers. That's why devs can't do anything until the sources for the device are released. Those sources are merged with the main AOSP code, compiled, and you get your rom.
What you might lose is carrier stuff...like T-Mobile's Wi-Fi calling.
Luckily, LG has released both the kernel and system sources, so devs can start working. The only problem is that the only version that has an unlocked bootloader is the D851 T-Mobile version.
We'll just have to wait and see now. There aren't any custom roms out yet, just modified stock G3.
Click to expand...
Click to collapse
So when I replaced Sense with CM on my HTC One M7 was I imaging the decline in photo quality? Genuinely curious if it's just my imagination or if it's a genuine thing.
ChummyDays said:
I had the same feeling on my HTC One X, but someone made a thread showing pictures taken with the aosp camera vs sense camera, and I was impressed (there might have been one on the m7 forums as well).
I think HTC did some trickery to the camera that made it seem better, but realistically, they probably take the same pictures, but you can see for yourself: http://forum.xda-developers.com/showthread.php?t=1943160
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
That's quite interesting actually. Thanks for the info.
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.
cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
Hate to be the bearer of bad news...
Ports assume the two devices (the base device, and the one to port to) are very similar (same chipset, et cetera). A good example (I used to use HTC) is the Sensation was a very good base for the MyTouch 4G Slide (they even shared the same battery design/size).
Unfortunately the Zenfone 2 and either of the new Nexus devices are worlds apart from each other. They don't share the same architecture, let alone chipset. We would be better off piggybacking off the work of the ASUS Fonepad 7 FE375CG (Z3560 Chipset) or the Asus Memo Pad 8 ME581CL (Z3580) - but in reality, in terms of updates - it's more likely we would be the base for those devices in a few months time.
Sorry.
---------- Post added at 20:36 ---------- Previous post was at 20:33 ----------
AkiroX said:
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.
Click to expand...
Click to collapse
That's right, all we can do is wait, then build from source once available.
Porting has it's place, but it can be a gong-show.
Source already available
We should wait for devs to build it ?
AL_IRAQI said:
Source already available
We should wait for devs to build it ?
Click to expand...
Click to collapse
AOSP is available, but now we have to wait to have CM13 in a manageable state. I don't imagine cpalmer and jrior001 will put on the brakes with CM12.1 to build straight from AOSP.
ROMe wasn't built in a day, and it will be months before CyanogenMod will be able to have the AOSP source modified for the new CM13 and reach the coveted milestone one.
Yap, waiting for you too @joel.maxuel for working on it
allasca said:
Yap, waiting for you too @joel.maxuel for working on it
Click to expand...
Click to collapse
Why am I being thrown under the bus? :silly:
In all seriousness, if CarbonROM continues to base their stuff off of CM (which I heard talk of that changing), this time around they may be once again months behind CM in terms of an official product (e.g, none of their devices have hit official status yet this round, or at least as of last night).
Not to speak ill of course, which is why I am curious of the route that does not involve basing off of CyanogenMod.
No guarantees with my involvement to 6.0, but I am interested in the job. I just can't predict what my life demands are going to be like in the spring (time seems tight right now, but I manage).
My short and medium term plans is to keep the 5.1 builds going, hopefully even after Carbon calls it quits for this branch to focus on the new one. The only possible things stopping me are:
Carbon leaves lp5.1.1 branch perfect, meaning I don't even have to do monthlies anymore (also means no future security issues)
CyanogenMod breaks their sources badly (has happened recently when Carbon couldn't keep up)
I get the official stock 6.0 image which ends up breaking modem usage - leaving me unable to properly downgrade to 5.1 to test
It feels like with this plan, someone is going to beat me to the punch by building a CarbonROM mm-6.0 ahead of me. Which is why at some point, I will (probably) be doing builds in parallel. But we shall see when we get there.
Just read this: http://arstechnica.com/gadgets/2015/10/android-6-0-marshmallow-thoroughly-reviewed/
Doesn't seem much for us CM12.1 users to get very excited about anyway. Material design not changed from Lollipop, Google Now launcher already updated with the changes, selectable app permissions already included in CM12.1 via Privacy Guard, fingerprint api and 4K display stuff irrelevant to our zenfones...
Personally, I think a stable CM12.1 (5.1.1) build is more important. In fact, the unofficial build we already have is stable and very nearly there, but I would rather see the last few kinks ironed out and official status before any time is put into 6.0
Most importantly, it should support 64bit for the z00a. Any news on this?
Sent from my iPhone using Tapatalk
The next month, asus update android 5.1 for zenfine 2, maybe 6.0 ? I don't know this,
So I finally broke my Galaxy S4 last night, and I'm thinking about buying an LG G4 to replace it. However, the LG UI "improvements" look awful, and I bet I would be changing the firmware pretty soon if I get it. So with that in mind, I'm wondering if I should be buying the phone. Is CM13 or other roms stable enough that replacing the stock rom a good idea on a new phone?
I'm also considering any any other phone in the same price range, including the Moto X Style (Pure).
Unless you're looking to get the T-Mobile (811) or the International EU (815) version, there is no way to install custom roms. Those are the only two unlockable variants.
The other versions are rootable if you stay on 5.1.1 LP, but if you want 6.0 MM, you'll be stuck with the T-Mobile or EU Int version. There is no way to root all the other variants on 6.0
Luckily, I would be getting the 815 version.
As far as I can tell the ROMs based on stock are very stable. You won't even notice the difference. CM and CM based ROMs are the usual. Stable but have a few annoying bugs. I haven't really tried any AOSP so I won't speak for those
Heres my opinion.i have a tmobile version and if i flasha custom rom it seems to drop the bands as i cannot get signal in places where i can on stock based custom roms or pure stock rom.it does not switch between towers properly and i lose the ability to make or recieve calls.when i check phone info on aosp or cm based roms it shows it uses only 4 of the 12 bands i have.
Overlord Yuri said:
So I finally broke my Galaxy S4 last night, and I'm thinking about buying an LG G4 to replace it. However, the LG UI "improvements" look awful, and I bet I would be changing the firmware pretty soon if I get it. So with that in mind, I'm wondering if I should be buying the phone. Is CM13 or other roms stable enough that replacing the stock rom a good idea on a new phone?
I'm also considering any any other phone in the same price range, including the Moto X Style (Pure).
Click to expand...
Click to collapse
I made the same transition; from Galaxy S4 to Lg G4.
I'm running stock with Xposed. The G4 Tweaksbox app has a themes option and I've got a stock android one applied. It's really stable (I always expect themes to go crazy). The only other thing is the settings. You can get a stock settings mod but I don't really see the point. It works well enough for me and settings isn't really something you'd aim to be going on everyday anyway.
The clip tray is annoying but can be disabled. Add nova launcher and Google keyboard and it's all good. This is a much better solution than a custom ROM. You'll never get this kind of stability. Not forgetting that your camera app and fm radio and others will also be gone.
EDIT:
When buying, make sure the serial number starts with 601 or 602 603... These phones were manufactured this year so hopefully won't have the bootloop bug. If buying 2nd hand, ask the seller for the serial. If they can't provide it, ask for the IMEI and look up the serial number using https://imeidata.net/warranty/lg
There are too many references for 6XX bootloop issues, so I wouldn't recommend LG G4 at all , for custom theming,roms etc. Even after replacing motherboards of 5xx to 6xx, the bootloops are something more common than I used to believe...
personally am very happy with g4(601). best combo for me is Genisys Rom 4.2 + SimpleGX KERNEL (then Tweaksbox, xposed & nova launcher). very stable, no lags, speedy, good battery, amazing camera/lg app. downsides are unlocking bootloader voids warranty & the body corner feels painfully sharp after a while in the hand.
I am happy with the G4 too, 601 as well , but unfortunately that doesn't change the fact that there are many issues with the phone! I hope the OP can enjoy and proceed at his own risk of course!
Thanks for the replies guys! At the moment I think I'm leaning towards the Moto X Style, and will probably order it (at pretty much the same price as the G4) tomorrow unless someone talks me out of it.
Overlord Yuri said:
Thanks for the replies guys! At the moment I think I'm leaning towards the Moto X Style, and will probably order it (at pretty much the same price as the G4) tomorrow unless someone talks me out of it.
Click to expand...
Click to collapse
I'll be honest with you.....my mom has this phone and has massive battery drain issues, where as I have none. If your going for good battery and fast updates than Motorola will be your best bud, but if you don't mind mediocre battery but a kick ass camera then the G4 will be your best bud. PS it's as good as point and shoot this is coming from someone that does photography for a living.
Sent from my LG-H812 using XDA Free mobile app
I also have little to no faith in LG anymore. Moving on to bigger better things but will ride it out until my upgrade is eligible.
Going back to Samsung, Motorola, Huawei or HTC.
Sent from my VS986 using Tapatalk
Going to repeat this over and over again, i don't understand those people who after unboxing immediately install custom ROM (What!? you know what you're buying, you support OEM in this case LG, you support their firmware, skin and now you throwing out your money for something else in many cases worse, facepalm) if you want pure Android you buy Nexus, Motorola maybe, that's it, as Google says "Be together not the same". Installing custom ROM's it's like putting BMW rims on Toyota's car... beside that, G4 don't need a custom ROM, just imagine what your going to deal with custom ROM, awful camera, sound issue, lost functionalities, bugs, strange battery drains, degradation in overall battery life and everything for stock Android look? for latest security patches? themes? it's not worth it atleast now, IMO custom ROM's comes in handy when OEM stop's supporting your device with the latest firmware so if i done calculations right you should look for CM for LG G4 when Android 8-9 comes out. All you need is a root and good kernel then comes a good stuff, long story short, CM is a cancer for latest devices, flagships, believe me and don't think i'm condemning CM.
Frant1c said:
Going to repeat this over and over again, i don't understand those people who after unboxing immediately install custom ROM (What!? you know what you're buying, you support OEM in this case LG, you support their firmware, skin and now you throwing out your money for something else in many cases worse, facepalm) if you want pure Android you buy Nexus, Motorola maybe, that's it, as Google says "Be together not the same". Installing custom ROM's it's like putting BMW rims on Toyota's car... beside that, G4 don't need a custom ROM, just imagine what your going to deal with custom ROM, awful camera, sound issue, lost functionalities, bugs, strange battery drains, degradation in overall battery life and everything for stock Android look? for latest security patches? themes? it's not worth it atleast now, IMO custom ROM's comes in handy when OEM stop's supporting your device with the latest firmware so if i done calculations right you should look for CM for LG G4 when Android 8-9 comes out. All you need is a root and good kernel then comes a good stuff, long story short, CM is a cancer for latest devices, flagships, believe me and don't think i'm condemning CM.
Click to expand...
Click to collapse
+1
I used to be one of those who buys a flagship device, then immediately look for bootloader unlock, root and flash. But after having LG G4 for 3 weeks now, stock MM latest, installed with my needed apps and games, I lost the feel of flashing custom ROMs.
G4 is great as it is, although optimizations can be done, a little upgrade here and there. As long as LG supports G4 with updates and with their accessories, then I'll stay with LG as manufacturer. Of they abandon us (like what they did with G PRO), then I'll switch devices.
LG has been my favorite since 2013.
Overlord Yuri said:
Luckily, I would be getting the 815 version.
Click to expand...
Click to collapse
Be extremely cautious where you get your 815 from. I bought one from Value basket that was advertised as a European Variant for the express purpose of developing a CFW- When it came it wasn't and they refused to exchange it. I've got an email trail as long as your arm trying to get the thing exchanged but they're just con-merchants.
But it's still an awesome phone....
Frant1c said:
if you want pure Android you buy Nexus, Motorola maybe, that's it, as Google says "Be together not the same". Installing custom ROM's it's like putting BMW rims on Toyota's car... beside that, G4 don't need a custom ROM, just imagine what your going to deal with custom ROM, awful camera, sound issue, lost functionalities, bugs, strange battery drains, degradation in overall battery life and everything for stock Android look?
Click to expand...
Click to collapse
I do get your point. Buying the G4 would have been a compromise to get some good hardware for a low price, and I hoped to to sweeten that deal even more by customizing the firmware to my liking. However, I ended up getting a second-hand Nexus 6P instead. :victory:
Overlord Yuri said:
I do get your point. Buying the G4 would have been a compromise to get some good hardware for a low price, and I hoped to to sweeten that deal even more by customizing the firmware to my liking. However, I ended up getting a second-hand Nexus 6P instead. :victory:
Click to expand...
Click to collapse
Smartest move you could have ever made. LG has left me with a bitter taste in my mouth. Ever since I got my phone back with a new circuit board it feels like a ticking time bomb and I don't use it for anything other than texting, phone use and browsing. How pathetic is that.
Sent from my VS986 using Tapatalk
Hi.
I'm using EU MIUI 7.3.30 and it's not bad, but I would much prefer using a non-MIUI ROM such a LineageOS.
However, all the AOSP variants using the stock kernel (LOS,RR...) until now have had mediocre to faulty camera implementations and I've tested many camera apps at that - Piximod mark IV, stock LOS, stock RR, Google camera, a better camera, open camera, manual camera... None of them are able to hold a candle to the stock camera app under MIUI in terms of having everything (video,RAW,HDR,panorama...) working flawlessly under one app.
I'm not even sure if this will change now that we have the released kernel for the mi5s, so please help me understand the following:
1. Does having the released kernel potentially help in getting a better camera experience under LOS, RR or a similar ROM versus using the stock kernel from MIUI? How so?
2. Does having the released kernel potentially help in porting the stock MIUI camera app under LOS/RR?
3. Does having the released kernel potentially help in getting a *better* camera implementation than currently under stock camera app MIUI by better utilizing the camera2API (from my understanding the stock camera app in MIUI doesn't use V2 of the camera API)?
4. Does having the released kernel potentially allow one to port the Pixel camera app?
Thanks all
I think you should create this thread into the Question & Answer Section.
But for your question regarding the kernels and implementation for los / rr, yes indeed it'll help for dev to use new released kernel from xiaomi, since the kernel is made specifically for mi5s hardware optimization and function.
Yes and yes, the bottom line is the kernel will give us huge advantage rather than use stock kernel like we use right now if we use los / rr, for the camera of course there will be some improvements, not only the camera, fingerprint, ambient display, multi touch, etc will improve.
As far as I understand the source doesnt contain every information.
Open source sounds cool yeah. But take Amazons FireTV as an example. There is a source code available because of GPL, however they only share the source of the stuff they have to share and nothing else. So source doesnt mean, the source code of everything.
As a better example you can take the Google Pixel. You would expect that the VERY Android device itself should have source code of everything available. Like the Google Camera Software and algorithm that could be used for the Mi5S since both share the same Sony Sensor. Sounds awesome right? Sadly Google, doesn't share this particular piece of source code/drivers.
And when I talked with LuK about source, he was not very optimistic. It is because the Qualcomm Fingerprint reader is also closed. Which is why he said "Qfp will still be a mess"
So.. Long story short. It will still be a custom rom with its disadvantages. But I believe that it will contribute a lot in terms of stability. Phone calling , no force closes and sudden reboots.
I mean after all these years on xda , everyone should already got used to "everything works. Stable build. not working : camera etc"
This will not change I think. In fact it will get more complicated and the list of troublesome things will get longer as phones get more and more features with closed source. Fingerprint reader is such a thing for instance. and More advanced sensors in the future etc..
So there are two options:
1) Either you stick with your current phone and try to make it work and live with its downsides. Maybe after 3 to 5 years, almost everything will be supported or maybe not. Although by then the phone will most likely be obsolete and any 100$ phone will beat it.
Go back 5 years. Would you still bother with a Samsung Galaxy S2 or S3?
2) Just get a phone that has proper company support from the start and use the phone at its full potential right away. Like the Google Pixel. However it costs more. So you have to weigh the Pros and Cons. Do you want to spend more money or more time and headaches. Everyone has to make a decision there.
As for me: I know that I drop and break expensive stuff. So I buy cheap phones. xD
All the other XIaomi phones from last year , including the ones with the same ram , storage and processors as ours have roms.
Is it that we just dont have the developers?
The mi max3 is soo similar to the other phones and even its predecessor.
I am baffled as to why we have to struggle with unreliable treble roms.
Just venting, but im sure 90% feel the same.
Almost all the GSI roms are stuck on Oreo and installing them is an iffy process
im trying to follow the guides, but i cant even get one of the trebble roms to success fully boot. ive got the 6gb/128gb variant. pffffff. ill have to sell it and try to upgrade to a mi mix3 in time
caniranges said:
All the other xisomi phonrd from last year , including the ones with the same ram , storage and processors as ours have roms.
Is it that we just dont have the developers?
The mi max3 is soo similar to the other phones and even its predecessor. I am baffled as to why we have to struggle with unreliable treble roms.
Just venting, but im sure 90% feel the same.
Almost all the GSI roms are stuck on Oreo and installing them is an iffy process
Click to expand...
Click to collapse
Maybe because access to other devices has been easier. I know that some manufacturers even offer some devices for this purpose, which should not be the case of the Mi Max 3. In particular, I bought this device by the screen and battery, and I am accustomed to little development, because my previous device was a Huawei (that I use until today), which I was able to install a version of the lineage, where the camera did not work. It may also be that mm3 is not as attractive as the others for development. The way to learn is to develop or hope to help.
I'm also a little bit disappointed by the lack of custom roms for the MiMax3, but i bought it for looking prime and netflix when i'm abroad. So the big screen and the battery is enought for me. And for flashing i have my Poco :laugh:
First: Stuck on Oreo?
You don't know what you are talking about.
Most decent ROMs have a proper Pie vendor build by now.
Unstable and buggy?:
Stick to the stable ones (AOSP, PE, AOSiP, Descendant, etc) and always run on a patched Pie vendor.
Use my latest fix bundle and you'll have no bugs.
You'll even have VoLTE no working.
I had the Mi Max 1, then the 2, which the day I first used it, I crashed the screen. The Mi max 3 had just been launched, so I bought it.
After two months of not getting any ROMs I decided to buy another Mi Max 2, which I totally love. Development is really good.
I keep my Mi Max 3 until development gets better and we can have more options, cause hardware is obviously better than the 2.
I will never buy a newly released phone or one that gets little development.
The thing I don't understand is: Why is everyone so obsessed with device specific ROMs?
You can install GSIs right now... Install my Max 3 fix patch on top and you'll have a flawless experience, no different to any other ROM you'll find out there.
That's (kind of) the whole point of treble to begin with!
Be able to build ROMs without the whole device specific crap...
MrColdbird said:
The thing I don't understand is: Why is everyone so obsessed with device specific ROMs?
You can install GSIs right now... Install my Max 3 fix patch on top and you'll have a flawless experience, no different to any other ROM you'll find out there.
That's (kind of) the whole point of treble to begin with!
Be able to build ROMs without the whole device specific crap...
Click to expand...
Click to collapse
There is just one or two things that don't work as it should with the gsi treble roms compared to xiaomi.eu
1.GPS, unable to get a lock..always hovering around 3 or 4 satellites with bad signal
2.viper4android not detecting the correct device, sometimes it does and sometimes not...not a big issue but to me it is annoying
Device specific roms would probably have these things working without issues.
Of course in the future there might be a bright minded who can fix this on the gsi roms and either get the dev to implement them in the treble system.img or provide instructions how to patch them.
But that's just my argument why it "could" in theory be better with a device specific rom for this device
You were saying?
MrColdbird said:
You were saying?
Click to expand...
Click to collapse
I'm sure it has gotten better but a few months back I was driving and came into a car accident and needed to take an alternative route so I would not sit there the whole night and it was snowing and pitch dark and the further up the mountain I drove and had to rely on my memory to know where I was, it was the only way around the highway that was closed off as the gps lost signal time after time.
I have also lived around this mountain area and it is a spot for radio silence.
Ham-radio has difficulties working here and only a few types of big antennas work properly
Calling with your cellphone don't work with most providers
The gps lost signal time after time on havoc while sitting at home testing several reflashes and updating the arb-less fw and xiaomi.eu I could not get a lock indoors or outdoors.
I also live in a cement building so it shields me, so of course the signal might be affected by that.
Because of that I have to use large 17db wifi antennas to be able to penetrate the walls.
Then I flashed the xiaomi.eu released after chinese new year holiday and imminently I got a lock on tons of satellites when sitting indoors.
Of course If I drive far away from any building the signal gets better for gps, but the difference between havoc and xiaomi.eu was significant enough for me to abandon it.
I need gps to work reliably in events such as this and I don't have time to play around with the phone
Your case sounds extremely special but in my case I notice absolutely no difference in GPS.
I believe it's because of the anti-roll back