This kernel is for CM7, but should work on any AOSP Rom.
This thread will be the discussion of the JDkernel nightlies only.
These kernels are compiled on a nightly basis by the JDkernel Bot. You may follow @JDKBOT on Twitter to get the latest and greatest when it's available.
Nightly 8-11-11
DOWNLOAD
To keep with the latest updates, you can also purchase the JDkernel update app JDkernel downloader
Installed this and the last stable kernel. Wiped cache and dalvik. Didn't notice until I installed the nightly, but lost WIFI functionality and access to MAC Address.
Went back and installed stable had the same...
Will this work on china ota sense 3 rom?
Sent from my HTC Incredible 2 using XDA Premium App
Nightly 7-26-11 = Bootloops
REDSCARFACE1 said:
Will this work on china ota sense 3 rom?
Sent from my HTC Incredible 2 using XDA Premium App
Click to expand...
Click to collapse
No, this is an AOSP kernel. It will only work with CM7, MIUI, OMGB, OMFGB.
Sent from my Incredible 2
drtchocky said:
Installed this and the last stable kernel. Wiped cache and dalvik. Didn't notice until I installed the nightly, but lost WIFI functionality and access to MAC Address.
Went back and installed stable had the same...
Click to expand...
Click to collapse
I'm having the exact problem...
Sent from my Incredible 2 using XDA Premium App
I assume the call record feature is back in the nightlies since it is in stable? What program should I use to make recordings?
vivow nightly 08-11-2011
md5sum
anywhere we can see a changelog?
bik2101 said:
anywhere we can see a changelog?
Click to expand...
Click to collapse
+1... a changelog would be helpful.
Strange question but in what ways is this kernel better than the Tiamat one?
Sent from my Incredible 2 using XDA App
This kernel is great but I noticed on the most recent nightly (9-6-2011) the headset volume is very low in my left ear bud. I thought it was my head phones but the issue goes away if I flash the tiamat kernel. Not sure were I need to go to report it...
jtseidner said:
This kernel is great but I noticed on the most recent nightly (9-6-2011) the headset volume is very low in my left ear bud. I thought it was my head phones but the issue goes away if I flash the tiamat kernel. Not sure were I need to go to report it...
Click to expand...
Click to collapse
You can post on the Rootzwiki forum. The dev usually responds there. http://rootzwiki.com
Just find the thread in the Inc2 developer section.
jtseidner said:
This kernel is great but I noticed on the most recent nightly (9-6-2011) the headset volume is very low in my left ear bud. I thought it was my head phones but the issue goes away if I flash the tiamat kernel. Not sure were I need to go to report it...
Click to expand...
Click to collapse
I just tested with my headset. I watched several Youtube videos, and played an mp3 with the music app. I couldn't find anything wrong with stereo sound levels. I tested using JDKernel 9-6-11 and CM7 nightly #56.
I've been using the 9-6-11 for the past few days now with Miui 1.9.9. I use my music player (player pro) for an hour each morning and have not noticed a lack of volume in the left side headphone. Strange...
JAS_21 said:
I just tested with my headset. I watched several Youtube videos, and played an mp3 with the music app. I couldn't find anything wrong with stereo sound levels. I tested using JDKernel 9-6-11 and CM7 nightly #56.
Click to expand...
Click to collapse
I am using the same CM nightly. I just reflashed jdkernel 9-6 and tested again. The first set of headphones were inner ear buds and its definitely most noticeable with those. With a pair of standard iPod headphones, its more subtle but it's still there. And I switched them back and forth between my ears to make sure I just wasnt going deaf in one ear
After listening some more, I would guess its 60% right, 40% left. Which isnt that noticable at lower volumes, but when you turn it up all the way, my right ear is almost hurting when the left feels about right.
jtseidner said:
I am using the same CM nightly. I just reflashed jdkernel 9-6 and tested again. The first set of headphones were inner ear buds and its definitely most noticeable with those. With a pair of standard iPod headphones, its more subtle but it's still there. And I switched them back and forth between my ears to make sure I just wasnt going deaf in one ear
After listening some more, I would guess its 60% right, 40% left. Which isnt that noticable at lower volumes, but when you turn it up all the way, my right ear is almost hurting when the left feels about right.
Click to expand...
Click to collapse
Don't worry, I have the same issue. Right side does not work at all. Through my car speakers.
Updates have been slow accross the board (roms, themes, and kernels) we are all waiting for kernel.org to go back up.
Sent from my Carbonite fused ADR6350
I finally scored a 4000 quadrant score clocked at 1766MHz.
trock79 said:
Don't worry, I have the same issue. Right side does not work at all. Through my car speakers.
Updates have been slow accross the board (roms, themes, and kernels) we are all waiting for kernel.org to go back up.
Sent from my Carbonite fused ADR6350
Click to expand...
Click to collapse
You should update the OP with the link for nightlies download location.
There's a new build up in the nightlies.
http://mirror.jdkoreclipse.net/kernel/vivow/
Related
I just starting to adjust to the new feel of it. but it keeps restarting my phone over and over. once every 30 mins. even if I'm in the middle of a phone call.
I'm happy as hell i didn't miss my call for the interview i have tomorrow.
anyway to fix this issue. started happening after i had to flash the file that helps fix the FC of the SMS/MMS popup
Make sure you have wifi sleep policy set to never.
Sent from my PC36100 using Tapatalk
it still restarted. just did 10 seconds ago lol
Change your kernel.
Did you try the EVO MIUI devs at forums.miui-dev.com?
Holyrolla said:
Did you try the EVO MIUI devs at forums.miui-dev.com?
Click to expand...
Click to collapse
yes i did that one. im on the kernal is came with cause idk which kernal i should use.
There are two usual culprits:
1.You need to set wifi sleep policy to NEVER (as sultan of swing mentioned), or
2. incomplete wipe. You need to fully wipe data,.cache, dalvik cache before installing MIUI, especially coming from a Sense rom. Search this forum for the format-all.zip file. Flash it in recovery for the full wipe. Then flash rom.
bigmoogle said:
There are two usual culprits:
1.You need to set wifi sleep policy to NEVER (as sultan of swing mentioned), or
2. incomplete wipe. You need to fully wipe data,.cache, dalvik cache before installing MIUI, especially coming from a Sense rom. Search this forum for the format-all.zip file. Flash it in recovery for the full wipe. Then flash rom.
Click to expand...
Click to collapse
i did set it to never. and i actually used a format-all.zip file.
kyhassen said:
i did set it to never. and i actually used a format-all.zip file.
Click to expand...
Click to collapse
Try a different kernel.
kyhassen said:
I just starting to adjust to the new feel of it. but it keeps restarting my phone over and over. once every 30 mins. even if I'm in the middle of a phone call.
I'm happy as hell i didn't miss my call for the interview i have tomorrow.
anyway to fix this issue. started happening after i had to flash the file that helps fix the FC of the SMS/MMS popup
Click to expand...
Click to collapse
hmmm...it would help if I read more carefully. I never flashed that zip file.
But if I were expecting an important call, I'd switch to a rom I could trust - probably a sense rom like Fresh or MikWhatever. And I say this as MIUI fan woman
im liking the rom so far. sad part is im a sense fan. this isn't what i wanted, but after playing around with this rom for 2 hours i liked it a lot and the stuff u can do.
i already can tell this is faster than a sense rom. 1 of the games i played on the sense roms lagged a little. but i dont get as much lag in the MIUI rom.
sultan.of.swing said:
Try a different kernel.
Click to expand...
Click to collapse
This. Do this.
I was so frustrated with MUIU until I changed kernals. Now it's great.
I am running Savage 1.6 CFS-HAVS-WIMAX-SBC.
I have not had any reboots and when I pulled off the charger today I stayed at 100% for over 2 hrs.
Having issues finding a kernal now for some reason.
Sent from my HTC Evo using XDA App
sultan.of.swing said:
I am running Savage 1.6 CFS-HAVS-WIMAX-SBC.
I have not had any reboots and when I pulled off the charger today I stayed at 100% for over 2 hrs.
Click to expand...
Click to collapse
I find Savage 1.6 works best for me but every Evo is different. Other people swear by Zen-Droid which only bootloops my phone. bcnice-stable (v7 or v8) is another popular kernel (laggy for me). The safest (?) one seems to be cm6-Snap 7.6 (don't use SnapTurbo) - everything seems to work this snap.
ok thank you bigmoogle. is this the one you were talking about http://forum.xda-developers.com/showthread.php?t=883455&highlight=Savage
also which do i use the CFS or the BFS. i dont quiet understand the difference between the two.
kyhassen said:
ok thank you bigmoogle. is this the one you were talking about http://forum.xda-developers.com/showthread.php?t=883455&highlight=Savage
also which do i use the CFS or the BFS. i dont quiet understand the difference between the two.
Click to expand...
Click to collapse
Yep, that's the kernel. As to which to use, I am definitely NOT the person to ask. In the beginning, kernels were pretty.simple but as time went by, they've collected more and more acronyms. I use Savage 1.6 CFS HAVS. I think it has SBC because the other one is named noSBC.
I have been working on fixing the bugs in cyanogenmod that cause the data issues when using BFS kernels.
The CM7 nightly build is here: http://www.multiupload.com/0Z3Z8M5FE7
and my v0.6 bfs kernel is here: http://www.multiupload.com/ZOAMV7NQBI
If nothing seems to be broken, feel free to review http://review.cyanogenmod.com/#change,9829 and http://review.cyanogenmod.com/#change,9734
aeroevan said:
So I still can't post to the development forum, but I have been working on fixing the bugs in cyanogenmod that cause the data issues when using BFS kernels.
The CM7 nightly build is here: http://www.multiupload.com/0Z3Z8M5FE7
and my v0.6 bfs kernel is here: http://www.multiupload.com/ZOAMV7NQBI
If nothing seems to be broken, feel free to review http://review.cyanogenmod.com/#change,9829 and http://review.cyanogenmod.com/#change,9734
Click to expand...
Click to collapse
I may work on flashing this this week, I'm on miui but missing me some cm7. Is this having the youtube and mms issues cm has?
Sent from my Incredible 2 using xda premium
Loaded Saturday morning, been running fine. No data drops.MMS, YouTube, data anamation
arrows, compass works. Haven't tried any flash videos.
Running smarta** at 245/1113. Getting 2200 - 2500
on quadrant. (If that matters)
I think I finally fixed all of the possible data issues:
Updated cm7 nightly kang: http://www.multiupload.com/UI6MOP5OSD
which includes http://review.cyanogenmod.com/#change,9829 and http://review.cyanogenmod.com/#change,9850
That should cover every corner case where data could be lost due to the dnsproxyd cache (this was a bug in AOSP, so all AOSP roms will have this bug until the fix is applied).
I also have a test build for v0.7 of my kernel (which should fix zram enable issues): http://www.multiupload.com/WDSSQ85LJM I also rewrote my updater-script, so let me know if there are any issues (I've only tested on my cm7 kang build).
Working well for me so far. Using the 0.7 Kernel, CompCache up and running. No data loss issues so far today. I think all may be well
can i flash this over my current cm7 nightly?
Been running for a day now, haven't noticed any depreciated performance/battery.
haven't really followed your kernels, but have you addressed the low call volume issue that plagues the built in kernel?
if so, I'll jump on and start testing immediately.
Yes areoevan kernels have the vol. fixed.Been running them since the first one he released.
from the dates of the changes and the fact they've been merged, I assume all new nightlies have the new changes (minus the kernel part) correct?
dnoyeb said:
from the dates of the changes and the fact they've been merged, I assume all new nightlies have the new changes (minus the kernel part) correct?
Click to expand...
Click to collapse
133 and 134 nightlies have the changes incorporated.
ok, so. i flashed this. the is the best my compass has acted since i flashed CM7, the in call volume is perfect. I'm getting really good Quadrant scores(for whatever that is worth), data dropping in and out seems to be gone. It wouldn't connect to WiFi right away, but eventually did.
My question is; what is the difference between this kernel and the .06 cfs version?
Umm ok So that was weird... Delete please.
What's weird?
Sent from my Incredible 2 using XDA App
Mt reply was to another topic, and somehow ended up here
PacerguyDon said:
Mt reply was to another topic, and somehow ended up here
Click to expand...
Click to collapse
yea, that's weird.
Which one would you suggest?
Sent from my DROID2 GLOBAL using xda app-developers app
good jelly bean rom
I got one from the goo. im app jellybean v1.3 otter oxd34d and everything works besides Google now and bluetooth
Just got jelly bean every thing works except Bluetooth of course. I flashed gapps and not Google works
Sent from my Amazon Kindle Fire using xda premium
I've also been using the "goo" one (a.k.a. "Jandycane") as well with very few problems.
Get from goo.im or here
http://forum.xda-developers.com/showthread.php?t=1766829
Sent from my Amazon Kindle Fire using xda app-developers app
I would recommend CM10 using SGT7 enhancements by twa_priv
And I have been very pleased with EyeCandy. The ROM's title speaks for itself, it is simply the sexiest ROM out there.
I have been using eyecandy and its great.
Sent from my DROID2 GLOBAL using xda app-developers app
I've found that although jandycane has lots of features, hashcode's ROM is more stable.
I have been using Hashcode's release. From what I heard it is the most stable.
When life gives you tech....Make use of it.
I flashed JellyCane last night and its a really nice ROM. Ive found zero issues in my 6+ hours of testing after flashing it last night.
I'm using twa_priv's and it's working very well. I still get some crashing errors whenever I mute the volume and cannot install the Kindle android app (error -24). I've had Chrome crash once or twice and had the device spontaneously reboot a couple times but otherwise it's working way better than how Amazon shipped it to me.
I'm following all of the JB ROM threads and it sounds like they are roughly equivalent in terms of stability.
-S
Sent from Tapatalk on twa_priv's ROM
shuddles said:
I'm using twa_priv's and it's working very well. I still get some crashing errors whenever I mute the volume and cannot install the Kindle android app (error -24). I've had Chrome crash once or twice and had the device spontaneously reboot a couple times but otherwise it's working way better than how Amazon shipped it to me.
I'm following all of the JB ROM threads and it sounds like they are roughly equivalent in terms of stability.
-S
Sent from Tapatalk on twa_priv's ROM
Click to expand...
Click to collapse
What build are you on that crashes when you mute?
Both the 7-23 and 7-28. I just reflashed 7-28 and wiped cache / dalvik to be sure.
I had the problem with the stock volume widget and now also with the Volume Control app when I slide the volume down to zero percent.
Anything I can do to gather more info? Am I the only having these muting crashes?
I just tried it again with the stock widget in the status bar (tablet mode) and hitting mute does not produce the com.android.phone errors; only when you slide the volume down to zero.
-S
Sent from Tapatalk on twa_priv's ROM
shuddles said:
Both the 7-23 and 7-28. I just reflashed 7-28 and wiped cache / dalvik to be sure.
I had the problem with the stock volume widget and now also with the Volume Control app when I slide the volume down to zero percent.
Anything I can do to gather more info? Am I the only having these muting crashes?
I just tried it again with the stock widget in the status bar (tablet mode) and hitting mute does not produce the com.android.phone errors; only when you slide the volume down to zero.
-S
Sent from Tapatalk on twa_priv's ROM
Click to expand...
Click to collapse
confirm this crash
Hashcode's was a great jumping off point, but I think Jandycane is the way to go now. Very stable, almost all the features you could want in a ROM. Google Now is fc'ing for me, but I just use the browser for search anyway.
shuddles said:
Both the 7-23 and 7-28. I just reflashed 7-28 and wiped cache / dalvik to be sure.
I had the problem with the stock volume widget and now also with the Volume Control app when I slide the volume down to zero percent.
Anything I can do to gather more info? Am I the only having these muting crashes?
I just tried it again with the stock widget in the status bar (tablet mode) and hitting mute does not produce the com.android.phone errors; only when you slide the volume down to zero.
-S
Sent from Tapatalk on twa_priv's ROM
Click to expand...
Click to collapse
Can't reproduce. Both muting and sliding to 0 works fine for me.
chemo1191 said:
Hashcode's was a great jumping off point, but I think Jandycane is the way to go now. Very stable, almost all the features you could want in a ROM. Google Now is fc'ing for me, but I just use the browser for search anyway.
Click to expand...
Click to collapse
How stable is it would you say? Enough to use as a daily driver? I still have Gede 1.7 for my girlfriend's KF, but thinking about upgrading to a jelly bean rom. Just wondering if they're stable enough yet..
exoteric said:
How stable is it would you say? Enough to use as a daily driver? I still have Gede 1.7 for my girlfriend's KF, but thinking about upgrading to a jelly bean rom. Just wondering if they're stable enough yet..
Click to expand...
Click to collapse
Hard to answer since it depends what you need to work, but I'm extremely happy with the stability. I use the ROM primarily for chrome, gmail, google reader, tapatalk, boid (twitter), youtube, google+, goodreads. All that stuff is working great for me for at least a week of heavy use. I get some occasional crashes/reboots but not more than once per day.
I haven't tried any games or the Facebook app. My primary disappointment right now is that I can't get the Kindle android app to install. It's ironic that I can't use my Kindle as a Kindle.
If you want to test the waters I recommend going the FFF dualboot route. Put one of the JB ROMs on the main partition and Gede on the alternate. Minor hassle to reboot to the other ROM but also amazing that all of these great devs have made Amazon's limited device into something ridiculously versatile. My formerly dusty KF has become my primary device!
-S
exoteric said:
How stable is it would you say? Enough to use as a daily driver? I still have Gede 1.7 for my girlfriend's KF, but thinking about upgrading to a jelly bean rom. Just wondering if they're stable enough yet..
Click to expand...
Click to collapse
I am using it as a daily driver and it seems to be working well.
I have tried a few of them now, but love eye candy the best, however all the devs have done an outstanding job so far.
Sent from my Amazon Kindle Fire using xda premium
I've read through all of the individual ROM threads, as well as any question threads, and it seems like none of them are quite ready.
I run CM 7.2 with essentially no modifications, for reference. S-off, CWM 3.0.0.8.
Thanks in advance for your input.
nitzua said:
I've read through all of the individual ROM threads, as well as any question threads, and it seems like none of them are quite ready.
I run CM 7.2 with essentially no modifications, for reference. S-off, CWM 3.0.0.8.
Thanks in advance for your input.
Click to expand...
Click to collapse
What are you missing from them to be a daily driver? I've had zero issues on my CM9 build and you can find two options in the development thread that are extremely stable.
The only thing not working with ICS is the stock camcorder to my knowledge, but third party apps still work if you need it.
Zimeron said:
What are you missing from them to be a daily driver? I've had zero issues on my CM9 build and you can find two options in the development thread that are extremely stable.
The only thing not working with ICS is the stock camcorder to my knowledge, but third party apps still work if you need it.
Click to expand...
Click to collapse
I'm wondering the same thing.
Almost everything works from what I used.
Sent from my Galaxy Nexus using Tapatalk 2
Zimeron said:
The only thing not working with ICS is the stock camcorder to my knowledge, but third party apps still work if you need it.
Click to expand...
Click to collapse
Abduction ICS and Abduction the 4th Kind have the Camcorder working good.
Herp Derp Tapatalk 2
I can't get mlb at bat to play mlb.tv on both DInc and Nook Color running CM9. Not a location issues, it tries but says Error-Can not play video. All other video seems to work.
Can't see any other issues with CM9, runs ok but maybe a little slower than CM7.
Depends what your standards for a daily driver are. If you mean a phone you can use to make calls, use some apps, without a lot of hassle, then yeah, they're daily drivers. If you want perfection, no glitches or bugs ever, then no.
The camcorder is the biggest issue for me (I was running Evervolv, but they're all built on the same base). Yeah, the camcorder kind of works, but playback is broken, and it's not nearly as smooth as stock. Also, I find that after a while (a day or two), things just start to get laggy. Not awful, but it doesn't fly like it does on stock. The graphics (especially the home screens and the app drawer) are actually way smoother on ICS than on stock, but it takes longer to actually get your apps opened and running. I'm currently rockin' Ice Cream Senseless with Holo Launcher. ( I also spent some time using Touch of Blue, I liked it a lot, but the 2am reboots kept making me miss my alarm clock and be late for work...) My current setup gives me 95% of what I liked about ICS, and it's very snappy and extremely stable. No doubt I'll be back to craving Ice Cream Sandwich (or Jelly Bean - lol) in another week or so, but I always end up coming back to this one.
Smoothness is the biggest issue, IMO.
Sent from my ADR6300 using xda app-developers app
I used CM a9 build before going to the SIII and it worked the best for me. Was using Evervolv for a while, but that soon became very unstable.
bucks130 said:
I used CM a9 build before going to the SIII and it worked the best for me. Was using Evervolv for a while, but that soon became very unstable.
Click to expand...
Click to collapse
I ran drk.hd's CM a9 for a while and it worked well except for the known video camera issue. The only reason I changed is because I got flash happy.
I went to mamarley's CM9 w/linearo and it is running very smooth (still no stock video camera). Although, I had to use the ics incredikernel w/HWA because mamarley's kernel was not communicating with my touch screen.
Also, I find that after a while (a day or two), things just start to get laggy. Not awful, but it doesn't fly like it does on stock.
Click to expand...
Click to collapse
This is the general consensus that scares me away.
http://forum.xda-developers.com/showthread.php?t=1719879
[ROM] Touchwiz 5.1.4 Fixed Location
I been on this rom for a bit. No major complaints. No CC and voice search will crash using navigation. But very smooth overall. Daily driver worthy for sure.
Sent from my ADR6300
I've been using the Linaro optimized CM9 ROM with the included Mamarley kernel.
The only issue I've run into is a problem with the bluetooth connecting to my car and not being able to play the call audio through the car speakers. I "think" they're working on a fix for it.
EDIT: SUPER sorry wrong forum
txlnghrnpe said:
I ran drk.hd's CM a9 for a while and it worked well except for the known video camera issue. The only reason I changed is because I got flash happy.
I went to mamarley's CM9 w/linearo and it is running very smooth (still no stock video camera). Although, I had to use the ics incredikernel w/HWA because mamarley's kernel was not communicating with my touch screen.
Click to expand...
Click to collapse
is your's a amoled or slcd? I ended up having to do the same thing and I am just curious.
I've been on MIUI v4 since May and it's been very solid with the exception that Netflix doesn't work for me. It plays about 2 seconds of sound (no video) and then just a black screen. Going forward or backward in the video doesn't do anything to help it pick back up. MIUI GB worked great with Netflix previous to the ICS build. I thought maybe it was HWA related, but I've tried a few different kernels and haven't had any luck. Youtube plays just fine.
I am going to flash cm9 in a moment to see if Netflix works there.
edit: Flashed cm9 -- still the same issue with Netflix. Plays sound for about 2 seconds, then stops. Anyone else with this problem?
Cheesethief said:
Abduction ICS and Abduction the 4th Kind have the Camcorder working good.
Click to expand...
Click to collapse
Loving Abduction the 4th Kind, thanks for the tip
---------- Post added at 12:57 PM ---------- Previous post was at 12:48 PM ----------
Aeckert said:
edit: Flashed cm9 -- still the same issue with Netflix. Plays sound for about 2 seconds, then stops. Anyone else with this problem?
Click to expand...
Click to collapse
I think it's a problem related to the camcorder not working. I'm no Android programmer, but I'd bet it's because of a codec issue. Shame that barely any ROMs support a working camcorder.
Have you tried Evervolv 2.2.0p3? I hear that ROM has a working camcorder, but haven't tested it myself.
drk.hd CM9a9 with Chad/Tiny Incredikernel HWA
Working great as a daily driver, camcorder/netflix/youtube (occasionally) dont work.
Im very happy with it otherwise.
(I thought I'd report the following issue, in case someone else had experienced it or if someone understands why)
On non-stock ROMs, the sound from ANY application (phone, music player, etc...) comes out heavily distorted through the audio jack but NOT through the phone's speaker. This has been verified on CM10.1.3 STABLE and various 4.3 ROMS.
I used to not have this problem and I've been running CM10.1 based ROMs and more recently various 4.3 ROMS without this problem for many months. Recently the problem started so I tried completely wiping, reformating of SD card, and re-installations of ROMs to no avail. Took it to a technician who replaced the whole jack-unit but it didn't help. So...I ODINed back to stock 4.1 and problem was fixed! However, any time I install a non-stock ROM, the problem returns, and only re-ODINing back to a stock ROM fixes it. I've tried 4 or so times....
I've been able to flash Custom 4.3 STOCK-BASED ROMS (based on leaks) without any issue as well, so it's not an issue with flasing "custom ROMs" perse, or with Android 4.3...(thank God! at least I can flash Touchwiz 4.3!)
Does anyone have a clue what's going on here?
Do the roms have a volume or sound enhancement mod do you think? If you flash an older one that used to work fine, does it also exhibit the same problem? If not, maybe try using the audio files from the old Rom in the new one? Probably won't help, but you never know...
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Do the roms have a volume or sound enhancement mod do you think? If you flash an older one that used to work fine, does it also exhibit the same problem? If not, maybe try using the audio files from the old Rom in the new one? Probably won't help, but you never know...
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
As far as I know, there were no audio/volume enhancements in the ROMs I tried (CM 10.1.3 and Carbon ROM) only the usual DSP audio app (which I made sure wasn't running). Yeah, those exact ROMs totally worked in the past without a problem, and it wasn't just my sound files that sounded distorted out of the jack it was any sound from any app (system sounds, phone, etc...)
I might try again with a non-stock ROM if/when Android 4.4 becomes stable, otherwise for the time being I'm happy to stick with TW 4.3 (thanks to you!) It's really awesome!
jon.s.nelson said:
As far as I know, there were no audio/volume enhancements in the ROMs I tried (CM 10.1.3 and Carbon ROM) only the usual DSP audio app (which I made sure wasn't running). Yeah, those exact ROMs totally worked in the past without a problem, and it wasn't just my sound files that sounded distorted out of the jack it was any sound from any app (system sounds, phone, etc...)
I might try again with a non-stock ROM if/when Android 4.4 becomes stable, otherwise for the time being I'm happy to stick with TW 4.3 (thanks to you!) It's really awesome!
Click to expand...
Click to collapse
Can't argue with you there! On a new build now and will get it released when I get my computer back from my daughter! So watch out for that in just a bit!
And in case you didnt see it, there is a 4.4 Rom posted. Looks like it was just updated with more functionality too. You should take a look if you haven't yet.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Can't argue with you there! On a new build now and will get it released when I get my computer back from my daughter! So watch out for that in just a bit!
And in case you didnt see it, there is a 4.4 Rom posted. Looks like it was just updated with more functionality too. You should take a look if you haven't yet.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I tried the 4.4 and unfortunately I the same audio distortion problem returned right away. This was coming from being on the TW 4.3 Leak (#2) from over a week straight with the problem. I researched how to lower the audio jack levels in Cyanogen ROMs and found out about this file: "snd_soc_msm_2x" in the system folder
I messed with that file a bit (with a text editor) and managed to get the distortion to go away by lowering ALL of the headphone outputs by 20%. Problem is that then the volume was really too low to enjoy music on. I tried only 10% lower but then the distortion came back. After that I gave up, but convinced that there's something in the deep CM audio settings which my phone no longer likes, Weird.
BTW, I was able to Nandroid back to my TW 4.3 and the problem disappeared. So at least, there's no need to ODIN if I ever want to try again.
there is information about hacking that file here on xda. i think i saw it in an s4 forum but they got their info from the s3. if i remember or find it again ill let you know. but a quick search might find it as well.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2