[ROM][4.4.4/4.3.1][Hummingbird][EMMC][UNOFFICIAL] LineageOS 11 & CM 11 & CM 10.2.3

[ROM][4.4.4/4.3.1][Hummingbird][EMMC][UNOFFICIAL] LineageOS 11 & CM 11 & CM 10.2.3 - Nook HD, HD+ Android Development

[ROM][4.4.4/4.3.1][Hummingbird][EMMC][UNOFFICIAL] LineageOS 11 & CM 11 & CM 10.2.3
Download link is found under the "Downloads" tab on the top left of this post / thread.
Or, https://forum.xda-developers.com/devdb/project/?id=22294#downloads
Changelog:
The 2017-12-09 build is a must need update. It contains the latest security patch and removed the browser for security reasons. The browser is now replaced with Lightning Browser +. lineage-11-20171209-UNOFFICIAL-hummingbird.zip
The 2017-12-10 build contains a needed update to the user interface instead of the userdebug interface. This is being added due to security reasons with the old browser and the userdebug interface. lineage-11-20171210-UNOFFICIAL-hummingbird.zip
The 2017-12-29 build contains, fixed fonts, fixed the boot animation file, and updated webview stuff. lineage-11-20171229-UNOFFICIAL-hummingbird.zip
The 2017-12-29 #2 build contains, removed Lighting Browser + because it crashes, and added a safer browser. lineage-11-20171229-UNOFFICIAL-hummingbird.zip
The 2017-12-30 build contains, removed Browser for crashing reasons (download your own browser). lineage-11-20171230-UNOFFICIAL-hummingbird.zip
The 2017-12-31 build contains, updated CM apps. lineage-11-20171231-UNOFFICIAL-hummingbird.zip
The 2018-01-10 build contains, updated security patch. lineage-11-20180110-UNOFFICIAL-hummingbird.zip
The 2018-01-16 build contains, fixed system apps, priv-apps, and framework. This update fixes the UI crashes after each reboot or shut down. lineage-11-20180116-UNOFFICIAL-hummingbird.zip
The CyanogenMod 11 2018-01-23 build contains, updated everything, this is the first release. cm-11-20180123-NIGHTLY-hummingbird.zip
The CyanogenMod 11 2018-01-23 build #2 contains, fixed boot animation on start ups. cm-11-20180123-NIGHTLY-hummingbird.zip
The LineageOS 11 2018-02-07 build contains, updated webview stuff, added .so files, updated CM apps, updated .so files, removed Lightning Browser+, updated the security patch, and added Prebuilt Chromium browser. (Thanks to @Android-Andi for creating Prebuilt Chromium browser. Which it can be found here, https://github.com/andi34/prebuilts_chromium) lineage-11-20180207-UNOFFICIAL-hummingbird.zip
The CyanogenMod 11 2018-02-26 builds contains, updated webview stuff, updated security patch, and updated CM apps. cm-11-20180226-NIGHTLY-hummingbird.zip
The Testing #1 build of CyanogenMod 10.2.3 2018-03-02 build contains, FIRST RELEASE.
cm-10.2.3-hummingbird.zip
CyanogenMod 11 2018-09-18: Updated CyanogenMod apps, updated webview stuff, updated security patch, fixed some security issues within the system, and added these unofficial builds changes into the change-log. cm-11-20180918-NIGHTLY-hummingbird.zip
CyanogenMod 11 2019-03-23: Updated security patch, updated webview stuff, and fixed some system security issues. cm-11-20190323-NIGHTLY-hummingbird.zip
XDA:DevDB Information
[ROM][4.4.4/4.3.1][Hummingbird][EMMC][UNOFFICIAL] LineageOS 11 & CM 11 & CM 10.2.3, ROM for the Barnes & Noble Nook HD
Contributors
secretwolf98, LineageOS, and CyanogenMod
Source Code: https://forum.xda-developers.com/devdb/project/?id=22294#downloads
ROM OS Version: 4.4.4 KitKat (KK) & 4.3.1 JellyBean (JB)
Based On: LineageOS 11 & CyanogenMod 11 & CyanogenMod 10.2.3
Version Information
Status: Stable
Stable Release Date: 2018-02-07 (LineageOS 11) & 2019-03-23 (CyanogenMod 11) & 2018-03-02 (CyanogenMod 10.2.3)
Created 2017-08-30
Last Updated 2019-03-23

@secretwolf98 This is a placeholder.... soon to be closed if nothing tangible appears. Why start a thread with no build to offer?

LenAsh said:
@secretwolf98 This is a placeholder.... soon to be closed if nothing tangible appears. Why start a thread with no build to offer?
Click to expand...
Click to collapse
I am going to add download link ASAP after school (about 1 hour I get home)
I had gotten kinda busy. Sorry

Don't suppose you could do an Ovation build as well?

twiztid_ said:
Don't suppose you could do an Ovation build as well?
Click to expand...
Click to collapse
Sure, let me finish Acclaim build, and I will start Ovation build.
But I don't have a Nook HD+, so I need you to help me test it.

twiztid_ said:
Don't suppose you could do an Ovation build as well?
Click to expand...
Click to collapse
Check your XDA messages. I had sent you a Ovation test build.

secretwolf98 said:
Check your XDA messages. I had sent you a Ovation test build.
Click to expand...
Click to collapse
Install went smoothly, and the system itself runs fine aside from a few long standing issues (Advanced Reboot -> Reboot to Recovery, plugging in the Nook will make it boot up).
Issues using this build vs verygreen's EMMC CM11 install 141129:
On initial boot it will prompt you to set up a Google account, even without a GApps package installed. This causes a CM Updater "crash" both with and without a Gapps package.
Both GApps packages I've tried have crashes on startup: PAGapps which worked on verygreen's (Now gives "There was a problem communicating with Google servers."), and OpenGApps ARM 4.4 Pico which had crashing issues before.
Amazon Underground (Amazon's App Store) crashes after logging in.
Given those two issues, it's hard to further test any other crashes/problems.

twiztid_ said:
Install went smoothly, and the system itself runs fine aside from a few long standing issues (Advanced Reboot -> Reboot to Recovery, plugging in the Nook will make it boot up).
Issues using this build vs verygreen's EMMC CM11 install 141129:
On initial boot it will prompt you to set up a Google account, even without a GApps package installed. This causes a CM Updater "crash" both with and without a Gapps package.
Both GApps packages I've tried have crashes on startup: PAGapps which worked on verygreen's (Now gives "There was a problem communicating with Google servers."), and OpenGApps ARM 4.4 Pico which had crashing issues before.
Amazon Underground (Amazon's App Store) crashes after logging in.
Given those two issues, it's hard to further test any other crashes/problems.
Click to expand...
Click to collapse
Would you by the chance have the CyanogenMod 11 Ovation Nightly 8-15-2016 build (latest one)? Maybe I can take some sources out of that.
***EDIT***
I had found latest build on, https://www.mediafire.com/folder/6f68b2wtf6db4/NookHD+
I will look into this problem. I will have another test build done later tonight or tomorrow.
Thanks for your feedback.

twiztid_ said:
Install went smoothly, and the system itself runs fine aside from a few long standing issues (Advanced Reboot -> Reboot to Recovery, plugging in the Nook will make it boot up).
Issues using this build vs verygreen's EMMC CM11 install 141129:
On initial boot it will prompt you to set up a Google account, even without a GApps package installed. This causes a CM Updater "crash" both with and without a Gapps package.
Both GApps packages I've tried have crashes on startup: PAGapps which worked on verygreen's (Now gives "There was a problem communicating with Google servers."), and OpenGApps ARM 4.4 Pico which had crashing issues before.
Amazon Underground (Amazon's App Store) crashes after logging in.
Given those two issues, it's hard to further test any other crashes/problems.
Click to expand...
Click to collapse
Test 2 is done. I had sent you link threw XDA messages.

secretwolf98 said:
Test 2 is done. I had sent you link threw XDA messages.
Click to expand...
Click to collapse
I haven't tested much, but so far: Flawless.
Again, no errors during install/boot.
For the second wipe/install I installed the PA Gapps immediately after LNOS (no reboot), setup went fine but with one minor hiccup; everything worked, but kept offering to set up my Google account after I had logged into it. I simply hit Skip and the setup continued as normal, and everything was fine including Google Account/Play Store. -- This may have been a one-time 'accident', I didn't try to reproduce it because it wasn't a significant issue.
I did a second fresh install with GApps, this time installed OpenGApps ARM 4.4 Pico, and had zero issues. Everything set up perfectly fine.
After booting to the 'desktop' I installed my cable TV provider's app and the SyFy app (TV Station), logged in to both, and played a show without any problems for either app (aside from my Cable provider complaining about USB Debugging, after turning it off it was fine). I don't have Netflix/Hulu, but it seems there are no apparent problems with codecs/DRM.
Thank you so much for your work, and super fast turn around on this!

What, exactly, is the value of putting this on our nooks instead of the current go-to ROM? I'm curious because I've been out of the loop with my nook for several months. Is this a more memory friendly but with the tweaks that the newer one has included, or is it just a matter of preference?

ieatabiscuit said:
What, exactly, is the value of putting this on our nooks instead of the current go-to ROM? I'm curious because I've been out of the loop with my nook for several months. Is this a more memory friendly but with the tweaks that the newer one has included, or is it just a matter of preference?
Click to expand...
Click to collapse
I'm using 4.4 because it feels faster than M/N builds, the response/loading times feel more snappy.

twiztid_ said:
I'm using 4.4 because it feels faster than M/N builds, the response/loading times feel more snappy.
Click to expand...
Click to collapse
That's what I was curious about. The M/N builds are great, but it just feels like the nook's showing it's age more with them. How does this new build rate against some of the now-dead KK builds? Does it feel newer, or is it just the latest release of the old stuff? Does the ROM use any of the newer tweaks from LNOS backported? Does it have that annoying screen flicker most older ROMs had? And how does youtube play on it (I have always had issues with it freezing during playback)? I might have to hop in line with you to be a tester for this on my ovation too!

ieatabiscuit said:
How does this new build rate against some of the now-dead KK builds? Does it feel newer, or is it just the latest release of the old stuff?
Click to expand...
Click to collapse
I'd say it's a "LNOSified" version of the CM11 ROM.
From the bit I've used it, feels just as good as the CM11 in verygreen's post... which is surprisingly good. I hopped back to 4.4 (well, 4.3, then 4.4) because the GUI of some apps I was using, and the UI itself at times, were feeling sluggish. I'm not sure I'd say it feels "newer" in the sense of KitKat vs Android L/M/N interface, but it does in terms of overall "snappyness" where things feel more responsive. I'm guessing it has some newer versions/commits of files, but that might be all.
The rest of your questions I'll answer without quotes to save on length:
I don't believe it uses any of the LNOS (or even CM) tweaks from 5.0+, but I don't know for sure.
I can't say how into this secretwolf98 wants to get, but so far I'm not sure if it "needs" any tweeks.
I never had the screen flickering issue untill Lollipop builds, and that was something Amaces fixed completely(?) in the M builds I think.
I didn't get to try out Youtube (yet), but I did try out my Cable Co.'s TV App (Live TV and On-Demand) and the SyFy app (On-Demand) and had no issues. I'll give that a shot tonight and give you an update on this post.
Just watched an 18ish minute video on YouTube, and didn't have any buffering issues.

twiztid_ said:
I'd say it's a "LNOSified" version of the CM11 ROM.
From the bit I've used it, feels just as good as the CM11 in verygreen's post... which is surprisingly good. I hopped back to 4.4 (well, 4.3, then 4.4) because the GUI of some apps I was using, and the UI itself at times, were feeling sluggish. I'm not sure I'd say it feels "newer" in the sense of KitKat vs Android L/M/N interface, but it does in terms of overall "snappyness" where things feel more responsive. I'm guessing it has some newer versions/commits of files, but that might be all.
The rest of your questions I'll answer without quotes to save on length:
I don't believe it uses any of the LNOS (or even CM) tweaks from 5.0+, but I don't know for sure.
I can't say how into this secretwolf98 wants to get, but so far I'm not sure if it "needs" any tweeks.
I never had the screen flickering issue untill Lollipop builds, and that was something Amaces fixed completely(?) in the M builds I think.
I didn't get to try out Youtube (yet), but I did try out my Cable Co.'s TV App (Live TV and On-Demand) and the SyFy app (On-Demand) and had no issues. I'll give that a shot tonight and give you an update on this post.
Click to expand...
Click to collapse
Nice, I might have to look into this more, and poke at secretwolf98 to see what I can learn. Thanks!

ieatabiscuit said:
Nice, I might have to look into this more, and poke at secretwolf98 to see what I can learn. Thanks!
Click to expand...
Click to collapse
If you want Ovation, I will be posting it here soon as a thread in XDA. Stay tuned!

twiztid_ said:
I haven't tested much, but so far: Flawless.
Again, no errors during install/boot.
For the second wipe/install I installed the PA Gapps immediately after LNOS (no reboot), setup went fine but with one minor hiccup; everything worked, but kept offering to set up my Google account after I had logged into it. I simply hit Skip and the setup continued as normal, and everything was fine including Google Account/Play Store. -- This may have been a one-time 'accident', I didn't try to reproduce it because it wasn't a significant issue.
I did a second fresh install with GApps, this time installed OpenGApps ARM 4.4 Pico, and had zero issues. Everything set up perfectly fine.
After booting to the 'desktop' I installed my cable TV provider's app and the SyFy app (TV Station), logged in to both, and played a show without any problems for either app (aside from my Cable provider complaining about USB Debugging, after turning it off it was fine). I don't have Netflix/Hulu, but it seems there are no apparent problems with codecs/DRM.
Thank you so much for your work, and super fast turn around on this!
Click to expand...
Click to collapse
Your welcome

ieatabiscuit said:
Nice, I might have to look into this more, and poke at secretwolf98 to see what I can learn. Thanks!
Click to expand...
Click to collapse
Here is the post link, https://forum.xda-developers.com/nook-hd/general/rom-lineageos-11-t3668779

twiztid_ said:
I'm using 4.4 because it feels faster than M/N builds, the response/loading times feel more snappy.
Click to expand...
Click to collapse
Here is the post link, https://forum.xda-developers.com/nook-hd/general/rom-lineageos-11-t3668779

twiztid_ said:
I'm using 4.4 because it feels faster than M/N builds, the response/loading times feel more snappy.
Click to expand...
Click to collapse
For me CM11 was great and fast but the lack of memory was more apparent than with current M/N builds. Typical is Firefox (with uBlock installed). With CM11 you can't sometimes even open single tab with some heavy page (like some long blog with lot of youtube videos) without running out of memory and crashing. Latest builds have zram swapping enabled and even a bit more physical memory available so Firefox works just fine even with many tabs. But yes swaping means it is sometimes slow when memory gets tight but it does not crash. Maybe CM11 with same memory layout and zram swapping enabled and tuned in same way would be even better? Haven't tried this build, maybe it already has some tuning like that?
Edit: This is with Ovation, most probably the memory pressure with Hummingbird is not so bad due to lower display resolution.

Related

[Nook HD/HD+] EMMC CM11 install - updated 11/29

I see there's this new CM11 going, and thanks to @Hashcode who solved most of the complex problems already, here's my first stab at CM11 on our Nook HDs that installs into internal memory (EMMC).
The install is a lot similar to how it was done in CM10.2 days, but you will need a new recovery image (and a new sdcard image for those doing initial install):
So, For Nook HD+: Initial ovation sdcard image (cwm) | ovation recovery image (CWM)
For Nook HD: hummingbird Initial sdcard image | hummingbird recovery image (CWM)
I did some light testing and things seems to be working for whatever light loads I came up with, but still there are probably tons of problems that I have not yet noticed. Please write in the comments about what's broken and I'll try to fix it. Once it's good enough, I'll try to get official nightlies going for CM11 as well, I guess.
Latest CM11 EMMC images are now available as CM11 nightlies at:
For Nook HD+ get ovation builds
For Nook HD get hummingbird builds
There also might be experimental builds available referenced below in the history section.
(Also for completeness, For Nook HD+ sdcard image cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip, | initial sdcard image for ovation )
For new Installs:
Download the initial sdcard image
ungzip and write to sdcard using dd (winimage or whatever for those stuck on Windows)
Instert the card into your nook and reboot
Flash the recovery image
Flash cm11 image
Flash whatever other extra things you need like gapps
remove the sdcard
reboot the nook
For upgrades from CM10.x (the only tested are 10.2 and 10.1). If you have any problems after upgrade - you'll need to do factory reset to clear /data:
Download recovery zip and CM11 install and place it on the nook
Reboot into recovery you already have installed
Flash the recovery zip you just downloaded
reboot into recovery again (This is important! Failure to do this will botch your upgrade and you'll need to wipe /data) so that the new recovery is started.
Install CM11, install other stuff you need like gapps
reboot
enjoy
Note: After upgrade you will need to reenter all of your wifi passwords.
Useful apps:
Overall loudness and volume control app: NookHDVolumeAdjuster-1.apk
Touch screen sensitivity control: NookTouchscreenSensitivityAdjuster-4.apk (backup link)
USB host control (usually only needed on official CM builds, as otherwise you can use Quick Settings panel): USBHostSwitcher.apk
Known problems:
- attempting to reformat external sdcard from android crashes volume manager - seems to be upstream problem of some sort. The sdcard is left in some strange state, so don't do it. (if you did, reformat the sdcard on your PC, all data will be lost either way)
Changelog:
2014/11/297 - Bring sdcard build to current source version:
* cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip
2014/08/17 - Bring sdcard build to current source version:
* cm-11-20140817-UNOFFICIAL-ovation-sdcard.zip
2014/01/18 - Fixed 1080p movie playback on Nook HD+:
* cm-11-20140118-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140118-UNOFFICIAL-ovation-sdcard.zip
2014/01/17 - Fixed headset mic issue
* cm-11-20140117-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140117-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140117-UNOFFICIAL-ovation-sdcard.zip
2014/01/15 - Switched to TI wpa supplicant, should fix a bunch of wifi-related issues
* cm-11-20140115-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140115-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140115-UNOFFICIAL-ovation-sdcard.zip
2014/01/09 - Fixed inability to write to sdcards.
* cm-11-20140110-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140110-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140110-UNOFFICIAL-ovation-sdcard.zip
2014/01/08 - Misc updates: autodetect sdcard format, not just vfat. fuzzy touch patch courtesy of D Marble, bt-pan services that reportedly fix bt tethering for some people.
* cm-11-20140109-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140109-UNOFFICIAL-hummingbird-emmc.zip
2014/01/06 - Initial release
* cm-11-20140106-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140106-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip

The screen kept flickering like a tube light few times.

Thank you! Welcome back
Sent from my BN NookHD+ using xda app-developers app

Welcome back, you've been missed greatly. I kept telling everyone not to panic, you would be back.
Sent from my BN NookHD+ using XDA Premium HD app

Thanks dude. I was hoping you'd start building it. Downloading now!

Working well so far. Thanks for making it and glad to have you back.

for those who need gapps you could see below (Be sure to choose 4.4.2 gapps.)
Link for PA gapps : http://forum.xda-developers.com/showthread.php?t=2397942 <MINI MODULAR PACKAGE 121 MB>download link http://goo.im/devs/paranoidandroid/roms/gapps-mini/pa_gapps-modular-mini-4.4.2-20131230-signed.zip
My personal favorite is BaNK's gapps : http://forum.xda-developers.com/showthread.php?t=2012857 <core gapps only, 17MB>download link http://www.androidfilehost.com/?fid=23269279319195954

Thanks for starting the work again -- I can't wait for official nightlies. And welcome back.
Also, it seems that we have to use CWM. Is there a reason TWRP isn't supported, or is that on the to-do list?

Nice to see this, I've used Bokbokan's eMMC build off his blog with TRIM support by default (MAG2GA ver06 10/2012), and I've used yours with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!

It would be interesting to know if it presents visible differences from CM 10.2 regarding responsiveness, especially with ART enabled. It's the last fort to be conquered with our nooks (trim+art). Sadly my nook is not back yet so any reports would be welcome.

Awesome
Nice to see this, I've used Bokbokan's eMMC build (off his blog) with TRIM support enabled by default (MAG2GA ver06 10/2012), and I've used your CM10.2 with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!

jjjooonnn said:
Nice to see this, I've used Bokbokan's eMMC build (off his blog) with TRIM support enabled by default (MAG2GA ver06 10/2012), and I've used your CM10.2 with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!
Click to expand...
Click to collapse
It should be updatable via the settings once it's an official built. Right now, all of the builds are unofficial ones, so they have to be fully downloaded and flashed.
verygreen is the official device maintainer for CM though, so once he "approves" of the build, it will be built nightly by the CM servers, and then it will be fully integrated into their update mechanism (or CyanDelta if you use that). Just like the 10.2 builds.

TeutonJon78 said:
Also, it seems that we have to use CWM. Is there a reason TWRP isn't supported, or is that on the to-do list?
Click to expand...
Click to collapse
It's on the todo list, but cwm was easier to make at first (as in, next to zero effort)
jjjooonnn said:
Does this build come with TRIM enabled?
Click to expand...
Click to collapse
Yes, this has TRIM-enabled kernel, though I have not decided if I should do it for the official releases.
Have there been any more bricks with the trim-fixed kernels in the past couple of months?
Will this be updatable via CM updates in settings?
Click to expand...
Click to collapse
I guess yes, once there are official nightlies again. But I want to make sure it's at least of adequate quality before enabling that.

Just an advisory: I just flashed this over Succulent's rom with no problems, BUT I lost all my saved wifi profiles and had to reflash gapps. Not any big deal, but to anybody else who plans to do that and isn't coming from CM 10.1/2: be prepared. Relatively painless upgrade, though. Very glad to see TRIM enabled. Don't plan on enabling ART until xposed/gravitybox is compatible. This is much, much smoother than Succulent's build.

Good job!
I can't speak for anyone but didn't see anything from a quick search in the post: TRIM FAQ. I can attest that mine works and I believe it should be one of the bad eMMC (MAG2GA ver06 not ver05).
I did test TRIM (vdc fstrim dotrim) no issues, and found the CM11 under updates (after I updated to CM11) so I can attest to that much!
Thanks for the reply

Darrian said:
Just an advisory: I just flashed this over Succulent's rom with no problems, BUT I lost all my saved wifi profiles and had to reflash gapps. Not any big deal, but to anybody else who plans to do that and isn't coming from CM 10.1/2: be prepared. Relatively painless upgrade, though. Very glad to see TRIM enabled. Don't plan on enabling ART until xposed/gravitybox is compatible. This is much, much smoother than Succulent's build.
Click to expand...
Click to collapse
I would say they are about same smooth. Succulent's build has some nice framework and more option in performance settings. But just from system ui or user experience they are almost the same. Not could I tell the difference in app opening or transition.
Stock launcher Does lag when press the app drawer butter from home screen. But I use Nova launcher to solve the problem.
No find significant performance inprovememt over cm10.2 yet. Maybe Kitkat just does more job in UX polishing rather then performance.
Hopefully we could find some Performance MOD to use in KitKat.

It may very well be due to the fact that I upgraded from CM 10.2 and did not do a clean install, but for me Succulent's build was extremely laggy, many apps froze frequently, and when too many apps (more than like 3) were open it would reboot itself. I have none of those problems with this build, it's super smooth and fast and I haven't had any apps become laggy or crash or reboot my tablet. And this is upgrading from CM 10.2>Succulent's KK>Verygreen's KK; I still haven't done a factory reset and don't plan to unless it becomes necessary later. I use Nova as well. I'm not saying Succulent's build is bad, I thought it was bearable enough to use and was planning on using it long term, updating with each new build until it got to where I thought it should be, but then I installed this build and the difference is staggering. If I reflashed Succulent's build and wiped my data partition I might have a better experience, but now that I have this I don't see any need to.

this is great, glad to see you're back =)
my nook is currently being borrowed, i was wondering if anyone could quickly benchmark it?
thanks

Thank you Verygreen for this new build.
I will try it today.
I have 2 questions about CM11 and Nook HD+ hardware:
- did the HD+ have a bluetooth low energy (BT 4.0) chips?
- did the HD+ have a Low-power audio playback (kitkat new feature) capable chips?
If yes, is it included in this new CM11 build?
Thanks
Edit:
I found that Nook HD+ has wl1271l chip and uses wl12xx driver. That chip is BT 4.0 and BLE. See here http://www.rfm.com/products/data/wls1271l.pdf
But this thread show that BLE isn't activated in CM.

verygreen said:
久しぶりでした
(Also for completeness, For Nook HD+ sdcard image cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip, | initial sdcard image for ovation )
Click to expand...
Click to collapse
Thanks verygreen. Great to see your are back in action.
The SDCARD image link is downloading emmc image. Here is the correct like if any one is looking.
cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip

[ROM]Unofficial OmniRom 5.1 for the Galaxy S 4G (SGH-T959V and T959P)

Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
Installation Instructions
Make sure you have a second partition on your SD card before flashing!!!! This can be created with minitool partition wizard on Windows or gparted on Linux.
If on a BML rom (stock-based GB)...
0. Read "Things to take note of" below
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. It will reboot a couple of times, don't be worried.
4. If you want root or Gapps, flash them now
If on an MTD rom (CM7 and all ICS+)(I tested CM9, CM10.1 and CM11)...
0. Read "Things to take note of" below
1. Reboot to recovery
2. Wipe data, and cache paritions (just in case). If updating to a newer build, you can probably skip this step
3. Install zip
4. If you want root or Gapps, install them now
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
Humberos (the i9000 maintainer) has moved on to different projects which means no first-gen Galaxy S devices are being actively maintained. Builds may break at any time!
I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess and also provide T959P builds.
The USB connection is MTP and not mass storage as Omni has removed mass storage. In recovery there is still an option to mount as mass storage device.
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps reportedly slow down the device significantly so tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Taking pictures
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Powered-off charging animation
Flash from BML
Video Recording
Automatic Brightness
Moving Apps to the SD Card
GPS
Encryption
Compass
SElinux in enforcing mode
What probably doesn't
Microphone mute option doesn't work during calls
What doesn't
720p recording is very laggy
What's been removed
TV-Out - It was removed upstream plus I think binary blobs are broken in Lollipop...
Live wallpapers - this is a low-ram device
Everything else is not tested!!!
XDA:DevDB Information
Unofficial OmniRom 5.1 for the Galaxy S 4G (T959V) and Galaxy S Fascinate 4G (T959P), ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99, humberos
Source Code: http://github.com/omnirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: All
Based On: OmniRom
Version Information
Status: No Longer Updated
Created 2015-06-30
Last Updated 2016-05-12

Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to FB and Dao for their work on the CM-11 device tree. I used several of their fixes.
Thanks to noiphonehere for his device trees and kernel, most of my work was based off of his.
Thanks to bhundven and the other members of teamacid for their work on the aries kernel.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-5.1 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Download folder in .repo/local_manifests folder of the source tree.
After syncing the source, open a terminal and in the directory where you downloaded the source code type "source ./build/envsetup.sh" and then "brunch galaxys4gmtd"
Changelog
Changelog for 07/03/2015 Build
Newer Omni source
Added volume controls and flight mode toggle to power button menu
Added Bigmem option. This increases available RAM by ~20mb but breaks 720p video recording. Humberos created the kernel setup and I integrated a toggle for it into Advanced device settings.
Selinux is now in enforcing mode. I had to modify the GPS startup to have any chance of getting here. Please let me know if it still works/doesn't work/never worked
Notifications are sometimes wonky. To fix, in Settings, go to Performance, then Advanced. Select Force high-end graphics and reboot your phone.
Changelog for 2015/07/20 Build
The data partition is now the second partition of the SD Card as opposed to internal storage
Gapps now work. If you get error 461 when installing from Play Store, a full data wipe should fix it. You can try experimenting with clearing data for the Play Store and/or Play Services or removing and re-adding your Google account if you don't want to do a full data wipe.
HSPA vs UMTS settings in DeviceSettings has been fixed
High-End graphics are forced by default to fix notification issue
ART parameters have been tweaked
Miscellaneous other tweaks, see my Github for details
Changelog for 2015/07/24 Build
Stabilized bluetooth connection
Fixed typo in GPS initialization. Does it work?
Added ability to use f2fs file system on /data. Supposed to give better performance
Added force fast charge and touch wake to kernel. Touchwake is accessible through its sysfs path, fast charge through Performance Settings, BatterySelinux currently denies these requests...
Changelog for the 2015/07/29 Build
This is a maintenance build. Very little has changed
Some more RAM freed (disabled some debugging stuff, TV-Out driver, IR driver)
Sepolicy updated for fast charge and touch wake
GPS initialization tweaked - unsure if works. If it doesn't, a dmesg would be appreciated
Changelog for 2015/08/02 Build
SElinux changed to permissive - this build only
GPS sepolicy changed - unsure if all necessary things are implemented
Changelog for 2015/08/13 Build
Selinux back to enforcing. Thanks to @anoymonos for the dmesg and @DerPugNa for offering to send me one as well
Fixed encryption
Changelog for 2015/08/31 Build
Updated Android version (5.1.1_r5 to 5.1.1_r12)(upstream Omni Change)
Restoring /system in TWRP should now work
When installing from BML, a chance is given to install gapps and/or SuperSu before rebooting
zRam is now actually used...
Changelog for 15/10/2015 Build
Fixed typo in updater.sh (thanks @FBis251!)
Update Omni source code - plenty of little tweaks since last build

Source Code and Downloads
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see android-5.1-t959v branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-5.1 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-5.1 branch)
Downloads!
All builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing
Please let me know if the link doesn't work! There are also builds there for the T959P, in case there are any users of it left.
Gapps
Gapps do not work on builds prior to 2015/07/20. On more recent builds, they can be installed from http://forum.xda-developers.com/showpost.php?p=59731008&postcount=2
SuperSu
SuperSu can be found at https://download.chainfire.eu/696/SuperSU/

Thanks thanks ....

Awesome work @xc-racer99!

Wow, bringing this ole device back from a coma here. Nice to see someone else willing to work on lollipop for this oldie but goodie. Keep this device alive man.
Edit: If you are in need for some GFX for this thread, let me know and I'll see what I can brew up for you.

GFX.myst. said:
Wow, bringing this ole device back from a coma here. Nice to see someone else willing to work on lollipop for this oldie but goodie. Keep this device alive man.
Edit: If you are in need for some GFX for this thread, let me know and I'll see what I can brew up for you.
Click to expand...
Click to collapse
I hope I can keep this great little device going a little longer, however it will probably get tough. I did a repo sync earlier today and things are starting to break. The last few builds haven't even booted. With humberos no longer maintaining the i9000 and aries-common, I've had to fork the aries-common repository to try to keep going. The only upside of this is that I now have a little bit more freedom and can add things in if I want to.
Thanks for the offer of the graphics. If I can get a new build working, then I'll probably take you up on your offer. I think I've traced the problem but I'll have to wait and see...
For anyone that is trying/has tried this out, I'd be very curious on the status of the GPS on the T959V. I'm interested in creating the sepolicies for it so we can put selinux into enforcing mode but I don't want to go to the effort if it doesn't even work right now.

I've downloaded the zip and one of the smaller Gapps packages...won't be able to flash until early next week...I'll be out of town...will post results later...thanks for keeping this phone current.

New Build Uploaded!
Download is still at the same link as before, just use the 2015-07-03 build
I managed to find out why my new builds hadn't been booting - it was because the syntax for using a custom kernel toolchain had changed.
Anyway...
Changelog for 07/03/2015 Build
Newer Omni source
Added volume controls and flight mode toggle to power button menu
Added Bigmem option. This increases available RAM by ~20mb but breaks 720p video recording. Humberos created the kernel setup and I integrated a toggle for it into Advanced device settings.
Selinux is now in enforcing mode. I had to modify the GPS startup to have any chance of getting here. Please let me know if it still works/doesn't work/never worked
On another note, I've had a look at re-implementing TV-Out support. It doesn't look promising as several of the functions in the android frameworks that it used have been tweaked.... Still working on it but don't hold your breath.
Also, if somebody could test dock audio that would be appreciated. I don't have any way of testing it. If it doesn't work, I do have an idea on how to fix it (for those interested, another almost-aries device, the Infuse 4G, had to modify things slightly to get it to work. I would try to emulate their solution).

Omg download nowwww....thanks my friend

Alright, I'm having some issues on the latest build with notifications and the lockscreen. I'm still working on tracing down the reason for the problem...

DickyG said:
I've downloaded the zip and one of the smaller Gapps packages...won't be able to flash until early next week...I'll be out of town...will post results later...thanks for keeping this phone current.
Click to expand...
Click to collapse
Hello, im a user of a t959v. And I've been using this rom for three days. Everything is fine and very smooth on this rom except that, I can't install anything from the playstore. I always get (cannot install app due to an error 963). And Ive tried all the gapps, even the new link provided but still no luck.

billowusu47 said:
Hello, im a user of a t959v. And I've been using this rom for three days. Everything is fine and very smooth on this rom except that, I can't install anything from the playstore. I always get (cannot install app due to an error 963). And Ive tried all the gapps, even the new link provided but still no luck.
Click to expand...
Click to collapse
Good to hear that that's its (mostly) been working for you. I was hoping that the gapps problem was just me
Out of curiosity, which of the alternate gapps did you try?
A brief google of the error brings up a couple of possibilities...
Try an older gapps version. The ones from devloz on the i9000 thread devloz and the oldest revision for 5.1.1 are probably your best bet. Please be aware that Google Play store will automatically update!!! In order to prevent this, you will need to create a folder called "com.android.vending-1.apk" in /data/app (use a root explorer such as ES File Explorer or adb if you know how). If a file with that name already exists, delete it first.
Another thing to try would be to unmount your sdcard first before trying to install an app. I know, its a terrible work-around but it should work. This is because the error is that Google Play is trying to save some data on your sdcard but then for some reason it fails (I'm not sure why).
I'll hopefully get around to seeing if its a permissions problem after I find out what's been causing the issue with the notifications on the latest build.
P.S. Does the GPS work?

Early update...
...ROM flashed fine...a little slow to boot...about 3 minutes...but it booted.
...Gapps flashed fine...used 20150513_5.1.x package
...Installed Super SU (although I don't think that's necessary) and TB.
...So far only gave a quick test to camera and web browser...no problems.
...Am now in the process of re-installing user apps and data from TB...this will take a while.
When I'm done with that, I use Link2SD to link most of my user files to the SD card. After that is all set up, I'll test stuff like GPS, root access, etc. I'll post back later...maybe tomorrow.
But so far so good.

OK...I did some testing tonight and here's some results.
Working:
.it boots
.root
.browser
.playstore
.camera
.link2sd (about 180 mb free in internal)
.camera
.wifi
.email
Nor working:
.bluetooth
.google search/voice search
.just about all the rest of the Gapps
.tons of force closes including Maps so can't test GPS
Won't be able to do anymore testing until next week.

DickyG said:
OK...I did some testing tonight and here's some results.
Working:
.it boots
.root
.browser
.playstore
.camera
.link2sd (about 180 mb free in internal)
.camera
.wifi
.email
Nor working:
.bluetooth
.google search/voice search
.just about all the rest of the Gapps
.tons of force closes including Maps so can't test GPS
Won't be able to do anymore testing until next week.
Click to expand...
Click to collapse
Alright, thanks very much for the update. I'll do some more testing here and see if I can solve anything. For me, bluetooth file transfers to the phone work but not from the phone.
I've been looking at the notification "error" where the lockscreen notifications do not appear correctly. It appears to have been introduced upstream with a merge. I'm having difficulty finding out exactly what changed and since no errors are being thrown in the logcat, it could be a while...
For testing the GPS, there's an app from the Play Store called GPS Test which does a nice job of showing satellites and whether or not you have a lock on them.

you're the man!
nice one! its nice that this device are still alive.! and now were on 5.1

DerPuGNa said:
nice one! its nice that this device are still alive.! and now were on 5.1
Click to expand...
Click to collapse
No, it should be Humberos is the man! I basically re-hashed his code for the i9000 and used bits and pieces from people like Bhundven, noiphonehere, maxfierke, Dao, and FB to get things to work properly.
For a status update, I figured out the lockscreen notification problem. I have a new build being made that I hopefully will be able to upload in the next couple of days (internet dependent). TV-Out looks totally broken as the proprietary blobs no longer function. I don't have the know-how to make ugly hacks to get them to work. The new build will have SElinux in enforcing mode and have the different GPS initialization (like the last build) until someone tells me that it doesn't work
Uh-oh, looks like I jumped the gun.... Having problems once again

Any updates on getting the play store to work? I have searched, downloaded, and tried every gapp made for 5.1. I found that I can load any app on the rom, if I get the APK version of it.

AgainstTheFlow said:
Any updates on getting the play store to work? I have searched, downloaded, and tried every gapp made for 5.1. I found that I can load any app on the rom, if I get the APK version of it.
Click to expand...
Click to collapse
Darn, so its still not working. Not surprising. I've been struggling on the notification issue and am at my wit's end as to what the problem is. I don't think its only our phone as several i9000 users have been reporting it as well. Whether it is only the first-gen Galaxy S series that is having the problem or not is anyone's guess. My programming skills are insufficient to fix the issue!
I'll have another look at gapps over the next couple of days and see if I can figure out a combination that works 100% of the time.
I'm assuming the error message is still 963 or does it silently fail now? Its probably related to the fact that we have only an external sd card and no internal sd card like most devices...
All the problems with the notifications that I've found are:
Only one notification will show up at a time
Large notifications such as the music player do not render properly. They are cut off at the normal notification size and occasionally it seems as if there are two layers there (one for the small version, one for the bigger version) (see attached picture, taken with VLC as the media player, but also appears with Apollo)
Notifications don't always show up. A little icon appears in the top left corner of the status bar but no notification is present. Seems hit or miss
The words No notifications appears in the lockscreen just above the clock when there are no notifications. Otherwise, a notification (and only one) which can't be clicked covers part of the clock

SRGX2 Rom for the Life One X2 Mini

SRGX2 for Life One X2 MiniThis Rom Is a Stripped down modified version of the Life One X2 Mini stock Rom.
NOTE: After installation give Launcer 3 notification permission and update Google Play Services (click on the notification).
(Please remember I do this in my free time and with my own money. If you like it please hit the thanks button)
Mods:
Malware removed
Build.prop Tweaks
Oreo Launcher
Camera app replaced by OpenCamera
File manager replaced by MiXplorer
To do list:
Build wifi drivers into the Kernel
Strip down rc scripts
What Works:
Boots
Calls
SMS
Data
GPS
Wifi
Bluetooth
Audio
Video Playback
Sensors
Led
Camera
Flash
Fingerprint
Not Working Yet:
(You tell me)
Downloads:
Current Build: https://www.androidfilehost.com/?fid=673956719939824825
Builds: https://www.androidfilehost.com/?w=files&flid=239712
Patches: https://www.androidfilehost.com/?w=files&flid=254440
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhTERvcGxlSkZFa2M/view?usp=sharing
Kernel: https://github.com/vampirefo/android_kernel_blu_kernel_x2 (Special thanks to @vampirefo for the kernel source)

Screenshots: comming soon

Changelog
Version: Testing
Build: 01072018211020
Initial release
Version: rc1
Build: 01142018205847
switched to stock theme
Version: 1.1.0
Build: 02182018215948
rebuild off of the 01/04/2018 update
Version: 1.1.1
Build: 02242018165134
fixed mobile data bug
Version: 1.1.2
Build: 03032018224915
changed DPI to 441
added stock calendar app
added stock calculator app
add stock clock app

Troubleshooting

reserved

Does quick charge work?

Been running for a couple of days now without issue.

cyrusharding said:
Does quick charge work?
Click to expand...
Click to collapse
Yes it works, I've beeen using 2 QC3 chargers with no problems at all.

Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!

cyrusharding said:
try "dogfood spotify" i had same issue and got that to work on the lineageos 13 blox2mini ROM.
Click to expand...
Click to collapse
Interesting, didn't know that exists. I currently just download off of http://download.spotify.com/android/SpotifyAndroid.apk

enduo said:
Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!
Click to expand...
Click to collapse
I'm doing my mods on the precompiled factory rom. If you go to the Lineage OS thread, Vampirefo has a link to the device and vendor tree he created for his rom. I am considering having two versions of my rom for the Mini. A light theme (stock) and dark theme the one that is out now. Right now the rom is only in testing stage. I enjoy seeing your interest in learning how to do what I am doing, the more developers the better.
Thanks for you feedback, here are some helpful links. I am a Linux user and my links may be geared toward Linux, some things can be done in Windows, but some require Linux.
Lineage OS for the Mini: https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814 (has links to his device and vendor tree)
How to compile an Android kernel: https://forum.xda-developers.com/le-2/how-to/guide-compiling-64-bit-android-kernel-t3512749 (I'm still trying to locate the Mini kernel source)
Tool to unpack and repack a rom: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
tool for unpacking apks: https://ibotpeaches.github.io/Apktool/
I hope these help you and enjoy

srgrusso said:
I'm doing my mods on the precompiled factory rom. If you go to the Lineage OS thread, Vampirefo has a link to the device and vendor tree he created for his rom. I am considering having two versions of my rom for the Mini. A light theme (stock) and dark theme the one that is out now. Right now the rom is only in testing stage. I enjoy seeing your interest in learning how to do what I am doing, the more developers the better.
Thanks for you feedback, here are some helpful links. I am a Linux user and my links may be geared toward Linux, some things can be done in Windows, but some require Linux.
Lineage OS for the Mini: https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814 (has links to his device and vendor tree)
How to compile an Android kernel: https://forum.xda-developers.com/le-2/how-to/guide-compiling-64-bit-android-kernel-t3512749 (I'm still trying to locate the Mini kernel source)
Tool to unpack and repack a rom: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
tool for unpacking apks: https://ibotpeaches.github.io/Apktool/
I hope these help you and enjoy
Click to expand...
Click to collapse
This is awesome thanks so much!! I use Windows on a daily basis but I do have a pretty good knowledge about Linux and have set up a build environment in for Android. These links should help me understand what I am missing. I am also happy to continue testing and give you feedback on this ROM as it is currently my daily driver.

New Rom out. It has the stock theme, other than that it is the same.. I haven't decided if I'm going to build two Roms or have the theme be a patch. Maintaining all the different variants of the Rom are getting to be very time and space consuming.
https://www.androidfilehost.com/?fid=889964283620778170

Strange question, but on the original stock rom, I started having issues with the Package Access Helper not working, while installing updates for Paypal, and just straight up trying to install Spotify, even the APK. I did a full factory reset, still did not work. I also installed the custom rom over at BLOX2.com, and the Package Access Helper still would stop working, even after clearing data/cache. I'm just curious if you know if your rom will fix that issue?

Requia77 said:
Strange question, but on the original stock rom, I started having issues with the Package Access Helper not working, while installing updates for Paypal, and just straight up trying to install Spotify, even the APK. I did a full factory reset, still did not work. I also installed the custom rom over at BLOX2.com, and the Package Access Helper still would stop working, even after clearing data/cache. I'm just curious if you know if your rom will fix that issue?
Click to expand...
Click to collapse
Is this without root? I don't know if my rom will fix that, I never used the Paypal app. Your welcome to try and let me know. Also there is LineageOS 13 for the mini which has been built from source.
https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814

New rom rebuilt from the 01/04/2018 update.
v 1.1.0

There is a problem with the latest version of SRGX2. Mobile data doesn't work. I work on it this weekend and keep everyone updated.

Here is the fixed rom.
https://www.androidfilehost.com/?fid=818070582850494825

Good news I was able to get Android File Host to make the Life One X2 an official device. I have made a request for the Mini too. For now all the files will be under the Life One X2 device.
Updated rom: https://www.androidfilehost.com/?fid=673956719939824825
It includes the stock Calendar, Clock and Calculator apps. I changed the DPI to 441. Let me know if anyone has any problems with the Playstore. I know that there has been some requests for the stock Camera and file Manager apps. It's hard to please everybody so I added a patch section which may please some.

[ROM][UNOFFICIAL][7.1.2] Unlegacy Android Grouper Nougat [Nexus7 WIFI][12NOV2019]

I'm skipping 90% of words here because if you are here I assume you know what you are doing. And you can either Google, use the search button, or ask.
This is a private work of mine, that I use normally on my spare device. Supported as is.
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Known issues:
- Camera not working
INSTRUCTIONS
Clean Flash
Download The ROM & GApps (pick latest one in drive, I use opengapps)
Wipe: System, Data, Dalvik, Cache
Flash ROM + GApps (Opengapps pico)
Reboot & Enjoy
Dirty Flash
Download the ROM
Wipe: Dalvik and Cache
Flash ROM (+Magisk if rooted previously or if want root)
Reboot & Enjoy
Download Folder Link:
https://drive.google.com/open?id=1D0Od55prO_Q_e8RY6QkZ-DjO36Qb188X (Pick Grouper)
Credits to:
Unlegacy Team

Initial Release:
May Security Patch

Can't download the ROM 404 error

JT1510365 said:
Can't download the ROM 404 error
Click to expand...
Click to collapse
https://drive.google.com/open?id=1usLQT6qkg8eUe3FwOvXXHRRaBF8VxR5H
This is the direct link for latest, thanks for trying out! cheers!

KiD3991 said:
https://drive.google.com/open?id=1usLQT6qkg8eUe3FwOvXXHRRaBF8VxR5H
This is the direct link for latest, thanks for trying out! cheers!
Click to expand...
Click to collapse
Which kernel you use?

TureX said:
Which kernel you use?
Click to expand...
Click to collapse
It's stock thus far, but I am testing out other things.

So I assume F2FS can't work, right?

New update:
Direct Link: https://drive.google.com/open?id=1ObhbiIgSwxIS3fDfb2AREEx_6syQSpi_
Consider this pre-June patch build. And no F2FS doesnt work @Stylez Ray. I am too noob to implement it. (For now)

Guys, I apologize but this month's upload will be slightly delayed due to my work and studies having major setbacks. Again, I apologize.

New update:
Direct Link: https://drive.google.com/open?id=1LkbL1TEupSYUY2zA_L_NklEP-j9xWDUP
Changes are minimal in this build other than using a better build machine lol

Thank's good job !!!
All works fine magisk v19.3, dax_axon7_v1.6.1.zip
I return on Andisa rom 7.1.2 freeze and lags horrible

This is really awesome, no more random system freezes like in the first official UA builds. Thanks a lot, it really makes this ancient device useful again ?

@KiD3991 hello, maybe you would like to join Unlegacy team as Tegra 3 developer?

Slightly odd request at this stage probably but is there any chance off an unlegacy lollipop build for grouper? with a 3.4 kernel please?
actually strike that the marshmellow build will be just fine
but does anyone know if shared memory is implemented in a chroot I get -
sysctl -w kernel.shmmax=268435456
returns cannot stat /proc/sys/kernel/shmmax: No such file or directory

New build up, sorry I was really unavailable.
I tried fixing a couple of things, see if it helps, do tell me though, mention me and I will show up.
Direct link: https://drive.google.com/open?id=1g4eu0ulizZ8ZO44hRjMUnIyEYIyWQL9t
Changelog:
Minor bug fixes
July Security Patch

curioct said:
Slightly odd request at this stage probably but is there any chance off an unlegacy lollipop build for grouper? with a 3.4 kernel please?
actually strike that the marshmellow build will be just fine
but does anyone know if shared memory is implemented in a chroot I get -
sysctl -w kernel.shmmax=268435456
returns cannot stat /proc/sys/kernel/shmmax: No such file or directory
Click to expand...
Click to collapse
Interesting for the marshmellow build. Does it have to be UL?
For the bottom one you gotta dig the right directory.

KiD3991 said:
Interesting for the marshmellow build. Does it have to be UL?
For the bottom one you gotta dig the right directory.
Click to expand...
Click to collapse
Hmm I've kind of slipped off this little project for a while I'm trying to use it with the newer kali builds chroot (requiring the 3.4 kernels I believe) in the hope of having a device with WiFi monitor mode available but I was running in to that shared memory issue with services such as postgresql etc think is was causing me issues with csploit too but as I say not really looked at it in a few weeks now.

curioct said:
Hmm I've kind of slipped off this little project for a while I'm trying to use it with the newer kali builds chroot (requiring the 3.4 kernels I believe) in the hope of having a device with WiFi monitor mode available but I was running in to that shared memory issue with services such as postgresql etc think is was causing me issues with csploit too but as I say not really looked at it in a few weeks now.
Click to expand...
Click to collapse
OMG SAME! I was trying with the Kali too on my other device. It was kinda confusing no doubt

This rom is working great, thanks. Please can anyone help me with how to install browser on this rom, as the USB is not working.

did u tried to activate the debug mode , in dev settings? if that doesn't work .. you have to switch the drivers by yourself, in windows ( devices manager ) from ADB Bootloader to Storage Device .. for your Nexus 7

[ROM]|SM-T520|SM-T900|[UNOFFICIAL] LineageOS 17.1 | Android 10

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
Special thanks to Exynos5420 team and LineageOS for all the sources.
Use SM-T900 build at your own risk. I can't guarantee you it will work, because I have no device to test it on.
Work
Almost everything
It has pretty much the same functionality as Lineage 14.1
Known Issues
Built in mic not working
USB problems
You tell me...
Installation:
1. Flash latest official Samsung Firmware with ODIN
2. Flash latest TWRP Recovery: SM-T520 - SM-T900
3. Backup all partitions
4. Wipe Cache and Data
5. Install ROM.ZIP
6. Install latest GApps (ARM/Android10) https://opengapps.org/
7. Reboot and Enjoy
8. Optional: Install Magisk
For SM-T520 TWRP recoveries 3.1.1.0 and older will not flash this rom ending up with error 7: incompatible device.
Make sure to flash TWRP mentioned above.
Download:
SM-T520
SM-T900
I ll probably create builds with updated security and device code patches occasionally.
Enjoy fresh new Android!
Sources:
https://github.com/LineageOS (LineageOS 17.1)
https://github.com/exynos5420/ (Kernel, Device, Vendor)

Damn!! Just installed and working.
Really good work! Thanks!!!!
i found a bit problem, starting android it loops between voice assistant and set lock for tablet. i needed connect earphones with microphone to finish voice assistant configuration and then it continued.
Thanks for rom!

@TechDriver can You build a LineageOS 17.1 ROM for SM-T900 who is used the same Exynos5420 CPU?
If is necessary I can be a beta tester.

manix01 said:
@TechDriver can You build a LineageOS 17.1 ROM for SM-T900 who is used the same Exynos5420 CPU?
If is necessary I can be a beta tester.
Click to expand...
Click to collapse
You got it there try it out!

Larision said:
Damn!! Just installed and working.
Really good work! Thanks!!!!
i found a bit problem, starting android it loops between voice assistant and set lock for tablet. i needed connect earphones with microphone to finish voice assistant configuration and then it continued.
Thanks for rom!
Click to expand...
Click to collapse
Did you install on the t520 or the t900? Did you really go back to the Samsung official build first? (I'm on t900 lineage 14.1)

pjotrski1000 said:
Did you install on the t520 or the t900? Did you really go back to the Samsung official build first? (I'm on t900 lineage 14.1)
Click to expand...
Click to collapse
You don't need to go stock, just backup your data using TWRP and follow installation steps above. I am little unsure about build for T900 because I do not own this device, so I wait for someone who can report me if it works or not.

@TechDriver Clean flashed 17.1 over 14.1 without flashing stock on T900 using twrp-3.5.1_9-0 and it flashed great. I plugged in a headset but my Hey Google was already recorded and didn't give me any trouble. I don't know what would have happened if I hadn't plugged in the headset. Play Store does not recognize my already purchased apps. This usually means something is not right and I wonder if not flashing stock first is related to this? Can be very smooth but can be a little glitchy as well. Still experimenting and trying things. Bluetooth Keyboard and Mouse work great. Thank you for this.

kb8no said:
@TechDriver Clean flashed 17.1 over 14.1 without flashing stock on T900 using twrp-3.5.1_9-0 and it flashed great. I plugged in a headset but my Hey Google was already recorded and didn't give me any trouble. I don't know what would have happened if I hadn't plugged in the headset. Play Store does not recognize my already purchased apps. This usually means something is not right and I wonder if not flashing stock first is related to this? Can be very smooth but can be a little glitchy as well. Still experimenting and trying things. Bluetooth Keyboard and Mouse work great. Thank you for this.
Click to expand...
Click to collapse
It has probably something to do with missing play protect certification. I will try to sign device for certification but need someone with T900 who will cooperate with me. For now easiest way to avoid problem is going to browser version of play store and installing paid app to specific device from there. It should work fine. Also thanks for testing and reporting that T900 build works.

Just for understanding, these are still 32 bit builds, vor did you switch to arm_64?

@TechDriver SELinux is not enforcing. That may be why Google Play does not recognized my purchased apps. Installing purchased apps trick from Google Play on the web worked as expected. Booting tablet, it does not accept passcode on the first try, but works on second try. This is repeatable. I will be happy to be your T900 tester if you make some test builds.

hamudistan said:
Just for understanding, these are still 32 bit builds, vor did you switch to arm_64?
Click to expand...
Click to collapse
Exynos5420 is 32bit SoC. It doesn't support arm64

@TechDriver The pass code works the first time if you are not impatient and click the accept arrow before the last number changes to a dot. There is a delay and the passcode entry is laggy and you have to be patient for a few seconds. twrp-3.5.1_9-0 is able to back up and restore 17.1 with no problem.

@TechDriver The first login with PIN after booting will fail. The second and future screen saver logins will work with the caveat that you are patient until the last number turns into a dot.
Pixel launcher does not work correctly with mouse clicks and has a focus graphics glitch. It works right as long as you don't click the mouse. If you click with the mouse to open a group of icons in a folder it leaves a residual grey box behind. You can see this same grey box where the PIN numbers appear on the screen saver as well. I changed to Nova Launcher and the problem improved with the grey box occurring if I open the icon folder and actually open an app but then disappearing on moving into a different folder. This is all with the exception of the PIN screen saver which causes the same grey box on both launchers. Something is not quite right with the graphics using mouse.
I mostly use this tablet with keyboard and mouse and Nova is more acceptable now. I prefer Nova Launcher anyway as it is much better at using the whole screen.
The camera is extremely basic. Open Camera seems to be an improvement. Any Google Camera port available that might work?

Just to make things clear, I am not developer of code and not skilled enough to make changes in it. For this job, there is team exynos5420 and other cool contributors to make device sources. I use their device sources from exynos5420 and LineageOS github to build together final product... Rom.zip you install on device. I can't fix bugs, i only can wait until some contributor fixes it and I will build rom with fixes and updated security patches included.

@TechDriver Got it. Will the devs be watching this thread for feedback?

kb8no said:
@TechDriver Got it. Will the devs be watching this thread for feedback?
Click to expand...
Click to collapse
I am unsure about that, most of original devs for n2awifi and v2awifi stopped developing code for this devices. Keep an eye on exynos542X github for new commits.

First of all I want to thank you for the this ROM.
I tried this ROM with the latest TWRP version for two days and I want to inform that it is working good with some small non-conformities:
I had some random reboots and the system crashed and freezing
After rebooting there is a long time after entering the unlock pattern, sometimes it is necessary to enter the pattern several times.
I have installed ROM, gapps nano rebooted and after that install Magisk 22.1
my model is SM-T900

@TechDriver ,Great work on this build! Never thought I would see this accomplished. Many thanks and keep up the good work. This is fully usable with Nova beta 7.0.27.

Works perfectly on my T900, many thanks! Keep up the good work!

stanl56 said:
@TechDriver ,Great work on this build! Never This is fully usable with Nova beta 7.0.27.
Click to expand...
Click to collapse
Can you provide a link for this latest Nova beta? APK mirror seems booked.
Nova 7.0.27 Works smoother and scrolling and moving icons is better. PIN screen on first login is same problem and will not work on the first try. Mouse clicks and mouse related screen painting remains an issue. If you don't use a mouse you may not notice any problems other than first login. Come to think about it, 7.1 had issues with the mouse most noticeable when I used Collabora and I had attributed it to the app.

Database Info

welcome