The flashable zip contains SnapdragonCamera.apk and needed libs. Both - the apk and the libs have to reside inside system, so the only way to install this system app is either flashing this zip, or to unpack the zip, remount /system rw (root required), copy the files by hand (root and writeble /system required), fix fs permissions (root and writeble /system required), remount /system ro (root required) and reboot.
I'm no photographer, so judging the pic quality and checking all that settings is up to you. Taking pictures, taking panorama shots, 4k video w/o and 1080p with stabilization is tested and working on oos4; since the codebase is M I'm pretty sure it's working on oos3 as well.
If you like to use a Magisk module instead of this flashable zip, you'll find it https://forum.xda-developers.com/oneplus-3t/themes/magisk-magisk-modules-oneplus-3t-t3548446 (many thanx to @Spasticdroid)
The version string I include in the filenames, refers to caf versions, not to android version, nor oos version: https://wiki.codeaurora.org/xwiki/bin/QAEP/release. At the moment I build inside oss source tree (see url at the end of the posting) - which is ahead with oos-3.5.4, guessing frommthe commits.
I consider you are on oos3 or oos4 and twrp is installed and working.
Installation:
boot to twrp
flash SnapdragonCamera[version].zip
reboot to system
go to Settings->Apps and find SnapdragonCamera
go to permissions and allow (at least) camera, storage and mic (I don't want to location tag my pics, so I leave location disabled; I'dont know why SnapdragonCamera wants to read my contacts, so I leave this disabled as well - for both YMMV)
Uninstall:
boot to twrp
flash uninstall-SnapdragonCamera[version].zip
reboot to system
IMPORTANT: the uninstall-SnapdragonCamera-[version].zip has to match EXACTLY! the version of the zip you have installed before, since different versions carry different files!
Source code and license:
https://source.codeaurora.org/quic/la/platform/packages/apps/SnapdragonCamera/
https://github.com/OnePlusOSS
Happy flashing!
Note: The old SnapdragonCamera-OSS.zip is exactly the same as SnapdragonCamera-LA.HB.1.3.2-27300-8x96.0.zip! I've decided to put the caf version string in the filename, to match the uninstall names, because different versions seems to need different libs.
Really nice job man! I will test this when my phone comes in! Thanks for the share and your work put into this!
It's working on 3.5.4, thanks! Only one problem I noticed: the continuous shot doesn't work, when I press the shutter button longer, the app quits. And it feels so bad seeing the 240hfr function, when the camera sensor doesn't support it
Doesn't work in 4.0.1. Thanks anyway.
Hammerhand.17 said:
Doesn't work in 4.0.1. Thanks anyway.
Click to expand...
Click to collapse
it is working. you have to give the right app permissions (camera, storage) then it will work. without the permissions it will fc.
Got really excited when I saw 240fps recording only to get "not supported for selected resolution" (even in 480p)... This phone is 100% capable of recording 240fps why won't oneplus add this in...
I'm no video or photo profi, so let me ask some noob question just to better understand this topic:
1080p is standrad 1920x1080 pixels at 50 fps non interlaced, isn't it? hfr240 (supported by our hardware/blobs or not doesnt matter for my question) means a high frame rate of 240fps, doesn't it? If the selected standard defines 50fps, but you request 240fps; isn't the error message "hfr is not supported on selected mode" absolutly true? The error is that hfr is selectable at all for *p standard modes, isn't it?
If this is very stupid, please be patient - I'm one of these guys using the mobile as camera really rarely, and when I use it,mI draw a circle, point at my object and tab... ...call me "fire and forget"-photographer...
So, it will only work on oos and not on cm, lineage etc?
ye would be interesting if it works on 7.1 lineageos?
@nvertigo67 would you mind sharing your build? I'm interested to check it out
Thanks
Notor1ouS- said:
ye would be interesting if it works on 7.1 lineageos?
Click to expand...
Click to collapse
Again: I don't now. I havn't started building lo-14.1, since I wait till oneplus has published oss4 keenelsources, to use N blobs. I hate shimmingm- but that's my personal problem.
But: just test it. if it doesn't work or you don't like it, just dirty flash the same lo version and you are done.
I have ask in @koenkk's lomthread to give it amtry, but havn't received (or not seen) any feedback. I guess it should work as good or as bad as on oos.
t-shock said:
@nvertigo67 would you mind sharing your build? I'm interested to check it out
Thanks
Click to expand...
Click to collapse
Sadly I have no oos build - what I have done is building oss. I used plain source. I only changed fstab to include f2fs for data, and increased dmesg size in the kernel sources. The build is boring - really. But if you really, really want it, I'll upload it (1Mbit uplink; 15€ for 3GB; build is 450MB). Don't want to offend you, with asking, just want to be sure.
nvertigo67 said:
Sadly I have no oos build - what I have done is building oss. I used plain source. I only changed fstab to include f2fs for data, and increased dmesg size in the kernel sources. The build is boring - really. But if you really, really want it, I'll upload it (1Mbit uplink; 15€ for 3GB; build is 450MB). Don't want to offend you, with asking, just want to be sure.
Click to expand...
Click to collapse
I meant OSS (typo).
So do you want a donation to upload it?
t-shock said:
I meant OSS (typo).
So do you want a donation to upload it?
Click to expand...
Click to collapse
No, I just want to be sure. I'll make a at rsync job for tonight - if the upload succeds, you find a pm tomorrow morning.
snapdragon camere cannot full screen. how to fix it ?
paratox said:
it is working. you have to give the right app permissions (camera, storage) then it will work. without the permissions it will fc.
Click to expand...
Click to collapse
plz mention the right permissions?
bitf03m030 said:
plz mention the right permissions?
Click to expand...
Click to collapse
Read op: at least camera, mic and storage.
nvertigo67 said:
Read op: at least camera, mic and storage.
Click to expand...
Click to collapse
i have given these permissions, but yet it is fc.
brmbjn said:
snapdragon camere cannot full screen. how to fix it ?
Click to expand...
Click to collapse
Since android runs all apps in fullscreen mode (if not rum in multi win mode), I'm guessing you are talkking about preview view: preview shows you the picture you will get, if taking the pic/video. If you go for 16MP, you have selected a mode with 4:3 aspect ratio. If you want to show 4:3 on a 16:9 screen, you have black borders - if you need a preview wirhout borders, select a mode, that has 16:9 aspect ratio.
bitf03m030 said:
i have given these permissions, but yet it is fc.
Click to expand...
Click to collapse
Logs please.
Related
Please read this carefully :
- BASE ROM by Kibuuka AOSP ICS 4.0.4
- PORT ROM from Mazda Team Dirt PARANOIDANDROID v0.2.1 for Supersonic aka HTC Evo 4G and Xylograph ParanoidAndroid for HD2
All the Credit and Donate go to :
1. Mazda [Team Dirt] (http://forum.xda-developers.com/showthread.php?t=1714415)
2. Molesarecoming aka PARANOIDANDROID (http://forum.xda-developers.com/showthread.php?t=1717079)
3. Xylograph
3. Kibuuka (you know where to find him)
4. Nop (you know where to find him)
5. TheManii (you know where to find him)
Please do me a favour, hit the THANKS button at least for above name list.
As usually, I take no credit at all for this rom because this is not my work, I'm not build this from the source, all I do is take the 2 rom, combine it, then try to make it boot on my device.
The rom from Mazda was made for running on HTC Supersonic, if running on DS5 sure it will have much problem and bugs.
All I can do just fix as much as I can, I'm not have experience in build rom, so do not expect too much on this rom.
I just want to share, not intend anything by making this, just have fun and feel excited when others ICS rom can running on my old device.
So lets have fun.
Not work
camera
Temporary work
wifi tether (use barnacle wifi tether from playstore)
headphone (use toggle headset2 from playstore, thanks to machbe 1984)
How to
Nandroid back up before flash.
Wipe cache and dalvik cache, factory reset from streakmod recovery
Flash rom
Factory reset from dell recovery
Be patience, phone need longer time to boot up, if it stuck on boot animation, press and hold power button untill phone shutdown and reboot again. This time will boot up.
Download link
http://www.mediafire.com/download/7eq27tblav0qdjt/ParanoidAndroid_Streak.zip
How to have tablet ui
HOW TO MAKE ANY ICS ROM HAVE TABLET UI
Thanks to Veisen for his awesome work, you can follow his thread
http://forum.xda-developers.com/showthread.php?t=1767955
Tools
- Winrar or 7zip
- dex2jar
- hex workshop
- services.jar from ICS rom
How to
- extract services.jar from ICS rom (system/framework)
- use winrar to extract classes.dex from services.jar
- use dex2jar to compile classes.dex [ d2j-dex2jar classes.dex ]
- the result "classes_dex2jar.jar", use winrar to open and extract WindowManagerService.class form classes_dex2jar.jar\com\android\server\wm
- open WindowsManagerService.class in hex workshop, choose replace icon from menu bar, fill the pop up with
Find : 8E0009000A000000821B9900781D36061C36072A2A2A2A1506
Replace : 930009000A000000871B99007D1D36061C36072A2A2A2A1506 8617046E8B
click ok, then choose replace all, after that choose replace icon from menu bar again, fill the pop up with
Find : B11C36061D3607A7FF8B
Replace : B11C36061D3607A7FF86
click ok, then choose replace all
- save WindowManagerService.class
- replace WindowManagerService.class by winrar in classes_dex2jar.jar without compression
- use jar2dex and create new dex file [ d2j-jar2dex classes-dex2jar.jar ]
- rename it to classes.dex
- use 7zip to replace your classes.dex in services.jar
- copy the mod service.jar back to your rom or phone
- in build.prop change density to 128 and reboot.
Now you have tablet phone
I have tested it and the result are
- dpi 128 [phone not work, data and wifi work well]
- dpi 240 [everythings work well]
Feel free to try use other phone.apk and post the result here.
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
Try use streakmod?
Sent from my Dell Streak using Tapatalk 2
Anybody success flash it ? I'm afraid there is bad upload.
Sent from my PC36100 using Tapatalk 2
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
i have flashed it successfully by both StreakMod 0.3.2.8 and ClockworkMod 5.0.2.7
it has some interesting changes
i hope it will be better and better (such as camera and languages)
Yep, was able to flash it too. Preferred the CM9 ROM though! To each his own, I guess!
i always thought that this rom is nice... and ... it is nice..
My friend not believe that my old device can run paranoid android, same like his galaxy note untill I show him. He always laugh at me, said my ds5 is old enough and I should replace it with something new. Ha....this time I beat him
Sent from my PC36100 using Tapatalk 2
nom051205 said:
My friend not believe that my old device can run paranoid android, same like his galaxy note untill I show him. He always laugh at me, said my ds5 is old enough and I should replace it with something new. Ha....this time I beat him
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
streak 5 maybe old but it is still competitive hardware... and its large screen always beat others ( <5inch of course)
though i find it nowadays large screen is standard among south koreans...
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
Unless OP silently updated, I cannot confirm this.
What I mean is that it installed fine for me with CWM 6.0, though the way it mounts isnt the preferred way long term.
If anything it shouldnt be compatable with streakmod as it's using the newer format/mount syntax (it's rather complicated in how recoveries read the update scripts).
GApps is also included in it, perhaps you should remove it and point users to a Gapps package, either mine or the 'official' CM one.
ParanoidAndroid is a source based rom isnt it?
We do (preferrably) need a source port instead of a hackport as the rom still thinks it's an EVO
Perhaps when Kibuuka gets AOSP more closer to working 100%, we'll have more people building from source instead of hackports.
Unlike the S7/S10 CM9 ports (and this port of paranoidandroid), all the ICS based ones are currently hackports.
The S5 is terribly slow compared to the S7, it has the ram and nand space to run the newest roms, but the cpu is simply overwhelmed by new apps/stuff.
It's still plenty usable, but 1st gen snapdragons simply cant compare to 3rd/4th gen snapdragons (and their equivilent Exynos/Tegra chips).
It doesnt make it useless though, I still use my S5 ocasionally even though my S7 is pretty much better in every way (except size)
Edit: after reviewing this rom with Quadrant, it seems that the IO score is unusually low. This might explain why my S5 seems so slow with it installed, if it really is IO bottlenecked it could be bottlenecking the entire system.
The other scores are comparable with AOSP/ICS, but PA is signifigantly slower even though I did a fac reset before installing.
Hmm.. it seem that baseband ignorance patch is not working.. it gives blink to the light panel... lol... i am using 366bb to see how the call quality goes and it seems fine.. is there anyway to make the ignorance patch work? I pretty much like this rom and the lags is almost gone too..
TheManii said:
Unless OP silently updated, I cannot confirm this.
What I mean is that it installed fine for me with CWM 6.0, though the way it mounts isnt the preferred way long term.
If anything it shouldnt be compatable with streakmod as it's using the newer format/mount syntax (it's rather complicated in how recoveries read the update scripts).
GApps is also included in it, perhaps you should remove it and point users to a Gapps package, either mine or the 'official' CM one.
ParanoidAndroid is a source based rom isnt it?
We do (preferrably) need a source port instead of a hackport as the rom still thinks it's an EVO
Perhaps when Kibuuka gets AOSP more closer to working 100%, we'll have more people building from source instead of hackports.
Unlike the S7/S10 CM9 ports (and this port of paranoidandroid), all the ICS based ones are currently hackports.
The S5 is terribly slow compared to the S7, it has the ram and nand space to run the newest roms, but the cpu is simply overwhelmed by new apps/stuff.
It's still plenty usable, but 1st gen snapdragons simply cant compare to 3rd/4th gen snapdragons (and their equivilent Exynos/Tegra chips).
It doesnt make it useless though, I still use my S5 ocasionally even though my S7 is pretty much better in every way (except size)
Edit: after reviewing this rom with Quadrant, it seems that the IO score is unusually low. This might explain why my S5 seems so slow with it installed, if it really is IO bottlenecked it could be bottlenecking the entire system.
The other scores are comparable with AOSP/ICS, but PA is signifigantly slower even though I did a fac reset before installing.
Click to expand...
Click to collapse
You named it hackport was exactly what I did, honestly this is the first step of porting rom (make it can boot up then see how stable it run) after that there are others step more, I skipped it
I think when the base rom hit something like beta stage, there should be a lot of changes, on that time better to port from the beginning again to hv a better result
On supersonic, we used to put Papasmurfs script (found in HTC supersonic forum) then should hv good result, I hv tried it and rom show much better performance, but browser and gmail fc. (I choose I/O scheduler = SIO).
Sorry for the "Evo" things show up
I hv changed the strings.xml on values folder but always stuck when compile framework-res.apk.
Tried every method and apktool (apktool1.4.2/apktool1.4.3/apktool1.4.3.1/apkmanagers for ics/new aapt from android sdk) found on google still no go.
Sent from my PC36100 using Tapatalk 2
If you simply use pull the our AOSP build's drivers, I'd imagine that rebuilding shouldnt be too difficult as all the hard work is making the drivers work.
It would be similar to a hackport in that you dont build everything, but it means you dont have to worry about missing those strings
We'd lose device specific stuff like dock detection, but those dont work in the first place.
Kibuuka already has the device tree up on his git repo, you could prob just use that and it'd work with a couple changes at most (hopefully, and under the assumption that you can compile android in general)
AFAIK the 'official' apktool doesnt work on API15 apks, it only supports up to API14 (4.0.1-4.0.2).
Someone's supposedly made a mod to support API15, but I havnt tried it.
Hi good work i flashed the rom and it works perfect on my ds5 but just one problem the lights for the 3 softkeys on the ds5 stays on even when you turn the screen off did i do something wrong? Please advice thanks
That's problem on every ics rom for dell streak
SULEY1 said:
Hi good work i flashed the rom and it works perfect on my ds5 but just one problem the lights for the 3 softkeys on the ds5 stays on even when you turn the screen off did i do something wrong? Please advice thanks
Click to expand...
Click to collapse
use rootdim and select night mode #1 or #2 or #3 :good:
How to change at 160dpi?
ikimradio said:
How to change at 160dpi?
Click to expand...
Click to collapse
Use LCD modder. But the dial stops working for me after sometime on that.
ikimradio said:
How to change at 160dpi?
Click to expand...
Click to collapse
goto..
settings > paranoid settings > hybrid settings > global density
and change it to your preferrence...
disable hybrid mode in case the homescreen look big...
i am currently on 120dpi and i have no problem with the dial not working... all works so far...
---------- Post added at 11:36 AM ---------- Previous post was at 11:34 AM ----------
ncik said:
Use LCD modder. But the dial stops working for me after sometime on that.
Click to expand...
Click to collapse
if you really use this rom.. dont use lcd modder.. use the built in dpi changer..
Hi there,
i was searching the forum and the inet without any luck about information on how to create or generate *.dtsi files which are placed (in my case) in:
Code:
android\system\kernel\oppo\msm8939\arch\arm\boot\dts\qcom\15018\
im bringing up a new device the "Oppo R7S" which is a sibling device of the "R7 Plus".
So far i was able to compile and boot CyanogenMod succefully. Everything worked except for the Videorecorder
Here are a few pictures: http://community.oppo.com/en/forum.php?mod=viewthread&tid=45106&extra=&page=2
I have noticed that the display driver that my rom has used in my bring-up was either the one for the 15018/R7Plus or for the 15011/R7.
I can't remember which one. I went back to stock before i wrote it down. However it is not the one which should be used which is 15023.
This is where i noticed i must have missed something. I checked my panel in the stock rom using DevCheck and under Graphics it lists the Panel:
Code:
oppo15023samsung s6e3fa3 1080p cmd mode dsi panel
so i checked my stock rom where it gets that info.
On the stock rom i have a file in "system/etc/" it is named
Code:
pp_calib_data_oppo15023samsung_s6e3fa3_1080p_cmd_mode_dsi_panel.xml
But this couldn't be it. So i assumed it must be the display driver in the kernel.
I looked into the CyanogenMod sources https://github.com/CyanogenMod/android_kernel_oppo_msm8939/tree/cm-13.0/arch/arm/boot/dts/qcom
and i was right. There was no 15023 display driver.
Long story short. How do I create and generate those dtsi files?
At the moment this is an Unofficial Rom but i plan to make it an Official Rom as soon as all problems have been fixed.
I hope anyone can help me on my porting "adventure"
This is my device tree: https://github.com/Celoxocis/android_device_oppo_r7sf
celoxocis said:
I have noticed that the display driver that my rom has used in my bring-up was either the one for the 15018/R7Plus or for the 15011/R7.
I can't remember which one. I went back to stock before i wrote it down. However it is not the one which should be used which is 15023.
This is where i noticed i must have missed something. I checked my panel in the stock rom using DevCheck and under Graphics it lists the Panel:
Code:
oppo15023samsung s6e3fa3 1080p cmd mode dsi panel
so i checked my stock rom where it gets that info.
It gets that info from the kernel device tree.
On the stock rom i have a file in "system/etc/" it is named
Code:
pp_calib_data_oppo15023samsung_s6e3fa3_1080p_cmd_mode_dsi_panel.xml
But this couldn't be it.
Click to expand...
Click to collapse
Yeah, that's just Qualcomm's color calibration stuff.
So i assumed it must be the display driver in the kernel.
I looked into the CyanogenMod sources https://github.com/CyanogenMod/android_kernel_oppo_msm8939/tree/cm-13.0/arch/arm/boot/dts/qcom
and i was right. There was no 15023 display driver.
Long story short. How do I create and generate those dtsi files?
Click to expand...
Click to collapse
dts(i) is essentially just code. It's not autogenerated. In the CM kernel we only include the device tree files for devices we actually support (at the moment that's 14005, 15011 and 15018). For getting those files for your devices, the best source is a stock ROM release. Look's like you're lucky: https://github.com/oppo-source/R7plus-5.1-kernel-source/tree/master/arch/arm/boot/dts/15022
Click to expand...
Click to collapse
maniac103 said:
dts(i) is essentially just code. It's not autogenerated. In the CM kernel we only include the device tree files for devices we actually support (at the moment that's 14005, 15011 and 15018). For getting those files for your devices, the best source is a stock ROM release. Look's like you're lucky: https://github.com/oppo-source/R7plus-5.1-kernel-source/tree/master/arch/arm/boot/dts/15022
Click to expand...
Click to collapse
OMG, i was looking the other day at oppo-source github but i let myself fool by the "R7plus-5.1-kernel-source" naming and didn't look for the dts folder.
Thanks so much!
Could i simply copy the entire 15022 folder into
Code:
"cm-13.0\android\system\kernel\oppo\msm8939\arch\arm\boot\dts\qcom"
and compile the CM-rom?
I have a working device-tree and a working cm-rom, except proper display drivers. My guess is, it would include the display driver files in the kernel at my next compile.
Or would i have to edit specific files to make it work?
So far all i did was to simply copy the
Code:
cp cyanogenmod_r7plus_defconfig cyanogenmod_r7sf_defconfig which is in
cm-13.0/android/system/kernel/oppo/msm8939/arch/arm64/configs
and edit Android.mk in
cm-13.0/android/system/device/oppo/msm8939-common#
to include "r7sf"
Code:
LOCAL_PATH := $(call my-dir)
ifneq ($(filter r7sf f1f r5 r7 r7plus, $(TARGET_DEVICE)),)
One last question. What is the best way to make the Oppo R7Sf Officially supported by CM?
My device tree is already on github. I will soon commit the latest changes to it. I would really love for it to be included in CM Officially.
celoxocis said:
OMG, i was looking the other day at oppo-source github but i let myself fool by the "R7plus-5.1-kernel-source" naming and didn't look for the dts folder.
Thanks so much!
Could i simply copy the entire 15022 folder into
Code:
"cm-13.0\android\system\kernel\oppo\msm8939\arch\arm\boot\dts\qcom"
and compile the CM-rom?
Click to expand...
Click to collapse
You'll also need to add a top level dts file and add it to the Makefile. You can use the r5 commit as reference: http://review.cyanogenmod.org/143086
You'll also need to make some small modifications to get a working accelerometer: http://review.cyanogenmod.org/144868
What DTS to you use currently? Normally you should get an error by the bootloader as no DTS for 15022 is currently included.
One last question. What is the best way to make the Oppo R7Sf Officially supported by CM?
My device tree is already on github. I will soon commit the latest changes to it. I would really love for it to be included in CM Officially.
Click to expand...
Click to collapse
Let's make it work first Once we have it working (by adding the missing kernel bits), we can have ciwrl fork the device tree to CM and include it in nightlies. Please make sure to put up all required changes outside of the device tree to Gerrit.
Gesendet von meinem R7plusf mit Tapatalk
maniac103 said:
You'll also need to add a top level dts file and add it to the Makefile. You can use the r5 commit as reference: http://review.cyanogenmod.org/143086
You'll also need to make some small modifications to get a working accelerometer: http://review.cyanogenmod.org/144868
Let's make it work first Once we have it working (by adding the missing kernel bits), we can have ciwrl fork the device tree to CM and include it in nightlies. Please make sure to put up all required changes outside of the device tree to Gerrit.
Gesendet von meinem R7plusf mit Tapatalk
Click to expand...
Click to collapse
Thank you! Well the good thing is i made no changes except those mentioned above outside of the device tree. I tracked changes in the R7 Plus device tree and forked the device tree for the R7S.
And of course removed the bits which were not needed such as fingerprint support. While tracking Uberlaggydarwins F1f device tree i knew what i had to remove.
Thank you! I have seen the R5 commit and already made a diff check last night between 15011 and 15018 to see which files are common files and which are different, this way i can "base" my 15022 DTS files off.
The common files are probably refreshed (newer) files from CM than those from Oppo's github.
As far as i have noted:
Code:
meaning:
"+" = Identical(common) between 15011 and 15022
"<----" = means 15022 differs here:
+msm8939-bus.dtsi
+msm8939-camera.dtsi
+msm8939-coresight.dtsi
+msm8939-cpu.dtsi
+msm8939-gpu.dtsi<----
+msm8939-iommu.dtsi
+msm8939-iommu-domains.dtsi
+msm8939-ion.dtsi
+msm8939-ipcrouter.dtsi+
+msm8939-mdss.dtsi<----
+msm8939-mdss-pll.dtsi+
+msm8939-pm.dtsi<----
+msm8939-regulator.dtsi<----
+msm8939-smem.dtsi
+msm8939-smp2p.dtsi
+msm-gdsc-8916.dtsi
+msm-iommu-v2.dtsi
+msm-pm8916.dtsi<----
+msm-pm8916-rpm-regulato.dtsi
+skeleton64.dtsi
Not identical / different naming (diff 15011 / 15018):
(not compared with 15022 yet)
msm8939-audio-internal_codec.dtsi
msm8939-camera-sensor-mtp.dtsi
msm8939-common.dtsi
msm8939-mtp.dtsi
msm8939-pinctrl.dtsi
msm8939-v3.0-gpu.dtsi
msm8939-v3.0-pm.dtsi
msm8939-v3.0.dtsi
I can do the DTS files changes and can also do the changes in:
Code:
arch/arm/boot/dts/qcom/Makefile
drivers/input/touchscreen/synaptics_oppo/synaptics_oppo_driver_3508.c
but to be honest the changes below scare me off. I'm not an developer/coder. Im an Windows/Linux/Unix Systems Integrator my skills for coding are limited to simple scripts :-/
Code:
drivers/usb/phy/phy-msm-usb.c
sound/soc/codecs/wcd9xxx-mbhc.c
sound/soc/msm/msm8939-slimbus.c
maniac103 said:
What DTS to you use currently? Normally you should get an error by the bootloader as no DTS for 15022 is currently included.
Click to expand...
Click to collapse
I have not enable insecure adb for adb logging during boot. But I think it is using the DTS file for 15018. Devcheck shows the panel (display driver) as 15018.
I finished compiling CM13.0-20160520
and in this version i don't know why both but Cameras stopped working. Previously they worked but Videocamera did not. I guess this will fix once i include and compile the 15022 DTS files.
Orientation / Rotate is actually inverted. When i rotate the phone 90° Left the Display will rotate 90° right and vice versa. So it is inverted. Same with 180° degree. It will be upside/down.
Not sure what happened here, it worked in an older version. Maybe the "timestamp" fix from a few weeks ago worked for the R7S?
Display driver is 15018 but I'm working on that
Everything else works perfectly fine!
Previously to fix the audio and microphone i used the audio_platform_info.xml and mixer_paths_mtp.xml from the R7Plus.
I did compare mixer_paths_mtp.xml of the R7Plus and R7S from ColorOS stock and they only differed in one single line. It worked.
Only thing left are the TFA9890 profiles for the R7S https://github.com/oppo-dev/proprietary_vendor_oppo/commit/c66367fa3970afe98e1398a532c8553fc61d2f53
So it is not much to fix before everything works as most of the work has been done for the R7Plus by you guys
celoxocis said:
Thank you! I have seen the R5 commit and already made a diff check last night between 15011 and 15018 to see which files are common files and which are different, this way i can "base" my 15022 DTS files off.
The common files are probably refreshed (newer) files from CM than those from Oppo's github.
Click to expand...
Click to collapse
I'd suggest going a different route: diff e.g. the 15018 DTS between Oppo's release at oppo-source and CM. Then take the 15022 DTS off Oppo's kernel and apply the 15018 diff generated before onto that. You'll see at least the changes for the accelerometer interrupt and for the tfa9890 (the latter had reset pin and regulator definitions in the sound card in Oppo's kernel and has an own instantiation in ours)
I can do the DTS files changes and can also do the changes in:
Code:
arch/arm/boot/dts/qcom/Makefile
drivers/input/touchscreen/synaptics_oppo/synaptics_oppo_driver_3508.c
Click to expand...
Click to collapse
The Makefile changes are required, the TS driver likely doesn't need any changes as the 15018 kernel already supports 15022. (BTW, the 15022 TS firmware is named differently from 15018. Make sure you're using the right one.)
but to be honest the changes below scare me off. I'm not an developer/coder. Im an Windows/Linux/Unix Systems Integrator my skills for coding are limited to simple scripts :-/
Code:
drivers/usb/phy/phy-msm-usb.c
sound/soc/codecs/wcd9xxx-mbhc.c
sound/soc/msm/msm8939-slimbus.c
Click to expand...
Click to collapse
You don't need those; those were required for the R5's USB/headset mux. When pointing to the R5 support commit I was mostly referring to the DTS changes, not the (C) code changes.
I have not enable insecure adb for adb logging during boot. But I think it is using the DTS file for 15018. Devcheck shows the panel (display driver) as 15018.
Click to expand...
Click to collapse
Why not? It's only a matter of building -eng instead of -userdebug. I somewhat doubt it's using the 15018 DTS. The DTS features the model number (https://github.com/CyanogenMod/andr.../boot/dts/qcom/msm8939-v3.0-mtp-15018.dts#L23) which the bootloader uses to figure out the DTS to use. If the bootloader fell back to use 15018, that would be kinda weird.
I finished compiling CM13.0-20160520
and in this version i don't know why both but Cameras stopped working. Previously they worked but Videocamera did not. I guess this will fix once i include and compile the 15022 DTS files.
Click to expand...
Click to collapse
Maybe. It's unclear without further debugging. You can look in dmesg whether the kernel drivers found the right camera sensor. What blobs are you using? r7plus' verbatim or did you copy others off the stock ROM?
Orientation / Rotate is actually inverted. When i rotate the phone 90° Left the Display will rotate 90° right and vice versa. So it is inverted. Same with 180° degree. It will be upside/down.
Not sure what happened here, it worked in an older version.
Click to expand...
Click to collapse
It's not just the panel being inverted? You can check whether orientation is correct in recovery. If it is, the accelerometer is off and needs further debugging/fixing.
Maybe the "timestamp" fix from a few weeks ago worked for the R7S?
Click to expand...
Click to collapse
With the old state of timestamps being off the issue was that orientation changes stopped working altogether after some time. It's unrelated to your issues which must be isolated to DTS, as sensor HAL + kernel driver is working just fine on r5, r7 and r7plus.
Only thing left are the TFA9890 profiles for the R7S https://github.com/oppo-dev/proprietary_vendor_oppo/commit/c66367fa3970afe98e1398a532c8553fc61d2f53
Click to expand...
Click to collapse
That's mostly trivial as most of those files are straight copies from the stock ROM, they're just renamed. Only the .eq files need conversion (text -> binary), you can use this tool for doing that.
maniac103 said:
I'd suggest going a different route: diff e.g. the 15018 DTS between Oppo's release at oppo-source and CM. Then take the 15022 DTS off Oppo's kernel and apply the 15018 diff generated before onto that. You'll see at least the changes for the accelerometer interrupt and for the tfa9890 (the latter had reset pin and regulator definitions in the sound card in Oppo's kernel and has an own instantiation in ours)
Click to expand...
Click to collapse
You are right. That is the better route. I will see the changes and be able to apply add/delete the changes onto the 15022 DTS files.
maniac103 said:
The Makefile changes are required, the TS driver likely doesn't need any changes as the 15018 kernel already supports 15022. (BTW, the 15022 TS firmware is named differently from 15018. Make sure you're using the right one.)
Click to expand...
Click to collapse
Yes I saw the TS file naming in the source and have included those in my blob list already.
Should i use
Code:
"ifeq ($(CONFIG_OPPO_COMMON_SOFT),y)
+dtb-$(CONFIG_ARCH_MSM8916) += msm8939-mtp-15022.dtb
or rather
Code:
+dtb-$(CONFIG_ARCH_MSM8916) += msm8939-v3.0-mtp-15022.dtb
as the R7S was later released than the R7 Plus. It should be based of the R7 Plus.
maniac103 said:
Why not? It's only a matter of building -eng instead of -userdebug. I somewhat doubt it's using the 15018 DTS. The DTS features the model number (https://github.com/CyanogenMod/andr.../boot/dts/qcom/msm8939-v3.0-mtp-15018.dts#L23) which the bootloader uses to figure out the DTS to use. If the bootloader fell back to use 15018, that would be kinda weird.
Click to expand...
Click to collapse
I got curious too. I'm compiling and -eng version, once done I will flash and check the bootlog.
maniac103 said:
Maybe. It's unclear without further debugging. You can look in dmesg whether the kernel drivers found the right camera sensor. What blobs are you using? r7plus' verbatim or did you copy others off the stock ROM?
Click to expand...
Click to collapse
I extracted the dmesg and pasted it into pastebin here: http://pastebin.com/306q3xZS
maniac103 said:
It's not just the panel being inverted? You can check whether orientation is correct in recovery. If it is, the accelerometer is off and needs further debugging/fixing.
Click to expand...
Click to collapse
Im using TWRP which has no rotation. I will flash CM recovery later and check if its correct in the recovery.
maniac103 said:
That's mostly trivial as most of those files are straight copies from the stock ROM, they're just renamed. Only the .eq files need conversion (text -> binary), you can use this tool for doing that.
Click to expand...
Click to collapse
Thanks! I was looking how i would convert those two files a few weeks ago but didn't find sources.
This is a simple C-file compile?
Code:
gcc calc-biquad.c -o calc-biquad
While working on the sources and checking the diff's i discovered this difference between 15018 and 15022 (both oppo source).
Which i think could be the cause of the inverted rotation issue
Letf is 15018 and Right is 15022
(see attachment)
celoxocis said:
Should i use
Code:
"ifeq ($(CONFIG_OPPO_COMMON_SOFT),y)
+dtb-$(CONFIG_ARCH_MSM8916) += msm8939-mtp-15022.dtb
or rather
Code:
+dtb-$(CONFIG_ARCH_MSM8916) += msm8939-v3.0-mtp-15022.dtb
as the R7S was later released than the R7 Plus. It should be based of the R7 Plus.
Click to expand...
Click to collapse
Release date isn't relevant there. Check /sys/devices/soc0/revision - if it says 3.0 adding 3.0 to the DTS name is the right thing to do.
I extracted the dmesg and pasted it into pastebin here: http://pastebin.com/306q3xZS
Click to expand...
Click to collapse
dmesg alone likely isn't sufficient here. From it it looks like the sensors don't come up, though. Not sure what exactly the problem is, but are you sure you have the right blobs? Initializing the camera is mostly done by the blobs. If you say it worked some time ago, please try whether the r5 introduction kernel commit broke anything for you.
Thanks! I was looking how i would convert those two files a few weeks ago but didn't find sources.
This is a simple C-file compile?
Code:
gcc calc-biquad.c -o calc-biquad
Click to expand...
Click to collapse
Yeah, except you'll need the math library (-lm).
While working on the sources and checking the diff's i discovered this difference between 15018 and 15022 (both oppo source).
Which i think could be the cause of the inverted rotation issue
Letf is 15018 and Right is 15022
(see attachment)
Click to expand...
Click to collapse
Yes, it could. It's almost as likely that the difference is normal, though, as those properties tell the driver how the sensor is mounted in the device, and the mounting orientation isn't necessarily the same between 15018 and 15022. Worth a try though.
maniac103 said:
Release date isn't relevant there. Check /sys/devices/soc0/revision - if it says 3.0 adding 3.0 to the DTS name is the right thing to do.
Click to expand...
Click to collapse
Thanks! Checked and its "3.0" i applied 3.0 files.
maniac103 said:
dmesg alone likely isn't sufficient here. From it it looks like the sensors don't come up, though. Not sure what exactly the problem is, but are you sure you have the right blobs? Initializing the camera is mostly done by the blobs. If you say it worked some time ago, please try whether the r5 introduction kernel commit broke anything for you.
Click to expand...
Click to collapse
I just finished adding 15022 files into the kernel and started the compile. I will look into the problem as soon as i finish flashing the new rom.
I found my eeprom file for the camera too. I used to extract all blobs because i did not know which was the correct one.
maniac103 said:
Yes, it could. It's almost as likely that the difference is normal, though, as those properties tell the driver how the sensor is mounted in the device, and the mounting orientation isn't necessarily the same between 15018 and 15022. Worth a try though.
Click to expand...
Click to collapse
Yes i agree. I read about it online when i discovered the difference. The sensor is probably mounted differently in the R7S. We will see as soon as the compile is finished and i flashed the rom
So far the compile runs through without any complains to my kernel additions. I went with the suggested route. Diff CM-15018<->Oppo-15022 applied those changes to the Oppo-15022 files and got CM-15022.
I did not create a different defconfig for the R7S. I sticked with the settings from R7Plus. Just renamed it for dependency mode.
I noticed something. While i fixed up the TFA9890 files.
where did you get the "left.tfa9890_n1b12.patch" file from? it's not in the R7S nor R7Plus ColorOS stock rom.
i see one patch "TFA9890_N1C3_1_7_1.patch" which is renamed to "left.tfa9890_n1c2.patch"
i can see a second "coldboot.patch" but that looks empty and has not the same content as "left.tfa9890_n1c2.patch"
is it a generic file which is required for TFA9890? if yes. i guess i can simply copy and paste it. as "left.tfa9890_n1c2.patch" is identical in both roms?
for the compile i just copied the R7plus file as i didn't know where it came from.
n1c2/3 and n1b12 are just different revisions of the tfa9890. r7plus stock firmware carried both files IIRC; it should be OK to omit n1b12 if the r7s doesn't have that revision.
Gesendet von meinem R7plusf mit Tapatalk
maniac103 said:
n1c2/3 and n1b12 are just different revisions of the tfa9890. r7plus stock firmware carried both files IIRC; it should be OK to omit n1b12 if the r7s doesn't have that revision.
Gesendet von meinem R7plusf mit Tapatalk
Click to expand...
Click to collapse
Ok i will just leave that file out of the blob list.
I had time today to flash my new build today and test it, which included the 15022 kernel inclusions and as i hoped all the issues i had, are gone!
Thanks alot for your help!
As far as tested:
Both cameras work!
Videocamera works!
All Sensors + GPS, Wifi work too!
Flashlight works.
Rotation issue fixed too! The guess about the sensor mounting was right!
Display driver is the correct one!
I have yet to grab a boot log. "adb logcat" before and while booting the device should be enough to catch everything. right?
The only thing left to do is to filter out the proper camera blobs.
Im using JackPotClavin's Android-Blob-Utility for that.
Can i leave out the blobs for Camera, Camera autofocus, Camera chromatix which are referenced in "lib64/" ?
I have seen that the R7Plus nor the R7f use these blobs in the proprietary-files.txt.
I will try to commit all changes to github on the next weekend. Once i finish updating the blobs list with the proper camera blobs.
celoxocis said:
The only thing left to do is to filter out the proper camera blobs.
Im using JackPotClavin's Android-Blob-Utility for that.
Click to expand...
Click to collapse
That's one option, another one would be strace'ing the camera daemon (in adb shell):
Code:
su
setprop ctl.stop qcamerasvr
strace -f -eopenat /system/bin/mm-qcamera-daemon
That'll tell you what blobs it tries to open.
Can i leave out the blobs for Camera, Camera autofocus, Camera chromatix which are referenced in "lib64/" ?
I have seen that the R7Plus nor the R7f use these blobs in the proprietary-files.txt.
Click to expand...
Click to collapse
Yeah, you can, the media stack is 32 bit only.
maniac103 said:
That's one option, another one would be strace'ing the camera daemon (in adb shell):
Code:
su
setprop ctl.stop qcamerasvr
strace -f -eopenat /system/bin/mm-qcamera-daemon
That'll tell you what blobs it tries to open.
Yeah, you can, the media stack is 32 bit only.
Click to expand...
Click to collapse
I finished the blob list but there is something i have been trying to fix for days and i can't really figure out whats the cause.
It is Wifi:
In Oppo Stock ColorOS everything is fine and stable. Wifi just works out of the box. It keeps switching between 2.4Ghz and 5Ghz depending where im in the house. (Signal strength)
I have a AVM Fritzbox 7490 with the latest firmware and all features. Dual band etc.
In CyanogenMod i keep having "drop outs". The Wifi is just dropping out. Like i have it turned off.
When i force it to use only 2.4Ghz band in wifi advanced options, it never happens. I believe it happens when it should automatically switch between 2.4Ghz and 5Ghz.
In my device tree im already using the "WCNSS_qcom_wlan_nv_15022.bin" as my "WCNSS_qcom_wlan_nv.bin"
I have already checked following files and made a diff for what the cause could be:
p2p_supplicant_overlay.conf = same as stock
WCNSS_qcom_cfg.ini = same as stock
wpa_supplicant.conf = wifi-direct settings disabled. we don't need that.
wpa_supplicant_overlay.conf = same as stock
It seems like i can fix the issue when enabling "Always allow Wi-Fi Roam Scans" and "Use legacy DHCP client" in Developer Options.
But here is the problem as soon as i reboot the device those settings are unchecked.
How can i make it permanent? Is there a way to make it permanent in the device tree? to compile the ROM using those settings as default?
I can even replicate the problem by turning off those two settings and walking around the house.
Any idea?
Update:
After hours of testing. With and without the above options.
Forced 5Ghz wifi is not stable at all. I tried all combinations getting 5Ghz to work, with no luck.
Forced 2.4Ghz works fine with and without above options. So my conclusion. It is definitly something wrong with how prima handles the 5Ghz.
In stock both work fine.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate partition, with enough space (about 450mb) to place the whole vendor there.
As a result, I created a solution and tried to make it as much easy as possible for daily use.
I created 2 files - system.img/vendor.img as ext4 images and put it in to the system partition. And then on early init I mounting real system partition as /system_src and then mount system.img as /system and vendor.img as /vendor.
Also I created twrp treble's version for easy use /system and /vendor. It's can wipe new system\vendor partitions, you can restore images to system/vendor in the same way, as we use for boot/recovery.
How to
Prepare - need only once
1. in the current twrp make full wipe (at least we need clean /system, because later we fill all /system by 2 files: system.img/vendor.img)
2. you need flash my twrp with treble support (sm-t825-twrp_3.2.3-0_treble.img): https://drive.google.com/file/d/1GJMrHI4wkePXh8JmF_jgxBSly38B5tu1/view?usp=sharing
3. flash zip with new system.img/vendor.img as ext4 images: https://drive.google.com/file/d/14lwrnM85CoxcpjTUiJ0yfbGHXLa7k0DB/view?usp=sharing
Installation
1. download treble zip from Links and flash it as usual zip. It will flash boot.img and /vendor partition (this is part, specific for our tablet only)
2. download any treble system (64bit System A-only) image from: https://forum.xda-developers.com/project-treble/trebleenabled-device-development, if it not a .img file - extract it, then copy to sdcard/extsd card and then flash image as system_image in twrp (Install - switch to Install Image and flash as System Image)
3. some images require vendor's modification, in oreo some firmware has a 90 rotate, some 270, in my treble zip 90, if you see - image rotated on 180 - flash zip from Additional Links
4. if you wanna back to original lineage\rr without treble - you need flash normal twrp version and make full wipe or just flash stock firmware via odin
Known Issues
sound 2 skeakers only for now
fingerprint
keys light dnw on some firmwares
Links
2. 20180911: fix rotate, back to stock sound (fix bt, quad speakers): https://drive.google.com/file/d/1e_mzosWYL7bv29n613OKZpvSZPXMh26k/view?usp=sharing
1. 20180802: initial treble: https://drive.google.com/file/d/14lwrnM85CoxcpjTUiJ0yfbGHXLa7k0DB/view?usp=sharing
Few notes about item 2: your tablet has wrong image orientation, panel horizontal, sensor - vertical, as result troubles with show right image in right orientation. In 7.0-8.1 this problem was fixed by adding ro.sf.hwrotation=270 in build.prop. For pie this way dnw. Google remove this option and update configstore with new ISurfaceFlingerConfigs. It was added new method: primaryDisplayOrientation. Problem was in adding new configstore sources in the 15.1 sources. Finally I had successfully builded configstore 1.0/1.1 from 16.0 in 15.1.
Additional Links - need only for some oreo images, if image rotated on 180
2. 20180911: https://drive.google.com/file/d/1S4mvXFcX-d2xoZEp9b9dG3ywUhybT6U2/view?usp=sharing
1. 20180802: initial fix rotate: https://drive.google.com/file/d/1JKGu7vudrU0bJPEdkGwBVFkyCJpsHLLs/view?usp=sharing
Magisk
For some reason original Magisk dnw with our treble. It's somehow connect to sepolicy and I'm almost sure about it connected to our treble way with loop0/loop1 mount.
Finally I made small update of the original latest Magisk and it's working. Only one thing was done by me: inside zip in the binary magiskinit file I remove seclabel (seclabel u:r:magisk:s0) for magisk services.
Fixed 17.1 Magisk beta: https://drive.google.com/file/d/1lMhM8ceaJoy5pHRHjCsxxG2C9e5sB5Ot/view?usp=sharing
17.1 Magisk beta manager (this apk also inside Magisk, but cann't be installed automatically during Magisk install), install it as normal apk after install Magisk: https://drive.google.com/file/d/1qCoVPUxvvxopCGfIpoHdAnKueNIxMXal/view?usp=sharing
GApps
https://opengapps.org
Almost all firmware say about wrong vendor version. This is normal, just press OK.
Checked firmwares
AospExtended (need rotate 270 patch): https://forum.xda-developers.com/pr...evelopment/rom-aospextended-rom-v5-5-t3797509
Cosmic-OS: https://forum.xda-developers.com/pr...ment/cosmic-ospulsar8-1-0201805243-2-t3794806
DroidOnTime: https://forum.xda-developers.com/pr...pment/official-droidontime-dotos-2-x-t3794338
Havoc-OS: https://forum.xda-developers.com/pr...-device-development/rom-havoc-os-8-1-t3819050
Lineage: https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690
OmniROM Treskmod (need rotate 270 patch): https://forum.xda-developers.com/pr...development/rom-8-1-omnirom-treskmod-t3818188
Pixel Experience (it's requere register custom firmware): https://forum.xda-developers.com/pr...e-development/8-1-0-pixel-experience-t3796011
Resurrection Remix: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
let's experiment together!
Wow! Man, you rock! My Favourite dev! Thanks for Your hard work!
Thanks for this. One question, do we use A/B or A images?
Peeps1513 said:
Thanks for this. One question, do we use A/B or A images?
Click to expand...
Click to collapse
Forgot: system a only
Valera1978 said:
Forgot: system a only
Click to expand...
Click to collapse
And what did You think about the bugs You have mentioned? (Fingerprint, deepsleep, speakers) Fixable or not?
deepsleep, speakers - this is the common tab s3 problems (same in the original lineage), a bit later will back to it.
fingerprint - need to check, in the treble mode shim libs dnw because of linker in the system, also service from vendor don't see libs in system - i.e. some limitations. For camera I made workaround: launch second cameraserver service with my shim lib in environment, but this way dnw for fingerprint. It should be something easy to fix, but I still don't see it.
Valera1978 said:
deepsleep, speakers - this is the common tab s3 problems (same in the original lineage), a bit later will back to it.
fingerprint - need to check, in the treble mode shim libs dnw because of linker in the system, also service from vendor don't see libs in system - i.e. some limitations. For camera I made workaround: launch second cameraserver service with my shim lib in environment, but this way dnw for fingerprint. It should be something easy to fix, but I still don't see it.
Click to expand...
Click to collapse
Really appreciate your work :highfive:
Nice project. Good stuff.
I finally settled on HAVOC after much playing around but am facing an issue trying to install magisk (16.7), no success yet . When I searched [ROM][TREBLE] Havoc-OS 8.1 it seems that magisk has been installed on other devices so could it be a vendor issue? Any help would be appreciated. phh supersu seems to be fine though.
Peeps1513 said:
I finally settled on HAVOC after much playing around but am facing an issue trying to install magisk (16.7), no success yet . When I searched [ROM][TREBLE] Havoc-OS 8.1 it seems that magisk has been installed on other devices so could it be a vendor issue? Any help would be appreciated. phh supersu seems to be fine though.
Click to expand...
Click to collapse
Yep. I've tested treble but no sucess atm for me. Better stay with non-treble lineage, as most of the things work just fine. Maybe in future if Valera fix some things on treble bulid (if ever). Hope Dev focus on oreo lineage than treble project (which is good stuff, but not good enough as daily driver)
I want to leave a feedback after almost a month with treble roms
I have to change my mind: treble is fantastic! Such a great thing, very helpfull for all of us. I was running Valera's lineage 15.1 as daily driver for about 2 months.
In regular non-treble bulid almost everything work. Bad thing were performance (slow animations) and not working deepsleep.
I was happy but not at al. That wasnt this what i was looking for. Then i found again this thread and again give a try (longer) :fingers-crossed:
I am running now treble omnirom for few weeks. Worst things i find is: magisk did not work (very sad, tried multiple versions with no luck, other users report magisk is working for them) and my bluetooth headphones arent working (probably our side bug too)
In plus: no random reboots, performance is very good, no slow downs, deepsleep problem almost gone (drain 6% overnight connected to wifi)
Didnt find any other bugs
I am really happy now. It would be exelent with magisk and bluetooth audio working
Great job, i stick with treble for now :laugh:
Thanks for your great work, Valera!
Have anyone tried this on SM-T820 (Wi-Fi only version)?
imder said:
Thanks for your great work, Valera!
Have anyone tried this on SM-T820 (Wi-Fi only version)?
Click to expand...
Click to collapse
Work only with T825
Any updates Master?
@Valera1978
Could you PLEASE make this for us left out t820 owners???
How does this rom with Lineage compare to your non-treble build? Any reason to switch if I want to stick with Lineage?
robsmith11 said:
How does this rom with Lineage compare to your non-treble build? Any reason to switch if I want to stick with Lineage?
Click to expand...
Click to collapse
You better wait for Pie relase. Valera is working on it.
suzook said:
@Valera1978
Could you PLEASE make this for us left out t820 owners???
Click to expand...
Click to collapse
Without device this is impossible. Look like somehow vendors is differ in 820/825, and I need device to understand, what is wrong, why vendor from 825 dnw on 820 (except ril, may be gps). It should be something simple. Because on my another samsung's tablet on exynos no diffs at all. Treble for wifi version I had made based on lte version in first attempt.
robsmith11 said:
How does this rom with Lineage compare to your non-treble build? Any reason to switch if I want to stick with Lineage?
Click to expand...
Click to collapse
I'll update non-treble build soon. And treble too. During working on treble I had fixed some stuff, like hexedit finger libs to remove shim lib. But I need fix audio in calls again first.
About pie - I dont see any reason to start work on it right now, it's too early, it still has a lot of problems. Better spend this time to make something cool - may be even make samsung port from note 9 or tab s4 with dex and some stuff.
But if you don't want use treble (I agree, it's may be too complicate with special twrp and additional partitions), I think I can prepare integrated pie system images with simple flash without any additional manipulations, like you flash lineage.
Valera1978 said:
Without device this is impossible. Look like somehow vendors is differ in 820/825, and I need device to understand, what is wrong, why vendor from 825 dnw on 820 (except ril, may be gps). It should be something simple. Because on my another samsung's tablet on exynos no diffs at all. Treble for wifi version I had made based on lte version in first attempt.
Click to expand...
Click to collapse
Man, if you would be somehow able to build a unified or a separate treble rom for 820, you would be the greatest man on xda! Cause we have no support for 820 anymore...
I've made a modded version of the great "Simple Camera" by SimpleMobileTools ( simplemobiletools.github.io ) to work with the secondary pocophone and MI8 cameras including the front facing infrared camera, you can record videos and take pictures, it's free, no ads, no analytics, and open source.
Working:
- Camera and using back secondary camera or infrared camera on LineageOS/AOSP roms
Let me know if you have problems on any other rom
Not yet working:
it seems it is NOT WORKING on MIUI roms - it seems that MIUI has disabled the camera access on newer versions, maybe with root there is a way to reconfigure miui to allow the two new cameras to work, still investigating, if someone has an idea i would love to know
If someone knows some rom/kernel/root/magisk module developer that may be able to help me let me know and i'll be more than happy to try and make it work on MIUI!
Hope it's useful, thank you!
Download Links Removed
XDA:DevDB Information
IR camera - MI8, Device Specific App for the Xiaomi Mi 8
Contributors
TeraJL
Source Code: https://github.com/jlvcm/Simple-Camera
Version Information
Status: Testing
Current Stable Version: 1
Stable Release Date: 2019-01-04
Created 2019-01-07
Last Updated 2019-01-06
Wow, this is actually very good.
Working fine on Pixel Experience.
Thanks a lot. It is awesome in the dark.
Thank you. It works.
Out of curiosity, any use beyond "trying"?
Can you please post screenshots?
The MIUI Hidden Settings app is able to get access to the IR camera (Hidden Settings > QMMI > 34. Camera Front). Maybe something that you can pursue to gain access to the IR camera on MIUI in your app?
This photo attached I've shot in a 99% dark room.
The background is dark because it's pointing to my face. But if you point to the background ambient it all gets insanely brighter and visible (second attachment)
Of course the quality sucks. But we can clearly see what's in the path.
for me wont work on pixel3rom, only black screen, only work with the back camera
H4R81N63R said:
The MIUI Hidden Settings app is able to get access to the IR camera (Hidden Settings > QMMI > 34. Camera Front). Maybe something that you can pursue to gain access to the IR camera on MIUI in your app?
Click to expand...
Click to collapse
thats true. it works in xiaomi.eu rom also.
H4R81N63R said:
The MIUI Hidden Settings app is able to get access to the IR camera (Hidden Settings > QMMI > 34. Camera Front). Maybe something that you can pursue to gain access to the IR camera on MIUI in your app?
Click to expand...
Click to collapse
Good find!
Did you manage to find the pictures taken ? Don't think they're actually saved..
Stoffl_ said:
Good find!
Did you manage to find the pictures taken ? Don't think they're actually saved..
Click to expand...
Click to collapse
No, I haven't found the saved pictures. I'm not a 100% sure, but I think that the Hidden Settings app uses the factory/feature testing methods because of the Pass/Fail buttons that appear while using the Front Camera IR in it. I also get a green check mark next to the front camera entry in the QMMI list after I have tapped the 'take picture' button.
Yeah I think you're right.
Wow this is working quite good. Thank you for the mod.
Great it works on MIUI stock rom with magisk root
thank you
Latest xiaomi.eu doesnt work even with root.
After granting root, there is still problem
Mi8
Literally says in OP that MIUI roms aren't supported......
kael2404 said:
Latest xiaomi.eu doesnt work even with root.
After granting root, there is still problem
Mi8
Click to expand...
Click to collapse
i'm on xiomi.eu 9.1.24, and the IR camera works if you add this line to /system/build.prop
Code:
camera.aux.packagelist=com.joaolvcm.pocoseccamera
Stoffl_ said:
Literally says in OP that MIUI roms aren't supported......
Click to expand...
Click to collapse
Read changelog in play store
Yeah I tested it after reading gulps post,neat.
gulp79 said:
i'm on xiomi.eu 9.1.24, and the IR camera works if you add this line to /system/build.prop
Code:
camera.aux.packagelist=com.joaolvcm.pocoseccamera
Click to expand...
Click to collapse
D'OH!
I can't modify build.prop, tried mixplorer, kernel adiutor and build.prop editor from playstore. they all get root permission but fail on saving build.prop
I am on latest xiaomi.eu stable, BL unlocked, TWRP and and Magisk
if I open connectbot and try as root i am able to "mount -o remount,rw /" but no luck with build.prop
If I try to "mount -o remount,rw /system" i get:
'/dev/block/platform/soc/1d840000.ufshc/by-name/system' us read-only
How did you managed to do it? (te prego ^_^)
Z
zavorrax said:
D'OH!
I can't modify build.prop, tried mixplorer, kernel adiutor and build.prop editor from playstore. they all get root permission but fail on saving build.prop
I am on latest xiaomi.eu stable, BL unlocked, TWRP and and Magisk
if I open connectbot and try as root i am able to "mount -o remount,rw /" but no luck with build.prop
If I try to "mount -o remount,rw /system" i get:
'/dev/block/platform/soc/1d840000.ufshc/by-name/system' us read-only
How did you managed to do it? (te prego ^_^)
Z
Click to expand...
Click to collapse
Seem the usual problem with /system mount....
Try this:
1) Reboot in TWRP
2) in TWRP go to "Mount" and select "cache, System, Vendor, Data"
3) Reboot to System, and now you should be able to modify the "build.prop"
Daje!!!
crDroid 6.2 ROM 15-01-2020
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA before!
Make sure you have a custom recovery installed (TWRP is the preferred recovery. [I'm not using Fox recovery, I'm not going to give you advice.])
Boot into recovery
Wipe data, cache partitions to clean install. Wipe dalvik, cache to update previous crDroid.
(If your /data partition secured, maybe need format /data if you want to use this ROM.)
Flash Rom in TWRP (sideload or copy any storage)
Flash OpenGapps (Optional) [I'm not using GAPPS, I'm not going to give you advice.]
Flash Magisk Root (Optional) [I'm not using Magisk, I'm not going to give you advice.]
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 1 minute.
DOWNLOAD SF
DOWNLOAD AD
All ROMs here: LINK
Known issues: don't know
*
Screenshots: LINK
OS source: LINK Many thanks to adi153!
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140 (not my work)
ROM info: Q10 Lineage-17.1, system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 24-12-2019 6.0 version
Last Updated 15-01-2020 6.2 (build3)
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
You're welcome.
New build 15.01.2020, & many changes to the system. I'd like to get feedback on whether VOLTE is working? Thanks.
SYS update V1 out: 14-01-2020
Something wrong with the system updates, I moved it to the test directory.
Nice
Wow, a new rom... Thanks szanalmas, will give feedback after testing it
@szanalmas
Edit: Already tested your rom, so stable and smooth...
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Just that, still looking for other
Big thanks again for this nice rom
(Sorry for my bad english :v)
@szanalmas thanks ...for stable ROM.
---------- Post added at 04:18 AM ---------- Previous post was at 04:00 AM ----------
From long time i was waiting for stable ROM. Thanks for your hard work.
@szanalmas thanks for make stable ROM :good:
while there are no bugs,
if there are bugs
I'll tell you later
thanks man i like crdroid
rom stable smooth did not find any bug after 2 hours use
Fadly357 said:
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Click to expand...
Click to collapse
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
szanalmas said:
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
Click to expand...
Click to collapse
Okay, will tell you as soon as possible if i found other
could you teach me rom build? i wanna learn and help
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
viethoang18 said:
could you teach me rom build? i wanna learn and help
Click to expand...
Click to collapse
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Fadly357 said:
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
Click to expand...
Click to collapse
I once used the magisk in TWRP but not this ROM. It worked for some.
But I didn't write in my post on my TWRP either now.
(I don't use magisk now.)
Use Canary: LINK
Or whatever.
szanalmas said:
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Click to expand...
Click to collapse
can i use Unbutu wls on windows ?
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Thank you very much feedbacks and thanks to everyone! :good:
Call volume on speaker is very high by default
@szanalmas Call volume on speaker is very high by default. Please set lower level by default. I hope in new build it willbe resolve.
Thanks...
ahmedhelmy71 said:
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Click to expand...
Click to collapse
This is what LINK is all about, and I still hold that the double-tap feature cannot be used for two things at once. What's interesting is that I can't find the ambient display double-tap menu option, and there's a separate one in Havoc ambient settings.
This is also an Official bug unfortunately.
*
cpglbitm said:
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
Click to expand...
Click to collapse
The SD card problem is very-very interesting.
What filesystem is in sd card?
Could you send us a logcat digest right after the phone is started?
Code:
adb logcat | grep vold > sdcardproblem.txt
viethoang18 said:
can i use Unbutu wls on windows ?
Click to expand...
Click to collapse
I don't know. I haven't used Windows for years, sorry.