Related
We have had alot of activity over the last few days, what with the first 2.0 releases from the main players and now even some 2.1 builds. Which is excellent.
Maybe I am not 100% up to speed on the whole thing, but if AOSP 2.0 is "released" by google, then surely things like sync issues, etc shouldn't be in the source code?? I mean, the code should be as "bug free" as possible, so anything obvious like that would strike me as odd.
The reason I raise this point, is because I dislike the Rosie/SenseUI on my Hero, I would rather have the good, old Android standard like I had on my G1 - just what I prefer. However there are only beta versions of the AOSP eclair for Hero.
Would it be possible to build an AOSP eclair firmware, using the Qualcomm? proprietory drivers from someones leaked 2.1 image (working on an assumption that 2.1 has the same kernel base?) to produce a fully working Eclair 2.0 for Hero?
If I am way off the mark with this, please say, I'm just trying to think it through with the help of the people in the know.
Ditto. I am all for AOSP 2.0
richbayliss said:
Maybe I am not 100% up to speed on the whole thing, but if AOSP 2.0 is "released" by google, then surely things like sync issues, etc shouldn't be in the source code?? I mean, the code should be as "bug free" as possible, so anything obvious like that would strike me as odd
Click to expand...
Click to collapse
I think part of the "issue" is that whilst Google have release some 2.0 code to AOSP, it is not currently complete (see here). In addition, many of the Google apps (e.g. Gmail) are closed source, so you have to rely on prebuilt components which may, or may not, be compatible.
The long and short of it is that Lox is already doing what you are asking. The prerelease of HTC's 2.1 has possibly served as a distraction to the AOSP 2.0 build, but I'm sure once Google properly drops AOSP 2.1 code that work will be of direct relevance to the AOSP project.
Regards,
Dave
yeah exactly. just sit tight and wait for Lox_dev to finish his 2.1 Then he might look after the AOSP 2.0. and as AOSP 2.0 is running pretty fine without much hassle its fine if Lox takes some time before working on AOSP 2.0 . cheers
I'm with this idea!
I mean, just compare the 2.1 and 2.0 aosp videos; android 2.0 has much cleaner, and better transitions imo.
Design choices in 2.1 by HTC are, imo, bad as usual; the transparent notification drawer for example; what is the purpose? It's only jerky. And so on..
I suggest suspending judgement on HTC's 2.1 until they've actually released final code! Remember this is a leaked internal build - what ends up in the final ROM may be quite different.
Regards,
Dave
I think I have a clearer picture now, thanks guys.
I just wish that we could be in a scenario where we could flash a standard AOSP build onto our Hero's, sans the whole SenseUI, and have a basic usable phone.
I really dont get the whole "gmail is closed source" crap with Google. I mean, I can have Gmail on WinMo, S60, etc - but only on Android IF I have a license?? WTF! Crazy! Luckily, now that Gmail does support Exchange Activesync I don't need the standalone app anyway.
So the word on the street is wait.... which I guess is what we will have to do
I am keen to be able to build from source so I can start on a project I have in mind. Think along the lines of SenseUI, but a bit different.....
richbayliss said:
We have had alot of activity over the last few days, what with the first 2.0 releases from the main players and now even some 2.1 builds. Which is excellent.
Maybe I am not 100% up to speed on the whole thing, but if AOSP 2.0 is "released" by google, then surely things like sync issues, etc shouldn't be in the source code?? I mean, the code should be as "bug free" as possible, so anything obvious like that would strike me as odd.
The reason I raise this point, is because I dislike the Rosie/SenseUI on my Hero, I would rather have the good, old Android standard like I had on my G1 - just what I prefer. However there are only beta versions of the AOSP eclair for Hero.
Would it be possible to build an AOSP eclair firmware, using the Qualcomm? proprietory drivers from someones leaked 2.1 image (working on an assumption that 2.1 has the same kernel base?) to produce a fully working Eclair 2.0 for Hero?
If I am way off the mark with this, please say, I'm just trying to think it through with the help of the people in the know.
Click to expand...
Click to collapse
Forgive me if I'm missing the point, but we already have a fully working AOSP Eclair image for the HTC Hero. I've been using it for over a week, on a daily basis and other than the looping sync issue (which we are working on) it works fantastic..
jnwhiteh said:
Forgive me if I'm missing the point, but we already have a fully working AOSP Eclair image for the HTC Hero. I've been using it for over a week, on a daily basis and other than the looping sync issue (which we are working on) it works fantastic..
Click to expand...
Click to collapse
I wasn't aware that all issues apart from the syncing were fixed. I thought we still had issues with camera stability etc?? Is this not the case??
There are some minor issues with stability, but it's absolutely useable on a daily basis. I guess it would be better for you to list what your problems are or concerns, rather than making (what appears to me) to be a grand claim for concentrated work on something.
There are a number of us who are solely focused on getting AOSP Eclair working 100%.. but we're very nearly there. Having people contribute constructive information about what doesn't work would be the best.
jnwhiteh said:
There are some minor issues with stability, but it's absolutely useable on a daily basis. I guess it would be better for you to list what your problems are or concerns, rather than making (what appears to me) to be a grand claim for concentrated work on something.
There are a number of us who are solely focused on getting AOSP Eclair working 100%.. but we're very nearly there. Having people contribute constructive information about what doesn't work would be the best.
Click to expand...
Click to collapse
Believe me, I'll come back to AOSP soon with great things
That's an awesome news ! Thank you Lox !
Lox_Dev said:
Believe me, I'll come back to AOSP soon with great things
Click to expand...
Click to collapse
Thanks Lox, appreciated.
Lox_Dev said:
Believe me, I'll come back to AOSP soon with great things
Click to expand...
Click to collapse
Great news man! Thanks a lot! Holding my breath...
jnwhiteh said:
There are some minor issues with stability, but it's absolutely useable on a daily basis. I guess it would be better for you to list what your problems are or concerns, rather than making (what appears to me) to be a grand claim for concentrated work on something.
There are a number of us who are solely focused on getting AOSP Eclair working 100%.. but we're very nearly there. Having people contribute constructive information about what doesn't work would be the best.
Click to expand...
Click to collapse
I agree. The only reason I am now using Lox_devs Hero 2.1 1.4 instead of the pure Eclair one is that Eclair does not sync my exchange calendar. I just cant see why the calendar has been left out.
FroydVillain 1.3/2.x roadmap
EDIT: Due to unforeseen issues rapidly accelerating the release of 1.3 (more framework changes), I'll edit this roadmap to reflect 1.4 as well as what we hope to accomplish depending on how many of the 1.3 promised features make it into the accelerated release. Thanks for your patience.
Now that FroydVillain 1.2.x is somewhat stable we can concentrate on the next releases.
First, any and all "WHENNNNNNNNNNN???????!!!!!111oneeleven" posts will be ignored. As usual, "when" = "when it's done".
Features/items in this roadmap are things you can definitely look forward to unless otherwise stated, ie, something happens that renders that feature impossible. Like an asteroid hitting my house, for example.
First, the preliminary work.
I promised the guys over at Cyanogenmod that my new build profile for the Hero (and other MSM7xxA based phones, so the Dream, Slide, G1, etc etc) will be tidied up and offered up in a pull request. I will be cleaning up my tree and submitting my changes before I begin work on the next release of FroydVillain. The main reason for this being, the closer the CM tree is to my tree, the less work involved in keeping the FroydVillain tree up to date with upstream fixes.
Right, so the changes.
Version 1.3.x:
Obviously it is customary to break some **** with each major revision just to give me an excuse to release another release after that broken release.
So for 1.3.0 I nominate, umm...nah I'll let you find out. A release post isn't complete without at least 20 posts asking if anyone is having xxxxx problem and a further 20 posts complaining about the said problem after I post that we're aware and we're very sorry and those responsible shall be flogged.
FroydVillain 1.3.x:
Further changes to the build base and source code to move Froyo-on-Hero further away from reliance upon Eclair libraries. We aim to be building a native libcamera.so in the same vein as the D/S guys are. This combined with already eliminating proprietary liblights makes it easier to...
Switch over to the Froyo prelink map. If you don't know what prelinking is, don't ask. Either don't worry about it or do some Googling. The upshot for you the end user should be better stability and maybe even some added performance improvements.
Along with the addition of the CPU profile to the CM base I'm hoping to get VFP support fixed in the kernel and in the dalvik source. VFP is your phone's ability to offload number crunching to a dedicated number crunch piece of hardware. The cpu the Hero has supports it, however support for VFP on ArmV6 architecture is a bit...well, pants. Accomplishing this should also give another measurable boost in dalvik performance since currently the only enhancement to dalvik, is the optimised binary, the source itself still trudges along with only armv5te support which again rather pants.
Giant /data partition. Thanks Maxisma and co. I'm not going to bring this in until we next need to do a wipe, ie, 1.3 since it resizes the mtd partitions. Coupled with old school apps2sd there should never be a single whine about space on /data ever again. Even dkelley could fit all of his dalvik cache data on it with his encyclopaedic collection of apps. Be aware this will be accompanied by an updated recovery.img so the different layout is supported. You have been warned.
Debugged Exchange support. I can't promise that this will appear in a 1.2.x update but I will get it in for 1.3. I don't use Exchange and so have to rely on others to help find the cause of the issue, debug it and test it. I can't believe after nearly 10 years dodging it, I'm back troubleshooting Exchange bollocks again.
Theme revival. Because Google were kind enough to provide no theming engine what so f**king ever (cheers lads) theming is a pain in the behind that involves hacking the framework. However because we now build from source rather than trying to crowbar bits in and out of a prebuilt HTC tree, it's significantly easier to produce themes from the newly built source tree. I'm working with Alex24 on a project to go with 1.3.x which will put Themes back into the OTA app and they'll be available at the same time as the new releases are. This also allows us to easily add more themes over time.
CMSettings/CMParts. After having a chat with the folks at Cyanogenmod they're more than happy for me to make the menu entry in settings feel more at home within FroydVillain instead of looking like a kicking and screaming rip off from the Cyanogenmod ROM itself. So those of you that have been hopping up and down for CMSettings functionality, it's coming.
Better GPS functionality/better radio functionality overall. For various reasons, changes made by Google, the fact we'll never have official "Froyo supporting" radios, bugs creep into the OS when it comes to using newer Google based apps that make use of the radio. We'll have some fixes for the slow GPS locking and the random reboot/crash when looking for a GPS signal. We're hoping we have mobile data+gps properly nailed down as well.
We're also going to look into different Gallery implementations. Gallery 3D is annoying as hell and the bugs with it are likely due to us relying on the Eclair GL libs. So no further ground is likely to be made until/if/when another MSM7xxA class phone gets Froyo which if any will likely be the Legend. That's a big if though. Imagine if you will, 50 metre tall letters I and F, draped in neon coating with a flashing, strobing sign above them announcing "THIS IS A BIG IF." But no whining if the best you get is the old 2D Gallery as I'm really struggling to find any decent Gallery implementation. Which is somewhat surprising. Perhaps we should offer a bounty for a new decent one.
Add further language support
That's all for 1.3.x for now I think. I'll update this as new things occur or as things appear to be impossible.
FroydVillain 2.x:
Kernel 2.6.34.
What? That's not enough? Wtf is wrong with you? Ok fine.
2.6.34 will provide official support for the newer Froyd features such as in built Tethering and no more annoying bull**** surrounding connecting a simple USB phone to a simple USB port on a simple Windows system. Apparently the Windows driver stack is easier to confuse than a 90 year old Alzheimers suffering dementia patient.
We'll also be looking to bring the Hero Froyo platform closer in line to the more complete Cyanogenmod D/S platform. There's really no reason why we shouldn't be able to especially once 2.6.34 is available since as far as the hardware is concerned the phones are practically identical.
More will be added to the 2.x branch as we discover it. Don't be surprised if in the course of working on 1.3.x some features get pushed back to the 2.x release due to practical limitations or it just making more sense.
Now is the time for feature requests from you the user. 1.2.x is now critical bugs only, I do not want to have to make you wipe/flash 1.2.x now until 1.3 hits so any fixes involving a framework rebuild won't appear until 2.x. 1.2.x is now considered feature complete in the scope of features we want to have supported. New features will appear in 1.3.x or 2.x depending on the work required to make them appear.
So the forum is now yours, dear users, to get those feature requests in. We'll endeavour to get as many implemented as we can. Any ridiculous or unobtainable goals will be identified as such as quickly as possible so people don't get their hopes up only for me to dash them like an abusive husband.
Thanks for all of the Froyo deliciousness you've provided us with! I myself will be waiting with baited breath for the next installments of Froyd.
p.s.
If you need more people with access to Exchange, or if you'd like an Exchange environment to play around with, let me know. I've got an Exchange 2010 machine sitting next to me.
Looking great! Hope you'll get that all working!
acolwill said:
Thanks for all of the Froyo deliciousness you've provided us with! I myself will be waiting with baited breath for the next installments of Froyd.
p.s.
If you need more people with access to Exchange, or if you'd like an Exchange environment to play around with, let me know. I've got an Exchange 2010 machine sitting next to me.
Click to expand...
Click to collapse
Ah, now that -would- be useful. [email protected] if you want to hit me up on GTalk.
maxisma said:
Looking great! Hope you'll get that all working!
Click to expand...
Click to collapse
Cheers bud! Check your PMs.
wow keep on the great work...
Flash? 10char
dpi295 said:
Flash? 10char
Click to expand...
Click to collapse
Impossible, it doesn't work on ARMv6 CPUs.
Ah, now that -would- be useful. [email protected] if you want to hit me up on GTalk.
Click to expand...
Click to collapse
Req sent. Gimme a nudge
dpi295 said:
Flash? 10char
Click to expand...
Click to collapse
Best we can do is see if we can hack over the Flash Lite stuff from Sense, but don't hold your breath.
In fact, you all should start a campaign and hammer the **** out of Adobe to provide an armv5te or armv6j version of the flash library. It's their fault, make them fix it.
Hacre said:
Best we can do is see if we can hack over the Flash Lite stuff from Sense, but don't hold your breath.
In fact, you all should start a campaign and hammer the **** out of Adobe to provide an armv5te or armv6j version of the flash library. It's their fault, make them fix it.
Click to expand...
Click to collapse
They won't do that, they aren't powerful enough..
I'd appreciate it if you would make an optional patch for people who want their phone unlocked by double clicking menu button.
Amazing work! Data Partition, Themes, VillainSettings... cant wait!
As for Feature Requests, +1 for a quick 2D Gallery
Nice post ninpo.
Thanks for your great ROM. I'd love to see better rtl language support in your ROM.
Really lame request, and probably easily fixed just by finding the pictures myself, but could you put all the nice wallpapers you had back into the releases?
It's obviously a very trivial request, but the wallpapers were always exceptional compared to my attempts of being sophisticated. I always ended up with either breasts or something Xbox related...
mobydeek said:
As for Feature Requests, +1 for a quick 2D Gallery
Click to expand...
Click to collapse
+1 for the standard 2D Gallery.
Tanks guys for your hard work.
Sent from my HTC Hero using Tapatalk
Woah, that's a lot of things to do, and some big ones too. Good luck on that, would be awesome to see these things done in the next months, though, take your time, no rush .
As for Feature-Requests: I only have one, and I don't have any idea if it's already done (I don't test many ROMs that often, I'll prefer to stay on my 2.1 Vanilla ROM ) or if it's even possible, so sorry for my Noobishness in advance. Now, I would love to be able to control the Music Player with the volume keys. Short presses change the volume, like before, and long presses skip the songs.
Screatch said:
I'd appreciate it if you would make an optional patch for people who want their phone unlocked by double clicking menu button.
Click to expand...
Click to collapse
Blue-K said:
Woah, that's a lot of things to do, and some big ones too. Good luck on that, would be awesome to see these things done in the next months, though, take your time, no rush .
As for Feature-Requests: I only have one, and I don't have any idea if it's already done (I don't test many ROMs that often, I'll prefer to stay on my 2.1 Vanilla ROM ) or if it's even possible, so sorry for my Noobishness in advance. Now, I would love to be able to control the Music Player with the volume keys. Short presses change the volume, like before, and long presses skip the songs.
Click to expand...
Click to collapse
We'll be putting a modified CMSettings back into FroydVillain in 1.3, so these features will be there automaticallymagically.
Yeah, it's a fair bit of work, but with HTC pretty much ditching the Hero we can take the project and make sure it's all done and done right.
There's collaboration with other developers on other projects for a lot of this, it's not just me or Team Villain making it all happen. I'll be pushing the fixed cpuprofile up to cyanogenmod and they can then work on it too, I'm working with Elemag on the 2.6.34 port, Maxisma brought the repartitioning stuff to everyone's attention for the Hero, etc. Proper open source development at its best.
It's well worth it too. Look how different the Hero runs with FroydVillain 1.2.1, I'm quite frankly disgusted that HTC never, ever, tapped all that potential.
I can't believe it, my hero will never die!
This is indeed great news and I can't wait!
I just wanna thank everyone involved, all the developers are doing a fantastic job bringing us things i never thought was possible on the hero, and I totally agree Hacre, it's a real shame that HTC ditched ther hero when there's still juice left in it!
Cheers!
e2zippo said:
I can't believe it, my hero will never die!
This is indeed great news and I can't wait!
I just wanna thank everyone involved, all the developers are doing a fantastic job bringing us things i never thought was possible on the hero, and I totally agree Hacre, it's a real shame that HTC ditched ther hero when there's still juice left in it!
Cheers!
Click to expand...
Click to collapse
Not to mention juice they never, ever bloody gave us. Grr.
does anyone know, or have a reason, or encounted in a problem with CM 10.1 cuz i recently installed CM 10.1 stable on my ATT S3 and it keeps restarting itself after 20/30 minutes tops, maybe longer but once in a while it randomly restarts itself
installed everything perfectly, no reason to be acting crazy since its from CYANOGENMOD TEAM but ROMS are not perfect or as good as STOCK ROMS (that come pre-installed on your device)
any issues, bugs, any kind of thing you have noticed with cm 10.1 yu can post it here
new upcoming features, fixes, what should be there or shouldnt be there, whats missing everything
HELPING EACH OTHER SOLVE SIMPLE/SERIOUS with CM 10.1 and above ISSUES
am currently running Synergy ROM 4.1.2 Stock rom with ZIGGY KERNEL (clocked at 1.3 Ghz) and its pretty sweet, stable, good battery, perfomance is top notch for a stock based rom that come with all samsung boatload
SO DUMP ALL THE PROBLEMS/SOLUTIONS IN THIS NEW THREAD FOR CM 10.1 AND ABOVE - ATT S3 I747
ANYTHING YU THINK IS COOL/AWSOME ABUT CM 10.1 ON YOUR AWSOME S3 GET IT HERE
Or just post them in this thread which already gets developer support.
http://forum.xda-developers.com/showthread.php?t=1778270
Not all phones are created equal. You should try the newer nightlies since they're just as stable. I haven't had any issues with Cyanogenmod. The reboot bug has been squashed a couple of months ago for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
Or just post them in this thread which already gets developer support.
http://forum.xda-developers.com/showthread.php?t=1778270
Not all phones are created equal. You should try the newer nightlies since they're just as stable. I haven't had any issues with Cyanogenmod. The reboot bug has been squashed a couple of months ago for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
thanks for that, but this thread is based on everything to do with cyanogenmod 10.1 and above, clearly i am not a fan of nightlies as to do with updating my phone every second (thats a hustle for me cuz i gotta backup everything/reinstall everything again) and not to mention i have better things to do than just updating to a new bulds everyday or trying new roms
ihave too much variable things on my phone to delete for reasons like nightlies
THE REBOOT BUG STILL exists quite suprisingly for me as you dont have problems with nightlies or the reboot bug too
the thread yu mentioned is helpful but new ideas, new thoughts, easy to find a solution for a problem/question and navigate easly without having to dig it up tens of pages, a new thread with new people/same but fast replies, nice to workaround with.
am not trying to break any XDA rules/regulations or whatsoever by posting/asking a question or starting a thread thats already there(content and information that i need) but a new thread thats clean, new ideas about the rom, new problems/solutions is what this thread is all about
PHONES COULD BE EQAUL BUT ROMS ARE NOT SAME/DONT WORK SAME ON XXXXX PHONE
winosxbuntu said:
thanks for that, but this thread is based on everything to do with cyanogenmod 10.1 and above, clearly i am not a fan of nightlies as to do with updating my phone every second (thats a hustle for me cuz i gotta backup everything/reinstall everything again) and not to mention i have better things to do than just updating to a new bulds everyday or trying new roms
ihave too much variable things on my phone to delete for reasons like nightlies
THE REBOOT BUG STILL exists quite suprisingly for me as you dont have problems with nightlies or the reboot bug too
the thread yu mentioned is helpful but new ideas, new thoughts, easy to find a solution for a problem/question and navigate easly without having to dig it up tens of pages, a new thread with new people/same but fast replies, nice to workaround with.
am not trying to break any XDA rules/regulations or whatsoever by posting/asking a question or starting a thread thats already there(content and information that i need) but a new thread thats clean, new ideas about the rom, new problems/solutions is what this thread is all about
PHONES COULD BE EQAUL BUT ROMS ARE NOT SAME/DONT WORK SAME ON XXXXX PHONE
Click to expand...
Click to collapse
First and foremost, no OS or software, including android, is perfect. Secondly starting a new thread does not mean it will not get "cluttered" either. The ROM thread for CM is not as bad as you make it out to be. The idea is that the newest material covers the most recent nightlies. It is not that difficult to go to the end and work backwards. In regards to you random reboots, look on JIRA as it exists for this very reason. Take a logcat and report on JIRA if not already covered. JIRA gives you all the bugs reported and their current status towards a fix. This is a wasted thread for this very reason.
As far as ROMs being different...that is the point. Each developer(s) put their own spin on it. That is what makes these development threads so great. You can look for a ROM that you like best. Some ROMs are more universal (but you still need your device specific version), such as CM, while others are device specific.
And phones are not created equal. They may look the same, have the same hardware specs, and all else seemingly equal, but slight manufacturing imperfections make them different. Two people can have the exact same phone from the same carrier, manufactured on the same day, but due to some ever so slight differences from imperfections, ROMs will work differently on each. For instance, in your case CM reboots randomly. For others, such as myself, this is no longer an issue. However, it is possible that another ROM will work great on your phone but not on mine.
While you say CM is not perfect like the stock rom, the stock rom is not perfect either. I have AT&T and the stock rom has several issues. The lockscreen securities can be bypassed, the alarm likes to not work at random times (software bug), and every now and then I get a battery plummet after a phone call when the phone switches between 4G and 4G LTE. Others may or may not have these issues but they seem to be rather common (the security bypass affects all S3 phones that were on 4.1.1 that I am aware of). For this reason I stick to custom roms because I do not have these problems which I personally view as severe for me (Aside from protecting my data and enjoying battery life, I rely on my phone as an alarm clock). Now that 4.2.2 has come as far as it has, it is stable enough that I can use it as a daily driver. I knowingly accept any bugs that are there because typically the ones that exist do not have a large affect on me, if at all, unlike the stock rom.
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.
I'm seeing lot's of posts about LE2123, LE2120, LE2125 being upgraded to android 12, with lots of people experiencing issues with unstable phones. Please humour me by answering this simple poll.
I would wait a while before updating. 12 has been a bomb and 11 isn't much better across all device manufacturers. No easy fixes.
Let Mikey try it...
You might get more useful info with a poll asking whether people experienced issues. After following several threads across various sites, I'm convinced that only a small minority have actually experienced "issues" (as in, something legit broken). The other vocal folks are just complaining that a feature was removed or changed and they don't like it. It's no different than every other major release.
Every major version is going to be a bit different from the previous one (that's the whole point of the new version number), and there's always a small risk and a small percentage of people who experience issues (which are almost always resolved by a wipe or clean flash). That's why OP tells you to back up your data before upgrading.
I updated to A12 and I am able to see some differences.
1. I've got 5g, volte and vowifi finally (5g on scnd SIM slot)
2. DPI is messed up in certain apps and options.
3. Battery life is worse (but I've been using stock kernel on A11, so this could make a difference)
4. I like A12s way to grant permissions.
Was it worth update? If you like your phone up to date - yes. If you care about system stability and look, stick with A11 until fixed A12 shows up.
It's not a coincidence that OP suspended A12 update. They see it was not ready.
My phone is OP 9 pro EU version. Did wipe it after update.
OnePlus is pulling its OxygenOS 12 update for the OP 9 and 9 Pro
Hopefully a bug-free release will be out soon
www.androidpolice.com
Smedslund said:
OnePlus is pulling its OxygenOS 12 update for the OP 9 and 9 Pro
Hopefully a bug-free release will be out soon
www.androidpolice.com
Click to expand...
Click to collapse
Good thing they pulled it before our OnePlus9Pro forum blew up!
I have the le2123 and I have encountered so many bugs. I did a wipe data and now all seems to make sense.
Now I'm pretty happy with this update. Let's see the battery in the next days.
davyleggend said:
I have the le2123 and I have encountered so many bugs. I did a wipe data and now all seems to make sense.
Now I'm pretty happy with this update. Let's see the battery in the next days.
Click to expand...
Click to collapse
Nice to hear, did they deliver on the throttling?
AndyC76 said:
Nice to hear, did they deliver on the throttling?
Click to expand...
Click to collapse
I think yes? Found this option "high performance option" system always run at max performance.
When enable it an icon in the status bar appears but I think they forgot to change the style of the icon because it's a little oversized.
Apart from that after wipe no more glitched animation, more smoothness in all the operations, allarm clock work, icons and font now are ok and layout too (before i have mismatched dpi in various apps), keyboard now have the button for pull down (before there isn't). The only thing now it's Netflix on platstore, it say device not support.
Rooted with success with no problem, magisk hide works and installed Netflix with apk works too.