For those familiar with Velocity Rom this is the kernel I build for it. Velocity hasnt been on XDA as a rule so Im sure not many are familiar. Velocity is my personal Rom Ive been building for years and have shared with all that are interested. This isnt and will never be an "official development project" but will always exist as long as I continue to develop Android roms.
Velocity is focused on speed, stability, and efficiency and not on adding every imaginable feature. As this is my personal Rom it will have everything I deem useful to me and/or that doesnt compromise the goals of the project.
I dont add every conceivable governor, I/O scheduler, or other user tweakable options. In fact, I typically remove all the options and keep the best. This is designed as a plug and play kernel, not something to be changed. Its also not designed for other Roms.
Please do not ask for features, ETA's, or related. Again, this is my personal kernel for my personal Rom and will be shared accordingly. That said, I do encourage healthy, friendly dialog in my threads.
Flashing instructions
1) Reboot to bootloader
2) Fastboot boot 'bootimage_name'.img to make sure it boots with no issues
3) Reboot to bootloader again
4) Fastboot flash boot 'bootimage_name'.img
5) Buckle up for safety - optional of course
Changelog
Download
Source
Thanks for this!
It's great to see another person building for our device. Not that the others aren't doing great work, but the more the merrier.
Once Q source drops, the real fun will begin. I can see potential for crazy speed and battery life over 10 hrs SOT on Q. Im coming from Shamu (Nexus 6) so this is quite a change in use and development. I think Im getting a good handle on what makes it tick though.
Question, am running bootleggers rom, kernel flashed fine and everything smooth, only thing wifi was broken, I wiped dalvik and restart phone issue still persist.
Tmobile 3axl
jsanta11 said:
Question, am running bootleggers rom, kernel flashed fine and everything smooth, only thing wifi was broken, I wiped dalvik and restart phone issue still persist.
Tmobile 3axl
Click to expand...
Click to collapse
Not surprising. This is why I stated it works on stock but no idea on custom ROMs. I can cook a boot image if you want to try that, but that would also be based on stock.
Boot image is up in the same folder if you want to try that, but this really is designed to run on either my Rom or stock. Once velocity is out I won't be building stand alone kernels.
ctfrommn said:
Not surprising. This is why I stated it works on stock but no idea on custom ROMs. I can cook a boot image if you want to try that, but that would also be based on stock.
Boot image is up in the same folder if you want to try that, but this really is designed to run on either my Rom or stock. Once velocity is out I won't be building stand alone kernels.
Click to expand...
Click to collapse
My bad I overlooked that part.. Understood, I'll wait till you cook up the rom and rock with it.. Thanks in advance
Android 10 kernel coming soon. Got it all working correctly now. Will be a magisk patched boot.img for now as that seems to work best.
I don't see any files in the pixel 3a xl folder
Which file is the correct one to download? Folders are showing as empty?
oranget said:
Which file is the correct one to download? Folders are showing as empty?
Click to expand...
Click to collapse
I just updated all the folders and OP. I just uploaded the build to the current link in the OP.
Kernel flashed great....running it now. Will reply soon on overall usage. I flashed it through EX kernel manager.
V10.1 uploaded......see changelog for differences
ctfrommn said:
V10.1 uploaded......see changelog for differences
Click to expand...
Click to collapse
And so it begins. Thank you my friend!
Yes, expect a lot of builds for the next week or two. I'm trying to work on the ROM side too but 10 is very different than Pie and so it's slow going.
Works nicely. Thanks for your effort!
sysak said:
Works nicely. Thanks for your effort!
Click to expand...
Click to collapse
How is your battery life compared to the previous version?
Wasn't on it long enough but I would expect they would be the same. Honestly I won't get a good battery cycle until I'm done getting this where I want it. I'm already several versions newer than 10.1
ctfrommn said:
Wasn't on it long enough but I would expect they would be the same. Honestly I won't get a good battery cycle until I'm done getting this where I want it. I'm already several versions than 10.1
Click to expand...
Click to collapse
Well, thank you for your continued work.
v10.2 up
I had an issue with touchscreen not working when waking up from sleep on 10.2. I use the fingerprint and if i unlock the phone from sleep (always on display showing) touch wont work but if i wake it, switch off the screen with the button and unlock again quickly then it's ok. Reverted to 10.1
Related
Hello everyone,
as the old KANG build that got posted here is very old I've decided to compile my own builds.
As many people demanded a newer build you can use mine.
Flashing this may brick your device and there is no support from either Cyanogen and his crew or me. You do this on your own responsibility.
This build is not final - it's more an alpha build. If you decide to use it you shouldn't care about bugs.
I'll keep posting updates every day (if there is any reason for it). There will be no guaranteed support and I won't add user-specific features for anyone.
This is not my work - it's mostly from Pershoot & Cyanogen. This build uses Pershoot's GitHub as base for the device.
If you like the builds you're welcome to donate for some Club Mate / Beer and new hardware.
Works:
WiFi works
No more SOD or display flickering
Buttery smooth
HQ Videoplayback
USB Transfer - use the MTP mode and stop complaining about ICS
Doesn't work:
Camera doesn't work
I will not provide detailed Changelogs. Read CM9 Gerrit ICS & P4Wifi for that.
You can find the official app in the Android Market for 1 €:
https://market.android.com/details?id=de.messerschmidt.tabkang
It supports direct reboot (normal and into the recovery) and downloading the newest rom (incl. version-check) from my private FTP.
GAPPS (4.0.4):
http://dev-host.org/8Re
Voice Search Fix:
http://forum.xda-developers.com/showpost.php?p=21745603&postcount=1
Builds:
03/04/12
http://dev-host.org/kfz MD5: 7ef460037f4dd4378cfefb43258e315a
02/29/12
http://dev-host.org/fDR MD5: b759b43b1a5ac670f8ac316f1e9b43c7
02/12/12
http://dev-host.org/NKf MD5: 57da37ec78f3e02eeef0e7cd7672c396
02/08/12
http://dev-host.org/JLT MD5: 78e78cbb31664645627245276d6f02d3
02/03/12
http://dev-host.org/a7m
Installation:
Flash CWM if you've got none (I'm using the Overcome one)
Backup your current build
Wipe data
Flash my build
Flash the Gapps
Reboot (may take a few minutes)
Enjoy
USB MTP:
As some people requested me to do a little How-to for enabling MTP-mode:
Go into the settings
Choose storage
Tap the 3 dots in the upper right (menu)
Choose "USB computer connection"
Check "Media device (MTP)"
Done
Notice:
This is a pure Android rom and no Samsung rom. There won't be any unneeded additions like TouchWiz, My Files, or whatever.
Look in the Market for other/better apps if you're seriously missing something. I won't any additions/apps/whatever to this rom except I want to use it myself (not gonna happen).
Videos (made by qbking77):
How to Install:
http://www.youtube.com/watch?v=qcvfmnJdxdQ
Review:
http://www.youtube.com/watch?v=7m54DQ0Sqm8
downloading this right now, thank you
Any noticeable differences?
Ghost114 said:
Any noticeable differences?
Click to expand...
Click to collapse
Just bug fixes, I think. I'm downloading now, so I'll report back later.
Installed and booted fine. Testing now, report back later.
new boot animation?
Sent from my SGH-I997 using Tapatalk
why didnt he mention the difference between this build and the other one ? oh well thx anyway.
theROMinator said:
new boot animation?
Sent from my SGH-I997 using Tapatalk
Click to expand...
Click to collapse
No, but is that the first thing you think of when a new CM9 build is posted? Well, we are all diffrent
tarekkkkk said:
why didnt he mention the difference between this build and the other one ? oh well thx anyway.
Click to expand...
Click to collapse
Because I don't know when he built his build?
The display isn't flickering anymore and I didn't get any SODs anymore.
How suitable for everyday use is this build, beside of the above mentioned issues?
Gonna go ahead and subscribe to this and see what issues there are.
Not sure how much longer I can hold out for official CM9/ICS.
Murmel2k said:
How suitable for everyday use is this build, beside of the above mentioned issues?
Click to expand...
Click to collapse
Now that the flickering is fixed and SOD, I'd say it's well suited for daily use.
P.S. It also seems to be alot smoother, and you now get Terbuchet settings. Only thing missing for me is the camera.
is it safe to overinstall over DaAwesome1's ICS Kang, or must I wipe?
Does anyone know please, whether the cm9 kernal supports undervolting?
got556 said:
Gonna go ahead and subscribe to this and see what issues there are.
Not sure how much longer I can hold out for official CM9/ICS.
Click to expand...
Click to collapse
Ditto: well, I think I'll only hold out log enough to get my tablet charged.
danielsf said:
Does anyone know please, whether the cm9 kernal supports undervolting?
Click to expand...
Click to collapse
I was able to install setcpu and set the clock speed with the first ICS Kang
Beakerzor said:
is it safe to overinstall over DaAwesome1's ICS Kang, or must I wipe?
Click to expand...
Click to collapse
Basically a wipe shouldnt be needed. Test share your experience.
Does Netflix work? I'm this close to jumping on this.
This is just a whole new CM9 from the build posted earlier. The old build worked very smooth, as long as you didnt fill it with lots of user apps and widgets then it became very laggy. I have now restored all my apps 250+ and its still silky smooth, i have widgets with sync on several windows and app shortcuts and it still behaves as if it where just installed (empty). this sure gives hope for our tab. Go CM Team and thanks to OP for posting this build.
This build is an improvement over the prior kang, seems the CM team has been busy over the holidays. Smoother UI, screen flickers are gone, definite daily driver material. Will report back if I run into any problems.
Hi guys,
I successfully built CM12 off the official cyanogenmod source. All of dhackers builds in the past have thrown status 1 errors on our phone, so this is the closest thing to official cyanogenmod lollipop we have at the moment.
All credit goes to dhacker29 and the rest of the razrqcom / cyanogen dev team. All I did was set up a build environment and built straight from the source. I used no hacks, tweaks or mods to get this to build.
I'll try to build new builds occasionally, but I'm pretty busy so can't commit to making regular nightlies or anything.
Code:
[B]Instructions:[/B]
Download the latest zip (cm-12-*-UNOFFICIAL-mb886.zip) to your phone.
Boot to recovery.
Remember to make a Nandroid backup!
Format /system. (Some recoveries have this as "Wipe Data/Factory Reset > Clean to Install a New ROM") (You can try doing a "dirty flash" without formatting system but I don't recommend it)
Install the ROM (install zip from...).
Install gapps (install zip from...).
Wipe data/cache
Reboot.
First boot can take some time due to ART in lollipop.
DOWNLOAD from DevDB
Obtaining Root:
kabaldan said:
Please don't use SuperSU, it does not help the CM12 debugging at all (and it's been already reported as a cause of battery drain). The CM built-in su can be easily enabled under Developer options>Root access, it works just fine.
Click to expand...
Click to collapse
Gapps
I take no responsibility if your phone bursts into flames, etc.
XDA:DevDB Information
CyanogenMod 12.0 (Unofficial), ROM for the Motorola Atrix HD
Contributors
helloha1
Source Code: https://github.com/CyanogenMod/android_device_motorola_mb886/tree/cm-12.0
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Unlocked Bootloader
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-01-29
Last Updated 2015-02-17
Changelog:
http://www.cmxlog.com/12/xt925/
Since MB886 has no official nightlies currently, it doesn't have an official changelog. But changes should mirror the Razr HD builds very closely.
reserved
thanks for the rom.. will try it out and post feedback
Any known bugs?
Dirty updated from Miiju CM12 and seems to work fine. The ROM is smooth and solid. Reboot time is noticable longer than on Mijuu's build, maybe connected with the new bootscreen. Haven't noticed any bugs yet. Thanks for the great job.
PS. The new CM bootscreen is ugly :laugh: - imho of course. However, previous wasn't the masterpiece too .
Does this have the new theme engine? Good job bro you should maintain cm12 and let dhacker know.
Really laggy and random reboots
I made a clean flash of this build. It was smooth for first 30 to 40 seconds after that **** laggy and rebooted twice in 20 minutes.. i also experiences screen tearing. bugs are same as that of other builds though.
Great! I will try it tonight and report back. Thanks!
TecknoFreak said:
Does this have the new theme engine? Good job bro you should maintain cm12 and let dhacker know.
Click to expand...
Click to collapse
Theme engine implemented and works!
As far as being device maintainer, I'm definitely open to it but I'm not sure if I'm qualified enough to do it. If there were functional problems and things that break I don't really think I have the knowledge to fix those... All I really did here was follow some build guides and build this. But if you think that's all I need, I'll definitely consider it.
Aingaran said:
I made a clean flash of this build. It was smooth for first 30 to 40 seconds after that **** laggy and rebooted twice in 20 minutes.. i also experiences screen tearing. bugs are same as that of other builds though.
Click to expand...
Click to collapse
Aingaran I've also experienced some occasional reboots and force closes of google play services. Not so much the lag though. However, the rom seem significantly smoother if you use Launcher3 instead of Google Now launcher from my limited experience so far.
Legza said:
Dirty updated from Miiju CM12 and seems to work fine. The ROM is smooth and solid. Reboot time is noticable longer than on Mijuu's build, maybe connected with the new bootscreen. Haven't noticed any bugs yet. Thanks for the great job.
PS. The new CM bootscreen is ugly :laugh: - imho of course. However, previous wasn't the masterpiece too .
Click to expand...
Click to collapse
Good to hear Legza. Agreed on the bootscreen, I think it's better than the old one but that's not saying much
rangapsr said:
thanks for the rom.. will try it out and post feedback
Click to expand...
Click to collapse
mauchito said:
Great! I will try it tonight and report back. Thanks!
Click to expand...
Click to collapse
Thanks, look forward to hearing your feedback!
helloha1 said:
Aingaran I've also experienced some occasional reboots and force closes of google play services. Not so much the lag though. However, the rom seem significantly smoother if you use Launcher3 instead of Google Now launcher from my limited experience so far.
Good to hear Legza. Agreed on the bootscreen, I think it's better than the old one but that's not saying much
Thanks, look forward to hearing your feedback!
Click to expand...
Click to collapse
Nice job with the build, Im going to flash this thing tonight and report whats happening with this rom
Thank you for doing this for us.
Edit: Clean flashed rom without gapps: smooth as it should be, seems noticeably faster than LS
Now with Banks gapps: Still as fast with no random reboots yet. Looking great so far. I wonder if the bugs are gapps related for some of you people then.
Antutu benchmark for mb886: 19544, thats as fast as mijuus cm12, great job man.
Bugs: Chromecast cannot mirror, its the same OMX-720p error from log cat, its now a bug with dhackers builds. Mijuus doesnt have that at all, probably a hack . Im maybe wrong it could go away on its own. But its something to do with that which is causing the AvSource to fail with this error: w/err = -38
Overall this rom is as stable as it can be, there isn't any other bug I could find but that one, I did try mirror enabler for the previous one, it didn't affect anything. Speedy fast and simplistic, great job on this first build. Keeping that one as a daily driver until then.
Good job!
Thank you! :good:
Justatechie said:
Nice job with the build, Im going to flash this thing tonight and report whats happening with this rom
Thank you for doing this for us.
Edit: Clean flashed rom without gapps: smooth as it should be, seems noticeably faster than LS
Now with Banks gapps: Still as fast with no random reboots yet. Looking great so far. I wonder if the bugs are gapps related for some of you people then.
Antutu benchmark for mb886: 19544, thats as fast as mijuus cm12, great job man.
Bugs: Chromecast cannot mirror, its the same OMX-720p error from log cat, its now a bug with dhackers builds. Mijuus doesnt have that at all, probably a hack . Something is failing to start AvSource w/err = -38
Overall this rom is as stable as it can be, there isn't any other bug I could find but that one, I did try mirror enabler for the previous one, it didn't affect anything. Speedy fast and simplistic, great job on this first build. Keeping that one as a daily driver until then.
Click to expand...
Click to collapse
Great feedback, thank you. I experienced the same thing- super stable without gapps. Might try flashing again with banks gapps.
If anyone wants to try out the CM recovery I built based on the latest source, here it is. I haven't tried it out yet since I'm happy with the philz touch build I have, but if you do flash it let me know how it works.
helloha1 said:
Great feedback, thank you. I experienced the same thing- super stable without gapps. Might try flashing again with banks gapps.
If anyone wants to try out the CM recovery I built based on the latest source, here it is. I haven't tried it out yet since I'm happy with the philz touch build I have, but if you do flash it let me know how it works.
Click to expand...
Click to collapse
Try it with Banks, it makes your rom the way it is. I haven't even ran into a crash, I pushed this device pretty hard and its still not rebooting, came close though.
As for the future builds of this rom, maybe the problem will go away as time goes on, idk but I think I found a way around it.
Wow a cm recovery, but im happy for my philz but sooner or later this recovery will be needed to flash newer roms. Blisspop from droidrazr requires this recovery for some odd reason.
Plus its late for me anyway.
Great job on this rom and the recovery Thank you.:good:
Awesome, Thanks!
@helloha1 - Thanks for the build , It's really smooth :good: keep up the good work , Thanks to dev that helped to make this build i was tired of getting bootloops (blisspop & vanir) and otherdevs (laggy) builds ...
You really made my day
bugs ? isnt that too soon for cm12 to be bug free :silly:
users facing bugs probably because of CyanogenMod12
:good: :good: :good: :good:
Very impressive, good work adapting CM12 to work with our old phone.
Uploaded a new build. Don't think there are any big changes since yesterday.
Also switched hosting to XDA's DevDB.
helloha1 said:
Uploaded a new build. Don't think there are any big changes since yesterday.
Also switched hosting to XDA's DevDB.
Click to expand...
Click to collapse
What are the changes ?
1st build
Click to expand...
Click to collapse
too much Battery Consumption dont know why ... havent installed a single app yet , wifi and data also disabled , and the battery thing is happened when the phone was in Sleep.
From 100% to 86% in 45 mins during sleep!
see the SS of Batterystats below ...
mrroks said:
What are the changes ?
Click to expand...
Click to collapse
Should just be whatever is called out in cmxlog in post 2.
As far as battery life, not sure. I used the phone all day today from about 10 to 9 and was at around 40% at the end of the day. Granted, I have an upgraded EB40 battery.
I have had a DT since launch and I have had a custom ROM on for quite a while and upon using Android N (through crDroid) I found an extreme amount of forced reboots, I was wondering what causes them as I would love to join the ranks of the 1%ers who use android N across all platforms.
Obviously saying "it doesn't work please fix" is not going to get me anywhere so ill throw my pride out the window and accept any and all assistance if yall would be so kind.
Sareniah said:
I have had a DT since launch and I have had a custom ROM on for quite a while and upon using Android N (through crDroid) I found an extreme amount of forced reboots, I was wondering what causes them as I would love to join the ranks of the 1%ers who use android N across all platforms.
Obviously saying "it doesn't work please fix" is not going to get me anywhere so ill throw my pride out the window and accept any and all assistance if yall would be so kind.
Click to expand...
Click to collapse
crDroid is notorious for that. Try any of the other 7.1 roms that are out there. I installed AOKP 2 days ago and it hasn't rebooted yet. Battery life is awesome too.
ok. Ill try out aokp as that is what I used in 6.0.1 Thanks!
Sareniah said:
ok. Ill try out aokp as that is what I used in 6.0.1 Thanks!
Click to expand...
Click to collapse
Just to give you an update, I just removed AOKP because whenever I try to make a call through a Bluetooth device (like my car's hands free system), it completely messes up the phone and eventually force reboots. These roms are based on early versions of CM14.1 (we don't even have official CM14.1 builds yet) so some bugs are to be expected, but they're all being updated very regularly so I expect that they will be virtually bug free in a no time. Just keep trying them until you find one that works for you.
TheSt33v said:
Just to give you an update, I just removed AOKP because whenever I try to make a call through a Bluetooth device (like my car's hands free system), it completely messes up the phone and eventually force reboots. These roms are based on early versions of CM14.1 (we don't even have official CM14.1 builds yet) so some bugs are to be expected, but they're all being updated very regularly so I expect that they will be virtually bug free in a no time. Just keep trying them until you find one that works for you.
Click to expand...
Click to collapse
RR 7.x was just released yesterday. People are saying it's quite stable.
[ROM][All Quark][7.x]Resurrection Remix
http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3511109
khangozzy said:
24 hrs without reboot issue, great job as usual @bhb27, thanks.
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
johnbravado said:
This ROM is awesome. Using latest GApps and no reboots no issues. Smooth sailing. I believe much better than crDroid. The RR team is amazing and thanks to @bhb27 for working hard.
Click to expand...
Click to collapse
quantum tao said:
So far is running good. Not a fan of pixel launcher though, also i think the network icons in crdroid are more functional because they have built in traffic arrows.
Glad to have proximity speakerphone back.
Click to expand...
Click to collapse
xboxbr said:
very stable for me. no reboots so far
Click to expand...
Click to collapse
________
Also @calsurferpunk just re-synced his "unofficial" CM14 to RR's builds to hope to get that stability. Previously he was uing crDroids database (or whatever). His unofficial CM14 builds are a hybrid of more bare bones CM and everything-including-the-kitchen sink tweaks of custom ROMs. His builds have the more popular tweaks, like being able to download Moto apps and a couple more, but are not change-everything ROMs.
[ROM][2016-12-03][Quarks][CM 14.1 Unofficial][7.1.x]
http://forum.xda-developers.com/moto-maxx/development/rom-t3494646
calsurferpunk said:
I just posted an updated build. I'm using repos from RR instead of crDroid (still configured to be stock CM 14.1) and the "stock" kernel from 2bhb27. Hopefully this fixes the instability issues. You should go over and thank him as well for all of his hard work
https://www.androidfilehost.com/?fid=385035244224403322
Click to expand...
Click to collapse
I really appreciate your assistance with this mate. I remember back when we had mofo and your only option was basically build an image yourself or take whatever one guy was developing. I'm really thankful we have evolved no thanks to the developers like chainfire and all the wonderful people who still care for our 3900mah mini Nexus 6... Or at least close enough
Edit: I will try out CM14.1 Unofficial for a day and see how that goes. I really want to stay away from "kitchen sink" roms because of the restarts. Thanks again for your help
Flashed 15 different times today, stock OOS 7.0. camera works fine on stock, even with magisk installed. As soon as I flash any custom kernel the camera app gets unknown error. Tried clearing cache, etc everything. Only stock kernel works. What gives?
You might want to read the kernel threads for help. Seems like if it was a kernel issue like you claim then someone else might have noticed it. Sounds like user error to me
954wrecker said:
You might want to read the kernel threads for help. Seems like if it was a kernel issue like you claim then someone else might have noticed it. Sounds like user error to me
Click to expand...
Click to collapse
Thanks brain.
Magisk is the reason for those errors, im using custom kernel since android 7.0 with system less superSU only, I already tried three different custom kernels here and they didn't gave me any camera errors
J4DedPrez said:
Thanks brain.
Click to expand...
Click to collapse
Wow, smartass answer for someone who can't flash a kernel without breaking the camera.
Actually, the answer is the solution you need, search and read.
exaflare said:
Magisk is the reason for those errors, im using custom kernel since android 7.0 with system less superSU only, I already tried three different custom kernels here and they didn't gave me any camera errors
Click to expand...
Click to collapse
Thank you friend, sometimes being nice and giving the simple solution is the simplest method.
Migdilu said:
Wow, smartass answer for someone who can't flash a kernel without breaking the camera.
Actually, the answer is the solution you need, search and read.
Click to expand...
Click to collapse
Typical XDA user... It's a real shame kids these days act the way they do
J4DedPrez said:
Typical XDA user... It's a real shame kids these days act the way they do
Click to expand...
Click to collapse
What it's a shame is that there are people who don't know how to read.
Magisk does work with custom kernels, but the order you flash them in is important. Magisk alters certain files in the /boot partition, which is also where the kernel is located. You should flash Magisk first over a clean ROM prior to flashing any custom kernels, or else you may run into issues. If an update for Magisk is pushed, you should also install it in the following order:
1) Dirty flash ROM (or stock kernel)
2) Flash Magisk
3) Flash custom kernel
I'm currently using Magisk v11.6 with Franco's r16 on OOS 4.1.0 without a problem.
Don't mean to be rude, but did you flash the compatible kernel; and not using adb sideload problems; on TWRP 3.0.4-1?
If you did, well then Magisk seems to be a problem for you.
And do post logs next time of you encounter a problem until and unless you are sure you everybody can reproduce that problem with the steps mentioned (which should be though)
If you're still in Android 7.0 (like me), do not use the latest custom kernel release, it will break your camera (Unknown Error). I think it's because the dev has rebased their kernel to the new Android 7.1.1.
Currently, I'm still on FredomOS 2.5 (OOS 4.0.3) and its combined with BluSpark v.72 (last release before the 7.1.1 rebase).
I don't want to use the latest OOS update since it's still full of annoying bugs.
In my opinion only people who understand what they are doing with this kind of stuff should get the oneplus 3 or 3t as it isn't very noob friendly and takes someone that is some what an advanced user or at least knows a little about flashing ROMs and kernels etc..... Or at least is willing to search around and read before they complain to everyone that they can't figure it out. If you want a phone that is simple and noob use friendly then go to Samsung or Apple. not oneplus as phone from this company are aimed at the intermediate up to power user that understands how to solve irregular problems. I've had none of these issues even when I was using my oneplus x. I use the unofficial RR with ex kernel and no problems with camera or anything and great battery life. Bottom line is (in my opinion anyways) oneplus phones are for the more technically savvy so if you aren't some one like that expect to run in to difficulties and have to do some deep research in certain cases. But this is a great community here at xda and we are all willing to help as much as we can but patience is a must.
Anova's Origin said:
Magisk does work with custom kernels, but the order you flash them in is important. Magisk alters certain files in the /boot partition, which is also where the kernel is located. You should flash Magisk first over a clean ROM prior to flashing any custom kernels, or else you may run into issues. If an update for Magisk is pushed, you should also install it in the following order:
1) Dirty flash ROM (or stock kernel)
2) Flash Magisk
3) Flash custom kernel
I'm currently using Magisk v11.6 with Franco's r16 on OOS 4.1.0 without a problem.
Click to expand...
Click to collapse
Same exact order as you, even flashed fresh ROM and kernel only. Can't explain it at all. For now, I'm on stock with no custom kernel but have magisk.
mrinmaydhar said:
Don't mean to be rude, but did you flash the compatible kernel; and not using adb sideload problems; on TWRP 3.0.4-1?
If you did, well then Magisk seems to be a problem for you.
And do post logs next time of you encounter a problem until and unless you are sure you everybody can reproduce that problem with the steps mentioned (which should be though)
Click to expand...
Click to collapse
No sideload, using most recent TWRP, and yes, I will have logs to post tomorrow. As a quick flasher I never really bother for the logs, but this time I'm getting down to the bottom of this. I'll have logs tomorrow
motherninja said:
If you're still in Android 7.0 (like me), do not use the latest custom kernel release, it will break your camera (Unknown Error). I think it's because the dev has rebased their kernel to the new Android 7.1.1.
Currently, I'm still on FredomOS 2.5 (OOS 4.0.3) and its combined with BluSpark v.72 (last release before the 7.1.1 rebase).
I don't want to use the latest OOS update since it's still full of annoying bugs.
Click to expand...
Click to collapse
This is exactly the issue. Thank you
se7ensde said:
In my opinion only people who understand what they are doing with this kind of stuff should get the oneplus 3 or 3t as it isn't very noob friendly and takes someone that is some what an advanced user or at least knows a little about flashing ROMs and kernels etc..... Or at least is willing to search around and read before they complain to everyone that they can't figure it out. If you want a phone that is simple and noob use friendly then go to Samsung or Apple. not oneplus as phone from this company are aimed at the intermediate up to power user that understands how to solve irregular problems. I've had none of these issues even when I was using my oneplus x. I use the unofficial RR with ex kernel and no problems with camera or anything and great battery life. Bottom line is (in my opinion anyways) oneplus phones are for the more technically savvy so if you aren't some one like that expect to run in to difficulties and have to do some deep research in certain cases. But this is a great community here at xda and we are all willing to help as much as we can but patience is a must.
Click to expand...
Click to collapse
:good:
Flashing kernels made for 7.1.1 on 7.0 FW.
954wrecker said:
You might want to read the kernel threads for help. Seems like if it was a kernel issue like you claim then someone else might have noticed it. Sounds like user error to me
Click to expand...
Click to collapse
Normal, helpful, response(don't be discouraged by some).
J4DedPrez said:
Thanks brain.
Click to expand...
Click to collapse
Douche response.
Migdilu said:
Wow, smartass answer for someone who can't flash a kernel without breaking the camera.
Actually, the answer is the solution you need, search and read.
Click to expand...
Click to collapse
Obvious observation.
J4DedPrez said:
Thank you friend, sometimes being nice and giving the simple solution is the simplest method.
Click to expand...
Click to collapse
Hypocrisy.
Hi all !
This discussion might be related with my issue explained here:
https://forum.xda-developers.com/oneplus-5/help/camera-flashlight-youtube-t3886260
but only thing is I never flashed custom kernels, issue appears after a official update !
Any opinion, ideas ?
Thanks
Hello, so I'm asking if I should flash a custom ROM instead of keeping my OOS 4.1.3?
U have to try man. It's clear thing for this device.
Thunderbolt said:
U have to try man. It's clear thing for this device.
Click to expand...
Click to collapse
What roms do u recommend? Ive flashed RR on my mom's galaxy s5, it looks pretty good
idubis said:
What roms do u recommend? Ive flashed RR on my mom's galaxy s5, it looks pretty good
Click to expand...
Click to collapse
One of available versions of RR, phoenix AEX, official AEX, Dirty Unicorns. Today im back to Phoenix AEX, it is a great, stable and fast rom with great developer.
idubis said:
Hello, so I'm asking if I should flash a custom ROM instead of keeping my OOS 4.1.3?
Click to expand...
Click to collapse
This is so vague, as it tells us nothing about what features you may be looking for, why you want a custom ROM, etc.
If you are just looking for something different, then sure, go for it. Similarly, if certain features of a custom ROM (or ROMs) look attractive, then go for it. There is really no downside, as unlocking the bootloader does not void the warranty. And reversing any changes (returning to stock) is pretty easy as well.
On the other hand, stock OOS is amazingly good. Very little bloat or skinning, but with the right amount (IMO) of customization added. Many folks (myself included) accustomed to flashing custom ROMs to get the most out of their device, have been just happy with stock OOS. But of course, there is always room for improvement, tweaking, etc.
It's an individual choice. Most users of Android devices will never flash a custom ROM. Majority probably don't even know what that means.
idubis said:
Hello, so I'm asking if I should flash a custom ROM instead of keeping my OOS 4.1.3?
Click to expand...
Click to collapse
First determine what you`re missing in stock OOS, find those features in a custom rom/kernel and flash it. Done
gee2012 said:
First determine what you`re missing in stock OOS, find those features in a custom rom/kernel and flash it. Done
Click to expand...
Click to collapse
I want something different, and good battery life
idubis said:
I want something different, and good battery life
Click to expand...
Click to collapse
Its not just a rom or kernel that makes great batterylife, mobile reception strenght (modem ) and usage (apps, syncing, gaming yes or no) are vital too.
I'd go with FreedomOS or RRemix. Really LineageOS is mostly placebo battery fixes and an overabundance of customization options. Most of the lineage roms outside of RRemix are very unstable or just kinda useless. Hate to say it cuz some devs put lots of time in but Ive always found worse battery life with the same usage patterns on anything but stock.
OcazPrime said:
I'd go with FreedomOS or RRemix. Really LineageOS is mostly placebo battery fixes and an overabundance of customization options. Most of the lineage roms outside of RRemix are very unstable or just kinda useless. Hate to say it cuz some devs put lots of time in but Ive always found worse battery life with the same usage patterns on anything but stock.
Click to expand...
Click to collapse
Oh. That's bad. I want to use a custom ROM. But if Oxygen is so much better?!?!? :silly:
No good ROM available?
Well Oxygen OS was made for this specific phone in mind remember. So of course it fares best.
I don't know. Perhaps lineage with sultan kernel is an option.
I try to find the best ROM with great battery life, performance, stability, features etc. Any recommendations?
Phoenix is good, Resurrection remix also, but how is battery life and performance? So many features in it...
derAndroidler said:
Oh. That's bad. I want to use a custom ROM. But if Oxygen is so much better?!?!? :silly:
No good ROM available?
Click to expand...
Click to collapse
In the time you've been waiting around for someone to make a decision for you; you could have just unlocked the bootloader and flashed a ROM (of even more than one) and be trying it yourself.
Just make a TWRP backup of the stock ROM (or otherwise, know how to return to stock with the official zip file) and you can easily revert if you don't like the ROM you flashed.
No point in waiting for someone else to tell you what to do. Everyone's opinion and preference is going to be different. Just because someone tells you to flash a ROM or not (or which one), doesn't mean that is the right answer for you as an individual.
Even things like battery life and performance are going to vary drastically depending on how you as an individual use your device (as others have also mentioned). Then also throw in the differences in personal preferences and tastes; and the result is that you can't go by the direction of others. You need to decide for yourself.
redpoint73 said:
In the time you've been waiting around for someone to make a decision for you; you could have just unlocked the bootloader and flashed a ROM (of even more than one) and be trying it yourself.
Just make a TWRP backup of the stock ROM (or otherwise, know how to return to stock with the official zip file) and you can easily revert if you don't like the ROM you flashed.
No point in waiting for someone else to tell you what to do. Everyone's opinion and preference is going to be different. Just because someone tells you to flash a ROM or not (or which one), doesn't mean that is the right answer for you as an individual.
Even things like battery life and performance are going to vary drastically depending on how you as an individual use your device (as others have also mentioned). Then also throw in the differences in personal preferences and tastes; and the result is that you can't go by the direction of others. You need to decide for yourself.
Click to expand...
Click to collapse
Thanks. I already tried some ROMs. But I can't decide.
Are there big differences in battery life?
derAndroidler said:
Thanks. I already tried some ROMs. But I can't decide.
Are there big differences in battery life?
Click to expand...
Click to collapse
If you are still asking that question, then you missed one of the main points of my last post:
redpoint73 said:
Even things like battery life and performance are going to vary drastically depending on how you as an individual use your device
Click to expand...
Click to collapse
Plus others (more than one) on this thread have already answered the question (of battery life on the various ROMs).
No
Sent from my OnePlus 3T using XDA Labs
@redpoint73
You're right. It's only so difficult to decide, because here are so many ROMs and kernels and they are all similar and I want a good daily driver and don't want to change it the next years.
derAndroidler said:
@redpoint73
You're right. It's only so difficult to decide, because here are so many ROMs and kernels and they are all similar and I want a good daily driver and don't want to change it the next years.
Click to expand...
Click to collapse
If you're so concerned about battery life, beta 7 + Franco kernel
sakumaxp said:
If you're so concerned about battery life, beta 7 + Franco kernel
Click to expand...
Click to collapse
I will try lineage with sultanxda kernel. I hear it has amazing battery life.
I also like Resurrection Remix , but I suppose, it has bad battery life, but I'm not sure.
I've tried a handful of roms... they're all just fine in my opinion but I seem to always end up back on the Oxygen stock rom. I root, but that's about it. I just can't get over how well Oxygen OS is running these days compared to my OP2 ... Just flash and try! You won't hurt anything, and if you do you have a 99% chance of fixing it!