Hey all,
Any other guitarists here? Been using gstrings tuner app for awhile now and at some point between ICS updates it seems to have broken The microphone doesn't seem to detect the right frequency range for the notes anymore.
I think it worked at around FXP170 CM9, but that was ICS v4.0.3. My acer tablet still works fine with gstrings on 4.0.3, so not sure if it's a general android 4.0.4 problem, or a problem introduced with the CM9 tree. I'm currently running AOKP RC1.2 on my r800i, but prior to that I had the same problems on FXP119.
Going to try DoomKernel a bit later instead of KeiCSv2 to see if that makes any difference
Just tried the DoomKernel v2 listed in the AOKplay thread, that doesn't make any difference
Related
I decided to experiment with the phone and made the following modifications:
ZYGOT3 1.3 AOSP 4.0.3 ROM
4.0.3 Radio
Apex Kernal V3 IML74K
It seemed switching to a 4.0.3 ROM & updating to the 4.0.3 radio made some decent fixes to my signal strength + increased my DL speeds.
As for "overheating", I used Apex & over locked to 1350MHz but then under volted to 1125mV. Upon doing so, went back to doing some gaming & noticed both slightly increased performance as well as found the phone was no longer getting hot.
I'm not sure how this site is with external links(rootzwiki) but I went to the Galaxy Nexus development forum and found the items there.
[EDIT] This was done on an LTE Nexus in case anyone asks.
does this mean those issues can be fixed with an official android update?
hnakhi said:
does this mean those issues can be fixed with an official android update?
Click to expand...
Click to collapse
most likely yes. although the over clocking / under volting wouldn't be part of that.
In my opinion one of the main flaws of the Android ICS OS the big audio playback latency - about 88 ms. This impacts negatively many applications that emulate musical instruments and the ones that do VOIP like Skype or Google Talk. For VOIP apps the audio lag also has a negative impact on acoustic echo cancellation - probably the most difficult feature to implement on an Android phone. In spite of many user protests and requests apparently Google has chosen not to do anything about it.
This is a similar thread to the one started by "Windows X":
http://forum.xda-developers.com/showthread.php?t=1621914
but the solution is applicable to the Google Galaxy Nexus GSM phone ( or with custom ROMs based on ICS 4.0.4 GSM (maguro))
The attached package should be used only by experienced users that can eventually restore their system to the original state. I tested it only on ICS 4.0.4 GSM phone build IMM76I (maguro). In this configuration it worked flawlessly as far as I could test it. Other successful testing reports coming for CM9 Nightly Builds, AOKP and rascream maguro ROMs.
The latency after aplying it should be about 20 ms - as reported by the "Caustic 2" app.
Change log:
Original package replaced by "lowlatsnd_inst.zip"
To restore to original state you may use "lowlatsnd_rest.zip" or other restore methods if necessary.
Status: stable
Note: applying this might reverse changes made in other mods.
consider submitting to AOSP once you're sure it's stable
Actually I think it is pretty stable, but I tested it only on my ICS 4.0.4 GSM phone build IMM76I.
vonVideo said:
Actually I think it is pretty stable, but I tested it only on my ICS 4.0.4 GSM phone build IMM76I.
Click to expand...
Click to collapse
Ill be trying on AOKP later today, but as its just a modified AOSP, I dont expect any issues. Nice find!
vonVideo said:
In my opinion one of the main flaws of the Android ICS OS the big audio playback latency - about 88 ms. This impacts negatively many applications that emulate musical instruments and the ones that do VOIP like Skype or Google Talk. For VOIP apps the audio lag also has a negative impact on acoustic echo cancellation - probably the most difficult feature to implement on an Android phone. In spite of many user protests and requests apparently Google has chosen not to do anything about it.
This is a similar thread to the one started by "Windows X":
http://forum.xda-developers.com/showthread.php?t=1621914
but the solution is applicable to the Google Galaxy Nexus GSM phone.
The attached package is in an experimental stage and should be used only by experienced programmers that can eventually restore their system to the original state. I tested it only on ICS 4.0.4 GSM phone build IMM76I.
The latency after aplying it should be about 20 ms - as reported by the "Caustic 2" app.
Click to expand...
Click to collapse
So that's why I have an echo on almost all of my phone calls and voip apps?
Is this a flashable zip or something you have to include before compiling?
It is a flashable zip.
The big audio playback latency is one of the reasons for echo cancellation poor performance.
I'm guessing it's possible to manually paste these files into the phone via some form of root explorer, right?
Since I'm new to the GN (had a Desire before), is it possible for you to create a flashable version of the stock files which will get replaced, as a precaution, please? Backing up and restoring takes quite a while (some minutes vs. a few seconds compared to a patch )
Edit: maybe I haven't noticed it, but I'm on 4.0.4 update 2 (forgot the exact build number - as I said, I'm new to the GN ) so... where exactly (or rather, how) can I spot the differences before and after applying the patches?
Actually I have included in the zip the original libraries too with the extension ".orig" for ICS 4.0.4
They may work on 4.0.2 too, but I did not test them. You can copy your original libraries for example in /data/local/tmp/ and restore them later if you need by mounting system rw...
Tested this on the Modaco ROM ..
Seems to break system sounds. Music doesnt play anymore.
Phone calls still work though...
Caustic 2 does say 20ms latency..
going back to stock for now but sure deserves attention..
Unfortunately I don't know the Modaco ROM. On ICS 4.0.4 it works flawlessly with any sound source I tested so far.
So this should work on rascream ROM then? (AOSP from source with very few color changes...basically stock)
Sent from my Galaxy Nexus using xda premium
Would someone be kind enough to graciously tell us if this made a difference (and what other bugs they've noticed) with their ROMs and device performance? Not that I'm scared or anything, but I'd like to be aware of what I'm trying to spot the difference in.
Seems to work fine with newest AOKP. Thanks!
If rascream ROM is AOSP with very few color changes then this should work in the maguro version.
This sure sounds a very interesting project. I hope you get lots of feedback and continue to work on that. Unfortunately, I haven't noticed that lag you are talking about. Most probably my ear isn't trained to spot it. How could I reproduce it, so that I would notice the difference before and after?
Thanks
The lag is very easy to notice in a Skype of Google Talk call for example.
Also, you may try apps like "Caustic 2" - hit the keyboard and notice a lag of the generated sound from the moment you tap the screen, or "DroiDrum"... you don't need a trained ear for that...
Works great on newest aokp! Thanks can definitely tell a difference in caustic especially before flashing this.....good job
Flashed this on rascream and all seems good.
Sent from my Galaxy Nexus using xda premium
vonVideo said:
Unfortunately I don't know the Modaco ROM. On ICS 4.0.4 it works flawlessly with any sound source I tested so far.
Click to expand...
Click to collapse
yeah I wouldnt worry about Modaco..
its not a "full" 4.0.4 rom so thats probably why it didnt work for me..
quick question... would this increase battery usage, or has any of you testing this noticed something like that?
It might increase battery usage, but I didn't see any noticeable difference.
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.
Hey guys, I have been an AOKP user since long. Have been using their Milestone6 until they released Jellybean builds.
Must say I am purely satisfied with these builds but have a small problem with this...Right now I am on JB Build 4.
I am getting tabs in two rows if I change the dpi of my phone to 240 or lower than that. 260 works fine though.
This never used to happen in Milestone 6. I am a 240dpi user and loves to see everything in one screen, but these two row splitting is annoying.
It happens in all the apps based on HOLO UI like Phone, People, Boid(3rd Party), etc.
Attached are the screenshots to explain my problem.
I tried looking into build.prop as well, but didn't find out what's the problem. Before reporting to AOKP guys, I want to ensure if this can be solved and this is seriously a bug or not!
Please help.
P.S: Landscape view doesn't have any problem. The problem persist only in portrait mode. However, Milestone 6 based on ICS never had any of such problems. Also, I know AOKP JB builds are still in their preliminary stage but this problem is a small things which I think need to be reported!
Use 241.
No visible change in applications other than fixes.
Thanks alot
Sent from my Galaxy Nexus using xda app-developers app
Hi
I'm using AOKP Milestone[Stable] it's an awesome rom but after I play a game or watch a video (when the GPU is triggered i suppose) the rom goes crazy some parts of the system and apps become transparent respond to my touches but not displayed so i thought it's a kernel related problem so i flashed LuPuS kernel my favourite kernel but WiFi won't work even after flashing multiple modules
If anyone has a soloution for any of the two problems please provide it
Thanx
Lt18i-BB77
OppyNooby said:
Hi
I'm using AOKP Milestone[Stable] it's an awesome rom but after I play a game or watch a video (when the GPU is triggered i suppose) the rom goes crazy some parts of the system and apps become transparent respond to my touches but not displayed so i thought it's a kernel related problem so i flashed LuPuS kernel my favourite kernel but WiFi won't work even after flashing multiple modules
If anyone has a soloution for any of the two problems please provide it
Thanx
Lt18i-BB77
Click to expand...
Click to collapse
hey bro, may i advice you to change to LX CM11. CM9 is stone age & CM11 runs far more better. battery is like on stock or even better. its also fully stable. you will love it
thread: http://forum.xda-developers.com/showthread.php?t=2545354
Thnx for the advice
But the reason why im still using ICS/CM9 ROMS is that the sound of 4.1+ roms is not as good and loud as ICS ROMS if there is a solution for that problem it would be awesome
I tried AC!D MOD PimpUpMyRom Tweaks but i didn't feel a change (Maybe i didn't use them right)