yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Themes, Apps, and Mods] celticchrys:
I posted this on the ZTE Community forums, and thought I'd add it here as well.

The notification bell on the lockscreen is a major annoyance for many of us. I was looking for some other way to manage this, but lockscreen widget apps don't work, and most lockscreen apps don't support the fingerprint reader, Smart Lock, or double tap to wake. After reading a lot of reviews, I'm cautiously optimistic about Next Lock Screen, an Android app by Microsoft, of all things! This app sort of runs "on top" of/with your built in lockscreen. It shows the notifications, right there, no bell, and it still works with the fingerprint reader and the double tap to wake feature on my ZTE Axon 7. It claims to still work with Smart Lock, but I haven't been able to try that yet.

Google Play Store Link: Next Lock Screen - Android Apps on Google Play

In the Next Lock Screen settings, set the "Screen Lock" option to "System" to keep your double tap to wake, fingerprint, PIN, etc. just as you already have them. If you do this, you will still get a glimpse of your old ZTE lockscreen now and then, when you try to go into the Next Lock Screen settings, and it shows you the ZTE screen and makes you fingerprint scan before changing settings.

The Next Lock Screen is not quite as fast as the ZTE Lockscreen, so you glimpse it briefly before your homescreen, when the device unlocks.
[ZTE Axon 7 Themes, Apps, and Mods] klev2687:
I like the app that you suggest, but is there a way to keep showing ZTE wallpapers? ZTEs setup keeps changing wallpapers everytime the screen wakes up. I kinda like the feature. I know the Next Lock Screen app has a similar feature with Bing wallpapers, but that is only once per day.
[ZTE Axon 7 Themes, Apps, and Mods] JohnnyHempseed:
I've been using Next for the past week to get around the bell and it works quite well - especially with the fingerprint sensor. Very surprised that it took MS to make a very useful and intuitive lockscreen for Android. Of course, I'd rather have pure Android instead of an app work around.
[ZTE Axon 7 Themes, Apps, and Mods] aPexalpha:
That bell is truly a feature that i dont understand. So, si annoying and stupid.

Thanks for this but I'm gonna try the root way first :)
[ZTE Axon 7 Themes, Apps, and Mods] toyanucci:
There's a way to remove it with root?
[ZTE Axon 7 Themes, Apps, and Mods] tele_jas:
I was about to ask the same thing :highfive:
[ZTE Axon 7 Themes, Apps, and Mods] xgerryx:
Basically any 3rd party lockscreen, like Next, AcDisplay, Ambient display, etc, will disable the stock lockscreen when the 3rd party app takes control. It's a work-around. People probably want some kind of interaction from the lockscreen anyway, and this is a way to get rid of the stupid bell and get that interactive display at the same time.

Edit: I missed the post before yours. I do hope that someone creates an option in settings on a future ROM to disable it directly though. After root and bootloader unlock of course.
[ZTE Axon 7 Themes, Apps, and Mods] Gachmuret:
or just shout about it loud enough at ZTEs, so that they will make it an optional feature in coming updates... there is a bunch of optimal features they should integrate:

- optional bell on lockscreen

- optional on-screen buttons (as chinese 6gb versions have already)

- optional black/dark theme (specially with that amoled display)

... will tell more when I got the phone :silly:
[ZTE Axon 7 Themes, Apps, and Mods] runderekrun:
I kind of defeated the bell using Tasker to simulate a touch right where the bell is. Unfortunately it simulates a touch even when I use the finger print. Not really sure which is more annoying, the bell or having a touch in the upper left every time the screen comes on. That's how ****ing annoying this bell is.
[ZTE Axon 7 Themes, Apps, and Mods] mmamedov:
How's that a root workaround? The method you described can be used without root as well and the problem with it is that it doesn't support the fingerprint scanner.

Does anyone have a stock android lockscreen app so I can install is as a system app and delete ZTE one? Thanks
[ZTE Axon 7 Themes, Apps, and Mods] XblackdemonX:
Are you able to use fingerprint with NEXT and the stock lockscreen disabled? For some reason the only way I can use fingerprint is if I have both lockscreens enabled at the same time.
[ZTE Axon 7 Themes, Apps, and Mods] JohnnyHempseed:
No, only with both on. It's slightly annoying, but less annoying than the bell.
[ZTE Axon 7 Themes, Apps, and Mods] XblackdemonX:
Yes I agree!:good:
[ZTE Axon 7 Themes, Apps, and Mods] mmamedov:
Can someone please make an xposed mode or something similar for those who have root and would like to keep the stock lock screen? I imagine it's not that difficult of a task, but I have little to no skills when it comes to coding so can't make anything like that ? Thank you
[ZTE Axon 7 Themes, Apps, and Mods] celticchrys:
Sadly, I think you're limited to setting one wallpaper or using the Bing wallpapers.
[ZTE Axon 7 Themes, Apps, and Mods] celticchrys:
Still, that was rather clever of you. :good:
[ZTE Axon 7 Themes, Apps, and Mods] runderekrun:
I figured out how to have the bell auto open with Tasker. I uploaded the two profiles that are needed to do this. Probably not the most elegant Tasker work but meh it works. This works by simulating a touch where the bell is when you are on the lock screen but not when you use finger print unlock.

Looks like you need root for this.

To import: Save xmls to /sdcard/tasker/profiles

Load up tasker and long press profiles and hit "import".
[ZTE Axon 7 Themes, Apps, and Mods] scottk135:
I can confirm that this works for me as well. Thank You.
[ZTE Axon 7 Themes, Apps, and Mods] runderekrun:
This profile works without root to auto hit the bell and is much faster than my other one. You need tasker and autoinput.
[ZTE Axon 7 Themes, Apps, and Mods] Rigby J:
How does one set this up?
[ZTE Axon 7 Themes, Apps, and Mods] runderekrun:
Install Tasker and AutoInput.

Download the profile to /sdcard/tasker/profiles.

Load up tasker and long press profiles and hit "import".
[ZTE Axon 7 Themes, Apps, and Mods] thjoca3:
Thanks, this works grand.
[ZTE Axon 7 Themes, Apps, and Mods] sunny_j:
I did everything you said and it's not working for me. Any other ideas? Thanks
[ZTE Axon 7 Themes, Apps, and Mods] Gachmuret:
Could it be related to different DPI settings?
[ZTE Axon 7 Themes, Apps, and Mods] thjoca3:
I am running a 538 DPI on mine, I do think I had to go under the task tab - tap on "hit bell" tap on "autoinput action" and then edit icon - tap "Easy setup" from there it opens a notification, turn the screen off and back on and tap the notification bell icon. unlock phone, look at the notification and tap "accept" it should give you some options, I selected the coordinates, and then check the advanced area and made sure "is Tasker action" is checked, back out and hit the check mark at the top, back out of tasker, turn the screen off and back on and see if it works.
[ZTE Axon 7 Themes, Apps, and Mods] sunny_j:
Thanks for the feedback guys. Where do I adjust the dpi? The only setting in display I see if text size
[ZTE Axon 7 Themes, Apps, and Mods] thjoca3:
either rooted by changing the build.prop or non rooted by adb and wm density(some apps may look funny)
[ZTE Axon 7 Themes, Apps, and Mods] runderekrun:
Hmm I dunno. Did you start the autoinput service?

---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------

My first profile maybe but the second one isn't technically simulating a touch so it shouldn't matter.
[ZTE Axon 7 Themes, Apps, and Mods] CaiKroll:
Hey, I'm trying to get this working on my A7. For some reason it isn't and I've tried everything to my knowledge (I'm not an expert at Tasker).

I have AutoInput installed. I install the 2 .XML files but idk why it won't work.
[ZTE Axon 7 Themes, Apps, and Mods] stevenkelby:
Just install the single file from post #19 above then do this :

, I do think I had to go under the task tab - tap on "hit bell" tap on "autoinput action" and then edit icon - tap "Easy setup" from there it opens a notification, turn the screen off and back on and tap the notification bell icon. unlock phone, look at the notification and tap "accept" it should give you some options, I selected the coordinates, and then check the advanced area and made sure "is Tasker action" is checked, back out and hit the check mark at the top, back out of tasker, turn the screen off and back on and see if it works.

It worked perfect for me, thanks runderekrun and thjoca3!
[ZTE Axon 7 Themes, Apps, and Mods] max1001:
You do not want to disable the built-in lock screen. It's a security risk to only use a 3rd party lock screen because any 3rd party apps are disable once the phone is booted into safe mode.
[ZTE Axon 7 Themes, Apps, and Mods] stevenkelby:
Meh, no ones getting their hands on my phone and even if they do what's going to happen? They log in to my Internet banking and steal the dozens of dollars in my account? :D

Good point though, definitely a concern for lots of people and this disables it.

Next Lockscreen gets rid of the bell and keeps security, good option.
[ZTE Axon 7 Themes, Apps, and Mods] sunny_j:
Thank you so much for the detailed instructions. the BadBell xml is working for me now!

Is there a way to have the screen light up when a notification comes through? Now when I receive a notification on the lock screen, only the red led blinks.
[ZTE Axon 7 Themes, Apps, and Mods] Catalana:
Just got my Axon 7 (US version) from Best-Buy a couple of days ago. I'm using the 'Stock Android' theme and 'Nova Launcher'. "Show on the lock screen" notifications is enabled. Model is ZTE A2017U, build number is A2017UV1.0.0B20 and build time is Jul 7, 17:16:56 CST 2016.

I have yet to see the notification bell, and I have had plenty of notifications come in on the device. So I am at a loss as to how I could enable this phantom notification bell. Maybe someone can enlighten me, please.

BTW, so far I am extremely pleased, coming from a rooted Nexus 5.
[ZTE Axon 7 Themes, Apps, and Mods] Catalana:
Small update: after playing with the phone a bit more, I realized that I was using the fingerprint scanner almost exclusively to unlock the screen, hence I wouldn't see the little red bell. Using 'double tap to wake', would turn the screen on in its locked state, and yes, there it is. A sigh of relief, and the bell does not bother me a bit, as the finger print scanner makes this issue mute for me. I have the phone set to turn the screen off fairly quickly.
[ZTE Axon 7 Themes, Apps, and Mods] thjoca3:
My screen does light up when I get a notification, and the task runs... but I have messed with gravity box a lot, and who knows what I have set in there at this point...
[ZTE Axon 7 Themes, Apps, and Mods] Life Engineer:
Very simple... It's for privacy reasons so that not anyone who was able to get a glimpse of your lockscreen can see your notifications.

But yeah, we can hide those anyways within system!
[ZTE Axon 7 Themes, Apps, and Mods] rikin93:
On the next EU update they are making the bell optional :)
[ZTE Axon 7 Themes, Apps, and Mods] tele_jas:
I just installed Floatify and so far, I like it! https://play.google.com/store/apps/details?id=com.jamworks.floatify

You disable the stock android notifications (the bell) on lockscreen and use Floatify instead. It displays over your current lockscreen and in my 5 minutes of testing, I really like it.

I'm going to start a new thread about this
[ZTE Axon 7 Themes, Apps, and Mods] runderekrun:
I just had to set this up on a new phone. You have to activate AutoInput service not just install it.

Then the tasker task will work perfect.
[ZTE Axon 7 Themes, Apps, and Mods] NEMESIS_9000:
Do you know how to disable the wallpaper changing (mine is not on every unlock though)? I've tried to set different themes, setting my own wallpapers to no avail.
[ZTE Axon 7 Themes, Apps, and Mods] huntnyc:
Try clearing data and cache of ZTE Locker. I think this is what worked for me.
[ZTE Axon 7 Themes, Apps, and Mods] WesTD:
Can we fully disable stock lockscreen?
[ZTE Axon 7 Themes, Apps, and Mods] Znuf:
Tasker

The tasker file didn't work on my phone A2017G, i setup again autoinput. and it's perfect.

Here is my xml file.
[ZTE Axon 7 Themes, Apps, and Mods] aaronDroid80:
There is actually an option built in (at least on the B29 firmware) that lets you show notifications.

Sent from my (insert Nougat adjective) G2 (D800): the Nexus 5 I never had.
[ZTE Axon 7 Themes, Apps, and Mods] BIGWORM:
B29 brought that feature. I think before that on B09 it was locked to where the user had to toggle the bell to see the bells.
[Optimus One, P500, V Q&A, Help & Troubleshooting] niral.naik:
People who are using LG P500 must search about optimus one 's cm12 update .

This is a general thread to discuss the issues.

News:

CyanogenMod announces official CM12 Nightlies!

http://phandroid.com/2015/01/05/cyan...m12-nightlies/

Do not even expect P500 on the list!

CyanogenMod 12 nightlies now available for 31 devices, based on Android 5.0.1 Lollipop (LRX22C). LG Optimus One is out of the list to be sure

http://blog.gsmarena.com/cyanogenmod...-0-1-lollipop/

While in other hand, our devs are working to port experimentally newer version of CM12 (Android 5.0.2 LRX22G) on armv6 obsolete devices, though!

But …

To lg p500 users (you know who you are)

Long, long ago...

A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...

STATUS: NOT BOOTING

JENKINS SHUT DOWN

NO DOWNLOADS

The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.

I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.

Website:

http://androidarmv6.github.io/

Source code:

https://github.com/androidarmv6

You can watch development as it progresses, or you can sign in and participate here:

http://review.androidarmv6.org/#/q/status:merged

STATUS: NOT BOOTING

JENKINS SHUT DOWN

NO DOWNLOADS
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
Count me in. Trying to download enough to build. Never succeeded in the past.

Two issues here:

1. It will not fit. Newer file system places much on system that was before on data. It will never boot this way. Alternatives are to symlink away /system/app -- might it fit on the largely unused 64m cache or use sdcard sdext? Or reboard all of internal storage to system, data to sdext? First can be tried manually before attempting boot, I suppose.

2. ART compilation for ArmV6. After successful build, cannot even try it without solving 1.!

A third issue is reboarding already done, exchange previous data and system. Never was a good or sensible idea!, and TLS. To be able to play with this, I need to be able to get my phone back after failure or other errors that render the new ROM less than useful. Recovery versions no longer compatible. Solution might be to put things back as previous before building. I presently use CW that flashes 4.4.4 Omni from Rashed (never had luck with CM11). Have never tried TW but open to it if it gives be needed options and working backups.

Right now, cm12 sync is running much better than any I tried previously. Who knows? I would prefer to go to cm13 or omni versions, however.
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
Update: Repo sync has taken most of a day (on 100 meg connection?). Seems to hang up at:

Fetching projects: 99% (505/510) Fetching project platform/external/libseccomp-helper

When I hit enter at this point, asks for a github password. I have an account but had not logged onto that account so have no password to give it. Entering nothing will yield:

Password for 'https://github.com':

remote: Repository not found.

fatal: Authentication failed for 'https://github.com/cyngn/android_vendor_cyngn/'

It will the ask for a fuller login, but

Username for 'https://github.com': ....

Password for 'https://... [MENTION=4166799]github[/MENTION].com':

remote: Invalid username or password.

fatal: Authentication failed for 'https://github.com/cyngn/android_vendor_cyngn/'

error: Cannot fetch cyngn/android_vendor_cyngn

error: Exited sync due to fetch errors

Obviously not looking for my github. My build folder is left empty, all the stuff, I suppose in .repo.

So, what next.
[Optimus One, P500, V Q&A, Help & Troubleshooting] bigsupersquid:
Yep, everything is stuck in .repo limbo until it's satisfied.

The quick and dirty fix is to comment out the line with platform/external/libseccomp-helper

<!-- look I'm an XML comment -->

Or you can look here for repo tips

The big issue, as you said, is art.

you can totally run from a good sdcard.

Nobody got art to compile code properly. I tried patching it too, but I'm not as savvy with modern assembly as the androidarmv6 team was.

It did boot(loop) trying to dex system files over and over. Sometimes it'd even get through several of them before crashing and restarting art.

If you want to use adb to watch what's going on (or not going on) build -eng instead of -userdebug or it'll want authorization after the boot that never completed.

Best of luck!

Oh, and since twrp-multi has the reversed /system and userdata partitions, it won't flash other Roms than post-TLS Androidarmv6 based ones correctly, but it will back up and restore anything else. The backups will just have wrong names for system and data.

If you're really needing it, I can maybe pull out my p500 and PC and build a new twrp without the partition reversal and TLS (which, if I remember correctly, breaks older update-binary? Some annoyance happens from it.)
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
So I got as far as: CyanogenMod/android_packages_apps_Dialer, on same "server," password. Can likely live without seccomp but I guess I do need the dialer. Try commenting anyway, see what happens.
[Optimus One, P500, V Q&A, Help & Troubleshooting] bigsupersquid:
You might check out github.com/OS2SD [MENTION=4974969]HardLight[/MENTION] did nice work getting it up to date for cm-11

Change the .repo/manifest.xml so the default branch is cm-12.0 instead of cm-11 and that should get you most of the correct, updated projects.

You may have to tweak at the revision (branch) on a couple projects if cm-12.0 doesn't exist or is to out of date.
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
I did the init to cm-12 and that is what I have. No cm-11 anywhere.

There are too many things, at the 99% point of the sync, and it hangs up. I keep commenting lines but this is not the way to go. These things are not retrieved in order of their xml tags so this is problematic.

Is there an omni-6 github that I could combine with device files for our dinosaur?
[Optimus One, P500, V Q&A, Help & Troubleshooting] bigsupersquid:
Not that I'm aware. There is an omni p500 repo for KitKat on one of the aav6 people's GitHub, I forget which.

The problem with the sources you're getting is that they've been unmaintained for years. The os2sd repo has been pulled up to date for cm11.. not 12.. but the cm12 branch should remain in most of the projects. Repo downloads a lot more than you see, including alternate branches and git history.

If you copy the os2sd/android/default.xml to your .repo/manifest.xml and change the revision in it to cm-12.0 it'll not have issues with getting most of the projects, but everything hardlight has updated for cm11 will still be at the point it was abandoned by aav6 in cm12. It'll need lots of git pull and merge to catch it up.

I might be able to help more later when not on break at work.

Also, from experience building and using both lollipop and marshmallow on my new htc, marshmallow is a huge memory hog, and lollipop isn't much better. Even if getting it to run, it'll have to be fairly crippled just to not overload RAM on the old beasties.

Oh, and if the repo sync speed bothers you, bear in mind mine generally take up to five days (!) to make the first sync, then it's reasonably quick after that. My ISP speed tops at 5Mbaud/sec, and averages the same speed as 3g on the p500/v (30-100Kbaud/sec) on a bad day.
[Optimus One, P500, V Q&A, Help & Troubleshooting] bigsupersquid:
[MENTION=4708203]Dovidhalevi[/MENTION]

Any luck with syncing the repo?

I have a manifest.xml on my external hard drive that was syncing OK a while ago if you'd like to try it.
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
No. It ALWAYS fails at the 99% point.

That seccomp is the 505th item sought. fails there. If I comment out its <project> item, then it fails at the 504th item (which it got on the previous attempt!). Comment that, fails on 503, ad nauseum.

I have been using --force-broken to no avail. I did actually have it finish once but it then proceeded to say new repository available and restart. That one failed.

Just did a repo init and repo sync --force-broken. Failed at usual point. Attempted to enter passwords and such. This is what I finally got:

remote: Repository not found.

fatal: Authentication failed for 'https://github.com/cyngn/android_vendor_cyngn/'

error: Cannot fetch cyngn/android_vendor_cyngn

warn: --force-broken, continuing to sync

Fetching projects: 100% (509/509)

error: Exited sync due to fetch errors

So it "took" the force, went to end (509, the seccomp commented). But the same final error message. Leaves by build directory empty so cannot try any of the scripts suggested following the sync.
[Optimus One, P500, V Q&A, Help & Troubleshooting] bigsupersquid:
Dang.

Last time I tried to sync my aav6 cm12 repo it worked.

This time it's all "fatal: Couldn't find remote ref refs/heads/cm-12.0" on project after project.

I'll have to look into it when my PC is assembled... My phone can't do much more android building than repo sync until I get some arm tool chains built.
[Optimus One, P500, V Q&A, Help & Troubleshooting] bigsupersquid:
[MENTION=4708203]Dovidhalevi[/MENTION]

you can try this

https://github.com/AndroidArmV6OS2SD/android_roomservice

if you follow those instructions in your current working directory it shouldn't overwrite what you've already downloaded, except for the projects it'll want you to --force-sync

the existing cm projects should maybe update rather than redownload.

it should hopefully sync entirely but my test sync over my old aav6 cm12 hasn't finished yet. it does appear to be working though.

whether it builds in the next test. for now I've just been using my phone (ubuntu chroot) to play with the repo and github to set up an updateable base to work from since there's renewed interest in trying to work on the improbable dream...

Bear in mind none of the androidarmv6 projects have been updated to the most recent cm12, and should be merged with upstream cm. Because of that there will probably be build errors. This is a starting point for now. Plus I'm liable to get distracted with 7.0 since one of the aosp supported devices shares a very similar SoC with my current phone.

I'll help out what I can here though.