This is unofficial cm11 kitkat android 4.4.4 for the Virgin Mobile Optimus V (runs on Sprint Optimus S as well)
Uses my 3.08 kernel.
I'm offering this over here because skinbark has been busy for quite a while and my builds are way more updated these days.
Purely experimental builds. No real support, I'm sharing my personal builds plus making equivalent internal builds for those of you who like them.
newest builds offering f2fs os2sd!
also fixed camera, and kernel updated to 3.0.101 with HardLight's patchset.
second post mostly outdated, now it's opengapps instead of pa for example. I haven't been updating this in literally years.
now using some of
[COMMIT] [AOSP] JustArchi's ArchiDroid Optimizations - Increases performance up to 6x
go thank justarchi for source of optimizations.
not right now said:
now built with linaro gcc 4.7 (kernel is built with homebrew ct-ng armv6k tweaked linaro gcc 4.7) with -O3 optimizations, except -Os thumb.
Click to expand...
Click to collapse
Wifi AP will reboot if turned on/off/on.
Everything else should work, tell me if it doesn't.
OS2SD /data mounting tweaks from HardLight's OS2SD version.
Smaller, more limited, standard nand-flashable internal builds offered for backwards compatibility or the less adventurous.
Use only THIS RECOVERY (info) (download)
archived said:
OS2SD friendly TWRP recovery, handles partitioning of sd card for OS2SD thanks techvendetta
Click to expand...
Click to collapse
download folder for internal builds:
download folder for OS2SD builds:
here's partitioning info for the OS2SD recovery.
advise: whatever leftover on your card for VFAT/sdcard, either 1Mb or 864Mb swap, 512Mb-768Mb for system, 1Gb or more for data.
expand /sdcard and/or /data as preferred if you use a bigger card. more space in /system? dunno why. doubt there's enough armv6 system apps to fill 512Mb.
current internal build: cm-11-20141014-EXPERIMENTAL-bigsuperROM_internal-thunderc.zip
current OS2SD build: cm-11-20141018-EXPERIMENTAL-f2fs_os2sd_bigsuperROM-thunderc.zip
this should be considered a dev thread since it's on XDA, there's an earlier and discussion thread here.
Sprint and Verizon fix zips attached. Flash in recovery after the ROM before first boot.
OS2SD info in 2nd post.
almost forgot: source
https://github.com/bigsupersquid/android_roomservice
Gapps:
advise: Skinny_4.4_Gapps_new_internal.zip for easy gapps. From here Optimus S won't fit the larger Skinny_4.4_Gapps-new.zip but the V should.
Be patient on first boot. Some reports are as long as 10 min to get past the bootanimation. Takes me at least 5 min.
Carrier Fixes:
Sprint and Verizon. Want another? Got an apns-conf.xml, then post it and your other carrier info.
Basic instructions for internal install:
in twrp, wipe internal data, internal system, and cache.
flash rom, internal carrier fix, gapps.
reboot system.
androidarmv6 turned on TLS in the kernel, and swapped the /system and /data partitions for more room on /system, so you have to use the newest TWRP-multi now as well.
thanks androidarmv6, cyanogen, aosp, thekraven for TheJBC and help, skinbark for initial booting and much work on kitkat for these phones, and techvendetta for his TWRP port. Thanks androidarmv6 and thunderg devs for 3.08 kernel I ported over to thunderc, and HardLight for f2fs in kernel and fstab flags.
OS2SD
OS2SD information
I have been playing with rom-from-sd for quite a while.
kitkat and cm11 make it easy, just by changing the fstab you can mount the ext partitions instead of the mtd partitions in init.*.rc
OS2SD (skinbark named it, it was my mod) uses the regular VFAT plus 3 extra ext4 (or one linux-swap and 2 ext4) partitions on the SD card to hold /swap, /system, /data. Recommend in order: leftover after other 3, 512MB, 512Mb, 1024Mb.
This allows virtually unlimited storage without link2sd methods of any kind. /system can handle whatever you want to flash to it without running out of space, which is handy because kitkat has to be trimmed down to fit an Optimus S or V with their respective 15*Mb or 165Mb of /system space.
when android is running from the card, mount external storage allows manipulation of /system and /data from your linux file manager.
Yeah, yeah, it's all a security hole, but I don't care. It's experimental and fun, and you can fit hundreds of apps on this four year old phone that is labelled 'obsolete' by LG and Qualcomm both.
I still need to remove the 'format sd' and 'unmount sd' from the storage menu in settings to avoid crashes.
Gapps:
advise: Skinny_4.4_Gapps-new.zip for easy gapps. From here
if you want a REAL gapps package...
I made pa_gapps flashing facilitator for twrp/os2sd.
Go get current micro pa_gapps, don't touch the zip.
flash after rom, pa_gapps_modular_micro*.zip no reboot needed.
then after flashing pa_gapps you flash the facilitator (it gets rid of armv7 keyboard libs and installs compatible play services framework.)
Click to expand...
Click to collapse
if you want to use any bigger pa_gapps packages (and you can even install the 200+Mb Stock package on os2sd!) you'll have to follow the instructions for the pa_gapps remover zip TKruzze posted up to remove Google+ (or you'll have fc'ing nightmares) and don't let it install Chrome either (there's another text file needed on the card like the remover, TKruzze left instructions.)
Remember, if you install Google Now (Search) go as quickly as possible into app drawer>Google settings>Search and Now>Voice>Hotword Detection and turn it off, then back up one submenu to Voice again and turn off all the checkboxes.
You can install voice search and talkback from market (enable talkback in accessibility settings) for those functions without fc. (and voice search wrapper from xda if you want voice control over Search.)
or just go the easy way on os2sd and use the Skinny_4.4_Gapps_new.zip which don't need a facilitator. But it's harder to get current Google Search that way since Play thinks we can't handle it.
Basic instructions for OS2SD install:
Use NEW twrp.
Wipe system, data, cache. Flash ROM carrier fix, gapps.
reboot.
reserved
Thanks for this! Just got this as a replacement phone, good to see support. Any recommended gapps? And is art supported?
Edit: Neither Banks nor PA gapps seem to work past setup. slimgapps or whatever its called in the other forum is all that goes then it seems.
Sent from my LG-LS670 using xda app-developers app
I cannot believe this phone is still going. You are the man, bss!
Sent from my SPH-L710 using xda app-developers app
Maestertk said:
Thanks for this! Just got this as a replacement phone, good to see support. Any recommended gapps? And is art supported?
Edit: Neither Banks nor PA gapps seem to work past setup. slimgapps or whatever its called in the other forum is all that goes then it seems.
Sent from my LG-LS670 using xda app-developers app
Click to expand...
Click to collapse
I forgot to link gapps. the skinnygapps from ac are the basic model.
I just tried pa gapps and they work ok without onetimeinitializer and setupwizard,
I haven't seen reference to art running on any armv6. I tried to walk it thru compilation early on, but ran out of free time to keep translating the thumb2 asm to thumb1 (or finding source where others had already done so) so it'd work.
new os2sd build.
zram turned on, p500 ami304d to match their kernel drivers (long-standing whoops there.)
probably other cm changes. I don't track em I just build and use it.
update. new builds up.
Excellent rom, but every so often it will freeze up and reboot. Is this normal? Im doing nothing but basic tasks like listening to music and then it freezes and reboots itself....
Sent from my GT-N5110 using xda app-developers app
ghostswagking said:
Excellent rom, but every so often it will freeze up and reboot. Is this normal? Im doing nothing but basic tasks like listening to music and then it freezes and reboots itself....
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
check your overclock, if it's too high you'll get random reboots. Best way I've found is run gallery while OC'd and play with it until it reboots. Set OC down on notch below where it doesn't reboot in gallery or camera.
If you're not OC'd then I'm not sure why it's doing that. some apps cause issues. logcat or /data/tombstones may have stuff you can pastebin if you want me to look into why.
4.4.3 update later today .
bigsupersquid said:
4.4.3 update later today .
Click to expand...
Click to collapse
bump... rom update, carrier fixes need updated but should work as long as you don't mind settings showing old build.
bump for really new release.
now using
[COMMIT] [AOSP] JustArchi's ArchiDroid Optimizations - Increases performance up to 6x
go thank justarchi for source of optimizations.
now built with linaro gcc 4.8 (kernel is only linaro gcc 4.7) with -O3 optimizations.
4.4.4
Looks like next rev be along here soon.
4.4.4
Gotta see if anything really changed.
big update
requires new recovery.
carrier fixes updated to 4.4.4
new release.
BUG:
ADB debugging needs toggled off and on to recognize cable.
Otherwise, optimized, with linaro kernel.
Might need to update your TWRP (since this is experimental, after all, things change.)
bugfix release.
takes care of adb toggle to connect cable issue.
adds armv6k-specific toolchain optimizations.
bump
new kernel toolchain (I built a linaro 4.7.4 with crosstool-ng with armv6k-specific flags)
p500 config imports... zram reenabled and selinux enforcing.
probably other upstream changes.
no screenshot
Related
OneClickLagFixV2PLUS inside the app is currently in RELEASE status. It has been tested on a fairly enormous number of devices without issue.
This is an APK (Normal Android App) that will install an EXT2 lag fix for you.
The APK itself can support a number of different lag fixes. It currently has the old OCLF V1 fix, which uses symlinks, and it now also has a new V2 fix which uses bind mounts.
This is in a new thead, as the old thread is very very long, and this is now version 2.
New features of the OCLF2+ lagfix vs OCLF1+
- Bind mounts are faster and require less O/S overhead than symlinks, making this fix smoother in everyday use.
- The bind mount allows for Android to report the correct free space available.
- If something goes wrong at boot, and the bind mount does not initialize, you will boot up to a copy of your data from before the lagfix was applied. This makes V2 safer than V1. (copying /system/bin/playlogosnow onto /system/bin/playlogos1 will effectively restore your device to how it was before you applied the lagfix. There is also an undo option, which will copy all of your changed data back to RFS before restoring.)
- As a bonus, an option to set the wifi screen off timeout is included.
How to use this:
Copy over the APK file onto your phone, and run/install it as normal using 'My Files'. There will be a 'One Click Lag Fix' app installed. Run that, and select the option you want!
The app will automatically kill all running tasks, and enable flight mode. You should probably not use the device while the lag fix is running. If you accidentally hit back or home by mistake, re-enter the app and re-select the lag fix. It should still be running.
Known issues in 2.0.0
Some devices with heavy carrier customization cannot install EXT2 Tools. Fix should be in the next version, if possible.
On Froyo (Android 2.2) this lag fix will refuse to install if the apps2sd feature is in use. The error you will see if Apps2SD is in use on installation will be that the loopback cannot be mounted.
Workaround: In order to install the lagfix on froyo, you will need to set each app that is on the external SD back to regular. Once the lagfix is installed, you can move apps back to the SD.
Fix should be included in the next version, if possible.
If you use up more space inside the EXT2 than is available outside the EXT2, you will have to remove apps/delete data until you have enough space to copy your data back when you want to uninstall. To help avoid this, don't set the space bar all the way on the far right.
Supported Devices And Firmwares
Root support is available for:
- I9000 Galaxy S on Android 2.1
- Captivate on Android 2.1
- Vibrant on Android 2.1
Other devices / Android versions will have to use a different method to root
Lagfix support is available for:
- I9000 Galaxy S on All Firmwares
- Captivate on All Firmwares
- Vibrant on All Firmwares
- Fascinate on All Firmwares
2.0.1 - 2.0.4 Changelog
- Fixed WifiTimeout option to work on Froyo
- Fix for OCLFV1 undo.
- Sync is called before bind-mounting, to ensure no data is lost.
- Fix for APPS2SD error (loopback can't be linked error)
2.0.5 Changelog
- Fixed WifiTimeout to work on strange firmwares without a system.system
2.1.0, 2.1.1Changelog
+ Lagfix V2+ has been updated to V2.1+ which features enhanced data security
In order to install it, you must first undo V2 using the option, and then install V2.1+ as usual
- Fixed WifiTimeout to now correctly require EXT2 Tools
- Fixed Cleanup option to now correctly clean up the V2 lagfix as well as V1
- EXT2 Tools will now remount /system as read-write
- Changelog included in app for market users
2.1.2 Changelog
- Fixed 'Restore Bootlogo' option to work correctly when V2 lagfix is installed.
- Fixed 'Restore Bootlogo' option to restore the froyo bootlogo if running froyo.
2.2.3 Changelog
+ Lagfix updated to V2.2+ which contains:
- Fix for new Vibrant, and I9000 JJ1 firmware.
- Fix for the timezone issue.
~ To Install V2.2+, use the undo V2 function, and then re-do with V2.2+
+ Kernel Installer (ALPHA) that allows you to easily flash a kernel to your device
2.2.4 Changelog
- Fix for menu->help button opening kernels page.
- Minfree now shows current settings
- Set scheduler now shows current settings
- Set scheduler now has an option to apply tweaks from hardcore on XDA forums
- Text cleanup
- Fix for occasional crash on fetching kernel manifest
2.2.8 Changelog
- Galaxy Tab Support
- Fix for installing with APPS2SD active
- Fix for set-on-boot for minfree and scheduler/tweaks
2.3.0 Changelog
- Bug fixes for occasional 'Broken Pipe', as well as related failure to copy boot up scripts.
- z4root option added, which opens the market to the z4root app.
- update.zip root option now downloads update.zip instead of having it included.
- Fix for typo in cleanup option, it should now work correctly
Rooting Froyo
Froyo's recovery mode is locked down, so you can't root it from your device.
However, you can use this: http://forum.xda-developers.com/showthread.php?t=803682
Donations
Since a lot of people have been asking, I set up a paypal account and got a donate link: https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
Feel free to donate if you want, but I'm happy if you don't donate too.
Full source code under the GPL is available from http://code.google.com/p/oclf/
Nice work! Will test it soon!
Sent from my GT-I9000 using XDA App
Very nice, thanks, will try it asap
Now downloading to test. I hope it will be great work.
Damn! Just when I decided to try out the stock firmware without any lagfixes. :-| Guess I have no choice but to succumb to your awesomeness now.
Will make a backup of data on my internal memory (just in case) and give this a shot on my brand new JM8 now
Sent from my GT-I9000 using XDA App
Hang on, looks like it has a bug! I did a clean firmware flash, and its just giving a 'disabled' message, because it seems to be erroring on trying to find /dbdata/ext2data/
I'll have a 2.0.1 up within a few minutes with the fix. Sorry! I need a QA department!
Good work!
Do we need to uninstall APK v1 before using this APK?
I guess yes, but you never know.
Thanks
Is this the app version of "voodoo" fix only with ext2 (the one you started testing earlier in different topic) or its old virtual file method?
Hmm, can't find the lagfix
Thx for readding it
lol ^^
Will report back in a few minutes
RyanZA said:
Hang on, looks like it has a bug! I did a clean firmware flash, and its just giving a 'disabled' message, because it seems to be erroring on trying to find /dbdata/ext2data/
I'll have a 2.0.1 up within a few minutes with the fix. Sorry! I need a QA department!
Click to expand...
Click to collapse
2.0.1 is up in the first post. If you downloaded 2.0.0 and noticed that it didn't work, grab that one.
Steephig said:
Good work!
Do we need to uninstall APK v1 before using this APK?
I guess yes, but you never know.
Thanks
Click to expand...
Click to collapse
You don't need to uninstall APK v1 first. It will overwrite it.
V1 lagfix will need to be uninstalled first, but the uninstall can be done by either V1 or V2 APKs.
dupel said:
Is this the app version of "voodoo" fix only with ext2 (the one you started testing earlier in different topic) or its old virtual file method?
Click to expand...
Click to collapse
Virtual file method, but better.
RyanZA said:
You don't need to uninstall APK v1 first. It will overwrite it.
V1 lagfix will need to be uninstalled first, but the uninstall can be done by either V1 or V2 APKs.
Click to expand...
Click to collapse
I phrased my question a bit weird, what I meant to say was if the v1 lagfix should be uninstalled, but you gave the answer anyway.
Nifty!
Can I try it this in 2.2 JPH?
Thanks...
halabibk said:
Can I try it this in 2.2 JPH?
Thanks...
Click to expand...
Click to collapse
It was deved this evening now, completely in JPH. So yeah, JPH works. If anything else works is unknown!
Also, the wifi timeout option does not work in 2.2, only in 2.1 Android. I'll put the fix up with whatever other bugs people find in a bit.
halabibk said:
Can I try it this in 2.2 JPH?
Thanks...
Click to expand...
Click to collapse
Tried it on my sluggish JPH.
Now it's blazing fast!
Very nice RyanZA.
THX!
Now my JPH firmware seems to be as fast as JM6 with Voodoo fix
Dennis
Thanks, another Q? actually I am using CFLagFix 1.80, still can use this?
Got an error (running XXJPH):
"Could not link loopback device /dev/loop0 to /dbdata/rtssdata/ext2/linux.ex2! loseup: /dev/loop0"
Damm i chose to upgrade the app from 1.6.7 but there are no install options am i missing something ? when i open the app no options to install anything
wifi timeout defo not working on 2.2 JPH
Android version: 4.4.2
Baseband version: I317UCUCNJ1
Build number: KOT49H.I317UCUCNJ1
ROM is NE5 patched with the NJ1 OTA. Rooted, Deodex'd, and Zipaligned
Thanks and Credit to @Zen Arcade for his Auto-deodexer
Added Tethering patch, Screenshot edit, and Quad-MultiWindow
No N3, N4 or S5 stuff. No Theming. Not sure if I'll go there on this ROM.
ButtNaked I317UCUCNJ1
https://www.androidfilehost.com/?fid=95784891001615960
MD5: d969d68f31c7ddb0d4b45292ada4a7a3
Almost Naked ROM IS POSTED BELOW. It has the stuff removed from ButtNaked.
Like Books, Flipboard, Magazines, SVoice, etc. All ATT crap will be stripped out.
I'm still learning what the changes were on NJ1. The camera feels like it takes pictures faster, a little quicker to respond for the next pic.
INSTALLATION
Instructions are the same as any other Custom ROM.
If you are on stock kernel it will probably hang. It should not if you are on AGNi kernel.
Download for AGNi kernel
http://forum.xda-developers.com/devdb/project/?id=2368#downloads
PSN_AGNi_pureSTOCK-v4.2.8_N7105_4.4.x_AROMA.zip
IT IS NOT RECOMMENDED TO FLASH Version 4.3.0 YET ! So use the 4.2.8 listed above
Great information is located here. Section 7 is How To Guides and References
http://forum.xda-developers.com/showthread.php?t=1987541 Credit @Bajanman
Custom Recovery
TWRP (TeamWiinProjects)
http://techerrata.com/browse/twrp2/t0lteatt (Zip is flashable, Tar is ODIN)
PhilzRecovery
http://forum.xda-developers.com/showthread.php?t=2159652
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt/ (Latest version looks like 6.48.6. I have 6.41.6 on my phone. I will test with that) Either one should work fine.
Install instructions: Credit: ATT DN5 Team @sawdoctor and @Bajanman
You need to have Samsung 4.3 Bootloader or newer.
Make sure you have the latest TWRP/CWM recovery installed.
Next, remember to backup your apps and your efs folder. That's something that you always should do before flashing anything.
Go to TWRP/CWM recovery via pressing home + power + volume up button at the same time.
Make a Nandroid backup of your working system, if you haven't done so.
Its best to do a clean install for any new Rom (clean installation recommended includes internal storage)
In TWRP Recovery hit wipe, and slide to factory data reset system. (Internal won't be touched fyi)
In PHILZ Recovery Format Internal SDCard (in mounts and storage) and do Factory reset (I will install a new ROM option in PhilZ)
(Reminder) Remember that everything you flash you do it at your own risk so do your research before flashing anything!!
Now find the location of the Rom on your external and install it.
Flashing the Rom zip.
It should take less than 10 minutes till it boots...
AlmostNaked I317UCUCNJ1
Android version: 4.4.2
Baseband version: I317UCUCNJ1
Build number: KOT49H.I317UCUCNJ1
ROM is NE5 patched with the NJ1 OTA. Rooted, Deodex'd, and Zipaligned
Thanks and Credit to @Zen Arcade for his Auto-deodexer
Added Tethering patch, Screenshot edit, and Quad-MultiWindow
No N3, N4 or S5 stuff. No Theming. Not sure if I'll go there on this ROM.
- SuperSu updated to 2.3.6 (After boot it will prompt to update binary, choose Normal not CWM) Credit: Chainfire
- AGNi kernel added V 4.2.8
- AGNi optimal settings added (I did back the Max CPU Freq back to stock 1600MHz)
* use AGNi control app to change other setings
- TW StereoSound & InCall Fix added
- Bootanimation.zip support (find a boot animation you like, drop it in /system/media change permissions to rw-r-r)
- Gmail 5.0 (15609867) Open it and it will require Google Play services to be updated.
- Google Calendar 5.0 (1579230) (under data/app) Can be removed
- Google Drive, Hangouts and Maps will need to be updated
- Everything else is current as of 11/28/2014
-- SVoice, Samsung Calendar, Google Books, Google Newstand, Flipboard and Group Play are not system apps so you can uninstall if you like.
But then you'd be ButtNaked......
AlmostNaked I317UCUCNJ1
https://www.androidfilehost.com/?fid=95832962473394667
MD5: cd3403d69995c9c4795307bfd8a6d3d9
See Post #4 for Small Update
INSTALLATION
Instructions are the same as any other Custom ROM.
Great information is located here. Section 7 is How To Guides and References
http://forum.xda-developers.com/showthread.php?t=1987541 Credit @Bajanman
Custom Recovery
TWRP (TeamWiinProjects)
http://techerrata.com/browse/twrp2/t0lteatt (Zip is flashable, Tar is ODIN)
PhilzRecovery
http://forum.xda-developers.com/showthread.php?t=2159652
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt/ (Latest version looks like 6.48.6. I have 6.41.6 on my phone. I will test with that) Either one should work fine.
Install instructions: Credit: ATT DN5 Team @sawdoctor and @Bajanman
You need to have Samsung 4.3 Bootloader or newer.
Make sure you have the latest TWRP/CWM recovery installed.
Next, remember to backup your apps and your efs folder. That's something that you always should do before flashing anything.
Go to TWRP/CWM recovery via pressing home + power + volume up button at the same time.
Make a Nandroid backup of your working system, if you haven't done so.
Its best to do a clean install for any new Rom (clean installation recommended includes internal storage)
In TWRP Recovery hit wipe, and slide to factory data reset system. (Internal won't be touched fyi)
In PHILZ Recovery Format Internal SDCard (in mounts and storage) and do Factory reset (I will install a new ROM option in PhilZ)
(Reminder) Remember that everything you flash you do it at your own risk so do your research before flashing anything!!
Now find the location of the Rom on your external and install it.
Flashing the Rom zip.
It should take less than 10 minutes till it boots...
MODz n ADDz
[MOD]AOSP/TW StereoSound & InCall Fix Note2 (TWRP/CWM flashable.zips) by @gregsarg
LINK http://forum.xda-developers.com/showpost.php?p=57026975&postcount=1
SHIFT Kernel 3.8.1 CREDIT: @rogersb11
[KERNEL][SHIFT][SINGLE/DUAL][TW/CM]11/29/14[LINARO]
Shift Dual Boot/ TW and CM Kernel
http://forum.xda-developers.com/galaxy-note-2/development-n7105/kernel-08-15-14-t2849082
This kernel supports both TouchWiz and ALL of AOSP other than maybe Pac Rom but it is not my fault it isn't supported lol. They use their own name in the framework instead of the one EVERYBODY else does.
CPU GOVERNORS: lazy, smartass, smartassV2, ondemand, powersave, interactive, performance, userspace, pegasusq, zzmoove
I/O GOVERNORS: deadline, cfq, row, sio
default cpu governor: ondemand
default I/O governor: cfq
CIFS & NFS Network FileSystems
F2FS/EXT4
kernel uses LZMA compression
OverClock to 2160
CPU Voltage Control
GPU OC, UC and Voltage Control
Boeffla Sound 1.6.6 (Use the control app from the play store)
Charge Control
TouchWake and Timeout support
Slide2Wake
DoubleTap2Wake
Mdnie HiJack
Dynamic Fsync Control
Kernel gesture support
Latest source updates
Compiled with Linaro GCC 4.9.2
STweaks is included for kernel configuration
https://www.androidfilehost.com/?fid=95784891001616471
AGNi Kernel
http://forum.xda-developers.com/devdb/project/?id=2368#downloads
Credit - psndna88
I'm running 4.2.8
PSN_AGNi_pureSTOCK-v4.2.8_N7105_4.4.x_AROMA.zip
https://www.androidfilehost.com/?fid=95784891001615962
Credit - psndna88
AGNi_settings_backup.zip (settings to try) Unzip copy to /system/etc/init.d
https://www.androidfilehost.com/?fid=95747613655042683
Credit - terpin32
Xposed Installer Credit : Author(s): rovo89, Tungstwenty
This is the installer for the Xposed framework, which is a requirement for all modules.
Xposed is a framework for modules that can change the behavior of the system and apps without touching any APKs. That's great because it means that modules can work for different versions and even ROMs without any changes (as long as the original code was not changed too much). It's also easy to undo. As all changes are done in the memory, you just need to deactivate the module and reboot to get your original system back. There are many other advantages, but here is just one more: Multiple modules can do changes to the same part of the system or app. With modified APKs, you to decide for one. No way to combine them, unless the author builds multiple APKs with different combinations.
http://repo.xposed.info/module/de.robv.android.xposed.installer
Xposed Module Repository
http://repo.xposed.info/module-overview
511 modules
ANIMATION TRANSITION:
Too add little more speed and smoothness on the transition you can change these settings.
- Go to System Settings then tap About Device.
- Touch Build Number until it says Developers Options Enabled
- Hit Back Button
-Select Developers Options, Scroll Down to
- Window animation scale 1x (default) change to Window animation scale .5x
- Transition animation scale 1x (default) change to Transition animation scale .5x
- Animator duration scale 1x (default) change to Animator duration scale .5x
ALMOSTNAKED FIXES <----------- Download
Thanks to @DoctorQMM for catching them (CSC, Multiwindow,Google Play) !
Tethering fix added also Thanks @kebran
Thanks my friend. ..g
black screen after flash. ill try flashing bn v1 then this. using twrp 2.8.0.0
update- flashing the ne5 buttnaked v1 rom first then dirty flashing ButtNaked I317UCUCNJ1 worked. test driving now. looks great awesome work
funtimez said:
black screen after flash. ill try flashing bn v1 then this. using twrp 2.8.0.0
update- flashing the ne5 buttnaked v1 rom first then dirty flashing ButtNaked I317UCUCNJ1 worked. test driving now. looks great awesome work
Click to expand...
Click to collapse
Thanks. It was late last night and was too tired to post instructions..
But I'm running TWRP 2.7.2.2, have been all through testing this week and it's worked also.
I do full wipe. (Dalvik Cache, Cache, System, Data, Internal Storage)
Boots up everytime.
@dicksteele
Thanx for yet another contribution to the noté2 community...:good:
Excellent work Mr steel..
You definitely need to use your skill to build aosp 5.0 if you can. Awesome work to keep this forum alive.
One Man Army !!!! Thank you for all you do sir.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Mentioned last night in PM but NICE work!!!
rob_z11 said:
You definitely need to use your skill to build aosp 5.0 if you can. Awesome work to keep this forum alive.
One Man Army !!!! Thank you for all you do sir.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
What the hell. Set up environment. REPO SYNC going now.
rogersb11 said:
Mentioned last night in PM but NICE work!!!
Click to expand...
Click to collapse
Mentioned?
Sent from my SAMSUNG-SGH-I317 using Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------
dicksteele said:
What the hell. Set up environment. REPO SYNC going now.
Click to expand...
Click to collapse
Well look forward to try if you ever need anyone. Thanks again for efforts like you and Roger and others which are frequent.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I'm excited about this build...and plan to heavily abuse it...lol
dicksteele said:
Thanks. It was late last night and was too tired to post instructions..
But I'm running TWRP 2.7.2.2, have been all through testing this week and it's worked also.
I do full wipe. (Dalvik Cache, Cache, System, Data, Internal Storage)
Boots up everytime.
Click to expand...
Click to collapse
funtimez said:
black screen after flash. ill try flashing bn v1 then this. using twrp 2.8.0.0
update- flashing the ne5 buttnaked v1 rom first then dirty flashing ButtNaked I317UCUCNJ1 worked. test driving now. looks great awesome work
Click to expand...
Click to collapse
So does this mean that you have to flash the ne1 ROM (buttnaked or full) before flashing this one? Also, how has agni kernel been behaving on 4.4 lately? I shied away from using it because of all the freezes and reboots awhile back. I'm using a 4.4 ROM whose kernel is stock based right now, but the network type within the APN keeps switching LTE off on me, and it's driving me nuts. I love it, but I also love your ROMS, I used your mk6 ROM for a very long time and always keep it in my back pocket. I might give this NJ1 build a shot, since it's an ATT base. Thanks in advance. ?
chris.l.naish said:
So does this mean that you have to flash the ne1 ROM (buttnaked or full) before flashing this one? Also, how has agni kernel been behaving on 4.4 lately? I shied away from using it because of all the freezes and reboots awhile back. I'm using a 4.4 ROM whose kernel is stock based right now, but the network type within the APN keeps switching LTE off on me, and it's driving me nuts. I love it, but I also love your ROMS, I used your mk6 ROM for a very long time and always keep it in my back pocket. I might give this NJ1 build a shot, since it's an ATT base. Thanks in advance. ?
Click to expand...
Click to collapse
I used the NE5 as base and patched the NJ1 OTA. So you can just flash it all by itself. It does not have the kernel, but it does have the NJ1 modem.
DoctorQMM has been chatting with Bajanman and he suggested do not go over 4.2.8 kernel.Doc has been running it for a few days and it's doing fine on his phone. But you know, every phone acts different.
I've been running 4.2.5 since it came out. I just loaded 4.2.8 last night. It's running good. I may add it to an update, only thing I see right now is removing a couple of Knox files I missed.
I'm messing with the AOSP 5.0, should be done with the Almost Naked today or tomorrow. Thought I was done last night until I flashed it.
I lost track of my builds ober the last week and the build I'm messing with had the newer Play services and store.
It was a train wreck when I tried to get into Play sotre.. Updates worked fine and it's running now, but it's half assed if I release it like it is.
I dirty flashed this over the ne5 buttnaked v1 I had installed, and it works flawlessly. I had some crashes on the ne5, but none so far on this rom. Thanks Dev...because of you guys, I don't have a need update my Note 2. Much appreciated.
RuKuS4Life said:
I dirty flashed this over the ne5 buttnaked v1 I had installed, and it works flawlessly. I had some crashes on the ne5, but none so far on this rom. Thanks Dev...because of you guys, I don't have a need update my Note 2. Much appreciated.
Click to expand...
Click to collapse
No worries. Glad it worked.
Just out of curiosity, I did a clean install of this rom, but got the black screen as well. I had to dirty flash over the n5 butnaked rom. Not sure why this is, but thought I should mention it as well.
RuKuS4Life said:
Just out of curiosity, I did a clean install of this rom, but got the black screen as well. I had to dirty flash over the n5 butnaked rom. Not sure why this is, but thought I should mention it as well.
Click to expand...
Click to collapse
Did you install anything between the flashes? The only difference really is the NJ1 Buttnaked does not have a kernel and the NE5 does.
chris.l.naish said:
So does this mean that you have to flash the ne1 ROM (buttnaked or full) before flashing this one? Also, how has agni kernel been behaving on 4.4 lately? I shied away from using it because of all the freezes and reboots awhile back. I'm using a 4.4 ROM whose kernel is stock based right now, but the network type within the APN keeps switching LTE off on me, and it's driving me nuts. I love it, but I also love your ROMS, I used your mk6 ROM for a very long time and always keep it in my back pocket. I might give this NJ1 build a shot, since it's an ATT base. Thanks in advance. ?
Click to expand...
Click to collapse
Use my 3.8.1 kernel. Super solid and stweaks is packed. Just fixed a boot issue with TW as it's dual boot but I've been running it on my Saber rom and it's been flawless. No SOD or RR. Kernel has updated LTE modem firmware too. Gave me an extra bar at home where I consistently had been getting only one. Make sure to get build 3.8.1 from AFH and not 3.8 on xda. I haven't been able to upload to xda for 3 days
Sent from my SGH-I317 using XDA Premium 4 mobile app
**************************************************
[ROM] 6045Y-DCZ
current version 2.2 (2016-08-09)
STOCK, STABLE, FAST, ROOT
**************************************************
FOR NOW IT IS ONLY FOR SINGLE SIM DEVICES!! DUAL SIM NOT WORKING
-it is not exactly a build. Its more a mod.
-based on latest Alcatel IDO 3 5.5 6045Y MMB29M EUROPE UPDATE
-including ROOT (latest supersu 2.76)
-removed all unnecessary apps from Alcatel. there is only the necessary basic to run the phone. All other things you can download by yourself.
-Due to source is the avaliable set of languages shrinken to English, German, Slovak and Czech. But More Locale 2 app (included) will do the trick for you on most apps.
GUIDE:
-Its always better to flash this upon a stock firmware. You can try to flash it upon custm roms like CM AOKP etc, but since i havent tested it, i dont know if it will 100% work
-download firmware and also the MD5 checksum and copy both files to your phone.
-go to TWRP recovery (please make sure you use the @Unjustified Dev version from here
-make backup of your current ROM
-here you can grab a bat file to make backup of your curent MODEM, or download your MODEM in a zip file. Don´t forget to thank @famewolf for the time he spends to gather the modems.
-If you hav ebackup of oyur curent modem, just open my ROM zip in a ZIP app (i use 7zip). Replace the non-hlos.bin with your non-hlos.bin (modem) file.
-copy the ROM (and if you choose the modem zip file from @famewolf )
-wipe chache/dalvik/system/data
-format data (just to be sure. Format data is something diferent than wipe data)
-install ROM (make sure you have MD5 check enabled and it gives no error)
-reboot
-on first boot be patient it takes a while after the first boot (about 5 minutes) untill the ROM settles down
DOWNLOAD:
From my google disk
ISSUES:
-on my 6045Y i have no issues so please report
changelog in 2.2 build (2016-08-09)
-parallax background on stock launcher (looks great)
-translucent appdrawer background
-cleared updater-script of useless lines
changelog in 2.1 build (2016-08-08)
-build from latest 6045Y 010 06 update (6045Y MMB29M EUROPE UPDATE)
-no need to do some silly unmount and mount crap, because i know how to write the updater-script
-Root (systemless) included, GAPPS included (as this is just a moded stock ROM)
-Debloated 6.0.1 version..lockscreen is working well for my on 6045Y
-Background wallpaper from Vikas Kanwal (no stealing from web)
-Included 6045Y modem, so if you are on non 6045Y version see above to get your corespondent modem zip fle or image file before you start flashing.
-Security patch for 6.0.1 (from 2016-1-7)
-Double tap on lock screen to sleep
-Launcher 5x6 and dock 5x grid (instead of 4x5)
-lcd density set to 430
-USB debuging enabled from first boot
-Color temperature setting
-Technicolor enhanced colors
-Call recorder - when you are in a call you can tap on the three dots on the right and record the call
-Multi window enabled (under sttings/developer option)
-Glove mode (higher sensitivity of touchscreen)
-Three fingers swipe to make screenshot
CREDITS:
@Unjustified Dev , @famewolf , @The Marionette, without them there will be no IDOL 3 5.5 develpment, so pelase give them a thnax!
And of course i am not responsible for any damage you do by flashing this on your device!
DallasCZ said:
**************************************************
[ROM] 6045-i806-DCZ
current version 1.0
STOCK, STABLE, FAST, ROOT
**************************************************
-it is not exactly a build. Its more a mod.
-based on latest TCL i806 (IDOL3) firmware (JSU_I806-2[ABC]LCCN7_7TMBRCB3)
-I exchanged the kernel for the ARDE DEV TEAM STOCK OC one (4x1651 MHz + 4x1601 MHz).
-Antutu player will love the 37K ratings (all cores set to performance Governors)
-including ROOT (latest supersu 2.52)
-added KERNEL ADIUTOR
-removed all unnecessary apps from TCL. there is only the necessary basic to run the phone. All other things you can download by yourself. So the ROM is only 600 MB on size.
-Due to source is the avaliable set of languages shrinken to English and Chineese. But More Locale 2 app (you can download form google play) will do the trick for you on most apps.
GUIDE:
-go to TWRP recovery
-wipe chache/dalvik/system/data
-install ROM
-install GAPPS (i use open gapps 5.0 nano)
-reboot
-on first boot be patient it takes a while after the first boot (about 5 minutes) untill the ROM settles down
DOWNLOAD:
From my google disk (size aprox 600 MB)
ISSUES:
I dont know of any, you tell me.
FUTURE PLANS:
-merge another languages from framework res, settings, systemUI apks . As i am not a DEV i will repack the apks adding these languages it should work with more locale 2 then. I cannot add the language support to the rom itself.
-replace the i806 launcher with one from 6045Y (will do need more tests because of lags of the 6045Y launcher).
-add some minor build.prop tweaks
CREDITS:
BIG thnax to @franq36 of ARDE DEV Team for the Kernel, also thank @Grarak for the Kernel Adiutor.
Click to expand...
Click to collapse
Nice work! Does your version allow wifi to be enabled while in airplane mode? Are you changing the model to something unique like x806 to prevent updates from trying to be downloaded/installed that could affect partitions beyond system/boot? Did you remove the system update checker? Have you modified or eliminated the default updater-script in the stock i806 rom which clobbers several partitions beyond system and boot?
famewolf said:
Nice work! Does your version allow wifi to be enabled while in airplane mode? Are you changing the model to something unique like x806 to prevent updates from trying to be downloaded/installed that could affect partitions beyond system/boot? Did you remove the system update checker? Have you modified or eliminated the default updater-script in the stock i806 rom which clobbers several partitions beyond system and boot?
Click to expand...
Click to collapse
-yes wifi can be turned on while in airplane mode
-i deleted update checker app, so there are no updates
-yes i deleted all entries that were messing around with radio etc.. So now this script only format and copy system, busybox, root, kernel thats all. So it should be also suitable for 6045I version. I can enable the double sim stuff in build.prop so this should work also for 6045K version.
DallasCZ said:
-yes wifi can be turned on while in airplane mode
-i deleted update checker app, so there are no updates
-yes i deleted all entries that were messing around with radio etc.. So now this script only format and copy system, busybox, root, kernel thats all. So it should be also suitable for 6045I version. I can enable the double sim stuff in build.prop so this should work also for 6045K version.
Click to expand...
Click to collapse
Sounds like you have all the bases covered! What a shame we can't get multirom to work on our device YET....it would allow us to use our external sd to swap between multiple roms and I could have cm12.1, yours and whatever new one I'm testing all going at the same time. Multirom also has it's own custom build of twrp that supports the roms.
i know i have used MULTIROM on my older devices...
DallasCZ said:
i know i have used MULTIROM on my older devices...
Click to expand...
Click to collapse
You may want to look back to your source and see if they do an unmount of /persist at the end. You have left in the code which format's it and extracts the wifi drivers then symlinks them but I didn't see an unmount so it may have gotten accidentally deleted. It may be unnecessary but normally for every mount you have an unmount as it can leave partitions mounted in twrp that could cause issues if the user installs packages after the current one.
Hmm I guess I should also confirm for the 6045i users that you are using the "group 2" kernel? If not, 6045i users will need to flash the group 2 kernel right after flashing the rom before they reboot..not a big deal but if necessary a link to it in post #1 might help. Looking forward to trying this one since the i806 rom had such better performance for the idol3 than the default roms.
famewolf said:
You may want to look back to your source and see if they do an unmount of /persist at the end. You have left in the code which format's it and extracts the wifi drivers then symlinks them but I didn't see an unmount so it may have gotten accidentally deleted. It may be unnecessary but normally for every mount you have an unmount as it can leave partitions mounted in twrp that could cause issues if the user installs packages after the current one.
Click to expand...
Click to collapse
My fault i wrote twice unmount system.... hmm thats when you make such things at 2:00 AM
thanx bro.
DallasCZ said:
**************************************************
[ROM] 6045-i806-DCZ
current version 1.0
STOCK, STABLE, FAST, ROOT
**************************************************
-it is not exactly a build. Its more a mod.
-based on latest TCL i806 (IDOL3) firmware (JSU_I806-2[ABC]LCCN7_7TMBRCB3)
-I exchanged the kernel for the ARDE DEV TEAM STOCK OC one (4x1651 MHz + 4x1601 MHz).
-Antutu player will love the 37K ratings (all cores set to performance Governors)
-including ROOT (latest supersu 2.52)
-added KERNEL ADIUTOR
-removed all unnecessary apps from TCL. there is only the necessary basic to run the phone. All other things you can download by yourself. So the ROM is only 600 MB on size.
-Due to source is the avaliable set of languages shrinken to English and Chineese. But More Locale 2 app (you can download form google play) will do the trick for you on most apps.
GUIDE:
-go to TWRP recovery
-wipe chache/dalvik/system/data
-install ROM
-install GAPPS (i use open gapps 5.0 nano)
-reboot
-on first boot be patient it takes a while after the first boot (about 5 minutes) untill the ROM settles down
DOWNLOAD:
From my google disk (size aprox 600 MB)
ISSUES:
I dont know of any, you tell me.
FUTURE PLANS:
-merge another languages from framework res, settings, systemUI apks . As i am not a DEV i will repack the apks adding these languages it should work with more locale 2 then. I cannot add the language support to the rom itself.
-replace the i806 launcher with one from 6045Y (will do need more tests because of lags of the 6045Y launcher).
-add some minor build.prop tweaks
CREDITS:
BIG thnax to @franq36 of ARDE DEV Team for the Kernel, also thank @Grarak for the Kernel Adiutor.
Click to expand...
Click to collapse
I participate in the development but the creator of the kernel is @acura2201 should also include in the credits, also a link to the original kernel thread in HTCMania
thx,good job
Does this ROM support all the variants?
Sent from my 6045X using XDA Forums Pro.
The Marionette said:
Does this ROM support all the variants?
Sent from my 6045X using XDA Forums Pro.
Click to expand...
Click to collapse
As it does not rewrites original recovery neither radio files it should be good to all variants, but I have not tested (only on my 6045Y).
the second thing is the OC kernel from HTCMANIA.com if it will be working on 6045I,6045O nad 6045K variants.
If someone with dual sim (K version) would try it and has no dual sim options there have to be a slightly build.prop modification. Just change line "persist.radio.multisim.config=single" to "persist.radio.multisim.config=dsds".
someone should try...If he made a full TWRP backup, there is nothing to worry about (i think)
famewolf said:
Hmm I guess I should also confirm for the 6045i users that you are using the "group 2" kernel? If not, 6045i users will need to flash the group 2 kernel right after flashing the rom before they reboot..not a big deal but if necessary a link to it in post #1 might help. Looking forward to trying this one since the i806 rom had such better performance for the idol3 than the default roms.
Click to expand...
Click to collapse
You re right as always i mentioned it on 1st post.
DallasCZ said:
Suprisingly no. I used the group1 OC kernel and i am running on it since yesterday and no hicups,lags or reboots.
Click to expand...
Click to collapse
*removed half asleep post since you had already added link to post #1*
I'm surprised the chinese rom had higher antutu scores than cyanogenmod but I'm looking forward to having a rom that flips "upside down" properly.
Edit: Disregard what I said below, I just looked at the page again without it being translated and found the link, I think. Wow, translators really make a mess of a page. Is this the correct file/img...."Nuevoboot_Alcatel_V1.img"?
I'd like to try this but the link to HTC Mania translates horribly, it's a absolute mess. I cannot find the download link for the Group 2 OC Kernel (6045i) anywhere on that page. Can direct links be posted?
Hmm, so I have cm12.1 11/23 running, and its rebooting alot more than it was yesterday Lol. I am running the group 1 oc. Is that the right one? I think it is, so hmm. Is it worth switching back to stock?
anyone with other model than 6045Y should download the Nuevoboot_Alcatel_V1.img as I understood.
Odesláno z mého 6045Y pomocí Tapatalk
DallasCZ said:
anyone with other model than 6045Y should download the Nuevoboot_Alcatel_V1.img as I understood.
Odesláno z mého 6045Y pomoc�* Tapatalk
Click to expand...
Click to collapse
Well, I have tried that one as well, and it doesn't boot. So I guess its for stock ROM? Haha.
Disregard previous information, apparently the kernel in the thread changed somewhat since the last time I downloaded it. Testing again, boots up with the group 2, will report back.
capeorigins said:
Hmm, so I have cm12.1 11/23 running, and its rebooting alot more than it was yesterday Lol. I am running the group 1 oc. Is that the right one? I think it is, so hmm. Is it worth switching back to stock?
Click to expand...
Click to collapse
You should talk about cm in the cm thread..thats what it's for. Group 1 and group 2 is only for "stock" roms. the i806 falls under "stock rom". Roms like cyanogenmod should be running the CM kernel on that page. It's part of the name and not either of the groups.
---------- Post added at 09:39 PM ---------- Previous post was at 09:34 PM ----------
@DallasCZ
What min/max/governor are you choosing for big & little in KA?
Ok... so:
6045i
- Full Wipe
- Installed without kernel, then hit reboot
- Rebooted straight to TWRP, said OS not installed. Installed over it, rebooted.
- Booted up, went through settings, then froze when Supersu free dialog box popped up
- Installed Nuevoboot_Alcatel_V1, and open_gapps-arm64-5.0-micro-20151124
- Booted up fine, no play service issues of any kind
- Ran AnTuTu 64-bit with big/little on performance (1651 and 1113), score 33,625
Can't fathom why the 6045Y would score almost 3,500 more on AnTuTu. Made sure there was no thermal throttling by placing phone in front of air conditioner.
Edit: Seems the 6045Y can throttle the little up to 1601, whereas my 6045i maxes at 1113? I'd assume that is where the extra 3,500 in AnTuTu is coming from. Odd, in the CM OC kernel I was able to 1601 on the little..
Edit 2: Set the GPU to max clocks and performance governor, score 35,868. If little clocks would hit 1601 instead of 1113, I'm betting it would pass 37,000.
Final Thoughts: I've had zero issues with performance in any capacity, and the MOTO Camera for v2 Lollipop works great. I think we've got a winner here. Not a big fan of the news thing when you swipe to the left though, hopefully an easy way to get rid of that... and apparently its pretty easy, just press and hold on homescreen, then hit the toggle on the mini version of the news screen, gone!
xStealth said:
Ok... so:
6045i
- Full Wipe
- Installed without kernel, then hit reboot
- Rebooted straight to TWRP, said OS not installed. Installed over it, rebooted.
- Booted up, went through settings, then froze when Supersu free dialog box popped up
- Installed Nuevoboot_Alcatel_V1, and open_gapps-arm64-5.0-micro-20151124
- Booted up fine, no play service issues of any kind
- Ran AnTuTu 64-bit with big/little on performance (1651 and 1113), score 33,625
Can't fathom why the 6045Y would score almost 3,500 more on AnTuTu. Made sure there was no thermal throttling by placing phone in front of air conditioner.
Edit: Seems the 6045Y can throttle the little up to 1601, whereas my 6045i maxes at 1113? I'd assume that is where the extra 3,500 in AnTuTu is coming from. Odd, in the CM OC kernel I was able to 1601 on the little..
Edit 2: Set the GPU to max clocks and performance governor, score 35,868. If little clocks would hit 1601 instead of 1113, I'm betting it would pass 37,000.
Final Thoughts: I've had zero issues with performance in any capacity, and the MOTO Camera for v2 Lollipop works great. I think we've got a winner here. Not a big fan of the news thing when you swipe to the left though, hopefully an easy way to get rid of that... and apparently its pretty easy, just press and hold on homescreen, then hit the toggle on the mini version of the news screen, gone!
Click to expand...
Click to collapse
Most folks could choose 1601 but their phone was rarely actually at that speed...people experiencing reboots should check their cpu temp in KA...in every case I encountered a reboot checking it right after boot showed it was still quite high and more than likely the cause of the reboot. You should however be able to set it to 1300 without issues.
I wouldn't use performance or interactive as they had all 4 cores going way to much of the time allowing temps to rise.....try "wheatley".
The Unlegacy-Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
This organization's goal is not to create feature packed ROMs, but to create a base ROM in such a way that custom ROM developers can easily adapt the changes. We're good at (properly) fixing compatibility issues between newer Android versions and older devices, among other core things. The "bells and whistles" like themes we leave to others.
The first public build here had something exclusive for the Galaxy Nexus, yet unseen on any other OMAP4 device: all RAM carveouts reserved for Ducati (the multimedia subsystem of OMAP4, responsible for hardware-accelerated video decoding, encoding and camera functionality) have been switched over to CMA.
A few words for those who see CMA for the first time:
The Contiguous Memory Allocator (CMA) makes it possible for device drivers to allocate big contiguous chunks of memory after the system has booted.
The main difference from the similar frameworks is the fact that CMA allows to transparently reuse memory region reserved for the big chunk allocation as a system memory, so no memory is wasted when no big chunk is allocated. Once the alloc request is issued, the framework will migrate system pages to create a required big chunk of physically contiguous memory.
Click to expand...
Click to collapse
This means that a total of 996 MB physical memory is available to the system, while keeping Ducati fully working - this is a huge step forward, coming from the 694 MB available in the last factory image released by Google (Android 4.3). This gives the OS access to an additional 300MB of RAM.
While CMA was just recently implemented for this device, thanks to one of our developers (let's just call him Luden), it's quite stable: even under heavy memory pressure, the system manages to free up the required memory in order to start up Ducati and launch the requested multimedia functionality in a few seconds at most.
Installation
For Marshmallow (6.0) and below, It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs.
Problems
While we weren't able reproduce any CMA-related problems, hidden ones can still arise. In most cases, these problems will be either lost Ducati functionality (no multimedia capabilities) until rebooting, or a kernel panic (hard reboot) - upon noticing any of these, be sure to grab a logcat/dmesg and/or last_kmsg and send it to us (preferably by attaching it to a post in this thread).
Other than that, these are bugs we're aware of in the current build:
- The RIL on LTE devices (toro, toroplus) isn't fully working; calls and texts should be OK, but expect no data.
- Sound pops can be observed, mostly when using touch sounds (this is being investigated)
- Some exotic video formats or camera modes might not be perfect - if you notice any artifacts or green spots (the issue that happened in the past), report the details in this thread
- Inverted colors mode not working
- Tricky connection to some 5 GHz Wi-Fi networks
- SELinux is in Permissive mode (this isn't a problem for most people, just mentioned it here as extra information)
If you notice anything else, be sure to report it in this thread. While we're kind of busy, we usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org.
As usual, feedback is appreciated
Want to support development? You can consider donating, we've spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Nexus
Contributors
Ziyan, MWisBest, Android-Andi
Source Code: https://github.com/Unlegacy-Android/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Created 2016-03-12
Last Updated 2017-04-07
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Incredible work! Thank you to ALL the volunteer developers for making this FREE and OPEN SOURCE progress possible! The code is free, but your time is not! Thank you!!!
Out of curiosity, is aosp_mm_tuna_2016-03-12 running DDK1.9 or DDK1.8? I feel like it's 1.9 from your mention of recording artifacts, but I'm not an android developer, so I can't tell.
I'm running this right now, and it's awesome. Marshmallow in general seems to have much better performance than Lollipop on our device. I do miss some custom kernel flags, but I'm sure that'll come with time.
@Ziyan Which recovery do you recommend ?
DRM services not working means also Netflix doesn't work?
PythonNut said:
Out of curiosity, is aosp_mm_tuna_2016-03-12 running DDK1.9 or DDK1.8? I feel like it's 1.9 from your mention of recording artifacts, but I'm not an android developer, so I can't tell.
Click to expand...
Click to collapse
DDK 1.9 of course
Master94ga said:
@Ziyan Which recovery do you recommend ?
Click to expand...
Click to collapse
The latest TWRP should be fine. I might have not mentioned it in the OP, but the ROM supports F2FS as well.
Master94ga said:
DRM services not working means also Netflix doesn't work?
Click to expand...
Click to collapse
Possibly.
Ziyan said:
DDK 1.9 of course
The latest TWRP should be fine. I might have not mentioned it in the OP, but the ROM supports F2FS as well.
Possibly.
Click to expand...
Click to collapse
Thanks, 3.0 unofficial or your last recovery?
You are a god!
I'm downloading and will be testing this, I'm super excited about this work.
EDIT: So, first thing I've noticed is that the phone is struggling with the configuration in the first boot. Either in the "checking connection" or in the "just a sec..." loading frame, it freezes and doesn't get past it. Is it because of google play services?
diogofd8 said:
So, first thing I've noticed is that the phone is struggling with the configuration in the first boot. Either in the "checking connection" or in the "just a sec..." loading frame, it freezes and doesn't get past it. Is it because of google play services?
Click to expand...
Click to collapse
Yes Google Play Services can mess it up - I don't recall how, but I managed to press a skip button or something to easily get past it when it started looping. I guess we should add a mini how-to to the OP about it, as I really don't want to hack the framework for this.
Yep, I'm stuck in "just a sec..."
Edit: I restarted the Phone and now it works.
Netflix works too
Big thanks to @Ziyan and all OMAP4 dev for all your contribution so far ! I'll test this immediately [emoji106]
Sent from my Galaxy Nexus using Tapatalk
Ah, another thing!
When I flash the rom .zip file with all the partitions in f2fs, it auto changes to ext4 and installs. Maybe I'm being noob using TWRP so I'll say what I did here:
1) Full wipe
2) Convert system to f2fs, convert data to f2fs, convert cache to f2fs
3) Adb push rom zip file
4) Flash it
5) Check partition format, it's all on ext4
diogofd8 said:
Ah, another thing!
When I flash the rom .zip file with all the partitions in f2fs, it auto changes to ext4 and installs. Maybe I'm being noob using TWRP so I'll say what I did here:
1) Full wipe
2) Convert system to f2fs, convert data to f2fs, convert cache to f2fs
3) Adb push rom zip file
4) Flash it
5) Check partition format, it's all on ext4
Click to expand...
Click to collapse
There are a couple things going on here. The system ROM is an ext4 image, so it doesn't matter what you format it to, because it'll always become whatever is in the image.
Furthermore, only /data benefits from being F2FS, but it's not you fault for not knowing this because it wasn't mentioned in the documentation!
The other thing is that I don't know of a TWRP build that isn't buggy. When I tried to format to F2FS, it didn't work because my particular version of TWRP had a bug. So maybe your /data format failed for the same reason. I personally do not know what version of TWRP will reliably work for this. But this is a discussion for the TWRP thread.
2) Convert system to f2fs
Click to expand...
Click to collapse
Don't do this! F2FS is not supported on /system.
Wifi is extremely slow.
I can't do anything.
Google Play store can't install apps.
vipelp said:
Wifi is extremely slow.
I can't do anything.
Google Play store can't install apps.
Click to expand...
Click to collapse
Wifi works perfectly fine here ....with 2.4ghz
you using 5ghz or 2.4 ghz ?
I already tried both and it doesn't matter.
Browser times out opening google.com.
Play store doesn't load images and can't download apps
Wifi automatically disconnects....
rohitchouhan07 said:
Wifi works perfectly fine here ....with 2.4ghz
you using 5ghz or 2.4 ghz ?
Click to expand...
Click to collapse
WiFi working fine for me on 5GHz as well.
To other people: when this ROM boots, you may see the Google splash screen, then the screen will go black, and the device will act like it has died. It hasn't. Just give it a minute and the regular Android boot animation will appear.
OK i'm trying a reflash now. Complete wipe.
For me all work correctly, no problem with google play store or wifi
Glassrom is for people who know what they are doing with their devices and know how to fix issues themselves if something goes wrong. Do NOT flash glassrom if you do not know what you're doing with your device. Glassrom will not take responsibility for any mishap, any good or any bad thing that happens to your device
Kernel hardening tip: kptr_restrict is useless on glassrom release builds as an attacker can easily extract kernel pointer data from the release build's image. If you want security you have to recompile the kernel (preferably the whole ROM by yourself
Glassrom recommends that you build it yourself with dm-verity and lock your bootloader to be fully secure instead of flashing release builds. The open-source version has full support for dm-verity. The closed source version does have support but doesn't enable verity. Anykernel2 can be used to inject a kernel with dm-verity enabled
This ROM has dm-verity. Learn how to handle verity before you flash or you will end up in a bootloop
Flashing GlassROM will encrypt your device. If you don't know what that means stop at this instant. Make sure you have backups
Glassrom can take a long time to boot. So be patient and don't freak out thinking it's bricked
Glassrom is based on lineageos
Glassrom respects your rights as a user (but will still be that shady guy who won't release the source code) and has very strict data protection and privacy rules. Please read our privacy policy for more details
Get support almost instantly! Such wow, very nice https://discord.gg/UF9qnts
Safetynet:
Update: as of oreo no longer "bypasses" safetynet. Follows CTS the way a proper ROM should in order to pass safetynet checks
-------
Features: support for microg out of the box
OMS added, adapted for support with lineage's accents
Heavily optimized:
-O3 for ROM
-Ofast graphite and other optimisations for kernel
Odexed whole ROM in speed mode to reduce strain on JIT
EAS
Undervolted
Stripped down kernel configuration to a minimum
Full AOT forced at boot
Secure:
Selinux hardening, yama, several security patches to ensure that the system is secure.
Privileged permission whitelisting
Linux-hardened
Hardware-accelerated forced encryption
Dm-verity entorced
Supports dm-verity (compile it yourself for dm-verity, we can't enforce it on release builds)
Upstreamed kernel
Audio:
V4a and jamesdsp drivers + sepolicy included. Just install the app as a user app and enjoy! No installation or root required
Alsa sound control for headphones (use kernel adiutor to control)
High performance audio support
Pdesireaudio 10.1
Filesystem:
Disabled file and directory access time for /data
Quota support to prevent apps from abusing device storage and faster storage statistics
Support for sdfat
Miscellaneous:
Wireguard support
TCP fast open enabled by default for shadowsocks
The ROM installer verifies each partition after flashing to prevent bad flashes
Note: this is kind of a modular ROM
It supports substratum but doesn't ship the APK. It's the same for v4a and jamesdsp. This is intentionally done so that people who don't want these apps will never have them and the feature would just never be used
-------
Download here
From glassrom server (no logging) (ipv4 and ipv6):
ROM: https://glassrom.pw/glassrom-release.zip
Recovery: https://glassrom.pw/recovery.img
Download from CDN (see privacy and GDPR notice below) (ipv4 only):
ROM: https://cdn.glassrom.pw/glassrom-release.zip
Recovery: https://cdn.glassrom.pw/recovery.img
ROM source: https://github.com/GlassROM
Device config files: https://github.com/GlassROM-devices/android_device_oneplus_oneplus2
Toolchain: https://bitbucket.org/anupritaisno1/aarch64-linux-gnu
Kernel source: https://github.com/GlassROM-devices/android_kernel_oneplus_msm8994
Verifying builds: https://github.com/GlassROM/glassrom-verification
------
Flash instructions:
Flash the recovery first
Go to the mounts and make sure "mount system partition read-only" is ticked otherwise the ROM will bootloop after the flash
If asked to allow system modifications, do NOT swipe to allow them. Tick "never show this screen on boot again" then press "keep read-only"
Do NOT mount your vendor partition unless you know what you are doing. This is NOT supported and will lead to a bootloop on the next boot
If this is your first time flashing the recovery then prepare the fakecache by reading the how to flash incremental section and reboot recovery before starting the process
Do not format data when the fakecache is mounted! This is not supported and will break things
(If coming from another ROM, factory reset is needed)
Backup data to PC
Mount the fakecache partition with
Code:
mount /data/fakecache /cache
If you get a "failed to update system image" error please reboot recovery and try again
Flash the ROM. Strongly Recommended to enable zip file signature verification while flashing the ROM and the firmware
At this stage you have 2 choices. Either flash the gapps addon to be able to boot with dm-verity or flash a dm-verity disabler and flash your gapps. For users that don't use gapps this is not much of a concern
Reboot
Notice for TWRP flashing errors: the error codes themselves are useless. The message above the error is what truly helps diagnose the issue
Below advisory only for people coming to glassrom from another ROM. Contact support if you upgraded from a previous build and a newer build doesn't boot
Starting from the February 2019 release encryption is no longer in place and formats the data partition. Please be careful and have backups of your data
Unlike other ROMs you don't need to clean flash every new build or even wipe caches after every flash. Just flash the new build and reboot. Nothing to worry about unlike other ROMs
--------
You want to use our kernel in your project?
clone the kernel and run bash travis.sh and the kernel will be automatically built for you. We don't really care if you give us credits but if you do we'd appreciate it.
Glassrom believes that rebasing kills any kind of collaboration that could happen so we don't rebase our repositories unless it is impossible to make a change without rebasing
----------
Some notes for posting here:
Keep your appreciation for the work to other threads. Get to the point when reporting a bug so that it can be fixed faster
Bug reports should have proper logs or a way to reliably reproduce the issue
Magisk causes issues. Please do not report bugs with magisk installed
-------------
About us:
This started as a small project, now it's known as glassrom, which is funded by RX Group LLC. Glassrom doesn't make any profit from this (see below)
Privacy policy: we do not collect any personal data at all. Not even analytics. The download server is totally anonymous and doesn't log anything. We do not use adverts of any form. No registration of any sort is ever required to download the ROM. Our provider does watch out for abuse patterns like DDoS and takes action accordingly
How we profit from this: glassrom was made to provide a stable ROM at no charge. Short answer: we don't and we probably never will. RX Group LLC has given us enough to be able to build glassrom for a while and we don't see any need to annoy our users with donation reminders. No advertisements either. Everything is provided free to use and modify without any restrictions whatsoever and we never intend to profit from it
Support: we've already stated that certain mods like magisk or xposed might cause us to refuse support however anything unrelated to the issue being reported will be ignored. This is for users who use shady apps who steal other dev's work. While we don't support nor condone the usage of such apps we can't bring personal issues into our product as an organisation either and will not refuse support if we see these apps in logs. We believe in user freedom and we are not like other ROM teams who declare what users should do on their phones. If you see a maintainer refusing support for
your device due to these issues please take it directly to the notice of @anupritaisno1. We also don't use automated ban bots that ban based on a list in our support for the same reasons.
Security: glassrom always is looking at ways to increase the security of the download server and the ROM. If you find any security issues please report them to us and we'll fix them immediately
T&C: Glassrom is not liable for any damages. Everything is available free of cost and you're making these modifications yourself. We did not tell you to do these modifications and you should be aware of your actions
If you're reporting a bug and would like glassrom to discard all data (logs, screenshots and other details) after the bug is fixed please let us know about it any time. We'll gladly discard all data (note that we usually discard log data once a bug is fixed in about 2 days)
Please read lineageos' privacy policy here: https://lineageos.org/legal/ so that you know what you're agreeing to
We use bunnycdn. Read their privacy policy here: https://bunnycdn.com/privacy
https://bunnycdn.com/gdpr
Note that if you access the server with glassrom.pw you bypass bunnycdn and connect to the server directly. If you don't want to use the CDN use https://glassrom.pw which directly connects to the server
--------
How to flash incremental:
anupritaisno1 said:
Added recovery-fakecache.img
It'll be used for the upcoming incremental OTAs
A full explanation:
Incremental OTAs are computed on the /cache partition
Incremental OTAs often ask for a lot of space on /cache
Op2 doesn't have that much of space on /cache
Why incremental OTAs are computed on /cache and not on /system and /vendor (and boot) directly? Because if this were a stock ROM there is a likelihood of the user interrupting an incremental OTA so Google added a failsafe for this so that an interrupted incremental OTA can be resumed if the device was rebooted by the user. Can't be helped really
What we do? Create a fake cache partition large enough to hold these bits so that incremental OTAs can be flashed. After a lot of testing, 512 MB seems to be the optimal size for a fake cache
First we need to create the fake cache
Boot to TWRP and decrypt data
Make sure data is mounted
Run these commands in terminal by going to advanced > terminal
Code:
dd if=/dev/zero of=/data/fakecache bs=1G count=1
mke2fs /data/fakecache # type "yes" and hit enter to confirm
Note that TWRP is hardcoded to only accept /data/fakecache. Other filenames will be rejected when you flash the ROM
Reboot recovery after creating the fakecache
If you accidentally flash the ROM and forgot to mount the fakecache before flashing you have to reboot recovery, mounting it after a failed flash won't work at all
The following additional directories will be added to the server:
full (no longer available, dm-verity has been enforced on release and full now is equivalent to a release build)
incrementals
Full: for full zips, exactly the same as the release zip but won't contain backuptool so that incremental OTAs can be flashed
Incrementals: will have a filename glassrom-release-incremental-from-source-to-target.zip
Example current glassrom release is july release
The August release would be something like
glassrom-incremental-from-july-release-to-august-release.zip
The file naming for the full zips will be
glassrom-release-full-target.zip
Example August release would be glassrom-release-full-august.zip
Likewise if there is more than one build in a given month you might see something like
glassrom-incremental-from-august6-release-to-august9-release.zip in the incrementals and glassrom-release-full-august9.zip
What to do? First flash the full zip and chain the installation of each incremental zip. Note that you can't be on, say July release and upgrade to September release without flashing the August release
So if you want to go from July to September release (say), you'd probably go something like
backup-script.zip (will be provided, necessary to backup gapps and other mods before flashing the new ROM)
glassrom-release-full-july.zip
glassrom-incremental-from-july-release-to-august-release.zip
glassrom-incremental-from-august-release-to-september-release.zip
.......
gen_verify.zip (optional, see FAQ)
restore-script.zip (will be provided, necessary to restore gapps and mods that were on the old ROM)
Remember that the flash order matters and incremental OTAs can take up to 30 minutes to flash so the larger you make your flash chain the longer you'll have to wait
Myth: aren't full OTAs always better?
No, if you think so you're free to verify the hash of the system with a full OTA and an incremental one. They will match which means that the contents are exactly the same
FAQ: also do I need to change anything else?
You might want to go to TWRP > mount and tick mount system read-only if you're having problems flashing incremental OTAs.
Why do I need to flash the full zip everytime? Can't I just flash the incremental OTAs? ****** ROM allows me to do so with delta OTAs!
First off, incremental OTAs move blocks of data around instead of files and write/erase blocks instead of touching the filesystem. The incremental OTA system isn't even aware of the filesystem being used. This is because the only way to recreate the entire filesystem is to operate at a level below the filesystem. Doing something as simple as even mounting system will disturb the order of the blocks the way they appear to the incremental OTA patcher, even though the filesystem didn't change. So you need to flash the full zip and all incremental OTAs in a chain and you can't flash them directly
Wait! This is different from the Delta OTAs I've used! Stop messing around
Delta OTAs take an existing zip and create a new ROM zip out of it. Incremental OTAs patch your partitions live. Incremental OTAs are also much smaller than Delta OTAs
For comparison:
A "typical" incremental OTA: 8 mb (actual releases should be around 80-200)
It's Delta counterpart: 140 mb (actual releases would be 60-70% of the size of the new ROM)
What's the gen_verify.zip?
Used to verify if an incremental OTA chain (or a full OTA) was correctly flashed. The zip will return valid results and will only log errors and always report a success regardless of whether there is an error or not. It will show you verifying partition... Where partition can be boot, system, vendor or recovery. It will say failed for recovery, that is expected but it should show verified partition for every partition other than recovery. Has to be redownloaded for every new release. It will just verify the partitions and not write anything to any partition. The script will also always return success even if verification fails so read that the script's output actually reports that verification passes and not TWRP's output that the zip flashed successfully
Can I flash normal release zips and skip incrementals and still use this TWRP to flash?
Yes
What's the difference between this TWRP and recovery-vendor?
Nothing except the fakecache addition
Availability: sometimes lineage will make really huge changes that might make it impossible to upgrade through an incremental OTA so you shouldn't rely solely on incremental OTAs. Anything can happen. In such a case I can only say sorry and give you a full OTA
You have to store these incremental OTA files! Glassrom will delete old releases
Click to expand...
Click to collapse
anupritaisno1 said:
Oh I forgot to mention this
Source means your current system
Target means the system you're upgrading to
So your target becomes the source for the next (incremental) OTA
Click to expand...
Click to collapse
Enjoy the incremental OTAs!
Locking your bootloader:
This is dangerous. Glassrom takes absolutely zero responsibility if you try this
Flash the recovery and glassrom
Boot to fastboot and issue this command
Code:
fastboot oem lock
IMPLEMENT
Please add full oms support in this ROM.And VOLTE support too...thanks
Ooo very nice will try soon m8 but micro G support is always interesting to me on mm, now on nougat without manually patching very nice and always appreciated by me... Also safety net patches where will you stop... :victory:
Shrinath0071 said:
Please add full oms support in this ROM.And VOLTE support too...thanks
Click to expand...
Click to collapse
Look volte is not my priority
And I may accidentally break ril completely trying to implement it
I am indeed trying but I can't guarantee a successful implementation
Is is impossible to add substratum to cm
You can add it to cm-based ROMs like RR, aicp, fh but not the pure LineageOS
Dr_DjEnder said:
Ooo very nice will try soon m8 but micro G support is always interesting to me on mm, now on nougat without manually patching very nice and always appreciated by me... Also safety net patches where will you stop... :victory:
Click to expand...
Click to collapse
There are many more features but I don't know because it's been quite a while since I've been testing
I can guarantee you, no unnecessary bloat
There's a commit that allows you to set a password longer than 16 characters and also another one to set a separate encryption password and an unlock password
Can someone test it out?
Interesting.. Thank you. Will flash and report after usage
Sent from my Pixel XL using Tapatalk
anupritaisno1 said:
There are many more features but I don't know because it's been quite a while since I've been testing
I can guarantee you, no unnecessary bloat
There's a commit that allows you to set a password longer than 16 characters and also another one to set a separate encryption password and an unlock password
Can someone test it out?
Click to expand...
Click to collapse
I can confirm that separate passwords work. When you set your screen password it changes your encryption password, but you can change that separately very easily.
will flashing this rom encrypt my device?
yuva_cool said:
will flashing this rom encrypt my device?
Click to expand...
Click to collapse
Interesting little feature but no
Damn! This ROM is butter smooooth. Great work @anupritaisno1
Sent from my Pixel XL using XDA-Developers Legacy app
yuva_cool said:
Damn! This ROM is butter smooooth. Great work @anupritaisno1
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Working with xos devs, tugapower and some of my own tweaks to make it better
The next build will be even faster
anupritaisno1 said:
Working with xos devs, tugapower and some of my own tweaks to make it better
The next build will be even faster
Click to expand...
Click to collapse
One question though. Using Ok Google, assistant keeps asking me to train the voice model again and again. How to make the model stick?
Sent from my Pixel XL using XDA-Developers Legacy app
yuva_cool said:
One question though. Using Ok Google, assistant keeps asking me to train the voice model again and again. How to make the model stick?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Maybe flash a new gapps package?
anupritaisno1 said:
Maybe flash a new gapps package?
Click to expand...
Click to collapse
Which is more compatible? Or did u just mean latest?
Sent from my Pixel XL using XDA-Developers Legacy app
yuva_cool said:
Which is more compatible? Or did u just mean latest?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Opengapps super will work on my ROM
You have freedom of choice here. I have merged all the gapps patches from upstream
Pick whatever package you like and flash
anupritaisno1 said:
Opengapps super will work on my ROM
You have freedom of choice here. I have merged all the gapps patches from upstream
Pick whatever package you like and flash
Click to expand...
Click to collapse
I flashed open gapps the first time.
Also, the MSM hotplug cant be tweaked with kernel aduitor, the max cores online cannot be changed. It always reverts back to 4. That is causing fps lag and spotify stutter while locking and unlocking.
Sent from my Pixel XL using XDA-Developers Legacy app
yuva_cool said:
I flashed open gapps the first time.
Also, the MSM hotplug cant be tweaked with kernel aduitor, the max cores online cannot be changed. It always reverts back to 4. That is causing fps lag and spotify stutter while locking and unlocking.
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thats because 4 is the max value. (This max core per cluster) So if its set to, say 3, it means max 3 for little cores and max 3 for big cores.
suraj.das said:
Thats because 4 is the max value. (This max core per cluster) So if its set to, say 3, it means max 3 for little cores and max 3 for big cores.
Click to expand...
Click to collapse
No if I enable the Hotplug all the cores of Big cluster are plugged out except for one and 3 cores of little cluster work.
Please check it
Sent from my Pixel XL using XDA-Developers Legacy app
yuva_cool said:
I flashed open gapps the first time.
Also, the MSM hotplug cant be tweaked with kernel aduitor, the max cores online cannot be changed. It always reverts back to 4. That is causing fps lag and spotify stutter while locking and unlocking.
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Then disable the hotplug?
Hotplug is just to avoid some heat. It doesn't help at all when it comes to battery life
suraj.das said:
Thats because 4 is the max value. (This max core per cluster) So if its set to, say 3, it means max 3 for little cores and max 3 for big cores.
Click to expand...
Click to collapse
Oh hey welcome