WHOEVER AGREES TO THE POST BELLOW PLEASE LEAVE A COMMENT TO SHOW SUPPORT FOR THE CAMERA PORT
Hello, there Sultanxda
I'm posting this post?with the hope that you'll see what I have to say.
First of all, congrats on the work you done on CM*13 and Lineage *14. Congrats on the touches you added to both.
I love the stability, the battery life on your CM*13, BUT, your camera, or CM'S camera user interface, I just dont think its that much USER FRIENDLY as OOS camera is. I have tried so many ways to get that camera ported onto this ROM and withkut success and I'm sure others have tried it too.
Through this post I am requesting a port file or an update which provides both cameras and let us choose which one we use, or use both in diff situations.
Look, man I get it, you've put work in the camera, BUT the user interface. Please allow us to use OOS camera with no issues.
I'm sure other people would appreciate it too if you would do that. That way your ROM would be the best ROK there is for OnePlus3T. The reason I left your rom ia because of the camera. The camera is one of the most important things in my phone since i capture moments, and I there are moments that I want to capture on the spot, quick and easy, moments when I want to take a quick video and by the time I bring up the video feature its too late, the moment is gone. I hope that you can underatand me of why I want the OOS camera on your rom.
WHOEVER AGREES TO THE POST BELLOW PLEASE LEAVE A COMMENT TO SHOW SUPPORT FOR THE CAMERA PORT
This rom ships with Snap and OnePlusCamera. It is 14.1 - not 13. RAW pic saving and burst mode doesn't work, but evryting else is working.
OnePlus does not use HAL3, but HAL1 with proprietary call backs to framework/av (libcameraservice) to implement some features of HAL3 to HAL1-running OnePlusCamera. Since this is neither real HAL1, nor HAL3 - and because this is proprietary - it's not easy to implement in lineageos. @vavill is working on this:
https://github.com/kxzxxx/android_device_oneplus_oneplus3t/commits/cm-14.1
On a side node: Read, understand, respect and follow the forum rules, please. Questions belong to the Q&A forum.
Jesus save this child..just bless him..
Wrong section.. In case you ask me why u need blessings..!!
arjunarora said:
Jesus save this child..just bless him..
Wrong section.. In case you ask me why u need blessings..!!
Click to expand...
Click to collapse
I think you're exaggerating there. My bad then, how do I delete the post?
benm98 said:
I think you're exaggerating there. My bad then, how do I delete the post?
Click to expand...
Click to collapse
Not at all bud.. @stephen can you please move this to the appropriate section..
nvertigo67 said:
This rom ships with Snap and OnePlusCamera. It is 14.1 - not 13. RAW pic saving and burst mode doesn't work, but evryting else is working.
OnePlus does not use HAL3, but HAL1 with proprietary call backs to framework/av (libcameraservice) to implement some features of HAL3 to HAL1-running OnePlusCamera. Since this is neither real HAL1, nor HAL3 - and because this is proprietary - it's not easy to implement in lineageos. @vavill is working on this:
https://github.com/kxzxxx/android_device_oneplus_oneplus3t/commits/cm-14.1
On a side node: Read, understand, respect and follow the forum rules, please. Questions belong to the Q&A forum.
Click to expand...
Click to collapse
Thats the ROM I previously used, but I gave up on it, I want sultan because of better bettery life and stabillity, also it has xposed, please show your support if you agree with me tough and spread the word till this gets to sultan.
benm98 said:
Thats the ROM I previously used, but I gave up on it, I want sultan because of better bettery life and stabillity, also it has xposed, please show your support if you agree with me tough and spread the word till this gets to sultan.
Click to expand...
Click to collapse
Haha, he's the maintainer of that ROM you gave up on, lol.
benm98 said:
Thats the ROM I previously used, but I gave up on it, I want sultan because of better bettery life and stabillity, also it has xposed, please show your support if you agree with me tough and spread the word till this gets to sultan.
Click to expand...
Click to collapse
I completly misunderstood your question.
If your question was: "Can I use OnePlusCamera from @nvertigo's cm-14.1 rom on @Sultanxda's cm-13.0 rom?", the answer is: no, but you can use the android 6 version.
Just copy these files from stock OxygenOS 3.x.x (you need this older version for cm-13.0):
Code:
/system/priv-app/OnePlusCamera/OnePlusCamera.apk
/system/priv-app/OnePlusGallery/OnePlusGallery.apk
/system/lib64/libfilter-sdk.so
/system/lib64/libopbaselib.so
/system/lib64/libopcameralib.so
/system/lib64/libopcamera.so
If this works, make a flashable zip of it.
A private word:
Your posting feels unfair, barefaced and offending. Where are your bug reports and/or logs? Have you asked for help? I havn't found one single word on your issues in the rom thread. You demonstrate a lack of respect for my work and real bad manner.
nvertigo67 said:
I completly misunderstood your question.
If your question was: "Can I use OnePlusCamera from @nvertigo's cm-14.1 rom on @Sultanxda's cm-13.0 rom?", the answer is: no, but you can use the android 6 version.
Just copy these files from stock OxygenOS 3.x.x (you need this older version for cm-13.0):
Code:
/system/priv-app/OnePlusCamera/OnePlusCamera.apk
/system/priv-app/OnePlusGallery/OnePlusGallery.apk
/system/lib64/libfilter-sdk.so
/system/lib64/libopbaselib.so
/system/lib64/libopcameralib.so
/system/lib64/libopcamera.so
If this works, make a flashable zip of it.
A private word:
Your posting feels unfair, barefaced and offending. Where are your bug reports and/or logs? Have you asked for help? I havn't found one single word on your issues in the rom thread. You demonstrate a lack of respect for my work and real bad manner.
Click to expand...
Click to collapse
Not home right now. I appreciate your guide, will try it when I get home. Look, lad, I didn't meat to offend, I have used your rom as my daily driver for a month since I gave up on SULTAN's because there is no OOS camera on it. I enjoyed using it, but I was missing xposed and the fact that sultan's uses Android 6 which in my opinion is more stable.
Again didn't mean to offent no one, is just the fact that sultan's offers xposed due to it being 6.0 and thats why I think battery life is better on that, since it's not as heavily loaded as 7.0 or 7.1 is.
Thanks again for the guide, looking forward to giving it a try. Also what do you mean by "If this works, make a flashable zip of it.", do you mean after I drop in the files from OXYGEN OOS to sultan's OS create a zip then flash it and then see if it works?
Related
This is for rom discussion of Raymans [ROM][N910C/H/U] CyanogenMod 13 thread.
I hope this will keep Raymans dev thread DEV TALK ONLY. Other casual questions should be posted here.
CHANGE-LOGS FOR N910C/H http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_samsung_treltexx+status:merged
CHANGE-LOGS FOR N910U http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_samsung_trhpltexx+status:merged
CHANGE-LOGS FOR TRE-COMMON http://review.cyanogenmod.org/#/q/p...id_device_samsung_trelte-common+status:merged
CHANGE-LOGS FOR KERNEL http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_kernel_samsung_trelte+status:merged
CHANGE-LOGS FOR CM 13 http://www.cmxlog.com/13/#
Newest compiles will be posted here.
N910U https://www.androidfilehost.com/?fid=457095661767105786 Oct 29th
N910C/H https://www.androidfilehost.com/?fid=24686681827313645
IMEI is one of the most important things of a smartphone. That’s why every time you flash a custom ROM, the developer strongly suggests you to make a backup of your IMEI partition because without that, the Galaxy Note 4 loses its main function which is making phone calls.
Quote:
Give the programmer some credit for basic intelligence: if the program really
didn't work at all, they would probably have noticed. Since they haven't
noticed, it must be working for them. Therefore, either you are doing something
differently from them, or your environment is different from theirs. They need
information; providing this information is the purpose of a bug report. More
information is almost always better than less.
Before reporting bugs, please check the KNOWN BUGS list below and read this how-to
KNOWN BUGS
SELINUX: Needs rules finished up to boot enforcing properly
VOIP: Uses an invalid route
RIL: SMS broadcast subscriptions aren't working (generic failure)
I DO NOT SUPPORT BUG REPORTS IF YOU HAVE XPOSED INSTALLED! END OF STORY!!!
removed
Good idea
I will post builds every week or so AS LONG AS CASUAL DISCUSSION STAYS IN THIS THREAD ONLY! Fair enough users?
Cool thanks for doing this man
Sent from my SM-N920C using Tapatalk
The noise fix by not-i will not work on aosp roms because aosp uses mixer_paths.xml whereas stock rom uses tinyucm.conf wich has to be recoded into mixer_paths.xml. So the noise fix WILL NOT WORK ON AOSP. I hope everybody understands this.
Perfect ROM aside from the broken Fingerprint, but that's no big issue for me.
What bothers me is the low mic recording sound.
Even if I use a 3.5mm mic it still sounds too low.. Any idea of solving this ?
need to up the volume in mixer_paths.xml and or dual mic is disabled at the moment.
one question that it's probably been discussed though. Is there any possibility in porting the touchwiz camera apk to cm13. I mean, why is it possible to port it in MIUI 7 and not in CM 13. It's probably something with the software but I really wish I could have JUST the Samsung camera in cm13 cause the quality of the cm13 barely resembles the quality of the Samsung camera. It's like night and day difference. Aside from this, happy new year ppl Enjoy it to the fullest!!!
Changelog for the new build ?
also, no idea what to increase in the mixer_path
---------- Post added at 01:15 PM ---------- Previous post was at 01:08 PM ----------
Konskl said:
one question that it's probably been discussed though. Is there any possibility in porting the touchwiz camera apk to cm13. I mean, why is it possible to port it in MIUI 7 and not in CM 13. It's probably something with the software but I really wish I could have JUST the Samsung camera in cm13 cause the quality of the cm13 barely resembles the quality of the Samsung camera. It's like night and day difference. Aside from this, happy new year ppl Enjoy it to the fullest!!!
Click to expand...
Click to collapse
MIUI v7 for note4 is based on touchwiz, if it were based on cyanogenmod it wouldn't have Sammy cam.
miui uses stock base rom so the camera can use the tw framework. Aosp can't use TW framework that is why camera can not be ported.
CHANGE-LOGS ARE HERE http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_samsung_treltexx
now stop asking about changes there are way to many between tre/trhp commits and cm13 commits to keep track of.
If you do not know what to change in mixer_paths google it or don't touch it for now.
travis82 said:
miui uses stock base rom so the camera can use the tw framework. Aosp can't use TW framework that is why camera can not be ported.
CHANGE-LOGS ARE HERE http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_samsung_treltexx
now stop asking about changes there are way to many between tre/trhp commits and cm13 commits to keep track of.
If you do not know what to change in mixer_paths google it or don't touch it for now.
Click to expand...
Click to collapse
Sorry, won't happen again
updated op with all change-logs.
plz give me downloading link of cm13 for n910 H thanks dev
loveaddicated said:
plz give me downloading link of cm13 for n910 H thanks dev
Click to expand...
Click to collapse
H/C are the same rom.
compiling a N910U rom with our proprietary drivers and audio configs I'll put it out if it boots when its done compiling you can let me know the difference if any.
travis82 said:
compiling a N910U rom with our proprietary drivers and audio configs I'll put it out if it boots when its done compiling you can let me know the difference if any.
Test build N910U cm-13.0-20160102-UNOFFICIAL-trhpltexx
https://www.androidfilehost.com/?fid=24352994023704101
Click to expand...
Click to collapse
I just tested this build and call noise still happen. Anyway, thanks for your work.
travis82 said:
compiling a N910U rom with our proprietary drivers and audio configs I'll put it out if it boots when its done compiling you can let me know the difference if any.
Test build N910U cm-13.0-20160102-UNOFFICIAL-trhpltexx
https://www.androidfilehost.com/?fid=24352994023704101
Click to expand...
Click to collapse
Thank you very much
After I install the 0102update base on 0101 , I found that the transition animation changed back to android 5.1.
I had to install dual zip with TWRP. use space in my sd to write the system. using dual patcher gave fails.
I was thinking: since we have an unlocked bootloader and custom roms, how hard would be to port AOSP Nougat?
There is any tecnical difficulty, like kernel version, that can block us?
Not much, I would imagine.
As far as I can tell, it'd just take a dev that's interested in putting in the effort.
Yes, this counts as my "yes, please" vote for Z00T.
I am votting with yes
I was thinking about do a try and compile it straight away, but i fear i'm not experienced enough to make something bootable
I don't think that the kernel or other thing will block it, but we got a custom ROM so late and I don't think we'll have a CM14 very soon
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Jhyrachy said:
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Click to expand...
Click to collapse
Umm, thanks for your thoughts about trying to bring N, it seem you got the answer yourself
from what i look at Z00L/T source, other than some fix and caf one, they could bring N to L/T with some borrowed libs. And looking from our source, I still found some line with L/T on it, so, yes, dev may bring N to this device, just hope that libs going to work with this devices.
But as you said, a fully fledged cm13 would be useful, using RR build for 3 days, and got the problem as they says. Plus, for me, front camera isn't working (called arclib or something, front camera effect when using asus camera, it's working fine with other camera because they didn't load that lib). Constant lag when using GPS other than "gps only" (might RR only problem). etc..
Either way, I hope that you could join the team (or, is he a one man army?) maintaining this device, fixing things come first, upgrade when everything is fine. At least "ok".
I don't know about AOSP, but many say choose CM because of CM broad compatibility layer. If that's true, then AOSP might slightly harder...
or... not really.
Sent from my ASUS_Z00RD using XDA Labs
Interesting, I'm not developer but I think this is possibke, Android 7.0 supports S410, maybe CM14 will better than AOSP.
yeah i still waiting ??
Sent from my ASUS_Z00ED using Tapatalk
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
I, but it will be possible tonight because now i working , phone at home
imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
i will try tomorrow ...good for this ??
Sent from my ASUS_Z00ED using Tapatalk
Some news?
waiting :victory:
Waiting for some USEFUL news.
Today I try to compile it, but do not know if I aim, because I'm not a developer and I have no experience, but I try the same, stay connected, sorry for my bad english
I can't download the sources because it me give an errore i can't compile a ROM,sorry
Still waiting for news.
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
kurnalcool said:
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
Click to expand...
Click to collapse
Hi! Could this help you in some way? I don't know how, but I hope there is something usefull. This is a link to a russian forum where CM13 for ZE500KL was first posted by his original creator. Is in russian but I think you can use google translate to read the forum http://4pda.ru/forum/index.php?showtopic=766921
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
There are lineage os builds for only tab s2 8.0 2015 models.
this version is stable without any known issues.
Root is not included here. For root install magisk or su-addon ( https://mirrorbits.lineageos.org/su/addonsu-14.1-arm-signed.zip )
install:
flash with twrp
don't forget to flash gapps ( opengapps.org ) you need version for android 7.1 arm
download:
20180102
t710: https://drive.google.com/open?id=1tkzdpZdGXNouu0ig-NHGErWfmUP_CICP
t715: https://drive.google.com/open?id=1cLX-gWvUM9miJ3JTmcnWeXrNxI0F3II5
test build 20180303 for t710 is here: https://forum.xda-developers.com/showpost.php?p=75756582&postcount=147
sources:
https://github.com/bonuzzz/android_kernel_samsung_gts2
https://github.com/bonuzzz/android_device_samsung_gts2-common
https://github.com/bonuzzz/android_device_samsung_gts28wifi
https://github.com/bonuzzz/android_device_samsung_gts28ltexx
https://github.com/bonuzzz/android_vendor_samsung_gts2-common
https://github.com/bonuzzz/android_vendor_samsung_gts28wifi
https://github.com/bonuzzz/android_vendor_samsung_gts28ltexx
WOW! This is the first build of Lineage that works great on my tab! Didn't test fingerprint but autobrightness and camera is working great. Thank a lot. On T710 by the way.
See my signature for twrp 3.1.1-0 for both gts28wifi and gts28ltexx.
Please note that twrp 3.2.0-0 has just been released! I'll be working on bringing it up to the Galaxy Tab S2 2015 tablets as soon as possible
On a related matter, I own a 9.7 wifi variant and I build for it daily. Netflix doesn't work with the official gts2-common repo, but if you use mine it will. I kept a long since abandoned fix which has worked very well in my builds.
Do we need gapps, thank you sooooooo much for this!!!!
Sent from my SM-T710 using Tapatalk
---------- Post added at 01:04 AM ---------- Previous post was at 12:45 AM ----------
ripee said:
See my signature for twrp 3.1.1-0 for both gts28wifi and gts28ltexx.
Please note that twrp 3.2.0-0 has just been released! I'll be working on bringing it up to the Galaxy Tab S2 2015 tablets as soon as possible
On a related matter, I own a 9.7 wifi variant and I build for it daily. Netflix doesn't work with the official gts2-common repo, but if you use mine it will. I kept a long since abandoned fix which has worked very well in my builds.
Click to expand...
Click to collapse
You sir, are a good among men, which gapps do you recommend? And we can install su manually whithout messing up the fixes you got to make this bad boy run? Once again thank you.
Sent from my SM-T710 using Tapatalk
lahegry said:
Do we need gapps, thank you sooooooo much for this!!!!
Sent from my SM-T710 using Tapatalk
---------- Post added at 01:04 AM ---------- Previous post was at 12:45 AM ----------
You sir, are a good among men, which gapps do you recommend? And we can install su manually whithout messing up the fixes you got to make this bad boy run? Once again thank you.
Click to expand...
Click to collapse
I flash pico on my phone and tablet, but even stock or higher should work if the builds are from official sources. I also recommend Magisk if you wish to root. If these builds have su root, Magisk simply uninstalls it before installing itself.
bonuzzz, you did what most (self proclaimed) devs failed to achieve and deliver for the T710/715 in the last months! i just installed the ROM and tried it out the last few hours. finally got a clean and reliable android for my T710.
it's working really smooth, no issues so far. everything - including bluetooth and fingerprint - is working perfectly [edit: haven't tried it, since not needed: according to some posts in this thread stock camera doesn't seem to be working properly]. i am really anstonished and amazed by this great initial release, thanks a lot. i hope you keep on delivering such a good work.
many thanks and best regards from germany
For me on my T710 the microphone did not work. So it isn't in perfect working order yet and the battery drains quite fast, but it's miles better than the previously shared builds here on XDA, and most certainly usable.
I also had issues with certain apps not working properly, so I ended up going back to stock for now. (more precisely: the Antutu 3D part and the Focus gallery application).
TWRP 3.2.0-0 for gts28wifi and gts28ltexx!
twrp-3.2.0-0-gts28wifi.img
twrp-3.2.0-0-gts28wifi.tar
twrp-3.2.0-0-gts28ltexx.img
twrp-3.2.0-0-gts28ltexx.tar
@ripee,
create your own topic please. dont spam here. thank you
bonuzzz said:
@ripee,
create your own topic please. dont spam here. thank you
Click to expand...
Click to collapse
Sorry if twrp is spam. Best of luck fiddling around with lineage recovery. For everyone's sake, I hope that Netflix works on your builds.
Thanks a lot for this build. An important progress for the T710/T715.
And also thx for the current TWRP link @ripee, missed that one.
Camera app force closed. Dont save any pictures
If you use a third party app like open camera, it actually works really well.
Either way, the microphone doesn't work at all, as in all roms for this device, and sadly it is a deal breaker for me since I use my tablet for video calls all the time.
azenyr said:
If you use a third party app like open camera, it actually works really well.
Either way, the microphone doesn't work at all, as in all roms for this device, and sadly it is a deal breaker for me since I use my tablet for video calls all the time.
Click to expand...
Click to collapse
open camera same problem.
My twrp recovery is old. I update this and I will try again
Having used this ROM for the last few days on a T710, I experienced a very stable system. UI was always smooth, no serious issues so far. :good:
However, I observed some strange behaviours/minor issues:
Fingerprint unlock isn't always working reliably. Sometimes, when trying to unlock the lockscreen, the finger on the fingerprint sensor doesn't seem to be detected and the PIN has to be entered manually.
LiveDisplay is not always active when the device comes from sleep and has to be unlocked. Upon the next sleep/active via short press on the power button iteration, the LiveDisplay mostly works as expected.
Once, presumably a wakelock drained the battery throughout the day until it was empty and the device turned itself off. I don't know why this happened and can't reproduce it.
Altogether a very successful start for this ROM, I will keep it on my device and hope the dev keeps on working on it to further improve it or even update to Lineage 15.x...
Thanks, @bonuzzz!
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img.tar
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img.tar
ripee said:
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img.tar
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img.tar
Click to expand...
Click to collapse
Hi! I tested gts28wifi for my SM-T700 but touch sensor is wrong. The interface is unusable for now. Best of luck. But you should start your own thread...
powerade001 said:
Hi! I tested gts28wifi for my SM-T700 but touch sensor is wrong. The interface is unusable for now. Best of luck. But you should start your own thread...
Click to expand...
Click to collapse
ripee said:
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
What would be the point of a dedicated thread if it doesn't work? Anyway, thanks for your feedback.
Click to expand...
Click to collapse
ripee said:
ripee said:
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
What would be the point of a dedicated thread if it doesn't work? Anyway, thanks for your feedback.
Click to expand...
Click to collapse
The point is,..
If your building it, wouldn't you want it all together so you could track it easier? Now you'll need to read all the threads that you've posted this into to find the results.
I know we all appreciate you doing this. But please make your own thread for it so we can all see what's going on. Without having to read through the 4+ threads this is in.
Keep it up. It's nice to see our tabs still getting some love. Thank you. ?
Click to expand...
Click to collapse
engine95 said:
ripee said:
The point is,..
If your building it, wouldn't you want it all together so you could track it easier? Now you'll need to read all the threads that you've posted this into to find the results.
I know we all appreciate you doing this. But please make your own thread for it so we can all see what's going on. Without having to read through the 4+ threads this is in.
Keep it up. It's nice to see our tabs still getting some love. Thank you.
Click to expand...
Click to collapse
Is it possible to make android oreo??
What are the basic requirements for it??
Click to expand...
Click to collapse
Discontinued.
Awaiting for thread deletion.
Thanks...Nice work after your miui 5 ROM
Help please..
Need someone who can risk his device by testing this ROM......
Happy holi.....
Happy holi my friends...
May this holi bring lots of Colors in your life!! and in mine too.
Kunal Gautam said:
Need someone who can risk his device by testing this ROM......
Click to expand...
Click to collapse
I tried to install but it gives error 7 i think update.script should be rechecked.
Deep_dhimaan said:
I tried to install but it gives error 7 i think update.script should be rechecked.
Click to expand...
Click to collapse
Thank you very much, i've understood whats the problem( as a pm by ashkineeeeee).
New update coming soon. Stay tuned.
Hey bros...
so there were some problem with permissions, it seems that it is fixed now..
Flash the ROM and review here....
----------------------edit 1---------------------
dont flash the rom now!!!
Some files are missing in boot.img
how stupid i am!!
------------------------edit 2-----------------------
Flash it now!
Last build not installed,error 7.
mels01 said:
Last build not installed,error 7.
Click to expand...
Click to collapse
Logs,screenshots?
Try installing from internal storage... Or update your recovery to the latest one by android andi...
Thanks!
Hey, I would like to help out, can I have the link to the ROM?
theportal2 said:
Hey, I would like to help out, can I have the link to the ROM?
Click to expand...
Click to collapse
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Links
Kunal Gautam said:
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Have you seen this CM 11? https://forum.xda-developers.com/galaxy-tab-2/7-inch-development/rom-cm-11-0-galaxy-tab-2-t3737392
Just made last month by @Deltadroid
Links are removed because *the ROM is not complete yet*.
Thanks, but I need to confirm a few things before I could use a ROM(includes init.d support and a bunch of other things). Also, it is very important that deltadroid provide me permission to use his ROM.
Thank you!
Regards,
KG
-----_edit_--------
I just saw deltadroid's thread, the title clearly says that the ROM is for p3110. I want to make a unified one. I need a ROM made with unified device tree.
If I do port, it will only work on p3110 and maybe on every 7" device. I don't want do this.
Sorry, but yeah thanks!
Just wait till 3 april 2018. Most probably I will upload.
Edit 2
Or I must say it an update. 75 percent of the work is done. Somehow I managed to get a base ROM(only I know how). Only build.prop editing and Updater script editing work left(these are the most difficult BTW).
Update coming soon. Stay tuned.
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Kunal Gautam said:
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Click to expand...
Click to collapse
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
secretwolf98 said:
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
Click to expand...
Click to collapse
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Kunal Gautam said:
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Click to expand...
Click to collapse
FYI, I port ROMs. It was pointers what to fix, if you wanted to get this ROM better, than it is already.
Kunal Gautam said:
(...)
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Android-Andi said:
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Click to expand...
Click to collapse
Thank you. For at least replying. You works will always be appreciated. Now, I am gonna close this thread. Thanks again!
I am not responsible for anything that happens to your device.
This is a port of MIUI 10 for the op6/6t
Flash at your own risk and make sure to check what's working. Logcats would be appreciated!
Instructions:
1: Flash OxygenOS 9.0.7 twice, this is very important
2: Extract the download somewhere
3: Run the OnePlus 6t flasher (make sure phone is still in fastboot/bootloader)
4: Reboot to TWRP (fastboot boot it if it dissapeared, if you install TWRP you must install Magisk)
5: Flash or adb sideload NFC fix that is included in the download
6: Reboot and install V4A Magisk module and enable headset and speaker, this fixes audio
7: Enjoy!
Download (v3):
MOD EDIT: LINK REMOVED
What works:
Everything except stuff in what doesn't work
What doesn't work:
NFC
Flashlight toggle (3rd party apps work)
MIUI camera (3rd party apps work)
Fingerprint (top priority - @nima0003 - me)
Audio fix #2:
Credits to @dougie313
Flash viper4android module
Grab root browser
Go to vendor\lib\soundfx folder and rename or delete all files in folder
Source code: https://github.com/OnePlusOSS/android_kernel_oneplus_sdm845
Credits: @nima0003 me @ProtoDeVNan0 for the current build
Dylan Neve
Omar
What is it based on? And will you keep working on it?
dennisbednarz said:
What is it based on? And will you keep working on it?
Click to expand...
Click to collapse
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)
nima0003 said:
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)
Click to expand...
Click to collapse
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?
dennisbednarz said:
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?
Click to expand...
Click to collapse
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.
nima0003 said:
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.
Click to expand...
Click to collapse
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier porting of features and so on? Would also make most kernels compatible.
Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??
champ784 said:
Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??
Click to expand...
Click to collapse
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.
dennisbednarz said:
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier portion of features and so on? Would also make most kernels compatible.
Click to expand...
Click to collapse
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.
nima0003 said:
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.
Click to expand...
Click to collapse
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start
I'm downloading to test, report back in a bit.
champ784 said:
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start
Click to expand...
Click to collapse
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...
nima0003 said:
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...
Click to expand...
Click to collapse
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!
champ784 said:
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!
Click to expand...
Click to collapse
Yeah same thing happened to my Xperia xc, I could only flash stock rom, not even rooted.
Flashing failed, error: invalid zip file format.
Dark Nightmare said:
Flashing failed, error: invalid zip file format.
Click to expand...
Click to collapse
Great, thank you, working on it.
You would be my hero
It is great to see other types of roms, instead of only los type roms. Great to switch between them over time.
nima0003 said:
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.
Click to expand...
Click to collapse
Hopefully not. Lot's of people prefer stock-based ROMs specifically for the reason that they're usually more stable, almost always better performant and always better for battery (with the exception of TouchWiz). And the whole feature thing is also useful.
Lot's of people base the ROMs of Lineage as it usually has hardware specific support, but as we don't have official lineage yet and it would still be a lesser experience than a stock ROM, I strongly advocate for the OOS base.
Wish I could help out but I'm not a developer. If you need something designed, contact someone at Xiaomi, OnePlus or Google, or if you need some piece of code some person is sitting on, let me know (on Twitter or Telegram @dennisbednarz as i don't use the forum DM system).
So basically you just ported the OS and want testers? As of now, OP6T is just 3 weeks old and hardly would anyone dare to try something that says 'I highly doubt it'll work' in the OP.
Can Not installed
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app