Overview
This is a kang port of ParrotMOD originally for the Nexus 7 (http://forum.xda-developers.com/nex...rrotmod-speed-2012-nexus-7-emmc-fix-t3300416) used with permission, but without oversight ... so very VERY unofficial. .
Full credit to @parrotgeek1
This MOD is a collection of tweaks aiming to improve performance of onboard storage. Our Note 2 is starting to show its age especially on CM13, so I thought it'd port this MOD and see how much it helps. Aiming mainly for AOSP/CM MM ROMs (but should work on other rooted ROM). The changes/tweaks are not quite as earth shattering on our Note 2 as they are on the N7, but still quite substantial, IMHO, especially when loaded with apps.
Target Audience
Most thoroughly tested with wilson3q's unofficial build cm12.1/13 . Been using this MOD with various daily builds over the past 2-3 weeks.
Also tested that it works with RR MM , but I have not done any long term tests with this.
Source Code
Sources are here: https://github.com/miji2/ParrotMod_Multi
Legacy sources: https://github.com/miji2/ParrotMod_N7105-legacy
Hack away
Downloads:
See attachments for this post (for now).
WARNINGS
:::: Backup backup Backup ::: ***
Always keep in mind:
* It is impossible for me to test every permutation of hacks you have installed.
* This mod is meant for “pure” ROMs (ie NO: IO scheduler/RAM/read ahead tweaks, L
* Speed/any other "supercharger" like tweaks, disable journaling, limit background processes)
* It’s replacing the guts of the system (libc + libart) so:
* It may be more unstable than your default ROM
* It may be more insecure than your default ROM
* it may break things
Instructions:
:::: Backup backup Backup ::: ***
a) read original post here--> http://forum.xda-developers.com/nex...arrotmod-speed-2012-nexus-7-emmc-fix-t3300416
b) flash MM ROM (CM13, RR, etc) for N7105
c) flash gapps if you want
d) flash SU
e) finally flash this MOD
Updates:
* May 31: initial post
* June 8: Update released codename "Mellon"
- syc sources with upstream to bring in all general changes, fixes, updates to our device;
- github project renamed; source branched differently to allow supporting a variety of devices though overlays
- initial bringup for N7105 (this device) on the new codebase as well as HP Touchpad and Asus Transformer.
- N7105 flashable ZIP posted as attachment. To upgrade on CM13 please wipe system, flash ROM+gapps+SU+ParrotMod . Tested on Jun 3, 6, and 8th builds. Oh yeah, *BACKUP* first.
Looks interesting. Wait for someone to test it.
Phone booted took awhile though, also Nova launcher keeps stopping
The thing about libc/libart being insecure is wrong, they have the latest security updates (March, but nothing changed since then). Otherwise it looks good. The only thing it will break is xposed
this is totally next level.
How's the battery life after this mod install?
Sent from my GT-N7105 using XDA-Developers mobile app
techx said:
How's the battery life after this mod install?
Click to expand...
Click to collapse
Can't really tell a diff since my Note2 is having RIL issues on new Cm13 builds causing it to burn through the battery pretty quickly by working hard on keeping connectivity. But I can't say I noticed any changes (for worse or better) when it comes to battery life on this MOD. Apps load faster and GUI is more responsive, tho
That is true, CM13 makes my phone also burn through the battery when it comes to reception.
Although in my case it could be due to the fact that I am running a T889v with a T-Mobile radio with the n7105 fix too.
However, just as proof that it is a reception issue, I can go into Amplify (the xposed app in case some of you may not know) and check RILJ.
9/10 the wakelock has gone insane in comparison to my whole phone. Sure I can Amplify it and all of the sudden I will have magical battery life. But, the phone tends to miss calls, specially when sleeping or have longer connection times. So generally it is not worth it to amplify it.
---------- Post added at 02:30 PM ---------- Previous post was at 02:16 PM ----------
Okay so this MOD sounds interesting but I have a few question.
To anyone, have you seen noticiable increases in performance, outside post-flash placebo effects? Since the OP has stated the changes are not a major as the original N7 MOD.
Does this break Xposed even if using the systemless ZIP?
Are some of the known bugs (slow charging) which could occur on the original MOD likely to happen here too?
agovinoveritas said:
Okay so this MOD sounds interesting but I have a few question.
To anyone, have you seen noticiable increases in performance, outside post-flash placebo effects? Since the OP has stated the changes are not a major as the original N7 MOD.
Does this break Xposed even if using the systemless ZIP?
Are some of the known bugs (slow charging) which could occur on the original MOD likely to happen here too?
Click to expand...
Click to collapse
Calling it placebo effect is unfair because this MOD has proven itself on the N7 without a shred of doubt. It does not affect charging as far as I can tell, or battery life, and I haven't tried Xposed on the Note2 but the original author specifically calls out potential conflicts with Xposed so I'm not going there. Cheers!
miji2 said:
Calling it placebo effect is unfair because this MOD has proven itself on the N7 without a shred of doubt. It does not affect charging as far as I can tell, or battery life, and I haven't tried Xposed on the Note2 but the original author specifically calls out potential conflicts with Xposed so I'm not going there. Cheers!
Click to expand...
Click to collapse
Funny how you attached yourself to the word "placebo," while ignoring the fact that I stated that the OP has made a point of saying that the MOD is not as dramatic as the N7 thus we do not know what exactly is different. Also, you did not answer any of the other questions unless "I do not know" is an answer.
Also, so you know, systemless xposed is different than regular xposed. Hence me asking the question.
agovinoveritas said:
Funny how you attached yourself to the word "placebo,"
Click to expand...
Click to collapse
Fine, I admit it, it is true that I am quite attached to the word "placebo". Not as quite as much as to the word "mellon", but still quite attached.
Even if that bothers you, allow me to connect the dots for ya.
agovinoveritas said:
To anyone, have you seen noticiable increases in performance, outside post-flash placebo effects? Since the OP has stated the changes are not a major as the original N7 MOD.
Click to expand...
Click to collapse
miji2 said:
Calling it placebo effect is unfair because this MOD has proven itself on the N7 without a shred of doubt.
Click to expand...
Click to collapse
Long answer: We know it is not placebo. The MOD addresses a bottleneck, namely slow eMMC on MM. The Note 2 is showing some slow eMMC effects, but it's not a bottleneck so addressing it does not have equally as dramatic effects. We know exactly what this MOD does. Source is available for you to study and improve.
agovinoveritas said:
Does this break Xposed even if using the systemless ZIP?
Click to expand...
Click to collapse
miji2 said:
I haven't tried Xposed on the Note2 but the original author specifically calls out potential conflicts with Xposed so I'm not going there
Click to expand...
Click to collapse
Long answer: The original author asks to not use Xposed. So don't. Since you obviously know much more about this than me, please ignore and let us know how it goes. If you do that you'll contribute to our collective knowledge and you'll be even more awesome.
agovinoveritas said:
Are some of the known bugs (slow charging) which could occur on the original MOD likely to happen here too?
Click to expand...
Click to collapse
miji2 said:
It does not affect charging as far as I can tell, or battery life
Click to expand...
Click to collapse
Long answer: No.
And if there are other questions which were not addressed explicitly, please assume that I either cannot read or that my implicit answer is "I don't know" . Thank you for clarification and for making me aware of my attachments. Cheers!
no mention of functionality on sammy roms?
R0B3RTF1SH3R said:
no mention of functionality on sammy roms?
Click to expand...
Click to collapse
No, sorry, I have not run Samsung ROMs for a while so can't even try.
Also, Note 2 did fairly well with regard to IO issues until Marshmallow .. and I don't think we have any (backported?) Android 6 Samsung ROMs for our legacy devices, right?
Appears to work with systemless xposed on blisspop without issues but haven't noticed any difference after flashing it.
So so far it seems like there is one vote for GUI/apps loading faster, and one vote for no difference -- I'm not sure I'm gonna install if nothing's happening.
Related
Here's a bit of info you may want on this project for how we do things differently:
CLICK HERE to find out more about the new team working on this project since our TeamEOS merger.
No features you don't need which slow the device down, or put your data at risk of being stolen. If you want to give it away, it should be your decision.
A fast and clean install with no UX decisions made for you. You make the ROM whatever you would like.
A team constantly exploring totally new feature sets and optimizations geared toward you, the user
We utilize a plethora of optimizations in a build system unlike any other:
Each build has a toolchain built for your device at the time of build. No more generic toolchain android builds.
Consistently updated upstream toolchain module source with our custom backports, fixes, and optimizations applied in a patch at build time.
Fully built utilizing Link Time Optimization (another custom ROM first). Feel free to google this one a bit to get an idea of the performance gain.
Many repositories have code fixes, cleanups, and many minor optimizations which are too generous to even speak of here.
Optimizations are toggled on and off based on device for the best experience we can acheive for your device without sacrificing any stability
Many Qcom optimizations and AOSP master (upstream) optimizations and fixes using device specifications to determine usage.
Fully built utilizing strict aliasing and isognu++11 mode.
Full "-O3" build. To those who don't know, this is the highest "optimization level" available in gcc that sets many other flags.
Important Links:
Download Nightlies - We have a very in depth review system, so these should be considered stable.
Download Weeklies - These are built once a week on Monday.
Download GApps
Download SuperSU installer
Kernel Source
Interactive and Rolling Changelog
Bug Tracker
Instructions:
In the same recovery session, flash the following:
Flash rom
Flash GApps
Flash Superuser zip
Reboot
Thank you for choosing codefireXperiment,
Yippee! First AOSP build with fully functional IR Blaster! I use the HTC implementation so any IR control app must use the HTC IR api. I tested with this app.
http://forum.xda-developers.com/showthread.php?t=2271113
Blaster mode and Learn mode are fully functional and stable. This is the first non-Nexus device I've done AOSP on so bear with me for a bit. The build is rock solid stable and I dare any build to try and out-benchmark me ;D
one more for good measure
This is truly a wonderful suprise!!
This is truly a wonderful suprise!!
Welcome bigrush!
This sounds cool! Thanks for the hard work. Im gonna give this a shot tomorrow.
gunna take this for a spin. sounds pretty solid.
or so i thought.
AAAARG...
keeps spittin out "Warning: no file_contextsassert failed.....Followed by various prop errors about the phones model"
anyone got any idea whats goin on?
Are the APN for ATT in this ROM or do I have to put them in myself
Sent from my HTC One using Tapatalk 2
Does cfx have the same janky animation and sluggishness of other AOSP roms for the One when compared against a Sense or GE ROM?
If anyone could fix aosp/optimize for device specific hw on non-nexus devices its you.
Sieze said:
gunna take this for a spin. sounds pretty solid.
or so i thought.
AAAARG...
keeps spittin out "Warning: no file_contextsassert failed.....Followed by various prop errors about the phones model"
anyone got any idea whats goin on?
Click to expand...
Click to collapse
I'm getting this same error too. Anybody know what's up yet? Probably something simple lol
Are you guys flashing with cw or twrp? Don't worry about the file context warning. I may have to disable device assert in installer script.
bigrushdog said:
Are you guys flashing with cw or twrp? Don't worry about the file context warning. I may have to disable device assert in installer script.
Click to expand...
Click to collapse
im using CW touch 6.0.3.3
running a backup atm but once finished il flash TWRP and see if it works.
Ok. So it fails to flash on cw then?
bigrushdog said:
Ok. So it fails to flash on cw then?
Click to expand...
Click to collapse
yup. it flashed with out a hitch on TWRP...
Sieze said:
yup. it flashed with out a hitch on TWRP...
Click to expand...
Click to collapse
Ya we compile the project with twrp recovery. I'll confer with my associates about tweaking or killing device assert in release tools. Also, I gotta drop a global device build too. First aosp build with IR Blaster and this board gets hardly any traffic! I personally run the build on my m7tmo so any derp gets my attention. There's little minor issues here and there but nothing major. Bluetooth OBEX is derped project wide but should be fixed soon.
bigrushdog said:
Ya we compile the project with twrp recovery. I'll confer with my associates about tweaking or killing device assert in release tools. Also, I gotta drop a global device build too. First aosp build with IR Blaster and this board gets hardly any traffic! I personally run the build on my m7tmo so any derp gets my attention. There's little minor issues here and there but nothing major. Bluetooth OBEX is derped project wide but should be fixed soon.
Click to expand...
Click to collapse
well initial response to laying my finger and moving it on the screen. amazing. i didnt think id feel or tell much a difference in response. but holy S#!7 so smooth and stuff happens when its supposed to aka as soon as i touch the icon its open...
(ノ^_^)ノ also the boot animation is pretty frickin sweet.
also the benchmark has me drooling.
Quadrant Standard: 6749
also im really frickin liking this ROM
Hahaha don't lie! The boot anim sucks ass man! Ya all this ui jitter talk I hear, I'm just not getting all that with our build. If the build sucked I wouldn't run it. And I sure as hell wouldn't publish it. Thanks for the kind words. More win in the pipeline.
bigrushdog said:
Hahaha don't lie! The boot anim sucks ass man! Ya all this ui jitter talk I hear, I'm just not getting all that with our build. If the build sucked I wouldn't run it. And I sure as hell wouldn't publish it. Thanks for the kind words. More win in the pipeline.
Click to expand...
Click to collapse
well hey credits due where its earned right? but yea im still crappin my pants at how there is absolutely no lag at my finger tip.
Hands down the best android experience ive ever had. i can trully feel the power of my device in my hand in all its glory.
Grab that IR app and program your TV man. Dude dropped source for the app so maybe I'll do some IR toggles or something
Sieze said:
yup. it flashed with out a hitch on TWRP...
Click to expand...
Click to collapse
I will also try with twrp tomorrow morning. I personally don't prefer one over the other so if twrp is what works then twrp it is!
mikexmayhem said:
I will also try with twrp tomorrow morning. I personally don't prefer one over the other so if twrp is what works then twrp it is!
Click to expand...
Click to collapse
Flashed with twrp. Still gave error but said successful. After reboot everything looks just fine. Great ROM!
[KERNEL] Starship-Kernel The Next Generation Stock/AOSP & CM-13 04/25/16 (Linaro 4.9)
Welcome to Starship Kernel The Next Generation (TNG) for the Nexus 6 Shamu. Not much else to say other than more than ever the Kernel is by design light wait, power efficient and moves at Warp Speed. There are no special features to play around with but instead designed to just be installed and just work. If looking for things to play around with may as well just move on as this is probably not the kernel for you.
Have shed some light on a few names below but really need to thank all the Nexus 6 Kernel Developers as could not have done much of anything without them. Before this project I had limited Kernel knowledge. Have been developing since I guess my first Rom had been CM6 based but never had much Kernel dealings. Have always worked joining up with a team to get CM or other AOSP like Roms up and running on TouchWiz,. Sense and other devices far from the Stock Android Experience. In working in groups and teams have for the most part always been the Device File & Vendor Blob guy. Everything I have learned about Kernels has honestly come from sifting through other Kernels and researching the hell out of out of commits until being able to stand on my own 2 feet and think so far have done a dam good job putting together a hell of a Kernel for the Nexus 6 that is extremely stable and performs well beyond expectation besides the big ol Jinx I just through out there.
This is now the new and improved Next Generation moving from say warp 6 to warp 9. Would say 10 but some funky stuff goes down at ten and if you dont know lets just say its not a place you wana go.
Definitely need to throw up thanks to Flair2, Imoseyon and Neoboddy89 as have used a decent amount of their commits in particular..
Features Worth Noting
Have placed features into either groups or single commits that make rather large improvements but are welcome to sift through the Kernels Commit History below as there are many individual changes to numerous to mention in a single post or even page . As mentioned most come from just sifting over and reading commits from every Kernel I could find. Most from Shamu but also some carefully selected from other devices with similar hardware
Kernel Version 3.10.101
Fast USB Charging
LZ4 Compression
Sio & Bfq i/o Schedulers - "bfq" used as default scheduler
ExFAT Support
Power Efficient Workqueues
KGSL Optimixations
Audio Codec Optimizations
Video Firmware Optimizations
CPU Idle Optimizations
GPU Power saving Optimizations
Adreno_Idler
Color Temperature Interface Using PCC
Frandom Support
LED Support (Rom must also Support)
MSM Vidc: Optimizations
Net: Wireless Bcmdhd, Various Optimizations
PM Enhancements.
F2FS 3.10
Starship Kernel, Nough Said!!
Source / Commit History aka change log
https://github.com/Chairshot215/starship_kernel_moto_shamu/commits/mm-mr1?page=1
Download Starship-Kernel_Class_SMTNG7_(Linaro-4.9) (04.16.2016)
Marshmallow 6.0.1 Stock/AOSP
https://www.androidfilehost.com/?fid=24499762636007231
CM-13.0
https://www.androidfilehost.com/?fid=24499762636007230
Again I am not responsible for any negative effects using any of the files on this thread or any post that has been linked in this thread so using is all at your own risk.
seems like nexus 6 development just blew up with new ROMs and kernels, thank you pal
Sent from my Nexus 6 using Tapatalk
Yup!
Does this kernel bypass force encryption?
Team Octos -Nexus 6
force encryption is disabled in the r_2 boot.img but so far is still showing that my N6 is Encrypted. With that said have not performed the recommended factory reset when going from a force encrypted boot.img to one that is not.
System UI Crash
Perhaps I've misinterpreted the OP, but I seem to have a major issue. Assuming this kernel is meant for 5.1.1 AOSP builds, upon flashing the kernel and wiping caches I get System UI crashes that do not allow me to actually start Android... am I at fault here?
That is odd I have flashed on AOSP many a time and have not had any issue. This is pure AOSP I compile without any modifications though. Is it a Rom on the forum, can maybe take a look see what might be the issue.
chairshot215 said:
That is odd I have flashed on AOSP many a time and have not had any issue. This is pure AOSP I compile without any modifications though. Is it a Rom on the forum, can maybe take a look see what might be the issue.
Click to expand...
Click to collapse
An issue like this is usually directed at the ramdisk. You may want to look into moving to an any kernel installer instead.
Sent from my Nexus 6 using Tapatalk
I was unencrypted, flashed the kernel and it booted up and told me encryption failed so I had to wipe and start over and decrypt again. If its disabled why did it encrypt again?
Sent from my Nexus 6 using Tapatalk
I like Starship ROM since my Nexus 5. :laugh::laugh::laugh:
ps000000 said:
I like Starship ROM since my Nexus 5. :laugh::laugh::laugh:
Click to expand...
Click to collapse
I hope you are referring to the Kit-Kat version and not the test flight Lollipop Rom I had up for a few days, lol.
Had pretty much put most of a year counting the L-Previews into that thing but was honestly not happy and did not think it measured up to what I had been releasing under Starship since Froyo so took it down and decided it was time for some off time. May pick it up again with M, Lollipop version had a few nice things could probably use. Think I had just about changed every hex color throughout the entire source. Took me for a loop when Google started using the Teal coloring I was using for a few versions.
calaeb08 said:
I was unencrypted, flashed the kernel and it booted up and told me encryption failed so I had to wipe and start over and decrypt again. If its disabled why did it encrypt again?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sorry had a hectic week, maybe you can save me some time. Honestly was trying to stay away from forums for a bit once got my N6. Was not till deciding to post something I looked around. Don't know how long I had only unlocked the bootloader so could fastboot the Kernel. Wanted over weekend to fix this and above mentioned any kernel so is more versatile than stock and pure AOSP. If could save me time and tell me what had done wrong would be a helpful thing. Am all about helpful and not so much smartest in the room syndrome so anyway committed the "fstab" had used if you see the issue at a glance. Otherwise think tomorrow is going to be a couch bound day so will read more into it.
https://github.com/Starship-Android...mmit/5f101827c8a0317d489134de756aacc534215d48
chairshot215 said:
I hope you are referring to the Kit-Kat version and not the test flight Lollipop Rom I had up for a few days, lol.
Had pretty much put most of a year counting the L-Previews into that thing but was honestly not happy and did not think it measured up to what I had been releasing under Starship since Froyo so took it down and decided it was time for some off time. May pick it up again with M, Lollipop version had a few nice things could probably use. Think I had just about changed every hex color throughout the entire source. Through me for a loop when Google started using the Teal coloring I was using for a few versions.
Sorry had a hectic week, maybe you can save me some time. Honestly was trying to stay away from forums for a bit once got my N6. Was not till deciding to post something I looked around. Don't know how long I had only unlocked the bootloader so could fastboot the Kernel. Wanted over weekend to fix this and above mentioned any kernel so is more versatile than stock and pure AOSP. If could save me time and tell me what had done wrong would be a helpful thing. Am all about helpful and not so much smartest in the room syndrome so anyway committed the "fstab" had used if you see the issue at a glance. Otherwise think tomorrow is going to be a couch bound day so will read more into it.
https://github.com/Starship-Android...mmit/5f101827c8a0317d489134de756aacc534215d48
Click to expand...
Click to collapse
I myself know nothing about developing roms or kernels, that's why I'm here to ride on the bus with the smart kids lol. I do know that you can just leave it the way it is, but you gotta let people know it's forced encryption so they don't have to start all over. They can flash that zip that disables it before booting up.
What's the point of a sig anyways?
Well Definitely it for Lollipop, Probably. One thing that bothered me moving from the N5 to N6 is my BT Headset sounded like a warped and scratched record. I had lucked out with that pair in that had been reasonable priced and sounded amazing previously. Have added a few choice commits, well almost 2 pages but the things work like a charm. Decided for that and a few other reasons for one last post until 6.0.
I remember you from the galaxy victory forums :3 thanks for trying with CM. We were SOL, but theres still development going on there!
Sent from my Nexus 6 using Tapatalk
NolenUmar said:
I remember you from the galaxy victory forums :3 thanks for trying with CM. We were SOL, but theres still development going on there!
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah I actually am still receiving emails about the Victory. Not that I could ever return to either the screen size or Touchwiz but wish I still had the device. Still feel like that SOB defeated me. Had been I think the 3rd device I worked on developing from the CM source and was so dead set on doing everything crazy proper so it could be an officially supported device. Wish I still had the device as do not like the feeling of spending countless hours on something and then leave unfinished. Think in the end all but GPS, Camera and that dang reboot when switching from Wifi to LTE. Think I used the Apexq as a template for getting everything else going. Otherwise wish the community luck. The phone was nice for the Price just a shame it has been years and everyone is still stuck on Stock with last I checked a bunch of out dated Kernels. Anyhow thats my Victory, rather defeated Rant. Remember at one point had got so frustrated used some command I don't remember off the top of my head and a lib decompiler and made the below list of all the files and their dependencies when trying to put together a vendor blob list.
http://pastebin.com/SFyJ14kv
Whats crazy about just pulling up this list is that I see the creation date was todays date but in 2013. Just had to mention that SOB device. Now I’m all worked up, lol.
Updated the M Kernel to r1.2 as works fine with SuperSU 5.1
This is an Encrypted Kernel. Will probably change with next update but for now it is Encrypted.
Now 2.0 with a few optimizations. Forgot about encryption but again looking for next update,lol.
Eill give it a try when it doesnt force enycrption
Sent from my Nexus 6 using Tapatalk
calaeb08 said:
Eill give it a try when it doesnt force enycrption
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah will need to look at that again. I use the same any-kernel installer for Lollipop-r_3.0-Kernel and M-6.0-r_2.0-Kernel.
With the L Kernel either flashing with an already un-encrypted Rom or flashing and performing a data wipe / factory reset with an encrypted Rom all works fine without encryption being forced.
Could be I just messed up the test with the M-6.0-r_2.0-Kernel and it actually does not enforce encryption as it uses the same fstab.shamu as the L version . Just did not feel like going through a data wipe to double check so am putting it off until the next release. Otherwise if you are not encrypted and remove the fstab.shamu file from the Ramdisk folder in the M-6.0-r_2.0-Kernel zip before flashing the Rom should still stay un-encrypted. I have at least not seen or read anything stating there is a difference between L&M when it comes to encryption.
Otherwise this is the anykernel installer used in both L&M. The only difference is the zImage-dtb I use.
https://github.com/Starship-Android/anykernel
chairshot215 said:
Yeah will need to look at that again. I use the same any-kernel installer for Lollipop-r_3.0-Kernel and M-6.0-r_2.0-Kernel.
With the L Kernel either flashing with an already un-encrypted Rom or flashing and performing a data wipe / factory reset with an encrypted Rom all works fine without encryption being forced.
Could be I just messed up the test with the M-6.0-r_2.0-Kernel and it actually does not enforce encryption as it uses the same fstab.shamu as the L version . Just did not feel like going through a data wipe to double check so am putting it off until the next release. Otherwise if you are not encrypted and remove the fstab.shamu file from the Ramdisk folder in the M-6.0-r_2.0-Kernel zip before flashing the Rom should still stay un-encrypted. I have at least not seen or read anything stating there is a difference between L&M when it comes to encryption.
Otherwise this is the anykernel installer used in both L&M. The only difference is the zImage-dtb I use.
https://github.com/Starship-Android/anykernel
Click to expand...
Click to collapse
You'd probably be better off using hellsgods anykernel scripts. Though, I'm not sure why yours isn't working to disable it. Theres also a fed patcher that should fix it. It kinda defeats the purpose of anykernel if your replacing files in the ramdisk instead of editing them.
Sent from my Nexus 6 using Tapatalk
Hello all, I am looking for a way to enable all cores on the Honor 5x. If you use Kernel Adiutor (and I'm sure you do) you'll notice that 99% of the time (save for a reboot) your little cluster is offline when using any AOSP ROM, now the only way I've found to enable them is to edit the value in the active file located in /sys/module/cluster_plug directory. The issue with this method is that it just enables them, 95% of the workload is still handled by the big cluster, even when it's straining itself the little cluster fails to pick up any of the workload. I have done clean installs of the Blaze kernel and the issue is still not resolved. Any incite into this issue will be greatly appreciated. Thanks.
You'll need to mess with:
/sys/devices/system/cpu/cpu0/core_ctl/min_cpus
/sys/devices/system/cpu/cpu0/core_ctl/max_cpus
/sys/devices/system/cpu/cpu4/core_ctl/min_cpus
/sys/devices/system/cpu/cpu4/core_ctl/max_cpus
It takes integer value ranging from 0-4. 0-4 meaning how many cores you want online per cluster.
The only issue is that I don't have /core_ctl directory that you've specified, I don't recall ever having it on this ROM, though I could be wrong. I'm using the krexus ROM in case I hadn't specified before.
I know, reading the stock ROM forums I got very excited to see the before mentioned information that was posted only to see that said (/core_ctl) directory was missing from any AOSP ROM I had used. This is the one thing that is holding me up from giving up my Windows phone as my business phone (the lag as a result of only being able to use 4 cores is intolerable in my line of work) even giving a link to what all these directory files mean would be very helpful. Thanks.
You could google what those directory means and that would give you that answer.
I have done this (and I consider myself well versed in the ways of the interwebs and I rarely come up with anything useful but I've been working on a solution for my original question and feel I am close to achieving it. I will post once I do.....though if anyone has ANY suggestions at all I'm open to try, all of my discoveries have been made through trial and error.
tboned82 said:
I have done this (and I consider myself well versed in the ways of the interwebs and I rarely come up with anything useful but I've been working on a solution for my original question and feel I am close to achieving it. I will post once I do.....though if anyone has ANY suggestions at all I'm open to try, all of my discoveries have been made through trial and error.
Click to expand...
Click to collapse
You may be needing a custom kernel to achieve this successfully.
Sent from my honor 5X using XDA Labs
adriansticoid said:
You may be needing a custom kernel to achieve this successfully
Click to expand...
Click to collapse
I can't recall if I mentioned it or not but I'm using the blaze kernel at the moment (as far as I know it's the only custom one available for this phone?) Also the CPU control I desire is available inside the stock KIWI ROM, just wish I knew of a way to "port" that hotplug to a AOSP ROM.... thinking SELinux policy is prohibiting me from achieving the CPU control I'm after, but not sure if it's the only thing at play when it comes to this issue.
tboned82 said:
I can't recall if I mentioned it or not but I'm using the blaze kernel at the moment (as far as I know it's the only custom one available for this phone?) Also the CPU control I desire is available inside the stock KIWI ROM, just wish I knew of a way to "port" that hotplug to a AOSP ROM.... thinking SELinux policy is prohibiting me from doing this, but not sure if it's the only thing at play when it comes to this issue.
Click to expand...
Click to collapse
Have you joined the beta channel of Blaze in Telegram?
adriansticoid said:
Have you joined the beta channel of Blaze in Telegram?
Click to expand...
Click to collapse
I have not, but would be very interested, what is Telegram?
tboned82 said:
I have not, but would be very interested, what is Telegram?
Click to expand...
Click to collapse
It's a messaging app. Just like Whatsapp, but with some diferences. You can check it in the Play Store. Telegram group link is in the Blaze kernel thread.
Wow thank you, I dirty flashed it (since version 2 dirty flashed fine) and didn't have pleasing results, going to do a clean flash AOSP, but those hotplug features are exactly what our phones need! Who's ready to hunt down some flagships?
tboned82 said:
Wow thank you, I dirty flashed it (since version 2 dirty flashed fine) and didn't have pleasing results, going to do a clean flash AOSP, but those hotplug features are exactly what our phones need! Who's ready to hunt down some flagships?
Click to expand...
Click to collapse
You didn't have screens of death?
Sent from my honor 5X using XDA Labs
tboned82 said:
didn't have pleasing results
Click to expand...
Click to collapse
Don't bother with blaze kernel. It's heavily flawed. As soon as you turn on hotplugging phone will crash and you have to reboot. Unfortunately development seems to be halted.
alpinista82 said:
Don't bother with blaze kernel. It's heavily flawed. As soon as you turn on hotplugging phone will crash and you have to reboot. Unfortunately development seems to be halted.
Click to expand...
Click to collapse
Yeah the developer have not seen action the past few weeks.
adriansticoid said:
You didn't have screens of death?
Click to expand...
Click to collapse
I apologize for my absence, I really hate being that "guy" but all my free time has been devoted to tracking down a nasty electrical gremlin in my sister in laws car, but no I have never had any adverse effects from dirty flashing anything really
alpinista82 said:
Don't bother with blaze kernel. It's heavily flawed. As soon as you turn on hotplugging phone will crash and you have to reboot. Unfortunately development seems to be halted.
Click to expand...
Click to collapse
I currently have blaze kernel installed and using the method I've mentioned before am able to enable all cores, but with very poor load balancing, and the beta version is far from RTM at the moment so guess I'm stuck with version 2 for the time being.
adriansticoid said:
Yeah the developer have not seen action the past few weeks.
Click to expand...
Click to collapse
I have noticed this as well, which is unfortunate because the dev seems like a very talented coder who is quite capable of the task at hand, sometimes life gets in the way of the things we would like to do so I'm just going to be patient and hope he picks back up on the project.
tboned82 said:
I apologize for my absence, I really hate being that "guy" but all my free time has been devoted to tracking down a nasty electrical gremlin in my sister in laws car, but no I have never had any adverse effects from dirty flashing anything really
I currently have blaze kernel installed and using the method I've mentioned before am able to enable all cores, but with very poor load balancing, and the beta version is far from RTM at the moment so guess I'm stuck with version 2 for the time being.
I have noticed this as well, which is unfortunate because the dev seems like a very talented coder who is quite capable of the task at hand, sometimes life gets in the way of the things we would like to do so I'm just going to be patient and hope he picks back up on the project.
Click to expand...
Click to collapse
It's been that story for many developers man. A great project paused because life hit hard again. I believe he'll come back to it soon.
tboned82 said:
Hello all, I am looking for a way to enable all cores on the Honor 5x. If you use Kernel Adiutor (and I'm sure you do) you'll notice that 99% of the time (save for a reboot) your little cluster is offline when using any AOSP ROM, now the only way I've found to enable them is to edit the value in the active file located in /sys/module/cluster_plug directory. The issue with this method is that it just enables them, 95% of the workload is still handled by the big cluster, even when it's straining itself the little cluster fails to pick up any of the workload. I have done clean installs of the Blaze kernel and the issue is still not resolved. Any incite into this issue will be greatly appreciated. Thanks.
Click to expand...
Click to collapse
flash official cm 12.1 built. lol no deep sleep and all cores online...go for it.
methuselah said:
flash official cm 12.1 built. lol no deep sleep and all cores online...go for it.
Click to expand...
Click to collapse
Drains battery like hell. Lol.
Sent from my Galaxy Tab 3 using XDA Labs
methuselah said:
flash official cm 12.1 built. lol no deep sleep and all cores online...go for it.
Click to expand...
Click to collapse
I had thought of doing this, though I don't see any cm 12.1 links in the Honor 5x thread, just 13, (though I'm at work at the moment and have to be stealthy about my research...errgghh Damn kids and their Snapchat) and I have to admit I've kind of fallen in love with the Krexus ROM and am apprehensive to flash another. Just need that hotplug support (and OTA updates would be nice as well
Working:
RIL
Audio
Display
Bluetooth
Wifi
Sensors
Camera
Fingerprint
Broken:
VoLTE?
I will release when I want to.
o.o this one fixes the display error for internal storage space!
kgptzac said:
o.o this one fixes the display error for internal storage space!
Click to expand...
Click to collapse
you sure you were using an SD card (and the phone detects it)?
Jus sayin', I'm not gonna test it for now
P650SE said:
Yay! I have never been so excited in my entire life! BTW, how do you guys know the bug for internal storage space has been fixed, or is that just purely speculation? You kinda make it sound like there's already a download available for people who want to beta test.
Click to expand...
Click to collapse
In my opinion nougat and oreo are the most unexciting Google OS I know. It's nice to have, but half of the first year after release devs on XDA and even Google itself trying to bring back the performance or/and battery life the OS version before had.
Not to mention the problems with Magisk etc.
SilentEYE said:
In my opinion nougat and oreo are the most unexciting Google OS I know. It's nice to have, but half of the first year after release devs on XDA and even Google itself trying to bring back the performance or/and battery life the OS version before had.
Not to mention the problems with Magisk etc.
Click to expand...
Click to collapse
I suppose you're right. Neither Nougat or Oreo have brought significant changes, they have both been 'minor' updates with subtle changes to improve certain aspects of the OS. The last major update to Android was Lollipop, when the entire appearance was drastically overhauled from previous versions. I'm only excited because we just have to take what we're given, and any update to update the appearance and usability of Android after an entire year is a refreshing change! Even though Nougat was only a small update, it feels unbearable to me when switching back to Marshmallow without the new quick settings swipe-down; the one before the entire notification area appears. So even the small features can make a lot of difference to the overall experience! I'm still really looking forward to seeing the changes made in Oreo for myself when it comes to the Axon 7.
SilentEYE said:
In my opinion nougat and oreo are the most unexciting Google OS I know. It's nice to have, but half of the first year after release devs on XDA and even Google itself trying to bring back the performance or/and battery life the OS version before had.
Not to mention the problems with Magisk etc.
Click to expand...
Click to collapse
I don't get why people say this, honestly. Just because you didn't get a visual overhaul like you got from KitKat to Lollipop doesn't mean there weren't significant changes. Visually the OS is already at a level where there's no need for a major change (it has been "ready" since Lollipop, imo; Marshmallow, Nougat, and Oreo have all had small visual tweaks but have stuck to the Material language), and most of the tweaks work "under the hood." Oreo will bring Project Treble, which may just be the most significant change in Android in the last few years. It also brings improvements on the behavior of notifications and background services or apps. It's an incremental update, yes. But it's by no means a small update.
@Gases
We talked about excitement.
I mentioned the problems with the new OS updates, which brings maybe more security but also many problems to custom ROMs. Furthermore there are more problems in the first months. I don't need visual tweaks.
Project treble is mainly positive for stock ROMs. We will see, in which way custom ROMs can profit of this new feature.
Background battery eating apps are no problem on custom ROMs based on LOS, if you use the internal features or external apps. But again. It's nice to have already implemented.
Finally I am always thankful for all kind of ROMs and kernels devs provide to the community. And I was always someone who donated to say 'thank you'
@SilentEYE Will this thread be used for development progress or is it just a tease thread?
ethanscooter said:
@SilentEYE Will this thread be used for development progress or is it just a tease thread?
Click to expand...
Click to collapse
I am not the dev but this is probably more a promotion thread. Final builds will surely be on developement thread.
Some devs are working on oreo right now.
Let's wait and be thankful for their work.
Here is a small update about the situation. Since the most common stuff is working im going to release this rom in 1-3 days. But don't expect to much. This rom is still WIP.
Working now:
RIL(Calls, Sms)
Audio
Most of the stuff (NFC etc.)
Broken:
Camera
Fingerprint
VoLTE (Will be probably broken until we get new blobs)
OrdenKrieger said:
Here is a small update about the situation. Since the most common stuff is working im going to release this rom in 1-3 days. But don't expect to much. This rom is still WIP.
Working now:
RIL(Calls, Sms)
Audio
Most of the stuff (NFC etc.)
Broken:
Camera
Fingerprint
VoLTE (Will be probably broken until we get new blobs)
Click to expand...
Click to collapse
Does cellular data work?
ethanscooter said:
Does cellular data work?
Click to expand...
Click to collapse
Yas.
What about the speakers? Do they have the same problem as before the fix was found?
Teet1 said:
What about the speakers? Do they have the same problem as before the fix was found?
Click to expand...
Click to collapse
Probably since they just got audio to work and the ROM is very experimental.
Really looking forward to testing this when the first release is posted on the forums. I'm just hoping the camera and fingerprint sensor will be relatively simple to fix. Thanks for everything you've done so far!
Teet1 said:
What about the speakers? Do they have the same problem as before the fix was found?
Click to expand...
Click to collapse
ethanscooter said:
Probably since they just got audio to work and the ROM is very experimental.
Click to expand...
Click to collapse
Audio is working normal. Like on cm14.1 both speakers are working just fine.
yes.. you are the man!
hopefully cam and fingerprint will fixed soon.
thanks ordenkrieger and all others
Actually it would be nice if you can upload to test for us fp and camera is not important for me.
WesTD said:
Actually it would be nice if you can upload to test for us fp and camera is not important for me.
Click to expand...
Click to collapse
That would be nice and all, but I think the devs want mostly everything to work for those that prefer to have a stable build and etc.
WesTD said:
Actually it would be nice if you can upload to test for us fp and camera is not important for me.
Click to expand...
Click to collapse
I was just looking over in the Nexus 6 forms and to overcome the camera issue for them they had to upgrade from 7.1.2 - 8.0 and then restart the phone. So there is hope especially since the Nexus 6 is a 32-bit phone and I'm pretty sure 8.0 was supposed to be 64-bit.
Hello. It's me again, with another part of whole process called "make your smartphone just like you".
I've got this nice and shiny phone for about a month or so, I was able to unlock it on the second try (not sure why myfriends decided to turn it down the first time, but don't think that matters now), now I'll like to install custom TWRP 3.2.1.0. I've read today, that I do not need to make a factory reset after doing so. Is it correct? Is it just a misunderstanding?
Anyway, which custom rom do You consider to be the best? I would of course like to have newest Android, instead of being still in version 7 (which is not bad, but if it could be better, why shouldn't I use it?).
I do not have any specific features that I would like to have, but having plenty of configuration options is always nice.
For other options I do not really have an opinion, what should be important and what should be irrelevant. I've read that You could improve photo quality by using this stuff, but I'm not sure is it true or not. https://www.celsoazevedo.com/files/android/google-camera/
If it would be possible, I would gladly accept FHD recording in 60 FPS (not sure if this is available in stock) and MAYBE (if possible again) better quality of night photos. Far the most important thing is battery life and no bugs. If the rom is having issues with getting network, gps, bluetooth or anything else, I'm dropping it at once. Also, stability and ability to work without reseting itself or crashing is wanted by me. I've also heard that some mods could be quieter than stock and I would also like to avoid that. And some extra points will be granted for mod WITHOUT most of the google apps, since I'm not using them and actually deleting them from any rooted phone. From what I remember, installing new ones has not been a problem, even on stock phone, but uninstalling them when You get it on start is pain the neck.
Thanks for any help that might be useful!
you've posted thread in wrong neighbourhood
anyways post here https://forum.xda-developers.com/redmi-note-4 in order to get more help suggestions regarding Mido
Oh, one more thing - I did not specify it before. My CPU is Snapdragon, so I believe it makes a difference.
OmniROM, NitrogenOS, ResurrectionRemix 6.0 all should be good to go, you can look through the respective threads to see what extra functionality/customization they offer and then decide.
Personally i recommend flashing FrancoKernel over (compatible with all above).
Also flash Nano or Pico Gapps if you want bare minimum google package.
I'm right now on Omni.
buczek0711 said:
Oh, one more thing - I did not specify it before. My CPU is Snapdragon, so I believe it makes a difference.
Click to expand...
Click to collapse
An extensive list of Oreo ROMs for mido is here: https://forum.xda-developers.com/redmi-note-4/help/extensive-list-oreo-roms-mido-t3741277
Take your pick. I prefer ROMs based on AOSP-CAF, because they tend to be lean and skinny.
As far as camera is concerned, it all depends on your camera sensor. I have a Samsung sensor, and I find cstark27 mods of GCam very good - see https://www.celsoazevedo.com/files/android/google-camera/dev-cstark27/
Ok, I'll look into it. Next question – how do I check which camera sensor do I have?
buczek0711 said:
Ok, I'll look into it. Next question – how do I check which camera sensor do I have?
Click to expand...
Click to collapse
You will need to search the forum for that.
I'm also curious about this. I just ordered a Redmi Note 4 Global, 4/64 (mido) and I'm trying to figure out which Oreo ROM I should go with: Pixel Experience or unofficial LOS 15.1. I'm leaning towards the latter because of that sweet Treble support, but I don't know if it's more stable than Pixel Experience or not. Or if there's a ROM more stable than those two.
I'm interested in installing Magisk, the Xposed Oreo beta, Viper4Android, various Xposed modules and root apps. I want to stay away from SuperSU and SuperUser because they don't pass SafetyNet, AFAIK.
sk8223 said:
I'm also curious about this. I just ordered a Redmi Note 4 Global, 4/64 (mido) and I'm trying to figure out which Oreo ROM I should go with: Pixel Experience or unofficial LOS 15.1. I'm leaning towards the latter because of that sweet Treble support, but I don't know if it's more stable than Pixel Experience or not. Or if there's a ROM more stable than those two.
I'm interested in installing Magisk, the Xposed Oreo beta, Viper4Android, various Xposed modules and root apps. I want to stay away from SuperSU and SuperUser because they don't pass SafetyNet, AFAIK.
Click to expand...
Click to collapse
Well xposed triggers safety net so yeah. Unistalled it for that reason
Laurisss said:
Well xposed triggers safety net so yeah. Unistalled it for that reason
Click to expand...
Click to collapse
Huh. I didn't know that. Good thing I have a separate phone for my SafetyNet/root-checking games, haha.
DarthJabba9 said:
You will need to search the forum for that.
Click to expand...
Click to collapse
I've looked into it, looks like my phone is having Samsung one.
buczek0711 said:
I've looked into it, looks like my phone is having Samsung one.
Click to expand...
Click to collapse
That is good. You may also want to try Arnova's V6 GCam mod. That seems to be even better than cstark27.