[Q] SEAndroid Baked in to Custom ROM - Xoom Q&A, Help & Troubleshooting

Hi All!,
First, I'd like to thank all on TeamEOS for all of their hard work and dedication to keeping the XOOM alive and competetive with tablets 2 years newer.
Second, I must say I am impressed at the pace of your progress in moving from the ultra buggy wingray-158 release to the (mostly) stable wingray-160 release.
I am impressed with the changes to JB 4.2.1, and the promise it brings both in terms of features and Google's dedication to seriously competing in the tablet arena. I'm especially excited for truly enforceable permissions on an Android -- a feature that could bring security to the level of the iOS devices, and with well defined policies -- well past that level.
Finally, my question -- are there any plans to incorporate SEAndroid into the EOS 4 family of ROMs? If not, am I encouraged to fork the project into an SE-wingray-... And what would the steps be to coordinate this more completely?
Thanks again for all your hard work and help!!

Related

[Q] Question for OfficialViewsonic

In light of the fact that you are monitoring this forum, I have a question for you. You can see the incredible progress that the developers have achieved thus far with the various ROMs. While I have not tested all of them, it would appear that most of the custom ROMs run much faster, making better use of the hardware than the stock configuration, even with the recent updates. What I want to know is for the owner who chooses to keep his tablet stock, will Viewsonic release an update down the road that matches or exceeds the quality of the custom ROMs? If so, when?
Most of the custom ROMs have some operational glitches, and it seems to me as the manufacturer Viewsonic is really the one in the best position to put forth optimized software.
I see where Viewsonic says that the kernel will be released soon, but that does not absolve Viewsonic from it's obligation to turn out the best possible software for it's hardware, right?
I look forward to your response! Thanks again for participating here on the forum.

development dead?

now, i understand that development takes time, but given the potential of this tablet, i am somewhat dissapointed. i haven't really seen much progress past getting root, unlock, a recovery, a few roms based on stock, and one guy trying to port cm10. i guess what we are waiting for is the official jellybean upgrade before development picks up.
tweeklulz said:
now, i understand that development takes time, but given the potential of this tablet, i am somewhat dissapointed. i haven't really seen much progress past getting root, unlock, a recovery, a few roms based on stock, and one guy trying to port cm10. i guess what we are waiting for is the official jellybean upgrade before development picks up.
Click to expand...
Click to collapse
I feel you buddy, I'm coming from the Epic Touch forum that is very active in the development area. I too am disappointed with the lack of devs and ROMs for this tablet, but you have to realize its still fairly new and pretty expensive. I imagine most tablet devs would gravitate toward the Nexus 7 instead. Give it some time though, more will come.
Sent from my Samsung Galaxy S II Epic 4G Touch.
SuperSwagSauce said:
I feel you buddy, I'm coming from the Epic Touch forum that is very active in the development area. I too am disappointed with the lack of devs and ROMs for this tablet, but you have to realize its still fairly new and pretty expensive. I imagine most tablet devs would gravitate toward the Nexus 7 instead. Give it some time though, more will come.
Sent from my Samsung Galaxy S II Epic 4G Touch.
Click to expand...
Click to collapse
yeah, and they released this iteration way too soon (<6 months i think) for devs to leave their primes
I think a lot of the devs have sent theirs back. I'm kind of wishing I had with mine. Pretty disappointed with the device so far.
One of the AOKP devs is working on a port to the tf700, and judging by his twitter the only major things holding him back from a release are issues with Bluetooth and some visual glitches. Once we have that, roms should follow since we'll have a working AOSP base.
His twitter account is here:
www.twitter.com/_mrbirdman_
Actually to me, having custom ROMS on tablets is a little overrated. Root I can understand but seeing as I have owned the Xoom, Prime, and new the Infinity, must of the ROMS I have played with didn't add that much to the experience that stock already had. Outside of being able to use Sixaxis app, I have had little interest in rooting this Infinity. I think the wait for Jellybean is going to be with it.
Add in the fact that people are doing this on their free time, taking time away from their families, waiting a little bit won't hurt too bad.
SuperSwagSauce said:
I feel you buddy, I'm coming from the Epic Touch forum that is very active in the development area. I too am disappointed with the lack of devs and ROMs for this tablet, but you have to realize its still fairly new and pretty expensive. I imagine most tablet devs would gravitate toward the Nexus 7 instead. Give it some time though, more will come.
Sent from my Samsung Galaxy S II Epic 4G Touch.
Click to expand...
Click to collapse
and if you were in the e4gt forums from the beginning you will remember that it took several months for anything worth while to show up and how long for stable cm9? it took that forum quite a while to really get going.
legendary1022 said:
Actually to me, having custom ROMS on tablets is a little overrated. Root I can understand but seeing as I have owned the Xoom, Prime, and new the Infinity, must of the ROMS I have played with didn't add that much to the experience that stock already had. Outside of being able to use Sixaxis app, I have had little interest in rooting this Infinity. I think the wait for Jellybean is going to be with it.
Add in the fact that people are doing this on their free time, taking time away from their families, waiting a little bit won't hurt too bad.
Click to expand...
Click to collapse
Well to each their own, but to me, it's in custom development that you really begin to use the device to it's full potential. For instance, the OG Xoom has been literally given new life with EOS Jellybean builds. Yes, the Xoom wifi did get the JB OTA update, but stock JB is nowhere near as great as the EOS nightlies. They have tweaked it to capacity. The same will happen with the TF700 in time, I hope.
I also have the Nexus 7 and it's true that development has exploded for it, but honestly, it's a really limited device. For that reason, devs are in a performance competition...pushing things to the max. The TF700 though needs to be able to work really well...we'll need to be able to find the balance between high performance and stability. The fact that it's not really skinned is in its favor. It's not a Nexus device though and so some devs will not be interested in working with it.
Part of the problem in developing custom roms - which I have been doing for the Galaxy S 2/3 - is that currently you cannot decompile/recompile the SystemUI.apk file for the TF700T. XDA user iBotPeaches has taken over development of the apktool (tool to decompile/recompile APKs) project and is aware of the problem I and others are having. He is working to fix it.
As soon as it is fixed, I will be releasing a custom rom for the TF700T, but I need to make changes to the SystemUI.apk file. I can decompile/recompile the framework-res.apk file (have added CRT OFF effect already - and it works better than on my Galaxy S3).
So please have a little patience while the development tools are fixed and improved.
One other point to consider is that the Jelly Bean update is right around the corner, so putting much effort into modifying the current ICS version or actually making Jelly Bean work on the tablet is a waste of time.

What is CM doing??

As an avid flasher and big fan of 3rd party software (not a dev) I have to ask this.. what is CyanogenMod doing?
It seems to me like they are running on a treadmill going nowhere. The latest problems are with introducing this new kernel, taking stability back to the stone ages. All this time and we still have general bluetooth errors, random reboots, weak cell coverage (yes, I know it reports lower, but it's actually LOWER). So, I have to ask, with the upcoming release of Android 5.0, the Galaxy S4 and after 8 months of CM10.1 development, why don't they produce a stable product?
CM 10.1 is so freaking awesome! But it sometimes can't be a DD for me cause I need reliability. The last stable release was from Nov 2012. I really want to donate and cheer on the CM team, but it's hard to when I don't know what they're up to. Samsung's software sucks, and CM really delivers on overall user experience, if they could button up the quality and reliability I feel it would have a lot more adopters.
BTW, the latest nightly (31 Mar) is doing really well.
youre wrong on alot of levels here.
1. signal is the same for me as TW. compared to my mothers AND brothers stock S3 over the holiday weekend at various locations.
2. Ive only had ONE random reboot running AOSP. ONE. Thats over 5-6 months.
3. Feel free to develop your own ROM instead of crying. These people put hours into their work and do it for you to download their ROMS for FREE.
So you're not a Dev yet your crying about progress from the most popular Android rom?
Maybe you should learn to Dev yourself so you can satisfy your own needs.
Not going to be a productive thread

OFF TOPIC- CyanogenMod Now an Official Company!

Link to article is below.
"Amid the mad rush to buy new iPhones this week, Android was still in the headlines. Perhaps the biggest news was in regards to CyanogenMod (CM): The group behind the custom Android software is now an official company and may have its first hardware partner.
Not familiar with CM? Most mainstream Android device owners probably aren’t and they’re missing out. CM has long been a great software option for those that want what may be an even better version of Android than Android itself. The small group of developers behind CM have made their custom software available for at least four years. So why isn’t CM software on mainstream phones? Users need to have root access to their handset; something that most people have no idea how to gain, or even know about.
Still, in the overall market — particularly with Android enthusiasts — CM has a solid base: It’s estimated that more than 7.5 million Android phones run the software with its custom improvements over native Android. And why not when CM offers features such as performance boosts due to CPU overclocking, better custom theme options and support for FLAC audio files, to name a few.
CM raised $7 million in venture capital this week and one of the easiest ways it can boost usage of its software is to make it easier to install. That’s exactly what the new company plans to do. Instead of a multi-step process that requires a computer to install CM, the company is working on an app for the Google Play store that will do all of the hard work.
It would also help CM if phones were launched with its software and it appears that may happen next week. Oppo’s N1 could be the first handset partner for the young company. An announcement is planned for September 23 and based on a teaser video, it appears a version of the N1 will ship with CM pre-installed."
http://gigaom.com/2013/09/21/android-this-week-cyanogenmod-is-a-new-company-while-ol-hp-has-new-slates/
Looks like it's not all sunshine and rainbows.
https://plus.google.com/106978520009932034644/posts/L8FJkrcahPs
Yeah, I read about the corp thing a few days ago on Facebook.
Not sure how I feel about it.
What will it mean to all the awesome AOSP ROM's produced around here that are based off CM's code.
But, I do hope it means I'll eventually get to use an AOSP ROM with the APT-X bluetooth codec. It's the only thing CM doesn't have, that I really, really want.
Anyways, anytime a new company is formed, there will be moral mistakes made and also some pretty awesome things should happen. So give CM time to make and fix mistakes, and then get settled in as a company.

Cyanogen teams up with Microsoft to offer bundled apps and services...

Correct me if I'm wrong, but wasn't the point of flashing Cyanogen ROMs to get back to the AOSP experience and get rid of bloatware that many phone's came with?
Yet, now they are teaming up with Microsoft to add in even more bloatware. Which, if past experience with Microsoft holds true, will be extremely resource hogging and battery draining bloatware.
http://www.androidcentral.com/cyanogen-teams-microsoft-offer-bundled-apps-and-services
http://www.engadget.com/2015/04/16/microsoft-apps-cyanogen-android/?ncid=rss_truncated
Cyanogen used to be the go to. But ever since they stopped trying to perfect their ROMs for specific devices and started offering up half assed ROMs for every phone with broken features (i.e. Bluetooth streaming has been broken on official Cyanogen ROMs for Nexus devices, and probably others, since CM10), they've just fallen to the wayside.
Pair that with their new Microsoft partnership and I just can't help but wonder how Cyanogen veered so far from what got them started in the first place.
The partnership with Microsoft only focuses on Cyanogen OS and not CyanogenMod ROMs
Cyanogen OS is not CyanogenMod.....
http://www.xda-developers.com/cyanogen-announces-strategic-partnership-with-microsoft/
What does this mean for CyanogenMod?
This is an interesting question which needs answering keeping in mind our demographic audience. As the Cyanogen team has explained on previous occasions, Cyanogen OS is the commercialized version of CyanogenMod, the open sourced AOSP fork that we love here at XDA Developers. Microsoft’s partnership to bundle its services should not affect CyanogenMod, limiting itself to Cyanogen OS and phones released with it.
Update: Russell Holly over at Android Central has provided some more details regarding the deal. For starters, the bundled Microsoft Apps would be uninstallable in the truest sense. This gives back power to the end user on actually choosing the default apps installed on the device. While it is still adds some “extra bloatware” that a power user would need to rid off, the fact that it can be actually rid off is a welcome and appreciated move.
Update 2, 17th April 2015: As we mentioned in the article when we published it, CyanogenMod remains unaffected by the partnership of Cyanogen with Microsoft. This point has been pointed out again by the CyanogenMod team.
Click to expand...
Click to collapse
Everyone can breathe again, CM is safe from Micro$oft.

Categories

Resources