Hello all,
I managed to make a flashable zip to update the GPU Adreno drivers(*) for our device. I'm on CM13 nightlies and I only own the XT1572 single SIM european model, so I really don't know if it works in other variants.
Google Drive link
Dropbox link
Enter TWRP recovery mode and flash the zip + (optional) enable OpenGL 3.2 in build.prop (modify the line to read ro.opengles.version=196610)
Note that changes aren't persistent after a ROM update, so if you are a "flashaddict" you will loose the updated drivers after each rom update, and you should reinstall the zip + (optional) modify the build.prop.
(*) developer preview, does not meet customer release quality
dani_mola said:
Hello all,
I managed to make a flashable zip to update the GPU Adreno drivers for our device. I'm on CM13 06-July nightly and I only own the XT1572 single SIM european model, so I really don't know if it works in other variants.
Google Drive link
Dropbox link
Enter TWRP recovery mode and flash the zip + (optional) enable OpenGL 3.2 in build.prop (modify the line to read ro.opengles.version=196610)
Note that changes aren't persistent after a ROM update, so if you are a "flashaddict" you will loose the updated drivers after each rom update, and you should reinstall the zip + (optional) modify the build.prop.
Click to expand...
Click to collapse
Any insight as to drivers improvements?
gmlogan said:
Any insight as to drivers improvements?
Click to expand...
Click to collapse
Still testing. By now the most noticeable is the OpenGL 3.2 support (build.prop modify required, but I think the Adreno 418 of our SD808 is limited to 3.1) and by the moment I don't see any overheating nor graphics corruption at all.
I was hoping to see Vulkan libraries...
Unless "libllvm-glnext.so" is one of them, but I would expect to see libVulkan.so now.
quakeaz said:
I was hoping to see Vulkan libraries...
Unless "libllvm-glnext.so" is one of them, but I would expect to see libVulkan.so now.
Click to expand...
Click to collapse
I hope so, but Vulkan is natively supported only in the next android version 7.x unlike 6.x that need a 'fork' from the maker side. For example, Samsung made a Vulkan own driver version for their Galaxy 7 model supporting android MM, but I think that Motorola isn't in the work to develop a driver for the 2015 (nor 2016) models running android MM.
CM13 nightly moved to MOB30R branch (05-July) and the latest Adreno drivers are for MOB30M (01-June) so I hope an update from Qualcomm side...
dani_mola said:
Hello all,
I managed to make a flashable zip to update the GPU Adreno drivers(*) for our device. I'm on CM13 nightlies and I only own the XT1572 single SIM european model, so I really don't know if it works in other variants.
Google Drive link
Dropbox link
Enter TWRP recovery mode and flash the zip + (optional) enable OpenGL 3.2 in build.prop (modify the line to read ro.opengles.version=196610)
Note that changes aren't persistent after a ROM update, so if you are a "flashaddict" you will loose the updated drivers after each rom update, and you should reinstall the zip + (optional) modify the build.prop.
(*) developer preview, does not meet customer release quality
Click to expand...
Click to collapse
Can this be flashed on truepure? Rom based on stock?
unitz0mbie said:
Can this be flashed on truepure? Rom based on stock?
Click to expand...
Click to collapse
Yes...
@dani_mola I just flashed those drivers did the build prop edit and man. Thank you. I was getting the lines and weird static on the bottom part of my screen been looking at it for the lady couple months and hated it. Now, it's not prefect but the harsh stripping is gone and the glitchy fuzz is endurable is all I can think you call it. Should've taken a SS before but here's what I'm looking at now http://cloud.tapatalk.com/s/57ba27bab92e7/Screenshot_20160821-181254.png?[/URL]
Does this improves performance?
sooyong94 said:
Does this improves performance?
Click to expand...
Click to collapse
really havent notice much, but some ppl say its smoother. i guess it depends on optimized is your phone, runs different on everyone's phone
Related
Cyanogenmod 7 for Motorola Milestone 2
This is an unofficial Milestone 2 port of CM7.
[ Downloads | Google apps ]
Known limitations
720P recording is not working
ALT lock does not work
Click to expand...
Click to collapse
Changelog:
08.09.2012 - Upgraded CM sources
01.09.2012 - Added OTA updater, upgraded CM sources
21.02.2012 - Upgraded CM sources (fixed blank screen after unlocking issue)
09.02.2012 - Upgraded CM sources
22.01.2012 - Backported ICS animations, UK 2.3.4 fingerprint, fixed Exchange FC for polish locale
04.01.2012 - Upgraded CM sources (e.g. T9 dialer)
29.11.2011:
Moved device specific settings to its own tree in the settings
Added lower backlight level
New multitouch module (no delay at startup)
Stock compass callibration app and audio effects
20.11.2011 - Hopefully fixed some wifi issues
18.11.2011 - Wifi tethering does not need DUN APN anymore
18.11.2011 - Fingerprint changed to UK 2.2 (fix Market from hiding some apps)
12.11.2011 - Tweaked CPU, camera, build.prop and recovery settings (Endless7);
settings for Droid2Bootstrap (will not destroy 2nd-init anymore)
11.11.2011 - Added keyboard switching, option to force PLMN display, more multitouch points
08.11.2011 - Fixed camera's photos
08.11.2011 - Initial release
Click to expand...
Click to collapse
Note:
If you have updated to stock gingerbread, you can't use this rom until you downgrade.
Instructions for upgrading from stock ROM:
1) Install Droid2 Bootstrap Recovery
2) Boot into recovery
3) Optionally: create a backup of your data
4) Choose Install zip from sdcard -> Choose zip from sdcard and select downloaded ZIP file.
5) Optionally: install Google Apps the same way
6) Wipe data/factory reset
7) Wipe cache partition
8) Reboot and enjoy
9) Optionally: use attached Baseband switcher app if you have troubles with phone signal.
Click to expand...
Click to collapse
Instructions for subsequent upgrades or upgrade from any CM7.x ROM:
1) Boot into recovery (long power off -> Reboot)
2) Choose "Install zip from sdcard" -> "Choose zip from sdcard" and select downloaded ZIP file.
3) Advanced -> Wipe battery stats
4) Advanced -> Wipe dalvik cache
5) Reboot and enjoy
Click to expand...
Click to collapse
As you can see, the update from the stock ROM requires a complete wipe, so be sure to backup your important data!
GIT sources:
repo init -u git://github.com/tezet/android.git -b gingerbread
Any collaborators are more than welcomed!
Click to expand...
Click to collapse
Donations
If you like and appreciate my work, and you may donate here (now in English).
Click to expand...
Click to collapse
Many thanks to Quarx for his Defy port and all folks involved in [email protected]
Looks very promising. Browsing your github right now.
Edit: Thanks for your effort. I was trying to start a similar project but some events IRL left me with NO free time at the moment. If there's any info you'd like to get from me just let me know.
What is the difference between this and the CM made by Endless7?
If this is really based on m2 files, that is a great progress
How is hardware video decoding working?
Edit: Difference is that there is no need to patch every build to make it work, and fixing things like video or 720 will be more easy to do.
And the really big difference, is that this way, we can get official cm7 support.
Yes, DSP decoding is working, including 720P.
I got lot of troubles with 720P encoding and gave up for now. Maybe I will come back to the topic, but for now I have already spent too much time on this...
Nice work, thanks!
Will I get anything extra in compare with Endless7 build? I mean, if I will now use your build instead CM7 from Endless7, will I get any perfomance boost or anything else than 720p decoding (can it hw decode same formats as stock firmware btw?).
Just asking.
Anyway thanks for this - official cm7 support would be nice.
I would say the most noticable difference is a better touch screen. Also the battery seems to be slightly better, but that may be very subjective opinion...
I'm not sure how about general DSP decoding, but at least h264 720P decoding didn't work in Defy build.
And I'm not sure what is the current state of Endless7's ROM, but this is the most noticable difference when I switched to this ROM.
From the APPs point of view, it is pure CM7.1, without any addons, so you may miss some Endless7's extra stuff...
Edit: I haven't verified lot of formats, just few 720P videos. If you notice anything missing in comparison to the stock rom, it may be probably fixed easily...
Forgot that, this roms uses another kernel
UK kernel should improve touch
Wonder if we can make it boot with a 2.3 kernel...
Another thing, phone will be listed as a953 on pc instead of 722, with uk kernel.
I guess I will wait for UK version of GB release before I will attempt to switch into GB kernel. I would like to use the same source of kernel and bpsw. There's no big gain in running GB kernel, really.
Yep, we are just a few days away from uk release.
2.3 kernel improve touch significantly from uk 2.2. Besides that not much more.
Is the multi touch working properly?
Yeap, the same as stock froyo.
I mean, the gingerbread roms here have 6 points multi-touch, is it the same here?
No, I haven't included that. You may add it by yourself, it's just a matter of module. Maybe I will include in the next builds, but it will be disabled by default. I'm not sure if it doesn't have any negative impact on touchscreen responsiveness...
Edit: why would you need that anyway? Is there any real-life use case other than keyboards?
As far as I see:
# use default multitouch configuration
ro.product.multi_touch_enabled=true
persist.sys.multitouch=2
You could change to 6 and you will get 6 points touch (maybe you have to add the module)
But, dont use anything higher than 4. It makes cpu consumption higher and laggy response in ALL roms.
Thank you for this great work !
A lot of people will be interested to know that it's possible to install your update.zip without data wipe when coming from Endless's CM7.
Forgot about it. It's perfectly OK to update from any CM7 rom without wipe. Just follow the usual upgrade procedure.
Could you consider adding a keyboard layout option in your nexts builds?
Also, alt-lock is not working at the moment. It's not critical though...
I also noticed bad 3d performance in Quadrant.
On the "planets" test, using Endless cm7 i get something like 60fps, but 10 with yours. Didn't notice any change when playing with n64oid/ogl-es though.
Edit : Scored 13.6 at Nenamark2, 21.6 at Nenamark1. Could somebody compare with Endless's CM7?
Edit2 : Concerning Quadrant, I remember getting 10fps too when on stock french 2.2.2 rom.
Thanks. Keyboard switch is on the top of todo list
I will look into 3D performance and compare it tomorrow with stock 2.2.2. Perhaps that's the UK's libs issue...
As for the ALT lock, that is on the very bottom of todo list I believe it does not work on Droid 2 either.
Edit: just confirmed the same result (10FPS) with stock 2.2.2 UK rom. Anybody could confirm it is really faster on Endless7's ROM?
I have a major bug with the camera : files created are 0byte large.
Video recording works fine.
Hey there guys,
I found these drivers http://forum.xda-developers.com/showthread.php?t=2238348, but they are not suitable ATM.
Sorry for making you all happy with something that doesn't work. Let's make a good discussion about how we can instead make all this work.
steyn_e said:
Hey there guys,
I found these drivers http://forum.xda-developers.com/showthread.php?t=2238348 for our Sensations, which solves the graphical glitches in Google Maps 7. Please all use these in your ROM's. I also found an even newer version, but that is not compatible with the Linux kernel we are currently using (3.0.x).
The build number for these are [JB_VANILLA.04.02.02.060.053]. These need a 3.4.x kernel.
I hope you can all enjoy these! The package can be downloaded here.
You can simply be flash it through 4ext, afterwards clear dalvik+cache.
Have fun!
Click to expand...
Click to collapse
If they need a 3.4.x kernel you need to state clearly that they are for JB sense. None of the aosp jb roms here use a 3.4.x kernel.
sjknight413 said:
If they need a 3.4.x kernel you need to state clearly that they are for JB sense. None of the aosp jb roms here use a 3.4.x kernel.
Click to expand...
Click to collapse
Only the latter ones (which I didn't include a link for) are for 3.4.x. The ones linked work for 3.0.x, and I am using them now on CM10.2. They will also work on CM10.1, and maybe on CM10 if the kernel is 3.0.x or over. I'll try to find a link for the other ones for people using a Sense based ROM.
Okay, I made myself clear. The first download is for kernel 3.0.x (tested on CM10.2 and working), the second download is for kernel 3.4.x (and maybe further), but I cannot test that as I am not using a Sense based ROM. It is sourced directly from Qualcomm.
Now I'm thinking of it: we should probably make a list of compatible kernels for the different drivers. I'm using the Albinoman 3.0.100 kernel.
Sad to say, but I've still got glitches.. Installed with 4Ext and wiped cache + dalvik cache.
Albinoman's 4.3.1 26-10 with his kernel.
84Guzz said:
Sad to say, but I've still got glitches.. Installed with 4Ext and wiped cache + dalvik cache.
Albinoman's 4.3.1 26-10 with his kernel.
Click to expand...
Click to collapse
You did install the upper one? Which version of Maps are you using?
Also, what is the Linux kernel version of your rom (in device info)?
Let's make this work...
steyn_e said:
You did install the upper one? Which version of Maps are you using?
Also, what is the Linux kernel version of your rom (in device info)?
Let's make this work...
Click to expand...
Click to collapse
Yes, I got the one for a 3.0 kernel
Maps: 7.3.0
Kernel version: 3.0.100
The glitches are not as bad as they used to be, but try drawing the notification bar. Also the dialog to turn on GPS when starting navigation will flicker.
Edit: Press the "go to my location" button (top right) it will prompt a dialog to turn on GPS, which will flicker between opaque and transparent
84Guzz said:
Yes, I got the one for a 3.0 kernel
Maps: 7.3.0
Kernel version: 3.0.100
The glitches are not as bad as they used to be, but try drawing the notification bar. Also the dialog to turn on GPS when starting navigation will flicker.
Edit: Press the "go to my location" button (top right) it will prompt a dialog to turn on GPS, which will flicker between opaque and transparent
Click to expand...
Click to collapse
Tried it. It does the same with me once, but the second time it didn't. And just moving through maps doesn't glitch anymore.
steyn_e said:
Tried it. It does the same with me once, but the second time it didn't. And just moving through maps doesn't glitch anymore.
Click to expand...
Click to collapse
Do you mean you tried the notification bar? This keeps glitching with me.
Moving trough maps is OK indeed.
I've now modded the 2nd set of drivers to install on my device, let's see how this goes.
A few things:
1. These libs don't boot. If they "booted" for you then that's because the installer never installed them. The line in the updater script to mount /system makes it try and mount system as a yaffs2 partition, but we don't use yaffs2 we use ext4, so /system is never actually mounted. I modified the installer so it actually installs the libs and they do not boot. Some more proof of this is that the zip flashes very quickly, when it should actually take about 10-15 seconds to flash. They probably require a kernel with ION and a GPU driver from a 3.4 kernel.
2. Our Maps glitches are not being caused by our Adreno libs. Read my post HERE
3. The package for 3.4 kernels is not a flashable zip.
4. The package for 3.4 kernels does not necessarily require a 3.4 kernel (I have booted them on a 3.0 kernel); all they require is a kernel with a GPU driver from a 3.4 kernel and ION.
android1234567 said:
A few things:
1. These libs don't boot. If they "booted" for you then that's because the installer never installed them. The line in the updater script to mount /system makes it try and mount system as a yaffs2 partition, but we don't use yaffs2 we use ext4, so /system is never actually mounted. I modified the installer so it actually installs the libs and they do not boot. Some more proof of this is that the zip flashes very quickly, when it should actually take about 10-15 seconds to flash. They probably require a kernel with ION and a GPU driver from a 3.4 kernel.
2. Our Maps glitches are not being caused by our Adreno libs. Read my post HERE
3. The package for 3.4 kernels is not a flashable zip.
4. The package for 3.4 kernels does not necessarily require a 3.4 kernel (I have booted them on a 3.0 kernel); all they require is a kernel with a GPU driver from a 3.4 kernel and ION.
Click to expand...
Click to collapse
Yes, I've noticed the META-INF was missing in the 2nd one. However, it did do something. Maps is not even nearly as glitchy as it was. It only glitches now if something pops in front (like that "do you want to enable GPS" or the notification bar).
Our Adreno drivers want ION, and the camera wants PMEM, however is it even close to possible to make the camera libs work with ION?
steyn_e said:
Yes, I've noticed the META-INF was missing in the 2nd one. However, it did do something. Maps is not even nearly as glitchy as it was. It only glitches now if something pops in front (like that "do you want to enable GPS" or the notification bar).
As it is nearly impossible to rewrite the Adreno libs to use PMEM, is it even close to possible to make the camera libs work with ION?
Click to expand...
Click to collapse
Sebastian modified VilleC2 camera libs to work with our camera sensor and rewrote the camera driver, but Sebastian is on a whole different level from me
Also, the first package did absolutely nothing. I tested it and nothing was flashed to /system because the installer couldn't mount /system (because it's trying to mount /system as yaffs2). My Adreno version did not change, and when I fixed the package to install correctly, my phone did not boot (as they probably require ION and a 3.4 GPU driver; my kernel has a 3.4 GPU driver but ION is still necessary to get them booting). There's no such thing as in between with these Maps glitches; the glitches are either there or they're not.
android1234567 said:
Sebastian modified VilleC2 camera libs to work with our camera sensor and rewrote the camera driver, but Sebastian is on a whole different level from me
Also, the first package did absolutely nothing. I tested it and nothing was flashed to /system because the installer couldn't mount /system (because it's trying to mount /system as yaffs2). My Adreno version did not change, and when I fixed the package to install correctly, my phone did not boot (as they probably require ION and a 3.4 GPU driver; my kernel has a 3.4 GPU driver but ION is still necessary to get them booting). There's no such thing as in between with these Maps glitches; the glitches are either there or they're not.
Click to expand...
Click to collapse
So I've noticed. Isn't Sebastian's kernel ION?
steyn_e said:
So I've noticed. Isn't Sebastian's kernel ION?
Click to expand...
Click to collapse
Yes. Sebastian's kernel satisfies all the requirements to use these libs (ION and 3.4 GPU driver) so they should boot on any ROM using his kernel.
android1234567 said:
Yes. Sebastian's kernel satisfies all the requirements to use these libs (ION and 3.4 GPU driver) so they should boot on any ROM using his kernel.
Click to expand...
Click to collapse
Now the final thing is obviously to make that kernel work with your ROM. Possible at all?
steyn_e said:
Now the final thing is obviously to make that kernel work with your ROM. Possible at all?
Click to expand...
Click to collapse
Even if I managed to get all the basic things working (which I don't think I can do), getting the camera working would be a problem and we'd probably be forced to use PMEM on the whole kernel (which would defeat the purpose of a 3.4 kernel).
android1234567 said:
Even if I managed to get all the basic things working (which I don't think I can do), getting the camera working would be a problem and we'd probably be forced to use PMEM on the whole kernel (which would defeat the purpose of a 3.4 kernel).
Click to expand...
Click to collapse
That means there is no hope for getting every single thing to work on our phones?
steyn_e said:
That means there is no hope for getting every single thing to work on our phones?
Click to expand...
Click to collapse
Man, we are running android 4.3 on phone which was officialy updated to 4.0 only. That is normal that some thing arent working
Wysłane z mojego HTC Sensation przy użyciu Tapatalk 4
szotaa said:
Man, we are running android 4.3 on phone which was officialy updated to 4.0 only. That is normal that some thing arent working
Wysłane z mojego HTC Sensation przy użyciu Tapatalk 4
Click to expand...
Click to collapse
That doesn't mean we shouldn't try. I'd love to learn more about this stuff. And if someone can teach me, we Sensation users will have another driven Devver. I won't be able to do this on my own however, as it has been too long since I've last been devving for a Phone (that was my Touch Pro 2).
Disclaimer:
/***
* Your warranty is void now (and I'm sure it was void before this process).
* I am not responsible for hard or soft bricked devices, boot loops, dead or corrupt sd cards, strange behavior or you getting a heart attack 'cuz your youtube app is not working properly.
* YOU and only YOU are choosing to make these modifications, do not blame on me.... I will just ignore you.
***/
Features:
Rom size of 619.4 MB (of 1.4 GB)
112 bloat/useless apps removed
Rooted with SuperSu as systemless
Busyboxed
Deodexed
Zipaligned
Nova Launcher as default launcher (installed as user app if you want/need to remove it)
Google Chrome present (just because SetupWizard need it at first boot)
Android O emojis by default (Android Nougat and iOS emojis present but not active)
Neon Android logo bootanimation added
Qualcomm bootanimation sound added
Installation steps:
Download the new assert-twrp version or the [email protected] twrp (wich should work if the stock rom worked) version and flash it as you would normally do it.
Standard Wipe (factory reset) and Format Data are optional (unless you have a non-stock based rom installed already). If you want a full fresh start you should format data, reboot into recovery again and do an standard wipe x3.
Install the rom.
Notes:
Your phone may reboot twice
Bootanimation it may take up to 4 minutes (as in my case)
Optimization process may take up to 5 minutes (as in my case) as a result of deodexing and zipalingning the rom
Download files:
New assert-fixed twrp version: https://www.androidfilehost.com/?fid=889764386195921266
czarsuperstart twrp version: https://forum.xda-developers.com/android/development/twrp-lg-aristo-aka-lv3-t3656019
Rom: https://www.androidfilehost.com/?fid=745425885120757599
Bugs:
You tell me...
------------------------------
Device: LG Aristo
Model: LGMS210
Code Name: lv3
Carrier: MetroPCS
Android version: 7.0
Software version: MS21010i
Patch level: April 1, 2017
Reserved 1...
Reserved 2...
I will add some screenshots later as I don't have the time this night.
Be patient guys...
I hope you enjoy it...
I was able to get messi2050 lineage for the stylo 2 plus to boot only problem wifi dont work and phone calls produced a shrill sound to the person on the other end. I split the kernel from your Rom and repack the lineage kernel and used messi2050 twrp that has the phone as ph2n. Maybe you can possibly get it working?
https://youtu.be/nbIL2jAacug
Gonna test it out now and I'll run a couple of stress tests.
Testing now! Thanks!
Minus Dolby and V4A, this is my currant app tray and god damn!
Overall boot time was 5 minutes. The optimizing apps stage took less time than the boot animation to finish.
Anyway, no bugs so far after such a heavy slim down.
My ram use is much better though, instead of it standing at 200 megabytes being withheld in standby, it's been bumped up to 700 megabytes at standby.
I tried installing this and it says error my device is not lv3
HaxUrMom69 said:
I tried installing this and it says error my device is not lv3
Click to expand...
Click to collapse
Check OP and replace any old twrp version that you currently have installed.
xtremelora said:
Check OP and replace any old twrp version that you currently have installed.
Click to expand...
Click to collapse
The twrp provided is a .7Z file
HaxUrMom69 said:
The twrp provided is a .7Z file
Click to expand...
Click to collapse
Just decompress the file and you should be able to get the .img
ninjasinabag said:
My ram use is much better though, instead of it standing at 200 megabytes being withheld in standby, it's been bumped up to 700 megabytes at standby.
Click to expand...
Click to collapse
I don't get it....
???
xtremelora said:
Just decompress the file and you should be able to get the .img
Click to expand...
Click to collapse
flashing worked this time. thank you for the help
Lineage completely fixed.
@messi2050 you know that I'm going to try and port it once it's uploaded lol. If Wi-Fi works on the aristo also it would be great.
[email protected] said:
@messi2050 you know that I'm going to try and port it once it's uploaded lol. If Wi-Fi works on the aristo also it would be great.
Click to expand...
Click to collapse
Lemme know if you get it booting down the line, I'm open for testing.
ninjasinabag said:
Lemme know if you get it booting down the line, I'm open for testing.
Click to expand...
Click to collapse
I already got it booted the phone is not working right. I'm uploading it now so he can try to work on it. Xtremelora.
[email protected] said:
I already got it booted the phone is not working right. I'm uploading it now so he can try to work on it. Xtremelora.
Click to expand...
Click to collapse
check this line in build.prop
ro.telephony.ril_class=LgeLteRIL
if is commented out reenable it to fix calls
I'll try it out. Im waiting on the newer build to actually really work on it but I'll check it out.
EDIT 2018-1-10
Changed ROM download link from single file to folder structure.
The folder will include new builds for OPPO R7f
Latest build currently 09-14
First off this wouldn't be possible without mikeNG, TheMuppets, LineageOS team
I'm just the cook
Devices supported: R7f, ONLY
Do not flash this rom on any other R7 variants. It will brick the device
Device specific changes/fixes compared to previous release:
BUILD: 07-15
* Tape 2 Wake should be completely functional now!
* Updated Oreo source (OPM2.171026.006.H1)
* Various minor kernel & device specific changes (Check Github)
BUILD: 09-14
* Android security patch level updated (September)
* Updated Oreo source (OPM6.171019.030.K1)
* Various minor device specific updates (check git)
* Various minor LineageOS updates (check git)
* Not verified, battery lifetime seems a bit longer
How to install and all that kind of jazz please refer to my previous 15.1 thread
Updating from previous 15.1 release. Regular wipe in recovery is enough also wipe Dalvik & Cache
Downloads :
[ROM] Unofficial R7f LineageOS 15.1
Archive must be unpacked! Contains flash-able zip & md5 checksum
[Gapps -> ARM -> 8.1]
*Don't select the Aroma variant. TWRP doesn't like it
[TWRP Recovery for R7f] (twrp-3.2.2-0)
thank you. I am downloading and want to try it now.
Thanks again. It looks like it's time for me to try it as well.
P.s. please don't create a new thread for each release
Forage81 said:
Thanks again. It looks like it's time for me to try it as well.
P.s. please don't create a new thread for each release
Click to expand...
Click to collapse
I'll keep this as a rolling thread
PS. I wasn't unable to successfully build with Ubuntu
ParrotOS worked much easier and seems more stable as build environment
Wow this is great! thanks!
oh and would u be updating the build with the new lineageos features like true dark mode etc.?
ph03nae said:
oh and would u be updating the build with the new lineageos features like true dark mode etc.?
Click to expand...
Click to collapse
With the next (major) device specific changes and/or android changes I'll make another build which will include the newer LineageOS features
Guess within the next 1 ~ 2 Months you could expect another build from me.
In the meantime I'm taking a crash course on Android kernel development.
Would be nice to squeeze some extra juice out of this device.
JJRT said:
With the next (major) device specific changes and/or android changes I'll make another build which will include the newer LineageOS features
Guess within the next 1 ~ 2 Months you could expect another build from me.
In the meantime I'm taking a crash course on Android kernel development.
Would be nice to squeeze some extra juice out of this device.
Click to expand...
Click to collapse
Alright! Will be looking forward to the next release! (oh and btw is it possible to shift the power menu from the right to the left since the power button is on the left?)
ph03nae said:
Alright! Will be looking forward to the next release! (oh and btw is it possible to shift the power menu from the right to the left since the power button is on the left?)
Click to expand...
Click to collapse
You'll have to do that yourself
I want to keep this ROM a pure LineageOS source no modified frameworks
Try Xposed with NeoPowerMenu module, think it's able to do the trick
@JJRT,
Thank you very much for 'cooking' this ROM! On vacation I discovered that GPS did not work on that old 7.1.2 version. Now again works perfectly fine with this ROM!
I have one small problem though. Android indicates that my SD card is corrupted and want to fix it by 'configuring' it.
1) Does anyone know if it is actually going to try to fix it or will it just reformat it?
Obviously I do not want the latter. I would rather remove it from the phone and repair it in my PC.
2) Can I 'hot swap' the SIM/SD tray or do I really need to turn off the phone? The latter will most likely cause the phone to go into boot loop.
Thanks in advance for any help or info.
eximiusnl said:
@JJRT,
Thank you very much for 'cooking' this ROM! On vacation I discovered that GPS did not work on that old 7.1.2 version. Now again works perfectly fine with this ROM!
I have one small problem though. Android indicates that my SD card is corrupted and want to fix it by 'configuring' it.
1) Does anyone know if it is actually going to try to fix it or will it just reformat it?
Obviously I do not want the latter. I would rather remove it from the phone and repair it in my PC.
2) Can I 'hot swap' the SIM/SD tray or do I really need to turn off the phone? The latter will most likely cause the phone to go into boot loop.
Thanks in advance for any help or info.
Click to expand...
Click to collapse
Likely partition filesystem issues/corruption.
Preferable to do this with a SDcard-reader
Under Linux I'd suggest using Gparted to check/change filesystem and/or format
Under Windows Paragon Partition Manager™ Would do the job splendidly. Even ext4 / exfat layouts
And yes you could hotswap with phone still on, but I wouldn't recommend doing so out of precaution
I notice the following issues with this ROM:
1) Battery life noticeably less than the 'old' 7.1.2 (of 23-8-17).
2) Notifications arrive 20 to 30 minutes late.
3) In the about it says "Playform: msm8916", which is a 4 core Snapdragon 410. However, the R7f contains MSM8939, which is an 8 core Snapdragon 615. Does this mean only 4 cores are used?
eximiusnl said:
I notice the following issues with this ROM:
1) Battery life noticeably less than the 'old' 7.1.2 (of 23-8-17).
2) Notifications arrive 20 to 30 minutes late.
3) In the about it says "Playform: msm8916", which is a 4 core Snapdragon 410. However, the R7f contains MSM8939, which is an 8 core Snapdragon 615. Does this mean only 4 cores are used?
Click to expand...
Click to collapse
1: I do notice a bit, not dramatically
Concerning battery , did you do a clean install? (format data / cache / system) coming from 14.1 it's advisable to do so
2: Not having those issues (WiFi and 3G) Whatsapp/gmail/youtube notifications are near instant. Have more info?
3: Yeah not sure what the deal is with that. While building the rom it does use the msm8939 sources from LineageOS/TheMuppets
But indeed the info screen of 'Model & Hardware' Does report msm8916. Shall look into that (Guess it's just a left over from a initial script source they've used)
Other diagnostic software does identify it correctly and the performance is on par with 8939
JJRT said:
1: Concerning battery , did you do a clean install?
Click to expand...
Click to collapse
Yes, I did a complete wipe.
JJRT said:
2: Not having those issues (WiFi and 3G) Whatsapp/gmail/youtube notifications are near instant. Have more info?
Click to expand...
Click to collapse
Notifications usually get in when I click the button on the left side to unlock the phone or after a certain time (20-30 minutes). So it seems it does not work instant when the phone is locked.
I also notice that I only get notifications from email, sms and whatsapp. I checked the settings and notifications are enabled for all apps, but I do not get any notifcations from any other apps.
eximiusnl said:
Yes, I did a complete wipe.
Click to expand...
Click to collapse
Try getting some stats about what is eating your battery in the battery usage section of the settings or an app like BetterBatteryStats.
With the 14.1 lineageOS release I sometimes have/had that sensor use went nuts for a long period of time, draining battery as a result.
eximiusnl said:
Notifications usually get in when I click the button on the left side to unlock the phone or after a certain time (20-30 minutes). So it seems it does not work instant when the phone is locked.
I also notice that I only get notifications from email, sms and whatsapp. I checked the settings and notifications are enabled for all apps, but I do not get any notifcations from any other apps.
Click to expand...
Click to collapse
Can it be that this only happens when you are connected to WiFi? If yes, verify the WiFi settings to make sure remains connected or if it's not doing something else undesirable.
is it possible to activate camera2api and install google camera? Los 15.1
Ravhinzy said:
is it possible to activate camera2api and install google camera? Los 15.1
Click to expand...
Click to collapse
Currently no, camera firmware restriction
Might become possible if someone manages to update the sources, but I wouldn't count on it
JJRT said:
Currently no, camera firmware restriction
Might become possible if someone manages to update the sources, but I wouldn't count on it
Click to expand...
Click to collapse
Just curious, who would be able to update the sources/what needs to done to update the sources?
I solved the problem with the notifications of Whatsapp. The trick is to disable battery optimization for Whatsapp. Of course this is even worse for the battery life. I find it interesting that Android 8 has measures to save battery, but ends up using much more battery than 7.1.2.
This does not help for the apps that do not give any notifications at all. Maybe there is something changed in the way Android 8 handles notifications? I did read some comments from one app maker that they had updated their app to make notifications work on Android 8.1.
ph03nae said:
Just curious, who would be able to update the sources/what needs to done to update the sources?
Click to expand...
Click to collapse
Someone with low-level hardware/firmware/kernel knowledge
What exactly needs to be changed in order to make it compliant, I don't have a clue. It's over my head
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