Related
Is smoking ass hot!!!
Sent from my ADR6300 using XDA App
cm7 build #7-#14 stock kernal HTC Incredible no video or sound for MMS... any fixes ?
cleared cache, wiped dalvik, and did a complete data wipe...
Nunoriffitti said:
cm7 build #7-#14 stock kernal HTC Incredible no video or sound for MMS... any fixes ?
cleared cache, wiped dalvik, and did a complete data wipe...
Click to expand...
Click to collapse
It's been fix several builds ago. MMS video with sound now works.
Sent from my ADR6300 using XDA App
I think pretty much everything works now with the latest cm7 builds. Of course, there are going to be several more bugs fixed that you may or may not ever run across.
I have flashed cm7 nightlies every night from build #7, it might be working but it is not working on my Incredible...the MMS is received but video won't play and the sound won't play either, usually a qcp file... this has been my only issue on every build, any help is greatly appreciated, thank you
Nunoriffitti said:
I have flashed cm7 nightlies every night from build #7, it might be working but it is not working on my Incredible...the MMS is received but video won't play and the sound won't play either, usually a qcp file... this has been my only issue on every build, any help is greatly appreciated, thank you
Click to expand...
Click to collapse
How have you been installing the nightly builds? Just flashing over? Clearing Dalvik and cache? Full wipe? If you've just been flashing over try clearing Dalvik and the cache. If that fails then do a nandroid backup and full wipe and reflash.
Agreed, it is really amazing
I'm looking forward to trying this ROM, but I'm loving my device right now while running Virtuous w/ Lou's #9 kernel. Everything works, is fast and very stable. Maybe after I get back from vacation next week the CM7 team will have most of the kinks worked out. Can't wait!
There aren't any kinks, that's the point
They're very close to a RC
I noticed with build 19 that notification beeps now come out as BEEPSQUAKPPP really loud and distorted (sorry for the bad sound effect impression). Is anyone else having this problem? Specifically I noticed it when connecting to BT Speakerphone and SMS inbound.
i started flashing these around #10. really great build so far. i may switch to CM7 as a daily once the final is released.
toosurreal01 said:
There aren't any kinks, that's the point
They're very close to a RC
Click to expand...
Click to collapse
Yes, they are close, but the reason they aren't there yet is because there are still a few kinks. They're calling it RC0 right now, but I'm not sure what to think of that. The following definition is from Wikipedia:
"The term release candidate (RC) refers to a version with potential to be a final product, ready to release unless fatal bugs emerge. In this stage of product stabilization, all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bug."
CM7 skipped right over Beta. It went straight from Alpha to RC0. Maybe the thinking is, with so many people flashing the nightly builds that suffices as Beta testing.
bgunckel said:
Yes, they are close, but the reason they aren't there yet is because there are still a few kinks. They're calling it RC0 right now, but I'm not sure what to think of that. The following definition is from Wikipedia:
"The term release candidate (RC) refers to a version with potential to be a final product, ready to release unless fatal bugs emerge. In this stage of product stabilization, all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bug."
CM7 skipped right over Beta. It went straight from Alpha to RC0. Maybe the thinking is, with so many people flashing the nightly builds that suffices as Beta testing.
Click to expand...
Click to collapse
According to their post, it is still Alpha. Not Beta, Not RC. It is Alpha.
So, will RC1 == beta??? I don't know, but at this point, I would say technically yes because they are still putting in new features every few days. That, by defination, is alpha. Beta would be testing and fixing, testing and fixing. RC would be they think it is done, lets do one more full-on test. If a problem is found, fix and increment RC. If none found, release as final version.
Also, at this point, there is no bugtracker for CM7. That would indicate alpha, where bugs upcoming features are still internal to the devs. Usually, during beta, public bugtracking is provided to get everything working on a broad scale and to accept additional feature requests.
wmsforties said:
Is smoking ass hot!!!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Tell me how you really feel...
Battery life
I am really liking the nightly builds as well.
I am on build #20 now and everything seems to be working just fine.
Except the battery life. My battery only last ~8 hours now. Looks like it is just being killed by the display. The display used 70% of the battery with an uptime of 2 hours.
I may have to switch back to another ROM if I can't get better battery life that 8 hours.
I'm on CM7 #19 - Anyone notice that the Pinch to Zoom in the browser is not re-sizing the text wraparound properly. Takes like 3 or 4 attempts to get it right.
Is it just me or are others seeing this as well?
im on 22 with the beta kernel and this thing rocks, should be an rc imo as it is, I havent had issues since the first omgb and evervolvs, never had a prob with crackflashers or nightlies. I have even gone back to other roms, they never make it thru the day on my phone. CM7 is THE ROM!
#24. Wow!
Sent from my ADR6300 using XDA App
Hard to believe these aren't listed as RC1, running very smooth!
So I have an Evo which I don't use for anything. It has not number on it and I don't need it as a back up. I use it only for listening to music (speaker only) and taking and watching videos. Sometime I may connect it to wifi to download a certain app or to watch something on YouTube. So this thread could be called a survey I guess? But what's the best ROM out here for me to put on the phone in my case? I basically want battery life + performance + louder speaker (the Evo speaker sucks compared to my other phones sadly). I flashed the 4 kornerz (sorry if I misspelled) ROM and flashed the beats audio and the underworld kernel, but noticed a lag after flashing that kernel so I re-flashed the stock kernel.
I have not had time to actually use it and test out how it goes with my usage but I think it'll be alright?
I have also used Energy ROM (kills my batttery too quick) and CM7 (phone speaker isn't loud enough) so what other ROMs would you recommend for me? Or what mods or kernels would work with 4kornerz ROM that would ensure better battery life?
Sent from my SPH-D700 using XDA App
I'm doing the same thing with my Evolution - typing on it right now, actually.
I'm using deck's 1.3d, mason .15 kernel, beats audio addon with go launcher. Smooth as can be and I get tons of battery life in airplane mode.
roflboxer said:
I'm doing the same thing with my Evolution - typing on it right now, actually.
I'm using deck's 1.3d, mason .15 kernel, beats audio addon with go launcher. Smooth as can be and I get tons of battery life in airplane mode.
Click to expand...
Click to collapse
That's exactly the kind of answer I'm looking for thanks =). I thought about trying an ICS build but wasn't too sure if I wanted to because I thought it might have some bugs or be laggy or have not so great battery life or sound quality decreased. But I'm going to test out 4 kornerz for a bit then will try your settings next. Thanks for the reply =).
Wait.. what's the ROM your using lol? When I first read it I thought you were talking about one of the ICS builds but I'm starting to have second thoughts. I'm not very familiar with every ROM out here because I barely use the Evo but can you post the link to the ROM? Or at least tell me what's the title of its thread lol? And also your kernel pleeeaseee.
Sent from my SPH-D700 using XDA App
Decks 1.3d is his famous Gingerbread build. Search for it and you can't miss it. The thread title has decks, and. 1.3d in it I believe. It is legendary for being the best AOSP Gingerbread ROM with the best battery life and stability. Coupled with that kernel the above user mentioned, it will give you tremendous battery life! Much better than ICS at this beta phase.
Sent from my PC36100 using XDA
Is 1.3d better than 1.3? 1.3 is newer...
Art2Fly said:
Is 1.3d better than 1.3? 1.3 is newer...
Click to expand...
Click to collapse
1.3d would probably be a later version of it, as a, b, c, and d. Probably just minor fixes through out that version.
No, I clarified it. 1.3d is just a beta, 1.3 is stable. 1.3 is newer.
*New Downloads*
gingerbread evo 1.3 Stable
gapps 8-28-2011
gapps 8-28-2011 with Voicemail.apk
*Older Downloads*
gingerbread evo 1.3d beta
gingerbread evo 1.3b2 beta
gingerbread evo 1.3b beta
gingerbread evo 1.2.1 Stable
gingerbread evo 1.2 Stable
gingerbread evo 1.0
Click to expand...
Click to collapse
1.3 is newer, but i've had the best results with the 'beta' d version. runs like a beeeeeeeeeeeeeast.
Well I did find it and I will try flashing it as soon as I can. Is the stock kernel that comes with it the one that was recommended to me? Or where can I find the other kernel?
And I'm just kinda starting to get confused. Some people are saying 1.3 and some are saying 1.3d. Which one is better..? Logically thinking I would say 1.3d would be better since it probably just contains little fixes and nothing major updated but those little fixes may be a big problem to me without them so I think ill try out 1.3d unless I am told not to.
Sent from my SPH-D700 using XDA App
if you were having issues with cm7 you may experience the same with Deck's as his is just a custom version of cm7, yet designed to operate on Sprint more effectively.
You say the speaker wasn't loud enough with cm7? Did you adjust the settings in DSP manager?
I have 3 EVO's, 2 operational and on is my 3 year old's "phone," he is an angry bird addict! I have the phone on constant airplane mode and simply turn on wifi when I would like to connect. We are constantly asking him to turn it down so no sound problems here.
I would recommend the cm 7.2 rc1 from the cyanogenmod website, and don't forget gapps.
Again Deck's is based on cm7 though he hasn't updated in a long time and there have been many many improvements to the cm source since he stopped building. Cm7 is also still a work in progress, they are not dropping support for it, though they may bring cm9 to the EVO eventually 7 is the current supported version.
Honestly, I think the advice above is sound, but I still recommended deck 1.3 with Mason v14 kernal without hwa. Or if you want more battery, flash the slightly less stable v15rc G version. G for nonhwa. And then I would clock down to about 850mhz as your Max (don't know the exact value but the performance settings in deck shouldn't be too hard for you to figure out) and then use the wheatley kernel if you're on v15rc or intellidemandx if you're on 14. Smartassv2 would be my recommended governor, but it doesn't play well with media when the screen is off so you take your choice.
Sent from my PC36100 using XDA
Well sound was only a problem to me because I have an Epic 4G which, stock v.s stock, is louder. And I've tried CM7 on my epic and loved it but the sound was a problem the same as on the Evo. But I guess I would give up sound for better battery life lol. I'm going to flash deck's 1.3 right now. But I still can't seem to find the kernels you guys are talking about can someone please post the link to the thread?
Sent from my SPH-D700 using XDA App
So I just flashed the rom with the kernel.
I'm having one tiny problem.
I didn't install gapps (don't really need it) so I tried to bluetooth a file explorer.
I've noticed with bluetooth on the phone reboots? (It happened twice so far)
Ill keep trying the ROM out and see if I have more reboots. If its just bluetooth related then its not a problem
Sent from my SPH-D700 using XDA App
One more thing. Not sure if its the ROM or my phone but the power button seems to not work so well. It turns off the screen normally but turning the screen back on is the problem. It doesn't turn on by just pressing it I have to hold it down and then the power menu pops up and the screen turns on.
Sent from my SPH-D700 using XDA App
What ROM and kernel did you flash? Sleepiness is due to kernel undervolting issues... or kernel related at least. Bluetooth would be the same I would gather... sounds like stock kernel for you!
My original EVO loved underclocking, and I could squeeze a few precious hours out of the battery with the right kernel, governor and voltages. My replacement however will not undervolt at all... not even 25 mA... so each evo is different. I am of the opinion that stock is going to give you the best overall performance.
Click to expand...
Click to collapse
...are you guys kidding me right now???
Mason kernel is for ICS, as in not Gingerbread so it will break things on Decks 1.3... come on man!!!
If you really want a great experience just flash CM 7.2 please and leave it be because those guys know Android and what it needs to love you long time... I apologize for the inconvenience of bad information...
imheroldman said:
...are you guys kidding me right now???
Mason kernel is for ICS, as in not Gingerbread so it will break things on Decks 1.3... come on man!!!
If you really want a great experience just flash CM 7.2 please and leave it be because those guys know Android and what it needs to love you long time... I apologize for the inconvenience of bad information...
Click to expand...
Click to collapse
But on the kernel's thread it said for "AOSP ROMs" and I did flash it and it worked. It does say it would also work on ICS tho.
I think I may just go to CM7 tho.
The april 8th update is better than the official one?
Sent from my SPH-D700 using XDA App
Here is what you want...
CM 7.2
Wipe:
All/factory reset
Cache
dalvik cache
System
Boot
Then flash the ROM, no gapps for you if you don't want.
Mason says it apparently works on GB or ICS, but I don't see how that could actually be possible... though I am not a kernel dev... but your issues do seem to stem from a kernel issue...
I'd imagine using a sense kernel based rom like swagged out stock N would get you the best musical results, since it has a kernel that was specifically built for the EVO, and not something AOSP generic. Maybe throw the zip file in for beat audio, or use poweramp instead.
Swagged out stock N 2.0.9 with universal aggressive lionfish 1.8 is doing REALLY well for me. It uses the go launcher, instead of sense.
haha luckily ICS is based off of a GB Kernel, Tiamat. Mason has two flavors of his popular kernel, the "G" version which CAN be used for Gingerbread AND NON-HWA ICS Roms, and the "I" version which is strictly used for HWA enabled ICS roms.
also jamieg71 has aosp gb build that is being updated more recently if you wanna check that out havent run it personally but if its anything like his ics build it will be great
I saw this thread over at the Galaxy Nexus forums, and since I figured more people than just me might want to know more about the different ROMs, I thought it was worrth a thread here as well.
What I'm interested is a quick reference thread for the various Jellybean ROMs. Run by who, what's the aim, etc. Basically a quick reference guide to assist people (like me) decide which ROM fits my needs.
So far, these are the Jellybean builds that I know about for the TF101:
Team EOS 3 Jellybean nightlies
RaymanFX's 4.1.1 AOSP builds
CM10 preview edition
JellyBro (CM10 kang)
AOKP KANG
Let me know if you see anyone missing.
It would be nice for each ROM to have a a post which lists its key features:
Aim of the ROM. Tweaks, Stability, Speed, AOSP-like cleanness, etc
State. In active development, experimental, mature, stable, abondoned, etc.
ROM base, if any. Based on AOSP, AOKP, CM, etc.
Release-type/frequency: Nightly, interval, fixed releases, etc.
Non-stock/AOSP features. Swag, Toggles, Theming, OCing, etc.
Basically enough info to assist making a decision, without aiming for pages and pages of stuff which noone will ever bother to write (or read). See this post for an example of what I'm thinking about.
Feel free to recommend a non-default kernel for the ROM, but the focus should be on what the ROM itself offers out of the box.
Sounds good? Anyone wants to give it a go?
User summaries of the various ROMs.
I'm not guaranteeing that I will be able/willing to include all reviews here. If things get out of hand, I will edit this post to indicate so.
Team EOS 3 Jellybean nightlies:
2012.08.02: josteink
2012.08.02: fone_fanatic
RaymanFX's 4.1.1 AOSP builds:
None
CM10 preview edition:
None
JellyBro (CM10 kang):
None
AOKP KANG:
2012.08.02: K900
I've been meaning to make a thread like this, but I still have yet to find the time.
I read through all the JB threads about a week ago and Team Eos seemed to have the least amount of bugs so I chose it over the other options.
I'll start off by saying I've been using it daily since build #53 [2012-07-24] and I'm currently on build #54.
That said, here's what I've noticed so far:
Speaker volume is a bit low.
When using the HDMI out cable, sound plays via TF101 speakers, not TV speakers.
Video effects (Silly Faces) in Camera cause camera to crash.
GPS doesn't work.
Other than that, it's a very stable rom and working great. Dock functions 100%. Very responsive, stable and fast.
Also I'm using Guevor's JB Kernel 693. I just noticed 696 was released yesterday, so flashing that now .
Feel free to ask any questions about the rom. Maybe some time next week I can flash all the JB kernels out there and put them through their paces .
Note this rom is a GREAT daily driver, unless you really need GPS or use HDMI out very often, I highly recommend it.
I'm also running Team EOS nightlies and I'm very happy with it.
Here's my quick summary:
ROM: Team EOS nightlies
Non-stock/AOSP features.. Notification toggles. Overclocking. (Themes added in build #55?)
Aim...................... Stability
ROM base................. Team EOS
State.................... In active development
Release-type............. Nightly
Build(s) tested.......... 2012.07.23 to current (2012.08.01). With and without dock.
Not working / problems:
Audio generally low. (Seems to be a general JB problem across devices?)
HDMI audio out
Have encountered 2 sleeps of death while using it for around 2 weeks.
Everything else seems to be working.
My only complaint so far is lack of a status-bar battery-widget for the dock, like you have in Megatron (ICS). But I don't think any other of the JB ROMs available has that one either.
Great idea!
Will keep this thread under close observation :good:
CalvinH said:
Great idea!
Will keep this thread under close observation :good:
Click to expand...
Click to collapse
If you try any of these ROMs out, feel free to contribute
josteink said:
I'm also running Team EOS nightlies and I'm very happy with it.
Here's my quick summary:
ROM: Team EOS nightlies
Non-stock/AOSP features.. Notification toggles. Overclocking. (Themes added in build #55?)
Aim...................... Stability
ROM base................. Team EOS
State.................... In active development
Release-type............. Nightly
Build(s) tested.......... 2012.07.23 to current (2012.08.01). With and without dock.
Not working / problems:
Audio generally low. (Seems to be a general JB problem across devices?)
HDMI audio out
Have encountered 2 sleeps of death while using it for around 2 weeks.
Everything else seems to be working.
My only complaint so far is lack of a status-bar battery-widget for the dock, like you have in Megatron (ICS). But I don't think any other of the JB ROMs available has that one either.
Click to expand...
Click to collapse
Check out Dual Battery Widget from the play store. It has an option for having the dock battery level show in the status bar.
Also I'd like to add I haven't had a single SOD on Team Eos nightlies (been on since #53). But I have had a few reboots, all but 1 have occurred while not using the tablet.
Sent from my Transformer TF101 using xda premium
Officialzies for AOKP
Aim of the ROM. Tweaks, Stability, Speed, AOSP-like cleanness, etc
AOKP.
State. In active development, experimental, mature, stable, abondoned, etc.
In development.
ROM base, if any. Based on AOSP, AOKP, CM, etc.
AOKP.
Release-type/frequency: Nightly, interval, fixed releases, etc.
Frequent releases but no fixed timing.
Non-stock/AOSP features. Swag, Toggles, Theming, OCing, etc.
AOKP.
I've tried both AOSP build 3, and CM10 Kang.
I am eagerly awaiting a stable jellybean rom I can daily.
Using RaymanFX's 4.1.1 JB
Hi guys, thought I'd share this info. I'm using RaymanFX's ROM and overall it's running well. My only issue so far is that Google Now crashes right after launching. It was working before I started adding new apps, so I'm guessing there is a conflict with another app. Unfortunately I don't know which one it is. I'm guessing maybe gmail, Google maps, or Google +. I haven't tested the HDMI or used in the dock yet but WiFi and graphics seem good. The ROM itself is extremely lean, no bloat to speak of.
I had to flash the ROM a second time to get it working but it's possible that I goofed it up the first time because it does take a bit to do the initial boot and I was getting impatient and thought it locked up and rebooted.
I'll probably try the EOS ROM next.
Nonek said:
Team EOS nigthly.. Rayman has not updated this one in awhile and has been working on other projects. I'm not sure actually how good CM10 is, but I've run both this and TeamEOS and I changed to a TeamEOS / KAT 1.14 (now) combo and I have never looked back.. TeamEOS has the most fleshed out version of JB in my humble opinion.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
If just install the rom 0.7 from raymanfx. The first time from me i root my tf101 !
It work great, some small functionnality are missing on the keyboard but it gives a second life to our baby.
Sent from my Transformer(4.2.1 rom 0.7) using xda app-developers app
Yep, I' using 0.7 from Raymanfx also. Its great to have the mutli-user support, but I think it comes with significant overhead and I'm not sure the TF101 can handle this.... still testing and will keep everyone informed.
Hey there! I have a Galaxy Note 3 SM-N9005 (HLTEXX) and have noticed that since flashing a custom rom, (Carbon Rom) recorded video has very low audio.
I went back to stock 4.3 to test and recorded video sounded normal, the same as video recorded on my previous device, an i9300 running Carbon Rom.
I have tested on my HLTEXX with Temasek's Unofficial CM11, with and without Temasek kernel, Official CM11, with and without Temasek Kernel/ Lean Kernel and again with Carbon Rom with Temasek Kernel and Lean Kernel.
When using one of the mentioned kernels, I used Trickster Mod app to try and increase the Mic Gain for video camera.
With Temasek Kernel, as soon as I ticked to apply settings, they reverted back to default. With Lean Kernel, the values appeared to stick but as soon as video was recorded, the values had reverted back to default and recorded video was still quiet.
Does anyone have any ideas how to increase mic gain when recording video? Or is it simply a case of waiting for more kernel sources?
I would appreciate any input, bearing in mind I am just an enthusiast with a basic knowledge of flashing roms and customising my android devices!
Thanks in advance
I don't think anyone uses the camcorder besides us
sent from my note 3
954wrecker said:
I don't think anyone uses the camcorder besides us
sent from my note 3
Click to expand...
Click to collapse
Haha! No one seems to mention it and mostly my queries have gone unacknowledged, hence the post. But Carbon on G+ were very helpful, Matt went through some troubleshooting and let me test a modified media_profiles file, which increased the audio bit rate and made it stereo but the volume wasn't changed. The low volume is most noticeable when viewing the clips on a PC.
Tapatalked that shiznit.
954wrecker said:
I don't think anyone uses the camcorder besides us
sent from my note 3
Click to expand...
Click to collapse
Out of interest, did you come from 4.3 or 4.4 stock rom? I'm wondering if the bootloader would make any difference, but don't know enough about that sort of thing to be sure. I'm considering testing a 4.3 custom rom, then perhaps flashing a stock 4.4 and rooting/ flashing Carbon again, but there's no going back then!
Tapatalked that shiznit.
I'm on 4.4 I don't remember the sound on 4.3 to be honest
sent from my note 3
954wrecker said:
I'm on 4.4 I don't remember the sound on 4.3 to be honest
sent from my note 3
Click to expand...
Click to collapse
So you had 4.4 stock touchwizz before rooting and flashing a rom? Damn, I hoped that might make a difference!
Tapatalked that shiznit.
At least with you on 4.3 and me on 4.4 we know it's not that.
***I've got another issue that seems to either be just my phone or nobody else notices.
http://forum.xda-developers.com/showthread.php?t=2710421
sent from my note 3
scoobyjenkins said:
Hey there! I have a Galaxy Note 3 SM-N9005 (HLTEXX) and have noticed that since flashing a custom rom, (Carbon Rom) recorded video has very low audio.
I went back to stock 4.3 to test and recorded video sounded normal, the same as video recorded on my previous device, an i9300 running Carbon Rom.
I have tested on my HLTEXX with Temasek's Unofficial CM11, with and without Temasek kernel, Official CM11, with and without Temasek Kernel/ Lean Kernel and again with Carbon Rom with Temasek Kernel and Lean Kernel.
When using one of the mentioned kernels, I used Trickster Mod app to try and increase the Mic Gain for video camera.
With Temasek Kernel, as soon as I ticked to apply settings, they reverted back to default. With Lean Kernel, the values appeared to stick but as soon as video was recorded, the values had reverted back to default and recorded video was still quiet.
Does anyone have any ideas how to increase mic gain when recording video? Or is it simply a case of waiting for more kernel sources?
I would appreciate any input, bearing in mind I am just an enthusiast with a basic knowledge of flashing roms and customising my android devices!
Thanks in advance
Click to expand...
Click to collapse
I have the same problem as you when I switched to the Resurrection Remix AOKP rom. It made me switch back to Jedi elite kk touchwiz rom until they fix it.
954wrecker said:
***I've got another issue that seems to either be just my phone or nobody else notices.
http://forum.xda-developers.com/showthread.php?t=2710421
sent from my note 3
Click to expand...
Click to collapse
I don't seem to have that issue, but I'm in the uk with just 4g, no LTE (I thought they were the same thing!) But Bluetooth sometimes won't work for me, it's a bit temperamental.
Tapatalked that shiznit.
scoobyjenkins said:
I'm wondering if the bootloader would make any difference, but don't know enough about that sort of thing to be sure. I'm considering testing a 4.3 custom rom, then perhaps flashing a stock 4.4 and rooting/ flashing Carbon again, but there's no going back then!
Tapatalked that shiznit.
Click to expand...
Click to collapse
Monster audio cables are guaranteed to fix any sound issues that could be caused by your bootloader
CrashTestDroid said:
Monster audio cables are guaranteed to fix any sound issues that could be caused by your bootloader
Click to expand...
Click to collapse
Thanks, but am talking about the built in mics and gain provided by the OS.
Tapatalked that shiznit.
Anything new on the recorded audio issue? I skim all the threads and changelogs for all the different aosp ROMS but never see anyone even mention the issue other than the two of us.
sent from my note 3
954wrecker said:
Anything new on the recorded audio issue? I skim all the threads and changelogs for all the different aosp ROMS but never see anyone even mention the issue other than the two of us.
sent from my note 3
Click to expand...
Click to collapse
It's gone quiet but Matt said he'd mention it to kernel devs a little while back as he'd experienced it for himself.
Tapatalked that shiznit.
@954wrecker Have a look at Temasek's twitter for some excellent news! Not tested yet, but about to!
Tapatalked that shiznit.
Im looking maybe for script as mic volume is too low in calls.
Hey guys. I'm new to the world of Android (had a Nexus 5 since November, coming from BB and iPhone). I'm even newer to modding (unlocked/rooted/installed CM on my device 4 days ago), and I'm even newer than that to XDA (first post!) so I apologize if these questions either don't belong here or are a little naive.
I've been reading and viewing a lot of reviews on OmniROM and I'm thinking of installing it when my new device comes in this week (had to RMA due to pixel issues). For the last few days I decided to unlock/root/flash a ROM on my phone just to try it out. Based on what I've seen and read, I think OmniROM would meet my needs better than CM, so I think that's the direction I'm going to go.
One thing I want to improve about my phone's performance is battery life. I've noticed a slight improvement with CM, but not nearly the improvement others have noticed when using custom kernels, such as Franco Kernel. I know that Franco Kernel has some compatibility issues with CM, and I'm wondering if those issues exist with OmniROM? If Franco Kernel is NOT compatible with Omni, could you suggest other options to achieve the same or similar improvements to battery life?
Second question is with Swype keyboard. Swype worked great for the first day or so after installing CM, but lately I'm getting the "stopped working" dialogue box after every word I type. The keyboard doesn't go away, and I can keep typing, but I get that dialogue box after every. single. word. I have no idea if it's the rom that's causing it. I downloaded Swype off of Amazon when they had a free app giveaway, but there are no updates available there. IF the issues with Swype are linked to CM, will those same issues exist with Omni? Are there any solutions to this issue?
Thanks a lot!
No clue. Alternate kernels are NOT supported and no one on the team is going to endorse one. It might work, it might not, you will not be able to file bug reports if you're running a modified configuration.
I think that Franco will work normally. It doesn't work on CM 'cuz it's CAF ROM. As I know, Omni is not CAF based so Franco (btw for me ElementalX kernel fits better, take a look at it too) should work.