Hi, I want to ask some questions to you guys. Can somebody help me!
I have exposed in my Moto E4 Plus xt1770 Nicklaus. I trying to mod my battery icon, so I extract the framework.apk file in folder system, I changed the battery icon, and make new framework.apk (my mod), I replace and reboot. After boot I found nothing changed. I really confused from where the device get the default battery icon, because I had replaced that. But some is more interesting is, after that I can mount my data/system partition (I forget about data or system partition) in twrp, so I can't restore that with twrp. My device is work, but I can mount some partition in twrp so I think should be some trouble. Any way I have another case. I get flash my device. After that I rooting with magisk and install Xposed again, now I try changing boot animation. I replace the boot animation.zip in system/media and reboot. But I got the boot animation is not changed, from where the device got the default video, I had replaced . Any way I sure my procedure from all modding I do is right. So I start to thinking. I think Xposed can manipulate the system UI and framework,
so I wanna know are modding framework apk or systemui is have different way for device with Xposed n device without Xposed?
Sorry if my explanation is not clear, but can someone to help me for understanding what going on. Thanks:laugh:
I just flashing my phone, so I don't have XPosed in my phone. After rooting I tried replace bootanimation.zop in "dev/system/media", after reboot I found my boot animation still default. But deferent when XPosed installed in my phone, in case without XPosed, my phone doesn't have any issue like, Bluetooth share stopped, systemui stopped. I got my phone very normal after I'm using for couple hours.
So now I think I do wrong modding procedure,
*Are true if you want to change battery icon, you can do it with modding framework.apk (replace the default icon)?
*Are true you can change boot animation with replace boot animation.zip in "dev/system/media"?
I do that, but all still default. Huft...
I think, I don't wanna modding it any.
Actually I have made my own battery icon. I really want to use it. You know, I'm newbie. So it's so difficult n much time to made it .But now I give up, I got stuck.
Related
First off, thanks to everyone for helping make the Nook Color such a vibrant community. There's a wealth of information here and I'm really grateful for it. I love the NC and it's great that we can unlock its full Android potential thanks to the hard work of the folks here... both the people that make the tools, and the people that help support it.
I am curious to know if anyone out there has some custom boot animations that aren't so flashy. Both the wife (who also rooted her NC) and I suffer from migraines, and the bootup sequence can be really painful with the bright flashing colors. Something a little more subdued would be preferable.
I'm also not sure if I can run a custom boot animation on the NC without using Cyanogen? I've upgraded to 1.4.1 today (which promptly went into a boot loop which MN 4.6.16 didn't solve, so I reverted to 1.2 and then went back to 1.4.1 and got it re-rooted with MN 5.12.20 properly... thanks again for all the info here!), so I'm just using a rooted stock system. I searched for boot animations on the forum but most of the results were pages of people mentioning which animation they got stuck on while trying to root
Also, does anyone know anything about NookDevs.com going dark? Their site just shows a blank HTML page and any old links give a 404. It's a pity, because their wiki was a bit more in-depth than the NC wiki here.
stormerider said:
[...] I am curious to know if anyone out there has some custom boot animations that aren't so flashy. Both the wife (who also rooted her NC) and I suffer from migraines, and the bootup sequence can be really painful with the bright flashing colors. Something a little more subdued would be preferable.
Click to expand...
Click to collapse
I'm also not a fan of the early MN startup screens, but there's an easy fix (see below).
I'm also not sure if I can run a custom boot animation on the NC without using Cyanogen?
Click to expand...
Click to collapse
Yes, you can. MN changes it on B&N firmware.
If you've already over-written the boot animation by running MN, you'll need to find a replacement somewhere. Not sure how to do that. However, if you either haven't replaced it yet or are willing to do a factory reset, you can tweak the ManualNooter scripts. If you open the MN .zip file, go into /META-INF/com/google/android/ and edit the updater-script file with a text editor. Look for the 3 lines that begin with "ui_print("Installing Boot Animation...");" and comment them out by putting '#' characters at the start of each line. There are 3 lines in 5.12.20. Write the modified version to that same location, and then run it to (re)root your unit.
Alternately, you could modify /data/local/bootanimation.zip in manualnooter-5.12.20.zip. Hack down the updater-script, and you can have it install ONLY the boot animation if you want to try a few variations.
Finally, if you've already rooted, you could try plugging a replacement in to /data/local/bootanimation.zip directly. No guarantees on this one, though.
bobstro said:
I'm also not a fan of the early MN startup screens, but there's an easy fix (see below).Yes, you can. MN changes it on B&N firmware.
If you've already over-written the boot animation by running MN, you'll need to find a replacement somewhere. Not sure how to do that. However, if you either haven't replaced it yet or are willing to do a factory reset, you can tweak the ManualNooter scripts. If you open the MN .zip file, go into /META-INF/com/google/android/ and edit the updater-script file with a text editor. Look for the 3 lines that begin with "ui_print("Installing Boot Animation...");" and comment them out by putting '#' characters at the start of each line. There are 3 lines in 5.12.20. Write the modified version to that same location, and then run it to (re)root your unit.
Click to expand...
Click to collapse
I just finished getting everything set back up (I hit a setting page that did a reset on my unit... not so happy. Running Titanium Backup now...), so I'm not really keen on re-running MN. I'd rather just tweak what needs to be done, as things seem to be a little bit fragile and breaking things requires a lot of time to get back up and running.
Alternately, you could modify /data/local/bootanimation.zip in manualnooter-5.12.20.zip. Hack down the updater-script, and you can have it install ONLY the boot animation if you want to try a few variations.
Finally, if you've already rooted, you could try plugging a replacement in to /data/local/bootanimation.zip directly. No guarantees on this one, though.
Click to expand...
Click to collapse
Does MN override the bootanimation binary to support /data/local, or does bootanimation support that location directly? I did some searching and it looks like some people are patching the binary so it works with more standard Android boot animations and it was unclear to me if the /data/local path was part of that customization as well or not.
Also, I was in part posting to see if anyone had any recommendations for the animations themselves. Graphics work is definitely not my forte, I'm more of a server guy
bobstro said:
I'm also not a fan of the early MN startup screens, but there's an easy fix (see below).Yes, you can. MN changes it on B&N firmware.
If you've already over-written the boot animation by running MN, you'll need to find a replacement somewhere. Not sure how to do that. However, if you either haven't replaced it yet or are willing to do a factory reset, you can tweak the ManualNooter scripts. If you open the MN .zip file, go into /META-INF/com/google/android/ and edit the updater-script file with a text editor. Look for the 3 lines that begin with "ui_print("Installing Boot Animation...");" and comment them out by putting '#' characters at the start of each line. There are 3 lines in 5.12.20. Write the modified version to that same location, and then run it to (re)root your unit.
Alternately, you could modify /data/local/bootanimation.zip in manualnooter-5.12.20.zip. Hack down the updater-script, and you can have it install ONLY the boot animation if you want to try a few variations.
Finally, if you've already rooted, you could try plugging a replacement in to /data/local/bootanimation.zip directly. No guarantees on this one, though.
Click to expand...
Click to collapse
No need to go through all of that trouble. If you don’t like the boot animation in MN, simply go to /data/local, and delete or rename bootanimation.zip to bootanimation.zip.old, this will take you back to the factory boot animation.
The NC will work with any boot animation you can think of, you just need to follow a few basic rules. The rules are outline at nookdevs.com, Link, the site is down at this time, so here is a link for the cached site, Link.
If you are going to take a boot animation from another device, or from online, and edit it for the NC, the most important step is to NOT use any compression when you zip it back up. You can screw-up almost every other step, and still have a working boot animation, but if you compress the zip, it will not work at all.
CM 7.1.0-encore note
FYI: After putting CM 7.1.0-encore on my NC (and then wanting to change the boot animation), I discovered that the path is: /system/media/bootanimation.zip
Awesome. thanks for the info. Starting to build my own intro...
I want to further u dressed what I'm doing wrong in changing lock.ogg and other sound and animation files. I understand that the qmg files are made in a way to make it more difficult to change but I'm doing something wrong. Even completely deleting the stock mini loop animations with my root browser has No effect. They aren't their but they continue play on every boot. I recently flashed a lollipop animation that is working but upon looking at the way the the files were done using .Baker did not work for me. I just want to understand what exactly I'm doing wrong. Existing file rename with .bak place new file in required location renaming to Samsung miniloop etc. Change permissions to match making sure the root browser is in r/w. AND NOTHING.... I really want to understand r/w and later decompose/recompile but this first hurdle with file changing is really messing with me. Any help is appreciated
pyroman2425 said:
I want to further u dressed what I'm doing wrong in changing lock.ogg and other sound and animation files. I understand that the qmg files are made in a way to make it more difficult to change but I'm doing something wrong. Even completely deleting the stock mini loop animations with my root browser has No effect. They aren't their but they continue play on every boot. I recently flashed a lollipop animation that is working but upon looking at the way the the files were done using .Baker did not work for me. I just want to understand what exactly I'm doing wrong. Existing file rename with .bak place new file in required location renaming to Samsung miniloop etc. Change permissions to match making sure the root browser is in r/w. AND NOTHING.... I really want to understand r/w and later decompose/recompile but this first hurdle with file changing is really messing with me. Any help is appreciated
Click to expand...
Click to collapse
Maybe you need to not leave that renamed file in the same directory?
SiNJiN76 said:
Maybe you need to not leave that renamed file in the same directory?
Click to expand...
Click to collapse
I tried deleting them altogether and they still play. And this really isn't matter of just having a custom boot animation because I can easily flash a zip file but I want to do it myself. Is it really necessary to use the Samsung theme to recreate a working animation for my phone
pyroman2425 said:
I tried deleting them altogether and they still play. And this really isn't matter of just having a custom boot animation because I can easily flash a zip file but I want to do it myself. Is it really necessary to use the Samsung theme to recreate a working animation for my phone
Click to expand...
Click to collapse
I would recommend downloading a boot animation that works on this phone and see what files you have to modify. I know for sound it is 3 of them.
BAD ASS NOTE 4
I did with a custom matrix boot animation and went and looked at all the files and tried my best to recreate what had already been done but all it did was take the animation away completely and put me in bootloop
pyroman2425 said:
I did with a custom matrix boot animation and went and looked at all the files and tried my best to recreate what had already been done but all it did was take the animation away completely and put me in bootloop
Click to expand...
Click to collapse
Link me to this and I will see what is up. I know of only one boot animation that was made for this phone. I could be wrong but let's check
BAD ASS NOTE 4
---------- Post added at 12:26 PM ---------- Previous post was at 12:16 PM ----------
http://forum.xda-developers.com/showthread.php?t=2943808
BAD ASS NOTE 4
---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------
That be the only one I came across that was done right without having to go in and change things
BAD ASS NOTE 4
http://forum.xda-developers.com/note-4/themes-apps/bootanimation-matrix-flash-recovery-t2952816
All of the boot animations and the certain shutdown animation work flawlessly on my sm-n910t running on hyperdrive RLS3. I used that lollipop animation until I found these it was jumpy but better than stock
pyroman2425 said:
http://forum.xda-developers.com/note-4/themes-apps/bootanimation-matrix-flash-recovery-t2952816
All of the boot animations and the certain shutdown animation work flawlessly on my sm-n910t running on hyperdrive RLS3. I used that lollipop animation until I found these it was jumpy but better than stock
Click to expand...
Click to collapse
If these work what is it that you are trying to do? I think I missed something.
BAD ASS NOTE 4
In the original post I inquired on what issue I'm having with moving/changing/renaming files and their permissions. I have tried everything I have seen on the the forums ie. Renaming original ending with .bak placing new file within the directory and renaming to match the original file. Changing permissions then reboot into recovery. Wipe dalvik and cache (even tried not wiping) reboot system anf either nothing at all or the original samsung boot. Ive tried boot animation changer and six different types of file explorers (2 paid versions) hours and hours of youtube videos and thread after thread to find my solution. I see that qmg files most likely can only be exchanged with qmg files created via samsung themer. Im currently using an sm-n910t on the hyperdrive rls3 rom and just recently flashed the bioshovk kernel in the hopes that it would support .zip boot animations but it doesnt quite work like that. I tried the starkissed kernel and the nadia kernel to end in softbrick. I am extremely interested in all of these things and eagerly look forward to decompile/recompile but as it stands im stuck at unchangable boots lol. Im really hoping to see possibly a video of the changes being done on an actual note 4 not an s5 or anything else. As always any info is greatly appreciated
Hello,
I'm a beginner lost in reading all the useful information on this forum.
I started with the idea to reduce the permissions of applications of my Razr I.
Google pointed to this http://www.xda-developers.com/protecting-your-privacy-app-ops-privacy-guard-and-xprivacy/
And I'm really happy and surprised about all information I can find here, thank you that much for
making this possible to all of you!
As today I feel ready to start playing around with my phone I wanted to ensure I understood the items right.
May be for you it takes only some seconds to verify my guess and can give a short notice
about Step 2 or 3 is easier to become implemented.
Step 1.) I wanted to do a full backup before I start, following this thread:
So I'll install ADB on my PC and run "adb backup -f FullBackup.ab -apk -all"
This works on a Razr I with 990.43.74.xt890.Retail.en.EU - of the shelf and is not risky at all - or?
Could you pls. tell whether it is really true I can switch back to my backup if I'm not happy with my System?
Step 2.) My first intention was to root my device and install Xposed framework
http://forum.xda-developers.com/showthread.php?t=2299428
http://repo.xposed.info/module/de.robv.android.xposed.installer
And to use Permission Master out from google play store
First of all I wanted to ask you whether this is feasible technicaly and esp. for a beginner?
Alternative to Step 2 Step 3?
Step 3.) In general I'm happy with my Razr I Android 4.4.2 (990.43.74.xt890.Retail.en.EU)
But I'm wondering whether it would be easier or has less risk to use a custom ROM instead of implementing Step 2.
By reading in this forum I found out there is a planty of features FM-Radio, enhanced stand-by current ,
to get rid of preinstalled aps and so on.
I'm an embedded developer but do not have the overview about the architecture of Android devices, what I got so far is:
There is a bootloader which needs to be changed from OEM closed to open.
There is a boot partition I flash ROMs in.
I need some tools on my PC combined with SDK and Motorola drivers to allow a USB-Debuging and flashing.
And sure as always once your bootloader is damaged you are lost, so I understand even backup will not help here.
So I'll keep my fingers crossed.
Thanking you in anticipation and pls accept my excuses about my english and stupid beginners questions.
Best Regards
gonso
PS:
As I main entry point I used the
http://forum.xda-developers.com/razr-i/general/index-razr-t2832722
from there I'll try to get ADB, drivers etc.
Hi GonsoXDA,
Step 1: I have never used it. Didn't even know that it existed. On the internet there are numerous people who uses it and it seems to work. Maybe someone else can give some info about this or just try it. U can try it with a non-important app and see if it works. Just backup it, delete it and restore it.
Step 2: This works just fine. But do know 3 things:
1. First root: To get root on stock rom, u need to use kingsdroot methode afaik. And that one sends your IMEI to some rare ip adress. I personnaly don't trust this and stay away from it, but there are many people who use it.
2. Xposed requires a recovery to install the framework. It can be done mannually or by the app i suppose. With only root u don't have a recovery on your device that can perform such action.
3. If something goes wrong only a full restore with RSD-Lite can most of the time help u out. Because u don't have a recovery that works than.
Step 3: We only have 2 full roms. 1 for JB (stock) and a working CM11 rom (kitkat).
Only the Jellybean roms support fm-radio, on every newer rom fm-radio is cut out of the audio firmwares. The risk of going to this is even less as Step 2, because u can do a full backup and restore of ur phone. ( I would chose for this if u want to play a bit with the phone and ur warranty is already out of years)
The gereneral idea about the android architecture is this (it is different for almost every device and the Razr I has many more thing to hold into account, but if u are here only for the roms and xposed, there is no more to know):
Bootloader: Is like an uefi bios for PC, but then for android. It also contains fastboot
Bootimage(boot): Has all the info like kernel and ramdisk to boot the system
Recovery: Is like 'boot', but boots into the recovery partition that lets u change every aspect of the device if u know how. Its mainly used to flash a custom recovery to, backup and restore a nandroid backup and flash/wipe roms, mods, (all/specific) data and packages.
Systempartition: Is the system the boot boots into. It's android.
Datapartition: Where all the user data is stored.
Cachepartition(dalvik): Where all cache is stored and in earlier android versions also dalvik. But not now anymore.
Fastboot: To flash/wipe the above partitions and many more (needs drivers)
Adb: To push, pull, command things in system or recovery (needs drivers)
Sdk: contain the abd and fastboot packages, but aren't needed for adb and fastboot because with the right drivers can work on there own (see the internet)
If u have a custom recovery and only change things on the system, data and cache partition there is almost no way to damage the phone. There is always a backup through recovery. As long as u stick to the things u can do in recovery.
The only thing tha can mesh up your phone beyond repair is doing wrong stuff withint the bootloader and other inner parts in the phone(like i did to get newer kernel working) or u are in bad luck and you internal memory blocks. See 'Super brick samsung phones' (emmc error).
I suggest:
- Unlock your bootloader
- Install custom recovery
- Make a backup with the recovery
- Do what u want, xposed on stock rom, try CM11?
- If things won't boot, restore through recovery
And always, read up before doing anything. There are thousands of articles about android, flashing things, repairing android, using adb and fastboot. AND ALWAYS HAVE A BACKUP PLAN!
Hello,
always having a backup seems not to be that easy.
So I unlocked my boot loader and tried to install twrp2850 and twrp2860 via mfastboot.
The mfastboot with 533.353kB caused the following "(bootloader) Variable not supported!"
I rebooted into bootloader and tried recovery -> horizontal Android man with a red !-rectangle
After reboot to normal power up my phone seems to be in factory reset, all my data is gone :crying:
ok crying dosn't help so I looked around and tried with another mfastboot 186.178kB and recoverycwm6.0.5.1.4.img.zip
http://forum.xda-developers.com/showthread.php?t=2441224
The twrp I tooked from here: http://forum.xda-developers.com/showthread.php?t=2278483 seems not to work.
I did a backup with cwm is there a change to get back my data? I think I know the answer.
In the meanwhile I installed
http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855
And will try to install
http://forum.xda-developers.com/xposed/modules/tool-installer-xposed-installer-zenfones-t2983589
Thank you for the help, work and excuse the stupid beginner posts.
Regards
gonso
gonsoXDA said:
Hello,
always having a backup seems not to be that easy.
So I unlocked my boot loader and tried to install twrp2850 and twrp2860 via mfastboot.
The mfastboot with 533.353kB caused the following "(bootloader) Variable not supported!"
I rebooted into bootloader and tried recovery -> horizontal Android man with a red !-rectangle
After reboot to normal power up my phone seems to be in factory reset, all my data is gone :crying:
ok crying dosn't help so I looked around and tried with another mfastboot 186.178kB and recoverycwm6.0.5.1.4.img.zip
http://forum.xda-developers.com/showthread.php?t=2441224
The twrp I tooked from here: http://forum.xda-developers.com/showthread.php?t=2278483 seems not to work.
I did a backup with cwm is there a change to get back my data? I think I know the answer.
In the meanwhile I installed
http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855
And will try to install
http://forum.xda-developers.com/xposed/modules/tool-installer-xposed-installer-zenfones-t2983589
Thank you for the help, work and excuse the stupid beginner posts.
Regards
gonso
Click to expand...
Click to collapse
Than u know the answer, it is no I think.
Both twrp images should work just fine, but always chose the latest. The message "(bootloader) Variable not supported!" doesn't do anything So don't worry about that one. There should be a lot more in you log that the message if twrp didn't install. U did extract it and flash it with the command: mFastboot flash recovery <recovery-image>. Where <recovery-image> could be C:/users/*/Downloads/recovery.img.
Hello,
yes sure "The secret of health for both mind and body is not to mourn for the past, worry about the future"
So I use CM11 now for about 2 days and I'm really impressed, so far everything works :good: THANK YOU!!!
As I asked already I installed XPosed and Permission Manager, but I found XPrivacy might be the better solution and switched to this.
(Today I do not have all the technical background to judge whether it is technically equivalent, but I'll investigate on it)
Esp. one thing I'm wondering, why XPrivacy is reading my Contacts once I check the permissions of an app?
But the more important thing I recognized differences between CM11 and the Stock ROM. One is the Entry
"Privacy" in the settings. It seems to be more or less the XPosed and XPrivacy, or?
But it seems the Restrictions are not shared, so I can restrict in the one and do not see the restriction in the other tool.
So first is there a risk to use both, is it useful or just doing the same twice.
Thank you
Gonso
gonsoXDA said:
Hello,
yes sure "The secret of health for both mind and body is not to mourn for the past, worry about the future"
So I use CM11 now for about 2 days and I'm really impressed, so far everything works :good: THANK YOU!!!
As I asked already I installed XPosed and Permission Manager, but I found XPrivacy might be the better solution and switched to this.
(Today I do not have all the technical background to judge whether it is technically equivalent, but I'll investigate on it)
Esp. one thing I'm wondering, why XPrivacy is reading my Contacts once I check the permissions of an app?
But the more important thing I recognized differences between CM11 and the Stock ROM. One is the Entry
"Privacy" in the settings. It seems to be more or less the XPosed and XPrivacy, or?
But it seems the Restrictions are not shared, so I can restrict in the one and do not see the restriction in the other tool.
So first is there a risk to use both, is it useful or just doing the same twice.
Thank you
Gonso
Click to expand...
Click to collapse
That's a sentence.
Why XPrivacy needs it i don't have a clue. For that sort of things u need to be by the dev of the app.
CM has a lot of features out of the box compared to stock, but stock is most of the time a bit more optimized in terms of proprietary stuff like camera.
So as u noticed, CM had an inbuilt security app. This app (CM) and XPrivacy don't share there settings, so that's the difference u see. But most likely if u disable something in one of the apps it is disabled even tho the other doesn't say it because it doesn't know of it.
I don't think it will be a risk. They both do the same thing, but they don't know about it. To be on the safe side, just use one and restore the other to default. U can always search on the web if they don't get along.
U can now make a full backup, so everything can be reverted and your data should be relative safe.
Hello,
thank you again - I now find the answer by reading in the development part of the forum. For me as a beginner it is sometimes not easy to interpret the discussions there.
If accepted I will use the thread now as a kind of diary, may be some other users will have similar destinations and my learn from my mistakes.
So to answer my question a little more detailed, but with less background know how than Hazou. Pls. do not trust me I'm a beginner, I have not analyzed the code just the behavior - feel free to correct or contradict my words!
The XPosed is in the area of permissions just a framework which allow other modules to put some code between an app requesting permissions and the Android core granting this permissions. The Xposed it self doesn't handle settings or permissions you did in modules like the CM Privacy, Permission Manager or XPrivacy.
As a result I came to the same conclusion it is not a risk, but an overhead to have more than one pice of code between the app requesting permissions and the Android core. -> My proposal: Do not use more than one of this Permission control apps in parallel.
From the privacy perspective the Permission is just a starting point, it allows you to hide your private information from the app. On the other side many apps will need access to the data to work and most of them are able to connect to the internet.
So I realized the next step would be the restriction of internet usage of apps. Here permissions are sword but we need a scalpel, to separate the necessary from the unwanted connections. This scalpel could be AFWall+ and "Netzwerk Log", this is a firewall and a sniffer.
What I can say to day the apps run on CM11 installed on my Razr I.
So it looks like I see my destination raising on the horizon and I will try to formulate it in the following order:
1.) Hide Contacts, Calls and SMS from Apps who do not need this to work -> XPrivacy
2.) Disable some Android features I think I don't need.
(e.g. Captive Portal Check - settings put global captive_portal_detection_enabled 0)
3.) Restrict the internet access of some apps to servers they need to connect. ( e.g. E-Mail client is restricted to connect to the mail server)
4.) Limit the access to my pictures, stored on SD card. [I have not found a solution so far]
If you read this I think 1 is reasonable for most of you, even if you do not have deep Android or Network know how (as I have), you just restrict the permissions - if app crashes or doesn't do the job you expect you may permit access or uninstall the app. (XPrivacy allows you also to fake data)
3 is a usual task of a network administrator, if you are used with iptables it is just work. I'll try to find out whether there is somewhere a source of "Templates". Usually the network admins share there common settings based on services, once I find out I'll post.
To restrict the access to SD Card I only see the change to extend the sandbox of Android to the SD and to hide files which does not belong to the app. As I would store my pictures on SD as I would store my Navi Data, but neither the Navi app should see my pictures nor the Cam and Gallery my Navi Data. ...
I don't know whether there is an app out there but It should be possible the same way like XPrivacy fakes the other data.
Thank you
Gonso
Hello,
Most of the time I used the numbers to just put in the extension, so if I want to call 0049 9876 54 321 I put the numbers 321 the Motorola dialer will show a list of all contacts where the number contains 321.
Some Numbers of contacts are not shown as well, seems if a contact has more numbers only one or two are shown.
The CM11 dialer doesn't show the number, is there a setting to get this feature?
I tried to get my Stock dialer back, so I copied dialer.apk from stock into the /system/sec-app/ directory of the CM11 and restarted the phone -> doesn't change the dialer ....
Any proposals? I'm terrible sorry for my stupid questions, I read several threads and still no idea about a possible solution
Gonso
PS: CM11 file manager shows a secure storage /storage/emulated/0/storage/secure - what is the algorithm used for the encryption.
gonsoXDA said:
Hello,
Most of the time I used the numbers to just put in the extension, so if I want to call 0049 9876 54 321 I put the numbers 321 the Motorola dialer will show a list of all contacts where the number contains 321.
Some Numbers of contacts are not shown as well, seems if a contact has more numbers only one or two are shown.
The CM11 dialer doesn't show the number, is there a setting to get this feature?
I tried to get my Stock dialer back, so I copied dialer.apk from stock into the /system/sec-app/ directory of the CM11 and restarted the phone -> doesn't change the dialer ....
Any proposals? I'm terrible sorry for my stupid questions, I read several threads and still no idea about a possible solution
Gonso
PS: CM11 file manager shows a secure storage /storage/emulated/0/storage/secure - what is the algorithm used for the encryption.
Click to expand...
Click to collapse
Stock CM dialer doesn't have that function afaik. The moto one doesn't work because it needs the Moto framework to work. Just download a dialer U trust from the playstore.
I don't have any clue about the secure storage, sorry.
I'm sure this is the right spot since it has to do with troubleshooting. Okay here goes, so I've looked in a lot of places in the nexus 6 and Samsung sections and cannot find any info on how to remove the binary for Samsung devices (I know, let me explain first) to be able to boot animation screens.... So, let me back up a bit and explain why I'm an idiot. I've been using rom installer to install boot screen animations for my rooted nexus 6 with 6.0.1 Marshmallow. Well, I noticed that some were the incorrect size for my phone when I installed them. I had noticed an option in the app under room extras to install binary to allow boot screen animations (boot animation fixer). I was in such a hurry that I didn't notice that right above it said Samsung. I foolishly installed it, it rebooted and now the boy animation is a plain Jane google writing in white with no animation. Can't remove it or revert to backup because all my backups got corrupted somehow. So now I thought if I can reverse this somehow by deleting the binary, or script, or whatever, it will fix it. I did research on the app and can't find out where it installs the binary to. I came on here and looked in the Samsung section as well as the nexus 6 section, which led me to ask for help. I've looked where the boot animations are stored on the system and there's nothing there and I'm worried if I dig anywhere else blindly I'll have to wipe and install 6.0.1 and root all over again, using up a LOT of my data to reinstall a LOT of apps that I have. I have like 239 apps so I would like to make that a last resort. The phone boots fine, I just don't like the bland boot animation. I want to show off the different animations that I use. I would appreciate the direction anyone could lead me in to solve this goof up that is my fault, but hey, I'm learning a lesson here.
EDIT: I forgot to mention that I did find the XDA forum on the binary samsungani related to this (/system/bin/samsungani) and the boot animation binary (/system/bin/bootanimation) and deleted them. However, this did not change a thing.
I mean, as long as you're able to boot up, why not just install Titanium Backup and backup the apps. Reinstall your rom and just restore the apps, I would say that would be an easier fix. That way you won't be using any data.
The problem is, as you yourself found it, the bootanimation.zip is missing. Copy one in system/media, give 644 as permissions (rw-r--r--). And there you are.
Sent from my Nexus 6 running cyosp using Tapatalk
Hi everyone, I am new to this forum so excuse me if this isn't the right section to post my problem.
so I tried to change the theme of my Samsung Galaxy Ace S5830 after I install a custom ROM in it, so I installed ROM toolbox Lite and I tried to change the phone's theme from there but it didn't work, after that I searched for some apps (I thought that my phone needed those apps to apply the themes from ROM Toolbox Lite) apps like : Theme chooser ,Theme changer, Theme manager and I kept rebooting each time I installed a theme thinking that what must be done so my phone can load it. but nothing changed, so after some searching on google I found a topic in this forum that has some APK files to choose from to change the phone's theme and it must replace Touchwiz30.apk in the System/app directory and give it the permission to write , read and read but I didn't find it with that exact name ,in my case it was called TouchSpaceWiz50.apk so I deleted it and went and tried to replace it with the one I've downloaded except I couldn't give it the permission and I got an error message that says I can't change some system files permissions.
so I ended up without the file TouchSpaceWiz50.apk in my System/app directory not to mention that I wasn't able to go to the home screen.
so I turned off the phone and on again only to find out that the phone is frozen on the boot animation screen, it doesn't keep rebooting just stuck at the boot animation that keeps playing.
I was able to fix this problem by re-installing the custom ROM from my SD-Card. but the main questions is why I wasn't able to change the theme via ROM Toolbox Lite when I have a custom Rom that includes ThemeChooser? and why the other apps didn't work as well? and is there another way to install themes? because I wasn't able to find any. and thanks in advance.
I am sorry if my post is so long I just wanted to explain what happened in details.