[Android General] 7awliet:
Addressing Multiple Issues

She was around again recently so I had some time to put down my LG work and test the things I had worked on for A5000. I ALWAYS have to backup her Data and restore that so as to make it look like I never touched the phone. She's on that Pokémon GO tip and using Instagram camera and other 3rd party camera, so she barely ever uses the stock camera.

Anyway, now to catch up on some posts:

HEY! I fully agree, I may get working on a FAQs, I'm not sure, my brain is so overloaded with stuff haha.

I can't remember if S124 has that option but if it does, it's under Display and it's called Brightness Adjustment, I think. Someone here's gotta know.

I don't advise this to you (but I include you

only

if you

absolutely

know what you're doing), but there is such a thing as S124_Lite2.1 (no login needed). This is for those that are insistent on S124.

This is identical to the first Destrooktor GPS patch, but only their update-binary and script (including certs) is - naturally - different.

I don't get why Ajit reverted most of his stuff to 5.6.8 in 5.7.0 and 5.7.1. If 5.6.8 has all the fixes, why is he not documenting it and why are his build sources not updated as such? I think he's applying mass patches to his source without knowing what it does. I dunno, I'm guessing. I'll talk about the GPS further down.

Hi, I really appreciate it. I'll list my findings further down. Thanks for helping out.

There are 3 camera fixes in the first post and a 4th in the form of an .apk that you posted later on. While I haven't tried fixes 1, 2, and 4, the common fix that everyone is trying (RR5.6.8 CAMERA & OTG FIX by wac pereng.zip) no longer works permanently in 5.7.1 (you said 5.7, not sure if you also mean 5.7.0). The thing that's bugging me is that I can tell the he got just about every file in that fix from UNPORTED 5.6.8, but I don't know where the libcameracustom.so nor where the boot.img came from. Cam fix 1 (Cam-fix-RR-M.zip) shares that same lib but contains 3 other files, and only one that is different in its contents.

I need to find this Wac Pereng guy because I can just about tell you that no matter what lib you tinker with, it's the boot.img that matters. Whoever found this Wac fix, please try to get some answers from him regarding where he got his files from. Thanks.

Hahaha your future self found out. I meant from SP Flash Tool. There is a guarantee that you will end up changing your MAC Addresses because you're also flashing NVRAM. I understand TWRP doesn't mess things up because you don't touch the NVRAM partition. If you wipe system in TWRP, it could be that 2.8.7.0 included wiping NVRAM in that and 3.0.0.0 didn't? Maybe that was the early issue? Either way, I regret not noting it down before nor backing up before starting all this.

You're gonna need to Google first to find out where file(s) is located in a stock ROM then download stock ROM and extract it. Tutorials for replacing bootlogo are to be found aplenty on YouTube. I'm sorry I don't have a flashable zip for you.

Hey, cute avatar [MENTION=6683954]iachimo011[/MENTION] :)

For those talking about settings not saving: the only time I ever came across this was on S029 (came like that from the shop, never upgraded it) and the Haptic Feedback (Vibrate On Touch (of the navigation keys)) would turn back on if I rebooted the phone. It was annoying but I don't have much else to say about what the problem can be. No such issue in RR 5.7.1 for me.

I can't access that, it asks for a FB account. No thanks.

There's TWRP 3.0.0.0 (recovery.img) on the first page. I also made a flashable zip version of it in post #1066 (read from after the last quote box onwards).

From my findings, I believe this was ported by jemmini and the original link is: http://4pda.ru/forum/index.php?showtopic=663798&st=2520#entry47505135 (you'll need an account to download).

They said (Google Translate from Russian): "Recovery compiled on the basis of Android 4.4.2 version of the kernel Linux version 3.4.67 (LuckAs@GMhost.com.ua) / Thu Feb 25 17:03:43 EET 2016"

Wanna REALLY test it? Here's how to know if a "camera fix" actually works: open camera, turn off flash, hold phone sideways with both hands, make sure normal photo mode it on (not video or panorama), now with left index finger on Vol+ and right index finger on Vol-, press Vol- + - + - + (rapidly as if you were taking a total of 6 images). If that doesn't freeze your camera and ultimately give you "Can't connect to camera" message the next time you start your camera then press both Volume buttons TOGETHER rapidly 4 times (as if you were taking 8 images), now you should have a non-working camera. Congratulations. :silly: :highfive:

Even though I've only tested cam fix 3 and not 1, 2, and 4, I'm sure enough to say that no camera fix will work. If you flash the 5.6.8 patch then that boot.img doesn't have GPS and the camera fix itself will conk out as just described above on RR 5.7.1. If you port and flash Ajit's RR 5.7.1 then I can confirm that has working GPS built in (I ported LuckAs' latest 3.4.67 kernel - 14th May) but the camera fix will break even sooner because it doesn't apply the patch that is IN the boot.img of the cam fix, the libs are anyone's guess about what they do and you can mess about with the libs and permissions files as much as you want, try to break it, but it will all depend on what the boot.img holds and where the fixer got there files from.

I really do appreciate that! Great work :D

I'll show you the screenshot further down comparing a certain BT file that Ajit asks in his guide to port, but has no sense to it. I'll explain it too.

Are they on RR 5.7.1? As I think that's when the 5.6.8 stopped working (if you inspect the files, you can see Ajit tried to incorporate HALF of the patch in his build, you would think that this would be even better but unfortunately not). I can't see where this group is on FB, do you need a FB account?

I really appreciate the effort but I don't think the cam fix will do anything. Also when porting I would love to know the kernel build you used.

I never understood the fascination with everyone using LuckAs' 10th Feb kernel build (released 11th Feb). I think they want to use the latest stable version on his releases, but if that was the case then they would at least use the 25th Feb build. I always use the very latest 14th May release.

Two people are reporting this issue in your build, don't be alarmed but I don't even touch the Wi-Fi folder when I port.

I inspected just about every file he asks to replace and if you did the same you would realise that ones in S030 are identical to RR 5.7.1. "So what else mustn't be touched?" is the question I'm asking.

I can't hold it in anymore so I have to say that as much as I appreciate Ajit's work, he porting method is ..... :silly: ..... it's outdated :eek: ..... some stuff makes absolutely no sense. I'm gonna release my thing in the next post ;)

Which camera fix? I hope you're using WinMerge. Also, open files with Notepad++ or......... no pad :cool:

HEAR, HEAR! :cowboy:

You tried my testing method I metioned above to northwindtrades?

I took 200+ with every possible mode and combination. Even with manual focus. By the way, to unlock the focus options, tap [HDR] in the top right to turn it on, then tap [HDR] just to the left of it (filters), then tap [Auto], now open the camera menu and focus can now be changed to Auto, Continuous, Infinity, or Macro :silly: :good:

...yet it will always break when trying my testing method.

I agree. The only reason I use RR is because Ajit said it's the best and I've seen mainstream tech sites even mention it in their articles. I'm becoming weary of this Ajit guy haha but I still love his work.

This has the simplest porting guide out of all of the ones he's posted. Skip the green text and follow the blue text. Do it only if you know what you're doing.

Woah, woah, woah... What do you mean can't run MM ROMs? If our 3.4.67 can do it, then maybe our 3.10.54 can do it too, no? May have to inspect the kernel that the one in that ROM uses. Does it have to be an A5000 specific kernel or will a MT6582 one do?

Or did you still mean what you said in #818?

TRUE, though the thing I don't like about joining forums is leaving an account dormant or no following up on replies. Though I do think I'll be winding down my input.

I never knew how to change the time in TWRP nor how to store it and make sure it saves.

Well with what I'm about to release should save you from uploading tons of MBs again ;)

[MENTION=7578167]Daz3n[/MENTION] as I said about GPS, RR 5.7.1 has fixed this issue (though I did use LuckAs' 14th May kernel) and the kernel in the boot.img in the 5.6.8 cam & OTG fix (10th/11th Feb release) breaks it (does not include it).

[MENTION=7387201]northwindtrades[/MENTION] & [MENTION=7453577]MithunSanthikumar[/MENTION] here's the list I have so far:

[My original (I think, doubt it)]

WLAN = 00:08:22

BT = 00:00:46

S/N: Box says 8 characters

[Downloaded S030:]

WLAN = 00:08:22

BT = 00:00:46

S/N: NULL (or it was 0000000000000000)

[My currently ported RR 5.7.0 and 5.7.1 from that very S030]

WLAN = 8c:77:16

BT = 44:8e:fb

S/N: 0123456789ABCDEF

[northwindtrades]

WLAN = a0:32:99

BT = e0:2c:b2

Roms tried validus,exodus,resurrection remix

Source ROMs were cm12.1 and octos v2

[MithunSanthikumar]

WLAN = 60:d9:a0

BT = 60:d9:a0

See S030 lines 11 - 13 on the left compared to Ajit's RR 5.7.1 lines 8 - 11 on the right:

[IMG="bt_did.conf"]http://dl-1.va.us.xda-developers.com/3/8/2/3/9/3/5/bt_did.png?key=qRsIPyKBXmGPTud57RgXUg&ts=1469497810[/IMG]

This doesn't mean much but it goes to show you that someone, at some point, touches unnecessary files.

See 15 and 29: https://www.bluetooth.com/specifications/assigned-numbers/company-identifiers

For fixes, can you try to make sense of this?: http://xdaforums.com/showthread.php?t=2695909

Also, does anyone know how to see hard-coded MAC Addresses?

[MENTION=5283894]Scout919[/MENTION], [MENTION=7326280]babigabi[/MENTION], & [MENTION=7570298]Hazem Mostafa[/MENTION] enjoy the next post with everyone else :cowboy: (and where's Qwerty@?)

[MENTION=7387201]northwindtrades[/MENTION] with RR 5.7.1 (without patches), the "GPS Test" app from Google Play takes 11 seconds exactly to find to the satellites (multiple at once) and 3 seconds more (14 seconds total) to lock on. Tilting the orientation of the phone, pressing the home key, switching apps, and pressing sleep/wake button - all these things will reset it so be careful, but I don't know if that would be the same for other apps like Google Maps and Pokémon GO. Hold the phone so the screen is facing the sky. Told you it was fixable :o

P.S.: [MENTION=6762092]FurqanHanif[/MENTION] you still want that stuff in #725?

P.P.S.: [MENTION=7369927]9jabasewap[/MENTION] your sig... haha too big and the xda app sig is unnecessary

P.P.P.S.: if something doesn't make sense, it's most likely a typo ('with' instead of 'will') or a missing word ('that the in' instead of 'that the one in'), 'cause there's plenty of them, my brain's out

P.P.P.P.S.: PLEASE don't quote this whole post

P.P.P.P.P.S.: read my sig and the first post, thank you.