THIS WILL LIKELY KILL YOUR OUYA
We provide no warranty to the work here, it will likely cause your OUYA to die if you attempt it.
So myself and another fellow are working on bringing the latest and greatest Linux Kernel to the OUYA.
The good news: It boots to command line. The bad news: That's about all that works right now.
It's in an extremely unstable state right now, I actually managed to burn out the onboard ethernet chip trying to get the regulators right.
I2C causes random hard locks. Don't even ask about I2S. EMMC is detected, but we can't do anything with it yet. Haven't even tried getting video working yet.
If anyone would like to get involved, my repository resides at https://github.com/pgwipeout/linux/
Be warned, this is VERY MUCH a work in progress, don't expect clean commits, sanity in the code, or lack of dragons.
If anyone would like to get involved feel free to post here or use the Github page.
The goals are as follows:
Maintain this as close as possible to mainline, all changes to mainline will be posted as separate patches in the main git.
As much as possible is done through the device tree and kernel config.
Currently we have two patches applied, both are perspective in mainline so we may get lucky and not need them anymore.
Trusted-Foundations Patch: Necessary to get the L2 Cache Controller to work, this enabled secure monitor mode.
Tegra-Clock Patch: The Tegra3 has a lot of clocks that do necessary things, during init the drivers would reset these clocks causing hard locks.
I will post here periodically as we make progress.
/* EDIT: Update 2: The following is the current status of the project. */
I have made enough progress with this that I felt it was time to give an update.
I am sourcing this against Linux-Next, as there is a lot of work going into the Tegra video drivers right now.
Performance is good, though running off USB we get I/O bound extremely easily.
Currently it builds the kernel in about 50 minutes from a clean slate.
Working:
Boots with serial support.
Systemd and Sysvinit are supported.
Reboot works, poweroff does not.
Wifi and Ethernet both work.
Both RTCs.
USB
Four cores active, with L2 cache support.
In Progress:
eMMC support.
CPUFREQ driver support.
Video Support.
eMMC support is proving extremely tricky, we still don't have it talking.
It is currently precluding my first release candidate.
If anyone is interested in building this for themselves, leave me a message and I'll help you out.
Currently a TTL converter is necessary to use this.
The CPUFREQ driver I'm working on porting the T20 driver over.
Video support is hopeful.
UPDATE #1
It's ALIVE!
Working:
V4.14
Boots Reliably, use SysV-Init, Systemd boots, but locks up after a short period.
Onboard Lan
TPS power regulator
USB
Four cores active, fixed at 1 GHz until CPUFREQ is working.
L2 Cache Controller
In Progress:
RTC, both are readable, but writing doesn't work yet.
EMMC support
CPUFREQ (Maybe, not sure if we will ever get this fully working)
Video Support (A lot of experimental drivers and software going into this)
Moving to v4.16
To do:
Proper thermal support (fan is hardcoded on low speed right now)
Audio
Known issues:
Systemd locks up after being left idle
Systemd cannot do any power related functions
Sysvinit can reboot, but poweroff doesn't work yet
Good luck, will be keeping an eye on this !
Great initiative. Looking towards support of latest Android versions.
Ouya, is it rising again?
Question, would the development happening on the Switch in any way help your development? I wasn't quite sure if it was a joke or not but fail0verflow did say their exploit may very well work on the Ouya. So I'm not sure if being able to tap into the bootloader would help devleopments or not.
I'm just about to start my deeper linux learning myself and may be able to contribute after a while. fail0verflow/shofel2 on github for reference.
Short Answer: Yes and No.
Long Answer: The Switch is light years ahead of the Ouya in terms of the SOC, but there are similarities.
Any development on the Linux kernel for Tegra devices helps.
Unfortunately we likely won't be able to break into the Ouya the same way, since so few of the IO pins are actually utilized on the main board of the Ouya.
Most of the pins on the Ouya's T3 go nowhere.
That being said, we may get lucky, but the number of Ouya's out there to experiment with is much smaller than the number of Switches.
Currently I've gotten 4.16 to boot with good success.
4.17 does not currently boot, likely due to major changes that are occurring in the kernel.
Power management, cpufreq, audio, video, and wireless are still on the table though.
Power management I'm making progress with, sysvinit can do some functions including reboot, but systemd still locks up.
Cpufreq may be shelved indefinitely, I'm using this to learn kernel development and I do not have the skills to port this from the T2 or Nvidia's custom implementation.
Video will likely come with 4.17 or 4.18, a lot of staging work is going on right now.
Audio is slaved to video, so I haven't even tried yet.
Bluetooth and wireless might be a futile effort, as they are running proprietary blobs that do not play nice yet.
But as it is, it boots, USB and networking works, and it is running at 1 GHz on all four cores.
Update # 2 posted.
Very nice.
Keep it up. Let's revive Ouya
Release notice.
Alpha 0.10 release notification.
https://forum.xda-developers.com/ouya/development/kernel-linux-ouya-console-release-alpha-t3797996
I came across this wondering if there was a way to use any of my old Android devices (which includes my OUYA) as nodes in a Docker cluster, although that generally means using a custom kernel as Android's default has a lot of Docker-required features missing. It sounds like this isn't really in a place where that's possible yet, though, is that right? No eMMC = no disk, boots but then freezes, might overheat?
It frustrates me that I have old Android devices in general that have become useless with their ancient distros. I'd love to be able to do this sort of kernel work to help remedy that. @pgwipeout, how did you end up acquiring the know-how that you needed to make the progress that you have on this?
So I did get this pretty well working, though I haven't touched it in a while.
The work is continuing over at PostmarketOS, and their support is shaping up quite nicely as Dmitry's Tegra video driver matures.
The eMMC issues were resolved, and now with the embedded memory controller driver merged into ryang's kernel performance is darn good.
Just to compare performance, the RK3328 running mainline comes in a less than half of the performance of the T33 based Ouya.
Hey, You still work on this little computer ?
Hello ! I got my hands on a OUYADEVS and i'm looking foward to change the OS to make an operational embedded system. Do you have some updates on your created System ? Much appreciated !
Related
ALL SOURCE CAN BE FOUND HERE
Concerns about XDA rules:
We will never charge for our forum. Our forum is read only to anyone without registering... you must register to post. Getting downloads of the advertised kernels will be listed on both XDA and forum.savage-zen.org. Savaged-zen's download site will always be publicly accessible, and nothing we have will ever be closed source or have any fees. This meets XDA's rules.
Our team consists of 5 guys. (in order of Name(real name))
NyghtGT (Anthony) Website, Graphics
Bbedward (Brandon) Kernel
Jsseidel1 (Josh) ROM/Kernel
Luisrcastillo (Luis) Kernel
mwielgosz (Mike) ROM/nonSBC Builds
Credits
Cyanogen and team --> various code bits
toastcfh --> various commits from .35 version of CM-Kernel
#teamwin --> wimax drivers in kernel and HDMI changes in kernel for full HDMI mirror (using the HDMwIn app)
erasmus --> smartass gov
intersectRaven --> HAVS
ms79723 --> SBC Mod
Zen-Kernel team --> various modifications
If we forgot anyone or you think you should be added to credits please PM us
(credits are given to the dev's where we got some code from, may no be original designer)
Please visit http://mirror.savaged-zen.com for the download.
you can give the progress of the builds @ http://buildbot.savaged-zen.org/builders one there all green you will see them on the mirrors.
Changelog is listed on the homepage: http://www.savaged-zen.org/?page_id=57
We request that you look for updates on our forum. We will post links to download there, as well as updates to the changelog.
Keep note : We will still update OP title, and answer questions on XDA, but as we all have admin rights on the forum we dont have to depend on one person to keep updated, and it will also make it easier for us to create a WIKI
our forum is located at
http://forum.savaged-zen.org
Check out our homepage at http://www.savaged-zen.org
If you like our kernel and want to support us... donate (supports the homepage payments and then beer!!)
nonSBC Versions can be found here
SBC WARNING:The Savaged-Zen team takes no responsibly for any issues to your phone or battery, including but not limited to, battery derogation or failure. SBC has been rumored to have caused issues with battery's and claims have been made that it actually causes physical damage to your phone. It is the users responsibility to review any opinions or warnings about such claims, and by flashing kernels that include the SBC mod, the user is taking the responsibility for any issues or failures to their phone. Please research this Modification, review the code, and come to your own decision before using such modification.
reservedaaaaaaaaaa
Sweeeet! Bringing the inc out of the dark ages. We'll finally be on par with the nexus one and supersonic
Sent from my ADR6300 using XDA App
I'd love to test. Just PMed you
Just pm'd you. Im so excited!
Sent from my DROOOOOID Incredible using XDA App
running GB cm7... I will test it out!
Just responded to all the PMs, once a couple people report back i'll just make it available to the public
All i heard so far was that it booted, the first build i forgot the atmel touch screen driver, but the test2 build (the one i just sent out in the masses) includes it, so hopefully most everything works.
*EDIT*
Everyone who PM'd got a build, i'm going to wait to hear back before sending out anymore so please don't PM, if the results are good i'm going to update the OP with both test builds.
Didnt work for me. It splash looped for me.
Sent from my full_inc using XDA App
flashing now. will report back
did not work for me either, I got stuck at the incredible screen, pulled battery it got past that, the screen went black and then I noticed green/red/blue bars running vertical down my screen
dang, i was too late
I got it to boot but no touch capabilities
Updated the OP
The builds there fix the touch screen issue and probably the wifi and BT issues, although as a tendency in the newest bcm4329 drivers wifi sleep policy should probably be set to never
The people who can't boot I suspect cache/dalvik arent being wiped properly (depending on recovery, usually clockworkmod is the one with the issues). Other than that all I can think of is there's some difference between incredible and incrediblec (but i don't think it necessarily matters?)
Anyway, as I don't have an incredible i'm relying on the testers
bbedward said:
Updated the OP
The builds there fix the touch screen issue and probably the wifi and BT issues, although as a tendency in the newest bcm4329 drivers wifi sleep policy should probably be set to never
The people who can't boot I suspect cache/dalvik arent being wiped properly (depending on recovery, usually clockworkmod is the one with the issues). Other than that all I can think of is there's some difference between incredible and incrediblec (but i don't think it necessarily matters?)
Anyway, as I don't have an incredible i'm relying on the testers
Click to expand...
Click to collapse
I got a newer incredible with SLCD screen
Touchscreen works now, way to go! Now for things that don't work:
- Wifi attempts to turn on, but fails
- Bluetooth also attempts to turn on, but fails
- LED notification light doesn't seem to function for alerts, charging, or anything
Other things that work:
- GPS locks on in about 5 seconds (sitting inside of a house)
- 3G data
- Voice calls
- SMS/MMS
- Still camera
- Camcorder
- Battery charge counter
neur0tk said:
I got a newer incredible with SLCD screen
Click to expand...
Click to collapse
Could be just a missing driver then, should be easily rectified, i suspect the same with LEDs, and wifi is strange unless for some reason the module isn't probing, maybe the module goes in a different place for the incredible who knows
bbedward said:
Could be just a missing driver then, should be easily rectified, i suspect the same with LEDs, and wifi is strange unless for some reason the module isn't probing, maybe the module goes in a different place for the incredible who knows
Click to expand...
Click to collapse
Want me to modprobe for the wifi? I'll need the module name.
jonesh said:
Want me to modprobe for the wifi? I'll need the module name.
Click to expand...
Click to collapse
it's bcm4329, it's built and in there, unless something funky in the makefile is changed it should work fine.
bbedward said:
it's bcm4329, it's built and in there, unless something funky in the makefile is changed it should work fine.
Click to expand...
Click to collapse
$ su
# modprobe bcm4329
modprobe: chdir(2.6.37-Savaged-Zen-INC-0.0.1-alpha+): No such file or directory
#
Something else peculiar... I'm not sure if the phone's charging. I have it plugged into a wall outlet, and while the LED is not lit as reported before, my charge percentage is dropping. That said, the battery icon is displaying the 'animating' charge. Thoughts?
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
StoneRyno said:
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
Click to expand...
Click to collapse
Known issues are basically the camera and mic don't work, some folks have wifi issues and some don't... and some have issues with the audio acting up when waking from sleep... I myself am happy to say I don't have wifi or audio issues... but camera and mic are driver issues that may never get to work. All in all very stable though
Sent from my cm_tenderloin using Tapatalk 2
If camera and mic are the only problems then I see no reason not to give it a shot. I don't know if I would ever use them.I was concerned that it was missing core functionality making it something one wouldn't use as a daily OS and only switch over to it for test scenarios and then switch back. I have cm9 on my Samsung epic (the one with hw kb). Would the current latest nightly be the one to go with?
Just curious, why are the camera and mic drivers so difficult? I would have thought having them running on WebOS was at least some of the work. I guess porting said work to Android is a completely different ballgame.
I wonder if the wifi/audio issues are still being worked on tho? Or are those of us with those stuck with em forever?
The big thing for me was hardware video decoding. Alpha 1 fixed that for YouTube, and alpha 2 finished the fix for Netflix and others.
If you haven't already, check out the thread at rootzwiki.
I was using webOS by choice until CM9 came out. I switched to CM9, and have been using it as my daily driver since the very first Alpha. I never video chat, but if I wanted to I know I can just boot webOS.
Don't let people here tell you CM9 (or the Kangs thereof) are unstable. Some people continue to spew that we don't have a stable version of android purely because its called an alpha. I don't think it will graduate past alpha without camera/mic support, and that may never happen. Right now, without trying, I am sitting at 587 hours of up time on my TouchPad. I can't think of a better word to use than "stable."
Sent from my Galaxy S II (i777)
Known Issues that I can think of. I know some were mentioned above, but all in one place is good.
Broken, NO FIX:
1) No Microphone
2) No Camera
Partial Workarounds:
1) Audio gets noisy with screen off. Kinda workaround: Turn volume down, only happens at higher volume levels. Or set screen timeout longer/always on while playing audio. No complete fix.
2) Wi-Fi dies or doesn't reconnect. Some people never have a problem, others do. Workarounds: First, set WiFi to always on so it doesn't turn off with the screen. Second, try changing the channel on your router, or if you have 2.4ghz/5ghz switchable, try using the other. If Wi-Fi still dies, toggle it off and back on.
3) Some people report that if the TouchPad fully discharges to 0% they have trouble getting Android to charge properly. Others report that if you reboot the device with it plugged in, sometimes it won't charge. I've experienced neither problem, but the best advice is, charge before the device shuts off fully, and unplug the charger/usb while booting.
Broken, but Completely Fixable:
1) Random crashes. Install CPU Master and raise minimum CPU speed to 384 or 416 depending on which works for you, and crashes go away. Also, don't overclock too much.
Setup Issues:
1) DPI is at 160dpi stock. This works for most things, except a few tablet apps and games will not work properly. Setting DPI to 120dpi fixes everything, but the display quality is not ideal. 132dpi is ideal, but breaks the market after a day or two. Most people use 160dpi or 120dpi.
2) The default launcher, Trebuchet, is NOT compatible with the 4:3 aspect ratio of the TouchPad's screen if you use any DPI other than 160. Why something so easily fixable has not been fixed escapes me, but you will quickly find you need a new launcher. Go Launcher HD is one of a few that are very friendly to the TouchPad.
App Issues (not really issues but you probably want to know)
1) A few apps really, really, really are picky about the screen size and just won't scale right. (see Trebuchet notes above). One example is Politico HD - it forces 16:9 aspect ratio and thus gets cut off. Some apps simply refuse to run. Contacting the developers rarely works. This is probably less than 1% of the apps on the market, however.
2) Some developers simply are too strict on app compatibility on the market, and whitelist only select devices. Getting compatibility from these guys is a longshot. Best option is to install on another device, grab the APK or use Titanium Backup to move the app to the TouchPad.
3) Some games (notably Gameloft is the worst) enforce device compatibility checks within the program itself and it will refuse to run unless you masquerade as an approved device by hacking your build.prop... which is not normally recommended.
Did I miss anything anyone?
N4N (Neked 4 Nougat) I6/I5 Kernel for 710,715,810,815,817There's just nothing like good ol' stock. Everything just works. Even after 2 years they're still selling these Tabs. And they can still compete with newer ones. So on with the show!!!!
You flash this at your own risk. I'm am not responsible for anything that happens!!! There's the discaimer.
MAKE A FULL BACKUP IN TWRP!!!!!
These kernels modify your ROM. So you WILL NOT be able to FLASH/RESTORE the stock kernel only.
A kernel tuner (Synapse) is enabled for V2.0 only - Get Synapse from the Playstore
See post #2 for Synapse info and other stuffs
Install instructions:
You MUST HAVE TWRP installed to flash this!!
MAKE A FULL BACKUP IN TWRP!!!!! YOU HAVE BEEN WARNED!!!!!!!!!
Flash Kernel- it'll wipe cache, dalvic automatically,
Flash SU v2.82, https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Wipe cache and dalvic when SU asks,
Reboot
Profit!!
So whats in this thing?!
V2.0 Synapse enabled (You should use a tuner (Synapse recommended) for this one as that's all that was added) But will run fine without
All below plus
Under volting
Overclock-big 2.2Ghz LITTLE 1.6Ghz
Underclock-big 500Mhz LITTLE 200Mhz
HMP tweaks and tunables
KSM with tweaks
Enabled all stock govs
V1.3 All below plus
Patched to 108EOL
V1.2 All below plus - Pulled for random issues-Use V1, V1.1 or V1.3
Patched to 3.10.105
817 only has this version
V1.1 All below plus
Patched to 3.10.61
V1
4.9 UBERTC Toolchain
Screen Mirroring built in - Seems to only works with Samsung enabled TV's
CIFS
OTG
TCP's-Cubic is default. Reno, Westwood+ and HTCP added
CDROM support
XPAD game controller support
A few tweaks
Bugs
If you have Synapse installed , make all settings to stock and uninstall. It'll probably still give you a "System UI error". Just move on, and reboot after a couple minutes.
Source
https://github.com/engine95
Thanks to
@andyroidking - for the 715,815, and 810 boot.img's
Donations. Never expected, but much appreciated
@sebmue
@andyroidking
Downloads
V2.0 Synapse enabled and recommended
710-I6 - https://www.androidfilehost.com/?fid=673791459329065685
810-I6 - https://www.androidfilehost.com/?fid=962021903579496837
715-I6 - https://www.androidfilehost.com/?fid=745849072291693169
815-I5 - https://www.androidfilehost.com/?fid=889964283620770516
817-3CQE4 - https://www.androidfilehost.com/?fid=962021903579499361
V1.3
710-I6 - https://www.androidfilehost.com/?fid=889964283620768631
810-I6 - https://www.androidfilehost.com/?fid=745849072291691184
715-I6 - https://www.androidfilehost.com/?fid=962021903579494937
815-I5 - https://www.androidfilehost.com/?fid=962021903579494940
817-3CQE4 - https://www.androidfilehost.com/?fid=889964283620772774
V1.2 Only for 817
817-3CQE4 - https://www.androidfilehost.com/?fid=745849072291694892
V1.1
710-I6 - https://www.androidfilehost.com/?fid=962021903579492239
810-I6 - https://www.androidfilehost.com/?fid=745849072291688529
715-I6 - https://www.androidfilehost.com/?fid=817906626617946405
815-I5 - https://www.androidfilehost.com/?fid=889964283620765858
817w-3CQE4 - https://www.androidfilehost.com/?fid=673791459329067028
V1
710-I6 - https://www.androidfilehost.com/?fid=889964283620763792
810-I6 - https://www.androidfilehost.com/?fid=817906626617944296
715-I6 - https://www.androidfilehost.com/?fid=745849072291686448
815-I5 - https://www.androidfilehost.com/?fid=889964283620763794
I'm just not a fan of the DevDB format anymore. It's difficult to update and modify. So this is what you get.
SYNAPSE Kernel Tuner - Maybe some others stuffs too.....
Well, because Synapse is built in now, here's some needed info on it:
Synapse is an awesome and custom built kernel tuner. It can do so much more than a lot of other tuners. And because we have Exynos processors, it's about the only one we can use. But it can create a lot of problems getting to work. Hence this post. :silly:
I decided to make this built in instead of a flashable add on. It's actually easier and less invasive to do it this way.
UCI, is what Synapse uses to work. It's built into the ramdisk. I've added a lot of tunables and may add more later.
Now for the fixes and problems you WILL run into:
If you have issues, make sure to check out these threads. As they will probably have better info about Synapse issues. https://forum.xda-developers.com/showthread.php?t=2736986 and https://forum.xda-developers.com/showthread.php?t=3558888
No UCI support detected These are the famous words you WILL run into.
When will this show up?
When Synapse is first installed
On reboot
When you've pushed your Tablet too far
The fixes:
On first install from the Playstore. You will need to go to Settings>Apps>Synapse>Storage. Then select "Clear Cache", THEN "Clear Data. In that order!!
You may have to backout to Settings and do it one or two more times. You want the numbers for cache and data at "0".
On reboot: This usually works unless you've messed up the settings or flash another kernel
On reboot select "Menu" and "Close all".
Open Synapse and hit "CANCEL" to have your last settings applied. (I know it's not normal but it works)
Close synapse, and reopen it to make sure of settings. (If "apply or cancel" don't show up at the top, you're good to go.)
Worst case scenario:
You will need to go to Settings>Apps>Synapse. Select "Force stop". Select "Storage". Then select "Clear Cache", THEN "Clear Data. In that order!!
You may have to backout to Settings and do it one or two more times. You want the numbers for cache and data at "0".
If you follow the above, Synapse will work. It hasn't failed me in over 50 tests, probably more. :silly:
810 good to go. Have to wait til later this week to try mirroring, gave my daughter my sammy tv..
Edit: confirmation #5H0834012J5874316 - Thanks for your hard work!
andyroidking said:
810 good to go. Have to wait til later this week to try mirroring, gave my daughter my sammy tv..
Edit: confirmation #5H0834012J5874316 - Thanks for your hard work!
Click to expand...
Click to collapse
Thank you for the donation!
Hopefully the 810 looks better on the screen. The 710 is a weird screen size and doesn't fill it. But it still comes in handy.
My "Neked Maker Rom" has it built into the build.prop. But i found I could add it to the kernel. It'll still work with both installed, which I have.
engine95 said:
Thank you for the donation!
Hopefully the 810 looks better on the screen. The 710 is a weird screen size and doesn't fill it. But it still comes in handy.
My "Neked Maker Rom" has it built into the build.prop. But i found I could add it to the kernel. It'll still work with both installed, which I have.
Click to expand...
Click to collapse
I posted a couple days ago but apparently it didn't send. Screen is fine! Everything seems good. It is charging good again too, probably not kernel related but take the credit will ya...
andyroidking said:
I posted a couple days ago but apparently it didn't send. Screen is fine! Everything seems good. It is charging good again too, probably not kernel related but take the credit will ya...
Click to expand...
Click to collapse
Ok.
I'm wondering if it is Synapse with the battery. Guess we'll see.
Haven't spent a lot of time with the kernels lately. Trying some different things, but keep coming back to what I've had in the past.
EX kernel managers builder was interviewed on XDA recently. flar2 . Had some interesting things to say about SELinux. Guess that might be why his tuner doesn't have an option for permissive. Just food for thought for us all.
engine95 said:
Ok.
I'm wondering if it is Synapse with the battery. Guess we'll see.
Haven't spent a lot of time with the kernels lately. Trying some different things, but keep coming back to what I've had in the past.
EX kernel managers builder was interviewed on XDA recently. flar2 . Had some interesting things to say about SELinux. Guess that might be why his tuner doesn't have an option for permissive. Just food for thought for us all.
Click to expand...
Click to collapse
I'll read through that later... his kernel is what I use on my nexus9. His dev app is pretty good too, playstore- DevCheck Hardware and System Info. Smart guy.
Just a little update
I have the 710 and 810 kernels done. I should get 715 and 815 shortly. Then I'll get them uploaded
Just patched to 3.10.61. No additions til I get them as far as I can.
The kernel is EOL at 3.10.108
V1.1 for all 4 is in OP Just patched to 3.10.61
I've changed the way I'm doing it so it's faster. And it's easier for others to track.
I'm hoping to get all the way to 3.10.108 for the next version. Then the addons.
We shall see. :fingers-crossed:
Thank you ! Amazing and smooth as expected ??
810 v1.1 A-Okay
V1.2 is in OP!!!!! Just patched to 3.10.105, which is Feb 2017
Not quite sure if I'll go to 108, or do some addons. I'm kinda burned out on the patches.
More than likely I'll patch to 108, but I am dreading it as just the 3 more patches has over 750 fixes.
And seeing as how our Tablets AND our Kernel is at EOL, I might as well finish it out.
Regardless, enjoy.
engine95 said:
V1.2 is in OP!!!!! Just patched to 3.10.105, which is Feb 2017
Not quite sure if I'll go to 108, or do some addons. I'm kinda burned out on the patches.
More than likely I'll patch to 108, but I am dreading it as just the 3 more patches has over 750 fixes.
And seeing as how our Tablets AND our Kernel is at EOL, I might as well finish it out.
Regardless, enjoy.
Click to expand...
Click to collapse
Thank you, thank you. Don't burn out!
---------- Post added at 01:50 PM ---------- Previous post was at 12:56 PM ----------
andyroidking said:
810 v1.1 A-Okay
Click to expand...
Click to collapse
1.2 good to go of course.
Okay, so I don't know what is missing or changed in the kernel but all of a sudden I am getting horrible battery life I can almost watch it drop sometimes. If you're thinking of updating more maybe putting back some of the tweaks that you had? First?
Edit- it literally dropped a percent when I typed the above.
andyroidking said:
Okay, so I don't know what is missing or changed in the kernel but all of a sudden I am getting horrible battery life I can almost watch it drop sometimes. If you're thinking of updating more maybe putting back some of the tweaks that you had? First?
Edit- it literally dropped a percent when I typed the above.
Click to expand...
Click to collapse
Now that's interesting. I used my Tab last night and all was well.
It could be a rogue app. Or maybe you need to shut it off for a minute. Then boot it up again. There were a lot of changes in the kernel and resetting doesn't always fix things. The battery might need to relearn too.
Side note:
Ya know how when climbing you see a peak and you just have to keep going til you can see over it? Yeah, well, I've just about finished the patches to 108. It'll be a couple days. I just barely got it built and need to see how it does.
Here's some pics of battery for me. And I've installed the kernel a few times too. So reboots are included.
Edit
There's an old trick I still do for "Ghosts in the computer".
Power the Tab off, wait for bout 15 sec, then just press the vol down, vol up and power buttons. Just a press. Do it a few times then boot it up.
The old belief is that there is still an electrical charge that can keep things in memory. By doing this, it'll discharge any current that is lurking.
It may be nothing, but I feel better doing it.
engine95 said:
Now that's interesting. I used my Tab last night and all was well.
It could be a rogue app. Or maybe you need to shut it off for a minute. Then boot it up again. There were a lot of changes in the kernel and resetting doesn't always fix things. The battery might need to relearn too.
Side note:
Ya know how when climbing you see a peak and you just have to keep going til you can see over it? Yeah, well, I've just about finished the patches to 108. It'll be a couple days. I just barely got it built and need to see how it does.
Here's some pics of battery for me. And I've installed the kernel a few times too. So reboots are included.
Edit
There's an old trick I still do for "Ghosts in the computer".
Power the Tab off, wait for bout 15 sec, then just press the vol down, vol up and power buttons. Just a press. Do it a few times then boot it up.
The old belief is that there is still an electrical charge that can keep things in memory. By doing this, it'll discharge any current that is lurking.
It may be nothing, but I feel better doing it.
Click to expand...
Click to collapse
I really wish it was ghosts or Rogue app... rebooted 1.2 browsed Reddit for 17 minutes lost 7%. Flashed 1.1 browsed Reddit and as I'm typing this only 2% in 22 minutes.... We will see what 1.3 brings when it is cooked.
HTML:
andyroidking said:
I really wish it was ghosts or Rogue app... rebooted 1.2 browsed Reddit for 17 minutes lost 7%. Flashed 1.1 browsed Reddit and as I'm typing this only 2% in 22 minutes.... We will see what 1.3 brings when it is cooked.
Click to expand...
Click to collapse
So with 1.2 I was getting 3 to 4% at idle an hour battery drain. Installed 1.1 and overnight 8 hours 1%. Could just be something with my tab and that kernel not liking each other, lol.
andyroidking said:
So with 1.2 I was getting 3 to 4% at idle an hour battery drain. Installed 1.1 and overnight 8 hours 1%. Could just be something with my tab and that kernel not liking each other, lol.
Click to expand...
Click to collapse
I think I found the issue. It was very random and hard to find, but I'm pretty sure I have it fixed now. It'll come out when I finish/ release 108.
For now, all the kernels run fine, so if there's no issues with what's installed, then just keep running it till I get 108 up. Like I said, it's a random thing with 105. Hit or miss. I'll pull v1.2(105)when I get v1.3(108) up.
Thanks for making me look into it. Lol
Thank you @engine95 for your amazing effort. You made my tablet super smooth. And really I was about to sell it, but you let me keep it for another year . Thanks ??????
V1.3 is in OP for all 4 kernels Patched to 3.10.108EOL
I've pulled V1.2 as it had random issues and/or isn't needed now with the fixed V1.3
Just a little FYI
Stock 3.10.9, vs Patched 3.10.108 - Stability vs Security
V1 is the mostly stock 3.10.9 kernel. It will be the most stable of all the kernels as Samsung has tailored it to our Tablet
The rest
These should be the most secure as it has all the Linux patches to date. Thing is, Samsung hasn't made adjustments to optimize the kernel to anything past 3.10.9
Patching it can cause some problems. Usually WiFi, Bluetooth, Battery, USB.
Patching it may make more current products useful. Routers, Game Pads, Hard drives etc....
So from here, I'll wait and see if we have more issues with the patched kernels before moving on.
My options?
Keep going with the patched kernel to build on
or
Go back to 3.10.9 for the stability, and leave the patched kernel where its at.
Let me know how V1.3 does so I can start with the addons on one or the other.
Thanks all and enjoy. :good:
Hi guys!
So I'm probably not as good with phones as you, but I learned to install a ROM, I've tried many of them but then returned to CyanogenMod ROM that was offered on their site. The performance is not that good, it lags often and battery life is too bad! The questions I want to ask you are:
1. Which ROM do you think is the most stable and would be a better alternative to Jelly Bean CyanogenMod?
2. What ROM are you using and why? Experiences etc.
Thank you!
Kind of in the same boat, just three meters further out. Have been putting off buying a new pho.... embiggened touch-pad device with phone capability and less battery life, that should in a reasonable world come with a carrying case with a shoulder-strap, and a stock portfolio for the handset maker... for a few years. But finally caved in, and bought something on sale with a really good screen, a replaceable battery, and a 3,5mm jack not made exclusively out of conductive rubber.
But. Now that I had a new phone pad, I wouldn't have to worry about bricking my old phone. All that much. So I went through a bunch of excruciating testing and failing yesterday to get something without ram-crippling bloatware and google applications that essentially force the 4x to run constantly at max speed.
What I seemed to be running into was two types of problems: a lot of the roms (custom firmware) were made by someone who was simply testing something new at the time, experimented a lot, and then left the project behind (or simply focused on other handsets). That's not necessarily a problem, but it can mean that you have stability issues you might not expect, and that has not been tested or reported while the project was active. And that might actually stop you from getting far enough to install some app that changes cpu-governor, ram-handling, and so on (even things like the standard keyboard/language variant.. kind of essential that that works). Install instructions also tend to link to outdated bootloaders, or have workaround suggestions that worked at the time, but now are obsoleted completely. The second problem was the OpenGapps - some of the core apps conflict with the builds' own apps.
And then there's the fact that the kernel in these roms tend to be from when the project was last maintained. I can't seem to decipher exactly what's going on, but I think a lot of the early roms were based on an old kernel with inserts (like the original one from LG). While the older builds on new kernel branches tend to have better support, but then have certain types of functionality simply gone completely. I don't know why that is, but the experience with this on linux laptops and android devices is what made me hold off until I had something that could replace the 4x before starting to try out some of the experiment builds people have.
So I went through getting the bootloader unlocked, trying a billion different methods before realizing they were all workarounds for the non-eu handsets - just use the oem-unlock method with fastboot. It's really as simple as it sounds. Use the "all in one" thing on the forum, set up the drivers, get root, and things like that - and then install a new, updated bootloader. I think after one of the official LG updates, everyone can actually use the oem-unlock.
Then I chose the wrong bootloader, apparently.. the cwm touch thing - superb bootloader. But apparently has some quirks that prevents it from installing certain firmware packages. I think it has something to do with consistency checking. I liked the idea of a multiboot, and didn't see why that wouldn't be extremely easy on android (with a storage size vs. cfw package being basically infinite to naught). But apparently what you want(need) is the twrp bootloader, and it has to be the last version. I don't know why that is, but you really don't want to be stuck - after basically wrecking your only boot - with an uninstallable image on your sdcard. So if you try something else than the "best one", just be prepared for an exit strategy with a backup and things like that before trying to install new images. There's also no way on these bootloaders to simply run a test first, nor is there a very easy way to partition the on-phone storage without having to start configuring install packages, so this is kind of awful if you're not actually deep into the development toolchains already.
I'd really love it if some of the tutorials said things like: our build really doesn't need a thorough wipe, and you can happily choose the file system you'd like, and the one that actually makes sense. For example. Or "for this cfw, you can just install gapps later on, that's going to work perfectly - don't force the install before you get through our own intro stage", etc. Alas.
Then I went through slimkat, an aosp lineage based rom, an old 4.1 rom, a new 5.1 rom, which all had different game-breaking problems. One refused to install gapps (note: you'll need the gapps that fit with the android version - but some packages simply won't install, period), another build had no sound other than on the speaker. One hanged randomly, another didn't scale the processor cores.
The good news is that this isn't really a problem - once you're set up you can just keep wiping and installing new ones. But it might be a really good idea to make a backup of your initial rom/custom firmware, just in case (i.e., you root, install the bootloader, and once you're in the bootloader, you make a backup of your current "rom" that is installed now. Then you can just revert to that without any problems later. I obviously didn't do that, because I was just fumbling around).
Some of the issues I ran into also might have workarounds, but I don't know - how would I, there's no way to actually tell what the problem is, or what it's related to. The most useful ones in the end seemed to be Vanir 6.0-based, and the one I ended up with, something called Euphoria on lollipop/5.1. That one seems to have all the hardware functions and benefitting a lot from a later kernel. I haven't done incredible amounts of testing on it yet, but it seems to work a lot better than the original firmware ever did.
And when you choose a gapps package, just go with the pico version. You can install everything you need after that from the store (and it takes less time than pre-installing the infinite amounts of crap in the stock package).
In sum - while you can get pretty far with the 4x on just rooting it and uninstalling some of the infinitely memory-hogging google crap, along with installing a new governor for the cpu and things like that. You can actually get something extremely neat by installing a new "rom"/cfw, that doesn't necessarily have the "oh, but you just have to forgo feature X, Y and Z because open source" problems.
I'm sure a cfw-developer is going to see this one day and roll their eyes back in their heads. And will have some very sharp words about the kind of effort that went into making a specific kernel, insert and build combination to even boot. But the later kernels seem to work really well.
And thanks to that Euphoria thing, I'm probably not going to use my new padphone-thing as much as I would. Because that one is over the "just testing stuff, getting it to work" stage. There's things with the home-button bar lighting up when there's notifications, things like that, that kind of show someone who used the handset was maintaining the build.
Anyway - I really recommend that you try out some different types to find these really good roms that works well. I'm sure there are lots of unknown cfw packages out there that work.. you know, for the 300 people who use it every day. That might be some of the early cfw variants with old kernels. And it might clearly also be some of the new ones, which I really didn't expect. Honestly, was kind of expecting stripes across the screen and hangs, but that didn't happen.
Optionally, a dev who actually knows what they're talking about could maybe suggest a list of cfw that have the later kernels that work, or the same kernels that Euphoria has Really, trying to search the net now, and find possible candidates was not easy.
Greetings all, I installed CyanogenMod version 11-20141112_SNAPSHOT-M12-ovation way back. It has always been unstable and frustrating so I just walked away from the project.
Now it is 2018 and I'd like to take another crack at it. Last time I followed a guide I found online but this time I'm trying to put a bit more forethought into it and want to start from the ground up.
So first things first, what is the most stable, responsive build for the Nook HD+? I don't think I need the latest and greatest, I just want my Vudu to not crash, be able to start the dang thing up, and not have my battery drain randomly.
Thanks in advance!
amaces Lineage OS 14.1 lnos_ovation-ota-NJH47F.171021.zip - You must install pico gapps to get through initial setup easily. Apart from that, this rom is very solid. secretwolf98 is also posting builds, but I have not tested them yet.
Unlegacy-Android Nougat ua_ovation-7.1.2-20180111-0528.zip - Has a wifi bug where you lose settings after reboot. The easiest way to work around this is to connect to two wifi networks, and then disable and re-enable wifi two times. You will autoconnect to the first network automatically from then on.
amaces Marshmallow aosp_ovation-ota-MOB30Z.160820.zip - This is the most stable and mature rom in my opinion. The one major bug is that for wifi to connect on boot, you have to pull down the notification bar completely and press the wifi button to show available networks.
Edit: Forgot to mention that all these recent unlegacy-android based roms are much more stable than roms of the past. No more ANR loops, random rebooting, and the need to disable hardware overlays. Everything is generally working and stable.
amaces Lineage OS 14.1 lnos_ovation-ota-NJH47F.171021.zip looks to be the way to go, Thanks!
fddm said:
Everything is generally working and stable.
Click to expand...
Click to collapse
AFAIK HDMI output does not work in recent years (unlike with CM11). Or did it change?
fanoush said:
AFAIK HDMI output does not work in recent years (unlike with CM11). Or did it change?
Click to expand...
Click to collapse
Yes, afaik that is still true. I haven't got around to testing yet, but I think cm11 is still being built and is probably quite stable now days. I don't think I'd recommend buying that hardware as even the Nook's own screen is too high a resolution for it's own processor and graphics chip. I'm amazed it plays YouTube [email protected] as well as it does.