Related
Z1 (brand unknown) is wrist watch phone with Android OS. It was first released in 4/2012 and it is Android 2.2.1. It has WiFi, AGPS, GSM/EDGE, 2 MP camera, mic, speaker, loudspeaker, capacitive touchscreen, display of 320x240, SDHC & SIM card slots etc.
As most Chinese phones it has SoC from MediaTek, MT6516 (armv5).
See my Czech review for photos: http://hodinky.blog.mobilmania.cz/2012/06/z1-hodinko-telefon-s-androidem/
Tweaks/tips for stock ROM (2.2.1)
Market/Google Play is missing in stock rom but it cam be added if you follow instructions on the page: http://www.ibuygou.com/p-z1_smart_android_2_2_watch_phone_gps_wifi_bluetooth_html-3638-usd.html (included in Clean ROM)
Default DPI is 120 however most controls are too small. Change it to 160 which will make all icons sharp. (included in Clean ROM)
Typing on tiny QWERTY soft keyboard is a pain, Flit Keyboard makes entering text much easier. (included in Clean ROM)
To enter engineering mode, dial *#*#8787#*#*
ADWLauncher EX works even better if you (see):
Disable all animations including scrolling homescreen
Disable dockbar and use swipe up instead (included in Clean ROM)
4x3 icon layout for home screen and 5x2 for drawer (included in Clean ROM)
Use something like Extended controls for toggles
Use No Lock if you don't need swipe to unlock feature.
Remove alternative Chinese markets and Chinese network account/sync providers from /system/app (included in Clean ROM)
Creating flashable dump
Use MT6516 BackUpTool for dumping your stock rom.
Use MTK_Rom_Studio_1.0.0a for converting dump into flashable format.
Flashing
Basically you need the driver: "MT6516_YuSu_USB_VCOM.inf" and flashing tool: "SP Flash Tool v1.1110". All tools can be found on the internet when searching for "MT6516 flash tools". The only necessary tools reuploaded can be found also here. (I'm not sure about the legality of these tools though.)
You have to use 32 bit Windows (I only tried XP in both VirtualBox and VMware but it could work with 32 bit Vista or 7).
Power off the watch, connect it directly to PC (no USB hub or extention cable) - new device will connect for few seconds - use it to install the driver. Unplug watch. (You may retry that few times because the watch disconnect within few seconds) Open flashing tool and select files to flash (I would recommend not to flash anything other than boot/recovery/system/data/logo), hit start and quickly connect the watch - flashing will start automatically.
Recovery
First build of ClockworkMod 5.0.2.8 seems to be working however all its features were not tested yet!
Recovery can be flashed with "SP Flash Tool" (use provided scatter file).
Rebooting to recovery from launched Android using "reboot recovery" works but I wasn't able to find working button shortcut to launch recovery directly from cold start. Please help me if you find a way!
Custom Clean ROM based on stock 2.2.1
Features
Removed alternative Chinese markets and Chinese (social) network accounts
Integration of Google apps (sync, Google Play, setup wizard etc)
DPI changed to 160 which makes the watch easier to control and the icons sharper
Preconfigured ADW Launcher, Flit keyboard
Includes root with Superuser, Busybox binaries
Minor clean-ups
So far this ROM doesn't include anything power user from XDA wouldn't be able to customize but this ROM is afford to save other users time with experiments.
Important notes:
Backing up your current ROM + data is highly recommended (use the above listed MT6516 BackUpTool)
The seller says you shouldn't do factory reset because of IMEI lost - I can't confirmed that - IMEI is kept even during factory resets so it doesn't seem to be stored in user data partition. BUT backup your current ROM anyway cause I might be wrong.
Clean ROM notes:
The first boot is slow. After the first boot, I recommend not touching the watch for 5-10 minutes because dalvik cache is rebuilding in the background and the setup wizard may lag a lot.
The default ADW launcher is configured to not have app drawer button - swipe up to open drawer
Known issue (to be fixed later): Because of DPI change - Bottom row of button in Dialer is smaller, however all buttons can be pressed
Known issue (to be fixed later): Because of DPI change - Superuser (root) confirmation dialog buttons aren't readable however the buttons are partly visible and can be pressed (press bottom left button to allow root acces)
Known issue (to be fixed later): Because of DPI change - There is small graphical glitch on the lock screen which however doesn't break anything
Flashing recovery is not needed at all. Just make sure you flash both partitions (it will erase all your data on the watch but not on SD). Follow instructions above on how to flash.
ROM download: http://www.multiupload.nl/3LHJ33CW95
or http://www.multiupload.nl/JK6NOATJ57
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CM ROM
WIP, first build of CyanogenMod 7 (2.3.7) booted so I continue testing/evaluating. So far I only used stock kernel but I have source for MT6516 kernel.
Notes: WiFi chip - MediaTek MT5921 - no open source driver
Currently on hold.
Proofs
Flit Keyboard
moneytoo said:
Typing on tiny QWERTY soft keyboard is a pain, Flit Keyboard makes entering text much easier.
Click to expand...
Click to collapse
I actually have bought 3 Z1's and virtual keyboard is REALLY a pain..
Flit Keyboard makes entering text much easier ! !
Just Eight ( 8 ) >> Huge << Buttons Keyboard..
..that By Easily Sliding You Can Type:
>> All << Alphanumeric Characters And Symbols ! !
No More Accidentally Typing Wrong Characters ! !
Perfect 5..
(this Should Have Been THE Number One Android Keyboard..)
Thanks moneytoo ! !
ff
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
Z1 Android Watch-Phone
From Wikipedia, the free encyclopedia:
http://en.wikipedia.org/wiki/Z1_Android_Watch-Phone
ff
Ive been thinking about buying the watch to use as a mp3 player, would you recomend it?
Sent from my NWZ-Z1000Series using xda app-developers app
Yes, I'm plugging my website, but hey, it's relevant.
I've just reviewed this device at:
http://linuxslate.com/Review_Z1_Android-2.2-Watch.html
Everything in this thread has been helpful, I just wanted to add my 2 cents.
DPI at 160 looks great. Unfortunately many apps will not fit, including keyboard, phone, and superuser prompt. Either find alternate keyboard and set superuser to auto-grant, or switch back and forth between 120 and 160 as necessary.
I like No Lock, but I find the phone wake-locking all the time until I turned No Lock off. I also like the fact that the time is there in big letters on the lock screen. It's very suitable for its watch functionality.
I did a manual backup without rooting (No need for Z4 Root)
Download and unrar MT6516 BackUpTool, but do not install anything.
On the Linux/Mac box, open the gscript folder, and open back22.sh in editor, or viewer.
Connect the watch via USB, and connect via adb shell
Cut, paste and execute each line from the back22.sh file
up to and including the last dd command in the first section - in other words
Code:
.
.
.
.
dd if=/dev/mtd/mtd11 of=/sdcard/backup_/expdb.img
Obviously, you don't do the comment lines.
exit the shell
Code:
exit
do:
Code:
adb remount
Install yaffs2image:
Code:
adb push <your_path_on_PC_to>/Install/BackUp/yaffs_back_2.2/gen/mkyaffs2image /system/bin/mkyaffs2image
Code:
adb shell chmod 4777 /system/bin/mkyaffs2image
(Again, the above is a cut and paste from the script)
Code:
adb remount
(for safety)
Code:
adb shell
Then cut and paste the remaining 3 mkyaffs2img commands.
Then:
Code:
exit
Copy the backup_ folder on the SD car to someplace safe.
If you want, you can remove mkyaffsimg:
Code:
adb remount
Code:
adb shell rm /system/bin/mkyaffs2image
Code:
adb remount
It's definitely more steps, but it leaves the system technically un-touched, un-rooted, and even returnable if you should have to.
Some more useful apps.
https://play.google.com/store/apps/details?id=com.coinsoft.android.orientcontrol
Orientation control to lock the screen in landscape mode; not free but worth it.
https://play.google.com/store/apps/details?id=itosisato.setsunasato.kokoroduyosato
Home button for soft home button in notification tray. Free.
https://play.google.com/store/apps/details?id=com.katecca.screenofflock
Off button in notification tray. Free.
https://play.google.com/store/apps/details?id=com.opera.mini.android
Opera mini has server side compression so makes best use of the slow 3g speed, but no multitouch so zooming is difficult.
m34n1ng said:
Ive been thinking about buying the watch to use as a mp3 player, would you recomend it?
Sent from my NWZ-Z1000Series using xda app-developers app
Click to expand...
Click to collapse
It can be done, but the MotoActv might be better, because the motoactv has a headphone jack so you can use any headphones you want. On the Z1, you have to use bluetooth headphones or a bluetooth headphone adapter.
I just ordered one of these last week, should have arrived today ... glad to see this exists!
Other than configuration/display-size issues, does everything work, i.e. all hardware? I noticed you had a note about the Wifi driver not being open source, but I assume that more effects if you try the MT6516 kernel. Even if it's a closed binary, I assume you could still load it and use it though. I'm not expecting any leaps and bounds in the kernel department.
As for CWM, is any part of it executed at cold boot? If so, I imagine you'd need to implement some kind of timeout menu that could optionally enter recovery before booting the watch. This is similar to what was implemented on the Kindle Fire which also doesn't have a normal stock recovery mode.
I assume you're still evaluating CM7 so you're not ready to distribute it ... but I do hope to see more from you soon, especially a HOWTO and download links!
I spent many nights trying to make GSM or WiFi working. Except few tweaks I only got the modem to start but nothing more. I have no experience with porting of binary drivers and this device has so many of them. Radio/modem and kernel modules - there are no problems with them but there are just too many dependencies on proprietary libs even from standard android native binaries.
So I'm giving up. At least for now cause I just don't have enough knowledge.
I consider making custom rom based on stock Android but I don't know if there would be any demand. Proper integration of Google apps, Chinese apps/account providers removed, tweaked launcher/drawer settings, tweaked global dpi/dpi of apps that not fit...
To have at least something, I give you very simple app "Z1 Backlight Toggle" apk (attached in 1st post) which can turn off completely display backlight. (Needs root) I use it on my bike when I have navigation running all the time cause it indeed saves battery and backlight isn't needed at all under direct sunlight, the display is readable the same.
moneytoo said:
I spent many nights trying to make GSM or WiFi working. Except few tweaks I only got the modem to start but nothing more. I have no experience with porting of binary drivers and this device has so many of them. Radio/modem and kernel modules - there are no problems with them but there are just too many dependencies on proprietary libs even from standard android native binaries.
So I'm giving up. At least for now cause I just don't have enough knowledge.
Click to expand...
Click to collapse
That's fine, I understand how frustrating these things can be. But still, can you post information about how to backup / restore the firmware and how to flash a custom ROM? I might try playing with it myself sometime and at least having the knowledge would enable further experimentation.
WTF!!!! a wrist phone with Android OS.... This is so freaking cool!!! :thumbup:
Awesome......
Sent from my GT-S7500 using xda premium
moneytoo said:
I spent many nights trying to make GSM or WiFi working. Except few tweaks I only got the modem to start but nothing more. I have no experience with porting of binary drivers and this device has so many of them. Radio/modem and kernel modules - there are no problems with them but there are just too many dependencies on proprietary libs even from standard android native binaries.
So I'm giving up. At least for now cause I just don't have enough knowledge.
Click to expand...
Click to collapse
I have an idea ... if we can get the MTK6516 kernel to build and boot, that's one step. If we can then get Android 2.2 stock to build, and then compare it against an image of the Z1's file system, we should, in theory, be able to identify all the unique areas of the watch's Android setup. If we at least know how to build an identical watch Android from source we should be able to extend that into making Cyanogen Mod work ... or something else. I think it's worth a shot anyway!
Also for an identical kernel, there shouldn't be any need to "port" binary drivers ... ideally they're built-in or load as modules, same as any other drivers.
I consider making custom rom based on stock Android but I don't know if there would be any demand.
Click to expand...
Click to collapse
You're probably right there will be very limited demand. So I ask again, if you can at least post steps about reflashing the watch, I'll give it my best shot. I just want to be sure I can restore the watch after messing around with it. Which I'm guessing you were able to since you didn't claim any permanent damage. It seems it should be able to go into a factory restore mode which I hope will override any messed up systems.
lokeshsaini94 said:
WTF!!!! a wrist phone with Android OS.... This is so freaking cool!!! :thumbup:
Awesome......
Click to expand...
Click to collapse
It really is neat. Kind of limited, but really neat. I think if we can get any amount of control over the kernel and Android version, we can really extend the abilities of the watch. It just needs a chance...
southbird said:
I have an idea ... if we can get the MTK6516 kernel to build and boot, that's one step. If we can then get Android 2.2 stock to build, and then compare it against an image of the Z1's file system, we should, in theory, be able to identify all the unique areas of the watch's Android setup. If we at least know how to build an identical watch Android from source we should be able to extend that into making Cyanogen Mod work ... or something else. I think it's worth a shot anyway!
Also for an identical kernel, there shouldn't be any need to "port" binary drivers ... ideally they're built-in or load as modules, same as any other drivers.
Click to expand...
Click to collapse
In my opinion there's no problem with kernel, modules or libraries, we can just reuse them. The real issue I think is native android binaries such as wpa_supplicant or rild. We can either use (original) already built binaries or build new ones - but this is the problem... Original binaries depend on proprietary libraries so they "do something" important with devices. Newly build binaries just don't have that unknown functionality. Yes, reusing stock binaries might work for 2.2 but my only target so far was 2.3 since that would be real benefit for us.
southbird said:
So I ask again, if you can at least post steps about reflashing the watch, I'll give it my best shot.
Click to expand...
Click to collapse
Have a look here: http://bm-smartphone-reviews.blogspot.cz/2011/02/mtk-hd2-hd9-flashing-tutorial.html
Basically you need the driver: "MT6516_YuSu_USB_VCOM.inf" and flashing tool: "SP Flash Tool v1.1110". You have to use 32 bit Windows (I only tried XP in both VirtualBox and VMware but it could work with 32 bit Vista or 7 as well).
Power off the watch, connect it directly to PC (no USB hub or extention cable) - new device will connect for few seconds - use it to install the driver. Unplug watch. Open flashing tool and select files to flash (I would recommend not to flash anything other than boot/recovery/system/data/logo), hit start and quickly connect the watch - flashing will start automatically.
moneytoo said:
To have at least something, I give you very simple app "Z1 Backlight Toggle" apk (attached in 1st post) which can turn off completely display backlight. (Needs root) I use it on my bike when I have navigation running all the time cause it indeed saves battery and backlight isn't needed at all under direct sunlight, the display is readable the same.
Click to expand...
Click to collapse
Which navigation software are you using?
adthor said:
Which navigation software are you using?
Click to expand...
Click to collapse
No idea what he's using, but I'll say that Sygic worked when NOT navigating (doing a route caused it to force close, I'm guessing possibly out of memory??) Using OsmAnd works pretty well ... of course, it's Open Street Map with all the usual limitations.
adthor said:
Which navigation software are you using?
Click to expand...
Click to collapse
I use RMaps (https://play.google.com/store/apps/details?id=com.robert.maps&hl=en) with collection of offline maps and prepared tracks for navigation.
southbird said:
No idea what he's using,
but I'll say that Sygic worked when NOT navigating
(doing a route caused it to force close, I'm guessing possibly out of memory??)
Using OsmAnd works pretty well ... of course, it's Open Street Map
with all the usual limitations.
Click to expand...
Click to collapse
Sygic 10 works nice with Z1 using 3D maps.
Sygic 12 works nice with Z1 using 2D maps.
When attempting to navigate Sygic 12 with 3D maps enabled,
the Sygic 12 crashes and Z1 returns to Home screen.
Correction..
Sygic 12 works nice with Z1 using 3D maps
only when Autozoom is turned off:
Settings > Map > Autozoom [untick]
ff
I consider making custom rom based on stock Android but I don't know if there would be any demand. Proper integration of Google apps, Chinese apps/account providers removed, tweaked launcher/drawer settings, tweaked global dpi/dpi of apps that not fit...
Click to expand...
Click to collapse
That is exactly what needs to be done! If porting the binaries is not possible at the moment, why not go ahead with building with stock android, with proper google account and apps, and removing the chinese accounts.
Once you have tweaked launcher/drawer, tweaked dpi of apps that not fit etc done, it would be almost as good as running CM7. Any improvement would be a big improvement
I sincerely hope that you continue development, the demand for a stock ROM is sure to come as the device becomes more popular, as of now, there is nobody developing for Z1, that i know of.
apurvasrishti said:
That is exactly what needs to be done! If porting the binaries is not possible at the moment, why not go ahead with building with stock android, with proper google account and apps, and removing the chinese accounts.
Once you have tweaked launcher/drawer, tweaked dpi of apps that not fit etc done, it would be almost as good as running CM7. Any improvement would be a big improvement
I sincerely hope that you continue development, the demand for a stock ROM is sure to come as the device becomes more popular, as of now, there is nobody developing for Z1, that i know of.
Click to expand...
Click to collapse
I started cooking custom ROM based on the stock two days ago and I'm very happy with it. Proper integration of setup wizard, google apps, keyboard, dpi, orientation, better preconfigured launcher, working voice search etc.
While this guide does still work, I'd highly recommend you check out the Fire Toolbox! The Toolbox is not only capable of removing the lockscreen ads, but it's also capable of installing custom launchers, custom keyboards, Play Services, and so much more! We hope to see you there!
Click to expand...
Click to collapse
To start off I just want to let you all know that the second you are done completing the steps in this tutorial you will be the happy owner of a clean lockscreen without cluttered ads. In my previous post, I shared a method with you that momentarily removed the ads from your lockscreen without a PC. Today, I'm going to perfect my previous method and can say upfront that this method does indeed REMOVE LOCKSCREEN ADS PERMANENTLY! Don't believe me? Try the method for yourself and let me know if it worked for you or not. So, without further ado... let's get started with the tutorial.
Video Tutorial:
Useful Links:
» How to install Google Play Services on Fire Tablets:
→ [url]https://goo.gl/oGV6P5[/URL]
» How to download and install ADB onto your PC:
→ [url]https://goo.gl/prH9PQ[/URL]
Text Tutorial:
To remove the ads all you will need is:
Fire Tablet
USB Cable
USB Debugging enabled
A computer with ADB installed
1. First things first you will need to download Automate by LlamaLab on the Play Store:
[url]https://play.google.com/store/apps/details?id=com.llamalab.automate&hl=en_US[/URL]
2. Once the app is installed go ahead and open it. On the dialog box that appears tap "Accept" then "OK" then finally "OK" once more. In the corner of the app look for the hamburger menu icon and tap on it. Next, from the menu that appears select "Settings" Next, you will need to click on the "Privileges" section.
Locate the following privileges:
Code:
access photos, media, and files on your device
Code:
modify system settings
Code:
modify private settings
Tap on it and wait for the installation prompt to appear. When it finally does please install it (you will need to install all three privileges above for the script to work correctly). Now make sure the boxes for the privileges are ticked before moving on to the next step. Once the boxes are ticked press the back button.
3. Still in the settings for Automate scroll down till you find:
Code:
Run on system startup
Once you find it tap on it and select "Enable" from the new dialog box that appears. Doing this allows the script to run at startup when the system boots effectively blocking the ads on the lockscreen
4. Next you will need to enable USB debugging.
Swipe down on the top of the screen until the quick settings and notification drawer pops down. Next, tap on the gear icon to be taken to the Settings app for your tablet. In the settings app look for "Device Options" now scroll down and look for the "Serial Number" and tap on it 3 times. You should see a new entry "Developer Options" underneath "Serial Number". *Tap on it and scroll down till you find "Enable ADB" tap on it and on the new dialog box that appears hit "Enable" once more. That's it ADB has been successfully enabled.
*If you are attempting to do this tutorial on a Fire HD 10 (2018) model please note that in the Developer Options you will be looking for "USB Debugging" instead of "Enable ADB". This is because Google changed the name of the setting to USB Debugging starting on Android 6.0 and up. So, to enable ADB just tap on the option titled "USB Debugging" and enable it. You are now ready to proceed with the tutorial. From here on out you shouldn't have to do anything else different.
5. Once USB debugging is enabled plug your tablet into your PC.
Now you will need to open a Command Prompt (Windows) or a Terminal (Linux) session with ADB installed (If you don't have ADB on your PC please visit this forum).
Now type the following commands EXACTLY as they appear on screen:
Code:
adb devices
Note: Please make sure you're tablet's serial number appears underneath "List of devices attached" If done correctly you should see:
Code:
C:\Users\(You're username here)>
List of devices attached:
xxxxxxxxxxxxxxxx device
Once you see your serial (the x's being replaced by you're serial number) and next to it, it reads "device" you are ready to move on to the next step. Once ready type the commands below (feel free to copy and paste):
Code:
adb shell pm grant com.llamalab.automate android.permission.WRITE_SECURE_SETTINGS
Code:
adb shell pm grant com.llamalab.automate android.permission.CHANGE_CONFIGURATION
Code:
adb shell pm grant com.llamalab.automate android.permission.SET_PROCESS_LIMIT
(Special thanks to XDA member @Toxicshadow for their assistance with removing the missing superuser notification).
Now, press ENTER. If nothing follows the command then it has been executed successfully and the permissions have been properly given to Automate. As illustrated in the picture below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: If anything follows the command it means it didn't go through. Please retype or recopy the command above and make sure there are no spaces included. The command is very sensitive.
6. Remove your tablet from your PC and once more open the Automate app. Now click the "More Flows..." option. Next, click on "Start". Go ahead and install the community flow add on.
7. In the right-hand corner, you will see a magnifying glass icon, click on it and type in the field "Amazon" and hit enter. Look for "Amazon Lockscreen Ads Remover V4.5 (ADB Required)" flow. Tap on it and wait for the page to load. Proceed to download it to Automate. If you have a hard time finding it in the community flows I've uploaded the script to Google Drive which you can download and import into Automate.
8. Return to the home screen for Automate. You should see the flow you just downloaded. Click on the "Amazon Lockscreen Ads Remover V4.5 (ADB Required)". With the proper permissions given and the installation of the script we are finally ready to KILL those pesky ads once and for all... with confidence, you can now tap on the "Start" button to run the script and finish the removal process.
Congratulations you have now removed all the ads from your tablet's lockscreen. You do NOT NEED TO REBOOT! Just lock the screen and enjoy the wonderful sight of your new ad-free lockscreen!
Before:
After:
The Explanation:
For my little brothers birthday, I bought him an Amazon Fire Tablet HD8 (7th Generation) which he began to jump for joy at the sight of. We got it all set up and everything was going smoothly that is until the lockscreen ads showed up! Looking up a tutorial here on XDA I came across a tutorial on how to remove the ads just by running a command through ADB and to my surprise it actually WORKED! But, it wasn't long before Amazon pushed out an update to the tablets that prevented the Offers app from being removed through ADB. My brother being used to having no ads on the lockscreen came to me and begged me to remove them. Unfortunately, none of the other methods I tried worked. Then it all came down to calling up Amazon and asking them to remove the ads with a chance I could be paying $15. So, I decided to see if I could figure out a method on my own that would work. Then one night I decided to check Android's settings database to see if I could find a resolution, I opened up the settings.db file using Settings Database Editor and begin to look through the database to see if Amazon was hiding any strings governing the lockscreen ads and much to my surprise I found the string I was looking for "LOCKSCREEN_AD_ENABLED" set with a value of "1" meaning it was enabled. By changing the value of the string from "1" to "0" I was able to remove the lockscreen ads. I threw my fist up in the air and began to celebrate my victory till the next day when my brother yet again complained about the ads returning. Opening up the database once again the value was changed back to "1". Then another thought hit me, what if I used an automated app to perform the actions of changing the values for me, and with a quick search on Google Play I found exactly what I was looking for: Automate. So, I began creating the flow and testing it to see if it worked... and it did. I gave it a few days with the script running and with hope I turned on the screen to the tablet and once again celebrated over my victory, knowing this time I had done it. Publishing the flow to the community, I wrote up this tutorial and filmed a video on the method with the hopes that others would be able to experience the same feeling I felt the moment I removed the ads for good. So, that's it... that's how I figured out how to remove the ads for good!
Latest Script Version:
Amazon Lockscreen Ads Remover V4.5
Build: January 11, 2019 @ 1:30 PM
Older Versions:
Respiratory
Changelog:
Version 4.5
*Support for "Amazon Lockscreen Ads Remover Updater (Add-On)" has been dropped.
*Support has been dropped because there aren't any planned updates, and it's just causing more issues than anything.
Version 4.0
Fixed an issue where an extra fiber would start when hiding the Service Notification.
*Disabled parallel launch to prevent the script from running multiple instances of itself.
Various bug fixes and improved performance/stability.
*Special thanks to XDA member @asdiidjisjd23, and Sabrina Wortmann for bringing the multiple instances bug to my attention, and giving advice on how to fix it. Thank you both so much!!
Version 3.0
*Fixed a startup bug that caused the script to function improperly.
You can now hide the Persistent Service Notification.
New downloadable add-on for auto-updating script.
Optimized performance of adblocker.
Various bug fixes and improved performance/stability.
* Special thanks to XDA member @andyk88 and Automate developer @Henrik Lindqvist for assisting me in fixing the startup bug! Thank you both so much!
Version 2.0:
Improved performance and stability.
* Fixed logging, and battery draining issues.
Squashed a few bugs.
* Special thanks to XDA member @jdmegkoupe for his/hers amazing help by fixing the script and preventing it from running continuously, improving battery life, and reducing logs. Thanks so much!
If you like my work and would like to support me feel free to Donate. Thank you.
Click to expand...
Click to collapse
Sounds legit. Great find. Is the solution permanent?
Sent from my Moto E4 using XDA Labs
DragonFire1024 said:
Sounds legit. Great find. Is the solution permanent?
Sent from my Moto E4 using XDA Labs
Click to expand...
Click to collapse
Yes! The ads WILL NOT come back unless of course you stop the Automate script that blocks the Ads!
excellent work. managed to pick the 8 up yesterday, not realising I couldn't do a lot with it, unlike my previous tablets. Getting rid of the ads for free was a good start.
projectsome said:
excellent work. managed to pick the 8 up yesterday, not realising I couldn't do a lot with it, unlike my previous tablets. Getting rid of the ads for free was a good start.
Click to expand...
Click to collapse
Excellent! Glad I could help you out! :victory:
Got it figured out on my 10 by using adb 1.3, but there are problems on my wife's 10.
When I try it for my wife's 10 I get the extra junk on the command prompt when I try to insert the code I copied.
You did not say what to do if you get the extra junk.
Would you help me please?
Thanks
TrofeoSC said:
Got it figured out on my 10 by using adb 1.3, but there are problems on my wife's 10.
When I try it for my wife's 10 I get the extra junk on the command prompt when I try to insert the code I copied.
You did not say what to do if you get the extra junk.
Would you help me please?
Thanks
Click to expand...
Click to collapse
Hi Trofeo5C,
You will get the extra junk after the command if the command wasn't typed or copied correctly. Please try and recopy the command and make sure you aren't copying ANY spaces. If you need further help you can watch the video tutorial (goto 8:30) at the top of this forum or you can reply to this comment and I will be happy to assist you further! Good luck!
Looks like the script runs continuously and drains the battery. Log file size is on the GB level.
rwalle said:
Looks like the script runs continuously and drains the battery. Log file size is on the GB level.
Click to expand...
Click to collapse
I'm currently working on fixing the script so it only runs when Android changes the LOCKSCREEN_AD_ENABLED value to 1 so it doesn't need to continuously run. The updated script will not run all the time. Also, the logging can be turned off, please visit step 8 and read through it. It will show you how to turn the log off.
Why so much trouble?
I found simply disabling the kindle special offer will do.
Must be rooted already.
adb shell
su
pm disable com.amazon.kindle.kso
Then change
LOCKSCREEN_AD_ENABLED
to 0.
weiqj said:
Why so much trouble?
I found simply disabling the kindle special offer will do.
Must be rooted already.
adb shell
su
pm disable com.amazon.kindle.kso
Then change
LOCKSCREEN_AD_ENABLED
to 0.
Click to expand...
Click to collapse
Yeah that's the issue. Root as far as I'm concerned isn't available on Fire HD8 Tablets (I could be wrong it's been awhile since checked.) but this tutorial is mainly for those who don't want to root their tablets and for those that can't obtain root.
ad block version 2
i have altered the flow to proceed when the setting has changed, which results in significantly less logging and better battery life "the infinite loop from the original version prevented deep sleep"
see attachment.
jdmegkoupe said:
i have altered the flow to proceed when the setting has changed, which results in significantly less logging and better battery life "the infinite loop from the original version prevented deep sleep"
see attachment.
Click to expand...
Click to collapse
Ah, I see you beat me to it. Thank you so much for fixing the script! I will post the new script to Automate and Google Drive and credit you for you're amazing help. Thanks so much!
No problem
It seems I would need to run the "adb shell pm grant" command again after power off and on, otherwise it does work. Thanks for any suggestions!
Update: https://forum.xda-developers.com/showpost.php?p=76887225&postcount=33
andyk88 said:
It seems I would need to run the "adb shell pm grant" command again after power off and on, otherwise it does work. Thanks for any suggestions!
Click to expand...
Click to collapse
Hmm very interesting ?
Once you run the adb command and it goes through it should be the last time you need to do it. Are you clearing the cache for the superuser addon?
Monkeybomb365 said:
Hmm very interesting ?
Once you run the adb command and it goes through it should be the last time you need to do it. Are you clearing the cache for the superuser addon?
Click to expand...
Click to collapse
Thank you for your response.
I didn't clear any cache. I think followed your detailed instructions exactly, except I used "Minimal ADB and Fastboot" (I didn't think it would make a difference).
Update: https://forum.xda-developers.com/showpost.php?p=76887225&postcount=33
andyk88 said:
Thank you for your response.
I didn't clear any cache. I think followed your detailed instructions exactly, except I used "Minimal ADB and Fastboot" (I didn't think it would make a difference).
Click to expand...
Click to collapse
Oh I see. Can I have you remove Minimal Adb and Fastboot (adb minimal sometimes causes errors) and install stock Adb using the link under the video tutorial in my first post. Once, installed can you try running the command in abd and reboot? Please let me know how it goes. Thanks! :fingers-crossed:
I did as the Video shows and after turn off and turn on the automation failed to grand permision any idea why dont work after turn on back. I used the adb from the video and no problems. Just is not working after restart.
danilo4033 said:
I did as the Video shows and after turn off and turn on the automation failed to grand permision any idea why dont work after turn on back. I used the adb from the video and no problems. Just is not working after restart.
Click to expand...
Click to collapse
OK. Let's see what we can do to fix it. Can you please confirm that you've enabled start on boot in Automate's settings (setting > Start on boot)
Hey guys!
First, my apologies if I am in the wrong section posting. I was not sure where to post. Please move my thread if needed. Thanks!
Second, would someone recommend and/or suggest Android 9 over Android 10 or Android 10 over Android 9? For myself, I really do not like Android 10. When I am referring to Android 10 and I am referring to the original in September and the two updates in September where that last update has a C3 in part of the name, as well as the October Android 10 update. I just do not like any of the updates. Would I be better off going back to Android 9? It is not an issue because I can flash the factory images via ADB when the phone is powered on than Fastboot once the phone is in the flashing mode
Can you explain why you do not like the update?
I personally don't find that there is a lot of difference between 9 and 10, but offcourse 10 has the latest security updates, which might be a reason for you to stay with 10.
Personally I think the biggest noticeable difference between 9 and 10 is the gesture based navigation. However you can turn the Android 9 style navigation back on if you so desire (Settings/System/Gestures/2-button navigation) or even the older 3 button navigation.
Other changes - like dark mode - are also optional. I see little reason to stay on Android 9. Especially since it is not being updated with security updates.
It would be nice if we could continue to use a preferred version but that comes with considerable security risks. If your dislike is purely asthetics, you can try other launchers.
For the sake of security I'll stick with Q10 for now. I have yet to succeed with a direct OTA update even under full stock. If the pending November OTA updates without needing to sideload, I might then install Magisk.
Cool I w up - Micr
alliance1975 said:
For the sake of security I'll stick with Q10 for now. I have yet to succeed with a direct OTA update even under full stock. If the pending November OTA updates without needing to sideload, I might then install Magisk.
Click to expand...
Click to collapse
The majority of pushback comes from people USED to Android 9/Pie. I get it; I really do - when folks get comfortable, change scares the bejeebers outta them. Because I never ran Pie before the Pixel 3a came along (and Android 10 was halfway through its beta when the 3a arrived) I was able to go from 8/Oreo to 10 pretty much directly with only one migration issue; the gesture support. Simply not using them (even with Gboard) was an option, however - and one I adopted.
Launchers - Pixel Launcher was one I was already familiar with (from my Android 6 and 7 days); returning to it was therefore rather a relief.
The even bigger surprise is that I'm not rooted - or using a non-stock recovery; the first time I've done that on a smartphone (or any Android device since Android 5). TWRP was a certain install on a smartphone (as certain as doing tax returns every year); now - I could, in fact, care less. I follow TWRP development (and Magisk development as well); however, it's more a case of looking for a reason to install either - so far, nothing in Android 10 has given me a reason to move away from dead-stock. (Basically, it's a NEW sort of comfort - dead stock - for the first time in my Android phone history - IS actually good enough to run un-stepped-on.)
Dark mode requires neither; it's an option in Settings. Same with VoLTE/VoWiFi. Basically, so much for Magisk.
The thing is, you have to be comfortable with dead-stock; being as this is, after all, a developer/tweaker-targeting community, how many folks are actually comfortable running dead-stock?
If you CAN get comfortable running dead-stock, Android 10 on your 3a or 3a XL (or any Pixel, for that matter) makes a ton of sense.
Follow up - Due to Microsoft Launcher changing it's code base, I installed the beta on my Pixel 3a, replacing Pixel Launched as default. Due to new features, Pixel Launcher is in trouble! It is not the support for Dark Mode, third party launchers either have or are adding it. It is being able to use apps as plug ins; two I use now are Word (expected) and Google Calendar (unexpected). How many third party launchers let you use a system app - even Calendar - as a plug in directly. While Outlook for Android does, it is still nice to have Launcher do so as well. This very post is another example - I have added the XDA app as a plug in. Depending on how often you use an app, using it as a plug in May be faster than as a shortcut.
Im a new pixel user, i come from Nokia 7 plus (Android 9 - android one program, almost the same as pixel) and simply cant go back to 9...
Im glad my nokia also updated to 10 today , i really like the gestures. And i have been on 9 for 1 1/2 year now...
Nova launcher, gestures work fine on android 10, dark mode is not everywhere but its coming....
PGHammer said:
The majority of pushback comes from people USED to Android 9/Pie. I get it; I really do - when folks get comfortable, change scares the bejeebers outta them. Because I never ran Pie before the Pixel 3a came along (and Android 10 was halfway through its beta when the 3a arrived) I was able to go from 8/Oreo to 10 pretty much directly with only one migration issue; the gesture support. Simply not using them (even with Gboard) was an option, however - and one I adopted.
Launchers - Pixel Launcher was one I was already familiar with (from my Android 6 and 7 days); returning to it was therefore rather a relief.
The even bigger surprise is that I'm not rooted - or using a non-stock recovery; the first time I've done that on a smartphone (or any Android device since Android 5). TWRP was a certain install on a smartphone (as certain as doing tax returns every year); now - I could, in fact, care less. I follow TWRP development (and Magisk development as well); however, it's more a case of looking for a reason to install either - so far, nothing in Android 10 has given me a reason to move away from dead-stock. (Basically, it's a NEW sort of comfort - dead stock - for the first time in my Android phone history - IS actually good enough to run un-stepped-on.)
Dark mode requires neither; it's an option in Settings. Same with VoLTE/VoWiFi. Basically, so much for Magisk.
The thing is, you have to be comfortable with dead-stock; being as this is, after all, a developer/tweaker-targeting community, how many folks are actually comfortable running dead-stock?
If you CAN get comfortable running dead-stock, Android 10 on your 3a or 3a XL (or any Pixel, for that matter) makes a ton of sense.
Click to expand...
Click to collapse
I don't know that I had to, but I sideloaded the December update. However, the January update downloaded and installed w/o problem. I have had time to get used to full Q10 stock and it does many nice things. I don't think I'll do root until major changes happen.
Despite numerous requests for adding a forum for Redmi Note 11 4G(spes) device, this website has continuously ignored the requests for the same stating "not much discussed", "not much user interest", etc.
So, please vote it out here for one last time to show how much of a user base need a forum for Redmi Note 11 4G(spes)
Okay, 9 votes till now and all say "YES" a forum is needed.
Now, how does one decide how many votes needed to open a forum?!
ajaynumb said:
Okay, 9 votes till now and all say "YES" a forum is needed.
Now, how does one decide how many votes needed to open a forum?!
Click to expand...
Click to collapse
So, nine votes from 11+ million XDA accounts. At least in my (democratic) country such a poll or party wouldn't make it into the smallest community parliament but I can ensure you that such a democratic petition would be at least filed by the administration. And even if I relax that to probably 15,000 - 20,000 members seen on XDA today (I didn't check the exact number) it wouldn't void my statement.
However, we might have another issue here: XDA-Developers is NOT a democracy but a privately owned website that is run by the guidances, policies and intentions of its owners and who have implemented the XDA constitution, the so-called XDA Forum Rules!
Personally I've no insight into the conditions when the admistrators create specific device fora in closest coordination with the site owners but my XDA search shows me that obviously never a development related thread for your subject device or just tutoriaks have been created although fora for this respect are available:
Miscellaneous Android Development
For ROMs, kernels, tools and scripts only (devices that do not have a forum on XDA)
forum.xda-developers.com
Android General
Android root tutorials, one-click root tools, ROMs and other Android modifications can be found in this forum for devices without a dedicated device forum
forum.xda-developers.com
Despite the lack of development threads for your device, there's certainly another chance to get a forum for it. I suggest to get in contact with your OEM and to convince them to a respective cooperation with XDA.
My esteemed team mate @TNSMANI has already closed one of your duplicate threads. Although commisioned by the above linked forum constitution (or rules) I've so far refrained from a deletion of your repeating duplicate or your demanding posts. Allow me to suggest that you review the XDA constitution, which you agreed to adhere to when you registered about 3 1/2 years ago, with special emphasis on article 2.3 and article 5. Thanks for your cooperation!
Pending on how this event continues I reserve the right to also remove earlier posts by you.
Respectfully
Oswald Boelcke
Senior Moderator
and i currently use it.
From Stock Rom to Pixel Experience Plus GSI Rom Android 12 and then back to stock rom because i installed TWRP Recovery and why? because if i didn't format in TWRP it can't detected Internal Storage and then i installed Stock Rom and Finally Xiaomieu Rom Via Fastboot
Popcorn (ポップコーン) said:
and i currently use it.
From Stock Rom to Pixel Experience Plus GSI Rom Android 12 and then back to stock rom because i installed TWRP Recovery and why? because if i didn't format in TWRP it can't detected Internal Storage and then i installed Stock Rom and Finally Xiaomieu Rom Via Fastboot
Click to expand...
Click to collapse
Can you share your experience with PE+ gsi rom? I'm in my 7 day waiting period for bootloader unlocking
ngocban2406 said:
Can you share your experience with PE+ gsi rom? I'm in my 7 day waiting period for bootloader unlocking
Click to expand...
Click to collapse
In My Experience if the Daily Use It's Okay (PE+ Slim which is without google apps cones with very few apps incl google phone, contacts, messages, chrome and PlayStore) but if some Specifics Game i.e. Drift Spirits (Japanese Version) not responds and Camera App Gcam Ported Latest Version 8.4.6 when i setting something wrong also (not responded) so i download OnePlus Camera Ported by AyraHikary version which is less not responded (Slow Motion and Watermark (Still takes photos) )
One Disadvantage: No Fast Charger Mode and After install i have to setting like some guides
1 - Enable Double tap to wake
Go to settings >phh trebble tree > xiaomi features > Enable D2W
2 - Bluetooth audio fix
Go to Settings> phh trebble tree> misc features > Force Disable A2DP Offload and then restart phone..done
3 - Fix call audio
Settings > phh treble settings > Qualcomn feature > tick mark use alternat audio policy and disable soundvolume effect
4 - 90Hz enable
Go to Settings> phh trebble tree> misc features > Force FPS > 90
5 - VoLte enable
Go to Settings> phh trebble tree> IMS features > Enable IMS network and force enable 4G calling....install 2nd option of IMS apk for qualcomn vendor...wait for download..then install it
and That's it. (After i re-unlock without 7 Days Period Noted: i tested on My Redmi Note 11 Spes) p.s. i installed with Fastboot mode by some guides https://mitanyan98.hatenablog.com/entry/2022/03/19/183132 (before reading please use google translate to english)
Popcorn (ポップコーン) said:
In My Experience if the Daily Use It's Okay (PE+ Slim which is without google apps cones with very few apps incl google phone, contacts, messages, chrome and PlayStore) but if some Specifics Game i.e. Drift Spirits (Japanese Version) not responds and Camera App Gcam Ported Latest Version 8.4.6 when i setting something wrong also (not responded) so i download OnePlus Camera Ported by AyraHikary version which is less not responded (Slow Motion and Watermark (Still takes photos) )
One Disadvantage: No Fast Charger Mode and After install i have to setting like some guides
1 - Enable Double tap to wake
Go to settings >phh trebble tree > xiaomi features > Enable D2W
2 - Bluetooth audio fix
Go to Settings> phh trebble tree> misc features > Force Disable A2DP Offload and then restart phone..done
3 - Fix call audio
Settings > phh treble settings > Qualcomn feature > tick mark use alternat audio policy and disable soundvolume effect
4 - 90Hz enable
Go to Settings> phh trebble tree> misc features > Force FPS > 90
5 - VoLte enable
Go to Settings> phh trebble tree> IMS features > Enable IMS network and force enable 4G calling....install 2nd option of IMS apk for qualcomn vendor...wait for download..then install it
and That's it. (After i re-unlock without 7 Days Period Noted: i tested on My Redmi Note 11 Spes) p.s. i installed with Fastboot mode by some guides https://mitanyan98.hatenablog.com/entry/2022/03/19/183132 (before reading please use google translate to english)
Click to expand...
Click to collapse
a few things i dislike in Xiaomi.eu rom is it can't detected Music in External SD Cards (Noted: i use Sony Music Center app instead of Mi Music) and i have to copy to Internal while Stock rom and GSI Does Detected.
Popcorn (ポップコーン) said:
In My Experience if the Daily Use It's Okay (PE+ Slim which is without google apps cones with very few apps incl google phone, contacts, messages, chrome and PlayStore) but if some Specifics Game i.e. Drift Spirits (Japanese Version) not responds and Camera App Gcam Ported Latest Version 8.4.6 when i setting something wrong also (not responded) so i download OnePlus Camera Ported by AyraHikary version which is less not responded (Slow Motion and Watermark (Still takes photos) )
One Disadvantage: No Fast Charger Mode and After install i have to setting like some guides
1 - Enable Double tap to wake
Go to settings >phh trebble tree > xiaomi features > Enable D2W
2 - Bluetooth audio fix
Go to Settings> phh trebble tree> misc features > Force Disable A2DP Offload and then restart phone..done
3 - Fix call audio
Settings > phh treble settings > Qualcomn feature > tick mark use alternat audio policy and disable soundvolume effect
4 - 90Hz enable
Go to Settings> phh trebble tree> misc features > Force FPS > 90
5 - VoLte enable
Go to Settings> phh trebble tree> IMS features > Enable IMS network and force enable 4G calling....install 2nd option of IMS apk for qualcomn vendor...wait for download..then install it
and That's it. (After i re-unlock without 7 Days Period Noted: i tested on My Redmi Note 11 Spes) p.s. i installed with Fastboot mode by some guides https://mitanyan98.hatenablog.com/entry/2022/03/19/183132 (before reading please use google translate to english)
Click to expand...
Click to collapse
Thanks a lot mate, I'll install pixel experience once my bootloader is unlocked, also i hope that there will be custom roms and xda forum for spes during these 7 days
okay so I've unlocked the phone, installed pixel experience plus gsi but the problem is that wifi doesn't work for some reason, same problem with lineage os gsi, return to stock rom then it's normal again, have tried some fix online but none of them worked
ngocban2406 said:
okay so I've unlocked the phone, installed pixel experience plus gsi but the problem is that wifi doesn't work for some reason, same problem with lineage os gsi, return to stock rom then it's normal again, have tried some fix online but none of them worked
Click to expand...
Click to collapse
what i did is i reinstall stock rom and then reboot to fastboot and following instruction to install Pixel Experience again and restart
ngocban2406 said:
okay so I've unlocked the phone, installed pixel experience plus gsi but the problem is that wifi doesn't work for some reason, same problem with lineage os gsi, return to stock rom then it's normal again, have tried some fix online but none of them worked
Click to expand...
Click to collapse
or another solution install Xiaomi.eu rom instead
Popcorn (ポップコーン) said:
or another solution install Xiaomi.eu rom instead
Click to expand...
Click to collapse
I've tried installing the stock rom first but no such luck, guess I'll try eu rom now
Man this bureaucracy is killing me.
Every single Redmi Note device is popular, there's no reason to not have a subforum for it. It's not even that hard to make a new subforum. The Note 11 will be insanely popular because of the 90hz display and superb battery life.
It's not like this is some obscure device from Panasonic or Energizer or some stuff like that.
On GSMArena alone, the Redmi Note 11 (SPES/SPESN) has 20,000 DAILY page visits.
Of course it would greatly help ROM development if we had one unified place for the ROMs and stuff.
xyzalify said:
Man this bureaucracy is killing me.
Every single Redmi Note device is popular, there's no reason to not have a subforum for it. It's not even that hard to make a new subforum. The Note 11 will be insanely popular because of the 90hz display and superb battery life.
It's not like this is some obscure device from Panasonic or Energizer or some stuff like that.
On GSMArena alone, the Redmi Note 11 (SPES/SPESN) has 20,000 DAILY page visits.
Of course it would greatly help ROM development if we had one unified place for the ROMs and stuff.
Click to expand...
Click to collapse
you are right
bought the NFC version of this device (codename: spesn). What can I say after a month of use: Screen - very good, battery - excellent, and I was pleasantly surprised by the audio quality (headphones). I'm waiting for the transition to the A12.
Don't be like StackExchange, you're better than that.
This phone was released on February 9, 2022. Today is 25 May 2022, three months and sixteen days later, still nothing. 3 and a half months and the admins or whatever can't take 5 minutes to make a subforum for this great phone.
Good thing there's forums for RN11 Pro+ 5G (peux/veux), RN11 Pro 4G (viva/vida), RN11S 4G (fleur), RN11T; BUT not the damn spes/spesn. Every model BUT the most popular one has a subforum. Even the damn Helio/Dimensity/Mediatek CPU RN11's have subforums... seriously now.
What can we do to get a subforum for spes/spesn? This is the SNAPDRAGON version. So modding is easy.
I can't believe, it could be happened? I had bought Snapdragon version thinking I will find mods easily but till date there's not a forum for device, development is later thing
ajaynumb said:
Despite numerous requests for adding a forum for Redmi Note 11 4G(spes) device, this website has continuously ignored the requests for the same stating "not much discussed", "not much user interest", etc.
So, please vote it out here for one last time to show how much of a user base need a forum for Redmi Note 11 4G(spes)
Click to expand...
Click to collapse
Thread closed as the device forum has been created:
Redmi Note 11 (spes/spesn)
The Redmi Note 11 is a 6.43" phone with a 1080x2400 resolution display. The Qualcomm SM6225 Snapdragon 680 4G chipset is paired with 4/6GB of RAM and 64/128GB of storage. The main camera is 50+8+2+2MP and the selfie camera is 13MP. The battery has a 5000mAh capacity.
forum.xda-developers.com
I have a Magisk (25.2) rooted Pixel 6a that I'm trying to get AccA to run on. I have https://github.com/MatteCarra/AccA (ACCA v1.0.35 (39)) and ACC Daemon v2021.8.31 (202108310). It installs fine, I click the 'grant root forever' popup for tAccA with Magisk, and then when going to run it, whether clicking Start or Restart, it runs for 30 - 40 seconds and then switches to ACC Daemon is not running. Looking at the contents of the files at /data/adb/vr25/acc-data/logs either doesn't produce anything telling about why the Daemon keeps dying or I'm not looking in the right place or looking for the right keyword(s). Any suggestions here? This same app works great on my older Pixel 4XL, of which even having used this app the battery is still well into its wear, so it's time for a new phone, battery, and couple generations of hardware newer. I've tried string searching and haven't found anything useful.
I can't do a "acc -t" to find a working switch to enter in the UI, most likely because the Daemon keeps dying.
Thank you for any suggestions.
Update the version of acc module from the app. The version you're using is very old. Works fine on my 6a, but the idle mode doesn't function.
Edit: Below is another ACC UI app. It is listed on the main git for ACC
GitHub - CrazyBoyFeng/AccSettings: Simple UI for Advanced Charging Controller
Simple UI for Advanced Charging Controller. Contribute to CrazyBoyFeng/AccSettings development by creating an account on GitHub.
github.com
Ace42 said:
Update the version of acc module from the app. The version you're using is very old. Works fine on my 6a, but the idle mode doesn't function.
Edit: Below is another ACC UI app. It is listed on the main git for ACC
GitHub - CrazyBoyFeng/AccSettings: Simple UI for Advanced Charging Controller
Simple UI for Advanced Charging Controller. Contribute to CrazyBoyFeng/AccSettings development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Thanks for the quick response. I'd seen some references to acc_v2022.7.30 but wasn't sure how to install that as I didn't see any simple apk's. Would I copy the acc_v2022.7.30-dev_202207300_2206.zip file to the 6a, extract it and then just run the install.sh or install-online.sh script from either ADB shell or right from the 6a with a terminal emulator app?
YDBB said:
Thanks for the quick response. I'd seen some references to acc_v2022.7.30 but wasn't sure how to install that as I didn't see any simple apk's. Would I copy the acc_v2022.7.30-dev_202207300_2206.zip file to the 6a, extract it and then just run the install.sh or install-online.sh script from either ADB shell or right from the 6a with a terminal emulator app?
Click to expand...
Click to collapse
I did run sh ./install-tarball.sh in the AccSettings-main/AccSettings-main/app/src/main/assets path and then the About page of AccA has a ACC Daemon dated 2022.6.12-dev and now the Daemon doesn't routinely die. I also got output now when running acc -t, yay! I didn't see anything similar to the "charger/charge_disable 0 1" that I have on a Pixel 4XL so I chose "maxfg/offmode_charger 0 1" with acc -ss, and that shows in the phone's AccA UI.
Which switch are you using? What I want it to do is have a settable stop % of charge.
All you have to do is remove the old module from magisk, then install the 7.30 build from the app, telegram group or GitHub. Once you reboot acc will become functional.
Following. Had it working well on my 4a I traded in...my 6a, not so much. Gonna get it current first...thx for the tip. Tricky to find applicable info as it seem seem to differ from model to model and even between users prefs. ...and the only java I speak is coffee.
Any recommendations for settings we should use? I have it to pause the charge at 85%.