[Q] Need to stop BootAnimation (Custom Launcher) - Java for Android App Development

Hi everybody,
I work on a light Launcher (to replace Launcher2.apk).
One of my objectives is obviously to have a quick boot.
But when my app is ready to show something, the bootanimation is still visible until the Boot timeout (40s after the first log):
WindowManager: ***** BOOT TIMEOUT: forcing display enabled
If I reboot with my command line :
adb reboot && adb wait-for-device && adb shell setprop service.bootanim.exit 1
My boot time is around 15s but with a bad rotation display until I receive the first ConfigurationChanged event. Without this point, the app is ready so...
Question 1: Do you know a way to properly close the boot animation?
Question 2: If the Q1 don't solve the ConfigurationChanged event, do you know a method to receive the ConfigurationChanged event in my Launcher?
Best Regards,
Kikiwa
PS : I hope this topic is in the right section, sorry if it's not the case.

Same problem
kikiwa said:
Hi everybody,
I work on a light Launcher (to replace Launcher2.apk).
One of my objectives is obviously to have a quick boot.
But when my app is ready to show something, the bootanimation is still visible until the Boot timeout (40s after the first log):
WindowManager: ***** BOOT TIMEOUT: forcing display enabled
If I reboot with my command line :
adb reboot && adb wait-for-device && adb shell setprop service.bootanim.exit 1
My boot time is around 15s but with a bad rotation display until I receive the first ConfigurationChanged event. Without this point, the app is ready so...
Question 1: Do you know a way to properly close the boot animation?
Question 2: If the Q1 don't solve the ConfigurationChanged event, do you know a method to receive the ConfigurationChanged event in my Launcher?
Best Regards,
Kikiwa
PS : I hope this topic is in the right section, sorry if it's not the case.
Click to expand...
Click to collapse
I am having the same problem , have you found any solution?

Hello !
Sorry but no. I'm still interested by the solution BTW.
Good luck
Kikiwa

kikiwa said:
Hello !
Sorry but no. I'm still interested by the solution BTW.
Good luck
Kikiwa
Click to expand...
Click to collapse
In my case I pushed my custom launcher apk to system/app and deleted launcher2.apk
Could it be that the system is waiting for some special response from default launcher? That should be made in custom luancher?

Possible Solution
Hey guys,
I was having this same issue for a while now, and I finally found a solution that works for me, at least as of Android 4.4.4 on a Nexus 7 2013 (LTE)
What I did to find this was selectively disable system apps one by one, and then test a reboot.
In my case, disabling Launcher2 didn't affect the boot sequence, but SystemUI (com.android.systemui) did cause these delayed boot times.
I dug through the ASOP source code, and found that the WindowManagerService performs a few checks in performEnableScreen() before stopping boot animation / displaying normally:
- System services must all be ready (mSystemBooted)
- A keyguard or application must be attached to Window Manager (haveApp || haveKeyguard)
- The Wallpaper Service must be disabled or ready (!wallpaperEnabled || haveWallpaper)
Since monitoring logcat showed my replacement launcher was open, and the system services had no errors, I suspected #3 was the problem
In the source for SystemUI, I found a single reference for "wallpaper" - com.android.systemui.ImageWallpaper is an included class that extends WallpaperService but itself is never referenced from that package.
Checking logcat again, I found these lines:
Code:
Attempted wallpaper ComponentInfo{com.android.systemui/com.android.systemui.ImageWallpaper} is unavailable
Default wallpaper component not found!
It turns out that the system-level WallpaperManagerService has hard-coded that particular class.
As a test fix, I created a new project with package name "com.android.systemui" and a single class "ImageWallpaper" that extends WallpaperService, declared this as a service in my manifest, and installed this apk on a device.
I rebooted, and the boot times were back to normal (~20sec) instead of the previous ~50sec.
So in summary: SystemUI was the culprit in my case; creating a fake replacement package with that hardcoded class back in fixed the long boot times.

Thank you
dtyler7 said:
Hey guys,
I was having this same issue for a while now, and I finally found a solution that works for me, at least as of Android 4.4.4 on a Nexus 7 2013 (LTE)
What I did to find this was selectively disable system apps one by one, and then test a reboot.
In my case, disabling Launcher2 didn't affect the boot sequence, but SystemUI (com.android.systemui) did cause these delayed boot times.
I dug through the ASOP source code, and found that the WindowManagerService performs a few checks in performEnableScreen() before stopping boot animation / displaying normally:
- System services must all be ready (mSystemBooted)
- A keyguard or application must be attached to Window Manager (haveApp || haveKeyguard)
- The Wallpaper Service must be disabled or ready (!wallpaperEnabled || haveWallpaper)
Since monitoring logcat showed my replacement launcher was open, and the system services had no errors, I suspected #3 was the problem
In the source for SystemUI, I found a single reference for "wallpaper" - com.android.systemui.ImageWallpaper is an included class that extends WallpaperService but itself is never referenced from that package.
Checking logcat again, I found these lines:
Code:
Attempted wallpaper ComponentInfo{com.android.systemui/com.android.systemui.ImageWallpaper} is unavailable
Default wallpaper component not found!
It turns out that the system-level WallpaperManagerService has hard-coded that particular class.
As a test fix, I created a new project with package name "com.android.systemui" and a single class "ImageWallpaper" that extends WallpaperService, declared this as a service in my manifest, and installed this apk on a device.
I rebooted, and the boot times were back to normal (~20sec) instead of the previous ~50sec.
So in summary: SystemUI was the culprit in my case; creating a fake replacement package with that hardcoded class back in fixed the long boot times.
Click to expand...
Click to collapse
It is exactly my problem and your solution seems perfect
Thank you for your efforts

command "setprop ctl.start bootanim" to perform boot animation;
command "setprop ctl.stop bootanim" stop the boot animation.

Related

HTC Stocks currency problem

The HTC Stocks app has the best widget of all other currency apps, so I was using it on my 1.5 Hero for displaying the EURO/GBP (EURGBP=X) rate.
After the 2.1 rom update I have a strange problem. When I try to add a new ticker for "eurgbp=x", I get the error message: "Unable to recognize the company name or stock symbol you typed. Please try again." However, this worked in the past like a charm. I have to note that adding "gbp=x" or "usd=x" works fine, with no problem at all.
Maybe this problem is related to an updated version of the Stocks app in the new rom. Is anyone experiencing the same problem? I haven't found a similar thread for a Sense Android phone. The same problem exists in the latest rom of HD2, but people have figured a work-around, by changing a file under "Application Data\HTC\", but this file doesn't exist on Android.
Any help would be more than welcome!
I experience the same problem (although I'm on VillainRom12). Previously adding currencies (EURUSD=X etc) was working, but right now I am unable to find it. This could be HTC problem as it was working fine on 1.5, but this could be also some Yahoo search glitch (I am unable to search for that quotes on mobile version of the Yahoo Finance page, while the desktop version works fine). The only workaround to that was to edit manually SQLite database of Stocks application (but this may require root - I can provide details if necessary). Once I added appropriate entries to the list of stocks, it seems to be working fine (it is displaying my currencies, but the search still does not work).
One other deficiency I found was the fact that graphs are not cached anymore - If I open the application and check for example a daily graph, I need to update it in order to see any chart - each time, even if I switch from 1D to 5D and back. It is also automatically updated each time I visit given tab, if I enable the automatic updates. Previously this app displayed previously cached graph. I'm not sure whether this happens also on stock 2.1 ROM.
Now that you mention it, I have the same problem with the graphs in the 2.1, too. It worked (showed the cashed graph) in the 1.5, but not any more. Blank graph until it updates.
Can you provide me some guidance about how to edit the Stocks' database? At least a link to something similar would be much appreciated. Can I access the phone's system folder without rooting it, through my PC (Win, Linux, whatever)?
eeVoskos said:
Can you provide me some guidance about how to edit the Stocks' database? At least a link to something similar would be much appreciated. Can I access the phone's system folder without rooting it, through my PC (Win, Linux, whatever)?
Click to expand...
Click to collapse
I'm new in the business, so I'm not sure if the root is necessary. You can try it, anyway to see if you will be able to push and pull files from the directory where Stocks stores its database.
Here's what I did:
Enable USB Debugging in Settings -> Applications -> Development -> USB Debugging
Download Android SDK from http://developer.android.com/sdk/index.html
In command line go to subdirectory tools of Android SDK
Close Stocks app and remove Stocks widget from the screen
Connect Phone via USB
... (Beginning of the optional part) ...
Go to Android shell
Code:
adb shell
List any processes to see if there's a com.htc.android.Stock process (like in this case)...
Code:
ps | grep Stock
7605 10007 130m S com.htc.android.Stock
7619 0 2156 S grep Stock
Kill any Stock processes (using the value in the first column):
Code:
kill 7605
Exit to command line
Code:
exit
... (End of the optional part) ...
Pull the Stock database:
Code:
adb pull /data/data/com.htc.dcs.service.stock/databases/stock.db stock.db
Sample output:
Code:
d:\Projects\Android\tools>adb pull /data/data/com.htc.dcs.service.stock/databases/stock.db stock.db
568 KB/s (5120 bytes in 0.008s)
Backup, just in case:
Code:
copy stock.db stock_backup.db
Run sqlite3
Code:
sqlite3 stock.db
Enable headers in sqlite:
Code:
.headers on
List contents of quotes table:
Code:
select * from quotes;
Sample output:
Code:
sqlite> select * from quotes;
_id|_name|_symbol|_price|_change|_percent|_open|_high|_low|_volume|_link|_type|_sequence|_updatetime
2|CHF/PLN|CHFPLN=X|3.08299994468689|0.0116999996826053|0.381900012493134|3.07209992408752|3.08550000190735|3.07010006904602|0|http://m.yahoo.com/htcwf/search?p=CHFPLN=X||0.0|1278490511305
3|USD/PLN|USDPLN=X|3.27649998664856|0.0200999993830919|0.617200016975403|3.25550007820129|3.27959990501404|3.24499988555908|0|http://m.yahoo.com/htcwf/search?p=USDPLN=X||100.0|1278490511305
4|EUR/PLN|EURPLN=X|4.1217999458313|0.0151000004261732|0.367700010538101|4.11250019073486|4.12349987030029|4.10799980163574|0|http://m.yahoo.com/htcwf/search?p=EURPLN=X||200.0|1278490511305
5|EUR/USD|EURUSD=X|1.25789999961853|-0.00469999993219972|-0.376199990510941|1.26170003414154|1.26259994506836|1.25689995288849|0|http://m.yahoo.com/htcwf/search?p=EURUSD=X||300.0|1278490511305
6|EUR/CHF|EURCHF=X|1.33689999580383|-0.000899999984540045|-0.0710000023245811|1.33879995346069|1.33910000324249|1.33609998226166|0|http://m.yahoo.com/htcwf/search?p=EURCHF=X||400.0|1278490511305
sqlite>
Note the last _id (here 6) and add new currency with _id higher by 1 (so here, 7):
Code:
insert into quotes (_id, _name, _symbol) values (7, "EUR/GBP", "EURGBP=X");
Check if it has been added:
Code:
select * from quotes;
Sample output:
Code:
sqlite> select * from quotes;
_id|_name|_symbol|_price|_change|_percent|_open|_high|_low|_volume|_link|_type|_sequence|_updatetime
2|CHF/PLN|CHFPLN=X|3.08299994468689|0.0116999996826053|0.381900012493134|3.07209992408752|3.08550000190735|3.07010006904602|0|http://m.yahoo.com/htcwf/search?p=CHFPLN=X||0.0|1278490511305
3|USD/PLN|USDPLN=X|3.27649998664856|0.0200999993830919|0.617200016975403|3.25550007820129|3.27959990501404|3.24499988555908|0|http://m.yahoo.com/htcwf/search?p=USDPLN=X||100.0|1278490511305
4|EUR/PLN|EURPLN=X|4.1217999458313|0.0151000004261732|0.367700010538101|4.11250019073486|4.12349987030029|4.10799980163574|0|http://m.yahoo.com/htcwf/search?p=EURPLN=X||200.0|1278490511305
5|EUR/USD|EURUSD=X|1.25789999961853|-0.00469999993219972|-0.376199990510941|1.26170003414154|1.26259994506836|1.25689995288849|0|http://m.yahoo.com/htcwf/search?p=EURUSD=X||300.0|1278490511305
6|EUR/CHF|EURCHF=X|1.33689999580383|-0.000899999984540045|-0.0710000023245811|1.33879995346069|1.33910000324249|1.33609998226166|0|http://m.yahoo.com/htcwf/search?p=EURCHF=X||400.0|1278490511305
7|EUR/GBP|EURGBP=X|||||||||||
sqlite>
Quit sqlite:
Code:
.quit
Push the file back to the phone:
Code:
adb push stock.db /data/data/com.htc.dcs.service.stock/databases/stock.db
Sample output:
Code:
d:\Projects\Android\tools>adb push stock.db /data/data/com.htc.dcs.service.stock/databases/stock.db
341 KB/s (5120 bytes in 0.014s)
Restart phone.
See if that worked
I hope HTC (or Yahoo) will be able to fix that, because the above is really a long process...
Anyway, I can't make it work. Entering "ps | grep Stock" gives me a "grep: permission denied" error message. I did some searching and I believe this is what people mean by saying "you need root access", right? I'll come back when I'm rooted (i.e. when I find a decent guide for rooting 2.1).
Thanks for your time & effort man. I really appreciate it.
eeVoskos said:
Anyway, I can't make it work. Entering "ps | grep Stock" gives me a "grep: permission denied" error message.
Click to expand...
Click to collapse
You can try to omit the "optional" part (steps 6-9) - the ps thing was just to make sure that Stock isn't running. But I noticed anyway that it never ran in the background when I closed it on the phone. Try to adb pull and adb push and see if you'll get any permission issues. If you do, then you indeed need a root (sorry I can't check that as I'm rooted)
A couple of days ago I updated the ROM of my HTC TD2, with the most recent one of HTC (WM6.5, Sense 2.5.20113030.0). Afterwards I noticed that I also could not get the stock app to accept the code EURUSD=X.
You mention the following
The same problem exists in the latest rom of HD2, but people have figured a work-around, by changing a file under "Application Data\HTC\", but this file doesn't exist on Android.
Click to expand...
Click to collapse
Can you tell me what that work-around is or point me to it? Hopefully this can help me.
Thank you in advance.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=706732
eeVoskos said:
Check this thread:
Click to expand...
Click to collapse
Thank you for the link (which I am not allowed to repost ).
Last Monday I wrote an e-mail to HTC about this problem and a couple of days later I got a reply. They told me they tried to search for the currency rate (eurusd) and that they got a result. So I tried again and lo and behold I got a result as well. Searching for eurusd=x gave me a result while last weekend it was not working.
So I tried several other currency rates and they all rendered a result, also eurgbp=x. Perhaps it is also fixed for the Android app.
[Extra information added below]
Tried again and nothing
I was connected with a data connection to my carrier, so I switched to my wifi connection. Tried again and... result.
So it seems to be a difference in communication between an ordinary data connection and a wifi connection. Maybe this will help someone
Wird problem. I tried it too on both UK and Greek carriers and on WiFi, but nothing. No result for either of them: "eurgbp=x", "eurgbp", "eurusd=x", "eurusd". I have been trying occasioanly more than one month now.
I think I should drop them an email too...
Why don't you do a soft (temporary) root and make the database entries as described in here? I did it and now I got all the stuff I need, and no trace of root on the device.

Dev tools setting causing reboot loop :(

Just installed Elelinux-7.1.0-Hero-v2.1, poked around in Dev Tools, and apparently turned on some debugging feature I should not have. Now my phone goes into a reboot loop. It isn't a full reboot... only the Android boot animation is shown, not the initial HTC splash screen. It makes it up to the lockscreen and the phone is responsive for about 10 seconds before it freezes up and reboots.
This isn't enough time for me to unlock the screen, open the app drawer, run Dev Tools, and change back the setting before the phone reboots. Is there another way of manually clearing the Dev Tools settings without having to do a factory wipe?
Since I can't get into Dev Tools now, I cannot say which options were enabled. I turned on one that shows the touch coordinates, and I think another that shows the running processes (trying to track down battery drain issues). There may have been a couple of others, but due to the delay in the reboot, it's hard to tell exactly which one is the culprit.
So I'm hoping there is some way to bring up the phone in single-user mode, edit or delete a settings file, and then rebooting the phone. I'm using the AmonRA recovery console, if that helps.
I'd just reflash...
Yeah, there isn't much on the phone yet, so I could do a wipe and not lose anything, but I'd rather see if there is a way to recover in case something like this happens again in the future.
I did find an issue tracker page on Google that describes the problem, and a couple of proposed fixes. I'm not allowed to post links yet, so demangle this to bring up the page. I'm going to try editing the settings.db file and hopefully that will fix things:
ht tp://code.google.com/p/cyanogenmod/issues/detail?id=1026
Hooray, editing the settings.db file worked! I followed the suggest posted by cryptographrix in post #14 of the code.google.com thread:
Code:
$ [B]./adb shell[/B]
/ # [B]mount /data[/B]
/ # [B]mount /system[/B]
/ # [B]/system/xbin/sqlite3 ./data/data/com.android.providers.settings/databases/settings.db[/B]
SQLite version 3.7.2
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> [B].header ON[/B]
sqlite> [B]select * from system where name="show_processes";[/B]
_id|name|value
109|show_processes|1
sqlite> [B]update system set value=0 where name="show_processes";[/B]
sqlite> [B]select * from system where name="show_processes";[/B]
_id|name|value
109|show_processes|0
sqlite> [B].quit[/B]
/ # [B]reboot[/B]

CM7 Lockscreen Mods

Alright. Now that Cyanogenmod has fixed the android.git.kernel.org sync errors, I have continued my CM7 Development (lockscreen stuff for now).
There are currently four new features:
1) Changeable pattern lockscreen size (3x3 - 5x5).
2) Visible dot toggle, for pattern unlock screen.
3) Custom lockscreen message (on normal and keyguard ones).
4) Carrier name change. NOT MINE anymore. Thanks Frederic Van Assche
After I get these problems fixed and setting for all of the features, I will release the mods here, and hopefully into official CM7.
Now for some pictures. See attached (untill i upload). Note: all images are at 180 lcd density (sortof needed for 5x5)
---------- Post added at 01:28 PM ---------- Previous post was at 01:10 PM ----------
Development Section
Im currently really busy with school, so most of the work will be done on the weekends.
Current development status, and todo list.
1) The lockscreen size mod works fine. Few small code cleanup things and stuff needed.
2) The visible dot toggle has a setting and works perfect. The checkbox sometimes doesn't display right so you may have to click it twice to turn it on/off (not sure whats wrong, low priority).
3) Custom lockscreen message works great. Sometimes you have to enable+disable it for it to update (work on auto do/fix). And I haven't added it to the PIN lock and stuff (have to check). In the end I would like the enable/disable and message to be on a different settings screen (like on Honeycomb).
4) And the carrier name thing is now obsolete. Thanks to the patch by Frederic Van Assche, shown to me by one_love_420.
Ohh. And if any of you have any suggestions on things to add or change, i'm happy to listen and try.
Beta Testing.
Current Bugs
Code:
1. Choose pattern size, press back, doesn't revert size (ex: unlock problem from 5x5->3x3)
2. Change lock pattern size. Can't unlock from the actual lockscreen, in settings its fine. (IMPORTANT!)
Fixed by rebooting. Changing to same size is fine
Notes
These builds are buggy. Use at your own risk.
If you cannot unlock your phone, you can fail 5 times and then log in with your google account.
Downloads
http://androtransfer.com/development/smasher816/cm7 beta/
For a better way to do the custom carrier text and to have it in the settings as an option check this over at the gerrit. I have used since he posted it for review and it works great.
http://review.cyanogenmod.com/#change,7314
And
http://review.cyanogenmod.com/#change,7313
Sent from my PG06100 using Tapatalk
Thanks man.
I'm assuming I would run the patch command (git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_frameworks_base refs/changes/14/7314/2 && git format-patch -1 --stdout FETCH_HEAD)
Edit: that seemed to do nothing but output the changes.
I did the checkout one ("git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_frameworks_base refs/changes/14/7314/2 && git checkout FETCH_HEAD") and now it says
Code:
~/android/system/packages/apps/CMParts$ git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_packages_apps_CMParts refs/changes/13/7313/3 && git checkout FETCH_HEAD
From http://review.cyanogenmod.com/p/CyanogenMod/android_packages_apps_CMParts
* branch refs/changes/13/7313/3 -> FETCH_HEAD
Note: checking out 'FETCH_HEAD'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at 5ed9b01... Custom carrier label (2/2)
Sorry, i'm still pretty new at git. What do I do now?
I'm new to the git and I do it probably the more difficult way but it gets the job done. What I do is download each change one by one, use "meld" to compare my java/xml files and add the new edits in. Like I said the more difficult way to do it.
Sent from my PG06100 using Tapatalk
Smasher816 said:
Alright. Now that Cyanogenmod has fixed the android.git.kernel.org sync errors, I have continued my CM7 Development (lockscreen stuff for now).
There are currently four new features:
1) Changeable pattern lockscreen size (3x3 - 5x5).
2) Visible dot toggle, for pattern unlock screen.
3) Custom lockscreen message (on normal and keyguard ones).
4) Carrier name change. No setting yet.
After I get these problems fixed and setting for all of the features, I will release the mods here, and hopefully into official CM7.
Now for some pictures. See attached (untill i upload). Note: all images are at 180 lcd density (sortof needed for 5x5)
---------- Post added at 01:28 PM ---------- Previous post was at 01:10 PM ----------
Developer Help Needed Section.
1) For the carrier name replacement I edited
Code:
String plmn = "<WHATEVER>"; //ss.getOperatorAlphaLong();
(line 587) in GsmServiceStateTracker.java. I would like to find a way to add this as a setting to CMParts but haven't looked around enough to figure out how yet. If any of you could hint me in the right way or something that would make my life easier.
2) SOLVED
Click to expand...
Click to collapse
how do we change our pattern size???
maxib123 said:
how do we change our pattern size???
Click to expand...
Click to collapse
If you read, he's developing it. Hence, you can't get it as of this moment.
sixstringsg said:
If you read, he's developing it. Hence, you can't get it as of this moment.
Click to expand...
Click to collapse
sorry, it wasnt that clear first time i read it
If you want a tester btw, you know where to find me
Thanks dude. I was out of town this weekend but started work on getting the pattern size setting more formal and correct.
However my Ubuntu vm decided to not boot.
Edit: fixed it with commands in slax, then in some terminal on ubuntu reboot.
However everything seems to be only. And I can't change the folders permissions due to read only filesystem. Any ideas?
e2fsck /dev/sda2 from root recovery seems to say it was fixed. but continues to not boot, and allowing me to run that command again and again.
If this doesn't get fixed soon. I think I'm gone to attempt to get my edited files from the read only (but bootable) snapshot, and add them back into the last working snapshot.
Smasher816 said:
Thanks dude. I was out of town this weekend but started work on getting the pattern size setting more formal and correct.
However my Ubuntu vm decided to not boot.
Edit: fixed it with commands in slax, then in some terminal on ubuntu reboot.
However everything seems to be only. And I can't change the folders permissions due to read only filesystem. Any ideas?
e2fsck /dev/sda2 from root recovery seems to say it was fixed. but continues to not boot, and allowing me to run that command again and again.
If this doesn't get fixed soon. I think I'm gone to attempt to get my edited files from the read only (but bootable) snapshot, and add them back into the last working snapshot.
Click to expand...
Click to collapse
have you tried chmod 777? if im on the right page, that should work. if not i have no idea mate, sorry
Smasher816 said:
Thanks dude. I was out of town this weekend but started work on getting the pattern size setting more formal and correct.
However my Ubuntu vm decided to not boot.
Edit: fixed it with commands in slax, then in some terminal on ubuntu reboot.
However everything seems to be only. And I can't change the folders permissions due to read only filesystem. Any ideas?
e2fsck /dev/sda2 from root recovery seems to say it was fixed. but continues to not boot, and allowing me to run that command again and again.
If this doesn't get fixed soon. I think I'm gone to attempt to get my edited files from the read only (but bootable) snapshot, and add them back into the last working snapshot.
Click to expand...
Click to collapse
e2fsck -A /dev/sda2
Try that
I ended up getting my read only changes and putting them on my actual computer,
then re doing my VM and melding my changes back in.
I got a backup, and a build made.
However settings crashes (doesn't look like my edits). I will attempt to fix it. Worst comes to worse go back to the good build and merge piece by piece.
Edit: The last two weeks and weekends have been super busy, barely able to turn on my PC. Anyways I got a 4 day weekend coming up, I should hopefully have everything worked out then.
any progress yet?
maxib123 said:
any progress yet?
Click to expand...
Click to collapse
He's got most of the work done, he just needs to get it all merged and get it all up on github. He got distracted by a fun new build system for our kernel.
Edit: Disregard the old information. I now have some freetime over this weekend, the last two weeks have been crazy busy. I am slowly putting my tweaks into the latest nightly and making sure everything is working (vm redo). Anyways the newest build works! - You go to settings -> location and security -> Change Screen Lock -> Confirm saved pattern -> Choose unlock type (pattern) -> Choose pattern size (3-5) -> Draw new pattern (x2).
Where in the settings should the custom lockscreen message be? CMParts -> Lockscreen -> Widget Options -> Custom Message, or Security -> Owner Info (like honeycomb), or somewhere else?
i prefer
CMParts -> Lockscreen -> Widget Options -> Custom Message
Click to expand...
Click to collapse
what i like best about this project is
a) i`ve always wanted a 5*5 unlock pattern
b) you`re working this into the Cyanogenmod Project
Thanks.
Heres a little development update. Im working on getting the 5x5 lockscreen perfect before adding back in the lockscreen message and stuff. The actual 5x5 works fine, all my problems come from the dynamically changing size. Im trying to fix these two important bugs I have found. Hopefully I can get it solved, if not I might upload my work and see if you guys can help me out
Code:
#BUGS#
1. Choose pattern size, press back, doesn't revert size (ex: unlock problem from 5x5->3x3)
2. Change lock pattern size. Can't unlock from the actual lockscreen, in settings its fine. (IMPORTANT!)
Fixed by rebooting. Changing to same size is fine
If your willing to put up with these bugs check the OP.
Is there anyway to add this on to a current build of cyanogen nightly rather than flashing an older one?
Sent from my Nexus One using XDA App
Ummmmm. I edited frameworks/base and packages/apps/Settings
So So replace the Settings.apk and framework folder or something.
This is something,I don't mind testing out. hopefully it'll work on cm7.1
From my fist to your face, enjoy.

Script/App for Shutdown

Hey,
I'm having a rooted Nook Simple Touch (FW 1.2.1) and want to add a shortcut (to launcher 8) for powering off the device. Unfortunately every tried command (adb reboot -p, several java shutdown methods) results in an immediate shutdown of the device and it looks like the device is frozen. After pressing the power button, you can see the usual "device is powering on" screen.
Does anybody know how I can power off my device, with showing the "Your NOOK has turned off completely" screen? Already tried some sendevent commands for simulating touch events, but with no success.
Thanks in advanced.
I always just hold the power button.
Do you want it to shutdown without even the confirm menu?
It's trivial, it's just an Intent, android.intent.action.ACTION_REQUEST_SHUTDOWN
Oh, but you just can't just:
Code:
# am start -a android.intent.action.ACTION_REQUEST_SHUTDOWN
Starting: Intent { act=android.intent.action.ACTION_REQUEST_SHUTDOWN }
[i]blah, blah, blah[/i] requires android.permission.SHUTDOWN
Unfortunately (or fortunately for security) android.permission.SHUTDOWN can only be obtained by a system app.
The solution? Write an app, put the permission in AndroidManifest.xml and sign it with the system signature.
This is only possible if you have re-signed your entire system.
It works fine on my Nook.
Yes, I want it without the confirm menu.
I tried your suggestion with the intent, transferred the app to with su to system app, but with no results. Do I have to generate a key by myself and sign the app to get the shutdown permission from android?
After a deeper system scan, I found the images which are shown if the device is shutdown or restarting under /system/assets. So I wrote an App set the image cold_boot_screen.png as background and shutting down the device with reboot -p. So this is working for me.
black-lord said:
I tried your suggestion with the intent, transferred the app to with su to system app, but with no results.
Click to expand...
Click to collapse
You should have seen "Not granting permission android.permission.SHUTDOWN" in logcat when installing.
You should have seen java.lang.SecurityException in logcat when attempting to run.
black-lord said:
So this is working for me.
Click to expand...
Click to collapse
True.
Still, that's really a Linux shutdown and not the kinder, gentler Android shutdown.
Or maybe not?
Maybe zygote gets a signal to shutdown and shuts down everything gracefully?
I don't know.
Re-signing your system does not have to be a big deal.
Moreover, if you want to go modifying some of the Nook's framework or Reader you'll have to do that anyway.

Is it possible to deinstall the Lockscreen on HD 10?

So the Lockscreen on my new HD 10 is pretty garbage, so far I've managed to get rid of the ads, but I can't change the Lockscreen wallpaper and I don't get any preview of a notification (e.g. the mail subject etc.)
Is there a workaround for those problems? Because simply isntalling a new lockscreen app, just makes me unlock my tablet twice, which isn't ideal.
Did you manually disable com.amazon.kindle.kso (special offers/lockscreen ads) over ADB in fire os 5.4.0.0 or lower using the method DragonFire1024 posted? If so, then yes, I found a fix that allows you to see notifications on the lockscreen without swiping down, more like the stock Android 5.x lockscreen.
lakitu47 said:
Did you manually disable com.amazon.kindle.kso (special offers/lockscreen ads) over ADB in fire os 5.4.0.0 or lower using the method DragonFire1024 posted? If so, then yes, I found a fix that allows you to see notifications on the lockscreen without swiping down, more like the stock Android 5.x lockscreen.
Click to expand...
Click to collapse
I did it over adb yes, but on the newest release of fire OS (5.6)
wieli99 said:
I did it over adb yes, but on the newest release of fire OS (5.6)
Click to expand...
Click to collapse
I thought Amazon broke the ability to disable apps over ADB with the release of 5.4.0.1. Did that not affect the new 2017 HD 10?
Sent from my Amazon KFGIWI using XDA Labs
lakitu47 said:
I thought Amazon broke the ability to disable apps over ADB with the release of 5.4.0.1. Did that not affect the new 2017 HD 10?
Click to expand...
Click to collapse
It works for me in adb shell with
pm clear --user 0 com.amazon.kindle.kso
Well, I don't know if this will work with your exact tablet, but try this:
1. If you haven't already, get the Google Play store/services on your tablet
2. Download this app without the quotes: "https://play.google.com/store/apps/details?id=by4a.setedit22&hl=en"
3. Follow on-screen instructions to grant tablet permission to edit secure settings (worked on 2 devices on 5.6)
BE CAREFUL WHAT YOU EDIT. If you change the wrong settings, your tablet can and probably bootloop or get bricked.
4. Go to the "secure" tab, scroll down to "limit_ad_tracking" and change value to 1
5. Go to "global" tab, scroll down to "LOCKSCREEN_AD_ENABLED" and change value to 0. Immediately reboot your device.
This was tested and worked on two HD 8 tablets on 5.6, with special offers manually disabled on 5.4. Since Amazon still thinks you are subscribed to special offers (ads), the notifications are hidden. This workaround actually makes the ads gone (hopefully), so the notifications will appear as soon as you turn on the screen, without a swipe down gesture.
Open up command prompt. Type in "adb shell", Then type in "su"
Then copy this into command prompt.
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled'"
You will not get a confirmation, now type "exit", then type "reboot".
Let the device reboot and enjoy! Now install a new lockscreen.
Want it back?
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '0' WHERE name = 'lockscreen.disabled'"
*This is messing with the sqlite in the actual android system files, please becareful and don't go around changing values in system files.
source: Tips Tricks and the Root
Jned said:
Open up command prompt. Type in "adb shell", Then type in "su"
Then copy this into command prompt.
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled'"
You will not get a confirmation, now type "exit", then type "reboot".
Let the device reboot and enjoy! Now install a new lockscreen.
Want it back?
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '0' WHERE name = 'lockscreen.disabled'"
*This is messing with the sqlite in the actual android system files, please becareful and don't go around changing values in system files.
source: Tips Tricks and the Root
Click to expand...
Click to collapse
do you have to have root for this? i did su and it said, " su not found."
Jned said:
Open up command prompt. Type in "adb shell", Then type in "su"
Then copy this into command prompt.
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled'"
You will not get a confirmation, now type "exit", then type "reboot".
Let the device reboot and enjoy! Now install a new lockscreen.
Want it back?
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '0' WHERE name = 'lockscreen.disabled'"
*This is messing with the sqlite in the actual android system files, please becareful and don't go around changing values in system files.
source: Tips Tricks and the Root
Click to expand...
Click to collapse
Like that one eh? That was one of the first ones I found. Works without root too.
wieli99 said:
So the Lockscreen on my new HD 10 is pretty garbage, so far I've managed to get rid of the ads, but I can't change the Lockscreen wallpaper and I don't get any preview of a notification (e.g. the mail subject etc.)
Is there a workaround for those problems? Because simply isntalling a new lockscreen app, just makes me unlock my tablet twice, which isn't ideal.
Click to expand...
Click to collapse
Personally, I'd suggest just rooting it and disabling it. I did it a few months ago on my Dad's HD10 by following one of the guides here- I just can't remember which one, but it was simple. I also installed Gravity Screen Pro since I have his set up more like a laptop. The screen turns on/off when opened/ closed without ever having to see a lock screen. I might stop by my parents today (depending on the weather) and if i do, I'll try to trace my steps and link the guide I followed
dondraper23 said:
Personally, I'd suggest just rooting it and disabling it. I did it a few months ago on my Dad's HD10 by following one of the guides here- I just can't remember which one, but it was simple. I also installed Gravity Screen Pro since I have his set up more like a laptop. The screen turns on/off when opened/ closed without ever having to see a lock screen. I might stop by my parents today (depending on the weather) and if i do, I'll try to trace my steps and link the guide I followed
Click to expand...
Click to collapse
There are also a few Xposed modules that work too.
Sent from my Samsung Galaxy S4 using XDA Labs
wieli99 said:
So the Lockscreen on my new HD 10 is pretty garbage, so far I've managed to get rid of the ads, but I can't change the Lockscreen wallpaper and I don't get any preview of a notification (e.g. the mail subject etc.)
Is there a workaround for those problems? Because simply isntalling a new lockscreen app, just makes me unlock my tablet twice, which isn't ideal.
Click to expand...
Click to collapse
I followed this guide: https://forum.xda-developers.com/hd8-hd10/help/root-required-completely-disable-enable-t3739257
I just had to do it again today because attempted to use Xposed and wound up getting in over my head and got caught in a bootloop, but at least I can reaffirm that this guide works
---------- Post added at 07:56 AM ---------- Previous post was at 07:49 AM ----------
DragonFire1024 said:
There are also a few Xposed modules that work too.
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
I love all your posts- it's your guide I followed to disable the lockscreen. Unfortunately, Xposed is a bit much for a "noob" like me. I attempted to install it and got caught in a bootloop and had to do a factory reset. Considering what my dad uses it for, the negatives far outway the positives for me to bother with Xposed ever again

Categories

Resources