Related
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])
I will release my changes to the franco.kernel in this thread before franco includes them in his kernel for the upcoming releases. So this is a "pre-release" thread for franco.kernel, for the changes I'm making.
v2 (included in [16 SEP] franco.Kernel)
- Speakerphone echo fixed. Works with normal calls, not with Skype (or other voip apps probably). Skype still works like before, echo with speakerphone mode.
The fix can be disabled with
Code:
echo 0 > /sys/module/snd_soc_msm7kv2/parameters/speakerphone_echo_fix
You can post in this thread how it works. It always uses speaker_mono_tx instead of speaker dual mic broadside dev.
- Removed some logging from msm7x30.c (left there by Huawei. They must have a logging fetish or something )
mod_v1 (Included in [11 SEP] franco.Kernel)
- "Use phone's mic with headset"-feature is now user configurable.
By default uses phone's mic with headset/headphones/line-out. So if you want that, no configuration is needed.
To use headset's mic create a file called "10headsetswitch" in "/system/etc/init.d/" and paste the following to it:
"echo 0 > /sys/module/snd_soc_msm7kv2/parameters/headset_mic_switch"
Future plans
- Fix speakerphone echo in Skype. Investigate the volume problems (max. volume is too high, etc..).
Flashing instructions
- Boot to recovery
- install from zip
- choose francokernel_X_ksatta_vX.zip.
Notes for devs
The latest franco.kernel has logcat disabled by default, to enable it put this in .config:
Code:
CONFIG_ANDROID_LOGGER=y
To enable kernel debug messages (can be seen with dmesg):
Code:
git checkout 0c1adc36ed u8800-kernel/kernel/printk.c
NOTE: disable logging again before releasing anything, probably slows down the phone quite a bit when logging is on.
Credits
ksatta - use phone's mic with headset
stockwell - user config for headset mic setting
franciscofranco - the franco.kernel
Thanks
wmi543
genokolar
And everyone else if I forgot to mention someone.
Files
franco.kernel-sep11+ksatta_v2.zip - Zip file to flash phone.
franco.kernel-sep11+ksatta_v2-src.zip - V2 source for devs. msm7x30.c file is from u8800-kernel/sound/soc/msm. Also includes compiling instructions.
To make it set to using the phone mic at boot, save the following script into /system/etc/init.d/. Call it whatever you like just with a two digit number at the start (ie. 10headsetswitch)
Code:
echo 0 > /sys/module/snd_soc_msm7kv2/parameters/headset_mic_switch
As mentioned this is already configurable in Miui using x5 settings so you don't need to worry about making the script yourself but the voice quality might not be very good (will be fixed for the next version) unless you use the kernel attached from ksatta.
Please could explain how to install this kernel? Because I read the file that you have attache and in the end I finish like in the begginign without knowing how to do it.
Is only need to do by the recovery with the zip file ans what about the secund zip file the smaller one?
Sorry but Ian sure that I am not the only o w that is asking this.
Sent from my u8800 using XDA App
vlc_marcos said:
Please could explain how to install this kernel? Because I read the file that you have attache and in the end I finish like in the begginign without knowing how to do it.
Is only need to do by the recovery with the zip file ans what about the secund zip file the smaller one?
Sorry but Ian sure that I am not the only o w that is asking this.
Sent from my u8800 using XDA App
Click to expand...
Click to collapse
Yeah I was a bit unclear, sorry. To flash boot to recovery, install from zip and choose my zip.
edit: Updated first post, flashing instructions
ksatta said:
Yeah I was a bit unclear, sorry. To flash boot to recovery, install from zip and choose my zip.
Click to expand...
Click to collapse
Ok thanks. And for what is the small zip file?
So I will use in this last miui without any problems correct.
Will I get battery problems?
Sent from my u8800 using XDA App
vlc_marcos said:
Ok thanks. And for what is the small zip file?
So I will use in this last miui without any problems correct.
Will I get battery problems?
Sent from my u8800 using XDA App
Click to expand...
Click to collapse
Sigh man, I'm growing tired of your questions everywhere in every thread you can find. This is just my kernel compiled with a different file to make this "Use phone's mic with headset"-feature is now user configurable." avaliable.
No it won't take coffees for you, no it won't explode your device, no it won't turn it into an airplane and fly in circles above your head, and no it won't make you rich beyond imagining.
Sorry for the smallish OT ksatta, it ****s me reading stupid questions everywhere.
Very nice job like I told you before
franciscofranco said:
Sigh man, I'm growing tired of your questions everywhere in every thread you can find. This is just my kernel compiled with a different file to make this "Use phone's mic with headset"-feature is now user configurable." avaliable.
No it won't take coffees for you, no it won't explode your device, no it won't turn it into an airplane and fly in circles above your head, and no it won't make you rich beyond imagining.
Sorry for the smallish OT ksatta, it ****s me reading stupid questions everywhere.
Very nice job like I told you before
Click to expand...
Click to collapse
First of all Ian not from your family so stupidity is not in my genes. Secund if you are tired go to sleep.
I didn't ask to you, so you don't need to react like this. Don't be a small kid.
When I don't know I ask.
So Franco don't give me your ****y opinions when I don't ask for then.
Thanks
Sent from my u8800 using XDA App
franciscofranco said:
No it won't take coffees for you, no it won't explode your device, no it won't turn it into an airplane and fly in circles above your head, and no it won't make you rich beyond imagining.
Click to expand...
Click to collapse
I think it's a fair question, I was wondering why my phone wasn't making me coffee
vlc_marcos said:
Ok thanks. And for what is the small zip file?
So I will use in this last miui without any problems correct.
Will I get battery problems?
Click to expand...
Click to collapse
You can already do this in Miui, have been able to for a while. Flashing this version should make the voice quality better though.
Yeah, like franco said, the v1 is just user-configurability for the headset mic thing.
For anyone else wondering, I will report any changes I make in the first post. So the zips here won't have any other changes compared to franco.kernel, except the ones I report in the first post.
vlc_marcos said:
Ok thanks. And for what is the small zip file?
Click to expand...
Click to collapse
I updated the first post to be less confusing. the smaller file is only the source file, only needed by devs.
franciscofranco said:
Sigh man, I'm growing tired of your questions everywhere in every thread you can find. This is just my kernel compiled with a different file to make this "Use phone's mic with headset"-feature is now user configurable." avaliable.
No it won't take coffees for you, no it won't explode your device, no it won't turn it into an airplane and fly in circles above your head, and no it won't make you rich beyond imagining.
Sorry for the smallish OT ksatta, it ****s me reading stupid questions everywhere.
Very nice job like I told you before
Click to expand...
Click to collapse
Mate, you seriously need to get a grip and settle down. Maybe lay off the espresso a bit. I know you are doing good things with your kernel and everyone appreciates that and is grateful. However, almost every post you make is aggressive and condescending. Ok so you have it all figured out, that's great. But the majority of us are just struggling and muddling along enjoying Android and trying to learn and contribute as we go. When you attack and belittle most posters it just make you look like a wanker.
May I suggest: if you don't wish to assist then simply don't respond. Someone else will or maybe no one will in which case the post will recede into the past and the poster will look elsewhere.
Maybe you, or anybody here can write me pm with very short info how to compile kernel [what parrameters should pass to it] and make zip package to be installable to phone? Once i tried to compile but image was 2x times bigger than original realese so i was afraid to test it
GolfCranK said:
Mate, you seriously need to get a grip and settle down. Maybe lay off the espresso a bit....
Click to expand...
Click to collapse
it's PASSION man! Who wants to read nice post i want to read **** words man!
Tommixoft said:
Maybe you, or anybody here can write me pm with very short info how to compile kernel [what parrameters should pass to it] and make zip package to be installable to phone? Once i tried to compile but image was 2x times bigger than original realese so i was afraid to test it
Click to expand...
Click to collapse
Maybe you were looking at the uncompressed Image file? zImage is the correct file. But anyway the -src.zip contains compiling instructions, I created them today with a fresh install of Ubuntu 11.04. If you test my instructions and have any problems, inform me and I'll update the instructions.
Before you edited you asked about what v1 does, there's a whole lot of text in the first post, but yes, it only makes the headset mic switch user-configurable Future releases might have more changes
Actually my version uses phone's mic by default. I made it default because franco.kernel has been using phone's mic by default. So, to avoid confusion:
If you want to use headset's mic use "echo 0 > /sys/module/snd_soc_msm7kv2/parameters/headset_mic_switch" in the script.
If you want to use phone's mic, don't do anything
edit: This applies to the v1 kernel in this thread, miui uses headset's mic by default. Reason above.
Man, this kernel fixed the only issue I had with Oxygen, and call quality is even great! Now I won't change ROMS ever in the next months (unless Huawei releases official Gingerbread). I'm not gay but this is true, I LOVE YOU!!!!
ksatta said:
Maybe you were looking at the uncompressed Image file? zImage is the correct file. But anyway the -src.zip contains compiling instructions, I created them today with a fresh install of Ubuntu 11.04. If you test my instructions and have any problems, inform me and I'll update the instructions.
Before you edited you asked about what v1 does, there's a whole lot of text in the first post, but yes, it only makes the headset mic switch user-configurable Future releases might have more changes
Click to expand...
Click to collapse
MAN! Thanks! finally someone wrote how to properly compile. THANKS!! You're awesome
ksatta said:
Actually my version uses phone's mic by default. I made it default because franco.kernel has been using phone's mic by default. So, to avoid confusion:
If you want to use headset's mic use "echo 0 > /sys/module/snd_soc_msm7kv2/parameters/headset_mic_switch" in the script.
If you want to use phone's mic, don't do anything
edit: This applies to the v1 kernel in this thread, miui uses headset's mic by default. Reason above.
Click to expand...
Click to collapse
lol sorry I edited it now.
My theory about the speakerphone echo is that the audiolibs in 2.3 roms use the wrong routing. They're probably now using the same microphone dev. id. as normal mode, when they should be using the "speakerphone mic" dev.id.
I wasn't able to confirm this yet, didn't get my debug messages out of the kernel yet Normal logcat works, but the kernel debug messages don't show up in it. Also I couldn't find a syslog file.
But I'll continue another day.
Ksatta i see you good with freaking linux stuff and sound So can you make that recording audio and video - audio quality to be good not some arm ****?
I found that codec is here arch/arm/mach-msm/qdsp5v2/audio_amrnb.c How to make that system uses different codec or this but with better sample rate ant bit rate, i can change this in file but i can't find the specification of this codec so maybe it's not supporting 44.1Khz sample rate or even 16Khz.
Thanks ksatta for this ! Was exactly what needed. Btw instead of setting that init script couldn't just change the value from 1 to 0 or it is restored after every reboot?
Well guys we have a pretty good chance to include everything (...what is possible) we ever wanted on our Atrix...
in an other thread th3bill (the dev. behind AOKP milestone 6 port) opened there were alot of request for features on the next builds, th3bill offered to open a discusion which include all requests in one place.
** Th3bill, we love your work and your willing to do for others. your private time "wasted" on porting and developing is not ovious and we do appriciate it. keep on the excellent work and again a major thank, us - the users.
since nobody did it so far i'll start:
i whould like the next build to include:
1. call recording option.
2. video call option.
3. webtop interface?
4. google music.
5. led color control in order to customize notifications.
6. o.c kernel.
7. some other cpu governors.
8. google's android jellybean featuers? espacially build-in voice recognition.
things to fix (what i've noticed):
1. video cam - known problem.
2. browser issus (fc when changing ls and portrait).
3. edit custom brightness levels (fc).
4. can't change signal and wifi colors.
5. also battery bar won't show up.
6. wifi direct won't work.
7. wifi hot spot works and immidiatly stops(maybe it's just my device).
-By now your port is the best rom my atrix had so...big thanks !!!
-I know you working too hard already (DON'T FORGET TO HAVE FUN !!, i wrote all of the things i think can be added. with or without them it is still almost perfect.
guys it is your turn now...make some suggestions for improvement:
Hey Everyone!
I'm sure most of you know me by now. Those of you who do not, I am NOT the type of rom porter who gets upset by questions/requests/PMs. Just understand that I build 3 builds of MIUI (Photon, Atrix, Infuse), 2 builds of AOKP (Photon, Atrix), 2 builds of Paranoid Android (Photon, Atrix), as well as help Jokersax11 with various projects, including our Kitchen Sink. That being said, it might take me a little bit to respond...but I will.
---------- Post added at 10:02 PM ---------- Previous post was at 09:53 PM ----------
toomaiv said:
Well guys we have a pretty good chance to include everything (...what is possible) we ever wanted on our Atrix...
in an other thread th3bill (the dev. behind AOKP milestone 6 port) opened there were alot of request for features on the next builds, th3bill offered to open a discusion which include all requests in one place.
** Th3bill, we love your work and your willing to do for others. your private time "wasted" on porting and developing is not ovious and we do appriciate it. keep on the excellent work and again a major thank, us - the users.
since nobody did it so far i'll start:
i whould like the next build to include:
1. call recording option.
2. video call option.
3. webtop interface?
4. google music.
5. led color control in order to customize notifications.
6. o.c kernel.
7. some other cpu governors.
8. google's android jellybean featuers? espacially build-in voice recognition.
things to fix (what i've noticed):
1. video cam - known problem.
2. browser issus (fc when changing ls and portrait).
3. edit custom brightness levels (fc).
4. can't change signal and wifi colors.
5. also battery bar won't show up.
6. wifi direct won't work.
7. wifi hot spot works and immidiatly stops(maybe it's just my device).
-By now your port is the best rom my atrix had so...big thanks !!!
-I know you working too hard already (DON'T FORGET TO HAVE FUN !!, i wrote all of the things i think can be added. with or without them it is still almost perfect.
guys it is your turn now...make some suggestions for improvement:
Click to expand...
Click to collapse
Enhancements:
1) Call recording, I need to play around with this rom some more...see if it has the capability...maybe I can pull from MIUI...can't guarantee, though
2) That will be tough until Moto gives libs
3) Loki and I have talked at length about this...we're trying to figure out a way to do it, but it will take a hybrid kernel and a lot of work. Not that we won't TRY...
4) This will be in the next release
5) Have an app in mind that I can include? Beauty Aroma is that I can include almost anything
6) I am working with Jokersax11 on making some that are compatible with our base. I know that some are kinda compatible, but not all....
7) By governors, I am assuming you're talking about some form of setcpu?
8) I have the apps on my PC...well some of them.
With respect to fixes, 1 and 2...those won't be till Moto plays nice with me and gives me drivers for ICS.
3) I need a logcat on this one please
4 and 5) Not too sure about these ones. I'll try them with my phone if I get a chance. If you can logcat, that'd be great
6) I think this is an ICS thing. Don't know that any of them do Ad-hoc at the moment
7) You need to forget whatever network you are near if you're connected...and make sure that wifi is ON before beginning tether
Sorry if I am a downer on some of it, but I would rather be honest with everything I tell you all. I have much love for the Android Community
I know of you and your builds well Th3Bill, unfortunately I'm just now working on my 10 posts, I have flashed everything for Atrix and Photon.
Much thanks
My Phone
log file
3) I need a logcat on this one please
4 and 5) Not too sure about these ones. I'll try them with my phone if I get a chance. If you can logcat, that'd be great
7) You need to forget whatever network you are near if you're connected...and make sure that wifi is ON before beginning tether
Sorry if I am a downer on some of it, but I would rather be honest with everything I tell you all. I have much love for the Android Community [/QUOTE]
Hi,
3+4+5) attached .txt file. (tried to make it shorter as possible.cleared log then did 3 then 4 then 5 and saved it)
7) you are right - worked.
tomer
really???
hey guys / girls,
there is not a single thing you would like to see on the next builds??
***DOESN'T MAKE ANY SENSE***
SO COME ON AND MAKE A WISH!!!
p.s
i defenetly would like a mod (or better - a buildin solution) that will trick the google play to show me all apps. (not the ones comptible with my specific device/settings).
tomer
toomaiv said:
hey guys / girls,
there is not a single thing you would like to see on the next builds??
***DOESN'T MAKE ANY SENSE***
SO COME ON AND MAKE A WISH!!!
p.s
i defenetly would like a mod (or better - a buildin solution) that will trick the google play to show me all apps. (not the ones comptible with my specific device/settings).
tomer
Click to expand...
Click to collapse
You can try changing the build I'd in the build.prop...but I'm not sure if that would work even...
Sent from my MB855 using xda premium
Just installed latest build an wanted to say thanks for bill's an jokers hard work..
I personally use the car dock alot an the transitions between audio playing and incoming call tends to be troublesome. When calls answered the phone doesn't port it over the USB. Usually speaker/headset and have to redock in call for it to work... also DSP manager doesn't have effect over the USB audio out. Only reason I revert to original moto rom.
That aside best cm9 based rom yet.
Sent from my MB860 using xda app-developers app
Also AOKP states it now supports adhoc.... tried on 2 different setups and no joy...
This is wifi direct I gather..
LS support also varies through various android tasks.
Sent from my MB860 using xda app-developers app
On paranoid android for the atrix when in tablet mode it won't allow me to make the recent apps the Sense htc style one, is there a fix for this?
Question/Report
Not sure if this is the right place to report issues. My luck, probably not. Here it goes..
I had your build 40. worked great!
updated to milestone 6 7b. worked better (yaay)
tried to update to milestone 6 revision. No wipe, same as previous, sent atrix into bootloop. tried few more times, same thing.
tried again with full wipe. Bootloop. tried again. bootloop. flashed 7b full wipe, works great again (yaay).
Just curious if you have any idea why my phone doesn't like the new one. saw in the rom thread a few others had same issue or similar, no answers there as of yet. i'm hesitant it try again unless you can think of something i could possibly be doing wrong somehow. Anything i can send or tell you that could help, let me know. Thanks
As for requests, i prefer Apex launcher over Nova. Maybe include it? it would be nice if i could uninstall Nova also
You Rock!
*So i tried installing again and it works now. not sure what the problem was*
Closer
hi,
not really worked...users didn't cooporate and besides cm 10 (JB) is already here and not bad, so this is closed!!
i wanna thank Th3Bill for his effort and wish you will continue develop for us.
tomer
CAN CLOSE THREAD
Hello
Hello One asks what is the kernel that I have to install
Call Recording and if possible hardware acceleration
paarkhi said:
Call Recording and if possible hardware acceleration
Click to expand...
Click to collapse
Hwa is in the ROM under advanced.
Call recording isn't yet supported by kernel. Funny you posted this as joker and I are discussing how to fix now
Sent from my MB855 using xda premium
Problems
I'm not sure if this is the right place to ask this. If not, i apologize.
I flashed your AOKP build 3 on my international atrix. The ROM doesn't recognize internal and external storage for me. When my phone boots it says that is safe to remove sd card. I used the two options EMMC and SD with or without build.prop tweaks. Also i flash this with FULL wipe (system, etc) The other thing that i cannot find are GApps. Can I use CM10 GApps for this rom ?
Thanks in advance.
So, are there options for an OCed kernel yet?
* Moved to development thread. *
I would really love to see an option to "Show only contacts with phone numbers" on Contact list settings...MIUI has this option and this is super usefull for me
MIUI SMS app is great too, but it doesn´t show smileys
Thanks
I have a good one! WebOS and Sense style multitasking (with long press home).
Sent from my MB860 using xda app-developers app
Facebook Sync
If this has been answered then i missed it and i searched first .
Is there a fix for the facebook sync
__________________________________________________________
MB860 running 4.1.2
Hi
[EDIT] my phone = I9300, OmniRom = latest (with a maximum of google apps disabled/alternatives preferred)
I can't quite figure that one out:
On every single system update, I lose my settings in terms of my custom ringtones, alarms...
I tried 3 different ways:
- I copied them into System/media/audio/ringtones & alarms --> after every update, my custom sound files cannot be found anymore and are therefore not available to select from Settings > Sound > Phone ringtone & Default alarm sound
- so then I copied them into sdcard/media/audio/ringtones & alarms --> althought they remain there after every update, they are not available from Settings > Sound > Phone ringtone & Default alarm sound
- so finally I copied them into extSdCard/media/audio/ringtones & alarms with the same effect: althought they are still there after every update, they are not available from Settings > Sound > Phone ringtone & Default alarm sound
Somehow this looks like a bug to me...
Can someone please explain how I can preserve my custom ringtones after system updates?
Thank you VERY much
beng
How did you copy them? It might be a selinux/permissions problem.
For reference, I haven't had any problem on my Nexus 5 (all internal ext4 with emulated sdcard) with
Code:
[email protected]:/ # ls -lZ /sdcard/Alarms/
-rw-rw---- root sdcard_r u:object_r:sdcard_internal:s0 Luminescence.ogg
Code:
/sdcard/Alarms, /sdcard/Ringtones, /sdcard/Notifications
Those are directories especially for custom sounds, which of course will survive ROM updates. Why don't you put them there?
klenamenis said:
Code:
/sdcard/Alarms, /sdcard/Ringtones, /sdcard/Notifications
Those are directories especially for custom sounds, which of course will survive ROM updates. Why don't you put them there?
Click to expand...
Click to collapse
done just that: my custom sounds don't even show up (Settings > Sound > Phone ringtone & Default alarm sound), nor after a reboot!
honestly this is a major bug as far as I am concerned - I keep missing my phone calls as the ringtone will default to none, makes the whole point about having a mobile pointless!!!
Until you can give steps to repeat, that someone else can repeat, it appears to be a problem that is specific to your phone and configuration. If it were a significant bug, you wouldn't be the only one claiming it was impacting them.
Nothing personal, but unless you can replicate this on a fresh install, without additional software, and document how to repeat it, it likely will never be considered an OmniROM bug. One you can do that, a JIRA is perhaps the right way to raise attention on the issue.
As a note, opening additional threads will more likely get you labeled as whiner than get faster resolution. One is plenty.
---
Posted from whatever phone booted today
jeffsf said:
Until you can give steps to repeat, that someone else can repeat, it appears to be a problem that is specific to your phone and configuration. If it were a significant bug, you wouldn't be the only one claiming it was impacting them.
Nothing personal, but unless you can replicate this on a fresh install, without additional software, and document how to repeat it, it likely will never be considered an OmniROM bug. One you can do that, a JIRA is perhaps the right way to raise attention on the issue.
Click to expand...
Click to collapse
Hi jeffsf
well I thought the steps were clearly detailed in my initial post?
The custom sounds I would like to set up as custom ringtones / alarms are snippets edited out of full mp3 songs (generally a loop edited out of the intro); If i use the default (boring) sounds provided, I keep my settings.
I first copied my custom snippets into System/media/audio/ringtones & alarms ; this works until I reboot following a new nightly update, my settings are lost; the ringtone is back either to the default one or to none (worse option as I miss my phone calls - I cannot work out a rule as to the default ringtone/none reset, sorry!); my custom sound files cannot be found anymore in the ringtones folder and are therefore not available to select from Settings > Sound > Phone ringtone & Default alarm sound
My second attempt was then to copy them into sdcard/media/audio/ringtones & alarms ; although they remain there after the reboot following any new nightly update, the settings are lost from Settings > Sound > Phone ringtone & Default alarm sound.
So my third attempt was to copy the snippets into extSdCard/media/audio/ringtones & alarms but it had the same result: although they are still there after every update, my previous settings are lost and the snippets cannot be selected from Settings > Sound > Phone ringtone & Default alarm sound ...
After all these tests, I am even more confused; I do not know/understand for sure what folders Android uses primarily / secondarily for ringtones / alarms...
jeffsf said:
As a note, opening additional threads will more likely get you labeled as whiner than get faster resolution. One is plenty.
Click to expand...
Click to collapse
I do get the point! Not my intention to whinge but as explained, there is not much point in having a silent phone!
First I asked a question (support); clearly no working solution can be provided
so I take it to the next level: software correction requirement (indeed JIRA can be the software to use for this - this is actually what I am using at work!)
Or the solution is to choose another rom, shame really...
BenG7 said:
Hi jeffsf
well I thought the steps were clearly detailed in my initial post?
Click to expand...
Click to collapse
Your observed behavior is clear in your first post, so there is no reason to repeat it. It adds no information by doing so.
The custom sounds I would like to set up as custom ringtones / alarms are snippets edited out of full mp3 songs
Click to expand...
Click to collapse
A tiny snippet of new information. But still, you haven't identified what format you are using on the device or how you are copying the files into the directories you are using, only on your source.
clearly no working solution can be provided [...] Or the solution is to choose another rom, shame really...
Click to expand...
Click to collapse
Or clearly it isn't a problem with the ROM. If it were a general problem with the ability to set and retain ring tones, there would most likely have been at least one other person who reported similar problems as you.
Unless you can replicate this (a) from a clean install, (b) without other software installed, (c) using a directory intended for the function, (d) clearly identifying how and where you have set the ring tone, and (e) how you updated, it most likely isn't a ROM bug.
GIven that this isn't impacting anyone but you from what I can tell, I would look at your own software, configuration, or use as the most likely cause.
Note also that two people in this thread have already clearly identified directories for these files that do not have the issues you mention.
unsupported audio format?
Hello,
I built omnirom from last sources and I I was in the same situation. My mp3 wasn't recognized anymore (regression? developper choix? I don't know)
Workaround: I converted them into ogg format, and it works like a charm (on my HTC Explorer).
Hi
Hey, for the first time I realise yesterdays nightly (20141030) solved this ongoing issue I had given up on:
it preserved my custom ringtone and alarm and I did not need to reset my ringtone & alarm after the update as I do after EVERY SINGLE update - a pain really!
Please keep it as such - thanks A LOT
cheers
beng
BenG7 said:
Hi
Hey, for the first time I realise yesterdays nightly (20141030) solved this ongoing issue I had given up on:
it preserved my custom ringtone and alarm and I did not need to reset my ringtone & alarm after the update as I do after EVERY SINGLE update - a pain really!
Please keep it as such - thanks A LOT
cheers
beng
Click to expand...
Click to collapse
Nothing has been changed that would affect this.
Also, you probably stopped getting responses because your responses were inconsistent. Post 3 provided the standard location where these files should be placed.
In post 4 you claimed exactly that, EXCEPT that in Post 6, none of the directories in post 2 were in your list of things you tried...
In the end it really doesn't matter. Your device is getting dropped with L as it hasn't had a maintainer in months and there is no one to fix I9300 issues.
Entropy512 said:
Nothing has been changed that would affect this.
Also, you probably stopped getting responses because your responses were inconsistent. Post 3 provided the standard location where these files should be placed.
In post 4 you claimed exactly that, EXCEPT that in Post 6, none of the directories in post 2 were in your list of things you tried...
In the end it really doesn't matter. Your device is getting dropped with L as it hasn't had a maintainer in months and there is no one to fix I9300 issues.
Click to expand...
Click to collapse
I can only report it works now.
Post 1 were the initial steps I took
I did as advised in post 3 ; this was post 4
Post 6 was only a repeat of post 1, not including steps from post 4, but these were carried out too, to no avail too.
Just forget it now.
Thanks
Hey,
I didnt know where i should Post my Bug Report so if its the wrong section dont hold back to tell me.
I'm currently using my Galaxy S2 for daily use and after flashing some Kitkat Roms Omni is in my opinion the most stable rom and with Nova + ART a damn fast Rom, so thank you very much for supporting my Device.
I dont know whats happening the last weeks but it all began with an Opendelta Issue, i wiped all Data / Factory Reset via TWRP and flashed the Rom completely new and OpenDelta still didnt work, it just said every day its all up2date. Now after a couple of days it is working again, dont know if it was a Server Issue or something else - at the official Omni Page no one post News so i have always to guess whats happening
Currently i found 2 Bugs, if you want to call someone you open up the Dialer and then the Button for the Numbers but after clicking it, theres nothing(Screenshot is attached). You have to go back and try it again then the Numbers are there. The second Problem is that there is no Zoom in the AOSP Camera App if you record a Video. My currently workaround is the Google Camera App, there all is working fine. Also there are some Issues with Apollo , freezing , doesnt update the Song DB etc. , dont know why its so popular - its horrible. Replaced it also with a 3rd party App - Omich/Rocket Player.
The last Problem is that not everywhere in the Settings the correct language is used, if you need some translation help im sure many users would like to help(including me) but that is in my opinion nothing critical .
...and sorry if my Text was hard to read, its not my native language but im working on it :silly:
Regards
Per the FAQ, this is not the place to put bug reports.
However, I9100 hasn't been maintained in a long time, so filing a bug report will be a waste of time. Support for this device is currently going to be dropped with Android 5.0, and if it receives 4.4 bugfixes, that'll have to come from a new maintainer as none of the former maintainers have time/motivation for the Exynos 4210 devices these days.
Some of the issues you describe with Apollo aren't Apollo issues, but the result of a very deep-down core bug that has a side effect of screwing up storage access. This bug has been known for nearly a year (there's a big thread disucssing it somewhere around here...) and still no one has found a fix for the root cause. In fact, it's one of the #1 reasons the device is getting dropped for L. (It will absolutely not receive nightlies unless someone finds and corrects the root cause.)
Hey,
Thank you for your response. :good:
I reported the Bug on jira and there is a workaround for the Dialer Bug: Setting The Animator Scale higher than 0.
The Drivers are the problem right?
pfxandroid said:
Hey,
Thank you for your response. :good:
I reported the Bug on jira and there is a workaround for the Dialer Bug: Setting The Animator Scale higher than 0.
The Drivers are the problem right?
Click to expand...
Click to collapse
Well, there are three things you listed:
1) Dialer stuff - probably some sort of odd HDPI issue and/or graphics subsystem stuff. The Exynos4 graphics subsystem is why many developers don't want to ever touch the platform again.
2) Zoom in video - What resolution was Google Camera? Zoom has NEVER been available for 1080p resolutions on the Exynos 4210 family, not even stock firmware will zoom in 1080p
3) The storage issues are a symptom of a deep-down kernel bug that no one has found the root cause of. This is the #1 reason the device is getting dropped for 5.0 - there is no chance even if a new maintainer steps up that nightlies will resume until someone tracks down the root cause of this one. http://forum.xda-developers.com/showthread.php?t=2612329 has more discussion (warning: It's long...)