Database Users

[DEV-ONLY][Z1-Z3][3.10 kernel][MSM8974/SD800-1] Custom ROM development

Hello,
this thread is only for development discussion regarding development of android for msm8974. If you have anything useful, it's the right place, however, it's not for non-dev things.
Current state of cam:
working, though, still low quality. Will be fixed on v6. (and no videocam)
if you wanna have live chat, you can join an IRC
http://webchat.freenode.net/?channels=#freexperia

placeholder

Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom, its just an aosp camera hal which is compiled by sony rom compilation! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove camera.msm8974.so from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so (which is not wrapper I think, its sony special camera hal), I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm!

So now i will explain all a little bit more
It is possible to get 3.4 kernel booting and working but the problem are the camera blobs for 3.4 too
All cam blobs above 4.4.4 can not used because they need drm keys but if you unlock your bootloader you will lose them
We have disscued this with all old cm maintainer and aosp devs including me as i'm one of the aosp devs
Booting 3.4 should need some hal changes in display and audio and the stock kernel need a lot of patches to get it boot on nougat
So in general 3.4 will work but we should focus on 3.10 its more efficend and if you see the progress over the last year we have done something which has no other manufacture. I fully understand all off you but we want to continue support of our devices for a long time and this is definitly easier on 3.10.
I know that sony will keep msm8974 as long as possible in the open device programm but it will end in some time because qcom discontinued the ardeno support which make it harder for all of us. I will give my best to bring msm8974 on 3.10 stable as a rock and hopefully with cam
So keep it up and help to fix the things
If you need some help or some more infos you can write me via pm or hangouts

munjeni said:
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove that file from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so which is not wrapper as a tomascus say, I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm
Click to expand...
Click to collapse
huh? isn't that camera.qcom.so too small to be hal? (sorry, still no device...)

munjeni said:
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove that file from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so which is not wrapper as a tomascus say, I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm
Click to expand...
Click to collapse
Stock uses camera. msm8974.so but it checks if drm vertity is present but we can nor rewrite the whole l drm verity on 3.4 because its closed source

SuperLamic said:
huh? isn't that camera.qcom.so too small to be hal? (sorry, still no device...)
Click to expand...
Click to collapse
I don't know but I will try in next few days when I get more free time for installing sotck rom

rcstar6696 said:
So now i will explain all a little bit more
It is possible to get 3.4 kernel booting and working but the problem are the camera blobs for 3.4 too
All cam blobs above 4.4.4 can not used because they need drm keys but if you unlock your bootloader you will lose them
We have disscued this with all old cm maintainer and aosp devs including me as i'm one of the aosp devs
Click to expand...
Click to collapse
Thats bul****! When you unlock bootloader on stock rom you still have working camera!!! WTH drm keys!
rcstar6696 said:
Booting 3.4 should need some hal changes in display and audio and the stock kernel need a lot of patches to get it boot on nougat
Click to expand...
Click to collapse
That allso is not true! Only selinux and mmap proc tunable for mmap_base ASLR is need to get it boot on nougat! For more info here you can see kernel which boots on nougat, see commits for more info! https://github.com/munjeni/android_kernel_sony_msm/commits/master
Please don't post misinformation if you are not 100% sure!

munjeni said:
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom, its just an aosp camera hal which is compiled by sony rom compilation! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove camera.msm8974.so from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so (which is not wrapper I think, its sony special camera hal), I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm!
Click to expand...
Click to collapse
Camera.msm8974 is an useless lib on stock rom
Camera.qcom is Sony camera hal.
I had found out it few months ago.

munjeni said:
Thats bul****! When you unlock bootloader on stock rom you still have working camera!!! WTH drm keys!
That allso is not true! Only selinux and mmap proc tunable for mmap_base ASLR is need to get it boot on nougat! For more info here you can see kernel which boots on nougat, see commits for more info! https://github.com/munjeni/android_kernel_sony_msm/commits/master
Please don't post misinformation if you are not 100% sure!
Click to expand...
Click to collapse
If you read it again you will see that i talk about drm verity not drm keys
Test it if you want we had cm13 booting on 3.4 and it was only possible with display patches audio patches where only needed to fix some small sound issues
Chirayu desai one of the cm maintainer can confirm this.
Selinux is correct this needs to be rewritten and mmap too but i wanted to write it understandable for all guys not only for devs
The other thing about the camera hal is an info from alin but if you say he isnt correct then you will be right :good:
It could be possible that the cam will start without but not with all Features
Do what you want but i'm quite sure that you don't get a fully working cam

rcstar6696 said:
If you read it again you will see that i talk about drm verity not drm keys
Click to expand...
Click to collapse
I don't know which device you have but I speak about Honami and Amami only. On Honami and Amami unlocking bootloader have nothing to do with camera, only some small changes in picture quality can be noticed. I will definitelly go to 3.10 kernel till after camera gets working

mkdmc said:
Camera.msm8974 is an useless lib on stock rom
Camera.qcom is Sony camera hal.
I had found out it few months ago.
Click to expand...
Click to collapse
Thats what I thinking now too! Did you tested, whats happening when camera.msm8974.so gets removed, is camera working? I need confirmation on rom 4.6.1.A.236 ! Which I found camera.qcom.so uses chocobal and excal blobs, camera.msm8974.so uses nothing from that.

rcstar6696 said:
Stock uses camera. msm8974.so but it checks if drm vertity is present but we can nor rewrite the whole l drm verity on 3.4 because its closed source
Click to expand...
Click to collapse
Did you try to grep that file? For example
strings camera.msm8974.so | grep drm
You can see null results about drm

rcstar6696 said:
So now i will explain all a little bit more
It is possible to get 3.4 kernel booting and working but the problem are the camera blobs for 3.4 too
All cam blobs above 4.4.4 can not used because they need drm keys but if you unlock your bootloader you will lose them
We have disscued this with all old cm maintainer and aosp devs including me as i'm one of the aosp devs
Booting 3.4 should need some hal changes in display and audio and the stock kernel need a lot of patches to get it boot on nougat
So in general 3.4 will work but we should focus on 3.10 its more efficend and if you see the progress over the last year we have done something which has no other manufacture. I fully understand all off you but we want to continue support of our devices for a long time and this is definitly easier on 3.10.
I know that sony will keep msm8974 as long as possible in the open device programm but it will end in some time because qcom discontinued the ardeno support which make it harder for all of us. I will give my best to bring msm8974 on 3.10 stable as a rock and hopefully with cam
So keep it up and help to fix the things
If you need some help or some more infos you can write me via pm or hangouts
Click to expand...
Click to collapse
Hi
thanks for your reply. First, excuse me if i miss some point or if i'm not accurate: im new to this world. I learn cm with my z3, running my first 'mka bacon', around 1 year ago. I read a lot (xda, aosp doc, an listen the experimented devs). I agree with you that running a 3.4 kernel on aosp will be hard as it need a lot of changes but, for cm, switching to caf HAL variant need only a few variables changes. Now i am able to boot cm-13.0 and cm-14.0 on z3 without changing the build tree and this cm-13.0 is now used at daily usage.
Obliviously it doesn't change anything to camera facts.
About the 3.10 kernel, the officials cm maintainers insists a lot that i work with it but after we got a "won't fix" on the screen flickering issue it reveal the problem was a panel driver init missing, i try to fix but it is out of my knowledge, so i decide to drop the 3.10 kernel definitively as it will remain unusable for z3/z3c.
I totally get the idea of only one kernel for all devices and really agree with that. If, one day, this screen flickering issue get fixed, i will be glad to give another try and will contribute as much as i can. But for now users have an upgraded rom, almost working, with recent security patches.
About the camera, i doubt it is related to TA partition.
I just made a test with:
z3 stock .575 locked bootloader
z3 stock .200 unlocked bootloader
z3 cm-12.1
Camera on both stock z3 are working the same way.
I need to make the same test with both stock device on the same rom version now.

munjeni said:
I don't know which device you have but I speak about Honami and Amami only. On Honami and Amami unlocking bootloader have nothing to do with camera, only some small changes in picture quality
Click to expand...
Click to collapse
Drm verity are not the same as drm keys the keys are needed to get some Algorithmen to work. So this explains your lose of qualiy but drm verity is a protection to protect data and libs. On stock you have a implimenation that verfiy the loading of the carefull data and drm will be okay but these implimenation is closed source and needs to be e rewritten and this is nearly impossible because no other devices has this in a so extremly way then the sony devices
You can look into hammerhead source and you see some commits about drm verity too but hammerheads cam libs are not included in the verity
I have castor and sirius
---------- Post added at 10:00 PM ---------- Previous post was at 09:55 PM ----------
nailyk said:
Hi
thanks for your reply. First, excuse me if i miss some point or if i'm not accurate: im new to this world. I learn cm with my z3, running my first 'mka bacon', around 1 year ago. I read a lot (xda, aosp doc, an listen the experimented devs). I agree with you that running a 3.4 kernel on aosp will be hard as it need a lot of changes but, for cm, switching to caf HAL variant need only a few variables changes. Now i am able to boot cm-13.0 and cm-14.0 on z3 without changing the build tree and this cm-13.0 is now used at daily usage.
Obliviously it doesn't change anything to camera facts.
About the 3.10 kernel, the officials cm maintainers insists a lot that i work with it but after we got a "won't fix" on the screen flickering issue it reveal the problem was a panel driver init missing, i try to fix but it is out of my knowledge, so i decide to drop the 3.10 kernel definitively as it will remain unusable for z3/z3c.
I totally get the idea of only one kernel for all devices and really agree with that. If, one day, this screen flickering issue get fixed, i will be glad to give another try and will contribute as much as i can. But for now users have an upgraded rom, almost working, with recent security patches.
About the camera, i doubt it is related to TA partition.
I just made a test with:
z3 stock .575 locked bootloader
z3 stock .200 unlocked bootloader
z3 cm-12.1
Camera on both stock z3 are working the same way.
I need to make the same test with both stock device on the same rom version now.
Click to expand...
Click to collapse
Hey yes i was only talking about stock not about thr cm kernel
When did you test 3.10 the last time all display issues are normally solved if you use 1.3.3 kernel base

rcstar6696 said:
Drm verity are not the same as drm keys the keys are needed to get some Algorithmen to work. So this explains your lose of qualiy but drm verity is a protection to protect data and libs. On stock you have a implimenation that verfiy the loading of the carefull data and drm will be okay but these implimenation is closed source and needs to be e rewritten and this is nearly impossible because no other devices has this in a so extremly way then the sony devices
Click to expand...
Click to collapse
Where you found that info? Any log about it?

munjeni said:
Where you found that info? Any log about it?
Click to expand...
Click to collapse
Ask alin Jerpelea or chirayu deasi all infos i give too you are from them
For drm verity just use google :/

nailyk said:
screen flickering issue[/URL] it reveal the problem was a panel driver init missing, i try to fix but it is out of my knowledge
Click to expand...
Click to collapse
I'm oticed frezings and some strange things using that msm8994 display hal, but on my buld I have used codeaurora LA.BR.1.3.6_rb1.3 branch for display, camera and some things in media, I can confirm that display things fly, its soo smoth, video soo smooth, screen power off/on smooth... if you want to try here is it http://munjeni.myiphost.com/mynougat.tar.gz , don't forget to build kernel with script buildkernel.sh since it will install kernel headers from 1.3.3 and will build 1.3.3. kernel too. I have told jerpelea about it but no reaply about LA.BR.1.3.6

rcstar6696 said:
Hey yes i was only talking about stock not about thr cm kernel
When did you test 3.10 the last time all display issues are normally solved if you use 1.3.3 kernel base
Click to expand...
Click to collapse
Really? My last try was with the LA.BF64.1.2.2_rb4.7 branch. Great i have some waiting patches for fm and nfc! Unfortunately i half broke my original screen which make screen flickering debugging harder. I will give a try asap. Thanks for the hint!

nailyk said:
Really? My last try was with the LA.BF64.1.2.2_rb4.7 branch. Great i have some waiting patches for fm and nfc! Unfortunately i half broke my original screen which make screen flickering debugging harder. I will give a try asap. Thanks for the hint!
Click to expand...
Click to collapse
Just use nougat and everything from sonyxperiadev instruction page, its kernel 1.3.3 which is very good, extract things from mynougat.rar to android tree, build kernel with script buildkernel.sh (you will need some path modification to it), and the rest like mentioned...

[ROM][7.1.1][LINEAGE] KryoRemix-Nougat[OPTIMIZED][SMOOTH][MORE!]

I can't help , but exclaim what a journey it has been ! It all started , when I was bent on rooting my Note 2 , and installing the S5 based ROM by team electron , at a time when TouchWiz was at its peak and I was 14 . I vividly remember that moment when it booted up , and I was really relieved ! I then went on to install RR , and was mesmerized by the smoothness and customizability . I thought to myself I will never be able to build a ROM from source like the devs do . But , when I got the Oneplus One a year and a half later , I had tried dozens of ROMs , based on CM , AOSP , and TW . I wanted to myself make a ROM from source , but didn't find any good guides , so I started trying to port ROMs as the guides were better for porting back then . Out of many failed ports , one came out to be real good , when I tried to port Skydragon ROM , and added lots of stuff from team Utopia's HTC app ports . I released the ROM in the start of 2016 , and frequently updated it , until I got busy with my studies . It was almost the start of April , when my 10th std. board exams were done away with , and I was bent on building ROMs from source . Then I saw @Aaahh 's post on the OnePlus forums , in which he had helped someone with ROM building . @Aaahh and @jgcaap were my favorite developers , and to learn development from someone like @Aaahh would be great I thought to myself . I then contacted him via Telegram , and we got to building ROMs within two weeks or so (I blame my internet speed for that ) . I will always be thankful to him .I then continued to release my first ROM , which was Hurricane-AICP , which was a highly acclaimed ROM for the opo . I then got to collaborate with @jgcaap , and I feel really lucky for that . I then got the Op3 in June , and continued my heavily optimized AICP builds for it too , under the name Kryo-AICP , paying homeage to the SD820 . I then again tried many ROMs after that , and saw RR to have drastically improved . I then decided to rebase my builds to RR , but I admit , it failed to hit the mark in the first shot , due to some bugs and rough edges . I now have them cleared out , and am capable of fixing bugs (finally) . I also have almost double the experience of ROM building by now , and without further waiting , let's get to the ROM itself !
Features :
All RR features !
GCC & Clang O3 (Optimized for speed ) !
Optimized Low-level code !
Polly on Clang !
Enabled Graphite and its identity transformation !
ODEXED for faster boot times and better performance !
More Optimizations and features coming soon !
INSTALLATION :
Download the latest build
Download Gapps
Take a nandroid backup
Recommended - Full wipe and factory reset
Flash ROM using latest TWRP Recovery
Flash Gapps
Reboot.
Enjoy!
UPDATE :
Download the latest build of Resurrection Remix ROM
Flash ROM
Wipe cache
Wipe dalvik cache
Reboot
Enjoy!
Download Stable ROM
Downloads :
ROM :
https://drive.google.com/file/d/0B3Gm6OPaAckxS3lablhGZFg1U1U/view?usp=drivesdk
Recommended GAPPS : http://opengapps.org
Credits :
@droidriz for being of great help in fixing the alert slider
@Joshua_B. for the bootanimation (coming soon) , and inspiring me , when builds were failing
@Taker18
@Naman Bhalla
AICP , for their fixed device trees
Source
https://github.com/RR-OnePlus3/rr_de...eplus_oneplus3
https://github.com/RR-OnePlus3/kernel_oneplus_msm8996
https://github.com/RR-OnePlus3/rr_pa..._apps_Settings
https://github.com/RR-OnePlus3/device_oppo_common
https://github.com/CyanogenMod/andro...e_qcom_display
https://github.com/CyanogenMod/propr...vendor_oneplus
https://github.com/CyanogenMod/andro...opensource_Nfc
https://github.com/CyanogenMod/andro...rce_frameworks
https://github.com/CyanogenMod/andro...rce_libnfc-nci
For more news , and insider info , join our Telegram (link soon!)
If you like my work , you can buy me a beer (though I'm 16 ?)
XDAevDB Information
Resurrection ROM, ROM for the OnePlus 3
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 7.1.x Nougat
Based On: CyanogenMod 14.1 , AICP
Version Information
Status: Stable
Current Stable Version: 5.8.0
Stable Release Date: 2017-1-4

Reserved

Reserved2

Thanks for the awesome Build

I'm all for performance, so if this is roughly a plain RR with "just" performance tweaks, well, I'd gladly check it out!

Call echo fixed? Like in matsaa's rom? Thanks for your work bro! Hope to see more ...
With great phones comes great ROMS!
Click to expand...
Click to collapse

Awesome rom keep up the good work Manav

Jole7 said:
Awesome rom keep up the good work Manav
Click to expand...
Click to collapse
Did you had chance to test it out already? My download is progressing slowly, but I'd be interested in your feedback.
Alert slider working? Echo issue? Feedback on performance / smoothness / stuttering?
Thanks!

Giocarro said:
Did you had chance to test it out already? My download is progressing slowly, but I'd be interested in your feedback.
Alert slider working? Echo issue? Feedback on performance / smoothness / stuttering?
Thanks!
Click to expand...
Click to collapse
Not yet but i tried Manav's tests builds and i can tell you performance and smoothness is insane and no bugs. I will try the rom for sure

shubhaemk said:
Call echo fixed? Like in matsaa's rom? Thanks for your work bro! Hope to see more ...
Click to expand...
Click to collapse
My question is the same. Could you help @Manav Bhagia please?
Many thanks for your work

What firmware is recommended for CM14.1?

liam_davenport said:
What firmware is recommended for CM14.1?
Click to expand...
Click to collapse
OpenBeta 7/9 should work fine.

OK, I installed this ROM with Open Gapps Nano and all is working well so far.
Started from scratch with a clean flash so I'm still setting things up.
One quick question: is there an option to force the volume panel to be always expanded by default? I remember this feature from some custom ROM in the past and really liked it.
Will keep posting my feedback along with the normal usage goes on.

1337jay said:
OpenBeta 7/9 should work fine.
Click to expand...
Click to collapse
Thanks bro :good:

Just found a little glitch: in Settings app the Gestures menu is listed ad "com.cyanogenmod.settings...." instead of "Gestures".
A second quick question: is there somewhere the possibility to choose the global accent color, or do we have to rely on themes when they'll be available?
Edit: one more: Settings > Additional buttons > Swap buttons get reset at each reboot.

Hey manav, thanks for the rom, it looks very promising. May I ask if you could look at unlink ring and notification tone? I realy miss it in RR N. The only Nougat rom that has it is AICP i think.
Thank you either way.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

OOS camera port not working on this ROM... It freezes at every photo taken. Need to exit and restart app...

Hey whats good mate? Glad to see what you have accomplished

Well, here is my impression after a full day using this ROM, started with a clean flash: performance are good (actually was really impressed from the speed of first boot) but to achieve a perfect stutter-free scrolling I had to set battery profile to "Performance".
Doesn't seem to use too much battery at the moment, will report back if anything changes.
I'd love to hear something from the builder about the questions raised yesterday.
Again, thanks a lot for this great ROM!

Giocarro said:
Well, here is my impression after a full day using this ROM, started with a clean flash: performance are good (actually was really impressed from the speed of first boot) but to achieve a perfect stutter-free scrolling I had to set battery profile to "Performance".
Doesn't seem to use too much battery at the moment, will report back if anything changes.
I'd love to hear something from the builder about the questions raised yesterday.
Again, thanks a lot for this great ROM!
Click to expand...
Click to collapse
There have been lots of changes on RR's side , so I'm gonna merge them and release a new build on Sunday or Monday . Lots of device tree improvements are there too , so don't judge the ROM by the first build itself

[ROM] [UNSTABLE] Pixel Experience 9.0 for Redmi 5 Rosy

0.Flash treble recovery.Get using (watch how to install treble recovery)
1.File comes compressed in .zip file format.Download and unpack using RAR on Play Store,you will get an IMG file
2.Flash Mokee 8.1
3.Flash vendor.IMG to vendor
4.Flash boot.IMG to boot
4.1 Reboot the phone and set it up
5.Flash the **Pixel Experience** GSI to system image
enjoy pixel experience.
Bugs:
Cam,
FP,
Infrared
To root:Magisk 16.7 will theoretically work
Credits and a lot of thanks :
Enes sastism for gsi
supdragonzj for Mokee ROM
@juananDev and supdragonzj for vendor.IMG and boot.IMG
@Sukrut4778 for Treble recovery
Links -
Mokee - https://mega.nz/#!6P5AFSAK!JprEHdSgVvw4SJ2xtouRS7Ri2GYY2TK6FA0aylS3W7E
Vendor IMG -
http://www.mediafire.com/file/z5phsw2gcsyelsg/vendor.img/file
Boot IMG -
http://www.mediafire.com/file/qqldpcy6cvbkh42/boot.img/file
Pixel Experience Gsi System Image -
http://goo.gl/dXDghg
(Link Updated)
Plz hit that thanks button!

Bro if i want restore TWRP (non-treeble) how can i do it once installed Treeble TWRP?

Hmm...
k4ppaj said:
Bro if i want restore TWRP (non-treeble) how can i do it once installed Treeble TWRP?
Click to expand...
Click to collapse
Hmmm.... So if u wanna restore ur original Twrp then just flash it using Fastboot flash command! That's it!

Thanks! I'll try it today

Can we use other fix for camera from another rom 9.0 rom for rosy

Im not sure
ConeSRB said:
Can we use other fix for camera from another rom 9.0 rom for rosy
Click to expand...
Click to collapse
I don't know man... But if u want then u can try... But it can be risky.. It can get stuck on bootloop.. U can try.

awesome thanks for the rom man, keep us updated when fp and camera are fixed on both android p roms ok?

can we flash oreo gsi using the same method?

Ok
driton.talinoci said:
awesome thanks for the rom man, keep us updated when fp and camera are fixed on both android p roms ok?
Click to expand...
Click to collapse
yeah sure! But did u flashed the rom?

Bro the GSI link doesn't work

Sorry.
k4ppaj said:
Bro the GSI link doesn't work
Click to expand...
Click to collapse
sorry about that. I will try to fix it asap

Done
k4ppaj said:
Bro the GSI link doesn't work
Click to expand...
Click to collapse
Bro link has been updated

YKP-8 said:
can we flash oreo gsi using the same method?
Click to expand...
Click to collapse
??

Good work!
Bro i finally installed this rom... Now i'm going to tell you pros and cons of this rom. Before starting I would like to tell you that I am Italian so my English is not the best.
Pros:
• Phone like pixel
• No need to install GApps
• Very simple installation
• You can root with Magisk 17.1
Cons:
• Fingerprint, infrared and cam doesn't working
• Adaptive brightness is a bit bugged
• Phone is VERY VERY HOT and this impact also on the battery
@AP hacker can you help me to fix temperature problem? Else i must reinstall MIUI :crying:
Pie is beautiful!

k4ppaj said:
Bro i finally installed this rom... Now i'm going to tell you pros and cons of this rom. Before starting I would like to tell you that I am Italian so my English is not the best.
Pros:
• Phone like pixel
• No need to install GApps
• Very simple installation
• You can root with Magisk 17.1
Cons:
• Fingerprint, infrared and cam doesn't working
• Adaptive brightness is a bit bugged
• Phone is VERY VERY HOT and this impact also on the battery
@AP hacker can you help me to fix temperature problem? Else i must reinstall MIUI :crying:
Pie is beautiful!
Click to expand...
Click to collapse
Hell yeah pie is beautiful, but I didn't face heating issue... After I flashed it I used it for 30mins... Till that my phone was warm but not hot. I immediately flashed other stable ROM after seeing all the features. Developers are working and they will release stable version soon just wait.. @ND watch

k4ppaj said:
Bro i finally installed this rom... Now i'm going to tell you pros and cons of this rom. Before starting I would like to tell you that I am Italian so my English is not the best.
Pros:
• Phone like pixel
• No need to install GApps
• Very simple installation
• You can root with Magisk 17.1
Cons:
• Fingerprint, infrared and cam doesn't working
• Adaptive brightness is a bit bugged
• Phone is VERY VERY HOT and this impact also on the battery
@AP hacker can you help me to fix temperature problem? Else i must reinstall MIUI :crying:
Pie is beautiful!
Click to expand...
Click to collapse
Hell yeah pie is beautiful, but I didn't face heating issue... After I flashed it I used it for 30mins... Till that my phone was warm but not hot. I immediately flashed other stable ROM after seeing all the features. Developers are working and they will release stable version soon just wait.. @ND watch

k4ppaj said:
Bro i finally installed this rom... Now i'm going to tell you pros and cons of this rom. Before starting I would like to tell you that I am Italian so my English is not the best.
Pros:
• Phone like pixel
• No need to install GApps
• Very simple installation
• You can root with Magisk 17.1
Cons:
• Fingerprint, infrared and cam doesn't working
• Adaptive brightness is a bit bugged
• Phone is VERY VERY HOT and this impact also on the battery
@AP hacker can you help me to fix temperature problem? Else i must reinstall MIUI :crying:
Pie is beautiful!
Click to expand...
Click to collapse
Hell yeah pie is beautiful, but I didn't face heating issue... After I flashed it I used it for 30mins... Till that my phone was warm but not hot. I immediately flashed other stable ROM after seeing all the features. Developers are working and they will release stable version soon just wait.. @ND watch

Ok bro after few hours heating issues are fixed @AP hacker would you mind telling me what stable rom do you use? And you know who is developer of this rom?

Yeah!
k4ppaj said:
Ok bro after few hours heating issues are fixed @AP hacker would you mind telling me what stable rom do you use? And you know who is developer of this rom?
Click to expand...
Click to collapse
bro I actually use viperos 7.1.2 its stable and! There are multiple developers of that ROM... So it would be difficult for me to mention them all!

AP hacker said:
bro I actually use viperos 7.1.2 its stable and! There are multiple developers of that ROM... So it would be difficult for me to mention them all!
Click to expand...
Click to collapse
Thanks probably i use MIUI 10 until stable Pie ROM is released

SM-N981U/U1/W ROM

Disclaimer:​​Your warranty is now void.​​I am not responsible if you use this and brick your device or if your device blows up, implodes. Follow the instructions and you should be good.​​This is stock ROM with modifications. I do not own this device any issues let me know.​​You must have an Unlocked Boot loader. This is only for SM-N981U, SM-N981U1 should work on SM-N981W.​​ALWAYS BACKUP YOU’RE DATA BEFORE FLASHING.​Instructions:​• Download the zip file.​• Put the ROM.tar in AP slot with Odin.​• Reboot​• Wipe data​• Enjoy!​• Any Issues let me know!​​ROM FEATURES:​Rom removed request this Thread to be closed.​​Mod Edit: TG link remove.​​To get your phone unlocked see this thread or contact @afaneh92 for boot loader unlock or Click Here >> Unlock​​TWRP Included Thanks to @afaneh92​​Donations are not required but are encouraging, If want to support my work just click Here​

Request this Thread to be closed.

Reserved

Oh thankswill try asap.
Nope, i'm on 981B

bklyn_syed said:
Disclaimer:
Your warranty is now void.
I am not responsible if you use this and brick your device or if your device blows up, implodes. Follow the instructions and you should be good.
This is stock ROM with modifications. I do not own this device any issues let me know.
You must have an Unlocked Boot loader. This is only for SM-N981U, SM-N981U1 should work on SM-N981W.
ALWAYS BACKUP YOU’RE DATA BEFORE FLASHING.
Instructions:
• Download the zip file.
• Put the ROM.tar in AP slot with Odin.
• Reboot
• Wipe data
• Enjoy!
• Any Issues let me know!
ROM FEATURES:
- Force Encryption off
- Safetynet-fix from kdrag0n included in ROM just enable MagiskHide
- ViPER4AndroidFX included just install drivers.
- Heavily Debloated
- Bluetooth, Screenshare and Shealth working.
- Disable shutter sound menu
- AppLock Protection menu
- Support RealTime Network Speed
- Enable Camera during call
- Voicecall recording
- Data usage view on quick panel
- Block call number menu
Telegram BKLYNROM
To get your phone unlocked see this thread or contact @afaneh92 for boot loader unlock or Click Here >> Unlock
TWRP Included Thanks to @afaneh92
Donations are not required but are encouraging, If want to support my work just click Here
Click to expand...
Click to collapse
bklyn_syed said:
Disclaimer:
Your warranty is now void.
I am not responsible if you use this and brick your device or if your device blows up, implodes. Follow the instructions and you should be good.
This is stock ROM with modifications. I do not own this device any issues let me know.
You must have an Unlocked Boot loader. This is only for SM-N981U, SM-N981U1 should work on SM-N981W.
ALWAYS BACKUP YOU’RE DATA BEFORE FLASHING.
Instructions:
• Download the zip file.
• Put the ROM.tar in AP slot with Odin.
• Reboot
• Wipe data
• Enjoy!
• Any Issues let me know!
ROM FEATURES:
- Force Encryption off
- Safetynet-fix from kdrag0n included in ROM just enable MagiskHide
- ViPER4AndroidFX included just install drivers.
- Heavily Debloated
- Bluetooth, Screenshare and Shealth working.
- Disable shutter sound menu
- AppLock Protection menu
- Support RealTime Network Speed
- Enable Camera during call
- Voicecall recording
- Data usage view on quick panel
- Block call number menu
Telegram BKLYNROM
To get your phone unlocked see this thread or contact @afaneh92 for boot loader unlock or Click Here >> Unlock
TWRP Included Thanks to @afaneh92
Donations are not required but are encouraging, If want to support my work just click Here
Click to expand...
Click to collapse
Thank you sir. I've been unlocked since before christmas and this is first custom rom installed (though i had a lot of these mods done just individually). i'm doing one for android 10 (first custom rom) just because for whatever reason a lot of patching seems to more consistent than on 11, at least for my methods and knowledge. that boot animation though..... bad ass. anyway you would share how you pulled that off? i've been banging my head against the wall for 2 months on that. Regardless, thank you so much, awesome to see the note 20 5g getting some love!! shout outs to @afaneh92 and @jrkruse for all the help on everything else.

kernal_root said:
Thank you sir. I've been unlocked since before christmas and this is first custom rom installed (though i had a lot of these mods done just individually). i'm doing one for android 10 (first custom rom) just because for whatever reason a lot of patching seems to more consistent than on 11, at least for my methods and knowledge. that boot animation though..... bad ass. anyway you would share how you pulled that off? i've been banging my head against the wall for 2 months on that. Regardless, thank you so much, awesome to see the note 20 5g getting some love!! shout outs to @afaneh92 and @jrkruse for all the help on everything else.
Click to expand...
Click to collapse
Actually I am working on V2.0 I was in accident so I should be done soon so it will have alot of features that will match with other roms
I used superr kitchen to edit super.img and csc files. To add mods to a rom you need to edit framework.apk and systemui.apk along with create apk that can control the mods, which I have released for other devices.
On android 10 its different file that patches the safety net. Other features like call recording and stuff can be added with csc

bklyn_syed said:
Actually I am working on V2.0 I was in accident so I should be done soon so it will have alot of features that will match with other roms
I used superr kitchen to edit super.img and csc files. To add mods to a rom you need to edit framework.apk and systemui.apk along with create apk that can control the mods, which I have released for other devices.
On android 10 its different file that patches the safety net. Other features like call recording and stuff can be added with csc
Click to expand...
Click to collapse
well first off, thank you again! secondly, i hope you are recovering well from your accident. also i will be looking forward to your 2.0 release. and thanks to @afaneh92 i have safetynet patches for 10 and 11 ( and someone has a fix on here for a more recent 11 update that fixes it).
one more question for clarity if you dont mind. is it possible for me to add your boot animation to android 10?

kernal_root said:
well first off, thank you again! secondly, i hope you are recovering well from your accident. also i will be looking forward to your 2.0 release. and thanks to @afaneh92 i have safetynet patches for 10 and 11 ( and someone has a fix on here for a more recent 11 update that fixes it).
one more question for clarity if you dont mind. is it possible for me to add your boot animation to android 10?
Click to expand...
Click to collapse
Yes sure

Sorry man one more question, so di$ you add your boot animation to the systemUI or framework apks, or where is that located in Android 11 because I can't find it for anything. Sorry to bug man, I appreciate it though

kernal_root said:
Sorry man one more question, so di$ you add your boot animation to the systemUI or framework apks, or where is that located in Android 11 because I can't find it for anything. Sorry to bug man, I appreciate it though
Click to expand...
Click to collapse
Files are in system/media bootsamsung.qmg bootsamsungloop.qmg shutdown.qmg sound system/media/audio/ui PowerOn.ogg PoweOff.ogg

2.0 uploaded I did not test, let me know on telegram if there are any issues

bklyn_syed said:
2.0 uploaded I did not test, let me know on telegram if there are any issues
Click to expand...
Click to collapse
No issues on 2.0. It's a solid rom. The font changer is great and the boot animation is awesome!

trook said:
No issues on 2.0. It's a solid rom. The font changer is great and the boot animation is awesome!
Click to expand...
Click to collapse
Good

Hey man, you did a very good job with the rom. I have a note205G I would like to help you improving the firmware quality with mods and things like that. How can I help? Thank you very much for the rom. I will donate very soon

Petition to have the "Recognized Developer" rule apply for this ROM thread. As, this ROM is not stable, V4A does not work at all, Magisk cannot pass safety net. It is a liability, and should be removed.
Edit: OP admits they have not tested the 2.0 ROM. Rolling back to 1.0, after wiping data, did not allow completion of setup. Just reboots on both 1.0 and 2.0 at this point. No matter how many times either version is reinstalled.
OP, this is not your free experiment grounds to throw untested software out and have other users be guinea pigs. Remove the 2.0 ROM until you have tested it.

asrah said:
Petition to have the "Recognized Developer" rule apply for this ROM thread. As, this ROM is not stable, V4A does not work at all, Magisk cannot pass safety net. It is a liability, and should be removed.
Edit: OP admits they have not tested the 2.0 ROM. Rolling back to 1.0, after wiping data, did not allow completion of setup. Just reboots on both 1.0 and 2.0 at this point. No matter how many times either version is reinstalled.
OP, this is not your free experiment grounds to throw untested software out and have other users be guinea pigs. Remove the 2.0 ROM until you have tested it.
Click to expand...
Click to collapse
First of all this ROM was tested by 2 people as the OP clearly states that I do not own the device. If the ROM was downloaded 47 times without any issues until now. This ROM was based on same based as my other ROM SM-G988U and SM-G981U which alot of people are using without any issues.
People have been using this ROM for over a month without any issues. I was working on an update no reason to waist my time.
To make life easy for me and you I will request to have this Thread closed and move on.

Thread closed at OP request.

[ROM] dotOS v1.2 for SM-J210F [Android 7.1.2]

Hello everyone!
This is a dotOS port from the Galaxy J3 2016 (made by @lucas000br) to the J2 2016.
Working: ​
My (basic) testings all seemed to work quite well
Added features and patched bugs:​
Patched lock button in boot.img
Pre-rooted the ROM
Added FM-Radio from ViperOS (microG variant only)
Optimized features
Signature spoofing patched on microG variant
[See post #2 for further information]
Known problems:​
Gapps variant is laggy (nothing I can do - Google sucks)
Your J2 shows up as a J3 (it's a port that's why)
Download links and installation instructions can be found in post #2​
Credits:
Nanolx for Signature Spoofing
PixelBoot for base
lucas000br for modified base
Me for everything else
Obligatory Links:
Kernel Source: Github
Original Build (Abandoned by PixelBoot): XDA Developers (No source code)
Port of Port (by lucas000br): Thread seems to have disappeared?

Variant information (Which one is which?)​
GAPPS: This one has most of the stock Google apps (Drive, YouTube, etc) + GSF present. Recommend for most users. RAM usage 640mb on idle
microG: All Google apps have been replaced with FOSS software. Google Services Framework has been replaced with microG. Signature spoofing is also present. RAM usage 560mb on idle
DIY: Want to build your own ROM? This one's for you! Everything except the bare minimum has been stripped out, so that you can decide what to pick for your ROM. (For power users only).
Stock dotOS: The stock dotOS compiled by PixelBoot for J3 2016; with Wi-Fi, Bluetooth, Signature spoofing and Power Button patched. Most stable out of all. You will need to flash additional GAPPS to get Google Services. RAM Usage 500mb.
Download Links:​Stock dotOS (Recommended): MEGA
GAPPS: Oreo-Themed dotOS
microG: Oreo-Themed dotOS
DIY: Oreo-Themed dotOS
Installation Instructions:​[If you don't have TWRP, get an image and install it from here]
GAPPS:
Boot to TWRP
[Do make sure to backup your data]
Wipe Dalvik, Data, System, Cache
Flash the ROM
Reboot. Done!
microG:
Boot to TWRP
[Do make sure to backup your data]
Wipe Dalvik, Data, System, Cache
Flash the ROM
After rebooting, open microG settings.
Go to self-check and tick the check boxes that are unticked (that will initialize microG)
Go back, and enable Device Registration, Cloud Messaging and Device Attestation
Then go to Location backends, and configure the DejaVu and Nominatim backends.
Done!
DIY and Stock dotOS will be the same as GAPPS variant

Changelog:
v1.2: Initial release​06/05/2021: After lucas' comment, I realized that this wasn't the stock dotOS. So I have ported the stock dotOS created by PixelBoot. Try it out!​

lucas000br said:
well done!
Also, PixelBoot did the DotOs base rom, i just modified it to be more like Android Oreo
(dont worry because i credited PixelBoot in the original j3 thread)
Click to expand...
Click to collapse
oops I need to credit him
Thanks for informing!

good soon try it out

i have flashed stock rom provided by u of dot os but my phone stuck at samsung logo pls look into it .....i am sure i have flashed it n follow all steps correctly

Uniqueshiva said:
i have flashed stock rom provided by u of dot os but my phone stuck at samsung logo pls look into it .....i am sure i have flashed it n follow all steps correctly
Click to expand...
Click to collapse
okay I'll try flashing it again. wait

NullCode said:
okay I'll try flashing it again. wait
Click to expand...
Click to collapse
btw i don't have stock rom installed before i flash it......I am on viper os....then i boot to twrp wipe sytem cache data n flash your provided dot os stock rom then i reboot but stuck at Samsung logo

@Uniqueshiva thank you for the information. I had made a typo in the updater script that caused the boot image to fail.
Please download the new ROM and flash it. I've confirmed it to work

NullCode said:
@Uniqueshiva thank you for the information. I had made a typo in the updater script that caused the boot image to fail.
Please download the new ROM and flash it. I've confirmed it to work
Click to expand...
Click to collapse
thx for responding so fast btw i will try it tomorrow as my data got finished today sorry for it...i will surely give feedback
edit- I tried stock dos os rom n flash arm 7.1 Pico gapps...boot animation appears but after sometimes black-brown screen appears after 5 min phone started but its written setup wizard failed i am not able to go ahead as setup wizard failed written every time so i turn off the phone maybe it can be the gapps problem now i will try dot os magisk gapps version provided by u btw i am curious that what is DIY dot os u give is all bugs fixed in it just asking..

Uniqueshiva said:
thx for responding so fast btw i will try it tomorrow as my data got finished today sorry for it...i will surely give feedback
edit- I tried stock dos os rom n flash arm 7.1 Pico gapps...boot animation appears but after sometimes black-brown screen appears after 5 min phone started but its written setup wizard failed i am not able to go ahead as setup wizard failed written every time so i turn off the phone maybe it can be the gapps problem now i will try dot os magisk gapps version provided by u btw i am curious that what is DIY dot os u give is all bugs fixed in it just asking..
Click to expand...
Click to collapse
hmm it could be flashing gapps causes problem with the rom...
yes try the gapps version i provided
the diy one is mainly for rom porters. it has many features removed so that rom porters can think about what features to add in the rom
only basic feature available in rom is phone and messaging support

I can't access internal storage after flashing. Stock file manager crashes if i open it. Stock browser says "no sd card, usb storage is required to download the file". There's no internal storage even after connecting the phone to pc. It only shows memory card.
Edit: Just wiped the internal storage and re-flashed it. Works fine now
Thanks for porting this amazing rom

@NullCode, thanks for your work for device j210f...I like the ui of dot os..but i must say your previous build i.e viper os was more stable n amazing atleast for me....btw thanks a lot for keeping this device alive...

Dark theme not working in settings and other apps.Any help?

shayara said:
Dark theme not working in settings and other apps.Any help?
Click to expand...
Click to collapse
there's a theming option in settings > display > scroll to the end
from there figure out what to do (I've confirmed its working)

Uniqueshiva said:
@NullCode, thanks for your work for device j210f...I like the ui of dot os..but i must say your previous build i.e viper os was more stable n amazing atleast for me....btw thanks a lot for keeping this device alive...
Click to expand...
Click to collapse
I know, viperOS was much more stable because I took 1 entire year to port and test the rom (i started testing January 2020 )
however, dotOS was ported in only 1 month
so it is not as polished
but im glad you liked it

NullCode said:
Hello everyone!
This is a dotOS port from the Galaxy J3 2016 (made by @lucas000br) to the J2 2016.
Working: ​
My (basic) testings all seemed to work quite well
Added features and patched bugs:​
Patched lock button in boot.img
Pre-rooted the ROM
Added FM-Radio from ViperOS (microG variant only)
Optimized features
Signature spoofing patched on microG variant
[New] 2 more ROM options to choose from (with varying features)
[See post #2 for further information]
Known problems:​
Gapps variant is laggy (nothing I can do - Google sucks)
Your J2 shows up as a J3 (it's a port that's why)
Download links and installation instructions can be found in post #2​
Credits:
Nanolx for Signature Spoofing
PixelBoot for base
lucas000br for modified base
Me for everything else
Note: You might've noticed how I didn't put [PORT] in the thread title. It is mainly because this ROM varies from J3's dotOS so much, I don't think it is fair to call this one a port.
Click to expand...
Click to collapse
Hey.
I am using this ROM since 6th May (stock variant) and it is very great but has lots of bugs.
1. Bluetooth Audio stutters really bad (problem in every Android N rom for this phone)
2. Google Meet doesn't work (just shows the logo and then crashes) I am using Open GAPPS
3. Many system app crash randomly (sometimes even the launcher and system ui) requiring me to take out the battery and restarting the phone.
4. Camera quality is significantly bad compared to stock 6.0
But still a great project.
Thank you for keeping this phone updated.

NullCode said:
there's a theming option in settings > display > scroll to the end
from there figure out what to do (I've confirmed its working)
Click to expand...
Click to collapse
Okay.Thnx.

NullCode said:
I know, viperOS was much more stable because I took 1 entire year to port and test the rom (i started testing January 2020 )
however, dotOS was ported in only 1 month
so it is not as polished
but im glad you liked it
Click to expand...
Click to collapse
Omg 1 year......that's y it feels so smooth in viper os i get nearly 900 mb free ram with gapps again thanks for your hardwork.....I know that u may be bored now for working on j210f that is old device but still hoping for more

Uniqueshiva said:
Omg 1 year......that's y it feels so smooth in viper os i get nearly 900 mb free ram with gapps again thanks for your hardwork.....I know that u may be bored now for working on j210f that is old device but still hoping for more
Click to expand...
Click to collapse
My build has more free ram and battery btw.