Related
I have flashed Miracle v4 for my phone.
Following the tutorial, i was able to get stuff like camera and calculator works.
But was unable to get sound recorder to work, it force closes everytime i press 'start recording'.
Any help ? Thanks in advance.
There now is a fix for it. Read the first few posts in the original Miracle V4 thread you should find the solution there!!
Thanks.
I read thru the first few posts again.
If you are talking about the tutorial which is this :
TUTORIAL 5: Recover System Apps than have been removed from V3
-- Place your desired app or apps on your sd-card
-- Use Root Explorer and copy them
-- Go to system\app and press the Mount R/W button on right top
-- Paste the app or apps you have selected
-- Long press what have you just pasted and set permissions to rw-r--r-- for each app
-- Reboot phone
Yes, i followed this. Was able to recover apps like camera. But sounds recording doesn't work.
If i misses out something, can you help me with pointing me to the particular fix for it ? I've done searching, and no people seems to be asking about sound recorder.
Thanks
rhythmyun said:
Thanks.
I read thru the first few posts again.
If you are talking about the tutorial which is this :
TUTORIAL 5: Recover System Apps than have been removed from V3
-- Place your desired app or apps on your sd-card
-- Use Root Explorer and copy them
-- Go to system\app and press the Mount R/W button on right top
-- Paste the app or apps you have selected
-- Long press what have you just pasted and set permissions to rw-r--r-- for each app
-- Reboot phone
Yes, i followed this. Was able to recover apps like camera. But sounds recording doesn't work.
If i misses out something, can you help me with pointing me to the particular fix for it ? I've done searching, and no people seems to be asking about sound recorder.
Thanks
Click to expand...
Click to collapse
Just download the latest version. It has a the video recording fix, BLN fix and 30volume step
Recording sound for me works perfectly, no FCs.
no it's not about that, it's something to do with video recording as well. There is a fix there I managed to sort the problem out myself. Alternatively you could redownload v4, the dev has now updated the original rom with the fix's added.
My video recording is working after changing the "true false" code stuff (not sure what it is called)
However the sound recording doesnt work.
I guess i will just do a reflash.
But an extra question, if i do a reflash, do I have to re backup all my apps and data ? Or i can just reflash without going to factory reset, dalvik wiping etc ?
Thanks
You can just flash over the top but you might have to reinstall some of you stock apps ie sms, music, gallery ect..
Thanks guys. I reflashed and it is working now.
My sound recorder works but in 3gp format. Is there a way to make it mp3 or whatever format?
Hello, I hope someone can help me.
The scenario is the following:
I've got a optimus black (Obviusly) flashed with the lastest cyanogenmod (cm-10.1-20130221). The problem is the in-call volume, it's as low I can't hear anything if I'm in the street so, I searched posts related with this issue, I found and tried:
-Volume+ --> It was the only which worked but, unfortunately the earphone boost is very slight, so it isn't enough.
-Increasing the volume steps --> This does nothing for my purposes, no earphone boost.
-AudioHack 2.1 --> This neither worked.
So, after I've tried this "methods", I saw in other models (I don't now if in mine is possible) a way in which you modify a file to gain more volume. This is the post I'm refering to:
http://forum.xda-developers.com/showthread.php?t=1722136
Is this possible in optimus black?
Thanks in advance.
Try this:
http://forum.xda-developers.com/showpost.php?p=38168998&postcount=1272
dcop7 said:
Try this:
http://forum.xda-developers.com/showpost.php?p=38168998&postcount=1272
Click to expand...
Click to collapse
I've done all that you say in your post, I think I'm doing something wrong because when I reboot my phone it doesn't goes further the lg logo. I'm going to explain you how I'm doing your steps.
Scenario: cm-10.1-20130221 with google apps (Last version)
-I use the default file explorer which comes with cyanogenmod (In root mode)
-Then I go to /system/
-After that, I open the file with the default text editor which comes by default with cyanogenmod and at the bottom of the file I write "ro.config.vc_call_vol_steps=5", and then I save the file
-Finally I open the properties of the file with file explorer and I set rw-rw-rw
am I right? If not, say me the way you do this or the step(s) I'm doing wrong.
Thanks a lot
In CM you don't have to do that. In CM, the calls are good
dcop7 said:
In CM you don't have to do that. In CM, the calls are good
Click to expand...
Click to collapse
Yes, I realised of that yesterday. I was doing some test aaand after seeing the thread of your response, I'm giving a try to IZS. It manages very very well the resources of the phone, cool theme and so on...The only that worries me now is the manage of the battery but anyway thanks for all .
If you want, you can test this:
http://forum.xda-developers.com/showpost.php?p=38383025&postcount=1341
dcop7 said:
If you want, you can test this:
http://forum.xda-developers.com/showpost.php?p=38383025&postcount=1341
Click to expand...
Click to collapse
I've tried it and I think now it sounds a bit more clear or clean than before. Thanks, I'm following you in the other IZS post.
Hello everyone,
So I've been using ARHD on my phone for some time now, but I have this issue happening with the latest version : after a reboot the phone would reset all sound settings to default (default ringtone/notification sound), so I'd have to set them again from the lists in settings. But after another reboot, the system would not find any ringtone/alarms/notification in the lists anymore (although they're on the SD card if I check with root explorer) and it's using a single default sound for everything.
I've checked the locations of the files : they're at sdcard/alarms (/notifications, /ringtones), but it seems the system can't see or find them.
And I tried wiping/reflashing the rom several times.
Also I'm using ROM Cleaner and supercharge scripts.
Any suggestions guys ?
R.azn said:
Hello everyone,
So I've been using ARHD on my phone for some time now, but I have this issue happening with the latest version : after a reboot the phone would reset all sound settings to default (default ringtone/notification sound), so I'd have to set them again from the lists in settings. But after another reboot, the system would not find any ringtone/alarms/notification in the lists anymore (although they're on the SD card if I check with root explorer) and it's using a single default sound for everything.
I've checked the locations of the files : they're at sdcard/alarms (/notifications, /ringtones), but it seems the system can't see or find them.
And I tried wiping/reflashing the rom several times.
Also I'm using ROM Cleaner and supercharge scripts.
Any suggestions guys ?
Click to expand...
Click to collapse
Mike once said that it wasn't just a ROM problem. The official HTC ICS 4.0.4 also has this problem and ARHD was directly based of it that so....
try fix promissions in recovery--->> tools
Hesam said:
try fix promissions in recovery--->> tools
Click to expand...
Click to collapse
This fixed the issue !
Thanks a lot ! Both of you
R.azn said:
This fixed the issue !
Thanks a lot ! Both of you
Click to expand...
Click to collapse
Just use thanks button
Follow Me On Instagram User : He_S_aM
I was about to post as I have the same issue. Fixing permissions in 4ext solved the problem. Its strange, ARHD 3.X and 4.X didn't have this problem. Perhaps Mike should have added this issue/solution to the FAQ at the start of the ARHD thread.
This is a persistent problem. I have to fix permissions in recovery everytime I reboot otherwise the media server doesn't find any audio files on the sdcard.
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?
You can use the original google dialer and contacts on Marshmallow.
Flash the attached zip and make the google dialer default in settings. That's all
Don't delelte the samsung dialer and contacts. You can hide them if you use nova launcher for example.
This is not my work, I downloaded the apks from apkmirror.
Did that manually myself and even pasted the frameworks from this thread http://forum.xda-developers.com/mot...p-google-dialer-2-32-google-contacts-t3263859 into my device.
Looking now how to enable heads-up for the dialer and why it FCs when clicking calls under settings in the call app
boilavera1980 said:
Did that manually myself and even pasted the frameworks from this thread http://forum.xda-developers.com/mot...p-google-dialer-2-32-google-contacts-t3263859 into my device.
Looking now how to enable heads-up for the dialer and why it FCs when clicking calls under settings in the call app
Click to expand...
Click to collapse
Hello, I tried this on my S6 Edge Plus running 6.0.1 but ended up in a boot loop on the boot animation.
Steps I followed were:
Copy the com.google.android.dialer.apk to /system/priv-app/Telephone/com.google.android.dialer.apk and chmod 644
Copy the com.google.android.contacts.apk to /system/priv-app/Contacts/com.google.android.contacts.apk and chmod 644
Copy the com.google.android.dialer.support.jar to /system/framework/com.google.android.dialer.support and chmod 644
Did I miss any particular step?
Thanks in advance.
rasheedshady said:
Hello, I tried this on my S6 Edge Plus running 6.0.1 but ended up in a boot loop on the boot animation.
Steps I followed were:
Copy the com.google.android.dialer.apk to /system/priv-app/Telephone/com.google.android.dialer.apk and chmod 644
Copy the com.google.android.contacts.apk to /system/priv-app/Contacts/com.google.android.contacts.apk and chmod 644
Copy the com.google.android.dialer.support.jar to /system/framework/com.google.android.dialer.support and chmod 644
Did I miss any particular step?
Thanks in advance.
Click to expand...
Click to collapse
Really? Thats interesting. I just downloaded the newest apk from apkmirror and pasted it into priv-app. Didn't even bother to change permissions and it worked. Try chmodding it to something like 744
boilavera1980 said:
Really? Thats interesting. I just downloaded the newest apk from apkmirror and pasted it into priv-app. Didn't even bother to change permissions and it worked. Try chmodding it to something like 744
Click to expand...
Click to collapse
Thanks for the quick reply.
I managed to get it working by flashing the Zip using TWRP.
I suppose the only difference is that it asked me to Wipe Cache after installing the zip, something that i didn't do while installing manually.
I could restore my /system partition and try again... but i guess the goal was to have the Google Dialer.. and that is what I have now
I'm getting similar results to what you got, no HUD and crash when accessing the Call Settings, any luck with any of those two?
EDIT: So I went through the log cat and found that when the user taps the Call Settings or the Emergency Call (on the lock screen) and intent is fired to launch the corresponding activity. For the call settings menu, the intent is android.telecom.action.SHOW_CALL_SETTINGS and there is no activity on the samsung version of android that listens to this intent so we get an FC.
I went through some of the source code and found that the activity for the call settings is named CallFeaturesSetting found in com.android.phone.
Looking at the manifest.xml of Google Dialer app, there is no such activity. This can only mean that a copy of com.android.phone.apk is expected to be present on the phone for the google dialer to run properly.
rasheedshady said:
Thanks for the quick reply.
I managed to get it working by flashing the Zip using TWRP.
I suppose the only difference is that it asked me to Wipe Cache after installing the zip, something that i didn't do while installing manually.
I could restore my /system partition and try again... but i guess the goal was to have the Google Dialer.. and that is what I have now
I'm getting similar results to what you got, no HUD and crash when accessing the Call Settings, any luck with any of those two?
EDIT: So I went through the log cat and found that when the user taps the Call Settings or the Emergency Call (on the lock screen) and intent is fired to launch the corresponding activity. For the call settings menu, the intent is android.telecom.action.SHOW_CALL_SETTINGS and there is no activity on the samsung version of android that listens to this intent so we get an FC.
I went through some of the source code and found that the activity for the call settings is named CallFeaturesSetting found in com.android.phone.
Looking at the manifest.xml of Google Dialer app, there is no such activity. This can only mean that a copy of com.android.phone.apk is expected to be present on the phone for the google dialer to run properly.
Click to expand...
Click to collapse
Yeah i have no idea why the Callnotification banner doesnt work. Framework didn't help too. There seems to be something missing. There is a mod for Sony devices where excactly this works but for LP. Maybe there are some hints there.
Edit:
Yeah copying the framework should work indeed if i look at the other mods but maybe something that samsung modified permits it from doing so. The changed many things, maybe this is the issue.
boilavera1980 said:
Yeah i have no idea why the Callnotification banner doesnt work. Framework didn't help too. There seems to be something missing. There is a mod for Sony devices where excactly this works but for LP. Maybe there are some hints there.
Edit:
Yeah copying the framework should work indeed if i look at the other mods but maybe something that samsung modified permits it from doing so. The changed many things, maybe this is the issue.
Click to expand...
Click to collapse
So this marks the end of my trying to fix this issue.
I managed to get the Call Settings But broke everything else
com.android.phone is not a standalone package, it comes in the TeleServices.apk file in /system/priv-app
As I suspected, the samsung version lacks the activities that the Google Dialer looks for.
I extracted the TeleServices.apk from a nexus 6p image and compared the two. Again as expected the google version has the required activity.
Another thing to note is that the Samsung Version is 13.2MB while the Google Version is just 3.2MB
Since they can't both be active on the device, replacing the samsung version by the google version fixes the call settings issue. But the phone doesn't register on the network.
in theory once can compile an app from AOSP with a different signature to allow the call settings to handle the activity required by the call settings app, or simply launch the settings activity of the default samsung dialer.
Any way.. just an update.
Can anyone post a screen shot of this dailer please?
rogerandgina said:
Can anyone post a screen shot of this dailer please?
Click to expand...
Click to collapse
http://images.lmgtfy.com/?q=google+stock+dialer+marshmallow
boilavera1980 said:
http://images.lmgtfy.com/?q=google+stock+dialer+marshmallow
Click to expand...
Click to collapse
No need to be a smart ass about it.
rogerandgina said:
No need to be a smart ass about it.
Click to expand...
Click to collapse
Sorry but that was funny.
Sent from my SM-G928F using XDA-Developers mobile app
soundstorm27 said:
You can use the original google dialer and contacts on Marshmallow.
Flash the attached zip and make the google dialer default in settings. That's all
Don't delelte the samsung dialer and contacts. You can hide them if you use nova launcher for example.
This is not my work, I downloaded the apks from apkmirror.
Click to expand...
Click to collapse
Any google sms.zip??