Based on Demetris' LOS 14.1, with :
Android security patch level updates, currently 2020-02-05
tracking LA.BR.1.2.9 from CAF, currently 1.2.9_rb1.44
WIP upstream with linux-stable, currently upgraded from 3.10.49 to 3.10.68 3.10.75
SELinux enabled (better security, SafetyNet & PlayStore should be ok, if not check @tess1 clear caches post )
2018 fixes : MTP, battery consumption, camrecorder crash, wifi, OpenGL ES version, dualsim 6045K (update to MM first), lid & proximity sensor
known problems :
camrecording low brightness
mobile internet connectivity loss and battery drain after a while (days) : toggle airplane mode and back, or reboot
new problems : none known at the moment, but the ROM is not so thoroughly tested before publication
How to investigate and report problems :
sudo adb shell dmesg > dmesg.txt
sudo adb logcat > logcat.txt
sudo adb logcat -b radio > radio.txt
Credits : @FireLord, @Demetris, @Unjustified Dev and all the giants whose shoulders we stand upon !
Source code : Kernel | Device | Vendor trees | Local manifest : View attachment idol3.xml
Changes since previous build : see the build release post
Downloads : lineage-14.1-20200226-UNOFFICIAL-idol3.zip | other releases
Kernel alternative (cam might not work since 20190619 build) : overclocked kernel by @DepressedHedgehog
Reserved
Thanks a lot for sharing this build. Now that the method for restoring our phones to stock has been taken away from us, I'm hoping that more people will jump in and try to solve some of the few remaining issues with this ROM.
Personally I'd like to figure out why the Play Store is installing old versions of certain apps and listing other apps as being incompatible while they can be still sideloaded without any problem. I've found many threads on XDA with people complaining about the same issue but no solution that worked so far. Is this an issue with opengapps, or bad entries in the build.prop? I've compared with the original build.prop from stock 6.0.1 and tried changing values around but no success.
Also battery life seems a lot shorter with Nougat, and there is no way to find out which apps/processes are being power hungry as you have already pointed out.
Issues aside this ROM still makes this phone quite usable and stable compared with other ROM's I have tried so good job and I'm looking forward to testing out new builds.
new thread - we're open for business!
@vknecht once again, thanks for your continued efforts... I tried your Sept 12 release with opengapps Sept. 12 as well - the Play store continues to thwart our efforts in the same manner.
@upyisfar I found that the battery drain during sleep could be reduced to almost nil with the following settings:
- turn off WIFI during sleep - Settings-> WIFI -> Gear Icon -> Keep WIFI on during sleep -> change to....
- turn off Emergency Broadcasts - Settings -> ...More ->Emergency Broadcasts -> Uncheck all
20180918 build : add ptt_socket_app for better wifi and battery
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Code:
09-19 15:14:35.466 1192 1344 E BatteryStatsService: no controller energy info supplied
09-19 15:14:35.748 1192 1212 E BatteryStatsService: power: Missing API
09-19 15:14:35.762 1192 1344 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
Thanks @upyisfar @tess1 for the feedback, keep us posted with your findings...
@vknecht
1. Just tried something... reinstalled 7/18 build where all of the play store program installations were working and then overlayed it with OTA 9/18 which then led to PLay Store blocking installation of many apps ("device isn't compatable" error) - I recall that the build after 7/18 included 25 fixes/commits. Not easy to track it down but could the problem be from one of those fixes/commits?
2. The proximity sensor (tsl2772-ps) error was earlier reported as either missing a driver or needing a shim. Is this a file that can be pulled from Marshmallow and put into this ROM?
Battery updates to follow
vknecht said:
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Click to expand...
Click to collapse
Interesting. How do we know if those changes were merged into the LineageOS's code repo?
vknecht said:
[*]SELinux enabled (helps with safetynet basicIntegrity test ; also better security, but some glitches here and there)
[*]new problems : probably due to SELinux now in "enforce" mode, like battery stats
Click to expand...
Click to collapse
I've installed your new build last night and I've set my kernel to run in permissive mode (Magisk SELinux Manager module) and safetynet basicIntegrity test still passes just so you know. Battery life now feels more comparable to what I get in stock MM. Not sure if this due to SELinux being switched to permissive or the the changes that you have made.
What build environment are you using to build your ROM's, I'm trying to build on Debian stable following your instructions here and keep getting compilation errors.
tess1 said:
@vknecht
1. Just tried something... reinstalled 7/18 build where all of the play store program installations were working and then overlayed it with OTA 9/18 which then led to PLay Store blocking installation of many apps ("device isn't compatable" error) - I recall that the build after 7/18 included 25 fixes/commits. Not easy to track it down but could the problem be from one of those fixes/commits?
Click to expand...
Click to collapse
I thought the 20180905 build ruled out the august kernel updates as the breaker but in fact I should and will retry kernel from july with SELinux enabled ; if it's still not OK then I guess the cause is LOS august update...
tess1 said:
2. The proximity sensor (tsl2772-ps) error was earlier reported as either missing a driver or needing a shim. Is this a file that can be pulled from Marshmallow and put into this ROM?
Click to expand...
Click to collapse
iiuc the hint is that we need either a HAL/framework wrapper OR reuse stock Lollipop driver+shim.
I'm sorry I don't know much about this low-level androidy stuff yet and don't have much time atm to focus on it.
upyisfar said:
Interesting. How do we know if those changes were merged into the LineageOS's code repo?
Click to expand...
Click to collapse
I think if it was in LOS it should appear here : https://github.com/LineageOS/android_system_extras/commits/cm-14.1/ext4_utils
upyisfar said:
I've installed your new build last night and I've set my kernel to run in permissive mode (Magisk SELinux Manager module) and safetynet basicIntegrity test still passes just so you know. Battery life now feels more comparable to what I get in stock MM. Not sure if this due to SELinux being switched to permissive or the the changes that you have made.
What build environment are you using to build your ROM's, I'm trying to build on Debian stable following your instructions here and keep getting compilation errors.
Click to expand...
Click to collapse
I'm using Fedora 28 ; note that you'd have to update the local manifest ($ANDROID_ROOT/.repo/local_manifests/idol3.xml) using given kernel/device/vendor trees as linked in OP, so at the moment it should look like :
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="vknecht/android_device_alcatel_idol3" path="device/alcatel/idol3" remote="github" revision="fix-ptt_socket_app" />
<project name="vknecht/android_kernel_alcatel_msm8916" path="kernel/alcatel/msm8916" remote="github" revision="upstream-lxstable-cafrb144" />
<project name="vknecht/proprietary_vendor_alcatel" path="vendor/alcatel" remote="github" revision="fix-ptt_socket_app" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
</manifest>
(to use july kernel change revision to "upstream-lxstable").
For idol3 build environment setup help, feel free to send me private messages or join #idol3 on Freenode, or maybe even create a thread, for the more we are able to build, the better...
vknecht said:
I thought the 20180905 build ruled out the august kernel updates as the breaker but in fact I should and will retry kernel from july with SELinux enabled ; if it's still not OK then I guess the cause is LOS august update...
iiuc the hint is that we need either a HAL/framework wrapper OR reuse stock Lollipop driver+shim.
I'm sorry I don't know much about this low-level androidy stuff yet and don't have much time atm to focus on it.
Click to expand...
Click to collapse
1 Just tried the 9/05 build --> same play store issue --> August updates maybe problematic
2 Fair enough... I don't know enough but am willing to beta test along the way
It is all in progress...
tess1 said:
1 Just tried the 9/05 build --> same play store issue --> August updates maybe problematic
2 Fair enough... I don't know enough but am willing to beta test along the way
It is all in progress...
Click to expand...
Click to collapse
I've tried the july 3.10.68 kernel (used in 20180718 and 20180905 builds) with current device/vendor trees, and still G compat problems, so it leaves the Android/LineageOS diffs from 2018-06-05 to 2018-08-05 patch levels (afaik there was no 2018-07-05 for LOS 14.1 and there's no 2018-09-05 yet).
20180924 build : 2018-09-05 android security patch level
Only change is Android/LineageOS framework (repo sync) for 2018-09-05 update
Too sad, it doesn't seem to solve the some-apps-in-proeminent-vendor-store incompatibility problem...
@upyisfar : I've wondered about "the method for restoring our phones to stock has been taken away from us", what did you mean ?
While, too bad, the Sugar utility (which had my preference) now fails on a "site not found" error (maybe should try a fresh install, why not in Wine), I still could reset by using the "Panasonic Eluga Switch" utility then the "Mobile Q upgrade" (~1 hour total, with 100Mbs connection) to go back to stock.
lineage-14.1-20180924-UNOFFICIAL-idol3.zip | or OTA zip
Q
vknecht said:
I've wondered about "the method for restoring our phones to stock has been taken away from us", what did you mean ?
While, too bad, the Sugar utility (which had my preference) now fails on a "site not found" error (maybe should try a fresh install, why not in Wine), I still could reset by using the "Panasonic Eluga Switch" utility then the "Mobile Q upgrade" (~1 hour total, with 100Mbs connection) to go back to stock.
Click to expand...
Click to collapse
The Sugar utility was what I was referring to. Haven't had any success with the Mobile Q though, I always get a "check your internet connection" message or something like that. The MM 6.0.1 ROM posted by The Marionette is close enough though. I don't expect Alcatel to push more OTA updates for this device anyway.
I'm sticking with your build of Nougat now that the battery drain issue has gone away. I don't mind manually transfering the APK's from another device to my phone, for now at least. I have managed to set up my build environment (was missing a dependency) and will be producing a test build soon to see if I can fix a thing or two. In the mean time I will happily upgrade to the new build that you have just posted. Thanks!
upyisfar said:
The Sugar utility was what I was referring to. Haven't had any success with the Mobile Q though, I always get a "check your internet connection" message or something like that. The MM 6.0.1 ROM posted by The Marionette is close enough though. I don't expect Alcatel to push more OTA updates for this device anyway.
I'm sticking with your build of Nougat now that the battery drain issue has gone away. I don't mind manually transfering the APK's from another device to my phone, for now at least. I have managed to set up my build environment (was missing a dependency) and will be producing a test build soon to see if I can fix a thing or two. In the mean time I will happily upgrade to the new build that you have just posted. Thanks!
Click to expand...
Click to collapse
@upyisfar
Just 3 weeks ago, I was able to restore (in Canada) my Idol 3 to stock MM using Mobile Upgrade (I think it was version 5.1.7 as 5.1.8 would not do anything).
Here is an upload link:
5.1.7:
https://mega.nz/#!KmogkYAa!e5y6ZSM987quN6bTYRNWnZuNQSBnCjANMglrhB4rtHo
5.1.8:
https://mega.nz/#!OuhEGaaQ!g6mH6RE7v7MEGSI5-uWsr_t4MZCX3qh1fmCtHzhHptI
I put the phone into download mode and it took about 30 minutes.
---------- Post added at 10:45 PM ---------- Previous post was at 10:39 PM ----------
@vknecht
vknecht said:
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Code:
09-19 15:14:35.466 1192 1344 E BatteryStatsService: no controller energy info supplied
09-19 15:14:35.748 1192 1212 E BatteryStatsService: power: Missing API
09-19 15:14:35.762 1192 1344 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
Thanks @upyisfar @tess1 for the feedback, keep us posted with your findings...
Click to expand...
Click to collapse
re: add ptt_socket_app for better wifi and battery
Would it be possible for you to list the (hopefully few) files and any edited files that you put into this build and the corresponding locations so that I can graft them onto my 7/18 build?
tess1 said:
Just 3 weeks ago, I was able to restore (in Canada) my Idol 3 to stock MM using Mobile Upgrade (I think it was version 5.1.7 as 5.1.8 would not do anything).
Here is an upload link:
5.1.7:
https://mega.nz/#!KmogkYAa!e5y6ZSM987quN6bTYRNWnZuNQSBnCjANMglrhB4rtHo
5.1.8:
https://mega.nz/#!OuhEGaaQ!g6mH6RE7v7MEGSI5-uWsr_t4MZCX3qh1fmCtHzhHptI
I put the phone into download mode and it took about 30 minutes.
Click to expand...
Click to collapse
OK. I was wondering if Alcatel was geo-blocking some countries seeing how some people have success and others don't. I'm in Canada too so I guess that isn't the issue. For now I'm more interested in trying to find a solution to the opengapps compatibility problem.
---------- Post added at 11:04 PM ---------- Previous post was at 10:51 PM ----------
tess1 said:
[MENTION=9435528]
re: add ptt_socket_app for better wifi and battery
Would it be possible for you to list the (hopefully few) files and any edited files that you put into this build and the corresponding locations so that I can graft them onto my 7/18 build?
Click to expand...
Click to collapse
See these commits https://github.com/vknecht/propriet...mmit/f84888778905c179e0d49d7587bc5467248e4b01 and https://github.com/vknecht/android_...mmit/dc64e2c79616e33640a2680451e2fe5ab0152d89
... and the workaround for disabling the bogus 3rd camera mode
https://github.com/vknecht/propriet...mmit/b57afd7960943e0dc8f0c593ae25cb74b5351a3f
6045K / dualsim / multisim
Code:
idol3:/ # setprop ctl.start ril-daemon1
Does it make it better for you too ? (dunno if there's a non-root or GUI equivalent...)
Good news!
I have found the fix for the opengapps store compatibility issue.
I noticed in CPU-z that the reported OpenGL ES version was 1.0 so I added a line to my build.prop:
Code:
ro.opengles.version=196609
And now CPU-z reports version OpenGL ES version 3.1 and all my apps are available for download in the G store.
the value "196609" is decimal for hexadecimal 30001 (OpenGL ES 3.1). Ive seen a commit on github that says support for 3.2 was added but when I change the value to "196610", CPU-z still reports 3.1 not sure why..
vknecht said:
new problems : probablymaybe due to SELinux now in "enforce" mode, like battery stats
Click to expand...
Click to collapse
Appears to be working since the 2 latest builds, with SELinux set to enforce:
[/COLOR]
upyisfar said:
Good news!
I have found the fix for the opengapps store compatibility issue.
I noticed in CPU-z that the reported OpenGL ES version was 1.0 so I added a line to my build.prop:
Code:
ro.opengles.version=196609
And now CPU-z reports version OpenGL ES version 3.1 and all my apps are available for download in the G store.
the value "196609" is decimal for hexadecimal 30001 (OpenGL ES 3.1). Ive seen a commit on github that says support for 3.2 was added but when I change the value to "196610", CPU-z still reports 3.1 not sure why..
Click to expand...
Click to collapse
SECONDED - Confirmed fixed! and the Play Store also reports that my Device is Certified under Play Protect Certification.
Thank you upyisfar
vknecht said:
Code:
idol3:/ # setprop ctl.start ril-daemon1
Does it make it better for you too ? (dunno if there's a non-root or GUI equivalent...)
Click to expand...
Click to collapse
6045I single-sim here, can't test this, sorry.
BTW can you add "low brightness in camera video capture mode" to list of known issues in the op? thx
Related
About OmniROM
The goal of Omni is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality.
Omni is a chance to get involved, no matter who you are. Developers, whether you’ve been developing apps for a week, or ROM features for 3 years, you’re welcome. Users, we know you want to help out, and now you can – Omni actively encourages bug reports and feature requests, which can be added to our publicly accessible roadmap. What’s the point in giving you a ROM, and forcing you to not tell us about any bugs you find?
We also recognise how people use Custom ROMs – we’re all custom ROM users and developers ourselves – the argument that “nightlies are not for end users” is over-used, and no longer valid. We’ve found that the vast majority of users want to get nightly updates to their ROM. For that reason, nightlies aren’t a playground – nightlies are for new features that are finished. You should be able to expect the same stability and reliability from a nightly as you would from a “release” ROM, and can report any bugs that prevent this from happening.
We know not everyone wants to update their ROM daily, and you are free to update as frequently or infrequently as you like. Omni is about flexibility and giving users what they expect – and we are excited to see where the community goes with it.
Click to expand...
Click to collapse
Info from omnirom http://omnirom.org/general/android-l-omnirom-progressing/
Disclaimer
Standard disclaimer applies, your warranty is void, this may eat your dog or burn your house down, delete all your pictures, etc.
This is an early stage release so many things are broken since many patches and fixes haven't been imported from old branches yet.
How to install:
Reboot to recovey
A backup is Recommended, you're gonna loose all your data
Wipe data
Flash rom
Flash SuperSU 2.19 2.40 or up just after the rom
http://download.chainfire.eu/supersu -> This is IMPORTANT
Flash Netflix fix if you need it -> Download
Reboot
Around 5 minutes are required for the first boot
Reboot again to recovery
Flash Gapps (See below)
How to update from a previous version:
Reboot to recovey
Flash rom
Flash SuperSU 2.40 or up just after the rom http://download.chainfire.eu/supersu -> This is IMPORTANT (not needed anymore)
Flash Netflix fix if you need it -> Download
Reboot
Gapps download:
Check http://forum.xda-developers.com/android/software/gapps-consolidated-gapps-thread-t3064693
How to report a bug
Use the search function, if the bug has already been reported and I or another person has answered do NOT report it again. I'm tired of writing ten times the same thing.
A bug report function is embedded in XDA forum look at the top there's a section called "Bug Reports". Use it
Provide a logcat and/or dmesg. Search on XDA if you don't know how to get a proper log
Always provide which model you are using and other information that you think could be useful to solve the bug
Downloads:
This is an early preview with lots of bugs and not usable as a daily driver. You have been warned. Flash this only if you are sure about what are you doing.
Download folder: https://www.androidfilehost.com/?w=files&flid=21696
Starting from 20150506 I'm uploading automated builds: this means that they should be treated as nigthlies (I won't create a new one every 24 hours though). All the new files will be placed in the "Download folder" automatically, so, if no new changes from my part, I will NOT update the changelog. These builds will include all the updates and commits from official Omnirom repos plus my commits not yet merged for our tablets. Good luck
Commits: -> Updated to 5.1.1_r2
Necessary commits
In frameworks_native: https://gerrit.omnirom.org/#/c/13068/ and https://gerrit.omnirom.org/#/c/13069/
In frameworks_av: https://gerrit.omnirom.org/#/c/12528/, https://gerrit.omnirom.org/#/c/12529/ and https://gerrit.omnirom.org/#/c/12530/ (in this order)
In kernel_samsung_smdk4412: https://gerrit.omnirom.org/#/c/12223/ (SELINUX to permissive) , https://gerrit.omnirom.org/#/c/13055/ (Kernel compression)
Optional commits:
Enable Stylus pointer toggle: https://gerrit.omnirom.org/#/c/13606/, https://gerrit.omnirom.org/#/c/13650/, https://gerrit.omnirom.org/#/c/13651/
And finally, if you want to test and/or help:
Netflix experimental codecs fix: https://gerrit.omnirom.org/#/c/13716/
Other commits not made by me:
Nothing here as of now
If you wish to have a kernel with overclock and other features, you can find the kernel sources for my custom kernel "mm_alpha" at https://github.com/marco9333/android_kernel_samsung_smdk4412 . See branch mm_alpha_lollipop for the working and updated version working with this rom (and other lollipop roms). I can share a compiled version, PM me if interested
Screenshots -> Click here
Donations:
Many thanks to Heide Ruehle and @Rand_
Thanks to:
Omnirom core devs
@iofthestorm(ported omnirom 4.4 and made it official for our devices)
@humberos (various patches and asked for an official new android-5.0 branch)
@lirokoa (for his advices on wifi and camera hal)
I forgot someone ???
XDA:DevDB Information
OmniROM, ROM for the Samsung Galaxy Note 10.1
Contributors
marco9333
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2014-11-23
Last Updated 2016-11-13
Status of things:
Broken:
Charging off mode isn't working
Using torch tile causes a forced reboot, use torch app instead
Wi-fi tethering isn't working
Screen recording causes an hard reboot (Now it just does nothing or System UI crashes and restart)
I haven't tested other things yet....
Report if you found something new to add here
Notes:
Using a proxy in APN settings doesn't work. Thanks to @farinjini for pointing this out -> I don't know if this is working now or not
Changelog:
Older versions changelog
20141123
Initial release
20141125
Fixed stylus (S-PEN input)
Fixed graphical glitches in screenshots and while rotating screen Thanks to @lirokoa
Upstream changes -> updated to android release LRX21V and other "under the hood" changes
20141126 for N801x
Solved bootloop problem, I hope (not booting kernel)
20141130 for N8000
Partially working RIL (this has been really hard )
20141204-05
Upstream changes -> updated to android 5.0.1 LRX22C
Gps fixed. Thanks to @humberos
Added Performance control and Advanced in settings as in omnirom 4.4.4 (thanks to omnirom core devs)
Mobile partially fixed (need to run a script to make it completely work) (only N8000)
20141207 for N8000
Mobile data completely fixed
20141218
Upstream changes
Added advanced reboot (normal reboot, reboot to recovery and reboot to bootloader)
Fixed the problem with keyboard (need to disable physical keyboard from settings)
Fixed forced reboots caused by Youtube and G+
Minor fixes about technical things
20150108
Switched to android 5.0.2_r1 LRX22G
Upstream changes
Random reboots should be fixed -> see https://gerrit.omnirom.org/#/c/11024/ and https://gerrit.omnirom.org/#/c/10997/
20150206
Upstream changes -> See https://gerrit.omnirom.org/
Lots of code cleaning -> Better stability (I hope)
20150326/27
Switched to android 5.1 LMY47D
Upstream changes
20150401
Upstream changes
Switched to android 5.1_r3 LMY47I
Youtube, G+, firefox, etc. reboot fixed (experimental fix please report if problems)
20150407
Upstream changes
Netflix fix (experimental.. please report)
Properly "keyboard not showing" fix
20150506
Upstream changes
Android 5.1.1 LMY47V
New DRM vendor libs (Report if they "work miracles" with netflix)
20150510
Upstream changes
Pointer disabled by default when using S-Pen (Can be re-enabled in Settings see screenshot at #372)
Reintroduced keyboard fix (sorry about that)
20150519
Upstream changes
Android 5.1.1_r2 LMY47X
Netflix codec fix -> See https://gerrit.omnirom.org/#/c/13716/
20150628
Upstream changes
Android 5.1.1_r5 LYZ28E
20150928 or 20150927
Upstream changes
Android LYZ28J
Stagefright fixes
20151104
Upstream changes
Video playing fixed (Sorry guys and girls )
Chrome is now working
You need to enable the showing of keyboard after first boot: go to settings, language and input, current keyboard and enable Hardware(Show input method)
20161110
Untested build
Upstream changes
Android LYZ28N
Reserved
Workarounds and advices
Smoothness: Go to settings, about tablet and press repentantly Build_number until it gives you that you're now a developer, Go back, press on Developer options, scroll down and set Window animation scale, Transition scale and Animator scale to .5x
Toggle stylus (S-pen) arrow pointer:
Go to Settings, Language & input, put a tick or not on "show icon when using stylus" option
marco9333 said:
Status of things:
Working:
Boot
Bluetooth (switching on and scanning)
Rotation
Suspend/Resume (need to keep wifi on though)
Audio
Root (flashing SuperSU from recovery)
Gapps install and start (I've tried CM Gapps but login in is impossible)
Vibration
Hd videoplayback (tested youtube)
I forgot something ???
Partially working:
Screen -> Rotation causes graphics glitches
Video playbackaudio is working, decoders too but black video
Wifi (something wrong with this module, suspending the device with wifi off causes an hot reboot)
Broken:
RIL (phone calls, 3g and so on) for n8000 -> I'll try lirokoa advice -> need to import samsungRIL from android-4.4 tree
Camera (videos) -> Imported opensource camera hal -> taking pictures is fine but video are completely broken
Gps ->I 've waited enough and no position found -> some error regarding this in the logcat
I haven't tested other things yet....
Click to expand...
Click to collapse
Hey marco,
For graphics glitch when rotating you need:
https://github.com/CyanogenMod/andr...mmit/540345f70db4f0cea6ad3f1150d2cb2fac18da25
https://github.com/CyanogenMod/andr...mmit/4e7f61fd6a36345e7994c236d1c128c4c8a6a0ea
https://github.com/CyanogenMod/andr...mmit/db4cec0e189b84e5999ae5b3bef0e7a6c2bb3087
you can probably find those in 4.4 omnirom branch as well.
Then it should be fixed
lirokoa said:
Hey marco,
For graphics glitch when rotating you need:
https://github.com/CyanogenMod/andr...mmit/540345f70db4f0cea6ad3f1150d2cb2fac18da25
https://github.com/CyanogenMod/andr...mmit/4e7f61fd6a36345e7994c236d1c128c4c8a6a0ea
https://github.com/CyanogenMod/andr...mmit/db4cec0e189b84e5999ae5b3bef0e7a6c2bb3087
you can probably find those in 4.4 omnirom branch as well.
Then it should be fixed
Click to expand...
Click to collapse
Thanks I've already merged one of them yesterday (the first), and I need to check the second one. I don't know about the last one because I haven't found any settings in the various configs that enable BOARD_USE_MHEAP_SCREENSHOT. I need to check better though.
marco9333 said:
Thanks I've already merged one of them yesterday (the first), and I need to check the second one. I don't know about the last one because I haven't found any settings in the various configs that enable BOARD_USE_MHEAP_SCREENSHOT. I need to check better though.
Click to expand...
Click to collapse
Yes maybe the one for heap screenshot is not needed.
Sent from my Nexus 4 using XDA Free mobile app
i'll try and see if YT even works
Running N8010 device with N8000 BL
seems imposible to get it to work :silly:
LastStandingDroid said:
i'll try and see if YT even works
Running N8010 device with N8000 BL
seems imposible to get it to work :silly:
Click to expand...
Click to collapse
It's working I've just tested with a 720p video
marco9333 said:
It's working I've just tested with a 720p video
Click to expand...
Click to collapse
i'll see if it'll work for me i've never got it working with any build
LastStandingDroid said:
i'll see if it'll work for me i've never got it working with any build
Click to expand...
Click to collapse
I'm in the same boat as you, stuck with the leaked N8000 bootloader on my N8010, and youtube works great for me on last CM 11 build.
Nice work Marco!!
I've flashed your build (while building mine... ) and I've noticed that the keyboard doesn't show up, I had to go to Settings>Language & input>Current Keyboard and switch on the Hardware flag to make the keyboard appear.
Youtube works fine (audio and video)
I've played a couple of mp4 videos with a default gallery without a problem
Music plays fine with Apollo
It seem very good for such an early build...If only the log in with Google Account worked...:fingers-crossed:
Sooo nice rom only network works on N8000 and it will be my rom
- There is a problem with the default browser as it closes after opening on few seconds
- Graphics errors at multi tasks cards.
TheMorpheus said:
Nice work Marco!!
I've flashed your build (while building mine... ) and I've noticed that the keyboard doesn't show up, I had to go to Settings>Language & input>Current Keyboard and switch on the Hardware flag to make the keyboard appear.
Youtube works fine (audio and video)
I've played a couple of mp4 videos with a default gallery without a problem
Music plays fine with Apollo
It seem very good for such an early build...If only the log in with Google Account worked...:fingers-crossed:
Click to expand...
Click to collapse
I've tried CM gapps but it chrashes on login.... maybe some others google apps will work. I'll try to extract them from my nexus 5 official L rom.
mysarasaid said:
Sooo nice rom only network works on N8000 and it will be my rom
- There is a problem with the default browser as it closes after opening on few seconds
- Graphics errors at multi tasks cards.
Click to expand...
Click to collapse
I usually use chrome. Default browser should be "deprecated" and replaced by chrome. Graphical errors are still there (during switching off screen, rotation, taking screenshots and so on), lirokoa pointed some commits I'll try with them, but they should do the job. RIL is a priority for me too, but it's quite complex and the code changed a lot so I'll need some time to merge that part.
marco9333 said:
I've tried CM gapps but it chrashes on login.... maybe some others google apps will work. I'll try to extract them from my nexus 5 official L rom.
I usually use chrome. Default browser should be "deprecated" and replaced by chrome. Graphical errors are still there (during switching off screen, rotation, taking screenshots and so on), lirokoa pointed some commits I'll try with them, but they should do the job. RIL is a priority for me too, but it's quite complex and the code changed a lot so I'll need some time to merge that part.
Click to expand...
Click to collapse
For RIL, many things are needed and I can't test since I have N8013, but I can point you to some to a repo that might help you:
https://github.com/ArchiDroid/android_frameworks_opt_telephony/commits/cm-12.0
Looks to all SamsungExynos4RIL / Samsung STK commits. That should help.
lirokoa said:
For RIL, many things are needed and I can't test since I have N8013, but I can point you to some to a repo that might help you:
https://github.com/ArchiDroid/android_frameworks_opt_telephony/commits/cm-12.0
Looks to all SamsungExynos4RIL / Samsung STK commits. That should help.
Click to expand...
Click to collapse
I'll give it a try because when I tried to merge RIL from omnirom 4.4 I've got an enormous amount of conflicts. Thanks maybe them will speed up the fix
Sent from my Nexus 5 using XDA Free mobile app
I've tested latest Banks google apps for android L and they are working. This is the link http://fitsnugly.euroskank.com/?rom=banks&device=gapps (added in OP too)
marco9333 said:
I've tested latest Banks google apps for android L and they are working. This is the link http://fitsnugly.euroskank.com/?rom=banks&device=gapps (added in OP too)
Click to expand...
Click to collapse
it did remove my recovery after flashing this rom not sure why i was just unable to reboot to recovery (regular key combination)
used philz recovery rom worked and booted but recovery was gone (also using adb reboot recovery) made my phone go into bootloop
N8010 device with N8000 BL just to mention,
---------- Post added at 10:24 PM ---------- Previous post was at 10:22 PM ----------
lirokoa said:
Yes maybe the one for heap screenshot is not needed.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
@llirokoa do u know what lib is patched to fix the graphic issue? is it the surfaceflinger?
LastStandingDroid said:
it did remove my recovery after flashing this rom not sure why i was just unable to reboot to recovery (regular key combination)
used philz recovery rom worked and booted but recovery was gone (also using adb reboot recovery) made my phone go into bootloop
N8010 device with N8000 BL just to mention,
---------- Post added at 10:24 PM ---------- Previous post was at 10:22 PM ----------
@llirokoa do u know what lib is patched to fix the graphic issue? is it the surfaceflinger?
Click to expand...
Click to collapse
I've written quite big in the third post that you need to flash supersu beta just after the rom or you won't be able to boot into recovery: you've been warned. I'm working on merging the fixes for graphics issues.
By the way I've fixed the stylus input which is working ok now. New version soon....
New version 20141125 out
I've just uploaded a new build. See OP for download links and second post for changelog. Before signaling a bug or something that isn't working, please read the third post, too.
Another bug I've found is in charging off script, please recharge your tablet while on until next release
On my n8013, every time I flash the ROM, then gapps, then superSU, I get a boot loop, never makes it to Omni logo. I tried to redownload all files from the OP, and still no luck. Tried 4 times now
Rom updated on May 19. This is LP 5.1 release 2. Latest Google/CM/Resurrection sources + all hardened features. Plus cleaned IP addresses (got rid of Google, Level 3 communication, AT&T, Orange, Department of Defense and other shady ips). Also enabled is Volte (enhanced LTE), which is Voice over LTE. This depends on the service provided by your carrier. In the States, for example, T-Mobile provides such services, which include high definition voice. Usually, you need special update done by the manufacturer in conjunction with your carrier. This rom does not need that. Your Z1 is already provisioned for Volte. You will see in Mobile Settings another entry: Enhanced 4g LTE Mode. ALso, in test menu/phone (*#*#4636#*#*), you will see a Volte Provisioned Flag. So, as soon as your carrier starts Volte, you are all set.
Sources are the same...
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=12531
_____________________________________________________________________________________
Rom updated to latest sources on May 4. In addition to regular hardened features, more than 40 instances of Google IP, Level 3 Communication and Department of Defense IPs removed from sources both for IPV4 and IPV6. The same is replaced with Opendns IP. Keep in mind that those ips go not only in configuration files, but libs also and the latter cannot be decompiled and fixed...
Download link: http://forum.xda-developers.com/devdb/project/dl/?id=12289
______________________________________________________________________________________
Rom Updated to LP 5.1.1. All hardened/security features implemented. Kernel used from Slimroms 5.1.
TWRP 2.8.6 is integrated in kernel.
Obviously, this is an alpha version...
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=12110
Kernel Source: https://github.com/AOSP-Argon/kernel_sony_msm8974/tree/lp5.1
___________________________________________________________________________________________________
Rom updated to 5.1: all hardened features enabled.
Download link: http://forum.xda-developers.com/devdb/project/dl/?id=11901
___________________________________________________________________________________________________
March 31: kernel updated to include screen color calibration:
See Download link: http://forum.xda-developers.com/showpost.php?p=59801528&postcount=94
_________________________________________________________________________________________________
March 27: New build is up, latest CM and Resurect changes; kernel includes voltage table, syncookie and TWRP.
Download Link: http://d-h.st/lw2s
Mirror Link: http://forum.xda-developers.com/devdb/project/dl/?id=11744
_________________________________________________________________________________
March 15: New build is up including latest sources, TWRP integrated in kernel, led lights fixed
DOWNLOAD LINK: http://d-h.st/UO7W
_______________________________________________________________________________________________
Marchh 7: Rom Updated to the latest version + plus all security enhancements. Sources for security changes are the same as posted
See Download section for update
Here is Resurection Remixed Lollipop hardened and secure. Built from sources on February 24.
Changes:
First of all, as many know, encryption on lollipop slows down the device to almost unusable. I was able to resolve that. The culprit was Qualcom crypto module and drivers that collide with graphics. In this rom, when you encrypt your device, there is no noticeable slow down at all. Your master encryption key is no longer stored in crypto module (which rumor has it is backdoored anyway), but rather hashed and salted on the drive itself.
1. Modified kernel to disable creepy SElinux and enable Tomoyo security. Now you can safely use Xposed framework and some modules such as Xprivacy, Appsettings and ShowDialpad, as well as many others
2. Modified kernel to disable qualcom module and drivers
3. Disabled creepy qualcom random number generation and enabled all other methods
4. Enabled 256 bit AES drive encryption as opposed to Google's default 128 bit
5. Enabled all ciphers and hashes available in kernel and disabled by default (thanks Sony and Google)
6. Latest CM changes
7. Omniswitch (to be flashed separately after flashing the rom)
Maybe more
INSTALL:
1. Be on Kitkat, rooted with CWM or TWRP
2. Enter Recovery, wipe System, Data, Cache
3. Flash the rom
4. Flash Omniswitch
5. Reboot and enjoy
If you want to encrypt your device, you need to do 2 additional steps before or after encryption. Go to Developer Options and enable "Force GPU rendering" and "Disable HW overlays. Yes, you have to enable (not disable) "Disable HW overlays" option. The latter won't stick after reboot. So, manually transfer the attached init.d script to /system/etc/init.d and set permissions to at least 744. This way the option will be set at boot and you won't have any noticeable slowdown. In fact, I don't see any difference in speed between encrypted and non encrypted device.
CREDIT: Resurection-Remix Team, Cyanogenmod, AOSP and Omniroms
WARNING:
I am not responsible if your device explodes and kills everyone around. You are doing it on your own. Russians, who are definitely coming, won't help you either :laugh:
Download links
Rom: http://d-h.st/l1rB For Update see Download Section
Omniswitch: http://d-h.st/AbGH
Init.d script (in case you want to encrypt your data): http://d-h.st/QIiE
Sources: https://github.com/ResurrectionRemix
https://github.com/HonamiZ1/android_system_vold
https://github.com/HonamiZ1/kernel_sony_msm8974
XDA:DevDB Information
Resurection-Remixed Lollipop 5.1.1 Hardened, ROM for the Sony Xperia Z1
Contributors
optimumpro
ROM OS Version: Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP, Cyanogenmod
Version Information
Status: Testing
Created 2015-02-25
Last Updated 2015-05-19
screenshots
Screenshots added
Kernel updated with CPU voltage table
Kernel updated to allow under/over volting. See attachment.
Instructions:
1. Unzip the file
2. Flash in fastboot: fastboot flash boot boot.img and fastboot reboot
Enjoy
Thanks for this ROM, are there any known bugs?
wis3m0nkey said:
Thanks for this ROM, are there any known bugs?
Click to expand...
Click to collapse
All CM bugs as of February 24. You can go on their site and see the list of changes...
optimumpro said:
All CM bugs as of February 24. You can go on their site and see the list of changes...
Click to expand...
Click to collapse
So just need to look at http://forum.xda-developers.com/xperia-z1/general/rom-official-cyanogenmod-12-nightlies-t3007118 is that right?
Sorry I have to confirm, there are multiple threads (Official/Development) for CM12.
This ROM will maintain root and recovery, right?
I'll flash and let you know if I find any other issues.
Tried it. Works great. Some strange problem with mms though. Could not load them even though data works perfectly. Battery life looks great. Didn't try calling so i can't say anything about the mic.
Kyrius said:
Tried it. Works great. Some strange problem with mms though. Could not load them even though data works perfectly. Battery life looks great. Didn't try calling so i can't say anything about the mic.
Click to expand...
Click to collapse
I use Textsecure as sms replacement. Microphone works great...
Very buggy
you should definately fix this rom as i cannot start camera it fc. it restart itseft
NOT STABLE
darkdevu said:
you should definately fix this rom as i cannot start camera it fc. it restart itseft
NOT STABLE
Click to expand...
Click to collapse
1. Learn the rule about not posting bug reports without logcat
2. Camera works fine: verified
3. Always wipe System/Data/Cache before flashing
4. Are you sure you have Xperia Z1?
Cheers
his profile says Z3. lol
Any further reports on this ROM? Interesting to know how it performs and about stability
Deleted
wis3m0nkey said:
Thanks for this ROM, are there any known bugs?
Click to expand...
Click to collapse
Rom Updated to the latest version. See Download section in the OP.
and where is the link to the update?
shikimafia said:
and where is the link to the update?
Click to expand...
Click to collapse
It is in Download section:
http://forum.xda-developers.com/devdb/project/?id=8412#downloads
Screenshots added in post #2. Note that only this rom and SlimLP work with the latest Xpivacy module. Tried on Crdroid and others and there is bootloop as soon as you enable Xprivacy.
Has no one tried this rom as not reports or posts
tried flashing update from scratch and get play services fc on every gapps i used............i am guessing i may have to flash initial release and dirty flash this over it? excuse me if i may have got it wrong
shingers5 said:
Has no one tried this rom as not reports or posts
Click to expand...
Click to collapse
Well. The first version had 69 downloads. The latest one had 20. Other than the bogus claim about camera foreclosing (by someone who has Xperia Z3) there were no reports of problems. I have been using this rom for about 10 days without any problems...
optimumpro said:
Well. The first version had 69 downloads. The latest one had 20. Other than the bogus claim about camera foreclosing (by someone who has Xperia Z3) there were no reports of problems. I have been using this rom for about 10 days without any problems...
Click to expand...
Click to collapse
I'm having issues flashing the new version as getting play services errors.... Was gonna try dirty flash over previous versions
Anyone with UART or USB access to u-boot willing to help with a dev project?
Devs only ATM, too many serious bugs
And there is the possibility of screen damage
If it hardlocks with papyrus ic on
test build #1 pulled due to poweroff/screen burnin bug
Test build #1: http://forum.xda-developers.com/showpost.php?p=60336716&postcount=14
Test build #2: http://forum.xda-developers.com/showpost.php?p=60453540&postcount=74
Test build #3: http://forum.xda-developers.com/showpost.php?p=60677266&postcount=136
Kernel Tree: https://github.com/kfazz/android_kernel_bn_zoom2/tree/nook_nst_3.0
zoom2 device tree: https://github.com/kfazz/android_device_bn_zoom2
vendor tree: https://github.com/kfazz/propietary_vendor_bn.git
Local manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="CyanogenMod/android_build" />
<remove-project name="CyanogenMod/android_frameworks_base" />
<remove-project name="CyanogenMod/android_frameworks_native" />
<remove-project name="CyanogenMod/android_bootable_recovery" />
<project path="frameworks/base" name="kfazz/android_frameworks_base" revision="nook"/>
<project path="frameworks/native" name="kfazz/android_frameworks_native" revision="nook"/>
<project path="bootable/recovery" name="TeamWin/Team-Win-Recovery-Project" revision="android-5.1"/>
<project path="build" name="kfazz/android_build" revision="nook"/>
<project path="device/bn/zoom2" name="kfazz/android_device_bn_zoom2" revision="master"/>
<project path="kernel/bn/zoom2" name="kfazz/android_kernel_bn_zoom2" revision="nook_nst_3.0"/>
<project path="vendor/bn" name="kfazz/propietary_vendor_bn" revision="master"/>
</manifest>
Done:
Kernel 3.0.8 boots
Zoom2 devicetree
Cm11 boots
Twrp boots and installs ROM
Wip:
Ghosting
Ram usage
Suspend
To do:
WiFi sleep of death,
USB(works, but kinda slow) fixed adb gets ~4mb sec mtp gets ~2.8
Integrate epdcontroller in framework (partially done)
Pngcrush grayscale all images done, by adding back custom squisher to android/build
Fastmode,
multitouch, done, using 1.3.1 zforce driver + changes based on http://lwn.net/Articles/572311/
USB host not sure what the limit is but a 100mA usb mouse works without a powered hub, and a 200mA usb stick doesn't
Themeing
Gapps don't work (but too much lowram lag to be practical)
kfazz said:
Anyone with UART or USB access to u-boot willing to help with a dev project?
Devs only ATM, too many serious bugs
And there is the possibility of screen damage
If it hardlocks with papyrus ic on
Done:
Kernel 3.0.8 boots
Zoom2 devicetree
Cm11 boots
Twrp boots and installs ROM
Wip:
Ghosting
Ram usage
Suspend
To do:
WiFi sleep of death, USB, fastmode
Integrate epdcontroller in framework
Pngcrush grayscale all images
Fastmode, multitouch, USB host, etc
Themeing
Gapps don't work
Click to expand...
Click to collapse
Woah, this looks sick! I'd be glad to help you in any way I can. I've got a Nook Touch Glow running a customized version of the 1337 ROM, a modded framework-res.apk, and a modded Settings.apk (see my sig for full specifications). Let me know how I can assist!
By the way, I'm inviting you to my Nook Touch Devs group now, so we can talk in there.
ИΘΘK¡€ said:
Woah, this looks sick! I'd be glad to help you in any way I can. I've got a Nook Touch Glow running a customized version of the 1337 ROM, a modded framework-res.apk, and a modded Settings.apk (see my sig for full specifications). Let me know how I can assist!
By the way, I'm inviting you to my Nook Touch Devs group now, so we can talk in there.
Click to expand...
Click to collapse
if you'd be willing to try compiling it, javifo has a u-boot tree that looks like it supports ttyUSB.
https://github.com/javifo/NST/tree/master/u-boot
I'm not sure if my kernel supports usb because my usb port is broken, but if you can get u-boot access over usb
i'll try to build a kernel and bootscript that will be debuggable over usb.
My current setup is completely self contained on the sdcard and doesn't touch stock partitions except reading device specific data from /rom
kfazz said:
if you'd be willing to try compiling it, javifo has a u-boot tree that looks like it supports ttyUSB.
https://github.com/javifo/NST/tree/master/u-boot
I'm not sure if my kernel supports usb because my usb port is broken, but if you can get u-boot access over usb
i'll try to build a kernel and bootscript that will be debuggable over usb.
My current setup is completely self contained on the sdcard and doesn't touch stock partitions except reading device specific data from /rom
Click to expand...
Click to collapse
I'll give it a go on the weekend when I have some free time.
rendering from userspace
omap3pfb drawing modes:
pageflip mode: (non deferred)
turned on by writing a 1 to
/sys/devices/platform/omap3epfb.0/graphics/fb0/pgflip_refresh
apps that are unaware of bn's eink setup work fine.
this is how stock recovery uses the display, and also bootanimation on stock rom (i think).
Downside: ghosting, no control over waveform used to draw ( that i know of )
'command' mode.
display update is controlled by various private ioctl commands to the /dev/graphics/fb0 file.
ioctl -> * -> EpdService function -> EpdController function
OMAP3EPFB_IO_SET_REGION <- * <- configureRegion <- setRegion
OMAP3EPFB_IO_GET_REGION -> * -> UNUSED
OMAP3EPFB_IO_RESET_REGION <- * <- resetRegion <- resetRegion
OMAP3EPFB_IO_FILL_REGION < * <- fillRegion <- fillRegion
* is jni function calls in libandroidruntime.so
EpdController.epdRefresh writes to /sys/devices/platform/omap3epfb.0/graphics/fb0/epd_refresh
1 = Gray Clear
0 = update
epdDisable writes to /sys/class/graphics/fb0/epd_disable
value is timeout period in milliseconds
by themselves these writes and ioctls do nothing. the magic is in libui.so
stock rom calls OMAP3EPFB_IO_REQ_AREA_UPDATE in FramebufferNativeWindow::queueBuffer()
to update the display. No idea what logic the is used to decide when or whether to update.
Deferred Rendering:
this is turned off in kernel config for stock rom, and theres a typo in one of the ifdefed clauses which
leads me to believe this code path was abandoned early in development of the driver
i got it to work, but it doesn't seem to have many advantages over regular pageflip mode, and it's slow.
more info on deferred io: http://elinux.org/images/2/25/E_paper_Displays.pdf
anyone see any errors or have any insights as to how to implement this on Kitkat's graphics stack?
Oh Wow !!!
is that really a cm11(KITKAT) lock screen on a NST G ???
thanks for trying @kfazz following this thread, look forward to what will materialize out of this GREAT effort. kitkat is known to support low ram devices, hopefully it will accommodate our Nook Simple Touch activity which is only static read centric operations.
thanks for attempting
Any chance of a video? I'm scared that this is just a late April fool's joke! Been waiting for this for so long!
coolius said:
Any chance of a video? I'm scared that this is just a late April fool's joke! Been waiting for this for so long!
Click to expand...
Click to collapse
I to can't believe it. but this is cool. I hope it will be usefull since I thought the cm7 would have the highest version of cyanogenmod to work well on our devices.
coolius said:
Any chance of a video? I'm scared that this is just a late April fool's joke! Been waiting for this for so long!
Click to expand...
Click to collapse
dorfd1 said:
I to can't believe it. but this is cool. I hope it will be usefull since I thought the cm7 would have the highest version of cyanogenmod to work well on our devices.
Click to expand...
Click to collapse
I mean, the source to compile is right there, and he last updated it about an hour ago... Id compile a version to test for myself, but my server that I've used in the past for compiling android has yet to be set up again(new install )
Im honestly amazing that kfazz got it working, major props to him and hopefully this would allow more funtionality to come out of my old nook(s)
Edit: Oh, and this would also open up a wider range of usb devices to plug into the nook, as well as better compatibility for any new apps
---------- Post added at 10:54 PM ---------- Previous post was at 10:46 PM ----------
Also, to kfazz, Ive got an extra nook that doesnt matter if the screen gets damages(a new one is fairly cheap anyways), Id love to help you test out this project. I can also get access to the uart if needed, ill just have to pop open the case and solder on a few points(right? I last read about the access to the uart on the nook many months/year ago and I may be mistaken)
Yes, yes, and yes. UART access isn't strictly necessary, but there are a few issues I want to resolve before release. Mainly the circle animation android draws on loading screens, and auto partitioning sdcard. PS delete system/core/ uncrypt/android.mk and it should build. (Twrp conflict)
Wow, unbelievable we have WIP and moreover kitkat of all, Can't wait to try it out.
switching off all possible animation is best don't want to lose out on valuable battery time.
thanks Guys.
aiamuzz said:
Wow, unbelievable we have WIP and moreover kitkat of all, Can't wait to try it out.
switching off all possible animation is best don't want to lose out on valuable battery time.
thanks Guys.
Click to expand...
Click to collapse
I think the boot animation would have to be disabled.
Trying to be optimistic ...
A LG optimus Pro C660 with 256 RAM and less than 200MB internal storage for apps.
Came across this Lollipop
I believe Kitkat was also attemtpted for this device. but the ROM file is purged and no longer available.
If this device can operate as a full fledged phone, Will our device hold any promise for static reading purposes only ?
super buggy test build #1
super buggy test build #1:
update: pulled due to serious bugs. poweroff may fail with the screen on, buring in an image.
First up, to the best of my knowledge this rom won't melt your eink screen, wipe your sd, or cause your nook to spontaneously combust, but NO WARRANTIES.
With that out of the way, here is a test build. I'm not publishing it because it's done, but rather to encourage others to sync the source and try bulding it.
backup contents of sdcard first
write sd.img to a sdcard in the usual way. (sd_img.zip is attached to this post)
nook_nst_3.0 kernel: (this still has wifi sleep of death bug)
Same thing built with encore_merge kernelno wifi sleep bug, may have other problems, probably usb)
copy rom zip and md5 to nook's media partition
boot from sdcard, mount media
install rom (make sure signature verification is on)
reboot
if it doesn't boot hard reboot by pressing power and home for 9 seconds
"Where's the source?"
See the first post.,
Specifically the kernel in this rom was built from commit 7c944768270ec14736c7977b876a107e0a30b87f (current tip of nook_nst_3.0 branch)
except arch/arm/mach-omap2/board-3621-gossamer.c which was checked out from commit fbd1b8ccbebcb483eed158c5b6d51a4f44bbd2c4 (current tip of encore_merge branch)
"How can I help?"
sync my code and send me patches
sync my code and build it yourself
make a cm11 theme and test it
patch apps to use EpdController
What isn't helpful:
it's buggy. it's slow.
feature x is broken / app x doesn't work.
it's ugly. etc.
"Where're the gapps? I really want gapps, even though i know they will run all the time stealing my precious ram"
try the pico ones, or pico(uni). you probably won't be able to run browser after they're installed
http://www.androidrootz.com/2015/03/download-android-44x-kitkat-pa-gapps.html
Alternative: https://f-droid.org/ has a market app for free/foss software, and lost of reading apps
I'm very excited to see where this is going. I have an app that requires 2.3+ and would love to get it working. I can put up with no Gapps, slow system, etc. Just wondering about a few things:
Ghosting: Does the e-ink screen not properly refresh?
Wifi Sleep of Death: What does this mean?
Cheers!
Kralik said:
I'm very excited to see where this is going. I have an app that requires 2.3+ and would love to get it working. I can put up with no Gapps, slow system, etc. Just wondering about a few things:
Ghosting: Does the e-ink screen not properly refresh?
Wifi Sleep of Death: What does this mean?
Cheers!
Click to expand...
Click to collapse
For Ghosting, its basically the same as the regular OS, theres issues after a while of use, but I havent seen much from a few hours of trying out the build.
And also to kfazz, this build is awesome! Ive been trying to compile the OS, but have been having issues compiling(last time I compiled an android zip was like 2 years ago for my Nook Color), Although I am not done trying yet
Also: I found a small bug(no idea where to go to fix it, but I remember it being like a bug a while back for the CM10 or 11 development build for the Nook Color) where if you you try to go into landscape(by an app forcing it), the x and y values for the touchscreen are flipped, it shouldnt be too hard to change.
kfazz said:
super buggy test build #1:
First up, to the best of my knowledge this rom won't melt your eink screen, wipe your sd, or cause your nook to spontaneously combust, but NO WARRANTIES.
With that out of the way, here is a test build. I'm not publishing it because it's done, but rather to encourage others to sync the source and try bulding it.
backup contents of sdcard first
;
;
;
Click to expand...
Click to collapse
Hey this is really great !!!
but too early for me to try ... not a techie who understands all this stuff.
We have CWM recovery installed and using yattaro&nookie's ROM
Can't this be flashed from CWM ?
Twrp Recovery a must ?
dombeef said:
For Ghosting, its basically the same as the regular OS, theres issues after a while of use, but I havent seen much from a few hours of trying out the build.
And also to kfazz, this build is awesome! Ive been trying to compile the OS, but have been having issues compiling(last time I compiled an android zip was like 2 years ago for my Nook Color), Although I am not done trying yet
Also: I found a small bug(no idea where to go to fix it, but I remember it being like a bug a while back for the CM10 or 11 development build for the Nook Color) where if you you try to go into landscape(by an app forcing it), the x and y values for the touchscreen are flipped, it shouldnt be too hard to change.
Click to expand...
Click to collapse
Hey dombeef, great to hear you complied it and have flashed it on your device.
Looking forward to your feedback on its performance.
Excited !!!
Just remembered -- I have the Glowlight model. Is turning the light on/off and adjusting the level supported? Is it possible to customize the left/right side buttons?
Kralik said:
Just remembered -- I have the Glowlight model. Is turning the light on/off and adjusting the level supported? Is it possible to customize the left/right side buttons?
Click to expand...
Click to collapse
Well @Kralik as you can see its a little too early for that ... i believe this is not even a beta build !!!
am i right @kfazz ?
dombeef said:
...
Also: I found a small bug(no idea where to go to fix it, but I remember it being like a bug a while back for the CM10 or 11 development build for the Nook Color) where if you you try to go into landscape(by an app forcing it), the x and y values for the touchscreen are flipped, it shouldnt be too hard to change.
Click to expand...
Click to collapse
change touch.orientationAware = 0 to touch.orientationAware = 1 in /system/usr/idc/zForce_Touchscreen.idc (device/bn/zoom2/prebuilt/usr/idc/zforce_ts.idc)
Fix tested and pushed
Kralik said:
I'm very excited to see where this is going. I have an app that requires 2.3+ and would love to get it working. I can put up with no Gapps, slow system, etc. Just wondering about a few things:
Ghosting: Does the e-ink screen not properly refresh?
Wifi Sleep of Death: What does this mean?
Cheers!
Click to expand...
Click to collapse
Ghosting: Screen updates in GU mode most of the time, so previous contents of screen are faintly visible.
Wifi Sleep of Death: sometimes after the nook is in suspend for a while, the wifi chip doesn't power back on and toggling wifi from the android settings will cause the nook to lockup in a bad state.
This is Android 4.4.4 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).
It includes various security fixes on top of 4.4.4 - but most likely not all. Major security hole detectors are green now (VTS, Bluebox, Zimperium).
NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!
Without much ado...
To install...
- Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
- Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/filedl/devs...mhoffmann/fp1-kk-stock/fp1-kk444-CH-0.9.7.zip MD5sum: 9140c93ff8f2b8327fdd330d2448c16f
- I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
- You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711
Bugs:
- IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?
- CTS is complaining about some issues. https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml
- As this is a merge of 4.4.4 into the MTK stuff, watch out for more bugs than the previous release. Not merged: the new 4.4.4 dialer screen (we stick with 4.4.2 dialer as the modifications are too heavy), chromium does not support wml anymore (who cares?).
- You most likely need to wipe to install this when coming from the previous KK version to 4.4.4. Email app e.g. seems to crash without.
- Playstore version of Google Authenticator does not work (see https://github.com/google/google-authenticator-android/pull/4). Use the OSS version https://github.com/google/google-authenticator-android/releases - this is not specific to FP1 but seems an MTK issue.
- A dirty update (without wipe) from 0.8 on an encrypted device seems to reboot once during the "Android is upgrading" dialog
- Sometimes the lower part of the homescreen launcher seems to lose transparency.
Changelog fp1-kk444-CH-0.9.7 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-MAY-2016 (https://source.android.com/security/bulletin/2016-05-01.html)
- Kernel CVEs including the mediatek wifi ones from https://source.android.com/security/advisory/2016-03-18.html, CVE-2016-2549, CVE-2016-2847, CVE-2016-2547, CVE-2016-2546, CVE-2016-2545, CVE-2016-2384
Changelog fp1-kk444-CH-0.9.6 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 2-APR-2016 (https://source.android.com/security/bulletin/2016-04-02.html)
- Kernel CVEs including the one from https://source.android.com/security/advisory/2016-03-18.html, CVE-2015-7550, CVE-2016-0774, CVE-2016-0821, CVE-2016-0723.
Changelog fp1-kk444-CH-0.9.5 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-MAR-2016 (https://source.android.com/security/bulletin/2016-03-01.html)
(incl. the kernel fixes that Google only publishes for Google One / Sprout - ported to MT6589)
Changelog fp1-kk444-CH-0.9.4 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-FEB-2016 (http://source.android.com/security/b...016-02-01.html)
- Kernel CVE CVE-2015-8785
Changelog fp1-kk444-CH-0.9.3:
- Android Security Updates from Google bulletin 1-JAN-2015 (http://source.android.com/security/bulletin/2016-01-01.html)
- Some kernel CVEs (CVE2015-8543, CVE2015-8575, CVE2015-7509)
- Attempt to fix German's E-PLUS on O2 roaming
Changelog fp1-kk444-CH-0.9.2:
- Fix that you can now call funny numbers like *143# without phone application crash
- Fix to be able to add contacts to SIM card
Changelog fp1-kk444-CH-0.9.1:
- several kernel CVEs (CVE-2015-5697, CVE-2015-8539, CVE-2015-8215, and a few more without CVE yet)
- the december 1st security advisory bulletin skia issue introduced in 0.9.0 - aka as the dilbert bug - is fixed now
Changelog fp1-kk444-CH-0.9:
- android security bulletin https://source.android.com/security/bulletin/2015-12-01.html
- also update gapps if you install them: http://opengapps.org/?api=4.4&variant=nano
Changelog fp1-kk444-CH-0.8:
- google location providers are used now, which should enable network location provider (in case you installed google apps).
Changelog fp1-kk444-CH-0.7:
- National roaming should be fixed (at least as good as CM). If you still have issue with national roaming, send me your mmc/mmn data.
- Use original FP1 lens parameters for fm50af lens - does this improve the auto/manual focus issues that some people reported compared to stock FP jellybean?
- Attempt to fix the problem where sometimes the scrollbar and recents screen stopped working and screen locked despite having higher screen timeouts.
- Full CTS result: https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml
Changelog fp1-kk444-CH-0.5:
- SELinux enforcing
- Camera app now shows all resolutions
- adb now requires acceptance of adb key
Changelog fp1-kk444-CH-0.4:
- ro.adb.secure set
- browser default pages revisited (removed wrong thumbnail).
- removed MTK root CAs that are not in AOSP
- fixed remaining security false-positives in VTS and Bluebox Trustable - all green now
- USB default setting should be MTP now
Changelog fp1-kk444-CH-0.3:
- More CVE fixes (e.g CVE-2015-3845). VTS and Bluebox Trustable are almost green. For some reasons they still think "Stagefright" is not fixed. Zimperium nevertheless shows all stagefright OK. Edit: found out why. It's false positive as MTK reports errors in MPEG4Extractor differently than stock.
Changelog fp1-kk444-CH-0.2:
- Netflix issue fixed with new blob from E3
- Some CTS issues fixed
- More security fixes CVE-2014-7911
Changelog fp1-kk444-CH-0.1:
- Upgraded to 4.4.4_r2.0.1: Yay! That was an insane amount of work. The following "shortcuts" were taken:
-- Chromium sources taken from AOSP - MTK added wml but it was too much work to merge this back in
-- Email app sources taken from aosp - MTK customized something there esp. exchange sync, is that really giving someone problems?
-- Dialer app taken from MTK without 4.4.4 updates - that stuff is too heavily customized also for dual sim, and 4.4.4 revamped the UI, so this was just too much work for now.
- Latest security fixes up to November 2015. Security fixes also for wpa_supplicant_8 (thanks to Michael Bestas for collecting them for CM)
- Kernel sec fixes
- FP1 power profile xml (does this actually change anything)
As usual some credits:
- @Santhosh M : for some advice on the modem/baseband
- @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
- @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
- @CyanogenMod for the stagefright fixes
Let me know if
- it works also on older FP1 (without U).
- you have problems with your IMEI, too
- if you find other major issues
- if you think I am missing some security updates
- i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.
Reserved - why do all people do this?
chrmhoffmann said:
This is Android 4.4.2 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).
It includes various security fixes on top of 4.4.2 - but most likely not all.
NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!
Without much ado...
To install...
- Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
- Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/devs/chrmhoffmann/fp1-kk-stock
- I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
- You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711
Bugs:
- IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?
As usual some credits:
- @Santhosh M : for some advice on the modem/baseband
- @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
- @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
- @CyanogenMod for the stagefright fixes
Let me know if
- it works also on older FP1 (without U).
- you have problems with your IMEI, too
- if you find other major issues
- if you think I am missing some security updates
- i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.
Click to expand...
Click to collapse
so far it works on my fp1 (without U), no Problems with my IMEI-Numbers. Thank you very very much, great!
Just flashed it and it works! Thank you so much! (although instructions how to create such a rom would be nice for me )
EDIT: some answers to your question:
I am using the FP1u.
No problems with my IMEI.
Other major issues: none noticed, and this actually fixed the transparency bug in the Play Store
Missing security patches: Stagefright CVE-2015-6602 is not fixed.
Thank you very much!
How do i flash the recovery? the typicall fastboot method does not work for me (says "flash not supported")
fredflegel said:
How do i flash the recovery? the typicall fastboot method does not work for me (says "flash not supported")
Click to expand...
Click to collapse
There's an old thread about it: http://forum.xda-developers.com/showthread.php?t=2615613
So in this case:
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/recovery
And because I can never remember if it's volume up or down when powering on: "Hold the Volume Up button, while at the same time press and hold the Power button. Hold these two buttons at the same time for about 10 seconds until the screen changes."
Then install from sideload, etc. and
Code:
adb sideload fp1-kk-stock-0.1.zip
Takes quite a while to update. I did NOT disable rom recovery, I don't think this one reverts the recovery, right?
aaaand
Sound and bluetooth seem to work fine, didn't test more so far.
Edit: By the way, are you going to do a Lollipop rom? That would be even more awesome than this. Meanwhile: Good job for raising the FP1 software to the minimum requirements for today.
Great Work! Thanks alot!
I will check this rom thoroughly. On little cosmetic issue that was fixed in Fairphones official rom is the issue with national roaming in german 02/E-Plus networks. I now allowed data roaming as a workaround, but this can get pretty expensive pretty soon. Any chance you can fix that in a future build?
fredflegel said:
Great Work! Thanks alot!
I will check this rom thoroughly. On little cosmetic issue that was fixed in Fairphones official rom is the issue with national roaming in german 02/E-Plus networks. I now allowed data roaming as a workaround, but this can get pretty expensive pretty soon. Any chance you can fix that in a future build?
Click to expand...
Click to collapse
You can enable "National data roaming" with GravityBox, which you can install via the Xposed installer. Helped in Austria with bob (and A1)
You forgot to mount the "external" storage:
Code:
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0
Workaround for getting the correct one for now:
Code:
umount /storage/emulated
mount -t vfat /dev/block/mmcblk0p8 /storage/emulated
But there are still symlinks to /storage/emulated/legacy.
So that needs some kind of fix up.
ccxxx said:
You forgot to mount the "external" storage:
Code:
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0
Workaround for getting the correct one for now:
Code:
umount /storage/emulated
mount -t vfat /dev/block/mmcblk0p8 /storage/emulated
But there are still symlinks to /storage/emulated/legacy.
So that needs some kind of fix up.
Click to expand...
Click to collapse
I think that you are using the old non-repartitioned fp1?
There's no such thing as /dev/block/mmcblk0p8 anymore on the repartitioned devices.
Chris
chrmhoffmann said:
I think that you are using the old non-repartitioned fp1?
There's no such thing as /dev/block/mmcblk0p8 anymore on the repartitioned devices.
Chris
Click to expand...
Click to collapse
Uhm, yes, I guess.
TIL https://fairphone.zendesk.com/hc/en-us/articles/201327645-What-is-Fairphone-s-storage-layout-
ccxxx said:
Uhm, yes, I guess.
TIL https://fairphone.zendesk.com/hc/en-us/articles/201327645-What-is-Fairphone-s-storage-layout-
Click to expand...
Click to collapse
You should then upgrade. It's much nicer with a single partition... And as you can see, I don't support the old storage layout any more
Chris
Upgrade to 4.4.4. available
See OP. Please test this. It's an update to android 4.4.4 and lots of additional security fixes.
Oh, and yeah, I recommend to wipe. Email (e.g. and maybe others) will crash without.
Chris
It wasn't obvious, how to do that, so I downloaded the "Storage Upgrader 1.8.7 * (~200MB)" from https://fairphone.zendesk.com/hc/en-us/articles/201189497-Fairphone-OS-multiple-versions-
It doesn't update the partitions when flashing, it does so on the first boot. It also overwrites the recovery.
After that I installed the 4.4.4 image and it boot loops: https://gist.github.com/ChristophHaag/64da8b31533d2c562c92
edit: And so does the 4.4.2 image that has worked before.
*sigh*
edit 2: Formatted a few partitions and tried again - now 4.4.4 works.
0.2 released.
It should fix Netflix (will confirm when all apps are installed after wipe) and should also squash a security problem that bluebox reported (CVE-2014-7911).
It should also make less CTS tests fails.
Still uploading... Edit: Uploaded.
Chris
Hallo, nach dem neuesten update funktioniert xposed-aktivierung nicht mehr. Sonst alles bestens
Sorry, in english:
After the newest update to 4.4.4 no chance to activate xposed-framework. Anyway, thanks a lot
for your hard work
btw Google Authenticator doesn't seem to work correctly on the 4.4.2 version. Authy works though.
jogri said:
Hallo, nach dem neuesten update funktioniert xposed-aktivierung nicht mehr. Sonst alles bestens
Sorry, in english:
After the newest update to 4.4.4 no chance to activate xposed-framework. Anyway, thanks a lot
for your hard work
Click to expand...
Click to collapse
Yes, the last security patches break xposed. https://android.googlesource.com/pl...+/d4d3181d013f8d9b96de8e396b029f8a418894a7^!/
See e.g. here: https://plus.google.com/114407246718577124209/posts/BwiPxSu84bD
Chris
z3ntu said:
btw Google Authenticator doesn't seem to work correctly on the 4.4.2 version. Authy works though.
Click to expand...
Click to collapse
This is most likely related to this issue: https://github.com/google/google-authenticator-android/pull/4
It is most likely an MTK issue with problematic math library (or something like that).
Anyway, it works for me when I use the open source version of the google authenticator: https://github.com/google/google-authenticator-android/releases
Chris
Jeah, I used the Play Store version, but this is also mentionable in "known bugs" (and that they should use the open-source version)
-Week 22, 2022 : Development and Testing Updates-
New build failed. The device tree will still be available on Gitlab. User with ROM building skills can continue building. Newly released applications like App Lounge and the soon-to-be released Privacy central have not been backported to Oreo and Nougat. Volunteers with the skill and bandwidth to backport these applications are welcome.
Users willing to take up the task of ROM Maintainers please let /e/OS Moderator @ManojNairOnline know.
/e/ OS/ (Murena) privacy-enabled LineageOS 14.1 (Nougat) fork
w/ free encrypted 1 GB Cloud Storage and working GPS
How to Install /e/OS on your Samsung Galaxy Note 2: N7100 (3G), N7105 (LTE)
Download latest Dev Build Images: N7100 (3G), N7105 (LTE)
Community | Chat Room | FAQ | HowTos | Get involved | Open Source
Please submit issues so that a developer can be assigned to fix the problem.
Disclaimer:
I am not affiliated with the e.foundation. All kudos go to the /e/ developers. Merci beaucoup!
New in v0.19-n:
Latest bugfixes and security updates from LineageOS source code trees
Please read always first the release Notes before updating
e-0.19-n-20211023142427-dev-n7100.zip (for GT-N7100 / 3G)
SHA256 5f0dd6c498d0e774e9281e09ae54d77059ab160779654b066e831cee98826e14
e-0.19-n-20211023142427-dev-t0lte.zip (for Gt-N7105 / LTE)
SHA256 7d7cbe0f36f9dc4d05f7935228d3154e5127352f6afbe35077c3cfb4f36d8cf1
Cheers!
Somebody installed it?
launcher20 said:
Anybody installed it?
Click to expand...
Click to collapse
Take a look at the YouTube video someone made about it.
Thx. What about bt? In Lineageos its working not good Phone calls are a amazing thing, too.
Installed! BT is working, phone calls ok, but WLAN is not working properly
wpa2/ccmp some times, wpa3 not!
muratafix installed , no change!
launcher20 said:
but WLAN is not working properly
Click to expand...
Click to collapse
You can create and submit an issue and track its progress to completion.
What about GPS? :fingers-crossed:
gps works surprisingly Magisk manager for root works, too!
But opengapps for google playstore doesn`t work. I need it for some paid apps! Any idea? I used actual version 7.1.
launcher20 said:
But opengapps for google playstore doesn`t work. I need it for some paid apps!
Click to expand...
Click to collapse
I doubt that it will be possible to use paid apps from Playstore without further effort.
This ROM has been made primarily for users who do not want to use Google services.
I know. I will try and go on testing! thx for this rom, the first one for nougat all sensors are working!
Update for support wpa3 would be nice!
battery no charging
several sudden reboots
several apps are not working
Sorry!
everything works for me, great rom :good:
I am quite happy with my installation on my N7105. Everything works. The browsing experience is quite smooth. Smoother as with the LineageOs Official that had been installed before.
I rooted with addonsu.
I installed Squit Pro to use the S-Pen productive.
The phone charges slow. With Galaxy Charging Current you get faster charging with more than 1000 mAh.
There is no flipcover function implemented implemeted in the rom. I installed Flip Cover Control to get auto on/off with the stock flipcover.
The cpu is running with 1600 MHz I tried to overclock it but the kernel does not allow that. I didn’t find another kernel till now that can be overclocked??
The /e/ environment is very interesting. Everything worked from the get-go! Mail, Cloud, Map,…nice!
The free account includes 1 GB. I didn’t find an answer to the question how long the account will be free? I hoppe forever??
_________________________________________________________________
Update 19.07.2020
I am very happy with the Rom but i am still interested in improving the performance and the internet browsing experience.
I installed the Kernel Auditor and changed a couple of settings I like to share:
- I set the CPU Governor to on demand.
- In the Governor settings, I increased the down_differential to 40 and the sampling_down_factor to 10. This had a strong impact on the internet scrolling.
- The scheduler to sio with 3072 kB read ahead for internal storage and 128 kB external storage.
- The LMK to 35, 53, 71, 88, 106, 124.
- The swapiness to 20.
- The entropie at 64, 64.
In the developer settings, I forced the DPU rendering.
Now the browsing experience is fine to me. There is definitely room for more optimization.
I would be happy to get some hints!
-------------------------------------------------------------------------------------------------------------------------------
Update 29.04.2022
Still using /E/. The Performance improved with the newer Releases. So i didn't use a Kernel Auditor any more.
But i found it helpfull to modify the buil.prop file. This improved Performance and Battery-life. There are lots of guides in the internet how to do is. For example: https://www.rankred.com/android-build-prop-tweaks/
ro.HOME_APP_ADJ = 1
ro.mot.eri.losalert.delay=1000 //this may brake tethering
ro.ril.power_collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=600
ro.mot.eri.losalert.delay=1000
power_supply.wakeup=enable
ro.config.hw_fast_dormancy=1
ro.config.hw_power_saving=1
debug.sf.hw=1
persist.sys.ui.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
debug.composition.type=gpu
v0.9 Update
Updated ROMs (v0.9) available
N7100: e-0.9-n-2020051153544-dev-n7100.zip
t0lte: e-0.9-n-2020051153544-dev-t0lte.zip
Improvements? Support wpa3?
launcher20 said:
Support wpa3?
Click to expand...
Click to collapse
Which version (3G / LTE) do you use?
Unfortunately there is no info about this in both of the release notes.
Fortunately it's quite easy to submit an issue (N7100, t0lte). Just collapse "open" column, hit the "+" button, edit the title and select your device from the "projects" pulldown menu.
Edit: Only Protonmail is crashing right now, and there is no single problem left. Also I searched a bit and understood how they're backporting security patches to Nougat. I am sorry for false accusations.
It is a great ROM.
New update: https://images.ecloud.global/dev/n7100/
ROM is awesome guys. Everything works. You can use Playstore from Nanolx Fdroid repo for iAPs.
Thank you
v0.10
New versions out now.
0.10-n Release Notes
e-0.10-n-2020081367789-dev-n7100.zip
e-0.10-n-2020081467789-dev-t0lte.zip
Cheers!
i don't know it's my fault or roms fault but i can't play videos with vlc player.