[Android General] 7awliet:
RR 5.7.4, GPS, Patches, And Kernel

I had compared and inspected every changed file in the "RR5.6.8 CAMERA & OTG FIX by wac pereng.zip" with the RR 5.7.1 from mtkroms.com because that's what I was working with. I believe people were applying the fix to 5.6.9 and 5.7.0 too. I actually missed the 5.7.2 build because mtkroms.com didn't build that one and at the time I was working with VTs & DTs and some other stuff and didn't bother to check other places for 5.7.2. I can't remember if properly tested GPS on 5.7.1 but I know it took me 20+ seconds to connect when I tried.

The next build I used (and did the scripts again for) were 5.7.3 and GPS works on that for me, everytime, but it takes 11-13 seconds to connect. I never used a GPS patch on 5.7.1 nor on 5.7.3. My GPS has always been fine - but I haven't tested it thoroughly in multiple apps.

As for the cam and otg fix, I remember that some things had changed between 5.7.1 and 5.7.3 but the same fix files bundled with 5.7.1 I also bundled with 5.7.3 because RR or mtkroms.com hadn't applied those patched files - not that I expected them too because the fix, after all, is for MT6582/A5000 devices.

That said, I completely comprehend that if something like libcameraservice.so and others are needed to be flashed again - after flashing the ROM - to be properly registered then so be it. :good:

I don't know anything about any other cam fix that you used on that other ROM you mentioned haha :p

I appreciate the research though, thanks.

I used my porting scripts to port RR 5.7.3 and my patching script to apply the "RR5.6.8 CAMERA & OTG FIX by wac pereng.zip" patch. I've also used my porting scripts alone and then afterwards applied the patch via TWRP v3.0.2.0 (can't remember which method I'm currently on), but that was 1 and a half months ago. Never applied a GPS patch nor any other patch and GPS worked first time right away and still does. I have had no other problems, although I must say that the Wi-Fi autoconnect issue is back for me and I have no idea why, but it doesn't irritate me as I don't use the device.

Also, RR 5.7.4 is the last Marshmallow RR build and so work on MM is finalised by the RR team, as they have now begun work on Nougat. I would suggest upgrading to RR 5.7.3 or 5.7.4 and apply any patches you need to (there's patches and workarounds for just about everything and there links have been posted countless times in this thread including in the last couple of pages).

I didn't yet get round to upgrading to RR 5.7.4 from 5.7.3 as I am myself looking into Nougat, but for those that wish to try, here's 2 links to RR 5.7.4 for A5000/MT6582:

http://x7customroms.blogspot.co.uk/2016/10/rr-574-for-lenovo-a5000-mt6582.html

http://4pda.ru/forum/index.php?showtopic=663798&st=5620#entry53461583 (no account needed) (if you encounter the Google Play connection issue, delete the spaces in between "Lenovo A5000" in \system\build.prop, as has been said a thousand times in this thread already).

I may upgrade myself once I get round to inspect those .zips on Wednesday perhaps and see what's changed in them regarding incorporating fixes.

[MENTION=4964045]bronozoj[/MENTION] if you wanna flash generic stock first like S030 then flash RR like RR 5.7.3 so you that you start from scratch and know you're doing everything right then you could try that, be sure to backup... and before you ask... it's post #1029 that you want (we know the post # off memory now because it's been asked and mentioned and linked countless times, even in the last few pages xD ). And no, your custom stock from your carrier wouldn't have made much difference. Though it's a rare build IF you have a backup of it and could share it.

Make sure to use the latest TWRP (v3) (I should update post #1029) and make sure you're wiping Cache and Dalvik Cache at the necessary points. Regards.

Exactly right. I get that it may not be your phone and that you may want preserve the warranty but the reason you were just given is why you need to flash TWRP recovery (or some other recovery but we here have only provided details for using TWRP).

I was going to suggest that you could flash the Luck@s 3.4.67 through SP Flash Tool (I think), so that you would keep the Lenovo recovery... but you would still be able to see that the kernel is not the stock one in one way or another. I don't think you can see the kernel info such as version and build number from the stock settings app (I can't quite remember), so you may be able to get away with flashing the Luck@s 3.4.67 kernel via SP Flash Tools (boot.img only).

This what you see when you got to ftp://185.86.77.191/LuckAs-kernels/A5000/ :

[IMG="LucaAs A5000 Kernels"]http://dl-1.va.us.xda-developers.com/3/8/9/2/8/0/4/Screenshot_(316).png?key=lLz6-D2SyyjxGiNr1nhV0w&ts=1475437226[/IMG]

I still don't get the fascination of people using a kernel other than the latest one (14th May 2016) :silly: