Related
I'm currently running .232 on my 5803. I'm used running custom roms as I had a nexus 5 before this but seeing as how stock is very close to aosp, what advantages does CM have over stock?
Also has the camera issues been resolved or is it still dependent on the ta partition?
Since the low light and similar functions require the TA partition, what's stopping someone from flashing cm 12.1, relocking the bootloader and then restoring the ta?
There are basicly no advantage in running other than stock. Camera "problem" with TA-partition is not fixed due to CM/AOSP does not support the Sony DRM function/framework at all so the TA-partition does not matter with custom rom (afaik). There is also a fish eye bug with the camera on custom rom when straight lines bends in the picture.
If you dont have the google play services battery drain bug, stock will give you +1-2 days battery life with stock rather than CM/AOSP. Ive noticed AOSP-based seems to have better battery performance than CM-based (even with m5 kernel).
The smoothness of stock VS custom is HUGE. AOSP with L Speed mod with smoothness activated is at best okay. CM is way more sluggish in the menues even with L Speed mod smoothness.
Stock rom (and especially SLiM (stock based)) is liquid smooth at all times.
Also the hardware camera button seems to semi-work in custom rom. The camera starts and it takes a picture but the picture is not saved. If you use on screen button it works as intended.
Custom roms does not seem to be able to read/write all NFC-tags. Ex: The MiFare Classic K1 does not respond at all but it works flawless with stock.
On the good side; with custom you get all those good things built in to the rom. Customization is huge with some roms. Carbon is the best out of the box ive tried when it comes to functionality but its CM-based and sluggish (seemes like low frame rate). SlimLP is the smoothest and best performing battery wise that ive tried.
Anyone checked this? Is its really stable? What about camera
http://www.android.gs/update-sony-x...with-stable-android-6-0-marshmallow-aosp-rom/
I understand everyone's urge to jump on Marshmallow but none are stable and none will be stable for a long time, just wait
And "what about camera?" has been asked TRILLIONS of times already on the MM ROM pages, if it started working i'm sure it will be spammed absolutely everywhere as a miracle.
Ranjith pottekkatt said:
Anyone checked this? Is its really stable? What about camera
http://www.android.gs/update-sony-x...with-stable-android-6-0-marshmallow-aosp-rom/
Click to expand...
Click to collapse
This guy is a fraud and waste of time. Did you check his links? Those are empty folders.
There is no stable MM and there will never be. MM won't even be beta. Remember, last year we had LP5.1.1 stable at this time. And by October/November there will be Android N, but not for Xperia Z1.
You know why there will never be any other rom above LP5.1.1 for Z1? Because CM and others have switched to AOSP trees and AOSP has NEVER had a stable rom for Z1 or Z1c. Not LP, Not Kitkat, and not even Jeallybean...
optimumpro said:
This guy is a fraud and waste of time. Did you check his links? Those are empty folders.
There is no stable MM and there will never be. MM won't even be beta. Remember, last year we had LP5.1.1 stable at this time. And by October/November there will be Android N, but not for Xperia Z1.
You know why there will never be any other rom above LP5.1.1 for Z1? Because CM and others have switched to AOSP trees and AOSP has NEVER had a stable rom for Z1 or Z1c. Not LP, Not Kitkat, and not even Jeallybean...
Click to expand...
Click to collapse
So thats mean those MM developers are wasting their time?
alfred0725 said:
So thats mean those MM developers are wasting their time?
Click to expand...
Click to collapse
No one is wasting their time. MM official developers are not wasting their time, because they cover many devices. Those who compile unofficial builds are just building; they are not improving/modifying. AOSP Sony developers are the only ones who are probably close to wasting their time, because Sony would never provide truly working binaries for patent reasons and absent that their open source developers are working blind.
CM switched to AOSP binaries, because of DRM issues. If I were them, I would disable DRM for rhine devices, but they will never do that.
The bottom line is: the only way to have the camera work is to return to CM tree with a camera wrapper, which would require disabling DRM feature, because Sony MM camera binaries are DRM protected...
optimumpro said:
No one is wasting their time. MM official developers are not wasting their time, because they cover many devices. Those who compile unofficial builds are just building; they are not improving/modifying. AOSP Sony developers are the only ones who are probably close to wasting their time, because Sony would never provide truly working binaries for patent reasons and absent that their open source developers are working blind.
CM switched to AOSP binaries, because of DRM issues. If I were them, I would disable DRM for rhine devices, but they will never do that.
The bottom line is: the only way to have the camera work is to return to CM tree with a camera wrapper, which would require disabling DRM feature, because Sony MM camera binaries are DRM protected...
Click to expand...
Click to collapse
Thanks. I am noob!:crying::crying::crying:
But what is the advantage of AOSP binaries rather than CM tree?
optimumpro said:
No one is wasting their time. MM official developers are not wasting their time, because they cover many devices. Those who compile unofficial builds are just building; they are not improving/modifying. AOSP Sony developers are the only ones who are probably close to wasting their time, because Sony would never provide truly working binaries for patent reasons and absent that their open source developers are working blind.
CM switched to AOSP binaries, because of DRM issues. If I were them, I would disable DRM for rhine devices, but they will never do that.
The bottom line is: the only way to have the camera work is to return to CM tree with a camera wrapper, which would require disabling DRM feature, because Sony MM camera binaries are DRM protected...
Click to expand...
Click to collapse
Why are you always talking about camera when it comes to aosp MM stability? I think that many people (like me) don't really need that much of a quality when it comes to camera. I use dedicated camera when I want to take a nice photo of something and I use phone camera only for notes from school.
What I consider stable is not restarting, not overheating, not draining battery rom. Of course with everything working. The problem I have is that 3.10 aosp kernel drains more battery in deep sleep and my phone heats a bit faster than on stock with custom kernel. Also it sometimes freezes and restarts. (maybe they fixed it with some workaround now? I'll try it when I'll have more free time to build the rom)
If they fix those issues I won't complain.
SuperLamic said:
Why are you always talking about camera when it comes to aosp MM stability? I think that many people (like me) don't really need that much of a quality when it comes to camera. I use dedicated camera when I want to take a nice photo of something and I use phone camera only for notes from school.
What I consider stable is not restarting, not overheating, not draining battery rom. Of course with everything working. The problem I have is that 3.10 aosp kernel drains more battery in deep sleep and my phone heats a bit faster than on stock with custom kernel. Also it sometimes freezes and restarts. (maybe they fixed it with some workaround now? I'll try it when I'll have more free time to build the rom)
If they fix those issues I won't complain.
Click to expand...
Click to collapse
Because camera is a major piece of hardware and without it working properly, a rom can't be stable. But with regard to MM, there are other big problems some of which you mentioned: data, sound, overheating, restarting, slow charging, offline charging. Looks like with every release Google starts from zero. In addition, CM is no longer spending time on fixing issues, because they have their own OS.
optimumpro said:
Because camera is a major piece of hardware and without it working properly, a rom can't be stable. But with regard to MM, there are other big problems some of which you mentioned: data, sound, overheating, restarting, slow charging, offline charging. Looks like with every release Google starts from zero. In addition, CM is no longer spending time on fixing issues, because they have their own OS.
Click to expand...
Click to collapse
by the way I saw that the offline charging maybe got fixed. (https://github.com/sonyxperiadev/device-sony-common/commit/e1b7ca125c4bf776be586066baf3efc8b5631e40 )
And I'll maybe try to fully fix at last the jack detection as it drives me mad when it doesn't detect my mi pistons (if I don't hold headset button when connecting) and when I plug 3-pole headphones it gives me long-press of headset button all the time.
I found out it's maybe related to jack detection (all these issues) - https://github.com/SuperLamic/kernel/commit/5df476d4a4fb0e628b431ecd93999a1a764fb633 (this solves just the connection of 4-pole jack)
I haven't noticed any slow charging? (I charge my phone all night anyway). For the data problem - I don't have any mobile data problems, but wifi strength is low and it sometime disconnects..
You're right I hate how google is modding their api every version they release. (does it even improve the system somehow or it's just to make portation of new versions harder?)
SuperLamic said:
by the way I saw that the offline charging maybe got fixed. (https://github.com/sonyxperiadev/device-sony-common/commit/e1b7ca125c4bf776be586066baf3efc8b5631e40 )
And I'll maybe try to fully fix at last the jack detection as it drives me mad when it doesn't detect my mi pistons (if I don't hold headset button when connecting) and when I plug 3-pole headphones it gives me long-press of headset button all the time.
I found out it's maybe related to jack detection (all these issues) - https://github.com/SuperLamic/kernel/commit/5df476d4a4fb0e628b431ecd93999a1a764fb633 (this solves just the connection of 4-pole jack)
I haven't noticed any slow charging? (I charge my phone all night anyway). For the data problem - I don't have any mobile data problems, but wifi strength is low and it sometime disconnects..
You're right I hate how google is modding their api every version they release. (does it even improve the system somehow or it's just to make portation of new versions harder?)
Click to expand...
Click to collapse
Slow charging is, in fact an issue, at least for me. The phone never detects AC supply in my case, and so always charges at ~500mA. However, I hear this is not an issue with people using magnetic charging cables.
And I have to agree with optimumpro to some extent. I had faith in Sony, and hoped they'd make things stable by now. But I don't see anything productive happening anytime soon (latest blobs were released about 2 months ago). Hopefully, with all the efforts done to match Google's master branch, porting newer versions of Android would not take as much time as it did for MM (if things ever get stable).
drakonizer said:
Slow charging is, in fact an issue, at least for me. The phone never detects AC supply in my case, and so always charges at ~500mA. However, I hear this is not an issue with people using magnetic charging cables.
And I have to agree with optimumpro to some extent. I had faith in Sony, and hoped they'd make things stable by now. But I don't see anything productive happening anytime soon (latest blobs were released about 2 months ago). Hopefully, with all the efforts done to match Google's master branch, porting newer versions of Android would not take as much time as it did for MM (if things ever get stable).
Click to expand...
Click to collapse
The problem is that the new Xperias were released and Z1 is quite old device, so it's just logical that they would prioritize newer ones.
hah, I'm always using magnetic charger (to prevent damage to waterproof). That's probably why I don't have this issue, I'll take a look at it - maybe in july? (I'm not really linux/android developer, so I'm not promising anything).
SuperLamic said:
The problem is that the new Xperias were released and Z1 is quite old device, so it's just logical that they would prioritize newer ones.
hah, I'm always using magnetic charger (to prevent damage to waterproof). That's probably why I don't have this issue, I'll take a look at it - maybe in july? (I'm not really linux/android developer, so I'm not promising anything).
Click to expand...
Click to collapse
It's not about priority. In fact, the MSM8974 is one of the easier SoCs to work with, compared to the others. None of the other Xperias have stable MM yet (though this charger issue is unheard of). From what I see in the dmesg, it appears to be a problem with healthd (i.e kernel based issue). I took a look at it, but nothing seems to be wrong from an initial run through. Maybe some experienced dev can help out.
In any case, working on a WIP project is much better than sitting around and complaining everywhere. It's especially bad when the person in question is of the best devs for our device.
Hey folks, I am Canadian that is looking to possibly import an MI5 but I figured I should find out a few things from you all that have been living with these phones for a while before buying.
Are there any hardware or software issues with the MI5 that I should be concerned about? I have a sony z3 compact right now and it's been infamous for vibration motors, headphone jacks, and screen failures. It also has no AOSP based daily drivers.
Development seems to be pretty active here, is that actually true? Are developers dropping off from this phone or is there still a steady amount of work being done?
From the lurking I've done it seems that unlocking, rooting and ROM installing is pretty easy. Are there any permanent dangers to doing these hacks (above and beyond the usual)?
I'm aware there is some camera quality issues on non-stock ROMs, is the camera still usable? How is the battery on custom ROMs?
Is there anything preventing this phone from being a daily driver when using a custom ROM like RR? Does the fingerprint sensor work on AOSP ROMs?
I am also aware of the radio bands the MI5 supports, I should be fine with that as my imported Z3 Compact has the same bands (as far as I can tell).
Edit: I was also wondering if the IR blaster works on custom ROMs!
Thanks for reading, answering and putting up with my ignorance. I'm just looking for some answers I couldn't find on this forum when I was searching yesterday.
Community is happy to help
1. Hardware wise you have to keep in mind the phone is fairly fragile. Low light performance of the camera is a bit poor. Audio out of the headphone jack isn't great on stock MIUI, but that can be fixed with Viper4Arise or any AOSP ROM. RAM management and general performance on MIUI is "ok" - but the phone is blazing fast on AOSP + CAF. There is no component that is prone to fail that I am aware of, but I have read of the occasional hard-brick triggered from nothing more than a reboot on custom ROMs - this can be solved by flashing stock ROM in EDL mode.
2. There seems to be a steady amount of development going on - we just got the drop on about 7 new ROMs in the last month. However, there are and have been developers leaving in favour of the One Plus 3, and development is only moderate compared to its forum.
3. It's fairly easy, but a bit frustrating getting the bootloader unlock from Xiaomi, as it usually takes about 5 days for the unlock to be approved and then 5 more days for it to actually work. There is also a possible driver issue on Windows which can prevent unlocking, so if you're stuck that's probably the case. Except for the above mentioned possible hard-brick there are no additional dangers, and dare I say less so than other phones I worked on.
4. The camera is usable on custom ROMs but considerably worse. Mainly there is a lot more noise in the photos, but detail remains high. Video recording seems to be broken on most AOSP ROMs, but alternative camera apps are apparently a work around. In my experience battery life is better on custom ROMs as they have functional Doze on Nougat, but not by much.
5. Fingerprint sensor works fine on custom ROMs, even better if you consider that you can wake + unlock your phone without pressing the button. There have been reports of some people experiencing slow fingerprint scanning on custom ROMs (3-4s). I use a custom ROM as my DD and I don't have any major issues except video recording that I haven't yet bothered to address.
I hope that this information finds you well. The Mi5 isn't perfect, but I'd be damned to say that a better phone exists for $200. The camera, battery life, performance, screen, audio, and design is good and there really isn't much to worry about.
xdadevet said:
Community is happy to help
1. Hardware wise you have to keep in mind the phone is fairly fragile. Low light performance of the camera is a bit poor. Audio out of the headphone jack isn't great on stock MIUI, but that can be fixed with Viper4Arise or any AOSP ROM. RAM management and general performance on MIUI is "ok" - but the phone is blazing fast on AOSP + CAF. There is no component that is prone to fail that I am aware of, but I have read of the occasional hard-brick triggered from nothing more than a reboot on custom ROMs - this can be solved by flashing stock ROM in EDL mode.
2. There seems to be a steady amount of development going on - we just got the drop on about 7 new ROMs in the last month. However, there are and have been developers leaving in favour of the One Plus 3, and development is only moderate compared to its forum.
3. It's fairly easy, but a bit frustrating getting the bootloader unlock from Xiaomi, as it usually takes about 5 days for the unlock to be approved and then 5 more days for it to actually work. There is also a possible driver issue on Windows which can prevent unlocking, so if you're stuck that's probably the case. Except for the above mentioned possible hard-brick there are no additional dangers, and dare I say less so than other phones I worked on.
4. The camera is usable on custom ROMs but considerably worse. Mainly there is a lot more noise in the photos, but detail remains high. Video recording seems to be broken on most AOSP ROMs, but alternative camera apps are apparently a work around. In my experience battery life is better on custom ROMs as they have functional Doze on Nougat, but not by much.
5. Fingerprint sensor works fine on custom ROMs, even better if you consider that you can wake + unlock your phone without pressing the button. There have been reports of some people experiencing slow fingerprint scanning on custom ROMs (3-4s). I use a custom ROM as my DD and I don't have any major issues except video recording that I haven't yet bothered to address.
I hope that this information finds you well. The Mi5 isn't perfect, but I'd be damned to say that a better phone exists for $200. The camera, battery life, performance, screen, audio, and design is good and there really isn't much to worry about.
Click to expand...
Click to collapse
Thank you so much for the detailed response! Greatly appreciated!
This all is reminding me of the fun I had with AOSP ROMs back on my Galaxy SIII, happy thoughts! (I've been stuck in Sony's software for too long!)
What is CAF?
Is the IR blaster working in AOSP-based ROMs?
TheHow7zer said:
Thank you so much for the detailed response! Greatly appreciated!
This all is reminding me of the fun I had with AOSP ROMs back on my Galaxy SIII, happy thoughts! (I've been stuck in Sony's software for too long!)
What is CAF?
Is the IR blaster working in AOSP-based ROMs?
Click to expand...
Click to collapse
It's a pleasure
Well then it's good to know they run brilliantly on the Mi5 (buttery smooth UI, and I get good numbers on benchmarks as testament, see attached pics).
CAF is short for Code Aurora Forums, a collection of companies that merge their updated driver code with the vanilla AOSP code from Google.
I don't know if the IR blaster works on AOSP as I currently don't have any devices on me to test it with. I could try this weekend when I get home.
Edit: I've since arrived home and can confirm the IR blaster works on AOSP. I used Anymote if you're interested.
Alright guys, I spent a whole night researching and reading all the comments and discussions in a lot of threads related to Lenovo K3 Note and I just registered myself. Now, I want to install a custom rom and I found that the roms build by daniel_hk are the most reliable. But the thing is I'm not sure which one to install. LineageOS or SlimRoms or CarbonROM?
Please let me know which one is the best regarding Battery Back up, Ram and least lag ?
Also please post some significant Screen Shots of each roms Home, Menu, Settings, Notification Bar, etc.
So that I can see which one looks better for my taste.
And lastly please post all the fixes available and the best karnel.
I'm sure everyone in the K3 Note community will be helped through this thread.
Also I'm a total noob in this department so please ignore any of my idiocy as I don't know everything.
Thank you very much.
As far as I'm concerned, there are no stable Android 7.1 ROMs for this device yet. They all suffer from a serious flaw in one way or another - either video recording not working properly, video playback not working properly, poor battery life, misconfigured buttons or just random glitches and bugs that shouldn't happen, even after flashing fixes. I tried both Carbon ROM and LineageOS but I had to return to stock. Then again, the Stock ROM has poor memory management so it lags a lot. It's a shame, I've probably tried around 15 ROMs and the only one that was moderately stable was AOSP Vibe 6.0 which was a remixed china dev ROM but that has problems with internal storage glitches which causes all the userdata to be moved to another folder randomly (don't ask me why this happens, I really don't know but it is frustrating and happened twice, had to move all my files over again).
If you know of a fully stable AOSP ROM, even if it is 6.0, I'd be very keen to try it.
stephendt0 said:
As far as I'm concerned, there are no stable Android 7.1 ROMs for this device yet. They all suffer from a serious flaw in one way or another - either video recording not working properly, video playback not working properly, poor battery life, misconfigured buttons or just random glitches and bugs that shouldn't happen, even after flashing fixes. I tried both Carbon ROM and LineageOS but I had to return to stock. Then again, the Stock ROM has poor memory management so it lags a lot. It's a shame, I've probably tried around 15 ROMs and the only one that was moderately stable was AOSP Vibe 6.0 which was a remixed china dev ROM but that has problems with internal storage glitches which causes all the userdata to be moved to another folder randomly (don't ask me why this happens, I really don't know but it is frustrating and happened twice, had to move all my files over again).
If you know of a fully stable AOSP ROM, even if it is 6.0, I'd be very keen to try it.
Click to expand...
Click to collapse
Thanks for the helpful information, but I know k3 note is yet to receive a fully stable custom rom. Knowing that I still want to install a custom rom by daniel_hk cause firstly the stock rom is very laggy and I cannot work with it and to my knowledge those three roms has received almost all the necessary and essential fixes already. for example the YouTube zoom thingy and the snapchat thingy got fixed I heard and many others. I think I can live with minor bugs like gps navigation not being able to be correct and **** like that. That's why I'm asking which one should I go with between these three.
Fair enough, but the ROMs from daniel_hk, whilst good, are definitely still in beta. YouTube zoom isn't fully fixed even if you flash the patch. If you go from 1080p to 720p, or 720p to 480p, you will get a zoom bug. 1080p videos recorded on the device do not play back in the gallery app or MX player, and the flashlight turns off by itself if you turn the screen off. Otherwise performance is good.
Edit: Carbon ROM is the only one with the latest fixes so I'd go for that.
stephendt0 said:
Fair enough, but the ROMs from daniel_hk, whilst good, are definitely still in beta. YouTube zoom isn't fully fixed even if you flash the patch. If you go from 1080p to 720p, or 720p to 480p, you will get a zoom bug. 1080p videos recorded on the device do not play back in the gallery app or MX player, and the flashlight turns off by itself if you turn the screen off. Otherwise performance is good.
Edit: Carbon ROM is the only one with the latest fixes so I'd go for that.
Click to expand...
Click to collapse
So does Carbon Rom gives the best battery back up and uses the least Ram ?
chococheesecake said:
So does Carbon Rom gives the best battery back up and uses the least Ram ?
Click to expand...
Click to collapse
Probably not, but it's still pretty good
use latest AOSP STABLE2 AKA MADos........ this is by far the most stable NG rom
btw,daniel has built latest lineage...with hdr fixed...which makes everything fixed......as daniel fixd the hdr..... now....mugik04 will build Latest RR with fix.......wait for that rom.....
Cpt.mactavish said:
use latest AOSP STABLE2 AKA MADos........ this is by far the most stable NG rom
btw,daniel has built latest lineage...with hdr fixed...which makes everything fixed......as daniel fixd the hdr..... now....mugik04 will build Latest RR with fix.......wait for that rom.....
Click to expand...
Click to collapse
In the previous build of lineage, the hotspot issue still has not fixed. I've to configure hotspot fresh everytime if I want to connect it to my PC or other device otherwise it just shows connecting and never connects. Is there any specific fix for that?
svs36 said:
In the previous build of lineage, the hotspot issue still has not fixed. I've to configure hotspot fresh everytime if I want to connect it to my PC or other device otherwise it just shows connecting and never connects. Is there any specific fix for that?
Click to expand...
Click to collapse
Not at the moment. And there are still issues with video playback, flashlight and camera video focus.
Lineage OS 14.1 is the one I've been happiest with. There are niggles and glitches, with battery being the biggest. On the whole I accept it's still work in progress. Stick to stock if you need stability.
Sent from my K3Note using XDA-Developers Legacy app
It depends on what you want, no custom nougat ROM has it all....
Having tested it all, I use Resurrection Remix 5.8.2 with March 5 security update.
Battery life is about 30 - 45 minutes less than Daniel's Rom but the smoothes of the performance is better.
#1 It has super fast charging (2180Mah)
#2 GPS locks in few seconds.
#3 Hotspot works once you on it off it and on it again.
#4 YouTube works perfectly
#5 Video recording does not crash at all, with or without flashlight. Footej camera works perfectly which is a plus for me, whatsapp, Facebook, Instagram, periscope works well with the camera.
#6 it works perfectly with three different custom kernels I've tried on it. (I currently use the latest Daniel_hk kernel with voltage tuning & OC)
It serves me well and since I have 2 spare batteries I don't bother however, tweaking the kernel to powersave gives me more juice.
So, it depends on what is a deal breaker for you.
I've used 2 AOSP Nougat that are very good but since all AOSP Nougat Audio recording level is low, which is a deal breaker for me, I switched to LineageOS before hitting RR Nougat.
FYI Footej Camera only works because it records in 720p by default. 1080p recording is the problem.
By the way - I got fed up with bugs so I created my own debloated VibeUI ROW ROM with a nexus feel - so far it seems to work well and no signs of lag so far. I think the lag isn't caused by the core ROM, but the add-ons that Lenovo insist on adding. If there are no major issues I'll upload it by the end of the week
Bolumstar said:
It depends on what you want, no custom nougat ROM has it all....
Having tested it all, I use Resurrection Remix 5.8.2 with March 5 security update.
Battery life is about 30 - 45 minutes less than Daniel's Rom but the smoothes of the performance is better.
#1 It has super fast charging (2180Mah)
#2 GPS locks in few seconds.
#3 Hotspot works once you on it off it and on it again.
#4 YouTube works perfectly
#5 Video recording does not crash at all, with or without flashlight. Footej camera works perfectly which is a plus for me, whatsapp, Facebook, Instagram, periscope works well with the camera.
#6 it works perfectly with three different custom kernels I've tried on it. (I currently use the latest Daniel_hk kernel with voltage tuning & OC)
It serves me well and since I have 2 spare batteries I don't bother however, tweaking the kernel to powersave gives me more juice.
So, it depends on what is a deal breaker for you.
I've used 2 AOSP Nougat that are very good but since all AOSP Nougat Audio recording level is low, which is a deal breaker for me, I switched to LineageOS before hitting RR Nougat.
Click to expand...
Click to collapse
So if you needed to compare between LineageOS and RR Nougat, which one would be better in terms of smooth user experience and which one do you think has the lowest issues?
Also I do really need the most battery backup I can get.
stephendt0 said:
By the way - I got fed up with bugs so I created my own debloated VibeUI ROW ROM with a nexus feel - so far it seems to work well and no signs of lag so far. I think the lag isn't caused by the core ROM, but the add-ons that Lenovo insist on adding. If there are no major issues I'll upload it by the end of the week
Click to expand...
Click to collapse
Please do, I'll check it out.
stephendt0 said:
FYI Footej Camera only works because it records in 720p by default. 1080p recording is the problem.
Click to expand...
Click to collapse
Using premium footej camera on resurrection remix 5.8.2 March 5th security update Rom and it hasn't crashed over two weeks....
Bolumstar said:
Using premium footej camera on resurrection remix 5.8.2 March 5th security update Rom and it hasn't crashed over two weeks....
Click to expand...
Click to collapse
It plays back 1080p recorded videos ok?
stephendt0 said:
It plays back 1080p recorded videos ok?
Click to expand...
Click to collapse
Yeah, it does, smoothly without any glitch.
---------- Post added at 03:17 PM ---------- Previous post was at 03:06 PM ----------
chococheesecake said:
So if you needed to compare between LineageOS and RR Nougat, which one would be better in terms of smooth user experience and which one do you think has the lowest issues?
Also I do really need the most battery backup I can get.
Click to expand...
Click to collapse
Both are the same core but RR has a little more customization and faster charging.
LineageOS by Daniel has the best battery backup time in CM based Roms. I've achieved 5hrs SOT with one AOSP nougat. It has low audio recording that's why I didn't continue.
You can achieve faster charging on Daniel's Rom with ultimate or Vince kernel. But it comes with dt2w and takes extra juice from the battery.
You should try flashing different Rom and check it out for yourself
Cpt.mactavish said:
use latest AOSP STABLE2 AKA MADos........ this is by far the most stable NG rom
btw,daniel has built latest lineage...with hdr fixed...which makes everything fixed......as daniel fixd the hdr..... now....mugik04 will build Latest RR with fix.......wait for that rom.....
Click to expand...
Click to collapse
Hdr has been fixed but with another hotspot bug replacing it
Did you face hotspot bug in RR 5.8.2?? Mugiks ?? Can you confirm? :/
Basically, and I'll make this short so I don't ramble, if this is a side/wifi phone where all I need it for is gaming and music, does upgrading bring anything that people 'cant live without', or is staying with an older version that has had more time to be customized a better option? I'm on Pie right now, but it's one of those things I really can't tell without setting aside time to test/experiment and focus, which I haven't ;p
GWARslave119 said:
Basically, and I'll make this short so I don't ramble, if this is a side/wifi phone where all I need it for is gaming and music, does upgrading bring anything that people 'cant live without', or is staying with an older version that has had more time to be customized a better option? I'm on Pie right now, but it's one of those things I really can't tell without setting aside time to test/experiment and focus, which I haven't ;p
Click to expand...
Click to collapse
Compared to nougat, the custom rom status of Oreo and Pie is miles ahead and better.....yes, there are some bugs here and there but those are minors and won't hinder your day to day usage and not to mention that even some of those bugs are being fixed and will be ironed out in the next few months of update.....recently the camera issues has been rectified and by the next updates, the camera should work flawlessly without any crashes.....even GCAM is working perfectly on the rom.....try Pixel Experience if you want, updates normally come on a monthly basis and the latest camera build prop fix posted at Pg 60-62 fixes many camera crashes.....
The only bugs which are left are normally based on the rom and its sources and normally gets fixed in the next update
.
Yes,4k recording still now doesn't work in footej camera or in Gcam, but if you really need 4k recording,use the Filmic Pro camera, it will allow you to record at 4k with variable frame rates.
In terms of performance,there are some internal improvements but for day to day scenario it is more than enough, in short you\ll be able to play PUBG at low/medium settings at 30 fps ......
What we really need is a kernel developer who can make some good custom kernels which will help in performance improvements and increase overall stability and feature array across the board....
So, in short the custom rom status is better than ever for le 2, right now ..... and this is coming from a guy who was there from the beginning when CodeWorkz was developing the nougat rom for the device....
Well then, I guess Ill stick with Pie :0 Guess Im just used to windows, to where when 10 came out, you were able to upgrade for free from 7, and dx12 was supposedly ready to be supported, so i figured, get the new directx, get to make my OS legal, why not?
Hardly any games use dx12 still to this day. Compatibility with games and such was funky, especially with scaling. Audio software like Audacity had, and still has, bugs which arent there for win7. Hardware certificates had issues for quite a while (esp Asus hardware) so i couldnt us3 my network card.
Ive prolly gone back and forth like 4 times, until i decided to just stick with 10. So i figured there might be similar issues with a phone that wasnt planned to be updated with a new os to run better with an older version.
Hope that made sense ha