Database Develop

Every Custom Kernel kills camera

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

[ROM][4.4.2][N801x] Fastest ROM [Based on: Stock TouchWiz]

Fastest ROM​
Credits:​Samsung Galaxy Note 10.1 - Samsung Electronics
Firmware: TouchWiz - Samsung Electronics
Android 4.4.2 - Google Inc.​
Requirements:​twrp-3.0.2-0-n801x.img​
Download:​https://www.androidfilehost.com/?w=files&flid=282751​
- Secretwolf98​

Not able to log in to wifi. Any ideas that can help me. Thanks.

wicho71 said:
Not able to log in to wifi. Any ideas that can help me. Thanks.
Click to expand...
Click to collapse
Flash this file in the recovery.

Revived my N8013, works great! Mirroring Fix Zip
Deleted everything on the Internal Storage and EXT-SD and flashed this ROM with the WiFi-fix. Very usable. Have been through all the other Custom Roms - this one works without lags and freezes.
Please add this zip to fix mirroring (Yes, works with FireStick) :
https://forum.xda-developers.com/attachment.php?attachmentid=2784504&d=1402087218

GT-N8000?
I was wondering if this ROM works with GT-N8000. I'm own a N8000 and I'm looking for the fastest ROM for the device. Thank you for any responses in advance

nsian001 said:
I was wondering if this ROM works with GT-N8000. I'm own a N8000 and I'm looking for the fastest ROM for the device. Thank you for any responses in advance
Click to expand...
Click to collapse
Were you able to try the ROM yet? I have the N8000 too, and Lineage just isn't working out well for me, so I'm looking for a stable build, and hoping this is it [emoji16]
Sent from my MAR-LX1M using Tapatalk

While flashing with twrp it is saying unable to mount system. My device is n8000

uzumakivishal96 said:
While flashing with twrp it is saying unable to mount system. My device is n8000
Click to expand...
Click to collapse
Need to use the TWRP 3.0.2 provided, I used a version of 3.2 would have the issue.

mkcs said:
Need to use the TWRP 3.0.2 provided, I used a version of 3.2 would have the issue.
Click to expand...
Click to collapse
Oh, when I re-flashed the rom again, the same problem arised even though the twrp is 3.0.2. After several trials, I found that the solution was to REBOOT to recovery after wiping your old system. Then, it could successfully be installed.

I found that the tablet cannot charge in power off mode. Even though I shutdown my tablet during charging, it automatically reboots. Any reason for this?

mkcs said:
I found that the tablet cannot charge in power off mode. Even though I shutdown my tablet during charging, it automatically reboots. Any reason for this?
Click to expand...
Click to collapse
Mine is N8000 as well. I could flash the rom with TWRP3.2 and I still can charge when tablet is power off.

Thanks for this.
I was having problems on the newer roms and went back to basics. All seems well.
I was also happy to see the Boeffla kernel inside. Any chance you have the final version of the Boeffla app? (now that his website is finished?)
Much appreciated!

Flashed on N8000 running Philz_touch_6.48.4-n8000. So far so good. WiFi working. Much more snappier vs AndroidRevolution 21 and LineageOS. Glad i stumbled upon this post.

androidfilehost isn't getting any mirrors :angel:

thanks for this beaut. Revived my note 10.1 n8000 (got a close error glitch on touchwiz but it only needs to wipe after flash rom). only problem is, this is an n8013 rom - coming from a WiFi only tablet, it isn't capable of making calls or sending SMS. But this is one of the fastest rom I have tried (only if you don't mind using an old stock gnote 10.1 rom)

[KERNEL] [Android 12] [v12.9] MVK - Maximum Velocity Kernel

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

ROM for Xiaomi mi 8

i am using xiaomi mi 8 and i don't know which rom is better for mi, i want to play game , good camera and GPS, Can you give me some suggest, which rom is suitable for me, thank you so much

Easy User said:
i am using xiaomi mi 8 and i don't know which rom is better for mi, i want to play game , good camera and GPS, Can you give me some suggest, which rom is suitable for me, thank you so much
Click to expand...
Click to collapse
This question has no sense.
Nobody know what rom is the best for you. There are several roms for dipper and all are good. Try yourself and stay with the best for you.

Easy User said:
i am using xiaomi mi 8 and i don't know which rom is better for mi, i want to play game , good camera and GPS, Can you give me some suggest, which rom is suitable for me, thank you so much
Click to expand...
Click to collapse
Personally I like Xiaomi.EU the best, it is always the most up to date, uses the latest source code and there are no issues with anything, battery life is outstanding. Absolutely there are many great roms, but for me is the most consistently stable.
If you try it, use the built in kernel, and it works fine with the latest magisk Canary.

Easy User said:
i am using xiaomi mi 8 and i don't know which rom is better for mi, i want to play game , good camera and GPS, Can you give me some suggest, which rom is suitable for me, thank you so much
Click to expand...
Click to collapse
If you need MIUI than xiaomi.eu is best option, if you need AOSP with extra gimmicks than you can consider HavocOS, if you need pure Pixel experience than PixelRom or Pixel Experience is your best bet. But there are several roms out there you can check but this is my own opinion and you asked for it :laugh:

tsongming said:
Personally I like Xiaomi.EU the best, it is always the most up to date, uses the latest source code and there are no issues with anything, battery life is outstanding. Absolutely there are many great roms, but for me is the most consistently stable.
If you try it, use the built in kernel, and it works fine with the latest magisk Canary.
Click to expand...
Click to collapse
I had a fingerprint issue with xiaomi eu. Where as soon as an app was launched it would detect ghost touches. Had to move over to lineage OS. Don't know if it was just me or it affected others too.

abmoh13 said:
I had a fingerprint issue with xiaomi eu. Where as soon as an app was launched it would detect ghost touches. Had to move over to lineage OS. Don't know if it was just me or it affected others too.
Click to expand...
Click to collapse
I have never had that issue. most people that had that issue was when Android 10 first came out. Try it again sometime. Just be sure to start clean with a full wipe.

tsongming said:
I have never had that issue. most people that had that issue was when Android 10 first came out. Try it again sometime. Just be sure to start clean with a full wipe.
Click to expand...
Click to collapse
Tried clean flash, yet no luck. Strange thing is that this issue only occurs with some apps, while others work just fine. All other roms (lineage, havoc and pe) work without this issue. Real shame as I prefer miui.

abmoh13 said:
Tried clean flash, yet no luck. Strange thing is that this issue only occurs with some apps, while others work just fine. All other roms (lineage, havoc and pe) work without this issue. Real shame as I prefer miui.
Click to expand...
Click to collapse
Without a doubt, one of those custom roms custom roms has corrupted one of your partitions .
You need to use a fast-food ROM and restore your phone, Use Mi Flash make sure the bootloader box is not checked or use Adb.
Note: A recovery ROM will not fix your issue it has to be a fastboot "images" ROM. Images will be in the name of the file.
Afterwards you can flash this ROM and no longer have those issues.

---------- Post added at 11:22 PM ---------- Previous post was at 11:21 PM ----------
tsongming said:
Without a doubt, one of those custom roms custom roms has corrupted one of your partitions .
You need to use a fast-food ROM and restore your phone, Use Mi Flash make sure the bootloader box is not checked or use Adb.
Note: A recovery ROM will not fix your issue it has to be a fastboot "images" ROM. Images will be in the name of the file.
Afterwards you can flash this ROM and no longer have those issues.
Click to expand...
Click to collapse
Your an absolute legend. Thanks.

Most stable Mi A2 rom?

which is the best and most stable rom for MI A2. By stable i mean for day to day use and obviously bug free rom.
Thanks in advance

Stock magisk y lswnchairv2

tohaxon said:
which is the best and most stable rom for MI A2. By stable i mean for day to day use and obviously bug free rom.
Thanks in advance
Click to expand...
Click to collapse
Sorry, but you'll have to test them by yourself and pick one that works for you... what suits me probably won't suit you. The features that I use the most probably are not as important to you, and probably the things that are important to you I don't use as much in order to say they are stable. The apps I use probably are not the same as you, the signal strength, the carrier, the charger, the bluetooth devices, the root method, magisk modules or even if you are not going to root.
I'm enjoying the PE+ rom, but I did many tweaks to it and it works for me, but there are many people facing really annoying bugs that makes it a no go. So there isn't an easy answer for what you are looking for.

Lunatiic said:
Sorry, but you'll have to test them by yourself and pick one that works for you... what suits me probably won't suit you. The features that I use the most probably are not as important to you, and probably the things that are important to you I don't use as much in order to say they are stable. The apps I use probably are not the same as you, the signal strength, the carrier, the charger, the bluetooth devices, the root method, magisk modules or even if you are not going to root.
I'm enjoying the PE+ rom, but I did many tweaks to it and it works for me, but there are many people facing really annoying bugs that makes it a no go. So there isn't an easy answer for what you are looking for.
Click to expand...
Click to collapse
can u suggest some?

tohaxon said:
can u suggest some?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/development

wow what kind of useless responses are those? He didnt say what is the best one, he asked what is the most stable dudes.

Hi! I tried most of them, PE+, HavocOS, AICP, LINEAGE, in my case the most stable and daily driver is Havoc OS, there is one problem on all of them for me, my banking app wont run on modded rom's so i reverted to miui, android one.
There is trial and error, some might work from start, some are harder to make them run ok, without any crashes. The fastest one i found was Pixel Experience+, the most stable one, Lineage OS(be carefull, it doesnt support google apps from the box), and the one which does any task well, good battery and stability in my case, was Havoc OS. With pleasure, ViVa.

omzart said:
wow what kind of useless responses are those? He didnt say what is the best one, he asked what is the most stable dudes.
Click to expand...
Click to collapse
And your input was more than helpful! Thanks for your effort!
The most stable ROM is obviously stock.

Exxdeea said:
The most stable ROM is obviously stock.
Click to expand...
Click to collapse
Lol, no.
Stock has serious bootloop issues between updates.
If you're staying on stock you should still unlock bootloader, just in case. And backup important data before updates.
This saved me 4 or 5 times already.

danannnn said:
Lol, no.
Stock has serious bootloop issues between updates.
If you're staying on stock you should still unlock bootloader, just in case. And backup important data before updates.
This saved me 4 or 5 times already.
Click to expand...
Click to collapse
Which Android version? I am on 10 and never had a boot loop after update but I always do it manually using fastboot.
I've also stripped Stock down to the bare-bones - no Google anything, except Play Services, Phone and Contacts and everything seems to work OK with no crashes ever.
I concur with your bootloader unlock advice.

Exxdeea said:
I've also stripped Stock down to the bare-bones - no Google anything, except Play Services, Phone and Contacts and everything seems to work OK with no crashes ever.
Click to expand...
Click to collapse
Hi all,
I bought my A2 yesterday. This is my first time thinking of using stock rom instead flashing i.e. Lineage. Can you describe the steps to stripe down stock?
Thanks!

danannnn said:
Lol, no.
Stock has serious bootloop issues between updates.
If you're staying on stock you should still unlock bootloader, just in case. And backup important data before updates.
This saved me 4 or 5 times already.
Click to expand...
Click to collapse
NEVER even once i had bootloop and im on stock since start

doc_relax said:
Hi all,
Can you describe the steps to stripe down stock?
Thanks!
Click to expand...
Click to collapse
Root using Magisk, then use something like link2SD to get rid of the bloat. I always freeze the unwanted Apps instead of deleting them.

ViVa[DOUD said:
;83039631]Hi! I tried most of them, PE+, HavocOS, AICP, LINEAGE, in my case the most stable and daily driver is Havoc OS, there is one problem on all of them for me, my banking app wont run on modded rom's so i reverted to miui, android one.
There is trial and error, some might work from start, some are harder to make them run ok, without any crashes. The fastest one i found was Pixel Experience+, the most stable one, Lineage OS(be carefull, it doesnt support google apps from the box), and the one which does any task well, good battery and stability in my case, was Havoc OS. With pleasure, ViVa.
Click to expand...
Click to collapse
can u tell me which version of havoc os u used was the most stable. thanks for ur answer

tohaxon said:
which is the best and most stable rom for MI A2. By stable i mean for day to day use and obviously bug free rom.
Thanks in advance
Click to expand...
Click to collapse
PixelExperience FAN EDITION is good its smooth but stilll there a few bugs btw PixelExperience unoffical is awsm its so smooth u can check it here https://mega.nz/folder/bZgRAAbA#AdWBnHBuAxkt4NHyvcdGoQ

Only Havoc OS. [emoji6]
Sent from my Mi A2 using Tapatalk

AICP for me.