Related
How do I make Live Wallpapers work on my NC ?
My NC
Rooted w/ adb working
Location Services Fix
Adhock Wifi Working
Zeam 2.6
Thibor69 said:
How do I make Live Wallpapers work on my NC ?
My NC
Rooted w/ adb working
Location Services Fix
Adhock Wifi Working
Zeam 2.6
Click to expand...
Click to collapse
http://nookdevs.com/NookColor_Enable_Live_Wallpapers
Is there a way to do this without adb, such as by flashing the zip file?
ADB frightens me.
timmyjoe42 said:
Is there a way to do this without adb, such as by flashing the zip file?
ADB frightens me.
Click to expand...
Click to collapse
Look at the Nook General page at "Work Around" issues. The OP his some tips. I believe #12 or 13 deals with live wallpaper manipulation with root explorer.
Thanks. The link to the file in #12 isn't working for me. Do you know what it was? (Was it the "LiveWallpapers_NC.zip" file?)
Edit: and do you know what the best program for the Root Explorer is? (Root Explorer was about $4. Is there something free out there?)
Doesn't Auto-Nooter 1.0.1 enable live wallpaper? It must, because I didn't do any ADBing or sideloading that I remember.
Cheers,
kev
timmyjoe42 said:
Thanks. The link to the file in #12 isn't working for me. Do you know what it was? (Was it the "LiveWallpapers_NC.zip" file?)
Edit: and do you know what the best program for the Root Explorer is? (Root Explorer was about $4. Is there something free out there?)
Click to expand...
Click to collapse
Try this link (I was able to download from there. Got the link from NookDevs, it should be valid). Root Explorer is the best way to work around adb most times. It is worth the investment. Just follow instructions in work around post.
http://www.multiupload.com/61YYJTKYTV
I am trying an app called "Super Manager" which is free.
I am confused at item #12, where it says to install "this" file. (I assume the zip file is what is being referred ti?)
Once I download the .zip file, How do I install it? Don't I have to flash it? (Am I only trying to install the LiveWallpapersPicker.apk, and moving the other 2 files into the correct directory in addition to setting the permissions?)
timmyjoe42 said:
I am trying an app called "Super Manager" which is free.
I am confused at item #12, where it says to install "this" file. (I assume the zip file is what is being referred ti?)
Once I download the .zip file, How do I install it? Don't I have to flash it? (Am I only trying to install the LiveWallpapersPicker.apk, and moving the other 2 files into the correct directory in addition to setting the permissions?)
Click to expand...
Click to collapse
I did not look at the zip file, sorry. I did notice that there were a couple of scripts with it that looks like the whole thing would be flashed in recovery. I found this stand alone apk for the app which I would feel more comfortable with. Install it per instructions. I got the download link from the attached thread that shares which wallpapers may be working. Good luck
http://www.mediafire.com/?oymijnnydnz
http://forum.xda-developers.com/showthread.php?t=891593
since I can not post directly in the discussion, I have to open a separate thread.
I used the file for dual touch using insmod and it worked.
Now I wanted to make sure that it is fixed with the phone, I read the procedure and tried to follow her, but I do not find any files bulid.prop ....
Where is it?
Please help me.
build.prop is in
root, system folder
tell me if it works for you, I tried this and I couldn't get it to work.
Ray_jai said:
build.prop is in
root, system folder
tell me if it works for you, I tried this and I couldn't get it to work.
Click to expand...
Click to collapse
using it without changing the files, it works QuickPic, Copilot.
In google maps does not work. Not even in browsers like Opera or Ninesky.
But I thought that by modifying these files, worked in the rest.
Thanks! I found the file "build.prop",
Where is the other file "hw_config.sh"? Because what I found I had no voice "insmod" ...
DomusX10 said:
using it without changing the files, it works QuickPic, Copilot.
In google maps does not work. Not even in browsers like Opera or Ninesky.
But I thought that by modifying these files, worked in the rest.
Thanks! I found the file "build.prop",
Where is the other file "hw_config.sh"? Because what I found I had no voice "insmod" ...
Click to expand...
Click to collapse
hw_config.sh is in ur "etc" folder... are you using root explorer???
You do know you can use the search function OF the root editor too...
DomusX10 said:
using it without changing the files, it works QuickPic, Copilot.
In google maps does not work. Not even in browsers like Opera or Ninesky.
But I thought that by modifying these files, worked in the rest.
Click to expand...
Click to collapse
Not sure what ROM you're using, but you may need this file to get the other apps using dualtouch:
http://forum.xda-developers.com/showpost.php?p=13497850&postcount=49
teapea said:
Not sure what ROM you're using, but you may need this file to get the other apps using dualtouch:
http://forum.xda-developers.com/showpost.php?p=13497850&postcount=49
Click to expand...
Click to collapse
this is the problem?? I've Stock ROM 2.1update1 with firmware 2.1.1.A.06
then, I have to create that file and copy it into /system/etc/permissions with rootexplorer...
now I try this...and you know I do!
EDIT: NOT WORKING...I have create that file (copy and paste the code in the frame in a txt file, and renamed android.hardware.touchscreen.multitouch.xml) then I've paste it into /system/etc/permissions and associated it permission rw-r-r
rebooted and not working...single touch.
yet launched from the console does the dual touch working in some applications ... why?
EDIT 2: Please do not send me to hell, but by creating the file and rebooting, if I launch "insmod" from the console, dual touch works in all apps!
How is it possible, however, that the changes to make it start with phone not work?
I want to work "even" when I restart the phone!
Did you try this version?
http://forum.xda-developers.com/showpost.php?p=13498769&postcount=56
I couldn't get it to work when doing it manually. but when I load it from the SD card through adb it works.
I ended up using the AAIS script and replacing the module in the AAIS with the one in the link.
Ray_jai said:
I ended up using the AAIS script and replacing the module in the AAIS with the one in the link.
Click to expand...
Click to collapse
I use that on the first post dedicated at my firmware 2.1.0.A.06
http://forum.xda-developers.com/showthread.php?t=1064558
manually loaded by terminal emulator work in every app. But, the procedure to autorun this module with telephone when start, don't work.
I do not know which is doing a script AAIS, because I'm not well prepared ... I do not know how to do it ...
use this.
http://forum.xda-developers.com/showthread.php?t=951274
Ray_jai said:
use this.
http://forum.xda-developers.com/showthread.php?t=951274
Click to expand...
Click to collapse
thanks!
With this script you can enable and disable a lot of things ... I can just see if it works ...and let you know ...
I wanted to ask, but what is JIT? what does it do?
thank you in advance for availability ..
EDIT: Works!!! without launching the script, I went just to see how the command was written in the file "hw_config.sh" ...
I corrected, and after restarting, it works!
I was wrong because we put the quotes, but no need to write.
The correct lines of code to be included in the file "hw_config.sh" (at bottom) are:
# load multi touch driver
insmod /system/lib/modules/cy8ctma300_ser.ko
sleep 1
After you have copied into system/lib/modules "cy8ctma300_ser.ko" , mounted it as rw-rr , and edit the file "build.prop" as indicated in the post.
works!!!
thanks!!!!
Has anyone tried to reinstall the stock asus Keyboard app?
I know it's the "keyboard.apk".
I tried to install it via root explorer by moving it to /system/app then giving it all permissions and rebooting. But it still won't show up.
Any ideas?
The stock keyboard isn't inside Keyboard.apk; that only contains the shortcuts for the Asus dock keys. The Asus Keyboard is inside XT9IME.apk.
**Edit**
Never mind I found it on this old post. You need these files:
Needed for software keyboard:
XT9IME.apk
/system/lib/libjni_xt9input.so
/system/lib/libjni_xt9kcm.so
/system/usr/xt9
I yanked these out of the revolver rom and put them in place with root explorer.
Now I'm good to go. Thanks agentdr8.
apollostees said:
**Edit**
Never mind I found it on this old post. You need these files:
Needed for software keyboard:
XT9IME.apk
/system/lib/libjni_xt9input.so
/system/lib/libjni_xt9kcm.so
/system/usr/xt9
I yanked these out of the revolver rom and put them in place with root explorer.
Now I'm good to go. Thanks agentdr8.
Click to expand...
Click to collapse
I know this is an old post, but it's the only thread where I found someone was able to successfully install the Asus keyboard on a custom ROM. I have the files you listed, but I'm unable to copy them to the required folders. I tried with a regular file explorer as well as a root explorer. I am running CM10.1, rooted of course.
jleonard711 said:
I know this is an old post, but it's the only thread where I found someone was able to successfully install the Asus keyboard on a custom ROM. I have the files you listed, but I'm unable to copy them to the required folders. I tried with a regular file explorer as well as a root explorer. I am running CM10.1, rooted of course.
Click to expand...
Click to collapse
So I found another thread which included a file called asus_keyboard.zip which I simply needed to download and install from recovery mode, but after doing that when I select the Asus Keyboard I just keep getting the error message "Unfortunately Asus Keyboard has stopped". And it keeps popping up every 2 seconds until I disable it. Any ideas?
Here's where I found it: http://forum.xda-developers.com/showthread.php?t=1542502&highlight=keyboard
I can get the OUYA controller connected fine, but the button mappings are terribly wrong. I found a keylayout file, but the tablet doesn't seem to want to use it. I tried it with my S3 running CM 11 and it was able to use it and the mappings are fine. I'm running a rooted 10.6.A.0454 and I've done the following.
1. Copied the keylayout file Vendor_2836_Product_0001.kl to /system/usr/keylayout (verified the Vendor and Product #s are correct)
2. Set the group to root and gave it permissions 644 (like all the other .kl files)
3. Rebooted tablet
I don't know why it doesn't want to work because I've gotten that exact file to work on older builds for the tablet, as well as my S3 running CM11. Any suggestions would be appreciated. Thanks.
cain05 said:
I can get the OUYA controller connected fine, but the button mappings are terribly wrong. I found a keylayout file, but the tablet doesn't seem to want to use it. I tried it with my S3 running CM 11 and it was able to use it and the mappings are fine. I'm running a rooted 10.6.A.0454 and I've done the following.
1. Copied the keylayout file Vendor_2836_Product_0001.kl to /system/usr/keylayout (verified the Vendor and Product #s are correct)
2. Set the group to root and gave it permissions 644 (like all the other .kl files)
3. Rebooted tablet
I don't know why it doesn't want to work because I've gotten that exact file to work on older builds for the tablet, as well as my S3 running CM11. Any suggestions would be appreciated. Thanks.
Click to expand...
Click to collapse
CM11 is android 4.4.4 as far as i remember. Stock 10.6.A.0454 ROM is android 5.0.2.
So the file you are copying is from different android version, which seems to be incompatible.
You can update to CM12(.1) and copy the same file to 10.6.A.0454 firmware or update to stock 5.1.1 ROM (10.7.A.0.222).
Secondly there is SixAxis controller app which will (presumably) help you to change keyboard mapping without messing with Vendor_2836_Product... files.
So this way is less difficult, i think. But the app is paid and you need root-access to use it.
I am trying to figure out how to extract the camera app from the stock ROM to use in the CM13 ROM. Partly because I would like to use it for slow-motion video and to experiment with it, but also because I would like to turn this into a learning experience. I've been following instructions to flash ROMs for a few years now, but haven't gone farther than that.
So here has been my experience so far:
- Backed up CM13, flashed stock (rooted), and converted the app to user app in order to back it up.
- I noticed that it would crash on startup as a user app, so I converted it back to a system app as an experiment. It still would crash on startup.
- I decided to try going another route and extracted the stock ROM in SuperR's Kitchen. Got the apk, flashed it in CM13. Same situation: crash on startup as user or system app.
I am unsure where to go from here. Any help is greatly appreciated. Thanks in advance.
Side note: I know there is a questions sub-forum too, but I figured it fit here better as it is about extracting an app to mod the ROM. If I was mistaken, please just move the thread over to the appropriate sub-forum.
Masterjuggler said:
I am trying to figure out how to extract the camera app from the stock ROM to use in the CM13 ROM. Partly because I would like to use it for slow-motion video and to experiment with it, but also because I would like to turn this into a learning experience. I've been following instructions to flash ROMs for a few years now, but haven't gone farther than that.
So here has been my experience so far:
- Backed up CM13, flashed stock (rooted), and converted the app to user app in order to back it up.
- I noticed that it would crash on startup as a user app, so I converted it back to a system app as an experiment. It still would crash on startup.
- I decided to try going another route and extracted the stock ROM in SuperR's Kitchen. Got the apk, flashed it in CM13. Same situation: crash on startup as user or system app.
I am unsure where to go from here. Any help is greatly appreciated. Thanks in advance.
Side note: I know there is a questions sub-forum too, but I figured it fit here better as it is about extracting an app to mod the ROM. If I was mistaken, please just move the thread over to the appropriate sub-forum.
Click to expand...
Click to collapse
Did the logcat give any pointers as to why it might have crashed?
It's a camera app, for MiFavor, and only for MiFavor. It's probably depending on something else from the stock ROM, and that's why it's crashing in CM.
I like this idea. I might even look into modifying the app itself, to see if we can get it working outside of MiFavor.
I don't think I worded it clearly enough, the first time I converted it to a user app and back to system, it was still in the stock ROM. Something about the conversion screwed things up. I'll have to flash stock again at some point and grab logcats while it's working and after I screw it up.
In the meantime, I attached a logcat for everything containing "camera" after it was converted to a system app in cm13. It's kind of harsh to look at it in pure text format, but I used the matlog app with its color coding to record it.
To be honest, I'm not quite sure what I'm looking at with this, or if I went about this in the right way.
EDIT: I have no idea why the logcat is not attaching correctly. I'll need to find some other way of doing it.
It works fine under CM according to a friend. You just need the libs to go along with the app.
Here is the WHOLE folder of ZTE camera, he just put this inside the /system/priv-app/ folder and apparently it's working just fine after a reboot.
https://my.mixtape.moe/znyabg.7z
Remember to press thanks and buy me a beer.
It's still not working properly for me, but here are a few things I noticed:
- When I extracted the app from the ROM using SuperR's Kitchen, that folder did exist in /system/priv-app/ZTE_Camera/. However, the directory was completely empty, unlike your download.
- When I installed the app in CM13 and converted it to a system app, it moved to /system/priv-app/ rather than /system/priv-app/ZTE_Camera/.
- I copied the lib folder to /system/priv-app/, didn't work. I then created the folder ZTE_Camera and copied both lib and the apk into it. Didn't change anything. Of course rebooting with each change. I didn't think this would work in the first place, as the application shortcut on my home screen points to /system/priv-app/.
Definitely thanks though for helping me out. Beer... that's another matter. Nasty stuff that is. I can just hear people yelling at me behind their screens lol.
Was it a deodexed ROM? Might need to try it with the odex files? When I check /system/priv-app/ZTE_Camera, there's also an "oat" folder with odex files since this hasn't been deodexed...
Or maybe SuperR's kitchen was trying to automatically deodex while you were extracting.
To be honest, I never understood odex, just throwing ideas out at this point.
Masterjuggler said:
It's still not working properly for me, but here are a few things I noticed:
- When I extracted the app from the ROM using SuperR's Kitchen, that folder did exist in /system/priv-app/ZTE_Camera/. However, the directory was completely empty, unlike your download.
- When I installed the app in CM13 and converted it to a system app, it moved to /system/priv-app/ rather than /system/priv-app/ZTE_Camera/.
- I copied the lib folder to /system/priv-app/, didn't work. I then created the folder ZTE_Camera and copied both lib and the apk into it. Didn't change anything. Of course rebooting with each change. I didn't think this would work in the first place, as the application shortcut on my home screen points to /system/priv-app/.
Definitely thanks though for helping me out. Beer... that's another matter. Nasty stuff that is. I can just hear people yelling at me behind their screens lol.
Click to expand...
Click to collapse
I'm sure it works, friend confirmed it works on CM13 and I'm using it on BrokenOS. To clear it up.
It should be /system/priv_app/ZTE_Camera. And inside that folder should be the apk along with the lib. If you just extract the zip I gave you into priv_app it should just work. I have no idea why it doesn't work for you. Everything about the camera works. Slomo, video h265, the works.
You can try making a backup of the stock camera app using titanium backup then install it on your phone after flashing CyanogenMod. What I would do is flash zad miix then back up the stock camera app with titanium backup. Then transfer the back up to your PC. Then flash CyanogenMod and reinstall the camera app with titanium backup.
as already I will have this phone I start doing this mods
if anyone can search the file this and tell me if an entry is interesting?
I'm currently using LOS 14.1, and the method suggested does not work - File Manager throws an error about R/W, TWRP claims /system is empty, and ADB push says "Successful" but isn't.
NadavCE said:
I'm currently using LOS 14.1, and the method suggested does not work - File Manager throws an error about R/W, TWRP claims /system is empty, and ADB push says "Successful" but isn't.
Click to expand...
Click to collapse
It is working for me, just copied the files with root explorer to priv-app, restarted and it is up and running.
Thanks @BlazingBullets for providing the files!
PS. the only problem so far is that you can't access the pictures right through the app, i think we need the zte gallery for that.
lian00 said:
It is working for me, just copied the files with root explorer to priv-app, restarted and it is up and running.
Thanks @BlazingBullets for providing the files!
PS. the only problem so far is that you can't access the pictures right through the app, i think we need the zte gallery for that.
Click to expand...
Click to collapse
Root Explorer doesn't work for me either. Did you root with SuperSU or with the Lineage root zip?
NadavCE said:
Root Explorer doesn't work for me either. Did you root with SuperSU or with the Lineage root zip?
Click to expand...
Click to collapse
Used SuperSU 2.79SR3.
I can confirm using the files provided works. I have the stock MM camera working with all of it's shooting modes !
Any body have the files in a .zip they can upload? I have no computer access and the few apps I tried on my phone seem to corrupt the files.
First app I tried extracted the 7zip file just fine.
NadavCE said:
Root Explorer doesn't work for me either. Did you root with SuperSU or with the Lineage root zip?
Click to expand...
Click to collapse
You have to disable the write-protect on the system partition: in a terminal emulator, preferably in TWRP, type out:
Code:
reboot disemmcwp
Erahgon said:
You have to disable the write-protect on the system partition: in a terminal emulator, preferably in TWRP, type out:
Code:
reboot disemmcwp
Click to expand...
Click to collapse
Thanks, that did it. Copied successfully to /system/priv_app, but it doesn't show up after a reboot. When I accessed the folder and tapped the APK, I got "there is a problem parsing the package."
NadavCE said:
Thanks, that did it. Copied successfully to /system/priv_app, but it doesn't show up after a reboot. When I accessed the folder and tapped the APK, I got "there is a problem parsing the package."
Click to expand...
Click to collapse
Maybe the app permissions are wrong?
Erahgon said:
Maybe the app permissions are wrong?
Click to expand...
Click to collapse
Should I give it full permissions then?
---------------------------------------------------------------------------------------------------------------------------
Update: After giving everything (ZTE_Camera folder, the APK, the lib folder, the arm folder, and all the libs) full permissions, the app works. However resolution is limited to 8Mp 4:3 (3200 x 2400). Can anyone else confirm this?