Related
My Moto X is rebooting on system startup. It doesn't happen always, but when it happens, it's always when the system is starting, when the apps are starting and being granted root permissions, etc. If I don't do anything, is fine, but If I unlock my screen while the apps are loading on startup and start to open some apps, it reboots(not always). I don't know If it overloads or something, but aLogcat doesn't record anything after the system reboots. I've already used Boot Manager to disable some apps from starting, but the problem persists. It's a Moto X 4.4.4 Stock and I never had this problem before. I belive t's a Xposed Module, but I want to know which one is. I've already did a factory reset, then rooted again, but the problem persists.(before I rooted I wasn't having this problem, this is why I believe it has to do with some Xposed Module or something related to root.)
PS: I will pay you 5 dollars(via Paypal) If you help me and find the problem (what's causing it) via these 2 logs. I know it isn't much, but I want to show some appreciation for helping me.
Here's the kernel message:
https://www.dropbox.com/s/5v9bcbsbqk3z3sq/kernel.pdf
Here's another one that I got right after the reboot happened.(I've waited for the device to start, connected my device to USB, then went to adb and wrote # adb shell dmesg.
https://www.dropbox.com/s/l2ghokfk2w97yv4/Kerneldef.pdf
Thanks.
Full Tutorial and clean Rom by @demenicis http://www.needrom.com/download/zte-axon-mini-model-b2016-only/
You can search on this thread to find the files for Android 6.0.1
You need to root and install TWRP for flashin Android Marshmallow
I recently bought a ZTE Axon Mini here in Europe. It is a pretty good phone, the only problem is the software part which has some lag and UI problems.
They certainly can be fixed with a custom rom or rooting and doing changes or by ZTE themselves.
Here I will write the problems
1) The touch responsiveness could be more fast and snappy, when scrolling etc.
2) random lag occurs from time to time, Some other lag issues with the background apps closing etc.
3) Notifications sometimes do not show at all even when keeping aps on whitelist (deactivate mi assistant to solve this)
4) Dolby Audio gets deactivated almost every time you use headhones .
5) Marshmallow release anytime soon?
6) the UI is too heavy for the phone, most stock apps have issues
7) You cannot adjust brightness inside camera app on auto mode, the HDR mode is really not good ( too blurry)
Click to expand...
Click to collapse
Most of these issues have been fixed on 6.0.1 Rom (search thread)
Summary and further tweaks by @demenicis http://www.needrom.com/download/zte-axon-mini-model-b2016-only/
Edit 1--------------------------------------------------
Root method has been found and works on all axon mini models Android 5.1.1
Credit for finding @orbitz52 and @Heze85
http://www.mgyun.com:81/thread-48100-1-1.html
Just translate the page on Chrome and follow the instructions
For 6.0.1 Marshmallow Root you need to have custom recovery and flash supersu via recovery
Edit 2--------------------------------------------------------
Notification issue has been solved (read pages 1-3)
!!IMPORTANT NEWS!!
Custom recovery for axon mini by @Bormental
TWRP 3.0.2 for ZTE Axon mini unofficial.
It works in all Axon mini mods (B2015 and B2016 with or without "Force Touch".
Installation manual:
1. ROOT device (see the manual in this thread).
2. Download the archive with TWRP.
3. Unzip twrp.img to phone's internal storage.
4. Install any terminal emulator from Google Play and open it.
5. Paste these lines one by one to terminal:
Code:
su
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/stock_recovery.img
dd of=/dev/block/bootdevice/by-name/recovery if=/sdcard/twrp.img
6. Keep the file stock_recovery.img in safe place. It is your stock recovery image.
7. Now TWRP is installed. You can run it by holding vol+ and power button when phone is off or just reboot your phone while holding the vol+ button.
HOW TO ENTER RECOVERY WHEN ON BOOTLOOP WITHOUT EMPTYING THE BATTERY by @Crisvendetta
1. Hold volume up and power button the whole time of this procedure until the moment said below
2. Keep holding, the first time the device will be stuck on boot logo for 10 seconds and restart
3.Keep holding until the device is stuck on boot loop for 5-6 seconds before powering down.
4. RELEASE BUTTONS AS SOON AS SCREEN SHUTS DOWN ON THE 5 SECOND BOOT
5.Now Device is shut down
6. You can enter recovery normally by holding power plus volume+
What to do if the phone with android 6.0.1 is suddenly switching off during backup, restore, copying heavy files or installing ROM:
CLICK TO HIDE CONTENT
Install aboot image from 5.1.1
Reboot recovery
Make all needed operations
Return back aboot image from 6.0.1 before rebooting to system
Attention! Android will boot only with proper aboot image installed!
WARNING! Your warranty is now void! Any operation with firmware can break your phone!
Special thanks
1) @Bormental
2) @orbitz52
3) @demenicis
Hi,
I can't confirm 1), actually my device runs smooth. I have the Build Version ZTE B2016 FTV1.0.0B01.0
2) random lags occurs, but rare.
3) it seems that this is an issue by the power saving management, I also have some issues with it. I'm actually testing autostart and whitelisting for background the important apps like messengers.
4) I didn't tested this yet
5) I read something arround February this year.
If you google for root, you can find some work instructions, but OTA will be deactivated. I have not tested it yet, will give the phone a few months and ZTE for the update
Issues
I have a lot of problems with this phone. Sometimes apps doesn't work. Most of the times I can't recive notifications, sometimes is laggy, some options doesn't work or change to it's inicial configuration, force touch is not accurate.... A lot! Please ZTE do something!. BTW, how can I solve the notification problem?!
Thank you so much
Korgan1983 said:
Hi,
I can't confirm 1), actually my device runs smooth. I have the Build Version ZTE B2016 FTV1.0.0B01.0
2) random lags occurs, but rare.
3) it seems that this is an issue by the power saving management, I also have some issues with it. I'm actually testing autostart and whitelisting for background the important apps like messengers.
4) I didn't tested this yet
5) I read something arround February this year.
If you google for root, you can find some work instructions, but OTA will be deactivated. I have not tested it yet, will give the phone a few months and ZTE for the update
Click to expand...
Click to collapse
The notification part is the worst until now.
What I would add is that the camera app is unstable. It gets randomly on night mode and could be improved, on the focus and autoexposure part .
Overall the phone is great, it needs to be improved on the software part and I believe it could succeed and give ZTE a even better reputation
Now on the updates, does anyone know when marshmallow will be released for the Axon mini?
Notification
Crisvendetta said:
The notification part is the worst until now.
What I would add is that the camera app is unstable. It gets randomly on night mode and could be improved, on the focus and autoexposure part .
Overall the phone is great, it needs to be improved on the software part and I believe it could succeed and give ZTE a even better reputation
Now on the updates, does anyone know when marshmallow will be released for the Axon mini?
Click to expand...
Click to collapse
Yes, the notification part is the worse. It should be solved in the coming days...
ZTE AXON notifications FIX !
Aitex10 said:
Yes, the notification part is the worse. It should be solved in the coming days...
Click to expand...
Click to collapse
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications. Otherwise, disable Mi-Assistant from the settings/apps.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
Also remove the accelerator settings inside the mi assistant / software settings
Dooosu said:
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Click to expand...
Click to collapse
I am also on 5.1.1.
Notification works better with enabling autostart and enabling background settings. I have disabled the Accelerator / Mi-Assistant, Android has its own power management.
Hello,
i did not find MI-Assistant, where exctely?
Crisvendetta said:
Also remove the accelerator settings inside the mi assistant / software settings
Click to expand...
Click to collapse
Hi,
where can i finf mi Assistant??????
ridowski said:
Hi,
where can i finf mi Assistant??????
Click to expand...
Click to collapse
Which version of Axon do you have ?
It seems the ZTE Axon A1R doesn't have mi-assitant or even power manger/ background manager, and it's on 5.1.1
Guess no way to get that without unlocking the bootloader?
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
Tried this on mine and this made no difference in fact in an attempt to combat the delayed notifications I had done the above and unfortunately in my case made no difference? If anyone has any other suggestions please let me know.
hoppi05 said:
Tried this on mine and this made no difference in fact in an attempt to combat the delayed notifications I had done the above and unfortunately in my case made no difference? If anyone has any other suggestions please let me know.
Click to expand...
Click to collapse
Inside mi assistant remove the auto run on startup and then press exit the mi assistant.
This last few days every notification has shown on time, I did a fresh factory reset and the applied all the settings. Don't know if that would help everyone but I am satisfied until now
I didn't do a factory reset and stopped the Mi-Assistant. Notifications work well after that. But don't forget to do Step 1 and 2, that is still neccessary beside of stopping the Assistant.
I was wondering what is the difference between zte b2015 and b2016 models. I have the b2016 but it seems nothing changes with b2015.
My geekbench 3 scores single core 712 multicore 3107
Antutu 38051 .
Korgan1983 said:
I didn't do a factory reset and stopped the Mi-Assistant. Notifications work well after that. But don't forget to do Step 1 and 2, that is still neccessary beside of stopping the Assistant.
Click to expand...
Click to collapse
Indeed, disabling Mi-assistant together with the steps mentioned, solves all notification issues
Dooosu said:
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Click to expand...
Click to collapse
What model is that? Sounds like the US version?
I am using MIUI Global 7.5| Stable (7.5.1.0 MXDMIDE) ROM & suddenly the notification area and lock screen is not working. The recent button and home button on the device is also not working. I was researching the web regarding the bug is android which might be causing this issue?
See this link here >> Android Police link >>
How To Fix Missing Home And Recents Buttons, And Notification Shade That Refuses To Pull Down After Android Update
Second Link >> Google Plus Link of PaulOBrien >>See this also
Now both the above try to resolve by connecting the mobile to you desktop/lappy in order to execute the command. There is an alternate option available here which might also work >> S7 Edge not showing notifications in tray and "recent apps" button and settings button dnt work
It talk about doing it by following this steps
"And I followed what the user Mike Tompkins said: "Did this using nova launcher. Long press home screen choose shortcut, activities, setup wizard, setup wizard test activity. Creates shortcut, open follow directions. Not sure if it really helps. Didn't have issue."
Here's the fix, being broken down dummy style:
1) Download Nova Launcher & set it as default to replace TouchWiz.
2) Long press on the home screen.
3) Choose Widgets.
4) At the top, under Nova Launcher, scroll to the right & press & hold on Activities and place it somewhere empty on the home screen.
5) Scroll down to Setup Wizard. I saw 2 Setup Wizard options.
6) Under the first Setup Wizard option, I opened it & scrolled down to the 3rd choice which said ".SetupWizardTestActivity". It might be in a different spot for you, but look at the small writing, that's how I saw this one.
7) Select that to create the widget shortcut.
8) Open it. Apparently you're supposed to have a menu to go through and just click through "Next", but there wasn't one for me.
The screen just flashed and then next thing you know, everything works!
But I am unable to find the .".SetupWizardTestActivity"
Any suggestion?
Moreover whenever I am going to developer option I see this message "Developer option is not available for this user"
I am sure I don't have any other user added to this handset.
Help & suggestions?
I have been able to access the device using abd, after adding permission, and have downloaded the logcat files of the device which is attached herewith >> Unable to attach logcat as am a new user, let me know how I can add them.
Now when I am connecting the devices via adb, the devices are showing in adb devices.
When i am executing this command >> adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
I am getting this following message:
Starting: Intent { cmp=com.google.android.setupwizard/.SetupWizardTestActivity }
Error type 3
Error: Activity class {com.google.android.setupwizard/com.google.android.setupwizard.SetupWizardTestActivity} does not exist.
I am not sure why this problem is appearing? any help to fix this issue of home button, recent button, notification issues fixed?
thing happened to you,seems like a system ui absence .. just reflash the rom ot try any other custom roms available.. or just a factory reset might help,,if not hepfull, i would insist you to try a custom rom..
btw are you rooted??
thilak devraj said:
thing happened to you,seems like a system ui absence .. just reflash the rom ot try any other custom roms available.. or just a factory reset might help,,if not hepfull, i would insist you to try a custom rom..
btw are you rooted??
Click to expand...
Click to collapse
Yes the problem seems to be System UI or something, I am not sure. I had rooted the device after the problem appeared, but it didn't able to resolve the issue. Today I had installed MIUI 8.0 on the device and all the problem disappeared, so it seemed like the problem, was with the bug in MIUI 7, or inherent bug when upgrading from KitKat to MM.
DESCRIPTION
If you have the Pixel Experience module installed on your phone and installed Google Phone from the Play Store or ever tried to use a patched Google Phone version (such as this one), you may have noticed that Google Phone force closes when you try to search for a contact or while opening the keypad. This Magisk module attempts to fix that and it works by replacing your non-AOSP contacts storage with Google's own version, the one supported by Google Phone.
IMPORTANT NOTES
Supports Android versions from Android 7 (Nougat) to Android P.
It will remove any phone/dialer/contacts/people applications from your phone (if supported) because they are incompatible with Google's Contacts Storage.
You should only install this module if you want/need to use Google Phone and Google Contacts.
TESTED/SUPPORTED DEVICES
HTC 10 (Sense based ROMs).
Note: It should work with other devices but I have no means no test them myself, I can only rely on the community to test this for me.
SPECIAL INSTRUCTIONS
Install the Magisk module as usual but DO NOT reboot your device just yet.
Go into "Settings » Accounts & Sync" and disable "Automatically sync data".
Go into "Settings » Apps" a, look for "Contacts Storage" (it's a system app) and clear application data.
Reboot your device now!
Go into "Settings » Accounts & Sync" and enable "Automatically sync data".
Google Phone should now work without force closing, hopefully.
Note: If you ever want/need to disable this module, you should also follow the procedure above (disable module, disable data synchronization, clear contacts storage data, reboot, and re-enable contacts synchronization).
DISCLAIMER
Install this module at your own risk.
Developer is not responsible for what you do on your device.
Please take all necessary precautions (like a nandroid backup) before installing this module.
DOWNLOADS
Google-Contacts-Storage-v0.0.0-TESTING.4.zip
XDA:DevDB Information
Google Contacts Storage, Tool/Utility for the XDA Community Apps
Contributors
rfgamaral
Version Information
Status: Testing
Current Beta Version: v0.0.0-TESTING.4
Beta Release Date: 2018-08-02
Created 2018-08-01
Last Updated 2018-08-02
@rfgamaral after installing magisk module and rebooting i keep getting android.process.acore has stopped.
I cannot get rid of it. By pressing ok all the time i managed to arrive to Apps but there is no Contact Storage app to clear data/cache after the reboot.
stathis95194 said:
@rfgamaral after installing magisk module and rebooting i keep getting android.process.acore has stopped.
I cannot get rid of it. By pressing ok all the time i managed to arrive to Apps but there is no Contact Storage app to clear data/cache after the reboot.
Click to expand...
Click to collapse
I also got that error when developing this module but I never got it after installing/enabling it, only after disabling it.
For some reason, the system does not recognize the /system/priv-app/ContactsProvider/ContactsProvider.apk (although the file is there). I'm not sure how to fix this to be honest, so I recommend you restore your backup to get you back to a working state. Maybe try the whole process again (makre sure you follow every single step) and instead of rebooting the system after installing the module, reboot to recovery and wipe dalvik/ART and cache. If that doesn't help, restore the device again until a solution for this problem is found.
Like I said, I also had this problem and because I live on the edge, I didn't make a backup of my system (idiot me). I had to make the system recognize the ContactsProvider.apk file and wen into recovery, deleted, copied it back from my ROM, set proper folder/file permissions, wiped dalvik/ART and cache and rebooted, the problem was gone. I installed my module again and it worked. But I'm honestly afraid to disable it and get that error back.
Which is weird because I'm replacing this file systemlessly, that's the whole point of Magisk. Maybe I'm doing something wrong, I'm no expert... We'll probably need help from someone with more knowledge on the whole Android system. But for the record, I currently have the version available on this thread installed on my phone. I have the Pixel Experience module installed and installed Google Phone from the store, it doesn't force close and all features seem to be working. I just need to get this module stable.
@stathis95194 Were you able to restore your device? I hope so... I've uploaded a new test version, didn't change much, not sure if it fixes anything.
rfgamaral said:
@stathis95194 Were you able to restore your device? I hope so... I've uploaded a new test version, didn't change much, not sure if it fixes anything.
Click to expand...
Click to collapse
Yeap I always take a nandroid before messing with the phone. Let me try the new version and report
Sent from my HTC 10 using Tapatalk
@rfgamaral soooo after flashing 0.0.4 i faced the same issue with android.process.acore has stopped popping all the time.
This time i took a different approach and didn't restore my nandroid. Instead i dirty flashed my LeeDroid rom.
Rebooted and lo and behold, stock dialer and contacts were missing and google phone was working perfectly. No crashing on searching (nearby places is working)
Now i need to test caller id and spam filter
I will keep testing and let you know.
stathis95194 said:
@rfgamaral soooo after flashing 0.0.4 i faced the same issue with android.process.acore has stopped popping all the time.
This time i took a different approach and didn't restore my nandroid. Instead i dirty flashed my LeeDroid rom.
Rebooted and lo and behold, stock dialer and contacts were missing and google phone was working perfectly. No crashing on searching (nearby places is working)
Now i need to test caller id and spam filter
I will keep testing and let you know.
Click to expand...
Click to collapse
Awesome, glad you got it working.
Now I just need to understand why installing this module crashes android.process.acore... But it's a bummer that this is happening, a little price to pay, I guess? At least until a fix is found... That and that whole install procedure which is required to avoid other different crashes because of incompatible storages.
Hi
I'm running 2.42.400.3 on U11.
I installed this and google phone from
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218
Dialer kept crashing so I installed your mod.
After that,com.android .phone keeps crashing.
I unistalled it and then I got acore crashing.
I restored feom nandroid but for some reason kept getting the acore crash, so I completely uninstalled magisk.
Now.... everything works. Even the dialer.
I'm really not sure what happened but.... thanks
gunnerhk said:
Hi
I'm running 2.42.400.3 on U11.
I installed this and google phone from
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218
Dialer kept crashing so I installed your mod.
After that,com.android .phone keeps crashing.
I unistalled it and then I got acore crashing.
I restored feom nandroid but for some reason kept getting the acore crash, so I completely uninstalled magisk.
Now.... everything works. Even the dialer.
I'm really not sure what happened but.... thanks
Click to expand...
Click to collapse
That's really weird, on so many levels... :/
Screenshot as proof :laugh:
Warning: Don't install an older OS on top of a newer one, you may have a very high chance of bricking your phone. If you are ready to take risk of bricking for the sake downgrading / requirement or already bricked, then only attempt the following . you need an autoloader & build version exactly matching to your phone.
I have downgraded successfully from Build ABP244 (Android 8.1.0) to AAX862 ( Android 7.1.1)
Caution: Blackberry/Google may introduce any constraints against downgrade through future OTA updates to strengthen the security etc.
My Phone Details:
BlackBerry, Keyone, Special Edition, Dual Sim, India.
PRD: PRD-63764-001 (Group: KEYone BBB100-7)
OS Build: ABP244 (Android 8.1.0)
[Upgrade history from ABB216 (android 7.1.1) to ABG076 (Android 8.1.0 ) ….to…to ABP244(Android 8.1.0 )]
1. I have checked phone PRD, by typing the following code into the phone dialer:
*#2886#
Clicked on "MANU"
Clicked on "Traceability"
There you can see phone's manufacturer no: Mine is PRD-63764-007 (for example) (photo#1 in attachment)
Exited from the menu click "PASS"
Then again clicked "PASS"
At the end of the menu clicked "exit"
2. compared with PRDs master at https://tclota.birth-online.de/ and download suitable Autoloader (ROM and its flasher)
3. AAX862 (it is written as AAX863 but actually AAX862) which is suitable to above PRD No is downloaded from
https://androidfilehost.com/?fid=890129502657599708
Topic: https://forums.crackberry.com/blackberry-keyone-f445/blackberry-keyone-autoloaders-1108372/
4. Removed passwords /patterns / finger prints from screen lock (settings>security>screen lock>select none), Removed google account [ settings>Users & Accounts (or Accounts in case of android 7.1.1 ) >googel>options>Remove, remove google]
[removed find my device at device administrator , find from Google Account (settings> google> google account >options (3 horizontal line at rhs bottom)>manage devices>black berry keyone>remove>remove- i have done but this may not be needed]
Theory: On BlackBerry devices powered by Android, Factory Reset Protection (FRP) is enabled by default to reduce the value of a stolen device. This feature prevents the use of a BlackBerry device powered by Android unless authorized by the known user.
Once you sign in with a Google account, FRP is enabled. Once enabled, only users who have reset their device via Settings > Backup & reset > Factory data reset may proceed through the setup wizard without being prompted to enter the Google login information that was previously used on the device before resetting. This form of reset is the only reset flow that is considered trusted.)
[I have reset the device from Android (I have done, but this may not be needed]
[Enabled Developer options and usb debugging was made on (I have done, but this may not be needed)]
5. Rebooted to fastboot mode by switching off >pressed and held volume down button and simultaneously , pressed power button till the phone restarts , then released volume down, once fastboot loads
[>select fastboot by pressing volume button , I have done, but this may not be needed (no further power button press)]
(photo#2 in attachment)
6. Installed BlackBerry-USBDrivers-5.0.0.2 downloaded from the link below for windows and restarted the windows.
Downloaded from https://swdownloads.blackberry.com/Downloads/entry.do?code=4EE0932F46276313B51570F46266A608
7. Connected it to Windows PC through USB port (Windows device manager photo#3 in attachment)
8. Extracted AAX862Universal.7z with 7z
9. Browsed to the above extracted folder, double clicked on file flashall.bat to run batch file (other option available is flashallnowipe.bat ).
10. Entered y in response to question …….. to continue (y/n), (photo#4 in attachment)
it immediately rebooted to fastboot again (photo#5 in attachment) but the process was going smooth.
Process successfully completed (photo#6 in attachment) and phone is rebooted to OS in Auto
Sometimes, the phone can get stuck when booting for the first time. If this happens to you, make sure you've waited long enough, and then just hold the power button down to force a reboot.
It needs simcard or internet to reach user interface.
Caution:
When Autoloader build no AAY819 (common/universal to many PRDs but not all) downloaded from https://mega.nz/#!wVxBxYZA!BahovAZA_...M5Ic_QkJigS3LI and flashed, flashing is successful but when is updated from App Drawer >updates…22 mb downloaded , install started , rebooted and installed to 100% but message appeared that “ This is embarrassing, the update failed, try to install again later, your phone will reboot after 120 sec…. Error code 3305” , It reboots and build no shows as ABB216 but 2nd Sim is not working.
Reflashed with Build No AAX862, both sims and other hardware are working normal , Further when update option is used it is getting updated to ABB216 without any error again both sims and other hardware are working normal .
Stop updates
(this facility not available in Oreo)
Pre requisite : disconnect phone from Internet (Put off Wifi and mobile data)
1). App drawer>Updates>Options(3 vertical dots)>settings>system> check for updates –Off (=never), Automatically download – off (=ask to download)
2). App drawer>Updates>Options(3 vertical dots)>settings>System applications > Automatically update –off (=never), new app notifications –off
If system update already started or pre -requisite is forgot: Go to Settings>Apps>Updates>Storage>clear data , now repeat step 1 & 2
Advantages:
1) The feel, the look , the smoothness , the speed , low in bugs of the build ABB216. It is excellent
2) “True phone dialer & contacts” app has all most all the features, you ask it has already has, like blue mark for outgoing calls, green for incoming, saffron for canceled, red for missed call as history (it cannot work properly with Oreo latest due to restriction on call log, restrictions increased in ascending order from Build ABG076 to ABJ879 to ABM376 to ABP244 ). Never hangs while calling (OS).It has contact share through SMS with pleasant interface, excellent dual sim management etc.
3) SMS Organizer by Microsoft also appears to be facing restrictions with Android 8.1.1 , hence it will be working excellently.
4) Rear camera (of Build ABB216)a lot nearer to true to actual ( than Oreo Build ABG076)
5) Light Manager works flawless with very low power consumption for customization of notification LED as keyone has no built in facility to customize.
Disadvantages:
1) less secured than Oreo,
2) 7.1.1 Camera not far better than improved camera by build ABP244.
3) Oreo has configurable alarms but same is achieved in Nougat with updating of Time App
4) Oreo has PIP useful e.g. for maps
5) Google playstore installs regular patches without our control making older android slow
6) call history symbols are rarely used and minor , further they can be seen at stock phone (the issue still exist with Oreo compatible TruePhone v1.78) advantage 2 may be considered almost nullified
7) file Explorer scrolling goes back if some shaking taking place.
8) Download is interrupted few times from playstore even when Download from mobile data
9) usb data transfer is slow
10) all features of Silence premium do not disturb app are not working ( my favourite profiles app ) like whitelist and repeat calls will enable ring, interruptions to silence mode (app is defective up to v 2.15f ) but they have created v2.17 which works as designed but does not install on nougat.
11) Light flow can be installed in place of Light Manager on Oreo , hence advantage 5 nullified
However I am happy with downgrade and will maintain as long as possible or till I get apps to get the nougat like flexibility and user experience as per above mentioned facts at advantages.
Thanks to the respective contributors& community. This is only experience sharing , no credit or responsibility.
As the time progressed, disadvantages increased and advantages reduced . I have re-upgraded please on 22.12.19 especially due to functional requirement of Silence Premium as mentioned above and no equivalent is available.
@knreddy, good work, please do you know if this exact firmware will work on the sprint variant of the keyone?