Related
edit: Most devs have added this to their roms already so don't be surprised if you find it in the build.prop already.
So I saw this mentioned in a tweet by the dev for Launcher Pro:
To get really nice smooth scrolling on your Eris add the following line to your build.prop:
Code:
windowsmgr.max_events_per_sec=60
To add it into your build.prop follow these steps using your adb tool:
Code:
adb remount
adb pull /system/build.prop
(Go into your tools folder and open it with notepad. Add the line I posted and save.)
Code:
adb push build.prop /system/build.prop
Reboot into recovery, wipe dalvik cache, and start the phone up. This can a while to boot up right after because of the wiping dalvik cache. You should notice that scrolling on your phone is much smoother.
I AM NOT RESPONSIBLE FOR YOUR PHONE. IF YOU BREAK YOUR PHONE DOING THIS (it's unlikely!) I AM SORRY BUT I CAN'T HELP YOU.
I currently have mine set to 70 and it's not any noticeably smoother than 60 that I can tell but it is stable so if anyone wants to try bumping it up to 90 or 120 feel free.
Thanks for the advice last night on this Hungry Man. I did this and notice a definite difference in the scrolling. I moved my Launcher pro scrolling speed down now from 100 to 45 because I no longer need it high with this fix. I also didn't wipe Davlik after pushing, but the file is in there when looking with Estrong file manager and the scrolling is definitely better now..
Thanks again..
Glad I could help! Wiping the Dalvik cache isn't really necessary I suppose, I just find it's good practice after doing anything to your build.prop to avoid possible glitches.
any reason why this wouldnt work on other devices?
Where exactly do I add this line? Thanks.
dev/null/ said:
Where exactly do I add this line? Thanks.
Click to expand...
Click to collapse
Just add it to the end of build.prop file.
Worked, I thank you for the reply and to the OP for the info.
Twidroyd
Could I get someone to fire up Twidroyd after applying this patch? Seems to cause super-heavy lag+slowdown in scrolling, but it appears that Twidroyd is the main offender.
This seems to work just fine for me. I guess it seems smoother... I can't really tell. Definitely not laggier.
Wouldn't you be able to open the build prop in something like Root Explorer's text editor and get the same result? I'm just not around my regular computer with adb setup... Thanks.
es0tericcha0s said:
Wouldn't you be able to open the build prop in something like Root Explorer's text editor and get the same result? I'm just not around my regular computer with adb setup... Thanks.
Click to expand...
Click to collapse
yes you can do this also.
Sent from my FroyoEris using XDA App
Implemented this tweak in my latest ROM and it definitely makes a difference
Sent from my nonsensikal froyo
I tried obtaining access through Root Explorer and it says that build.prop is read only?
drtchocky said:
I tried obtaining access through Root Explorer and it says that build.prop is read only?
Click to expand...
Click to collapse
You have to remember to make the directory R/W at the top of the screen.
Can't really tell if it made a difference. Has anyone experimented with setting the number even higher?
EDIT: Upon further review, it seems to have made my scrolling slightly smoother but also more likely to 'hitch'
Yeah, I think this is what I was seeing in Twidroyd. Scrolling is smoother in a list you've already scrolled through, but will stutter as it loads new table cells (a guess on my part, but it seems to make sense.)
Izeltokatl said:
You have to remember to make the directory R/W at the top of the screen.
Click to expand...
Click to collapse
Thanks! Rebooting now....
I think it's likely that if you aren't overclocking your phone may not be able to handle the extra load. If you aren't overclocking your phone or you're usually on a low cpu setting try chaing to 50. Anything above 35 will increase the smoothness, though not to the same extent. I don't suggest passing 60, I'm at 70 and the differences are negligable.
As for the lag and stutters, I haven't experienced that.
I did it. Didn't break anything, but didn't really seem to change anything either.
I have seen a huge difference in smoothness in screen scrolling as well as app drawer. I have large amt of apps and app drawer flies. One thing though I do not have a space before or after the equal sign on my line. Some of you who aren't seeing a huge difference take the spaces out and see if anything changes.
While poking around today, I discovered that I could deterministically cause "rild" to segfault - every time I tried it.
The method I used was to turn on WiFi with the Mobile Data network already running, and then I would launch the app "Wifi Analyzer" (farproc). Almost immediately the "rild" (Radio Interface Layer Daemon) would segfault. (Strictly speaking, I don't know if using WiFi Analyzer was necessary - my WiFi has beacons turned off, and sometimes I can't establish a session straight away; using a scanner seems to get my AP to come out of it's sleep).
That consistency convinced me to use strace to attach to the already-running "rild" daemon, and spew to a log file.
Note that historically, the SIGSEGV faults that were logged to the logcat output at the moment of the "undead call" implicated a problem in the fclose() call - almost as if something was trying to close a file that had not been opened correctly.
So, there in the strace output, was this:
Code:
16:43:23 writev(6, [{"\3", 1}, {"HTC_RIL\0", 8}, {"(t=1297817003)%% $HTC_3GIND:0\\r\\n\0", 35}], 3) = 44
16:43:23 open("/data/data/com.android.dmportread/history", O_WRONLY|O_CREAT|O_APPEND, 0666) = -1 ENOENT (No such file or directory)
16:43:23 chmod("/data/data/com.android.dmportread/history", 0666) = -1 ENOENT (No such file or directory)
16:43:23 writev(6, [{"\3", 1}, {"HTC_RIL\0", 8}, {"at_notify_cdma_g23_data_entry():Can't open /data/data/com.android.dmportread/history successfully \r\n\n\0",102}], 3) = 111
16:43:23 --- SIGSEGV (Segmentation fault) @ 0 (c) ---
a quick peek at /system/lib/libhtc_ril.so shows that - yep - buried in there is a reference to
/data/data/com.android.dmportread/history
So, I tried the following:
Code:
[COLOR=green][B]
mkdir /data/data/com.android.dmportread
chown radio:radio /data/data/com.android.dmportread
touch /data/data/com.android.dmportread/history
chown radio:radio /data/data/com.android.dmportread/history
[/B][/COLOR]
and guess what - no more segfaults. [SIZE=+3]YES![/SIZE]
If this is the cause of the "undead" call (seems highly likely), the explanation appears to be due to a bug in the HTC vendor library lbhtc_ril.so : a file open() fails, but the corresponding "close()" operation takes place anyway, and that is where the fault (segmentation violation) occurs. There is a stupid dependency of the libhtc_ril.so file on the DMPortRead.apk app.
Probably the only reason that this bug does not express itself in HTC "factory" 2.1 ROMs is because of the presence of DMPortRead.apk app - presumably that creates/maintains the history file.
[SIZE=+1]See the 3rd post of this thread for downloadable patch/script files[/SIZE]
If any of you are consistently experiencing the "undead call" problem, please consider testing the above to see if you think it is the fix. (I believe it is.)
bftb0
I knew I liked you!
I'll have to try this out when I get home.
Here's a flashable .zip and also a shell script which may be used in Gscript lite - you need to unpack the "unpackme.zip" file to get to them. ("unpackme" is NOT flashable).
I realized after I was 95% of the way through putting together the installer script that there was absolutely no reason to do this in an offline fashion (that is, "overflashing" it during a recovery boot) - it is perfectly fine to do what needs to be done in a shell script any time you please with the regular OS is running. Oh well, the ROM devs can look at it and use whatever they want from it (or nothing at all).
You can run the CureUndead_v0.9.sh script either from within the Gscript Lite app (you need to give the script root privilege), or you could use adb to push it to /data/local and chmod it and execute it by hand. Note that Gscript Lite on GingerBread has this annoying bug where it prints "stderr:" for every line in the original script. It's not my script that's doing that - it's either a problem with Gscript Lite, or something unusual about GSB.
Oh, yeah - the way the script is written, you can run it as many times as you want; as a side effect, this will truncate to zero length any prior history file.
MD5's and sizes of contents of "unpackme.zip":
0bf8c49312e61c436d379a24255b12f3 CureUndead_v0.9.sh - 421 bytes
9d459f9f598f51fffa98cf832c524e50 CureUndead_v0.9.zip - 2,678 bytes (this one is flashable)
Going to try it out... Thanks for this!
nice work...
Very interesting... so this is something that would need to be done post flash, what do you think...
... we use that lights.sh script conap put together in /system/xbin/ that runs @ every boot to initialize the lights for trackball/notifications... would it work if I added the lines to that? I'm not sure if it would cause issues running it @ each boot or not?
Trying to figure out a different way to add this pre-build too.
This is huge if it's the fix. Incredible work.
oceanminded said:
This is huge if it's the fix. Incredible work.
Click to expand...
Click to collapse
I think it is the fix
workshed said:
Very interesting... so this is something that would need to be done post flash, what do you think...
... we use that lights.sh script conap put together in /system/xbin/ that runs @ every boot to initialize the lights for trackball/notifications... would it work if I added the lines to that? I'm not sure if it would cause issues running it @ each boot or not?
Trying to figure out a different way to add this pre-build too.
Click to expand...
Click to collapse
Well, I'm putting together a flashable "fix" file that just uses the installer script, so it could be rolled up into a ROM install as well.
The one thing you might want at boot (rather than only at ROM install time) is some kind of zero-ing out of the history file every once in a while, so that it doesn't grow without bound. I only watched it for a short period of time, and it was only 4 lines long; it might not ever grow big, but that seems like the right thing to do.
So I guess I'll wait until one of you genuises makes this "point and click" simple. I don't have a clue how to implement this on my own. Awesome work bftb0 !
Sheesh you're a brain OP. Awesome job!
Sent from my Ginger Tazz using XDA App
Interesting... what's the undead call bug you're talking about? I've been getting this funny bug on long calls where sometimes the phone app just crashes after 15-30mins or so. I get the crash window, and if I force quit, it shows no signal until I reboot the phone. If that's the one, a fix would be really nice. Running KaosFroyo v39 and never flashed a new radio BTW.
I've also seen the same thing on the WiFi signal. I have SSID broadcast turned off, and it takes it's sweet time picking it up on its own, but running WiFi analyzer seems to wake it up.
ufmace said:
Interesting... what's the undead call bug you're talking about? I've been getting this funny bug on long calls where sometimes the phone app just crashes after 15-30mins or so. I get the crash window, and if I force quit, it shows no signal until I reboot the phone. If that's the one, a fix would be really nice. Running KaosFroyo v39 and never flashed a new radio BTW.
I've also seen the same thing on the WiFi signal. I have SSID broadcast turned off, and it takes it's sweet time picking it up on its own, but running WiFi analyzer seems to wake it up.
Click to expand...
Click to collapse
What he is referring to is during a call you get the tones and vibration like the call has been dropped but then you can hear the person on the other end again and the call was never dropped. What you are describing is a new one to me...
CondemnedSoul said:
What he is referring to is during a call you get the tones and vibration like the call has been dropped but then you can hear the person on the other end again and the call was never dropped. What you are describing is a new one to me...
Click to expand...
Click to collapse
Ah yeah, I've had that happen too. I didn't think of it, though, since it wasn't all that annoying to me. I already ran the fix anyways, so I'll see if it helps either problem.
I haven't had the problem for some reason, but I just entered all that in a terminal window on my phone (and wasn't that tedious). Thanks!
Scott586 said:
So I guess I'll wait until one of you genuises makes this "point and click" simple. I don't have a clue how to implement this on my own. Awesome work bftb0 !
Click to expand...
Click to collapse
I put up a script in the 3rd post in this thread which you could use in the Gscript Lite app. You will still need to figure out how to use Gscript Lite, but at least no "adb" or command-prompt typing is needed.
Everybody else - I would appreciate hearing back from you after you try this, especially if you have been experiencing the "undead call" bug frequently. (I've used my phone for calling so little recently I don't think it has happened to me in more than 5 weeks.) The more often it was happening to you in the past, the more valuable your feedback is now.
bftb0
bftb0 said:
I put up a script in the 3rd post in this thread which you could use in the Gscript Lite app. You will still need to figure out how to use Gscript Lite, but at least no "adb" or command-prompt typing is needed.
Everybody else - I would appreciate hearing back from you after you try this, especially if you have been experiencing the "undead call" bug frequently. (I've used my phone for calling so little recently I don't think it has happened to me in more than 5 weeks.) The more often it was happening to you in the past, the more valuable your feedback is now.
bftb0
Click to expand...
Click to collapse
thanks for the script bf, that's all I needed to add it in the rom. I'll be a tester also, as I do experience the bug quite often, but only on long calls which isn't as frequent for me currently. Bravo sir!
P.S. I will be sure to add "# Undead call fix by bftb0" in the rom and OP page
workshed said:
thanks for the script bf, that's all I needed to add it in the rom. I'll be a tester also, as I do experience the bug quite often, but only on long calls which isn't as frequent for me currently. Bravo sir!
P.S. I will be sure to add "# Undead call fix by bftb0" in the rom and OP page
Click to expand...
Click to collapse
dope
this is good news. great job op and workshed if u add it to your gb rom lol
love you both!
flashed it on gsb1.4. i'll let you know how it goes.
:O OMG! That always happens, but I thought I was crazy XD So I'm going to try this.
Sent from my Droid Eris ♥ (running Ginger Tazz v5 [eat your heart out Jobs])
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
Sorry for my poor english.
I really want Sense4a or Sense4 full version ROM in my phone as daily drive.
but current Sense4 ROM's performance compare with RCMix3D V4.0 + Neoc CFS kernel is poor....
the birds told to me, Virtuous Infinity alpha ROM plus V6SuperCharger can up performance & battery life!
but this threadhttp://forum.xda-developers.com/showthread.php?t=991276/ I can't understand....
who can provide me a simple teaching with illustrate??
thx
I read it and it seems like it would theoretically work on any device, any Rom. But I not sure whether you need to bake it in the Rom or if can be flashed through recovery. I would do a back up and see if it works.
Sent from my Inspire 4G using Tapatalk 2
V6 Supercharger is a script which you run trought smanager from android market
Sent from my HTC Desire HD using xda premium
Let me make you easier for you, as I just made my first supercharger on my dhd.
1. Go HERE and download SuperCharger_Starter_Kit_RC12.zip & V6_SuperCharger_for_Android-Update9_RC10.sh.pdf (attached on end of post). There is new version (V6_SuperCharger_for_Android-Update9_RC11_Test_4.sh.pdf), but its test file, so I stick with RC10.
2. Unzip supercharger starter kit -> put all files (including V6_SuperCharger_for_Android-Update9_RC10.sh.pdf) in some folder on SD card, where U will find them later.
3. Go on play store and download SManager
4. Open SManager -> Make it browse as root -> search your Supercharger starter kit folder -> Run StartMeUp.sh and before You hit "Run", please select "Su" option (it will make you green skull icon), below it. Now its time to press "Run" and follow instructions. As I didnt install BussyBox before, i followed on installation with all Yes on confirmation.
5. After you finish with StartMeUp.sh, you can press grey X on top left corner.
6. Search for V6_SuperCharger_for_Android-Update9_RC10.sh.pdf and open it. Same as before, before you hit "Run", make it "Su" (grey skull, after you press it, it will become green) -> Now press "Run".
7. Thats all, follow instructions and you will not need to make any custom editing as it was before 15.8.2012
If my post was helpfull for you, please press Thank You button
P.S.: My Virtuos Sense4 rom is still not so smoth, but i will remake it again with a little bit different settings in supercharger . Also i need to say, it is much smoother than before, but still not that what i want
Update:
If you are on Virtuos Infinity, change scene from Virtuos to HTC, its even smoother
droidhd said:
Let me make you easier for you, as I just made my first supercharger on my dhd.
1. Go HERE and download SuperCharger_Starter_Kit_RC12.zip & V6_SuperCharger_for_Android-Update9_RC10.sh.pdf (attached on end of post). There is new version (V6_SuperCharger_for_Android-Update9_RC11_Test_4.sh.pdf), but its test file, so I stick with RC10.
2. Unzip supercharger starter kit -> put all files (including V6_SuperCharger_for_Android-Update9_RC10.sh.pdf) in some folder on SD card, where U will find them later.
3. Go on play store and download SManager
4. Open SManager -> Make it browse as root -> search your Supercharger starter kit folder -> Run StartMeUp.sh and before You hit "Run", please select "Su" option (it will make you green skull icon), below it. Now its time to press "Run" and follow instructions. As I didnt install BussyBox before, i followed on installation with all Yes on confirmation.
5. After you finish with StartMeUp.sh, you can press grey X on top left corner.
6. Search for V6_SuperCharger_for_Android-Update9_RC10.sh.pdf and open it. Same as before, before you hit "Run", make it "Su" (grey skull, after you press it, it will become green) -> Now press "Run".
7. Thats all, follow instructions and you will not need to make any custom editing as it was before 15.8.2012
If my post was helpfull for you, please press Thank You button
P.S.: My Virtuos Sense4 rom is still not so smoth, but i will remake it again with a little bit different settings in supercharger . Also i need to say, it is much smoother than before, but still not that what i want
Update:
If you are on Virtuos Infinity, change scene from Virtuos to HTC, its even smoother
Click to expand...
Click to collapse
You can do all the steps above or just get AutoKiller Memory Optimizer Pro from Google play store. It does the same thing but through an a simple App.
Nothing does the same thing.
V6 is a complete fix which includes priority and grouping adjustments - not just minfrees.
If you don't know what I'm talking about, that means you don't know what you're talking about.
zeppelinrox said:
Nothing does the same thing.
V6 is a complete fix which includes priority and grouping adjustments - not just minfrees.
If you don't know what I'm talking about, that means you don't know what you're talking about.
Click to expand...
Click to collapse
Hey Zeppelinrox,
True, not all things do the same. But in this case simplicity works best.
Don't get me wrong. It's great that you wrote this script and a lot of people appreciate it including me and I hope you keep continuing to improve it. We just hope you would consider creating a front UI for it like an app since it would make things easier for people.
Thanks again for all your efforts.
droidhd said:
Let me make you easier for you, as I just made my first supercharger on my dhd.
1. Go HERE and download SuperCharger_Starter_Kit_RC12.zip & V6_SuperCharger_for_Android-Update9_RC10.sh.pdf (attached on end of post). There is new version (V6_SuperCharger_for_Android-Update9_RC11_Test_4.sh.pdf), but its test file, so I stick with RC10.
2. Unzip supercharger starter kit -> put all files (including V6_SuperCharger_for_Android-Update9_RC10.sh.pdf) in some folder on SD card, where U will find them later.
3. Go on play store and download SManager
4. Open SManager -> Make it browse as root -> search your Supercharger starter kit folder -> Run StartMeUp.sh and before You hit "Run", please select "Su" option (it will make you green skull icon), below it. Now its time to press "Run" and follow instructions. As I didnt install BussyBox before, i followed on installation with all Yes on confirmation.
5. After you finish with StartMeUp.sh, you can press grey X on top left corner.
6. Search for V6_SuperCharger_for_Android-Update9_RC10.sh.pdf and open it. Same as before, before you hit "Run", make it "Su" (grey skull, after you press it, it will become green) -> Now press "Run".
7. Thats all, follow instructions and you will not need to make any custom editing as it was before 15.8.2012
If my post was helpfull for you, please press Thank You button
P.S.: My Virtuos Sense4 rom is still not so smoth, but i will remake it again with a little bit different settings in supercharger . Also i need to say, it is much smoother than before, but still not that what i want
Update:
If you are on Virtuos Infinity, change scene from Virtuos to HTC, its even smoother
Click to expand...
Click to collapse
really simple. I will try this within a few days.
I hope I can rock in the Virtuous Infinity Alpha ROM, taste full Sense4.0
http://gphonefans.net/forum.php?mod=redirect&goto=findpost&ptid=45392&pid=725671&fromuid=263995
this a SuperCharger setup guide link. in this thread have photo & step, I really wont to see this style of guide.
However, I will get used to your way of teaching. :good:
blade1198 said:
Hey Zeppelinrox,
True, not all things do the same. But in this case simplicity works best.
Don't get me wrong. It's great that you wrote this script and a lot of people appreciate it including me and I hope you keep continuing to improve it. We just hope you would consider creating a front UI for it like an app since it would make things easier for people.
Thanks again for all your efforts.
Click to expand...
Click to collapse
Every time you talk, you say something incorrect.
Simplicity has no bearing on effectiveness and does not work best in this case.
When it's an app, I'm sure people will still be confused as **** even tho it will be as idiot proof as possible.
Just like the script is now, it's as idiot proof as possible and people still get confused as ****.
zeppelinrox said:
Just like the script is now, it's as idiot proof as possible and people still get confused as ****.
Click to expand...
Click to collapse
It's really idiot-proof
I'm using it besides and while were here, I just wanna thank you for this script, really gives a boost to my device
zeppelinrox said:
Every time you talk, you say something incorrect.
Simplicity has no bearing on effectiveness and does not work best in this case.
When it's an app, I'm sure people will still be confused as **** even tho it will be as idiot proof as possible.
Just like the script is now, it's as idiot proof as possible and people still get confused as ****.
Click to expand...
Click to collapse
This was currently written by another member:
While the guy that wrote the script is obviously a very very talented programmer, he's a horrible technical writer. Something as profound as memory management deserves clear and well-delineated overviews and instructions. I was left wondering at every step. The changes in font size, colours, and collapsible buttons weirded me out!
The script is way too much.
I would've preferred very succinct instructions and prompts during the script.
Does help for sure. Run your choice of memory widget and see!
At the next release of this ROM ill flash again (back on ARHD 6.3.3) but there are little things that are driving me batty - MMS/dropped connection, stereo bluetooth pairings that just drop off and need a reboot or re-pairing, and a periodic sluggishness that creeps in and out.
I'm very excited to see where this goes!
Sent from my Desire HD using xda premium
Telus Desire HD (Toronto)
The was written by thousands of people:
Between 5 and 10% think it's too complicated so didn't try it.
Of those that actually used it (2850 votes)...
47% call it the best mod ever,
Over 64% see a big performance boost.
Over 80% claim a noticeable performance boost.
I don't cater to those easily confused or illiterate or lazy so I'd rather weed them out nice, nice - cuts down on the stupid questions.