Try turning your volume all the way down to mute and then back up again, during the call. It was reported as a known issue with (if I read properly) all phones and this version of CM7. That being said, I haven't experienced this yet, but multiple people reported that fixing their sound issues.
[ROM][MTD]CyanogenMod 7.2.0 UNOFFICIAL by TeamAcid[R13][Mar-22-2013]
- Thread starter m4xm4n
- Start date
about the solutions that i have,
camera initialization fix *first boot after install switch front to rear. then there is no longer a problem, even after reboots(for me at least)
sound *first time install (R1) I had to toggle the full volume up and down, then no problem since. Also had a bug on r7, calling someone, no one could hear, bug not present in r6 or r8+.
vibration *had a toggle in r6, idk why max removed it
rotation screen driver black out... no fix for me yet, but the capacitive display seems to function fine.(if you know what you are supposed to touch eg, back in the day when you used a samsung rom or from another phone, just touch it there, and it functions fine. A great example is papi jump.as the game ends, you get a black screen with buttons disregard and restart, submit score, and more great games.(something like that), you will get a screen that is black. You can touch the left side just above halfway of your screen, the game will restart fine. Also, if you hit the back button, you see a blue strip at the top and bottom, but everything in between is screwed.(a big black screen). I don't think it is rendering .9 patches properly in the screen.
camera initialization fix *first boot after install switch front to rear. then there is no longer a problem, even after reboots(for me at least)
sound *first time install (R1) I had to toggle the full volume up and down, then no problem since. Also had a bug on r7, calling someone, no one could hear, bug not present in r6 or r8+.
vibration *had a toggle in r6, idk why max removed it
rotation screen driver black out... no fix for me yet, but the capacitive display seems to function fine.(if you know what you are supposed to touch eg, back in the day when you used a samsung rom or from another phone, just touch it there, and it functions fine. A great example is papi jump.as the game ends, you get a black screen with buttons disregard and restart, submit score, and more great games.(something like that), you will get a screen that is black. You can touch the left side just above halfway of your screen, the game will restart fine. Also, if you hit the back button, you see a blue strip at the top and bottom, but everything in between is screwed.(a big black screen). I don't think it is rendering .9 patches properly in the screen.
Would it be OK to flash a different modem using Odin? I'm having really bad signal issues now with the included modem
I believe they have to be padded to be exactly the same size as the official modem. FBis251 gave us two back in the other CM7 thread. The KD1 was worse for me, but KG4 worked fine.
actually, Bhundven padded them to the size that CM7's rild was looking for, so if you put the original kj6 modem back in, you rild (radio/modem) won't work.
We're using the proprietary rild. The padding is required by the proprietary Samsung RIL because it's used to reading the modem from a raw partition of a fixed size.
So basically, since the modern in BMP I'd it's own fixed partition, versus it being expandable in aosp.
Sent from my SGH-T959V using xda premium
Sent from my SGH-T959V using xda premium
bhundven
Inactive Recognized Developer
Start reading at this thread until I say modem works:
http://xdaforums.com/showthread.php?p=24500115#post24500115
Essentially: on a bml rom, the modem is written to a raw partition just like the kernel. On mtd, I followed how the other mtd devices format the radio partition with yaffs2 and symlink modem.bin to /dev/block/bml12 (as /dev/block/bml12 is what the rild is trying to read).
The modem is smaller then the size that rild is trying to read, because it was previously reading the raw /dev/block/bml12. So it worked then. After switching to just the modem.bin symlinked to /dev/block/bml12, the read fails because it's expecting to read in more then it did.
By padding the modem, it makes the read successful, and makes rild work.
i cant seem to download anything from the web from the XDA app. when i click on the link from XDA app, it just goes to a complete white screen.
NOTE: sorry if im posting in the wrong section, just need a little help. thanks and very much appreciate!
NOTE: sorry if im posting in the wrong section, just need a little help. thanks and very much appreciate!
bhundven
Inactive Recognized Developer
We could remove /radio and bml_over_mtd write the modem.bin to its partition, like the boot.img.
Sent from my HTC One X using xda premium
have any of you notice excessive battery drain and extreme phone heat when in a low service area.
At my school, there are many places that have no service and my phone starts heating up my leg.
also, normal use in a service region may drain 2 percent per hour, no service brings me down to maybe 5-6 percent per hour.
Today i didn't even look at my phone and in 7 hours, I was down from 100 to 66 percent battery.
At my school, there are many places that have no service and my phone starts heating up my leg.
also, normal use in a service region may drain 2 percent per hour, no service brings me down to maybe 5-6 percent per hour.
Today i didn't even look at my phone and in 7 hours, I was down from 100 to 66 percent battery.
Most of the building where I work has no service. Needless to say the battery always drains more than usual in there with whatever rom I am using or phone for that matter. The constant searching for signal does really does suck down the battery. As far as heating up, I am on third shift dripping sweat at work , if the phone heated up I wouldn't notice lol.
What does seem to drain the battery is video. I use MX Player and videos I play switch to S/W decoding instead of Hardware. I think this is a rom issue. I believe MX Player would play almost anything using Hardware before. Anyway 15 minutes of video drains my battery like 10 percent.
i guess that is just because of extreme video driver usage causing rotation/black out issues as well.
I got my new device today!
Many, many, many thanks to droidmyst, Keith H., and stephen_w for making it possible! It would not have been possible/taken infinitely longer to get a new device without them!
Lots of stuff to come soon, probably.
Many, many, many thanks to droidmyst, Keith H., and stephen_w for making it possible! It would not have been possible/taken infinitely longer to get a new device without them!
Lots of stuff to come soon, probably.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
105Code:
#include <std_disclaimer.h> /* * Your warranty is now void. * * I am not responsible for bricked devices, broken hearts, * thermonuclear war, you getting fired because the alarm app failed, or * unfulfilled sexual partners. Please do some research if you have any * concerns about features included in this ROM before flashing it! YOU are * choosing to make these modifications, and if you point the finger at me * for messing up your device, I will point that finger back at you and laugh. * Then I will put it in your eye. */ By using the ROM you agree with the above terms!
This thread is for the latest unofficial builds of CyanogenMod 7 for the Samsung Galaxy S 4G. This version is based only on upstream CM7 (currently CM 7.2.0 RC1). We have not made any theming changes, apk changes, etc. It's exactly how it would be on any other phone that receives CM7 nightlies (usually just slightly more broken). CyanogenMod 7 is stable enough on this phone where it can be used as a daily driver, provided a feature that you require is not broken. That said, you may encounter issues, so don't rely on everything. This is a beta port but we're getting very close to being ready to start the process of becoming official.
This thread is for development. If you have a problem and don't post logs (where relevant) or provide any detail, I will ignore you.
Please report issues with proper grammar, thorough explanation, and speak in a respectful manner. If you are reporting an issue that has already been reported, post some logs (logcat, dmesg, kmsg, last_kmsg, etc).
Working:
- MTD and YAFFS2.
- Tiny Preempt RCU in the kernel for lower memory allocation overhead.
- ClockworkMod Recovery (CWM) 5.0.2.8
- Power Management
- 2D and 3D Graphics
- Sound
- Brightness control
- Modem/Radio/RIL
- SMS/MMS
- WiFi
- BLN (Requires the use of neldar's BLN application. Use the pro version for the best experience)
- Ringtones
- Vibration
- GPS
- Rear Facing Camera
- Front Facing Camera *New
- Camcorder
- Video Encoding and Decoding
- cpufreq/underclocking, etc. No OC/UV.
- Rebooting to recovery
- USB Mounting in Android and Recovery Mode
- Wireless and Wired Tethering
- Bluetooth
- Voodoo sound
- 911
Broken
- Rebooting to download mode (not sure if anything can be done about this, short of hacking the bootloader)
- Car/Desk dock audio
- TV-Out
- WiFi-Calling
Known Issues/Bugs
- Check the Device Issue Tracker and the Kernel Issue Tracker
- WiFi reception is reportedly poorer than the KJ6-based ROMs. (Please report if the new wifi driver has helped!)
If you find more issues, please check with CM7 gerrit before you think it's a problem with something we've done.
If you find an issue, please provide any relevant logs. It's also preferable to post it to our github issue tracker.
If the error is occuring in /proc/kmsg or /proc/last_kmsg, it's definitely kernel related. Post it on the Kernel Issue Tracker
If the error is showing up in logcat, chances are it can be fixed through modification of our device tree. Post it on the Device Issue Tracker.
Github/Changes: https://github.com/teamacid/
Instructions are in the second post.
Builds are in the third post.73Builds & Modems
Builds & Modems
Builds
DO NOT attempt to flash these using ClockwordMod Recovery (CWM) 3.0.2.8
Twelfth Release (R13) - 03/22/2013 (04:37:48PM CDT) - Available on GooManager
update.zip:
Goo.im
Mirror
(md5sum: 48fabdf8be3fe2e52acbb6c008663b90)
Twelfth Release (R12) - 07/03/2012 (10:17:48PM CDT) - Available on GooManager
boot.img
update.zip (md5sum: a37b342792132316cb2a44f61cd0e542)
Fixed Eleventh Release (R11B)
boot.img
update.zip (md5sum: 5ea86295ef6a095cab83be6cc848def0)
Eleventh Release (R11) - 06/14/2012 (09:17:23PM CDT):
boot.img
update.zip (md5sum: b27ab2d86890381ce4109d613dedff46)
Tenth Release (R10) - 05/21/2012 (9:27:38PM CDT):
boot.img (debug version )
update.zip(md5sum)
Debug note: The debug version is meant to be used temporarily, when debugging a specific feature where extra kernel debugging is needed. Because of this, no external modules such as wifi are provided, causing wifi to no longer work until you go back to the regular boot.img.
Ninth Release (Fixed) (R9B) - 05/10/2012 (11:53:47PM CDT):
boot.img
update.zip(md5sum)
ADB Note: You need to use the Google USB drivers from now on, as opposed to the Samsung drivers. The Samsung drivers are only used for Heimdall/ODIN now, and not ADB.
I broke it. Use R9B.
Ninth Release (R9) - 05/10/2012 (06:15:24PM CDT):
boot.img
update.zip(md5sum)
Eighth Release (R8) - 04/30/2012 (12:43:31AM CDT):
boot.img
update.zip
Seventh (1st Reset) Release - 04/21/2012 (01:41:41AM PST):
boot.img
update.zip
Sixth Release - 04/19/2012 (6:47PM PST):
boot.img
update.zip
The download links to these are in the old thread, you shouldn't be using them:
Fifth Release - 04/18/2012 (2:13PM PST):
boot.img
update.zip
Forth Release - 04/09/2012 (10:17PM PST):
boot.img
update.zip
Third Release - 04/09/2012 (2:15PM PST):
boot.img
update.zip
Second Release - 04/08/2012 (12:15PM PST):
boot.img
update.zip
First Release - 04/05/2012 (8:12PM PST):
boot.img
update.zip
Modems
Here56Instructions
Build instructions: http://xdaforums.com/wiki/Samsung_Galaxy_S/SGH-T959V/Building_From_Source
Get the build from the thrid post. Make sure you read all the instructions before trying anything!
INSTALLATION INSTRUCTIONS:
Installing CyanogenMod 7 @ SGS4GWiki38Alrighty, video recording is fixed. Give me around an hour and a half to post a new build.
It's beta now. It's also thinking about getting official time.
Edit: If I don't have it up in an hour and a half or so, I probably fell asleep.
Edit2: I forgot about the front facing camera orientation. I want to fix that before I post the build. It'll take some trial and error.
New posts
-
How to make Fastboot Cable for brick Kindle for Noob/Beginner- Latest: newslettermakeman
