Related
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 just ordered the 7. I will want to root it, but I have some questions.
Right now I have a rooted Nexus 4, and got a notice for a system update. I looked on CM and can only find nightlies for download.
I'd prefer the stable version. What are CM ROM are people downloading and how stable is it as a nightly? Is there another ROM that might be suitable for a plain jane reference library?
I see about the same for the 7 - No stable version, but a lot of people running some form of CM.
The camera, speed, removable battery and the SD card are the main reasons, plus the carrier (TMO) is switching 2G to LTE and upgrading a lot of other towers, so I will need LTE eventually.
I usually remove most of the entertainment, social apps and widgets. I have a fairly extensive information library - all apps purchased, and all with rather large databases. Every update seems to increase the memory used, so I'd love the extra. I also use the camera.
I also get rid of most of Google. The only Google app I need is Play Store. I don't socialize and do personal info like banking on the phone.
I also won't use the built in apps. I dislike widgets and prefer folders. Yes, I do need a smart phone to run these apps. I run ADW Launcher.
Right now the Nexus 4 is on Android 4.3 and I like it. I usually only update for security. How would I find an equivalent ROM and keep it?
I see differences in battery use and a few other areas.
I also see it is almost identical to the new LG in size - can I use a case for that phone? Like one poster, I want a holster case.
With the sound player - I didn't see the play specs. I assume it does do MP3, but how about AAC and MID?
Thanks
there are a lot of 3rd party ROMs that are stable enough, only have a few non threatening bugs to iron out. Depending on the ROM, it is pretty easy to stay updated with it as they usually have a built in update manager. Look in the 7a forum as most of the builds are unified across the 7a/7s.
The audio question you have is in regards to codecs, not hardware. I haven't personally played those file types, but you shouldn't have a problem.
opie546 said:
there are a lot of 3rd party ROMs that are stable enough, only have a few non threatening bugs to iron out. Depending on the ROM, it is pretty easy to stay updated with it as they usually have a built in update manager. Look in the 7a forum as most of the builds are unified across the 7a/7s.
The audio question you have is in regards to codecs, not hardware. I haven't personally played those file types, but you shouldn't have a problem.
Click to expand...
Click to collapse
So where is a unified sticky or post that discusses all ROMS? I do like CM. I'd like to read through it.
We're all here because we want better roms than what our phones came with, upgraded roms etc. Idealy we'd want the most stable version with the last junk so it's the most responsive. As I upgraded more and more roms, I started to feel that the phone is showing it's age in processing power, and just like computers, you can't just install a newer stronger OS on older hardware, at some point you aren't gaining performance, you start to lose it because the hardware is struggling to keep up. I went from stock to 4.2 roms, then 4.4 roms, (pacman, mokee, CM, etc etc ). I eventually went back to 4.4 stock and it gave me the least trouble and quite snappy. Of course it had the OEM bloat from Verizon. Its been going strong for maybe a year, and now it too is starting to crash with a lot of bugs, probably from installing so many apps, but also I see a lot of built in apps taking up memory. So my main question is, if you still the Razr M and still using roms, what have you settled with ? What has been the most stable and fastest for you so far? For me so far it turned out to be the stock 4.4.2. So my options are to start over again with a fresh 4.4.2 or maybe a stripped 4.4.2, or one of the new 5.1 builds. I mainly use it for Navigation + music + calls, generally nav + music at the same time. Someone mentioned that CM12.1 couldn't handle that because of memory issues so that scared me off, but I love the CM12.1 on my galaxy tab pro. I do use the Bluetooth when im riding, and the camera from time to time, and the stock just had everything working.
If I can't find a stable build/rom, it might be time for me to move on to a newer quad core 2ghz + phone, browsing on the razer m is ok, but admittedly a little slow. The battery isn't what it used to, but it still gets through the day, and there are (albeit dodgy quality ) replacement batteries on amazon to hold out longer... The phone was basically free over 2 years ago, I've never been one to shell out $300 for a phone, but that oneplus one is mighty tempting to switch carriers for. ATT failed me on signal at this house so Verizon has been great, but i'd be willing to try tmobile if im forced to pick a new phone.
TLDR: Which rom has been the most stable for you ? ( rom name and build/version ).
vo_danh said:
So my main question is, if you still the Razr M and still using roms, what have you settled with ? What has been the most stable and fastest for you so far?.
Click to expand...
Click to collapse
Stock 4.1.2 (with uninstalled bloatware), as 4.4.2 has broken audio on (some?) Rev.B phones.
I have been on stock jelly bean, rooted stock kitkat (debloated with permissions removed for batt life), cm12.1 (our device is just too limited) and now cm11 snapshot 12 on kitkat boot loader. So far cm11 is my favorite.
Sent from my DROID RAZR M using XDA Free mobile app
For me stock kitkat debloated runs smoother, although is very sluggish sometimes: for example when I'm swapping messenger, whatsapp and running music player at the same time, it's almost impossible...
Ice tested cm when was 5.0,and was terrible. Pac man Kk, not as good as stock.
Sorry for this ugly link, I'm on my phone, but this post and the thread overall has a lot of good tips:
http://forum.xda-developers.com/showpost.php?p=53724034&postcount=17
In the last 2 and a half years I've been through:
Stock 4.1.2 (rooted after 1 day, debloated, Safestrap)
Eclipse Rom v1.2 (Safestrap)
CM10.1 (Unlocked BL)
CM10.2 (Unlocked BL)
CM11 (Unlocked BL, JB Kernel)
Stock 4.4.2 (rooted, debloated)
CM11 (Unlocked BL, KK Kernel)
CM12.1 (Unlocked BL, KK Kernel)
Best user experience for me? Sad to say but I had it with the Stock 4.1.2: overall smoother than all the rest. Then after some months my Razr M started a bootloop, so I unlocked the bootloader and tryed the CM ROM: the CM Power Widgets were an overkill at the time (mainly the 2G/3G toggle)...
After all the CM ROM that I've used, the second place goes to CM11 (with JB BL).
Right now I'm testing the latest CM12.1 builds, and they seems ok. I've installed onlyt the apps that are strictly necessary to me (gmail, maps, onenote, osmand, dropbox, wikipedia, Room Toolbox Pro, SuperSu, calendar, meteo, etc...). Everithing seems fine but I liked more the old KK style (lockscreen, quick settings). Everything is working, even if sometimes the data, Wifi and GPS signals are erratic. The performance are acceptable too.
So far a vote for CM11, and stock unlocked debloated. That's what i was heading towards too, stock debloat, and probably 4.1 it still has the best performance really. I mean the custom roms look great and all, but at the cost of performance which, after the initial wow factor, I think we would all prefer performance. Back when I had my HTC my favorite and most stable rom was jacko's most basic slim version ( he had like 1-5 tiers of peformance and features ). If I go back to stock and it lasts me another year or two i'll take it.
I'm trying out CM11 Snapshot 12 right now. I was already on 4.4.2 stock with unlocked kk bootloader so it made sense to try it first. Its already a lot smoother than what it was, freeing up half the memory. I noticed the dialer doesn't go all the way up sometimes, you have to push back and hit the keypad icon again. Otherwise very smooth so far. I'll report back after I get some use out of it and if I ever decide to go back to 4.1. I might need a new battery though, if I'm using it it doesn't last through a day.
*Update - I went from having basically no free memory left to about 50% free memory. I think my battery life increased dramatically with so much less running in the background. Maybe by 20-50%.
I took one phone call and updated a few apps, about mid day through the work day. was 12h by the end of the day and a few calls and some browsing w/o having to charge. Definitely gave new life to the phone. Very minor dialer bugs, sometimes the number pad doesn't come up correctly the first time.
Android 4.1 has various security issues that won't be fixed anymore, so that's not really an option.
But I don't think there are big differences in battery life anyway (see this).
After testing a lot of CM11, using Performance settings, changing memory settings, having a very poor battery performance, I've come back to the 4.4 backup with all the apps I had. The difference was incredible, now my phone feels snappier than an iPhone, and sincerely, i don't know why!! I think that doing a restore sometimes can help a lot.
Yeah the last time I did a fresh install of 4.4.2 stock it was great. After a while though with all my apps installed + the oem bloat the phone had very little memory left and became sluggish. My best options right now seem like going back to stock, either 4.1 or 4.4 and trying to do manual debloat.
I did a fresh install of CM11 again but still didn't fix it. I still had the occasional dialer error and wifi would only work upon boot, after disabling, it never reconnects to any wifi. Battery was still horrible. I went back to stock 4.4.2. RSlite would not work on any version on windows 8.1 64 bit. I had to do msfastbootv2 and was able to restore to stock 4.4.2 However upon booting, it wanted to update to 183.84.15 but failing. It would say there's an update, download it, reboot, and automatically boot into recovery. I would select reboot and it boots in, sometimes saying update complete but it hasnt' actually updated anything. I eventually gave up and started over, this time using stock recovery, not logging into my google account so it doesn't start downloading all my apps, no supersu, no gapps, and it successfully updated to 183.81.15. At that point using mfastbootv2 I installed twrp 2.8.5, rebooted into recovery, installed gapps and supersu. Then used titan to debloat using http://forum.xda-developers.com/droid-razr-m/general/complete-debloat-list-droid-razr-m-t3045731 , removed most of the things on that list, particularly anything I didn't use that I saw running. I also installed Greenify. After about a day I started noticing the google play services issue using a majority of my battery. I downloaded App Ops to disable google play services wake permissions. I am amazed at what happened. I feel like I have the original batteries back. I received 2-3 short calls today, and 2 browsing sessions, installed some apps (facebook lite), and I still have a lot of battery left, normally it would be over half gone. Going home after that much use and still having over 70% of battery left is nothing short of amazing and I no longer feel like getting a new phone. I was very close to trying the Droid Turbo.
TLDR: Got original usage/battery back with stock 4.4.2 + debloat (backup & Uninstall with titanium ) + App ops to fix google services wake battery drain + Greenify. I don't know how much Greenify is doing, I attribute most of my gains from debloat + fixing the google services issue. Before App Ops you'd see a giant bar at the top of Google Services instead of screen.
Still odd you having WiFi issues. I don't I did learn recently that my Bluetooth does not seem to be fully functional.
Sent from my GT-P3110 using XDA Free mobile app
So far, all I've tried (and stuck with) are stock 4.1, stock 4.4.2, and CM 12/12.1.
Stock ROMs were fairly snappy, but I was always a little fearful (irrationally, but still) of trying to debloat while on 4.4 (and I remain fearful of downgrading the bootloader). This is my daily driver, though, and it must remain so until I become eligible for a newer phone in December (or I can pick up something better, used, for extremely cheap ...).
I have been toughing it out on CM 12 since late January. I like several of Lollipop's UI changes and new features (as well as CM's additions over stock), so despite some frustrations with bugs and somewhat-laggy performance, I haven't felt terribly compelled to try CM 11, or to go back to stock 4.4.2. (At least, not all the time; there have been moments of extremely slow response times where I've wanted to wipe /system right then and there and flash CM 11. I have stuck with 12 so far in hopes of improvements on the way to the first snapshot.)
Also, vo_danh, I was the one who reported about the issue with simultaneously running Maps and Play Music. I don't think I've ever gotten a phone call while trying to run those, but suffice to say that I have enough trouble with (occasional) lag when a call comes in.
If you're already on the kk boot loader like me, you don't need to downgrade the boot loader for cm11. Its been almost a week and i am still just amazed at how well this config is working for me. The battery life is like new again. Don't be afraid of debloating with titanium, since you can back it up first before unisntalling, if anything goes wrong, simply reinstall the backup. As a safety, after I restored to stock 4.4.2, updated to 183.84.15 OTA, I created a TWRP backup, so if anything goes wrong I can just restore it with TWRP instead of doing through all the steps to go back to stock. I didn't remove everything that was on that debloat list, just most things from verizon or anything I raw under 'running' list that I didn't need. It's so stable and fast. I would only move to a stock + debloat rom now for this phone for now. If I had a stronger phone there's no doubt i'd be using Cm12.1 but for now, this phone isn't meant to handle it smoothly and the wifi issues i had with Cm11 just make it not worth it. All wifi issues are gone now on stock. I didn't have wifi issues on any of the other roms either.
vo_danh said:
We're all here because we want better roms than what our phones came with...
Click to expand...
Click to collapse
1. One that the phone came with, with a little tweaking. 4.1.2 deodexed and debloated. Best usability and battery life. Slows down with heavy games tho so i unlocked the BL.
2. KK debloated. 4.4.2 i think. better in many respects but I sorely miss the Jb camera. It was wonderful. Battery life had come down a couple of notches.
3. Currently running the Bliss rom (5.1). My earpiece and mic doesn't work with the latest update. lol.
Edit: Call issues in the Bliss rom have been fixed. It's a solid rom and deserves a strong recommendation.
Hi folks,
I hope this isn't a faux pas. I understand we're not supposed to start religious wars about which ROM is the best. So let's not do that. But I could use some advice on the pros and cons of the different options open to me. Here is my situation and success criteria:
1. My T-Mo M919 is currently running an old SlimKat Android 4.4.4 from August 2014. I'm on the MDL bootloader and NB4 GSM modem at the moment. It's running mostly OK, with some camera freezes, some issues with battery drain when Bluetooth is on but not connected to a paired device or in use (wakelock prevents deep sleep... possibly app related?), and I've noticed the ATT Visual Voicemail app, when used to listen to a voicemail, kills subsequent phone call audio/microphone requiring reboot.
2. I've gotten used to Android 5.1(.1) on my tablet and I'd like to make the jump up to Lollipop on my phone, too. So I'm mostly looking at ROMs that are either 5.1 or 5.1.1. However, I'm considering as an outside contender just getting the OH3 firmware for the M919, doing the double flash to get me all the way there, then rooting and freezing Samsung crapware.
3. My criteria are: STABILITY. I don't need a lot of customization. I just want the thing to work. This includes being able to use the camera without it freezing, and being able to use my visual voicemail app without it nuking the phone function of the... uh... phone.
4. I use the phone mostly as an email / texting / forum-browsing device that a few times a week is actually used as a phone to make voice calls. I occasionally tether other devices to the phone's wifi. This needs to work without a hitch.
5. I use Bluetooth to pair with my car's audio system and I need that to be smooth. I recall in the KitKat days there were lots of complaints about glitch pairing/audio. My Slimkat has worked well with the car audio (a late model Toyota); no glitches. I want something that will have stable Bluetooth audio.
My current planned front-runner is the 5.1 GPE ROM by Danvdh. It seems quite stable from reading the thread.
Team Radium's ROM also looks promising.
On the AOSP side, the relatively pure AOSP recently posted by AntaresOne looks good. And I've run Dirty Unicorns before, in the 4.4 days before I moved to SlimKat. That was a good experience. And of course I hear the Slim folks are rebooting so SlimPop or whatever is an option.
I'd like any good direction, focused on stability rather than artwork or customizability, that will help me decide. Thanks!
Frankenscript said:
I'd like any good direction, focused on stability rather than artwork or customizability, that will help me decide. Thanks!
Click to expand...
Click to collapse
Honestly, if your focus is on stability rather than artwork/customizability, you're best off flashing back to stock, as pretty much every 5.1.1 ROM for the S4 is going to have a bug somewhere in it; even in the ones you've mentioned, there are bug complaints in their respective threads.
Sent from my SGH-M919 using XDA Free mobile app
This is definitely something I'm considering, but I'd really like to move to 5.1(.1), so I'm willing to give a ROM a try. It sucks that T-Mo never released Lollipop for the M919. I figure if I pick the most stable / settled-in Pop ROM, maybe it will work out. If not I'll drop back to stock 4.4.4 OH3, then freeze out the crap.
Info:
Target Device: SM-T560NU only (gtelwifiue)
OS: Android 6.0.1 Marshmallow
Variant: LineageOS 13.0
Status: Usable as daily driver, but still to be considered experimental
This project is a side project of mine to bring Lineage 13.0 back to the SM-T560NU.
I recently purchased one of these, and use a few apps that have not been updated in years. These apps do not work on Nougat, therefore I needed Marshmallow.
vince2678 had a great Lineage 13.0 build, but had started to shift his efforts towards the more popular and updated Android Nougat by the time that I got this tablet. vince had started to warn that he was going to be dropping Marshmallow to focus on Nougat.
Therefore, using his code base, and attempting to apply some more modern patches to keep Lineage 13.0 up to date, I started creating my own builds in private. There was one single, obsecure link to it, on my website, and it was discovered. Since the community has shown interest in this project, and vince has now officially dropped support for 13.0, I am willing to release my private builds.
Please keep in mind that while vince's builds were designed to be as stock as possible, my builds are tailored towards my needs.
They are not perfect, but they work for me. There are still some issues to be ironed out, and sometimes new issues sneak in when you think you are just building a security update
But, since you wanted them, here they are. At the time of this post there is only one, but this will grow over time, when I have spare time to try to fix any issues and apply security updates.
All builds use my optimized kernel.
Releases and known issues:
You can find my builds over at:
https://losupd.zefie.net/builds/full/?C=M;O=D
lineage-13.0_j199_20170720
Android Security Patch Level: July 1, 2017
USB MIDI Support (example video of controlling Logic Pro X with the SM-T560NU)
No changes to previous issues in this build (same issues apply)
lineage-13.0_j196_20170617
Android Security Patch Level: June 1, 2017
AudioFX is missing (disabled in build due to unsolved issue in ROM causing crashes)
Updater is untested. You may or may not get a notification when a new build is available.
Flashing the recovery that comes with these builds is advised against. It may work but is untested. Use my TWRP Build.
Device encryption does not yet work
There is a strange issue that prevents you from taking still images using the built-in camera app. Preview and video works. As a workaround, use any third party camera app. I suggest Open Camera.
Just flashed it, everything works great so far.
Ive tried and liked very much
Smooth and lightweight
So far for me the camera dont work but i can record video
Also the encrypt tablet option does not seem to work (I select the option in the security part of the settings screen, it restarts tablet and thats it)
Other than that it seems to be perfect
Thanks for all the hard work
Solidium said:
Ive tried and liked very much
Smooth and lightweight
So far for me the camera dont work but i can record video
Also the encrypt tablet option does not seem to work (I select the option in the security part of the settings screen, it restarts tablet and thats it)
Other than that it seems to be perfect
Thanks for all the hard work
Click to expand...
Click to collapse
I knew about the encryption but the camera issue is interesting and strange. I just tried it and see what you mean.
I will see what I can do about these issues in the next update, which will probably be mid-august.
Thanks for the report.
The issue seems to be with the Camera app itself, and not any issues with communicating with the hardware (despite the error message), since other camera apps appear to work fine.
In the mean time, if you would like to take still images with this build, I would suggest this great and free (ad free as well) camera app from the play store:
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
I have just tested it (with both rear and front cameras) and it can take still images.
560?
Is it compatible with T560 only ? Whats the difference between T560 and T560NU maybe US Market? or what the difference and where i can get a custom Recovery for the Tab?
bluedesire said:
Is it compatible with T560 only ? Whats the difference between T560 and T560NU maybe US Market? or what the difference and where i can get a custom Recovery for the Tab?
Click to expand...
Click to collapse
This is for the T560NU only, not T560. From what I know they have entirely different processors so there is no way for a universal ROM.
Thanks for this amazing rom. I noticed following: can't change the size of analog clock and sound on the speaker is not very strong.
jon355 said:
Thanks for this amazing rom. I noticed following: can't change the size of analog clock and sound on the speaker is not very strong.
Click to expand...
Click to collapse
The clock issue is likely upstream, since I can't think of anything I did that would prevent resizing of widgets, and other widgets appear to be resizable.
But I will look into it.
Speaker issue noted, there was some issue with the internal mic being too low that I tweaked, I may have to check the values for the speaker.
Edit: personal tests show speaker volume is fine. any louder could damage the speaker. if the volume is low, check that the tablet is not laying on a soft surface or something that would otherwise muffle the speaker in the back. When not obstructed, the speaker volume seems fine to me.
Any progress on Audio FX and Camera issues?
Jacsd said:
Any progress on Audio FX and Camera issues?
Click to expand...
Click to collapse
Unfortunately I have not had the time to work on this in a while. When I don't have time I just update the source and build (and hope it works) for the security updates. This only takes a couple of minutes as the build process does all the work. One should be coming in the next few weeks. Once the automated build finishes, I test it locally for about an hour and if its good, I release it.
I am not sure when I will have time to actually sit and go through the code to try to debug it to fix the outstanding issues. This can take hours or even days of dedicated time which I just don't have at the moment due to trying to keep my bills paid.
Stay tuned to this thread for updates though, and I apologize for the delay.
zefie said:
The clock issue is likely upstream, since I can't think of anything I did that would prevent resizing of widgets, and other widgets appear to be resizable.
But I will look into it.
Speaker issue noted, there was some issue with the internal mic being too low that I tweaked, I may have to check the values for the speaker.
Edit: personal tests show speaker volume is fine. any louder could damage the speaker. if the volume is low, check that the tablet is not laying on a soft surface or something that would otherwise muffle the speaker in the back. When not obstructed, the speaker volume seems fine to me.
Click to expand...
Click to collapse
After uninstalling 3rd party music app, volume is good again.
EDIT:
Unfortunately I am discontinuing this ROM. I made this ROM for my personal use, and it is no longer useful to me, and I do not have the time to debug it. Therefore, I am discontinuing it. The current builds and source will remain up, and if you guys are not having the issues I am having, and would like me to continue doing security updates, I will, so long as it still compiles without much work on my part.
There will be no updates to the existing issues though.
Despite my previous aversion to Android N, I would highly suggest vince's Lineage OS 14.1 builds. They have come a long way since I last tried them, and Android N isn't so bad after all
I haven't gotten a chance to do a logcat or anything, but I'm getting an instant bootloop after installing Nova Launcher.
It wasn't an issue until Nova updated a few weeks ago, and it affects both your builds. That's my favorite launcher, but I guess I can live without it
EDIT: I see that you're discontinuing this, so I guess this post is more of an FYI to other users.