yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] ChristianWS:
Everything seems to be working fine, except Taskernet because that requires Google Login or something, my device is smoother than when I used OpenGAPPS, although the battery lasts the same as before, and the device is, surprisingly, using as much RAM as before (I think apps started using more RAM since there's more available)

I have a question: Why can't I change the setting for holding the recents button? There's an option, but it's greyed out, in fact, every LineogeOS build I've ever used has that option greyed out, why is that?

Also, random question, but do you have ever considered porting Oreo or Pie to our devices? If no, why
[Moto G Android Development] MSe1969:
Regarding 'recents' button, which setting do you mean?

And with regards to Oreo/Pie:

I am in general not good at bringing up devices, I don't really know what to do to fix non-functional features like Camera or bad battery behavior - this all is in the area of making kernel and HAL code plus device config work with old vendor blobs and old hardware - definitely a tricky task.

There are people offering Oreo and Pie threads for this device, but the results so far aren't suitable as daily drivers.

This Nougat ROM offered by me is good as a daily driver, and I am not able in any way to do a better job than the people offering O or P for the falcon.
[Moto G Android Development] Scranalot:
I think ChristianWS is refering to this in Settings > Buttons:

Absolutely :)

I've been on this cracking ROM kindly provided by MSe1969 since the demise of the official LineageOS 14.1 back in Feb - initially in its original 'A. Variant' (Default LineageOS 14.1 with substratum and microG patch) from March & moving over to the 'B.Variant' (Hardened build with pre-installed microG and F-Droid plus substratum patch) in April & now on the latest May release.

I have found the battery life longer with the B.Variant (almost certainly due to the lack of PlayStore & other G* applications, although as I have posted in thread , I do use GoogleContactsSyncAdapter & GoogleCalendarSyncAdapter apks) & although haven't scientifically measured it, & it's subjective as to what's in use, it is just I am charging it up less often.

I couldn't be happier with this ROM for our 'Golden Oldie' Moto-G, as I have documented throughout this thread.

I haven't tried any O or P ROMs for our device, & I have no intention to, but from what I see there are quite a few problems that arise - including the fact that these ROMs are 'heavier' & more resource intensive - & the fact that MSe1969, with the B.Variant, has 'backported' hardening/ security features from Oreo, keeps updating it monthly with ASBs :fingers-crossed: - not to mention other improvements (i.e. Yalp store now 'embedded') - is fantastic :good:

It keeps the venerable Moto-G nimble, stable, current & secure - once again many thanks MSe1969 :D
[Moto G Android Development] ChristianWS:
Scranalot is right, its called "Recents long press action", I've never seen that option working, I tried searching why, but I've never figured it out

That's understandable, I guess I'm just starting to get frustrated because development for our device seems to be slowing down, yet each rom has some different thing that got fixed, but lacks other fixes. Like, there's only one ROM that fixed the long boot times, couldn't other devs see the changelog of that ROM and port whatever fixed the boot time into their own ROM?
[Moto G Android Development] asdf2002:
I just came here to thank you for your work, MSe1969. I've been using this rom for a while now and it is absolutely flawless so far. Performance is great, battery life too (my phone drains about 0.4% per hour, this equals to a week of standby time), and I get no random reboots like in so many previous roms.

A little question I have, how does that work with security patches? Are they automatically incorporated into your build or do you have to put them in manually? And when there's a new one, you update this rom and I'd have to flash it over my existing one, right? I'm not too familiar with this stuff. Again, thanks for making this and keep up the good work, it is much appreciated.
[Moto G Android Development] MSe1969:
Glad to get positive feedback :)

In regards to sec. patches, the short story is that I work every month to publish a build with newest patches, which can simply be flashed over the installed build (no wipe, as you would like to keep your data!)

Long story: 1st step is to pick or back port the monthly published sec. patches from Google's AOSP into the LineageOS repositories (via Gerrit code review), this is done by contributors to the LineageOS project.(I am one of them, but there are faster and more efficient guys usually picking up that job, before I have the time, but I did it last time for the 15.1 branch) For legacy branches like cm-14.1, merging into the LineageOS github repositories usually takes longer, so I generally pick the patches in advance into my build tree. If applicable, I then also implement patches to the kernel by either back porting the published Google patches or by looking into other 3.4 kernel repos.
[Moto G Android Development] MSe1969:
In regards to the "long press" topic, when I look at that specific code, it seems that the code to offer options, if options are present, exists - but simply no such options have been coded in cm-14.1 (this is a CM/Lineage feature, not an AOSP one).

EDIT: The code disables the preference, when no options are present, that is why.

With regards to "long boot time", well - yes, not nice, but if everything else works, not really top priority, so I am not actively searching for a solution. If you can point me to a cm-14.1 ROM for the falcon device (LineageOS 14.1, not 15.1, and no other ROM base) with linked sources, I can have a look and decide whether I want to follow that path.
[Moto G Android Development] legendavey:
There is no long boot time on the LOS 14.1 builds you maintain [MENTION=7929484]MSe1969[/MENTION] :)

The person you quoted was referring to the long time to boot the current unofficial LOS 15 and 16 builds on XDA.
[Moto G Android Development] Scranalot:
Yep I'll definitely concur with that - in my experience :)

Yes I assumed that was what ChristianWS was referring in his post https://xdaforums.com/showpost.php?p=79611535&postcount=110 as he was responding to:

But perhaps best if ChristianWS could post just to be certain & clear that up :good:

Regarding ChristianWS post https://xdaforums.com/showpost.php?p=79611535&postcount=110:

I'm afraid that is inevitable I think - there are many more & newer & more capable devices now that will consume devs time & interest - we're just fortunate that the likes of MSe1969 still keep this little diamond shining :D
[Moto G Android Development] MSe1969:
OK, thanks for clarifying :) - However, I noticed that the regular boot time of the falcon device indeed is a bit long, also on cm-14.1, but that has never really bothered me too much, because once it is up, it acts smoothly. That's why I interpreted it this way - but don't worry, all is fine. :)
[Moto G Android Development] ChrisRM:
Any advantage to type B?

[MENTION=7929484]MSe1969[/MENTION], are there any advantages to the more-secure type B variant (apart from pandering to my paranoia)? The existing LOS 14.1 of yours is a gem and a keeper, but there's always that nagging question ... "Would it be better/faster/make me more attractive?"

thanks,

Chris M
[Moto G Android Development] MSe1969:
The features are listed in detail in the OP. That is the most precise answer I can give, plus maybe going into more technical detail upon request. Whether you consider this as advantage or not is up to your personal preference.

What can be said in general is, that many apps work fine with microG, so for sure w/o the genuine Gapps, your device is expected to have better battery behavior, consume less data, have more memory and be a little bit more reactive. That is because Gapps is huge and background intensive, which in fact DOES matter on an old device like the falcon.

So even if you don't care about the Google spy services doing things all the time, which people like me consider at least "questionable", the device performance would be one advantage.

BUT: Some apps require the genuine Gapps to work properly... (Especially the nosy kind)
[Moto G Android Development] ChrisRM:
Fair points; so, to go from A to B, I think I should:

Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and specify "Dalvik", "System", "Cache" and "Data" to be wiped.

Do I then need to get rid of the 70-gapps.sh file as well?
[Moto G Android Development] MSe1969:
If you wipe system, the 70-gapps.sh file is deleted as part of that wipe. If you are fine with wiping data, than that's what you have to do and the clean way.

If you prefer to keep the data partition, please have a look to the OP of my LineageOS 15.1 thread for the Sony Xperia Z1 compact, where you will find some advice, but that is on your own risk.
[Moto G Android Development] MSe1969:
New builds with June ASB available

Hi all, new builds with June ASB are available for download and flashing.

A. Standard build

https://www.androidfilehost.com/?fid=6006931924117893837

System Webview updated to 74.0.3729.157

B. microG build flavor

https://www.androidfilehost.com/?fid=6006931924117893838

Bromite Webview updated to 75.0.3770.86

Yalpstore replaced by Aurorastore. (Yalp isn't actively maintained anymore since October last year, and since mid of last month, the app search does not work any longer - the pre-installed AuroraStore also allows app installation w/o "unknown sources")

Updates of F-Droid, F-Droid privileged extension and microG GMS core

Happy flashing!

Regards, M.
[Moto G Android Development] Scranalot:
Cheers for this latest release MSe1969 very nice

I flashed the 'B Variant' over your release from last month. Install went smoothly & as a bonus my corrected /system/addon.d/91-cm.sh (https://xdaforums.com/showpost.php?p=79497963&postcount=78) worked fine too, reinstalling & reconfiguring the Google*sync*.apks automatically - alls good so far :good:

Glad to see the Bromite Webview has been updated, which will alleviate the issues with the M74 version (Google Login - https://xdaforums.com/showpost.php?p=79509963&postcount=83) & the pre-installed AuroraStore is a nice replacement for Yalp Store (not that I use it much - 3 apps only - I use F-Droid for the rest ;))

So allsgudinda'hood & silky smooth :cool:

Thanks once again MSe1969 :)
[Moto G Android Development] ChrisRM:
Just keeps on running...

Thanks indeed for this. This one just slipped over the May version, neatly removed the Yalp issue, and just works. Please keep on doing this, my Moto G is 'old' (nowhere near as old as my car or bikes) and still does what is needed for a smartphone. Excellent stuff!

Chris M
[Moto G Android Development] peelie:
hi thanks for june update

i canlt seem to get addonsu-14.1-arm-signed.zip working? i have flashed it but phone is saying it is not rooted?

i am on B variant

thanks for any info
[Moto G Android Development] MSe1969:
Just to make sure: Did you enable the root option in the developer settings after flashing the root add-on? Root is disabled by default...
[Moto G Android Development] Scranalot:
Ebay App - Please Refer to Post #143

Hello again

Happily 'chugging' along on my original Moto G (Falcon) XT1032 on the 'B variant' of your ROM MSe1969 :)

However I have bought another Moto G (Falcon) but this time an XT1033, for its dual sim capability because some areas I frequent have poor/no signal with my main carrier.

This 'new' phone itself is in near mint condition &, as far as I can ascertain, is in perfect working order.

It came with stock ROM (Asian firmware) so I unlocked the bootloader, put the latest TWRP on it & cleaned flashed the latest 'B variant' of your ROM as per your OP.

All is fine but I came across a problem with the eBay app (installed from Aurora Store) - when I try to sign in it comes up with 'Invalid Request' on the login page (cannot take screenshot of eBay app sign in due to inbuilt app permissions)

I have no such problem on my XT1032 - login is fine & the phone setup is a mirror image of the XT1033 :confused:

So my question is have you any idea why this may be? & is there anyone else with a XT1033 who is having a similar issue or that could possibly test out the eBay app installed from Aurora Store?.

TIA :good:
[Moto G Android Development] MSe1969:
Hi, I don't really know and I don't have an XT1033 to test. Does the eBay APP maybe somehow attempt to use your phone number for something (which in fact should be none of their business) and can't truly handle dual SIM?

To isolate the problem, you may want to switch the SIM cards, only use one etc.

Are all other apps somehow dealing with phone numbers working properly?

That's all coming to my mind, but can't really help further.
[Moto G Android Development] Scranalot:
Ebay App - Please Refer to Post #143

Thanks for your response MSe1969 :good:

My phone number is registered with eBay - for 'security' purposes :rolleyes: - but whether the eBay app uses it to verify when signing in I don't know - however all I have to input into the signing in page is my email address/user name & password.

I actually phoned eBay customer services last Thursday, 27th, when I tried to sign in & it failed. I explained my issue, described the phone & made particular reference to it being a dual-sim phone plus I also mentioned the fact that I had being using their app without any problem on my near identical other phone - the difference being that that one was only single-sim. The eBay representative said that it shouldn't be a problem & while she was on the phone I tried clearing the cache & re-signing in, switching off data from the 2 sims & using Wi-Fi, & also uninstalling & reinstalling the app - all failed with the 'Invalid Request' notice on the login page.

She said she would escalate the issue up the line & I should get an email from them later.

Coincidentally Aurora Store had an updated eBay app release later that day! :eek: (surely just a coincidence - or maybe exceptional service lol :laugh:)

Yes I have done both of these things too - I also tried uninstalling the eBay app, boot into TWRP & wipe dalvik & cache, reinstalling from Aurora - plus did the same again only this time I ported my eBay app over from my XT1032 - all tried with 2 sims, 1 sim & no sim (WiFi only) - all failed with the 'Invalid Request' notice.

I have 2 other apps installed from Aurora Store - Met office & Dropbox. While Met Office doesn't require me to input any data Dropbox requires me to login (email address/user name & password) plus they text me a 2-factor verification code to input. Both of these apps are working fine, as far as I can see.

The rest of my apps are from F-Droid & include, amongst others, email clients, & they are working OK too.

The dialler & messaging (texts) working fine.

One thing that I have noticed that is present on my XT1032 that isn't on my XT1033 is on my internal storage - 'sdcard' (actual location is: /storage/emulated/0/Android/data/com.ebay.lid/) is this:

facebook????? Any thoughts?

So its a bit of a mystery :confused: I'll await a response from eBay (but won't hold my breath - though I have already received a feedback email - "how did we do" lol & that was within half an hour of me getting off the phone to them on Thursday lolol :laugh:)

I'll also try a 'dirty' re-flash of your ROM MSe1969 & maybe a 'clean' flash if that doesn't work.

I do use the eBay app & I find it quite handy - its quick & pretty effective to use & gives timely notifications however I can still login to their site through a web-browser & get email notifications so its not the end of the world - having said that it would be nice to have :fingers-crossed:

Like I said at the beginning MSe1969 thanks for your response - much appreciated - as is this fabulous ROM that you are producing :)
[Moto G Android Development] peelie:
no i did not thanks!

sorry to have bothered u with this queston!
[Moto G Android Development] :
Hello. I was wondering why is it when I use the camera it tells me to insert a SD Card when I do not have a SD Card slot. This happens on every rom I have tried. Any help would be grateful. Thank you
[Moto G Android Development] MSe1969:
That is weird. This does not happen with my device and this behavior would also have been brought up, if somebody else had it. Since you state "happens on every ROM", there must be something specific with your device. Have you e.g. restored system app settings with an app like Titanium, which have been backed up on an entirely different device (having an SD slot)? Or use a specific Camera app?
[Moto G Android Development] :
I have wiped the entire storage and have tried changing the partition to ext4. I have a XT1034. I have tried a differnt camera app and such to no luck.
[Moto G Android Development] :
https://xdaforums.com/moto-g/help/insert-sd-card-using-camera-t3680962 also someone did post something similar awhile ago but I do not understand everything they where talking about in the form.
[Moto G Android Development] :
https://imgur.com/a/SO8JXrz

I can not take a screenshot as well
[Moto G Android Development] MSe1969:
Okay... after having looked at your screenshot and also the referred forum post, I may have an idea...

You have mentioned, that you tried to convert to ext4 - let's start here, because I have noticed, that your phone complains about missing space to even save a screen shot.

- Therefore my 1st question: Can you at all access internal storage?

- Can you e.g. connect your phone with your PC via USB and do you then see a folder structure and are you able to access files or even to save files at all (even it is is a two-byte text file)?

I would almost assume that you may already have an issue here. Anyways, please try the following:

1. Boot into TWRP

2. Check whether you can access the file system there (path /sdcard from internal file manager or attach device to PC via USB)

3. If that is okay, proceed with step 6, if not perform step 4 and 5.

4. See item #3 and only execute, as advised: Wipe & format /data again, please reboot LineageOS to make sure all content is regenerated accordingly.

5. Check whether all issues are fixed now. If nothing has changed compared to #2, I have no idea. If all works now, be happy and stop here. If all works, except for the Camera thing, proceed with step 6

6. In TWRP, create a new Folder DCIM under /sdcard, if missing

7. In TWRP the option "Fix contexts" under "Advanced"

Regards, M.
[Moto G Android Development] oscarmbv:
Hello mate, I want to let you know that microg services core was updated it yesterday to version 0.2.8, if you can take that into account, please, for the next update of B version. Thank you.
[Moto G Android Development] MSe1969:
Hi, thanks for the update. I can't promise that, as I track the lineageos4microg org. on Github. The pre-built apks there have the F-Droid signature, so if the new apk is there, when I provide the next build soon, it will be part of the next build, otherwise not. This however is not really an issue, because you can simply launch F-Droid, update the package sources and you will be offered to update microG to v2.8 already now, this is what I did.
[Moto G Android Development] MSe1969:
New builds with July ASB available

Hi all, new builds with June ASB are available for download and flashing.

A. Standard build

https://www.androidfilehost.com/?fid=6006931924117909739

B. microG build flavor

https://www.androidfilehost.com/?fid=6006931924117909740

Regards, M.
[Moto G Android Development] ChrisRM:
Another excellent bit of work, just replaced the existing MicroG without a sign of concern. Very good.
[Moto G Android Development] Roderick83:
Hai MSe1969,

I can't hear any sound from my earphone. The AudioFX going crazy when it is inserted even if It is off.

https://drive.google.com/file/d/1Wgmb70RhX2e3lpNkTAYwPiE004EGGT9s/view?usp=drivesdk
[Moto G Android Development] MSe1969:
Hi Roderick83,

with my own device, all works fine, also AudioFX.

Could it be, that either something with your earplug is wrong? Either the earphone itself, or the jack on the device?

(Maybe simply cleaning it?)

Regards, M.
[Moto G Android Development] Scranalot:
Morning

Same here no problem with headphones with both my XT1032 & my XT1033 on your latest ROM - B Variant.

I'll be posting later with an update regarding my issue with eBay app - but basically it isn't XT1033 specific.
[Moto G Android Development] Scranalot:
Ebay App Update - RE: Posts #126 & #128

Please Note:

All references to ROMs in this post are concerning the B Variant unless otherwise stated.

In my posts #126 & #128 I referred to problems I was having with eBay app installed via Aurora Store specifically on my XT1033, well after some further investigation it appears not to be specific to just my XT1033 but my XT1032 too.

With this July release of your ROM MSe1969 I thought I would take the opportunity experiment with my eBay app installed on my XT1032 to see if this was indeed the case.

I took a Nandroid backup of installation under the June release on my XT1032.

I then uninstalled eBay app via Aurora Store plus I removed:

/storage/emulated/0/Android/data/com.ebay.lid/fb.bin

(see my earlier post #128) after taking a backup of it.

I then 'dirty' flashed the July release ROM over the June one.

After the ROM had successfully installed I installed the eBay app, via Aurora Store & tried to login & it failed with the Invalid Request notice.

So I then moved the backed up:

fb.bin

file back to:

/storage/emulated/0/Android/data/com.ebay.lid/

.

I ensured that the permissions & ownership of both the folder & the file were as when it was previously installed under the June ROM & again it failed with the Invalid Request notice.

So I looked back to see when & how I had originally installed the eBay app that was working under the June ROM release (& previously) on my XT1032.

In my post:

https://xdaforums.com/showpost.php?p=79449551&postcount=72

In this post I made reference to the fact that when I moved over to your B Variant ROM MSe1969 in April I had installed 3 app saved from the G* Playstore:

So the eBay app probably installed some extra 'features' from the G* Playstore that make it app 'valid'

But the upshot of the situation is I cannot get the eBay app to login when installed 'ethically' from Aurora Store on either of my Falcon devices XT1032 or XT1033 - don't know if anybody else has?

I realise this issue probably really concerns the Aurora Store & I shall post over there on the Devs XDA thread plus I notice the Aurora Store Dev states that the v.3* releases are still under development are bugs are to be expected.

The other 2 G* Playstore apps that I have installed via Aurora Store, Met Office Weather & Dropbox are fine, as I have referenced in my #128 post.

Also, as I stated in my #128 post:

Apart from that MSe1969 still very happy on this smashing ROM you kindly provide :)
[Moto G Android Development] jemail:
I wonder if these problems are anything to do with Google using the new split apk delivery mechanism through the Play Store?

I've noticed that I can only install Swiftkey through the play store and not restore a functioning version at all using Titanium.
[Moto G Android Development] ChrisRM:
I find the same thing with my xt1032; all looks good until one tries to log in, then 'Invalid request'.