Related
I don't know if anyone knews this:
the Incredible S is unable to be used as a Hands Free Set with the Ear Piece Cabel plugged in.
I use my phone to make calls while driving. The Phone is connected via an adapter to the car audio kit and I wanna use the interal microphone.
Now, the internal HTC Noise cancellation blocks my voice... bad idea.
HTC don't want to help me.
On Nexus One, we have had the same problem, but we found out, that we can change one value in the build.prop to disable the noise cancellation.
http://forum.xda-developers.com/showthread.php?t=700958
Now I've searched the build.prop about this value, but I can't find it. Can anybody help me?
EDIT:
OK,
I've figured it out! ROOT IS REQUIRED!!!
You can fix this with root explorer or any application like this.
1. Navigate to the system folder
2. open the build.prop with an text editor
3. Search this line
htc.audio.alt.enable=1
Click to expand...
Click to collapse
4. and change it to the follow (yes, it's only switching from 1 to 0 - enabled to disabled)
htc.audio.alt.enable=0
Click to expand...
Click to collapse
5. save this as build.prop
6. reboot
7. ready
I want to know it too. But have you try adding that statement to the build.prop file even if it doesn't exist? I assume your IS is rooted, of course.
OK,
I've figured it out! ROOT IS REQUIRED!!!
You can fix this with root explorer or any application like this.
1. Navigate to the system folder
2. open the build.prop with an text editor
3. Search this line
htc.audio.alt.enable=1
Click to expand...
Click to collapse
4. and change it to the follow (yes, it's only switching from 1 to 0 - enabled to disabled)
htc.audio.alt.enable=0
Click to expand...
Click to collapse
5. save this as build.prop
6. reboot
7. ready
Thanks alot...
This is built into CM7 7.1 RC1 and still the mic does not work.
Any other suggestions?
FormelLMS said:
OK,
I've figured it out! ROOT IS REQUIRED!!!
You can fix this with root explorer or any application like this.
1. Navigate to the system folder
2. open the build.prop with an text editor
3. Search this line
4. and change it to the follow (yes, it's only switching from 1 to 0 - enabled to disabled)
5. save this as build.prop
6. reboot
7. ready
Click to expand...
Click to collapse
I tried this and my htc handsfree still doesn't work
Any other ideas?
Sent from my Incredible S using Tapatalk
Since the GB update it works on my phone.
Sent from my HTC Incredible S using XDA App
doesnt seem to want to work on my phone: running unity 1.29 ... still dont seem to get the mic on my headset working :S ... can hear myself talking but no voice goes thru... aghhh
Build.prop
In my build.prop tere are two lines very similar:
htc.audio.alc.enable=1
htc.audio.swalt.enable=1
but there isn't alt! I've the ICS rom "We want ICS by Nikhil007". How can I do?
Thanks.
Hi there!
I want to disable the backlights of the softkeys, without installing an ad-filled apk.
I have installed Slimrom 4.3 from maclaw.pl and the setting to turn backlight off is invisible.
If you go with an rooted file explorer to /sys/class/leds/brightness and switch the value to 0, the backlight immediately turns off.
But if u restart the phone the value is changed everytime to 1 and the Backlight is back on.
So i thought i could write a script, that do this job for me., everytime i start my phome. The script is in the attachments.
Can anyone check if the script is okay? I dont want to brick my phone
And Do you know where the autostart folder for android devices is (like in windows), ive read something about kernel init or something.
And if i want to make a flashable zip out of this script, How to make it? because i dont want everytime i flash an update to work in the system.
Thanks for your time
Go to system settings-buttons-backlight & disable it. If that option it's not present on slim, simply download this. Don't mess with any system file cause this ain't a xperia phone:laugh:
Thanks, but my device is not listed under supported devices in this app and i dont want to keep a 3rd party app running that increases the battery drain and takes ram away. i prefer a little script at system start.
And no the option is not listed in the settings.
kinqme said:
Thanks, but my device is not listed under supported devices in this app and i dont want to keep a 3rd party app running that increases the battery drain and takes ram away. i prefer a little script at system start.
And no the option is not listed in the settings.
Click to expand...
Click to collapse
FYI, I'm using bln app & doesn't drain my bat nor ram (on cm11). Have a nice day
Okay i found that folder it is localized in /system/etc/init.d
I copied the file to there and it is workimg, on every restart the buttons keeps off.
But how to make a flashable zip with that file? is it enough to create a zip with the folder system and its contents are only th underfolder and the file?
kinqme said:
Okay i found that folder it is localized in /system/etc/init.d
I copied the file to there and it is workimg, on every restart the buttons keeps off.
But how to make a flashable zip with that file? is it enough to create a zip with the folder system and its contents are only th underfolder and the file?
Click to expand...
Click to collapse
Search on xda how to make it & if you sure it works I'll add it to my FAQ
Simple flashable fix for that http://www.mediafire.com/?dcq8si0xa1s348j
PolishVodka said:
Simple flashable fix for that http://www.mediafire.com/?dcq8si0xa1s348j
Click to expand...
Click to collapse
I asume it works on all maclaw roms (cm11) too, right!? Can I add it to my FAQ here. Of course I'll give you the proper credits on the special thanks section.
Here we go.
One zip to disable them and one to undo the patch.
thanks for your time
Can I add it to my FAQ?
Of course then other people who has the same problem can solve this problem
kinqme said:
Here we go.
One zip to disable them and one to undo the patch.
thanks for your time
Click to expand...
Click to collapse
Don't think so is good script, because when you got a notification than BLN turn on lights again and will be stay it on to second boot.
sorry my very first try.
i will look on my device, if this happens to me too
The only problem i had was with whatsapp, if u get a message there, the light keeps on till restart.
But in settings - notifications - lights in whatsapp u can turn off the notification lights and then the problem is solved. ( standard is white )
Tahnk you polishwodka
kinqme said:
Here we go.
One zip to disable them and one to undo the patch.
thanks for your time
Click to expand...
Click to collapse
Thanks
Hi,
I have flashed a custom rom for the very first time.
I have flashed OMNI rom 18/12 build.
I find the haptic feedback or the vibration intensity too high to my liking. I can't find any setting where I can configure this.
The phone vibrates very strongly even when i press things like 'menu' , 'back button' or typing
Its very annoying, please help
kckinn said:
Hi,
I have flashed a custom rom for the very first time.
I have flashed OMNI rom 18/12 build.
I find the haptic feedback or the vibration intensity too high to my liking. I can't find any setting where I can configure this.
The phone vibrates very strongly even when i press things like 'menu' , 'back button' or typing
Its very annoying, please help
Click to expand...
Click to collapse
I think your only solution for that is to turn it off... Or to find out what to change to make it lower. You do not have an option in settings for that.
shut_down said:
I think your only solution for that is to turn it off... Or to find out what to change to make it lower. You do not have an option in settings for that.
Click to expand...
Click to collapse
I am willing to turn off the haptic feedback, but I can't find any option for that anywhere.
kckinn said:
I am willing to turn off the haptic feedback, but I can't find any option for that anywhere.
Click to expand...
Click to collapse
I can't remember where it was, but I did remove it when I used Omni. Try settings>more options - search there.
shut_down said:
I can't remember where it was, but I did remove it when I used Omni. Try settings>more options - search there.
Click to expand...
Click to collapse
Hi,
Thanks again. I found the option to completely turn it off yesterday. Sad, there was no feature to reduce its intensity.
After turning it off, I realized the samsung JB always had a subtle vibration feedback when touching all this. Initially found it a bit weird getting no vibration but now used to it.
Another thing, in samsung JB I could sync FB contacts as well. In this ROM neither does the option in 'contacts' nor in FB app allow to sync contacts to phone book. Not a major issue though.
But, in samsung JB I could sync my calendar with FB, so that I could see all b'days etc on my calendar. No option here. Even though FB is displayed under 'accounts' in setting. There is no option to sync.
But the great thing about it is its speed. There is no lag whatsoever, very smooth so far.
Have a couple of free days in hand, so thinking of trying out CM 10.2 as well
kckinn said:
Hi,
Thanks again. I found the option to completely turn it off yesterday. Sad, there was no feature to reduce its intensity.
After turning it off, I realized the samsung JB always had a subtle vibration feedback when touching all this. Initially found it a bit weird getting no vibration but now used to it.
Another thing, in samsung JB I could sync FB contacts as well. In this ROM neither does the option in 'contacts' nor in FB app allow to sync contacts to phone book. Not a major issue though.
But, in samsung JB I could sync my calendar with FB, so that I could see all b'days etc on my calendar. No option here. Even though FB is displayed under 'accounts' in setting. There is no option to sync.
But the great thing about it is its speed. There is no lag whatsoever, very smooth so far.
Have a couple of free days in hand, so thinking of trying out CM 10.2 as well
Click to expand...
Click to collapse
Maybe some app can help you with FB sync.
Hi,
You may be aware of the problem with the dash clock. It force closes. And it appears partially cut in the lock screen.
After going through the OMNI rom, I found that you had mentioned in post no. #225 to go to system/app and delete dashclock.apk from there.
Since there is no file manager in this ROM. I installed ES file manager and tried to delete dashclock.apk from system/app
But when I try to delete it says "dashclock.apk can not be deleted". I don't know why ?
Is it anything to do with rooting ? I found some discussion in the forum about rooting as well. But couldn't make much of it.
kckinn said:
Hi,
You may be aware of the problem with the dash clock. It force closes. And it appears partially cut in the lock screen.
After going through the OMNI rom, I found that you had mentioned in post no. #225 to go to system/app and delete dashclock.apk from there.
Since there is no file manager in this ROM. I installed ES file manager and tried to delete dashclock.apk from system/app
But when I try to delete it says "dashclock.apk can not be deleted". I don't know why ?
Is it anything to do with rooting ? I found some discussion in the forum about rooting as well. But couldn't make much of it.
Click to expand...
Click to collapse
Root it, set usb debugging on, in ES file explorer set Root explorer ON. Or use some other root explorer if that do not work.
shut_down said:
Root it, set usb debugging on, in ES file explorer set Root explorer ON. Or use some other root explorer if that do not work.
Click to expand...
Click to collapse
I read in the OMNI forum that installing OMNI Rom automatically roots the phone. So is that not true ? If that is the case I will google and find how to root the phone.
I tried to turn on 'root explorer' in the ES file manager. It says 'Sorry, test failed. This feature can not run on your device". Is it an indicator of the the fact that the phone is not rooted ?
Edit: Temporary workaround: I found the post wherein you had told a user how to expand the dash clock widget by sliding it down and holding it and removing it by taking it to the 'x'. I removed it from the lock screen and added the normal clock in its place.
kckinn said:
I read in the OMNI forum that installing OMNI Rom automatically roots the phone. So is that not true ? If that is the case I will google and find how to root the phone.
I tried to turn on 'root explorer' in the ES file manager. It says 'Sorry, test failed. This feature can not run on your device". Is it an indicator of the the fact that the phone is not rooted ?
Edit: Temporary workaround: I found the post wherein you had told a user how to expand the dash clock widget by sliding it down and holding it and removing it by taking it to the 'x'. I removed it from the lock screen and added the normal clock in its place.
Click to expand...
Click to collapse
No it doesn't have SU binaries installed.
metalhead.mechie said:
No it doesn't have SU binaries installed.
Click to expand...
Click to collapse
@metalhead.mechie Well I don't know what that means. I dont know much about tech stuff
From what I have gathered from the discussion in the OMNI Rom Forum, that I download something called 'Super SU" from http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip .
Question:
1. Do i need to extract the contents of the zip ? Or just go to TWRP and just select install from SD card and select the zip folder like i did with OMNI and gapps ?
2. Will this root the phone or do I need to follow other procedure as well ?
kckinn said:
@metalhead.mechie Well I don't know what that means. I dont know much about tech stuff
From what I have gathered from the discussion in the OMNI Rom Forum, that I download something called 'Super SU" from http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip .
Question:
1. Do i need to extract the contents of the zip ? Or just go to TWRP and just select install from SD card and select the zip folder like i did with OMNI and gapps ?
2. Will this root the phone or do I need to follow other procedure as well ?
Click to expand...
Click to collapse
Just install zip in TWRP. And check if usb debugging is on later in Developer options.
kckinn said:
@metalhead.mechie Well I don't know what that means. I dont know much about tech stuff
From what I have gathered from the discussion in the OMNI Rom Forum, that I download something called 'Super SU" from http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip .
Question:
1. Do i need to extract the contents of the zip ? Or just go to TWRP and just select install from SD card and select the zip folder like i did with OMNI and gapps ?
2. Will this root the phone or do I need to follow other procedure as well ?
Click to expand...
Click to collapse
Just flash the zip as shut_down said. This zip contains the binaries as well as supersu app for root acess
To make Xposed's AppSettings' DPI function work, I reverted this change: https://github.com/LiquidSmooth/and...92#diff-82378faf2a467d2f28e834dddd59207eR1363
Updated 01/04/2015 Build with overclock http://web.mit.edu/ispatel/www/builds/lsoc/LS-KK-v3.2-2015-01-04-vs980_yes_properoc.zip
First... Awesome. How did I beat Lawlrus.
Mightycaptain said:
First... Awesome. How did I beat Lawlrus.
Click to expand...
Click to collapse
I blame work on that one.
Glad to see a build of liquid again op, thank you. I'll DL at work and see about flashing.
Sent from my Vs980 running Aicp 5.0 4.4.4_r2
Edit nevermind, brain fart.
Its 4.4.4, can't read, sorry
@ishyesh
Maybe I'm missing it, but is there a toggle for knock on? Doesn't seem to be working and I don't see the option.
Sent from my LG-VS980
Lawlrus said:
@ishyesh
Maybe I'm missing it, but is there a toggle for knock on? Doesn't seem to be working and I don't see the option.
Sent from my LG-VS980
Click to expand...
Click to collapse
The knock code value is probably set to "0" instead of "1" in the kernel. ishyesh will most likely have to change the value in the kernel before compiling.
You can use a script to activate it in the mean time (assuming there is no option anywhere in the settings to turn it on or off).
EDIT: Try this (see if it fixes it): http://www.mediafire.com/download/icnb1bu56nq4jb9/Turn_Knockon-On_G2.zip
@bouchigo
Thanks, but it didn't work. I for the life of me cannot find the option to enable knock on if there is one. I'll just wait for op to respond I guess.
Edit: so it did work. But you need to make sure use proximity sensor to have it turn on.
I did mess with this option before flashing your zip, and it didn't work. So your zip definitely fixed it.
Thanks again bro.
Sent from my LG-VS980
Lawlrus said:
@bouchigo
Thanks, but it didn't work. I for the life of me cannot find the option to enable knock on if there is one. I'll just wait for op to respond I guess.
Edit: so it did work. But you need to make sure use proximity sensor to have it turn on.
I did mess with this option before flashing your zip, and it didn't work. So your zip definitely fixed it.
Thanks again bro.
Sent from my LG-VS980
Click to expand...
Click to collapse
To enable knock-on,
use Tasker or some sort of automation software to execute this whenever the system boots:
"echo 1 > /sys/devices/virtual/input/lge_touch/touch_gesture"
Also, I uploaded a camcorder fix in the OP. Flash like any other.
To change DPI for the overall system, use an application like "texdroider dpi". I haven't tested the built in DPI changer.
ishyesh said:
To enable knock-on,
use Tasker or some sort of automation software to execute this whenever the system boots:
"echo 1 > /sys/devices/virtual/input/lge_touch/touch_gesture"
Also, I uploaded a camcorder fix in the OP. Flash like any other.
To change DPI for the overall system, use an application like "texdroider dpi". I haven't tested the built in DPI changer.
Click to expand...
Click to collapse
I just changed the build prop using root browser. Thanks.
Also flashing that zip persists through reboots. No need to set a tasker if you flash that.
Sent from my LG-VS980
Btw, I'm not sure how Linux literate you guys are, but if you're curious and want to learn, try and unzip the KnockOnZip that bouchigo posted. Inside, you'll find a file within the path system/etc/init.d . Upon flashing, the script within that path is copied to your phone's /system/etc/init.d. On your phone, you can place whatever you want inside this directory so that it gets called whenever Android starts (read up on the naming of the script, that's critical). So in the zip, the 98knock-on-On script executes the same command I said you could tell Tasker to do.
Go crazy with that if you wish. And remember, make sure you check every zip that you flash.
ishyesh said:
Btw, I'm not sure how Linux literate you guys are, but if you're curious and want to learn, try and unzip the KnockOnZip that bouchigo posted. Inside, you'll find a file within the path system/etc/init.d . Upon flashing, the script within that path is copied to your phone's /system/etc/init.d. On your phone, you can place whatever you want inside this directory so that it gets called whenever Android starts (read up on the naming of the script, that's critical). So in the zip, the 98knock-on-On script executes the same command I said you could tell Tasker to do.
Go crazy with that if you wish. And remember, make sure you check every zip that you flash.
Click to expand...
Click to collapse
You probably already know this, but if you go into devices folder, and into the vs980 folder (I can't remember the folder structure, I haven't looked at source in a while), anyway, look for init.g2.rc and change the following before compiling:
From: chown system system /sys/devices/virtual/input/lge_touch/touch_gesture
To: write /sys/devices/virtual/input/lge_touch/touch_gesture 1
That should fix it so no scripts or tasker actions are required.
bouchigo said:
The knock code value is probably set to "0" instead of "1" in the kernel. ishyesh will most likely have to change the value in the kernel before compiling.
You can use a script to activate it in the mean time (assuming there is no option anywhere in the settings to turn it on or off).
EDIT: Try this (see if it fixes it): http://www.mediafire.com/download/icnb1bu56nq4jb9/Turn_Knockon-On_G2.zip
Click to expand...
Click to collapse
This zip worked great for me: VS98025A. Thanks
bouchigo said:
You probably already know this, but if you go into devices folder, and into the vs980 folder (I can' remember the folder structure, I haven't looked at source in a while), anyway, look for init.g2.rc and change the following before compiling:
From: chown system system /sys/devices/virtual/input/lge_touch/touch_gesture
To: write /sys/devices/virtual/input/lge_touch/touch_gesture 1
That should fix it so no scripts or tasker actions are required.
Click to expand...
Click to collapse
I did not know that! I'll be sure to incorporate that in my next iteration. Thank you!
http://forum.xda-developers.com/showthread.php?p=54906959#post54906959
Lawlrus said:
@ishyesh
Maybe I'm missing it, but is there a toggle for knock on? Doesn't seem to be working and I don't see the option.
Sent from my LG-VS980
Click to expand...
Click to collapse
could this also work? Worked for me on other ROMs. Liquid was one of my favorite GNEX roms.
mrdunn said:
http://forum.xda-developers.com/showthread.php?p=54906959#post54906959
could this also work? Worked for me on other ROMs. Liquid was one of my favorite GNEX roms.
Click to expand...
Click to collapse
No. I've never updated to knock code. So it didn't have anything to do with my touch firmware. Knock on needs manually turned on.
Sent from my Vs980 running CloudyFlex 2.6
Great work
Sent from my VS980 4G using Tapatalk
The best ROM!!!
The smoothness and fluidity of the UI is amazing.
Use one plus bionic optimized binaries and flash seeder using interactive governor and deadline as scheduler. Then, you have the best user experience on an Android device.
@luv2increase
Check yo pms
Sent from my Vs980
Anybody having issues with youtube playback on this Rom? I went back to stock for now as this Rom wasn't playing a lot of the youtube videos I was trying to watch.
What's the exact youtube error message?
Q&A for [ROM][GPL]Clean_Cm_7.2[26-05-2014]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Possible bug
First of all: Awesome ROM! Never knew CM 7.2 could be this fast and stable!
Second: I've possibly found two bugs:
1, Entering "Settings/CyanogenMod Settings/Lockscreen settings/Delay and timeout" always cause a FC.
Always.
Have tried rebooting and shutting down but the FC remain.
2, Power button does not activate lockscreen, it only shuts the screen off. Pressing power button again or home button will go directly to home screen. The only way to activate lockscreen is to let screen timeout.
Have tried different screen locks but nothing makes power button behave differently.
I've searched around in setting for a way around this but so far unsuccessfull.
Maybe the two issues are related.
And now some requests:
* A big button keyboard? Stock was good with big buttons for my sausage fingers.
* Ability to easily add foreign language keyboards (not system language) and dictionaries.
* Remove delete thread confirmation in messages.
* Remove confirmation when enabling storage by USB connection.
* Ability to easily add sounds without trying to find the setting for each event. Still haven't found out how to change the alarm sound...
I'm not really sure what is causing your problems as I never faced these issues. My suggestion is the following.
1. Reboot to recovery
2. Format system
3. Wipe data&factory reset
4. Install Rom
5. Reboot
6. Reboot again
I take it, that you did not change the Rom package?
Wunder_luftmjuk said:
* A big button keyboard? Stock was good with big buttons for my sausage fingers.
* Ability to easily add foreign language keyboards (not system language) and dictionaries.
Click to expand...
Click to collapse
I left it to the user to download and choose a keyboard on their own. There are plenty in the playstore
* Remove delete thread confirmation in messages.
Click to expand...
Click to collapse
Hm, not really something I would personally enjoy, but maybe
* Remove confirmation when enabling storage by USB connection.
Click to expand...
Click to collapse
Trust me, I tried that one, but couldn't get it to work. I even tried copying the function of the xposed module..
* Ability to easily add sounds without trying to find the setting for each event. Still haven't found out how to change the alarm sound...
Click to expand...
Click to collapse
This is fairly easy, just drop the sounds into /system/media/audio/alarms
Our create a folder structure like media/sounds/alarms on your sdcard.
I hope that helps.
Sorted
Wooaarr said:
I'm not really sure what is causing your problems as I never faced these issues. My suggestion is the following.
1. Reboot to recovery
2. Format system
3. Wipe data&factory reset
4. Install Rom
5. Reboot
6. Reboot again
I take it, that you did not change the Rom package?
I left it to the user to download and choose a keyboard on their own. There are plenty in the playstore
Hm, not really something I would personally enjoy, but maybe
Trust me, I tried that one, but couldn't get it to work. I even tried copying the function of the xposed module..
This is fairly easy, just drop the sounds into /system/media/audio/alarms
Our create a folder structure like media/sounds/alarms on your sdcard.
I hope that helps.
Click to expand...
Click to collapse
Thank you for the help!
The "Delay and timeout" setting kept getting FC, until I went into security setting and disabled all security (pattern, pin, e.t.c.).
After that there was no more FC, and I could change the settings in "Delay and timeout". This also fixed the other "bug" which was power button not locking screen. Subsequently I could again change back security settings to pattern.
The other things I can live with! :laugh:
B.t.w. do you know any kernel that supports adaptive undervolting/overvolting combined with underclocking/overclocking? Also, is there any better governor than "ondemand"?
Suggestions for task killers? Many recommend Greenify but it won't run on android 2.3.x.
My aim is to have maximum battery life when on standby, while still having good performance in times of need.
Thanks again!
Wunder_luftmjuk said:
Thank you for the help!
The "Delay and timeout" setting kept getting FC, until I went into security setting and disabled all security (pattern, pin, e.t.c.).
After that there was no more FC, and I could change the settings in "Delay and timeout". This also fixed the other "bug" which was power button not locking screen. Subsequently I could again change back security settings to pattern.
Click to expand...
Click to collapse
I will dig out my old mini and see if I can reproduce that bug. I never used any security pattern, so that might be the reason I never had any trouble.
B.t.w. do you know any kernel that supports adaptive undervolting/overvolting combined with underclocking/overclocking? Also, is there any better governor than "ondemand"?
Suggestions for task killers? Many recommend Greenify but it won't run on android 2.3.x.
Click to expand...
Click to collapse
I don't think that there is a kernel that supports custom uv for the galaxy mini. However I found that the ondemand governor works very well. I could never really complain leaving it on 600 mhz. I have to admit though that it is an old phone, so don't expect any wonders .
My battery backup was always a minimum of 2 days, but I don't do any gaming. I used my phone as a phone... ( And a bit of music and internet).
Taskkillers are generally a bad idea, as they will just cause a cat and mouse game between them and a dodgy app. I'm not sure if the xposed module (I think the name is something with service disable) was backported to gingerbread. Anyway I never used it and if you want to try something maybe go for "auto start disabler free" from the playstore. That is what I used.
I hope this helps to enjoy your mini a bit more
New bug
OK I guess I have to play around with settings and apps to see how battery life can be extended.
B.t.w. I found a new bug: Camera shutter sound can't be disabled. Even when turned off in CM settings the camera will still play the click.
This is the best rom i have been used
its light, fast, and very stable.
thats what i want
I have 2 questions,,is this rom for galaxy mini gt-s5570..and can i flash over jellybean rom with full wipes,or do i have to revert to stock first?
blueangel4ever said:
I have 2 questions,,is this rom for galaxy mini gt-s5570..and can i flash over jellybean rom with full wipes,or do i have to revert to stock first?
Click to expand...
Click to collapse
you can just wipe and then flash this rom..
i'm from jelly bean rom too, and i'd do that
Damn man! Your ROM is completely stable, really like it a lot .. I personally recommended this theme http://forum.xda-developers.com/showthread.php?t=1499191 to you guys cause it is looks PERFECT to combine with the HOLO Launcher by Mobint, if you guys confront with lagging issue, just use this setting (Setting > CyanogenMod setting > Performance > CPU Setting & select Governors choose to PERFORMANCE and set MAX CPU Frequency to 806 MHz & reboot
ICS Theme that I found
This theme i found on xda is a great companion with this rom and HOLO Launcher
Bootsplash
Can I flash a "bootsplash.zip" in this ROM?
Make a backup first and then try...
Next time try to ask in a nice way and I might test it for you...
Wooaar? Its seems I can't flash the "bootanimation.zip" [installation aborted]
S5 bootanimation that I dig from xda website
you should reconsidered to place back the GINGERBREAD "Zombie ART" picture as it will brings an original ROM feels ... and sorry for asking that way the other day, it was a joke, sorry dude .. btw you did really a good job
Since when is a boot animation flashable anyway? You should just put it into system/media.
But I also deleted the script that executes the boot animation from /bin, so you would have to replace that as well.
I will not put the zombie art back in, as it is of no use, but just steals space.
Already tried to put it at system/media, but didn't works .. tell me about the script please? how to replace it
and take a look at this dude http://forum.xda-developers.com/showthread.php?t=2708316
This is indeed a flashable zip. Two things come to my mind.
1. Your recovery simply doesn't like the zip. Which version are you using?
2. Your zip is broken. Maybe the download did not finish?
In either way you have to replace the bootanimation binary in /bin. You can grab it from any rom, replace it and give it the proper permissions. Our you wait till I come back home and upload it for you.
I use yagya CWM 5.0.2.8 Touch recovery and indeed I finished the download 100% using IDM .. really hope you can help me .. thanks btw
Ok, as I have no power for today and my laptop is empty I quickly patched something up in my phone. I'm not sure if that is going to work...
Give it a shot and let me know.
Flash via recovery.
Wooaarr said:
Ok, as I have no power for today and my laptop is empty I quickly patched something up in my phone. I'm not sure if that is going to work...
Give it a shot and let me know.
Flash via recovery.
Click to expand...
Click to collapse
Installation complete but still blank screen & about the binary you ask me to grab it on another rom, you mean any rom?? including other phone rom?? as I do not download any custom rom for Galaxy Mini other than yours & my internet is not as fast as light tho, could you upload the binary script?? then replace it using root explorer right? then what is the proper permission to put on that binary script later?