I had a custom boot animation and boot sound working perfectly, and then I flashed CM7.03. Now no master what I do, I cannot get the bootsound working again.
Initially I used a shell script based on a zip written by stevo for the evo (i think), and everything was fine. The shell script was a one-off that enabled bootsound.
I traced back through everything, and other than added echoed lines in both build.prop and local.init.rc, which are duplicates, but shouldn't cause any problem (and also, is it possible to edit a text file using the root explorer? I ask because I tried to clean up both of the above files this way, and my changes did not take...permissions were correct too), everything was fine--as it was before.
Thinking maybe something happened to Stagefright, I downloaded a streaming music app, but everything seemed fine, so that is not the issue.
Attached is a copy of the bash script that I used. I ran it from the terminal after cd'ing to /sdcard/root, and making sure the system wad mounted R/W.
I have been seeing-- and also getting questions from others-- whose bootsound also suddenly stopped working after the recent update to CM.
Can anyone figure this out for me?
Again, while doing all my diagnostics above, I double checked both permissions and my path variable and they were as they needed to be in both cases.
Thanks!
Syntropic
Sent from my HTC Glacier using XDA Premium App
I am a newbie here.
For those who is interested.
there is a recent CM7 SMod 1.0 ROM [link: http://forum.xda-developers.com/showthread.php?t=1142439]
I was interested in the MIUI Camera. What i have done is i downloaded the rom, extracted the MIUIcamera.apk,using root explorer; move the apk to /system/app, change the permission and reboot. [off course you can the alternative adb push method]
everything work fine, but sigh....
720p video recording not supported.
credit goes to sokolik315, CM dev and off course MIUI dev
MIUICamera.apk
by the way here is the MIUIcamera.apk for those who want it
Working well on my N1 with CM7 nightly #113 (with DarkTremor Apps2SD).
Just a couple of notes, for clarification:
- No need to rename this apk, copy it as is to /system/app
- If you're using Root Explorer, long-click the app and choose "Permissions" from the popup menu...Then check-enable EVERYTHING from the options that come up (or if you know exactly what you're doing, just the ones that are needed).
- After reboot, you'll now have 2 apps called 'Camera' in your apps list. The one with the white border on the icon is the MIUI Camera!
A few "kinks" and gotchas to expect with this:
- On my N1, the text in the settings is too large and is either cut-off or is funky formatted. I can still get to all the items though.
- The zoom doesn't seem to work via screen-press, but rather having to use the trackball
Thanks for yoinking this!
Thank you both. I had no idea there was a nicer camera app available, I think I'll be keeping this one (and upgrading it if those font bugs are fixed and/or 720p is added.)
I tried to install the MIUI Camera, but when I copy/move it using RootExplorer, it does not seem to show up under system/app under "Camera.apk" or "MiuiCamera.apk" or "miui.apk". It's like nothing happened. The file remains in the origin (my Dropbox folder) on the SD card even though it said "pasting".
Any advice?
Coldside... do u have root?
Put the file posted in your sd card.
Open rootexplorer copy the apk, go to system app, tap on "Mount R/W/" and paste the file. Then keep pressed the apk, tap permissions and give these permissions:
V V ⃞
V ⃞ ⃞
V ⃞ ⃞
Reboot
Yep I have root. I'm running CM7.0.0 on my Desire (Yes I know this is in the Nexus One forums but I googled and I didn't realize after I posted).
RootExplorer 2.16 has Superuser rights also. I mounted it to RW because when it's still in RO, you can't paste.
EDIT: I just realized my phone is S-ON. My guess is that it needs to be S-OFF? If I require S-OFF for this, do I need to wipe my phone and root it again? Thanks.
thanks, i have the miui camera up and working
the only problem i have is there is no front facing camera option and the photo taking is buggy
guess its not made for the mytouch4g
Not work on my Redmi 4x with LineageOs
Edited: Work. Thanks!
It does work and all I did was download this build prop. The file will not flash so I had to extract it and replace service.jar in system/framework folder remember to make it 644 for permissions reboot and there you go. Before you restart set LCD Density to 120 then reboot. On initial startup you will see a couple force quits but after they are done they will not appear again. I will update later after I run test
for AOKP build 27 : http://www.mediafire.com/?s2suuj1r57iz0rw
Restore : http://www.mediafire.com/?f8o0jt76p36d9ny
http://forum.xda-developers.com/archive/index.php/t-1467051.html
interesting find. Thanks.
Sent AOKPville
27 has a launcher glitch in it so I went down to 26 and o got no system UI problems. So it works to the rooms full capabilities minus some windows that pop up when starting up etc.
Sent from my PC36100 using xda premium
Here are some screen shots of it working. Video is Crap but everything else works.
https://lh5.googleusercontent.com/-...3oan0/s512/Screenshot_2012-03-04-18-51-15.png
https://lh5.googleusercontent.com/-...yJmDU/s512/Screenshot_2012-03-04-22-10-06.png
https://lh3.googleusercontent.com/-...1xSNs/s512/Screenshot_2012-03-04-22-10-29.png
I'm not sure if this is the right place to post this, but here goes.
I was running Mokee 4.3, and loved it; but the battery life was terrible.
So I went back to White Rabbit 2.11.
Now I'm getting lots of reboots due to Errors in Telephony Layer.
My question is: Is it possible to take the RIL from the stock ROM and replace it in White Rabbit?
If so, which files should I copy?
Thanks
Rijidij said:
I'm not sure if this is the right place to post this, but here goes.
I was running Mokee 4.3, and loved it; but the battery life was terrible.
So I went back to White Rabbit 2.11.
Now I'm getting lots of reboots due to Errors in Telephony Layer.
My question is: Is it possible to take the RIL from the stock ROM and replace it in White Rabbit?
If so, which files should I copy?
Thanks
Click to expand...
Click to collapse
Copy the bp_nvm_default folder from system/etc into the ROM.
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
Copy the bp_nvm_default folder from system/etc into the ROM.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks. I'll give this a try.
Update - progress so far:
As per advice from hotdog125, I copied the bp_nvm_default folder from a nandroid of the (rooted) stock ROM.
I found it in the /system/etc/motorola folder in this ROM
It appears to be working so far - I will keep a close eye on it for telephony errors...
If others want to try the same, here are the steps I took. (YMMV)
Extract the bp_nvm_default folder from the stock ROM (in /system/etc/motorola)
Rename to bp_nvm_default.stock
Copy to phone SD card
On the phone, copy from SD card to /system/etc/motorola
I had to chmod the folder to 755, and all the contents to 644 (again, YMMV)
Rename the existing bp_nvm_default folder to bp_nvm_default.bak
Rename bp_nvm_default.stock to bp_nvm_default
Reboot...
My phone booted up OK, and everything looked fine. So I decided to push a bit further. :fingers-crossed:
Reboot into recovery
Clear cache and dalvik cache
Reboot...
Again, I had success!
A few points:
Steps 4-7 were possible thanks to JRummy's ROM Toolbox Pro (great tool - worth every penny! :good
A message appeared saying changing permissions failed, but after refreshing the list, permissions were correct.
I had to chmod each file in the folder individually - a bit of a pain, but it only took a few minutes. (I tried it in the terminal, but that definitely didn't work).
Baseband has defaulted to Central Europe 3.4.2-145. I'll leave it on that one for now and see how it goes.
On the subject of Baseband, I'm in the UK and have these available under the GB heading:
3.4.2-117
3.4.2-11
2.51
T-Mobile 2.51
T-Mobile 2.21
3.4.3-3
4.5.1-85
Any recommendations from this list?
Thanks
Update:
No telephony reboots so far...
But the phone has got quite hot (while dark) on a couple of occasions.
Also, I couldn't get a connection to the Play Store this morning. Toggling Aeroplane Mode fixed it.
I might try one of the other basebands next.
Arrrgh! I spoke too soon!
RIL bug has struck 3 times since last night...
Damn... I thought I had this fixed.
RIL Bug is due to hardware issues. Changing the baseband will not help unfortunately
The best way to fix it is to use one of the later builds which have incorporated SlugZero's RIL patches
Sent from my MB526 using Tapatalk 4
So, In an attempt to get the configuration talk out of @franciscofranco's kernel thread, I decided to open this "swap meet"
As you may know I've wrote a couple scripts to make it easier to pull a backup of the kernel settings available through the franco kernel updater app.
Preparing files for sharing
Kernel Settings
so, if you want to share your kernel settings, grab the backup-script.sh file from here, run it either through a file manager or a terminal emulator, then head over to /sdcard/settings_backup/ and grab the restore-script.sh file, rename it to <your_user_name-defaults.sh> and post a link to it here.
Per App Modes
If you want to share you Per-App Modes settings, you'll need to use either the franco kernel updater or his stand alone Per-App Modes app, either way, the process is the same, just the file paths are a little different.
FKU App
So, if you use the fku app, go into fku -> Per-App Modes -> Manage your modes and click the BACKUP MODES in the top right corner. This creates an xml file of all your per app settings (one file per mode). These files are stored in /sdcard/franco.kernel_updater/saved_per_app_modes
Create a zip file including the modes you want to share and post it here.
Stand Alone Per-App Modes App
The process for using the stand alone app is the same. Per-App Modes -> Manage, and click BACKUP MODES in the top right corner again, this creates another batch of .xml files... Only they're stored in /sdcard/per-app_modes/saved_per_app_modes/
Once again, Create a zip file of the modes you want to share and post here.
Using Shared Settings
Okay, so you've downloaded the scripts and zips that you want to try out... how do you use them..
Kernel Settings
The scripts are easy, just run them (as root) through a file manager or terminal emulator.. then use fku or an init.d system to set the changes on boot if you want.
Per App Modes
The process for using the downloaded zips is just the reverse of sharing them...
Unzip the file and place the .xml files in the appropriate folder (/sdcard/franco.kernel_updater/saved_per_app_modes if you use fku, or /sdcard/per-app_modes/saved_per_app_modes/ for the standalone Per-App Modes app)
Then go into into your app, back to the manage page, where we clicked the BACKUP MODES last visit, only this time, click the LOAD MODES button.
Now, if you had copied the .xml file to the right folders, you should see the new PAM modules loaded into the list.
I will try to keep my signature link up to date with posted settings, and try to keep an eye out for identical or substantially similar settings.
For those using mobile apps and can't see signatures, here is the link to the scripts.
the backup-script.sh file is in the scripts folder, kernel and pam settings are in the settings folder.
Custom Paths for Per-App Modes
One thing that the stand alone app brought that hasn't (officially?) been ported back to the fku app is custom paths...
Giving you the ability to use any tunable setting in your Per-App Modes. --now in fku
While you can add and edit these easily through the stand alone app (and one reason why I think you should get it) once you know how the files work, thy can also be used in the main fku app...
Because of this, I am somewhat hesitant to give out the directions without approval from franciscofranco... Per-App Modes is a paid app of his and I would hate to take revenue out of his pocket.
Okay, since @franciscofranco has given me permission to release this, here we are...
This Zip file contains all the (useful) per app mode custom paths... to use this DO NOT FLASH IT... this is just a simple zip, nothing else... just unzip it in the right location...
If you use the fku app, then you need to unzip it and move/copy the files from the zipped folder to the franco.kernel_updater/per-app_custom_paths folder.
If you use the standalone per app modes then follow the same directions as fku, but put the files in the per-app_modes/per-app_custom_paths folder
Cautions and Warnings
-Any and all zips you find in this thread should NOT be flashed via recovery, don't try, bad things may happen...
-Permission errors may occur when running scripts from this thread as root. I haven't been able to figure out why, but some roms seems to set various file permissions to 444 instead of the 664 that my script expects... if you do encounter this situation, let me know and I'll give you a quick fix for it (requires adding a line to the scripts)
I haven't added the fix to my backup-script yet because I'm curious what files they are.. I've encountered 2 files so far
- Upon further testing, we've learned that root browser (app) might not work to run these scripts... adb shell and terminal emulator are working properly though. (backup script needed a small tweak as well)
Kernel setting scripts
Nexus 5
STOCK Settings
r46
aow1980
April 17, 2014
The Gingerbread Man
April 13, 2014
Tzfardaya
April 13, 2014
Vomer
July 22, 2014
Per-App Modes
The Gingerbread Man
April 13, 2014
Francisco Franco
May 11, 2014 - Low Power
May 12, 2014 - Games, Low Power
Vomer
May 11, 2014 - Low Power
Subscribed
Sent from my Nexus 5 using XDA Premium 4 mobile app
Subscribed! This is gonna be good! I'll upload a few of my setups soon!
Interesting Kernel settings , will give it a try and test your script. Thanks for sharing. Good luck with your thread
Tapatalk Team SlimRoms
This would be the perfect place to share some custom paths too
Subscribed and I'll see about linking to this thread from my learner lounge
Sent from my Nexus 5 using Tapatalk
The Gingerbread Man said:
This would be the perfect place to share some custom paths too
Subscribed and I'll see about linking to this thread from my learner lounge
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, I've got a zip of ALL the custom paths ready, just working on the write up for them...
and trying to solve a small moral dilemma with them...
This thread could also be used for all the supported fku devices if you were to split up the op into several device specific sections and ask about getting the thread moved to Android General forum. New posts can also be inserted on your behalf but you need to contact a moderator for both of these...
Sent from my Nexus 5 using Tapatalk
The Gingerbread Man said:
This thread could also be used for all the supported fku devices if you were to split up the op into several device specific sections and ask about getting the thread moved to Android General forum. New posts can also be inserted on your behalf but you need to contact a moderator for both of these...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I know, but I don't have the other devices to get the scripts set up for it.. and I'm more interested in working the nexus 5 right now..
I would have no problem if others wanted to use my scripts as a base for writing their own for swapping
Tzfardaya said:
Per-App Modes
The Gingerbread Man
April 13, 2014
Click to expand...
Click to collapse
FYI, getting a bad zip file here, but the tgbm.zip in your sig works just fine
(damn that was hard to write with auto correct on SwiftKey. Lol.)
Sent from my Nexus 5 using XDA Premium 4 mobile app
WettbackMartyr said:
FYI, getting a bad zip file here, but the tgbm.zip in your sig works just fine
(damn that was hard to write with auto correct on SwiftKey. Lol.)
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
heh, yeah, swiftkey autocorrection is a pain at times..
but I just downloaded through both the pc and nexus 5 and got clean downloads of that zip...
I'm not sure if the two gingerbread zip are different, but he just sent me the current batch today... (hence the date in the name) the others are from when I first worked on the scripts
Tzfardaya said:
heh, yeah, swiftkey autocorrection is a pain at times..
but I just downloaded through both the pc and nexus 5 and got clean downloads of that zip...
I'm not sure if the two gingerbread zip are different, but he just sent me the current batch today... (hence the date in the name) the others are from when I first worked on the scripts
Click to expand...
Click to collapse
Hmmmmmm :-/ I just can't get a good download on my Nexus 5. I'm not complaining tho, just trying to help for other people that may encounter the same. I got the scripts on my end one way or another.
Sent from my Nexus 5 using XDA Premium 4 mobile app
WettbackMartyr said:
Hmmmmmm :-/ I just can't get a good download on my Nexus 5. I'm not complaining tho, just trying to help for other people that may encounter the same. I got the scripts on my end one way or another.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try this one https://docs.google.com/file/d/0B2ar5BB6clkDQ0JfMVQ3NGtucEU/edit?usp=docslist_api I probably won't keep it in my drive long but feel free to get it while its there
Sent from my Nexus 5 using Tapatalk
How do I run (as root) or file manager for script ?where do I put the script file for kernel settings? I open the .sh file and it open and I see just texted files
Sent from my Nexus 5 using xda app-developers app
Just tested The Gingerbreads configuration and I must say I definitely see an improvement from the settings I had previously set. Nice job.
The Nexus 5 advocate (Team Inferno)
Ramone360 said:
How do I run (as root) or file manager for script ?where do I put the script file for kernel settings?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
It doesn't matter where the scripts are ran from, you run them either by selecting them in the file browser or running the following commands in a terminal emulator.
Code:
su
Then
Code:
sh <script-name>
Just realize that running the script alone will not keep the settings across reboots...
You need some other way to persist the settings... Either using fku or an init.d system.
My recommendation is fku, use these scripts to set the values all at once, then use the fku set on boot toggles.
All a shell script is is a text file with a series of shell commands, it's only purpose is to run a series of commands in a row to prevent forgetting one or making typos... It's like the old dos/Windows batch commands...
Tzfardaya said:
It doesn't matter where the scripts are ran from, you run them either by selecting them in the file browser or running the following commands in a terminal emulator.
Code:
su
Then
Code:
sh
Just realize that running the script alone will not keep the settings across reboots...
You need some other way to persist the settings... Either using fku or an init.d system.
My recommendation is fku, use these scripts to set the values all at once, then use the fku set on boot toggles.
All a shell script is is a text file with a series of shell commands, it's only purpose is to run a series of commands in a row to prevent forgetting one or making typos... It's like the old dos/Windows batch commands...
Click to expand...
Click to collapse
Sorry I still don't get it. I'm too familiar with terminal emulater. l always use root explorer. I downloaded the file but now my question is how do I run as root.
Sent from my Nexus 5 using xda app-developers app
Sent from my Nexus 5 using xda app-developers app
To run the script from terminal emulator you'll need to first locate the file.. But you need to be root to launch an .sh file.
Type "su" without quotes and let SuperSU prompt you, make sure you grant it root access.
Navigate to the file by using the "cd" command without quotes.
If you're like me..and downloaded it from a browser or Tapatalk.. You'd type cd storage/sdcard0/Download
Then run "ls" without quotes to make sure the file is in there. Once it is make a note of the name.
Type su FILENAME.sh (replacing filename with the actual name of the file) and hit enter. Should have worked. It did for me. If done correctly you should see no confirmation or error message. In Linux no messages are a good thing.
PS : don't forget to grant root to terminal emulator if you haven't yet. Remember to use FKU or init.d to make settings stick after reboot.
Edited to include "su" command for those who don't know how to run terminal emulator as root.
The Nexus 5 advocate (Team Inferno)