I just traded up from an HTC Legend to a Desire Z but unfortunately I have two gripes which are both due to Bell:
1) Preinstalled games and apps. Asphalt 5; Cyberon Voice; GPS Navigator; Kobo; Let's Golf!; Remote PVR; SoundHound; Tunes & Apps; TV & Radio; UNO; Zoompass. 11 apps that I don't need. 11!
2) HTC Locations is missing. Instead they want you to use GPS Navigator which is $10 a month. No thanks!
Anyway my questions are:
1) Is there any way to remove the excess apps without a full root? Ex: with VISIONary + another apps?
2) Is there any way to get HTC Locations back? I see it in some of the system settings, but can't actually launch it.
not too sure about htc places, but to remove those waste of space third party Apps all you need to do is run visionary. once you've done that, load up Root Explorer application and navigate to /system/app/ directory. here you will find those pesky Apps and games, but be careful with what you delete. some of these apk's are critical to htc sense. good luck... let me know how it turns out.
Sent from my HTC Desire Z using Tapatalk
Thanks for the reply but as with my Legend, it's all back after reboot. :-(
Sorry, I currently just experienced the same thing. I think this occurs due to the apk remaining in /data/Dalvik-cache/ files. I would suggest deleting the files corresponding to the .apks you remove and repeat the first process as well.
Sent from my HTC Desire Z
That seemed to have solve the problem. I just rebooted and they did not return. Let me know if it works for you.
Sent from my HTC Desire Z
No go. I deleted from /system/app and /data/dalvik-cache but after reboot, everything is back.
Maybe you did a power down and then turned it on again - since they have quick-boot now (aka sleep mode) it doesn't actually power down or restart the phone, causing it to appear as if the changes stuck when they didn't.
I remember reading that you need a true root to get rid of sys apps on HTC phones, but I also thought I saw something about doing it from command line on a PC somehow.
The practice of preloading uninstallable demos and useless apps is unacceptable.. ugh
have you checked the G2 forums ??
This same Q for this same device has been previously asked and discussed there
They are lightyears away form us
I still think both forums should be merged...
.
gtrab said:
have you checked the G2 forums ??
This same Q for this same device has been previously asked and discussed there
They are lightyears away form us
I still think both forums should be merged...
.
Click to expand...
Click to collapse
Agreed, it's going to be kinda silly have the two sets of forums. On the G2 they've figured out loads of things like this already.
The new HTC phones have a good system protection thing going on.
Basically each time you reboot the phone it checks to see if the contents of /system has been edited (apps added or removed etc etc) then if it has changed it will reflash it back to stock.
Basically you can root using "visionary" and make any changes you want, but as soon as you reboot it will all change back.
That being said Modaco has now come up with a method for removing apps permanently but not adding them.
Lennyuk said:
The new HTC phones have a good system protection thing going on.
Basically each time you reboot the phone it checks to see if the contents of /system has been edited (apps added or removed etc etc) then if it has changed it will reflash it back to stock.
Basically you can root using "visionary" and make any changes you want, but as soon as you reboot it will all change back.
Click to expand...
Click to collapse
That was the original story, but I think it's been debunked now, hasn't it ? It doesn't revert things to normal once you reboot (as proved by Paul's program which can delete built-in apps), but merely prevents you from writing to the on-board storage.
steviewevie said:
That was the original story, but I think it's been debunked now, hasn't it ? It doesn't revert things to normal once you reboot (as proved by Paul's program which can delete built-in apps), but merely prevents you from writing to the on-board storage.
Click to expand...
Click to collapse
not quite
Pauls method basically tricks the phone into thinking the app was legitimately removed therefore it doesn't think there is an issue so won't reflash it.
Lennyuk said:
not quite
Pauls method basically tricks the phone into thinking the app was legitimately removed therefore it doesn't think there is an issue so won't reflash it.
Click to expand...
Click to collapse
I don't think that's right though. Paul's method just fools the phone into deleting the app as part of a supposed update.
There is no check to see if anything's been changed when the phone boots, as far as I can tell from the G2 forums.
steviewevie said:
I don't think that's right though. Paul's method just fools the phone into deleting the app as part of a supposed update.
There is no check to see if anything's been changed when the phone boots, as far as I can tell from the G2 forums.
Click to expand...
Click to collapse
Well it has to check something otherwise it would not know to erase anything you change like Overclock levels etc.....
Lennyuk said:
Well it has to check something otherwise it would not know to erase anything you change like Overclock levels etc.....
Click to expand...
Click to collapse
It doesn't erase those though, it's just that when you "change" them via the tools, it doesn't write to the internal storage, it's just caching the changes in RAM. So it reads the cache and uses the changes. When you reboot, of course the cache is flushed, so the changes disappear.
They used to think there was a "revert to stock on reboot" thing on the G2 too, a few weeks back. No disrespect, but this is an example of how out of date "we" are here on the DZ forums, compared to the G2 which has been out a few weeks now.
steviewevie said:
It doesn't erase those though, it's just that when you "change" them via the tools, it doesn't write to the internal storage, it's just caching the changes in RAM. So it reads the cache and uses the changes. When you reboot, of course the cache is flushed, so the changes disappear.
They used to think there was a "revert to stock on reboot" thing on the G2 too, a few weeks back. No disrespect, but this is an example of how out of date "we" are here on the DZ forums, compared to the G2 which has been out a few weeks now.
Click to expand...
Click to collapse
hmm, I am still not convinced caching would hold it without significantly lowering perfomance, plus why the very very long boot times when you do make a change and then reboot?
Lennyuk said:
hmm, I am still not convinced caching would hold it without significantly lowering perfomance, plus why the very very long boot times when you do make a change and then reboot?
Click to expand...
Click to collapse
Try asking about this on the G2 forum if you like ...
On the caching thing, there's more in the Wiki - http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Intro . Specifically :
For anyone interested-- despite what the blogs are saying-- THERE IS NO "ROOTKIT" and THERE IS NO "RESTORE ON REBOOT". What *is* happening is that Android thinks it's writing to the eMMC (memory card), but it is not. What you are seeing as a successful write is just the cache
Click to expand...
Click to collapse
And here's the proof - http://pastebin.com/cm75Z9UA
Lennyuk said:
hmm, I am still not convinced caching would hold it without significantly lowering perfomance, plus why the very very long boot times when you do make a change and then reboot?
Click to expand...
Click to collapse
Because that's a REAL reboot
The fabulous fake "5 seconds boot time" is just a hibernation trick, a feature called "HTC Fast Boot" (= power off hybernates instead of really "powering off").
Check the G2 forums, this has been confirmed by HTC.
When you press "power off", the phone DOESN'T power off, it just "hibernates", then when you power the phone on again, you see the "amazing 5 seconds boot up"
If you want REAL power off you have to REMOVE THE BATTERY
.
gtrab said:
Because that's a REAL reboot
The fabulous fake "5 seconds boot time" is just a hibernation trick, a feature called "HTC Fast Boot" (= power off hybernates instead of really "powering off").
Check the G2 forums, this has been confirmed by HTC.
When you press "power off", the phone DOESN'T power off, it just "hibernates", then when you power the phone on again, you see the "amazing 5 seconds boot up"
If you want REAL power off you have to REMOVE THE BATTERY
.
Click to expand...
Click to collapse
So how long are these very very long boot times??? Have had android 2.1 take about 1 minute to load up normally on a 600mhz processor, so surely 2.2 wouldn't take much longer than this?! ???
Anyway, back to the question (in a way)...
Is TomTom actually available as standard on the Desire Z? As I'm sure I read somewhere that it was Route66 or some other software with a similar name, not TomTom...
gtrab said:
Because that's a REAL reboot
The fabulous fake "5 seconds boot time" is just a hibernation trick, a feature called "HTC Fast Boot" (= power off hybernates instead of really "powering off").
Check the G2 forums, this has been confirmed by HTC.
When you press "power off", the phone DOESN'T power off, it just "hibernates", then when you power the phone on again, you see the "amazing 5 seconds boot up"
If you want REAL power off you have to REMOVE THE BATTERY
.
Click to expand...
Click to collapse
yes thanks but I knew this already, I knew this from the moment I heard of the new "fast boot" its the same as blackberry have been using for years
Related
Has anybody figured out a way to use the back button to exit out of programs instead of hiding them so that you don't have to go to "manage applications" in order to force close them and save battery life?...i know, run.on.
konsts said:
Has anybody figured out a way to use the back button to exit out of programs instead of hiding them so that you don't have to go to "manage applications" in order to force close them and save battery life?...i know, run.on.
Click to expand...
Click to collapse
From what I understand the MT4G is supposed to do a job on it's own of closing most applications most of the time, better then any other android had (at time of release anyway). I suppose if you think it's that big of an issue you could download a task killer, but I've heard over and over again to not use on on the mt4g because you just don't need it. That's just what I heard though.
Could be wrong, wouldn't be the first time.
Is there a setting for that then? because nothing closes on my phone
yeah i agree on NOT using those task killers. i have seen many posts from devs saying they cause more problems then there worth. interfere with apps causing force closes and some other thing that i cant remember off the top of my head.
Google up "Why you shouldn't be using task killers with Android", read, educate yourself, and stop doing unnecessary things with your phone. Understand how things work before you attempt "making them work better", and screw them up in the process.
Ok sounds good, but why then when you get rid of the bloatware like "amazon mp3" by disabilig them, do you get improved battery life? What am I missing?
You don't. Battery life won't be bothered by having or not having Amazon MP3. The only thing you get is more memory (which isn't used anyway) and more space on the /system (which isn't used anyway). Additional thing you get that IS used - is less cluttered app drawer.
konsts said:
Ok sounds good, but why then when you get rid of the bloatware like "amazon mp3" by disabilig them, do you get improved battery life? What am I missing?
Click to expand...
Click to collapse
Task Killers do more harm then they do good. any developer, any coder, any one with any Android knowledge will tell you "you do not need it, and they do more harm then good". In fact Google themselves has said that it's not worth it. and the dev team @ Cyanogen will not accept a event log for trouble shooting if you have used a task killer.
But the reason we delete bloat ware is to gain that memory for other applications and data. no all apps can be stored to the SD card and they do leave a foot print on the phone. So we delete them to gain the space back.
Android phones are Lunix based computers which can multitask lightyears better than any current windows based computer system, phone or server. They were designed with this very principle in mind. In fact if you have ever used Ubuntu 10.10 they have a 4 "work spaces" where you can do different stuff simultaneously. similar to the "home screens" on android.
as far as them "running" in the background they are not absorbing any data/battery/resources from your phone. They are setting in a "frozen" state until you open them. In fact, if you didn't know this, if you press and hold the home button you can access recently open apps. It keeps them in the "frozen" state so if you switch back to them they'll open where you left them.
Thanks for all the comments. But I don't need convincing on the task killers; I understand they're worthless. My intent was to find out how to make my phone perform better (battery life-wise). And although I think I have a better understanding on how android handles apps it also just confused me.
I used to get 8-10 hrs max on my phone and basically have to charge it all the time. Since I temp rooted (permroot isn't working for me) using VISIONary and disabled a bunch of apps using Terminal Emulator, I'm sitting on 23.5 hrs off the charger right now with 45% battery left!!! And all I did was disable apps. So I'm mad confused how I'm getting so much battery life when the only thing that's changed in my phone according to you wouldn't change anything.
konsts said:
Thanks for all the comments. But I don't need convincing on the task killers; I understand they're worthless. My intent was to find out how to make my phone perform better (battery life-wise). And although I think I have a better understanding on how android handles apps it also just confused me.
I used to get 8-10 hrs max on my phone and basically have to charge it all the time. Since I temp rooted (permroot isn't working for me) using VISIONary and disabled a bunch of apps using Terminal Emulator, I'm sitting on 23.5 hrs off the charger right now with 45% battery left!!! And all I did was disable apps. So I'm mad confused how I'm getting so much battery life when the only thing that's changed in my phone according to you wouldn't change anything.
Click to expand...
Click to collapse
battery life has alot to do with your social networks, and syncing. If i turn off everything, and turn the screen brightness to about 25%, i drop about 2% per 5 hours. So it really depends on what you disabled, and if they were absorbing any resources on your phone.
neidlinger said:
Task Killers do more harm then they do good. any developer, any coder, any one with any Android knowledge will tell you "you do not need it, and they do more harm then good". In fact Google themselves has said that it's not worth it. and the dev team @ Cyanogen will not accept a event log for trouble shooting if you have used a task killer.
Click to expand...
Click to collapse
That is correct. However, there is one situation in which I do end apps, and that is in the case of resource-intensive, 3D games. The MT4G has so much RAM, that even games like NFS Shift, X-Plane, and Jet Car Stunts never close. They stay running in the background forever, which is unnecessary. So I'll close those, but no other apps.
TeeJay3800 said:
That is correct. However, there is one situation in which I do end apps, and that is in the case of resource-intensive, 3D games. The MT4G has so much RAM, that even games like NFS Shift, X-Plane, and Jet Car Stunts never close. They stay running in the background forever, which is unnecessary. So I'll close those, but no other apps.
Click to expand...
Click to collapse
I do the same but i'll got to settings > apps > running > and sever them.
BTW Backbacker is a good 3D game.
neidlinger said:
BTW Backbacker is a good 3D game.
Click to expand...
Click to collapse
I'm not finding that one. The closest I can find is this one, but that's a GPS resource, not a game.
TeeJay3800 said:
I'm not finding that one. The closest I can find is this one, but that's a GPS resource, not a game.
Click to expand...
Click to collapse
look for backbreaker football. it was a the Amazon freebie yesterday.
konsts said:
Has anybody figured out a way to use the back button to exit out of programs instead of hiding them so that you don't have to go to "manage applications" in order to force close them and save battery life?...i know, run.on.
Click to expand...
Click to collapse
Settings/applications/development/stop app via long press.
Make sure you check the box. That's how you stop the app completely.
Sent from my HTC Glacier using XDA App
No such thing on stock ROMs. CM feature.
didnt know he had a stock rom till i read his sig. xda app doesnt show that sig. saw it now that im a pc. my bad.
Its stops the tablet from searching for a cell phone signal that eats up some of the battery.
Acer Iconia Phone Disabler (strange name)
zanetti2000 said:
Its stops the tablet from searching for a cell phone signal that eats up some of the battery.
Acer Iconia Phone Disabler (strange name)
Click to expand...
Click to collapse
Please provide a link when posting info in future for reference
here's the reference :
http://forum.xda-developers.com/showthread.php?p=14053121
I went ahead and downloaded the app..but becuase of differing opinions on the feasibility and safety in removing or changing those 2 .apk files...im a bit reluctant to actually use it. Anyone have any wordds of wisdom one way or another?
Chlballi
It's a good app but i worry cannot update to 3.1 after root it. So wait for Honeycomb 3.1. Thanks for sharing
is thera any other way to disable cell stanby? not buying this app?
i've deleted phone.apk and telephonyprovider.apk through system apps remover but cell standby is still draining my battery
Glebaka said:
is thera any other way to disable cell stanby? now buying this app?
Click to expand...
Click to collapse
Well, I did the same thing - downloaded then changed my mind and uninstalled. It's nothing more than renaming the telephony.provider and phone apk's so why pay - you need to be rooted to use it anyway so why not just rename them?
BUT - there's a big issue if you need to do a hard reset and also, you will not be able to get the update because as we know, the updating procedure checks for completeness of all the apps - if any are missing, it won't install.
I'm waiting for Acer to fix this (actually it's a Google problem since many other tablets have this issue).
Convenience, maybe?
It's quick, don't have to mess with remounting /system to read/write. And when it's time to take that update, just run it again and click "Enable" and they are back to normal. After an update, you can disable them again, if they haven't fixed the battery drain issue.
docfreed said:
Well, I did the same thing - downloaded then changed my mind and uninstalled. It's nothing more than renaming the telephony.provider and phone apk's so why pay - you need to be rooted to use it anyway so why not just rename them?
BUT - there's a big issue if you need to do a hard reset and also, you will not be able to get the update because as we know, the updating procedure checks for completeness of all the apps - if any are missing, it won't install.
I'm waiting for Acer to fix this (actually it's a Google problem since many other tablets have this issue).
Click to expand...
Click to collapse
I have a way that seems to work for me... I downloaded power widget, made 2g/3g toggle, clicked it, then unchecked everything. (Doesn't delete or rename anything) and my tablet no longer wastes battery on cell standby
So I just updated to UD 1.5b3. This reset my settings back to having the double sized notification bar, which annoys the crap out of me, so I used Reditus2's method:
http://forum.xda-developers.com/showthread.php?t=1114069
I used this method for UD 1.0 and it worked wonders. After running this on 1.5b3 however I am now unable to boot up as usual (can still get to recovery mode and thus was able to fix, but wanted to share this). I get as far as the UrukDroid Loading... page, trys to load for about 5-10 seconds, goes black for about 1 second, and then shows the Loading page again. I have allowed it to sit on this screen for 10+ min to no avail. Just wondering if anyone has any ideas on how to keep UD 1.5b3 without having the huge notification bar. Also wanted to give Reditus2 a chance to see this and maybe there's just an update needed to the scripting to resolve this.
I had the same problem with rc1
i gave up on reframing
at least the bar disapear when you lunch a full screen app
I'll try as well - but right, full screen works at least.
working like a charm for me on UD 1.5
have you tried this? - http://forum.xda-developers.com/showthread.php?t=1139882
I've created UD 1.5 package with smaller top buttons.
http://code.google.com/p/urukdroid/wiki/Download
enricogrim said:
Hi $aur0n I installed UrukDroid 1.5 and all worked perfectly! but today I installed package with smaler top buttons and now Urukdroid freeze while booting, it stops when in the botton of the display appears : UrukDroid 1.5 boot: switching to rootfs... How can I do? I don't want to reinstall the system from scratch.
Click to expand...
Click to collapse
Did update went ok? What has the message on top of the bar during update? What messaged you have seen during startup of device?
Anyway best/fastest/easiest etc. way is to restore rootfs from backup (RescueMenu) if you had one. Second is just to do quick reinstall of rootfs (your data will stay untouch).
@$auron:
As i never use it the search button, is there any chance of switching it off?
And wouldn't be 32 px a better solution, as normally everything alligned to 4 or 8 gets better scaled and painted on normal devices?
Otherwise, nice.
fzelle said:
@$auron:
As i never use it the search button, is there any chance of switching it off?
And wouldn't be 32 px a better solution, as normally everything alligned to 4 or 8 gets better scaled and painted on normal devices?
Otherwise, nice.
Click to expand...
Click to collapse
Hmm I've started with 28px but it looked a bit too small. I can try 32. I also don't use search button at all. I'll remove it...
enricogrim said:
Thank you very much for your quick answer. My update went ok, at the end of it on the top bar the message told me to reboot the device. But while rebooting my device (A43) freezed with the above message: UrukDroid 1.5 boot: switching to rootfs...
As I hadn't a backup I did a quick reinstall and now it seems to work well!
thank you again
Enrico
Click to expand...
Click to collapse
How long did you wait?
I remember the first time I updated the framework with Fisha21's one, it took a while to boot up on the first boot. Apparently android was rebuilding the dalvik cache with the new framework.
$aur0n said:
I've created UD 1.5 package with smaller top buttons
Click to expand...
Click to collapse
Thank you for this package ! I was trying to make my own framework-res but I always fail
fzelle said:
@$auron:
As i never use it the search button, is there any chance of switching it off?
And wouldn't be 32 px a better solution, as normally everything alligned to 4 or 8 gets better scaled and painted on normal devices?
Click to expand...
Click to collapse
32px height buttons, I've also made them shorter - 70px instead of 80px. Sadly removing search is not so easy (I don't know if I will have time to look further).
UrukDroid-1.5-32pxButtons.tbz2
Thanks for trying.
Don't hurry.
$aur0n said:
32px height buttons, I've also made them shorter - 70px instead of 80px. Sadly removing search is not so easy (I don't know if I will have time to look further).
UrukDroid-1.5-32pxButtons.tbz2
Click to expand...
Click to collapse
It's probably easier and quicker to remove them all and use button savior
sibere said:
It's probably easier and quicker to remove them all and use button savior
Click to expand...
Click to collapse
Yes (I still use ButonSavior - even with buttons on top, because they can disappear on some apps) - but less universal..
ps. I know where to remove search button (or any other) but system refuses to accept new framework - probably once again this ****ty certificates issue !
Thanks aur0n, the button package works great! !!!
@$auron
32px work better, as now batterie and wifi are next to each other instead of ontop.
Have deinstalled buttonsaior, as this together with std buttonmode (longpress power) is enough for me.
Thaks again.
Hey $aur0n, thanks for the link to the package! Definatly going to try it as soon as I figure out what happened to my /data/urukupdate folder. Just disappeared on me. Whole /data folder is empty.
kurigami said:
Hey $aur0n, thanks for the link to the package! Definatly going to try it as soon as I figure out what happened to my /data/urukupdate folder. Just disappeared on me. Whole /data folder is empty.
Click to expand...
Click to collapse
That's kind of unlikely - device would not work with empty /data (it would write a lot of new stuff in it during boot...)
I agree, that's why I was so confused. Did manage to find an answer on that one though. For some reason lost my SU permission for my file explorer so that's resolved. Don't suppose you might know why the kernel file isn't doing the auto-update/install once dropped into the urukupdate folder? The modified top bar you listed worked perfectly, but the Kernel file isn't automatically updating, and it looks like the new UrukConfig doesn't allow me to force the update.
Heya, new to fiddling with root files but really wanted to get rid of camera click. Followed advice about renaming camera_click.ogg in terminal Emulator using:
ADB shell
SU
mount -o remount,rw /dev/block/mtdblock4 /system
mv /system/media/audio/ui/camer_click.ogg /system/media/audio/ui/camera_click.ogg.old
(source: www droidforums net/forum/droid-hacks/23107-droid-remove-camera-click-shutter-sound html) - sorry new poster not allowed to post url
Now have issue when open stock camera and vid in Motorola Atrix (gingerbread 2.2.2) where:
1) camera opens, but have lost all previous images.
2) camera takes silent shot
3) camera 'locks' open and can't return to 'desktop', can't view image taken,, can't access menus etc
Basically camera is stuffed...
is there a solution, is there code to go back and follow some of the other advice in here etc?
It is a setting. What's the point?
Sent from my MB860 using xda premium
it's a setting what's the point? Thanks for taking the time to reply. I did mention this is all new to me. I asked a question because i do't know the answer. It's a swttibg whats the point is hardly helpful.
To anyone else, i'd appreciate any help or advice. As i mentioned i'd just like to undo what i've done usibg script i found on another forum. looking forward, hopefully, to hearing from you!
have you tried to add the following line to local.prop file located in /data?
ro.camera.sound.forced=0
If you don't have the file then just create the file and add it, otherwise append it to the end of file.
File permission is: 0644
Good Luck
I never heard of adding ".old" on the end of the file. I always add ".bak", then reboot. Works everytime.
EchoK8 said:
it's a setting what's the point? Thanks for taking the time to reply. I did mention this is all new to me. I asked a question because i do't know the answer. It's a swttibg whats the point is hardly helpful.
To anyone else, i'd appreciate any help or advice. As i mentioned i'd just like to undo what i've done usibg script i found on another forum. looking forward, hopefully, to hearing from you!
Click to expand...
Click to collapse
I giggled when I read gingerbread 2.2.2
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Thanks for pointing that out, that gave me a good laugh to start the day off.
Phalanx7621 said:
I giggled when I read gingerbread 2.2.2
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
EchoK8 said:
it's a setting what's the point? Thanks for taking the time to reply. I did mention this is all new to me. I asked a question because i do't know the answer. It's a swttibg whats the point is hardly helpful.
To anyone else, i'd appreciate any help or advice. As i mentioned i'd just like to undo what i've done usibg script i found on another forum. looking forward, hopefully, to hearing from you!
Click to expand...
Click to collapse
I was on my phone at the time (tiny keyboard) and was trying to succinctly say that if you open the camera app and touch "settings", there is an option to quiet the click.
When I first read your OP I didn't notice that you identified Gingerbread as v2.2. You are confused. v2.2 was named Froyo (frozen yogurt). Gingerbread is v2.3. My answer relates to Gingerbread. If you are actually on Froyo, I don't remember if the setting was available on that release.
So, in Gingerbread silencing the camera is a setting and there is no point performing internal surgery.
Yep, ok, noob blunder. Novice blunder, amatuer, beginner whatever blunder. Glad you all got a giggle, and thanks for pointing it out. I was told at the shop it's Gingerbread. The About phone states 2.2. So, if that makes it Froyo then great, i've learnt the basics today. Thanks for your help again!
Well re- the settings, froyo or otherwise, yes there is a setting to turn sound off. You turn it to off and it still makes the click sound, volume can't be altered. Hence diving off the deep end and into something i know very little about - internal surgery!!
Live4nyy - is there a simple way to rename to .bak (you see my level of expertise here - none! - in asking).. forward some script for me at all?
or
CSharpHeaven that sounds gr8... any way to explain to a complete novice how to do that?
I thank anyone who sticks with me to reply after this MUCHLY as you know you are dealing with a friking novice
Seriously....why would you want to silence your camera again?
Do you have root? If yes, then you can just use any file manager that has root access, ES File Explorer works I've heard, and just go to the folder where the sound file is (/system/media/audio/ui) and just select to rename the file and add ".bak".
EchoK8 said:
Yep, ok, noob blunder. Novice blunder, amatuer, beginner whatever blunder. Glad you all got a giggle, and thanks for pointing it out. I was told at the shop it's Gingerbread. The About phone states 2.2. So, if that makes it Froyo then great, i've learnt the basics today. Thanks for your help again!
Well re- the settings, froyo or otherwise, yes there is a setting to turn sound off. You turn it to off and it still makes the click sound, volume can't be altered. Hence diving off the deep end and into something i know very little about - internal surgery!!
Live4nyy - is there a simple way to rename to .bak (you see my level of expertise here - none! - in asking).. forward some script for me at all?
or
CSharpHeaven that sounds gr8... any way to explain to a complete novice how to do that?
I thank anyone who sticks with me to reply after this MUCHLY as you know you are dealing with a friking novice
Click to expand...
Click to collapse
I'd like to replace my shutter sound. Does anyone have a sound file of a shotgun blast/ slide rack?
Thannnks
island-guy said:
Seriously....why would you want to silence your camera again?
Click to expand...
Click to collapse
i actually dont want or need to silence it again. my query is how to restore my camera to a mode where it is functional bcs at the moment its stuffed. If theres a simple string to go back that'd be ideal.
live4nyy said:
Do you have root? If yes, then you can just use any file manager that has root access, ES File Explorer works I've heard, and just go to the folder where the sound file is (/system/media/audio/ui) and just select to rename the file and add ".bak".
Click to expand...
Click to collapse
Ok, got 'root explorer'... so simple just to enable R/W and rename.. Thanks. Changed to .bak . Seems better, actually appears to take photos and has more functionality than after i ran that script... but
I don't know what that original script did. Here's what using my built in camera is like:
1) Turn Camera on. Opens, appears normal. Take photo fine. Thumbnail (link to camera roll) in bottom corner as per usual, which disappears after a few seconds as per normal.
So far so good.
2) After taking another photo decide to click on thumbnail to open camera roll. Camera Roll opens but says there are no pictures to display. return (via 'back' menu button) and the thumbnail of the images is there again. Ok, weird.
3) Try take another photo... nothing happens, wait a few seconds and camera switches off back to ;desktop'. Try open camera again but no dice. In fact all phone functionality gone, frozen, locked up, including menu buttons below screen. Put phone to sleep by pressing rear button briefly. Press rear button again to awake. Unlock swipe is slow to respond (a few seconds) and then back to main desktop screen. Can once again open camera. Repeat process from dot point 1).
4) next time go to camera roll, this time locks up on camera roll (which has no images to display again). Sleep and wake up camera, slow swipe unlock, can take photos again when open camera. repeat step 1 - 3 again!
5) Sleep, wake up phone. This time straight to gallery instead of camera. Gets stuck telling me it's loading media files. Frozen.
6) sleep- wake - slow swipe unlock. This time to video. Same thing as camera. Frozen.
I could go on.... but im sure the idea is clear!
used root explorer to simply remane camera_click.ogg to original name. Same as above
Tried camera zoom fx app incase it was the built in camera app. This won;t even open - well, it starts but then says i need to force it to close.
Does this need a factory reset??!
Ta
Have you rebooted? Maybe try and go into "Manage Applications" under the "All" tab and find the camera and "clear data"?
EchoK8 said:
Ok, got 'root explorer'... so simple just to enable R/W and rename.. Thanks. Changed to .bak . Seems better, actually appears to take photos and has more functionality than after i ran that script... but
I don't know what that original script did. Here's what using my built in camera is like:
1) Turn Camera on. Opens, appears normal. Take photo fine. Thumbnail (link to camera roll) in bottom corner as per usual, which disappears after a few seconds as per normal.
So far so good.
2) After taking another photo decide to click on thumbnail to open camera roll. Camera Roll opens but says there are no pictures to display. return (via 'back' menu button) and the thumbnail of the images is there again. Ok, weird.
3) Try take another photo... nothing happens, wait a few seconds and camera switches off back to ;desktop'. Try open camera again but no dice. In fact all phone functionality gone, frozen, locked up, including menu buttons below screen. Put phone to sleep by pressing rear button briefly. Press rear button again to awake. Unlock swipe is slow to respond (a few seconds) and then back to main desktop screen. Can once again open camera. Repeat process from dot point 1).
4) next time go to camera roll, this time locks up on camera roll (which has no images to display again). Sleep and wake up camera, slow swipe unlock, can take photos again when open camera. repeat step 1 - 3 again!
5) Sleep, wake up phone. This time straight to gallery instead of camera. Gets stuck telling me it's loading media files. Frozen.
6) sleep- wake - slow swipe unlock. This time to video. Same thing as camera. Frozen.
I could go on.... but im sure the idea is clear!
used root explorer to simply remane camera_click.ogg to original name. Same as above
Tried camera zoom fx app incase it was the built in camera app. This won;t even open - well, it starts but then says i need to force it to close.
Does this need a factory reset??!
Ta
Click to expand...
Click to collapse
live4nyy said:
Have you rebooted? Maybe try and go into "Manage Applications" under the "All" tab and find the camera and "clear data"?
Click to expand...
Click to collapse
Thanks L4NYY.. yep had rebooted. Tried clearing data but all the same
Had a quick look in the internal storage DCIM folder..All files appear to be there. The one vid file has a play button icon. The .jpg's have the android robot icon. I don't know what was there before. Trying to open the files from here freezes the phone.....
Connecting usb and viewing dcim shows that any images taken since the change to camera_click.ogg appear unknown thumnails in the PC explorer..and can't be opened on the PC via USB connection or when stored locally on the PC itself 'can't display this is an empty file' . This is probably all irrelevant but might be useful to someone, somehere...
Have just noticed today that battery was going flat very quickly. Realised since rooting and using that script (can't decipher which) that location services are no longer working, hence apps that provide location services are continually searching and draining battery. Yes i can turn those services off, but wouldrather resolve the issue!
I'm thinking more and more like factory reset Any thoughts?
Just factory reset. Used Astro File Manager to backup apps before hand, which for interest worked well (although did have to reinstall one by one). Of course Appstore keeps a lsit of purchased apps as a failsafe for thsoe.
After rest, reinstalled apps, including Root Manager. Simply followed Live4NYY's advice, renamed camera_click.ogg to camera_click.ogg.bak
All issues described earlier resolved. Camera functional and silent.
just goes to show sometimes you should ask noob questions. I tried following instructions on a post to avoid annoying the experts with a mum-mum dad-dad question! Anyhow, thnaks to live4nyy for taking the time.
Ciao
The ".bak" just stands for "backup". It will essentially hide any file/app and keep it from running (which in turn frees up RAM). So if you had a system app that you don't use you can just add ".bak" and it would be the same as freezing it. It's much safer than deleting files and apps as you can always go back and remove the extension (and reboot) and it will be back to normal.
EchoK8 said:
Just factory reset. Used Astro File Manager to backup apps before hand, which for interest worked well (although did have to reinstall one by one). Of course Appstore keeps a lsit of purchased apps as a failsafe for thsoe.
After rest, reinstalled apps, including Root Manager. Simply followed Live4NYY's advice, renamed camera_click.ogg to camera_click.ogg.bak
All issues described earlier resolved. Camera functional and silent.
just goes to show sometimes you should ask noob questions. I tried following instructions on a post to avoid annoying the experts with a mum-mum dad-dad question! Anyhow, thnaks to live4nyy for taking the time.
Ciao
Click to expand...
Click to collapse
It's here! Downloading it now and I'll flash it ASAP. Download link here, for those who want to give it a try:
http://developer.android.com/preview/download.html
I'm also gonna throw it out there: if you don't know how to flash this image you probably shouldn't. This is a developer preview and you are likely to run into far more problems than you would with the current official release.
I don't think it works with Nexus 9 LTE though
Edit: So you can flash the system, boot, cache and vendor img files using fastboot and get it working with just wifi. Just tried and successfully booted.
shenye said:
I don't think it works with Nexus 9 LTE though
Click to expand...
Click to collapse
no, probably not. it'll be no different from trying to flash the normal nexus 9 image with the LTE model. that image probably won't come out until the final release - this is just a developer preview after all.
Flashed (did a dirty flash, without performing a factory reset), but back to 5.1.1 now. At least in my case I found it impossible to use as a daily driver.
Issues discovered:
1. Settings panel (in notifications) had an extra white pane underneath. Once swiped away / clicked, the settings panel was not available anymore when dragging down from the notification area.
2. Home button not working
3. Unlock screen missing, on wake up the desktop is displayed, however swiping occasionally produces an unlock effect.
4. Facebook app crashes when trying to open it.
5. Holding and swiping up on the home button did nothing (instead of opening Google Now)
Other discoveries:
1. The application drawer now scrolls vertically. It has a search bar and the last apps (or maybe most used?) at the top, separated by a horizontal line from the rest of the drawer. When scrolling, only the search bar remains pinned at the top.
2. Profile icons on the right side, (only) the first time the notification panel is pulled down.
3. The notification panel opens wherever you swipe your finger from the top (not centered anymore).
4. The volume pane now has a drop down button on the right that reveals the other volume channels.
Warning: for me flashing back (again dirty flash) to 5.1.1 leads to a boot loop, where it boots, optimizes the apps, then throws a short Google Play Services has stopped and then black screen and reboots. Then does it again.
adancau said:
Flashed (did a dirty flash, without performing a factory reset),
Click to expand...
Click to collapse
I have no clue why you would do that then complain about what doesn't work.
JeeperDon said:
I have no clue why you would do that then complain about what doesn't work.
Click to expand...
Click to collapse
I was not complaining (I take full responsibility for flashing a preview edition). I was just describing my experience.
JeeperDon said:
I have no clue why you would do that then complain about what doesn't work.
Click to expand...
Click to collapse
So, to do this properly, do I have to unroot and go back to stock recovery? Or what's the best process when I'm unlocked, rooted, and with customer recovery already?
generosity21 said:
So, to do this properly, do I have to unroot and go back to stock recovery? Or what's the best process when I'm unlocked, rooted, and with customer recovery already?
Click to expand...
Click to collapse
You don't have to unroot and go back to stock (as this is not an update). If you go into the bootloader (adb reboot bootloader) and flash all the img files in the factory image (fastboot flash * *.img, where * is bootloader, boot, system, cache etc.) it will give you stock Android M. I'm saying flash the img files, as for me the flash-all thing didn't work (it complained about the system partition, apparently a common issue).
adancau said:
You don't have to unroot and go back to stock (as this is not an update). If you go into the bootloader (adb reboot bootloader) and flash all the img files in the factory image (fastboot flash * *.img, where * is bootloader, boot, system, cache etc.) it will give you stock Android M. I'm saying flash the img files, as for me the flash-all thing didn't work (it complained about the system partition, apparently a common issue).
Click to expand...
Click to collapse
Thanks! Can I skip the recovery.img and keep my custom recovery, or is that likely to cause problems?
generosity21 said:
Thanks! Can I skip the recovery.img and keep my custom recovery, or is that likely to cause problems?
Click to expand...
Click to collapse
I wouldn't. But you could experiment I guess (no guarantees though). Before you proceed make sure OEM unlocking is still on in Developer options, just in case.
Can someone who flashed it say some words about the the first impressions regarding performance ?
so after over an hour of trying to get it to work, i've finally got it to boot into the OS. i ended up having to force reboot it a bunch of times during the initial loading animation. interestingly, it showed a small warning for 5 seconds saying something like "your device has failed verification and may not work properly" with a red warning symbol on top, right after the bootloader splash screen.
before i force reset it (and reflashed the system image twice) it would get stuck at the loading screen for a very long time, much longer than what is normal for an initial boot on an encrypted device, and the top right corner of the tablet was getting very warm, meaning it was clearly working on something - maybe stuck in an infinite loop? anyway, installing my applications from a backup now and i'll get back about the performance and how it works.
something interesting i noticed right away is that when swiping down to show the notification shade, instead of always coming down right in the center it'll slide out from either the left, right or center of the status bar depending on where you swiped down. cool trick for making one-handed use easier i guess. i'll see if i can take a few screenshots once everything's set up.
oh, something else - there are a bunch of new neat animations everywhere. everything's a bit more fluid and there are some nice touches in a few places. not really something that can be explained without experiencing it though.
aside from the issues with booting up i haven't run into any other problems yet.
Flashed manually partition by partition, and erased user data before booting.
Absolutely no issues during flash and it booted on the first attempt.
It's currently restoring from my last Google backup, but so far a pretty easy experience (beyond flash-all being broken).
ooh there are a bunch of new battery optimization and battery usage tracking features, as well as a utility which tracks memory usage of various apps, and how often an app is running - and lets you choose whether to look at the past 3 hours, 6 hours, 12 hours and day.
foxmeister said:
Flashed manually partition by partition, and erased user data before booting.
Absolutely no issues during flash and it booted on the first attempt.
It's currently restoring from my last Google backup, but so far a pretty easy experience (beyond flash-all being broken).
Click to expand...
Click to collapse
I've noticed that the audio doesn't keep up with the keyboard if you type in any way reasonably quickly. Definitely seems slower to me so far compared with 5.1.1. I did a full clean wipe. I'm gonna do a restart once i install some stuff again and see if it clears it up. Noticed that the theme option under 'developer options' has an 'automatic' option, itd be pretty cool if it turned on at night for instance but its 10:24pm here in N.Ireland and it didnt go to dark mode when i chose automatic so who knows. Also see an option to enable/disable tap-to-wake, not something I want to disable but handy enough for those who do and maybe even potentially a small battery saving.
Jumpy audio through google play music, presumably related to the keyboard issue I was talking about. Still haven't restarted yet though.
EDIT: dark theme has enabled itself after i set the theme option to 'automatic', presumably because it's night time
seanashmore said:
I've noticed that the audio doesn't keep up with the keyboard if you type in any way reasonably quickly. Definitely seems slower to me so far compared with 5.1.1. I did a full clean wipe. I'm gonna do a restart once i install some stuff again and see if it clears it up. Noticed that the theme option under 'developer options' has an 'automatic' option, itd be pretty cool if it turned on at night for instance but its 10:24pm here in N.Ireland and it didnt go to dark mode when i chose automatic so who knows. Also see an option to enable/disable tap-to-wake, not something I want to disable but handy enough for those who do and maybe even potentially a small battery saving.
Jumpy audio through google play music, presumably related to the keyboard issue I was talking about. Still haven't restarted yet though.
Click to expand...
Click to collapse
Oddly, mine did go dark when I set the theme to automatic - I'm in England, so same time zone as you.
Can't say much else yet - still downloading my apps.
Quite a few force close pretty much immediately when I try to run them, but I'll let the restore take its course and reboot before making any firm judgements.
Given how generally poor my experience with my N9 has been to date, I'm prepared to put up with a few warts and teething issues.
adancau said:
I was not complaining (I take full responsibility for flashing a preview edition). I was just describing my experience.
Click to expand...
Click to collapse
I dont think its the fact that its dev preview that messed you up. By dirty flashing and then claiming it is not stable enough for a DD is stupid tho. If you want to truly experience it and not going around telling people you cant use it, then you should probably clean flash.
addicted1900 said:
Can someone who flashed it say some words about the the first impressions regarding performance ?
Click to expand...
Click to collapse
Its running great so far. Seem smooth for a dev preview. No FCs or other problems so far.
ilatimer1 said:
Its running great so far. Seem smooth for a dev preview. No FCs or other problems so far.
Click to expand...
Click to collapse
thanks. Then i will make the step tomorrow.
Does it still heats up like crazy when using Chrome?