Wear 24 DevelopmentContributors: @JaredTamana, @davwheat
Current Status: ActiveCurrent Kernel Status: Building, NFC driver working but still potentially WIPSystem ROM Status: Still WIP. Current task: collecting/compiling files, modifying .jarsTHIS ROM IS NOT YET AVAILABLE TO DOWNLOAD AS AN END-USER ROM
This project has a few goals:
- Bringing NFC/Google Pay support to Wear24 [Feasible, main goal]
- Bringing system updates to the Wear24, ie System H [Probably doable, second goal]
- Adding/fixing functionality in the Wear24 (such as new radio bands, no cloud icon, etc) [Maybe possible but needs more research, low on the list)
- Other projects are being considered for the Wear24, but no news on them at this time.
Links
Social
Wear24Dev Blog, periodic updates on this project: http://wear24dev.blogspot.com
Wear24 NFC Discord, open chat so users can see us develop in real-time! Also, tech support. https://discord.gg/8XyTeUC
Development
Wear24-NFC-Kernel GitHub, this is our source for building the kernel. Instructions for building it yourself are in the README. https://github.com/davwheat/Wear24-NFC-Kernel
Travis-CI Build Logs for Kernel: https://travis-ci.org/davwheat/Wear24-NFC-Kernel
Wear24-NFC-ROM GitHub, will soon contain the files needed to make an image/zip, depending on how we decide to distribute. https://github.com/davwheat/Wear24-NFC-ROM
JaredTamana's GDrive dorado folder, may contain files you need: https://drive.google.com/drive/folders/1h6gz-oLMPZ90nwt7BLhWVgHii1DRCW5c
davwheat's GDrive dorado folder, may contain files you need: https://drive.google.com/drive/fold...droid-msm-dorado-3.18-nougat-mr1-wear-release
tetra release for enabling NFC: https://forum.xda-developers.com/sm...ony-smartwatch-3-nfc-support-package-t3219713
NXP Setup Guidelines: https://github.com/NXPNFCProject/NF...r/AN11762-Android_NXP_NFC_Setup_Guideline.pdf
Special Thanks
janjan: Dev guidance
@bensdeals: Donor, help
@yochanmarquos, u/lerxi: Development help.
-- RESERVED -- Because you never know
Someone should have a TWRP backup handy with the images you are looking for. Correct me if I'm wrong, but all the images you require are inside a TWRP backup image.
Anyone remember that Sony SW3 port thread? I'm not sure what happened to the project, but dev seems quiet and the device tree repos are gone. Was hoping to use those as a resource and it wasn't crawled by archive.org. Wonder if external forces got involved, which makes me a bit worried. If anyone has a clone of that repo, it might be really useful.
Please. I beg you to make this happen. Thanks for even trying
I'm definitely interested in this. If I knew I could get Google Pay working on this device, I would definitely buy one. I'll happily throw a few dollars your way too, if you can release something that works.
Hoping I found it
JaredTamana said:
Anyone remember that Sony SW3 port thread? I'm not sure what happened to the project, but dev seems quiet and the device tree repos are gone. Was hoping to use those as a resource and it wasn't crawled by archive.org. Wonder if external forces got involved, which makes me a bit worried. If anyone has a clone of that repo, it might be really useful.
Click to expand...
Click to collapse
Is this what you're looking for? (Sorry, I'm not allowed to post url yet so just remove space before .com)
github .com/FlorentRevest/android_device_sony_tetra
My Wear24 just came in from eBay . It's a really good looking device. I might be able to help you test at some stage. Also willing to donate ducats if you get far enough. Good Luck :good:
I got my wear24 a few months ago, and was slightly disappointed to find out about the lack of root, customization, etc. I'm still not a huge fan of opening it up, but I'm up for helping any other way I can!
YTSec said:
I got my wear24 a few months ago, and was slightly disappointed to find out about the lack of root, customization, etc. I'm still not a huge fan of opening it up, but I'm up for helping any other way I can!
Click to expand...
Click to collapse
I appreciate the thought, but doing anything in the vein of system modification will require opening the watch. Luckily, the pinout is right under the back cover, so chances of damaging the watch are minimal. If you change your mind, let me know.
** NEWS **
Semi-daily updates will be going on this Blogger Page so I don't clog up the thread
http://wear24dev.blogspot.com
Hi, can i flash this rom to zte quartz 2017?
Hi, can i flash this rom to zte quartz 2017?
Eshal said:
Hi, can i flash this rom to zte quartz 2017?
Click to expand...
Click to collapse
Eshal, this ROM hasn't even been built yet. I cannot guarantee compatibility with your device because I'm not building for your device. You can try flashing whatever you like, but I'm not liable for your device.
This ROM is still in its first steps and I quite literally have nothing to release yet. I've just finished bringing backups over to my PC.
JaredTamana said:
I appreciate the thought, but doing anything in the vein of system modification will require opening the watch. Luckily, the pinout is right under the back cover, so chances of damaging the watch are minimal. If you change your mind, let me know.
Click to expand...
Click to collapse
I took a look, it's not as bad as I thought. Its probably worth unlocking the bootloader anyway! I'll let you know tomorrow if I do.
YTSec said:
I took a look, it's not as bad as I thought. Its probably worth unlocking the bootloader anyway! I'll let you know tomorrow if I do.
Click to expand...
Click to collapse
Glad to hear it! Make sure to read the main thread as to tips on how to do it. Use lots of heat, and don't forget the Y000 (0.6) screwdriver.
Kernel builds are now passing, and I've begun debugging the boot process. More info on the Blogspot
Sorry for the late reply, I'm just waiting on a toolkit that works on it, then I'll start ripping it apart to help out! Also, I got that new UI which is great.
How goes the testing? I've noticed that there haven't been any new posts on the blog or on this thread. Hope everything is well
@JaredTamana Have you seen this? BLOCKS announces Project OpenWatch: an Android Oreo-based OS for smartwatches in collaboration with CarbonROM and LineageOS
Here's their GitHub.
VlitalityX said:
How goes the testing? I've noticed that there haven't been any new posts on the blog or on this thread. Hope everything is well
Click to expand...
Click to collapse
Hiya! Sorry for the lack of updates. I've hit a wall with that Binder error. All documentation online seems to be about x86 machines and ranges from IO errors to SELinux errors. I've already tried compiling without SELinux in a few different ways to no avail. I've tried contacting development channels on IRC, but no one seems to have the answers I need (most times I don't even get a reply...)
I'm still brainstorming. I took a look at the kmsg from the stock build and there's a LOT being sent to logs there that isn't from my kernel. I'm not sure where to go next, and I don't want to go knocking on the door of every single developer that might know the answer. The problem is the Binder errors are so vague about what's causing the failed transaction that I can't even start to understand what's wrong.
yochananmarqos said:
@JaredTamana Have you seen this? BLOCKS announces Project OpenWatch: an Android Oreo-based OS for smartwatches in collaboration with CarbonROM and LineageOS
Here's their GitHub.
Click to expand...
Click to collapse
Thanks! I do remember seeing this. Problem is, if I can't even build a stock kernel, nothing else can be done. I need the device booting first before I can move to system changes.
Related
So I've been troubleshooting all morning with modifying our device tree + OmniROM source to be able to attempt a jflteatt build of the new ROM, and I finally have my build compiling as I write this.
However, based on the trouble I've had getting the grouper (N7) build to boot - it compiled just fine - I'm doubting that I'll be able to get our device's build booted on the first try either (assuming this build finishes without error).
As such, I wanted to reach out to you guys to see if anyone else is currently working on building this ROM - and hopefully create a place where we can share tips or troubleshoot for our specific devices.
I apologize if this is the wrong forum to post this in, but I figured if I posted this in any of the main forums it would get flooded with "plz build for Sprint S4" or "ETA plz?" posts....lol.
http://forum.xda-developers.com/showthread.php?t=2483622
Grarak might be able to help...
DSA said:
http://forum.xda-developers.com/showthread.php?t=2483622
Grarak might be able to help...
Click to expand...
Click to collapse
Thanks....I saw that thread, but figured that the chipsets are different enough that it wouldn't be of that much use. Am I off-base there?
CPA Poke said:
Thanks....I saw that thread, but figured that the chipsets are different enough that it wouldn't be of that much use. Am I off-base there?
Click to expand...
Click to collapse
no your in the right forum, and yes your also right that that omnirom thread, while semi useful, isnt the best since our processors are different and what works for them might not work for us. Looking forward to watching this develop though,
Do you mean porting from source?
CNexus said:
Do you mean porting from source?
Click to expand...
Click to collapse
Of course. I guess "port" probably wasn't the best verbiage...more precisely, adding our device tree to the OmniROM source
There's a write up on xda-university on porting from source. Might wanna take a look at it
I'm not sure what the point of this thread is though. No point discussing it if you haven't even tried it/reached a compile/runtime error
CNexus said:
There's a write up on xda-university on porting from source. Might wanna take a look at it
I'm not sure what the point of this thread is though. No point discussing it if you haven't even tried it/reached a compile/runtime error
Click to expand...
Click to collapse
That guide was my main starting point with all of this, actually...however I'm thinking that it was written by someone who's first language is something other than English, as I always end up getting lost midway through because I literally can't figure out what he/she is trying to say.
And I've been at work all day but managed to remote in to my home PC a couple times - both times discovering that the build had failed, and both times attempting to troubleshoot each error. I was planning on posting the error and my roomservice.xml (as I suspect it's probably where I'm going wrong), so I'll post them shortly.
CPA Poke said:
That guide was my main starting point with all of this, actually...however I'm thinking that it was written by someone who's first language is something other than English, as I always end up getting lost midway through because I literally can't figure out what he/she is trying to say.
And I've been at work all day but managed to remote in to my home PC a couple times - both times discovering that the build had failed, and both times attempting to troubleshoot each error. I was planning on posting the error and my roomservice.xml (as I suspect it's probably where I'm going wrong), so I'll post them shortly.
Click to expand...
Click to collapse
I don't know your circumstances, but I was able to understand the guide perfectly and my first language is english.
It might be better if you take to the OmniROM irc chat (#omni for dev chat) and say you're trying to add support for your device and just list the error you're getting.
CNexus said:
I don't know your circumstances, but I was able to understand the guide perfectly and my first language is english.
It might be better if you take to the OmniROM irc chat (#omni for dev chat) and say you're trying to add support for your device and just list the error you're getting.
Click to expand...
Click to collapse
Haha, my "circumstances" are that I'm am accountant (see my user name) and I tend to over analyze things and create problems where there are none.
I'm also trying as hard as I can to learn as much as I can, all the while trying not to bother the real devs...but I'm late to the Android game (relatively) and it seems to me that the distribution of users on XDA is pretty polarizing - either they are (a) seasoned devs who either have prior/current experience in programming or have some type of IT background, or (b) are useless, ungrateful noobs who just got rid of their iPhone yesterday and now want to go bonkers hacking their device. At least those users that actually post.
So my problem thus far (and the main reason why I thought this was the most appropriate forum to have this discussion) is that, in the year that I've been on here, I've had a hard time finding any material for folks like me...people who enjoy LEARNING (not just typing a problem and having someone fix it for them), enjoy exploring the extent that our awesome technology can be taken to, and are genuinely interested in being a "seeder" - not a "leecher" - in the development community.
So, again, I apologize if this doesn't belong here. I did read the rules sticky before even starting the OP (imagine that lol), and I guess my interpretation was that this sort of discussion would be welcome. I wasn't asking anyone to fix my problems, I wasn't asking for ETAs...I just wanted to offer up a medium for discussion for anyone interested.
But I will check out the irc. Good idea, thanks.
've been working on it with all the necessary file (so i think). One of my team mates help me out with jf tree but havn' had any successful build yet. usually get an error when its close to being finish so have to troubleshoot one fail build at a time
I dont know why you need to run of to the omini irc and abandon this one...i believe in team work. the IRC is a lot of help they help me t roubleshoot my way through...at the same time will be nice to have a discussion among individuals who actually uses our device. the people i've met in the irc do not use gs4 or any form of it from what i saw
CPA Poke said:
Haha, my "circumstances" are that I'm am accountant (see my user name) and I tend to over analyze things and create problems where there are none.
I'm also trying as hard as I can to learn as much as I can, all the while trying not to bother the real devs...but I'm late to the Android game (relatively) and it seems to me that the distribution of users on XDA is pretty polarizing - either they are (a) seasoned devs who either have prior/current experience in programming or have some type of IT background, or (b) are useless, ungrateful noobs who just got rid of their iPhone yesterday and now want to go bonkers hacking their device. At least those users that actually post.
So my problem thus far (and the main reason why I thought this was the most appropriate forum to have this discussion) is that, in the year that I've been on here, I've had a hard time finding any material for folks like me...people who enjoy LEARNING (not just typing a problem and having someone fix it for them), enjoy exploring the extent that our awesome technology can be taken to, and are genuinely interested in being a "seeder" - not a "leecher" - in the development community.
So, again, I apologize if this doesn't belong here. I did read the rules sticky before even starting the OP (imagine that lol), and I guess my interpretation was that this sort of discussion would be welcome. I wasn't asking anyone to fix my problems, I wasn't asking for ETAs...I just wanted to offer up a medium for discussion for anyone interested.
But I will check out the irc. Good idea, thanks.
Click to expand...
Click to collapse
Your discussion is welcome here. I completely understand your dilemma. But if you are having issues it might be beneficial to post the specific issue you're having instead of trying to promote discussion in this thread. Im sure if you asked someone they would explain how they got to the solution of the problem.
Sent from my XT912 using xda app-developers app
CPA Poke said:
Haha, my "circumstances" are that I'm am accountant (see my user name) and I tend to over analyze things and create problems where there are none.
I'm also trying as hard as I can to learn as much as I can, all the while trying not to bother the real devs...but I'm late to the Android game (relatively) and it seems to me that the distribution of users on XDA is pretty polarizing - either they are (a) seasoned devs who either have prior/current experience in programming or have some type of IT background, or (b) are useless, ungrateful noobs who just got rid of their iPhone yesterday and now want to go bonkers hacking their device. At least those users that actually post.
So my problem thus far (and the main reason why I thought this was the most appropriate forum to have this discussion) is that, in the year that I've been on here, I've had a hard time finding any material for folks like me...people who enjoy LEARNING (not just typing a problem and having someone fix it for them), enjoy exploring the extent that our awesome technology can be taken to, and are genuinely interested in being a "seeder" - not a "leecher" - in the development community.
So, again, I apologize if this doesn't belong here. I did read the rules sticky before even starting the OP (imagine that lol), and I guess my interpretation was that this sort of discussion would be welcome. I wasn't asking anyone to fix my problems, I wasn't asking for ETAs...I just wanted to offer up a medium for discussion for anyone interested.
But I will check out the irc. Good idea, thanks.
Click to expand...
Click to collapse
I understand, I've been through the exact same thing (and am still usually unable to find help on things like source building and kernels). I was not trying to discredit your post, just
And by "circumstances" I meant whatever language/languages you know, or background you come from, etc etc that lead you to have trouble understanding the xda-university write-up.
No offense was intended, but it does help to fix errors when you post the error you're getting lol.
Surge1223 said:
Your discussion is welcome here. I completely understand your dilemma. But if you are having issues it might be beneficial to post the specific issue you're having instead of trying to promote discussion in this thread. Im sure if you asked someone they would explain how they got to the solution of the problem.
Sent from my XT912 using xda app-developers app
Click to expand...
Click to collapse
CNexus said:
I understand, I've been through the exact same thing (and am still usually unable to find help on things like source building and kernels). I was not trying to discredit your post, just
And by "circumstances" I meant whatever language/languages you know, or background you come from, etc etc that lead you to have trouble understanding the xda-university write-up.
No offense was intended, but it does help to fix errors when you post the error you're getting lol.
Click to expand...
Click to collapse
Absolutely agreed. Honestly I was trying to be as non-noob as possible and wanted to try and work through as many of the errors related to syntax, etc on my own, saving the real discussion for the thread.
I'm going to take a look at this for jfltespr this weekend. I'll start adding my notes here as well.
garwynn said:
I'm going to take a look at this for jfltespr this weekend. I'll start adding my notes here as well.
Click to expand...
Click to collapse
I've been working on JFLTEATT for a bit, very, very frustrating since CM's selinux and AOSP selinux are very different. causing a LOT of build issues.
take a look at my github, you'll be able to fork my
android_kernel_samsung_jf
android_device_samsung_jf-common
device trees
https://github.com/jakew02
hopefully this gives you a head-start.
I should have a build up for jflteatt within the next few hours , by tonight im hoping.
Update So, i got a booting build. just needs to be fine-tuned to actually work!
jakew02 said:
I've been working on JFLTEATT for a bit, very, very frustrating since CM's selinux and AOSP selinux are very different. causing a LOT of build issues.
take a look at my github, you'll be able to fork my
android_kernel_samsung_jf
android_device_samsung_jf-common
device trees
https://github.com/jakew02
hopefully this gives you a head-start.
I should have a build up for jflteatt within the next few hours , by tonight im hoping.
Update So, i got a booting build. just needs to be fine-tuned to actually work!
Click to expand...
Click to collapse
Seriously? That's great! I appreciate the PM's btw.
Did you run into this error at all during your compile?
Code:
Install: /home/dev/omni/out/target/product/jflteatt/system/usr/share/zoneinfo/tzdata
/home/dev/omni/out/host/linux-x86/bin/checkpolicy: *loading policy configuration from /home/dev/omni/out/target/product/jflteatt/obj/ETC/sepolicy_intermediates/policy.conf
Install: /home/dev/omni/out/target/product/jflteatt/root/fstab.qcom
device/samsung/jf-common/sepolicy/property.te":2:ERROR 'duplicate declaration of type/attribute' at token ';' on line 6889:
#line 1 "device/samsung/jf-common/sepolicy/property.te"
type bluetooth_prop, property_type;
checkpolicy: *error(s) encountered while parsing configuration
make: *** [/home/dev/omni/out/target/product/jflteatt/obj/ETC/sepolicy_intermediates/sepolicy] Error 1
make: *** Waiting for unfinished jobs....
Edit: Forked your device trees, and syncing now. While that's downloading, I'm curious what "fine tuning" you're referring to? Are you having NFC/bluetooth issues by chance?
I remember reading in the i9500 thread that @Grarak was having issues with bluetooth.
CPA Poke said:
Seriously? That's great! I appreciate the PM's btw.
Did you run into this error at all during your compile?
Code:
Install: /home/dev/omni/out/target/product/jflteatt/system/usr/share/zoneinfo/tzdata
/home/dev/omni/out/host/linux-x86/bin/checkpolicy: *loading policy configuration from /home/dev/omni/out/target/product/jflteatt/obj/ETC/sepolicy_intermediates/policy.conf
Install: /home/dev/omni/out/target/product/jflteatt/root/fstab.qcom
device/samsung/jf-common/sepolicy/property.te":2:ERROR 'duplicate declaration of type/attribute' at token ';' on line 6889:
#line 1 "device/samsung/jf-common/sepolicy/property.te"
type bluetooth_prop, property_type;
checkpolicy: *error(s) encountered while parsing configuration
make: *** [/home/dev/omni/out/target/product/jflteatt/obj/ETC/sepolicy_intermediates/sepolicy] Error 1
make: *** Waiting for unfinished jobs....
Edit: Forked your device trees, and syncing now. While that's downloading, I'm curious what "fine tuning" you're referring to? Are you having NFC/bluetooth issues by chance?
I remember reading in the i9500 thread that @Grarak was having issues with bluetooth.
Click to expand...
Click to collapse
bluetooth should be fixed now
https://github.com/omnirom/android_...mmit/62d71414709f0f6282b8d108cc66716f37872f96
btw remove selinux union
then it should build correct
Grarak said:
bluetooth should be fixed now
https://github.com/omnirom/android_...mmit/62d71414709f0f6282b8d108cc66716f37872f96
btw remove selinux union
then it should build correct
Click to expand...
Click to collapse
MONEY, thanks my friend.
CPA Poke said:
Seriously? That's great! I appreciate the PM's btw.
Did you run into this error at all during your compile?
Code:
Install: /home/dev/omni/out/target/product/jflteatt/system/usr/share/zoneinfo/tzdata
/home/dev/omni/out/host/linux-x86/bin/checkpolicy: *loading policy configuration from /home/dev/omni/out/target/product/jflteatt/obj/ETC/sepolicy_intermediates/policy.conf
Install: /home/dev/omni/out/target/product/jflteatt/root/fstab.qcom
device/samsung/jf-common/sepolicy/property.te":2:ERROR 'duplicate declaration of type/attribute' at token ';' on line 6889:
#line 1 "device/samsung/jf-common/sepolicy/property.te"
type bluetooth_prop, property_type;
checkpolicy: *error(s) encountered while parsing configuration
make: *** [/home/dev/omni/out/target/product/jflteatt/obj/ETC/sepolicy_intermediates/sepolicy] Error 1
make: *** Waiting for unfinished jobs....
Edit: Forked your device trees, and syncing now. While that's downloading, I'm curious what "fine tuning" you're referring to? Are you having NFC/bluetooth issues by chance?
I remember reading in the i9500 thread that @Grarak was having issues with bluetooth.
Click to expand...
Click to collapse
No it boots up.. Shows the boot animation, the capacitative buttons light up and vibrate on touch, but the screen stays black and it eventually force reboots. i originally used CyanogenMod trees but decided to rebase to these device trees.https://github.com/AOSP-S4, but running into errors again.
I PM'd task and he said that he already has it up and running and there's no need to port,, just sync add device trees and build.. but when i did that i ran into about a million build failures that i had to manually fix, hence the github
Update: so based on what task said, I'm going to try just creating my own device tree, basing off of cyanogenmod's very first commit for jflteatt , jf-common , and kernel_samsung_jf. here goes nothing
Sent from my SGH-I337 using Tapatalk
CarbonDev said:
About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained whenever possible and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Click to expand...
Click to collapse
These builds are for the Samsung Galaxy Player 5.0.
Models:
YP-G70
Download: meticulus.co.vu
GApps here
NEW Update!
update: http://www.meticulus.co.vu/2016/08/carbon-lp-511-for-galaxy-player-5_19.html
-Effing Compass fixed! :highfive:
- Screen record fixed. :good:
- Torch fixed. :good:
Meticulus said:
update: http://www.meticulus.co.vu/2016/08/carbon-lp-511-for-galaxy-player-5_19.html
-Effing Compass fixed! :highfive:
- Screen record fixed. :good:
- Torch fixed. :good:
Click to expand...
Click to collapse
Hi Meticulus,
I have a new phone now so haven't been around on this forum for quite some time, but it suddenly occurred to me that I might be able to breath new life into my old sgp5 by using it as a media hub connected to a hard drive and an amplifier.
Im Using your 4.4.4 carbon room at the moment and after a bit of monkeying around I came to the conclusion that USB otg is not implemented. (Was it just a wild dream I had that you sorted that out years ago?).
Anyway, I was wondering whether you had any ambitions of implementing it in 5.1.(I know all about the necessary y splitter cable etc and as a fixed home media hub this would cause no disadvantage).
I'd love to get my sgp back on the road again.
What do you think?
Mmmm-) said:
Hi Meticulus,
I have a new phone now so haven't been around on this forum for quite some time, but it suddenly occurred to me that I might be able to breath new life into my old sgp5 by using it as a media hub connected to a hard drive and an amplifier.
Im Using your 4.4.4 carbon room at the moment and after a bit of monkeying around I came to the conclusion that USB otg is not implemented. (Was it just a wild dream I had that you sorted that out years ago?).
Anyway, I was wondering whether you had any ambitions of implementing it in 5.1.(I know all about the necessary y splitter cable etc and as a fixed home media hub this would cause no disadvantage).
I'd love to get my sgp back on the road again.
What do you think?
Click to expand...
Click to collapse
Otg IS implemented, its just Y-cable otg and it has never been tested and might need a little work to get it fully operational...
Mmmm-) said:
Hi Meticulus,
I have a new phone now so haven't been around on this forum for quite some time, but it suddenly occurred to me that I might be able to breath new life into my old sgp5 by using it as a media hub connected to a hard drive and an amplifier.
Im Using your 4.4.4 carbon room at the moment and after a bit of monkeying around I came to the conclusion that USB otg is not implemented. (Was it just a wild dream I had that you sorted that out years ago?).
Anyway, I was wondering whether you had any ambitions of implementing it in 5.1.(I know all about the necessary y splitter cable etc and as a fixed home media hub this would cause no disadvantage).
I'd love to get my sgp back on the road again.
What do you think?
Click to expand...
Click to collapse
You need this app too. App is old and may have selinux trouble.
setenforce 0
http://forum.xda-developers.com/showthread.php?t=1468531
Meticulus said:
You need this app too. App is old and may have selinux trouble.
setenforce 0
http://forum.xda-developers.com/showthread.php?t=1468531
Click to expand...
Click to collapse
Ahh, Thanks for the info.
Using USB Host Controller I get a promising result on the info screen, but not so promising on the USB screen (see screenshots).
I don't know whether this is a problem with what I'm doing or a problem with the ROM.
Do you have any idea?
Hi,
I'm now on stock GB 2.3.6 on my YP-G70 (int version) and i'm looking for a slimest and fastest build. What do you suggest? I'd like camera to be working as well as Gapps and GPlay working. I'm looking on your page Meticulus, but I don't know if Carbon LP 5.1.1 is the right decision or should I try any other build? Thanks in advice for your suggestion. Also a step-by-step update instruction for newbies is welcome
tss555 said:
Hi,
I'm now on stock GB 2.3.6 on my YP-G70 (int version) and i'm looking for a slimest and fastest build. What do you suggest? I'd like camera to be working as well as Gapps and GPlay working. I'm looking on your page Meticulus, but I don't know if Carbon LP 5.1.1 is the right decision or should I try any other build? Thanks in advice for your suggestion. Also a step-by-step update instruction for newbies is welcome
Click to expand...
Click to collapse
Carbon LP 5.1.1 does not perform well in some situations. I run this ROM without gapps and for the things I do (SD quality video mostly), it runs OK. This ROM won't be for everyone.
It's hard to say, KitKat ROM's are the most functional; meaning I've put the most work into making all the hardware and software function properly. KitKat ROM's are definitely faster than LP. ICS and JB ROM's would probably be faster but also a little more out of date and a little less functional.
I have written extremely detailed instructions for installing Carbon ROM (KitKat).
here: http://www.meticulus.co.vu/p/carbon-rom-for.html
There is a line that says "If you are comming from stock..." with a link that says what you need to do if you are on stock.
Mmmm-) said:
Ahh, Thanks for the info.
Using USB Host Controller I get a promising result on the info screen, but not so promising on the USB screen (see screenshots).
I don't know whether this is a problem with what I'm doing or a problem with the ROM.
Do you have any idea?
Click to expand...
Click to collapse
Can you post dmesg/kmsg output while plugging in otg cable with device connected? Oh, and are you connecting a thumb drive and does it show evidence that it powers up?
I do not have a Y-Cable so I was never able to test and at the time no one seemed interested in this but if you'll keep workin' with me, perhaps we can get this working properly. I did test it enough to see that the usb device was recognized in dmesg even without power...
You might also check /dev folder and see if anything new appears like "sda or sda1". If so you might be able to mount it the standard linux way.
mount -t auto /dev/sda1 /storage/usbdisk
Meticulus said:
I have written extremely detailed instructions for installing Carbon ROM (KitKat).
here: http://www.meticulus.co.vu/p/carbon-rom-for.html
Click to expand...
Click to collapse
Thank you very much Meticulus, I'll try your Carbon ROM (KitKat) on sunday . I'll have enough free time then.
I've installed carbon ROM 4.4.4 (CARBON-KK-UNOFFICIAL-20141107-1920-venturi) afew days ago. also installed this ROM (CARBON-5.1.1-METICULUS-20160705-1413-venturi) and its updates yesterday.
In both cases, the camera quality is extremely low.
What can I do to maximize camera quality?
In addition, because there is little space impossible to install gapps.
Does this ROM Support moving apps to SD card?
sattar.ray said:
I've installed carbon ROM 4.4.4 (CARBON-KK-UNOFFICIAL-20141107-1920-venturi) afew days ago. also installed this ROM (CARBON-5.1.1-METICULUS-20160705-1413-venturi) and its updates yesterday.
In both cases, the camera quality is extremely low.
What can I do to maximize camera quality?
In addition, because there is little space impossible to install gapps.
Click to expand...
Click to collapse
Those who have followed development for the past 4-5 years know, but for those that are new, I have outlined the challenges with the camera here:
http://www.meticulus.co.vu/2016/08/carbon-lp-511-for-galaxy-player-5_19.html
In short, there is nothing you can do to improve the quality of the camera on this ROM. I camera image quality is important to you, your only real option is stock. Working on the camera is frustrating but I continue to try from time to time.:highfive:
If you install the smallest gapps, there is sufficient space. I know, I have done it.:good:
This is the exact package I have been using...
https://www.androidfilehost.com/?fid=96039337900114811
XAN_ said:
Does this ROM Support moving apps to SD card?
Click to expand...
Click to collapse
Yes it does...:good:
Meticulus
Hello, welcome back!
Meticulus said:
Can you post dmesg/kmsg output while plugging in otg cable with device connected? Oh, and are you connecting a thumb drive and does it show evidence that it powers up?
I do not have a Y-Cable so I was never able to test and at the time no one seemed interested in this but if you'll keep workin' with me, perhaps we can get this working properly. I did test it enough to see that the usb device was recognized in dmesg even without power...
You might also check /dev folder and see if anything new appears like "sda or sda1". If so you might be able to mount it the standard linux way.
mount -t auto /dev/sda1 /storage/usbdisk
Click to expand...
Click to collapse
Hello again Meticulus.
I've only just managed to find time to reply! Things are hectic...
I think although working together to fix it sounds great, in practice It might literally take forever because I'm just super busy at work at the moment. What you need is a cable right? If I donated some money for you to get a cable would that work?
I feel really annoyed that I can't find time to help out, and a little guilty... but I really can't...
What do you think?
Mmmm-) said:
Hello again Meticulus.
I've only just managed to find time to reply! Things are hectic...
I think although working together to fix it sounds great, in practice It might literally take forever because I'm just super busy at work at the moment. What you need is a cable right? If I donated some money for you to get a cable would that work?
I feel really annoyed that I can't find time to help out, and a little guilty... but I really can't...
What do you think?
Click to expand...
Click to collapse
Thank you for your offer. Another person donated and I already order a cable. It'll be here in a week or so...
Meticulus said:
Thank you for your offer. Another person donated and I already order a cable. It'll be here in a week or so...
Click to expand...
Click to collapse
Ooh fantastic, looking forward to hearing what you discover.
The sultan kernel had it working long long ago if you need any pointers (although ntfs never worked for me).
Hi
every time I power on on Galaxy YP-G70 (meticulus 5.1.1) i found in interal storage and SD Card several directory LOST with strange name,
is normal?
giuleppe said:
Hi
every time I power on on Galaxy YP-G70 (meticulus 5.1.1) i found in interal storage and SD Card several directory LOST with strange name,
is normal?
Click to expand...
Click to collapse
No it's not normal, I have found this is due to Overclocking... Back up your data... Dial down your OC!
Why is there such alot more development and forum activity on for example the Xiaomi Redmi phones than on this one? The p9000 got excellent hardware for a great price but the community is really small somehow and the software is still buggy? How come? Do you think its still worth to wait for more activity and responses from developers for this phone or is it a "dead cow" already and better to swap to another brand to get support from developers on for example CM or RR?
furchtlos76 said:
Why is there such alot more development and forum activity on for example the Xiaomi Redmi phones than on this one? The p9000 got excellent hardware for a great price but the community is really small somehow and the software is still buggy? How come? Do you think its still worth to wait for more activity and responses from developers for this phone or is it a "dead cow" already and better to swap to another brand to get support from developers on for example CM or RR?
Click to expand...
Click to collapse
Development for this device is far from dead, we have a stable device tree for building custom ROM's, CM and RR ROM's already released, a fully source built TWRP and work on custom kernels is just beginning. That's a lot more development already than an awful lot of devices see in their entire lifetime.
I would rather say it has just begun. Development for this MTK chip is not a matter of course and the outcome so far is pretty exciting. This opens the way for other devs who work on other devices with the same chipset. It's just that many devs simply prefer Snapdragon which leads to higher dev count on those devices, faster bug fixing etc. I am pretty excited what the future brings not only for our P9000 but MTK devices in general as far as flashing and development goes.
Development is dead? What gave you that impression? For starter this phone already has a working twrp recovery. That is more then some Chinese phones get in their whole lifetime. Kernels is the area of development next and elephone has been kind to release the source code for the phone. Again more then most developers even bother with.
well, it got twrp,root and xposed working. More than some name brand phones that stop official updates after a year.
But i admit it is easier to update my old nexus 4 with cm downloader. Just click the update notification and latest cm gets installed.
It is also getting nougat in November hopefully
mangoman said:
well, it got twrp,root and xposed working. More than some name brand phones that stop official updates after a year.
But i admit it is easier to update my old nexus 4 with cm downloader. Just click the update notification and latest cm gets installed.
Click to expand...
Click to collapse
That's because Nexus 4 is an officially supported device by CM.
It's very difficult for MTK devices in general to get official CM support because we have to patch some things in the framework to make camera, RIL (mobile data) etc working.
The official stance is that these things should be done in device tree as no proprietary code is allowed in CM framework.
Initially when our patches were submitted to CM Gerrit they were rejected because of this, Leskal is working on minimising the patch work needed and getting more of the generic MTK code accepted on Gerrit.
Not helped by the fact that MTK themselves aren't helpful or willing to support developers as it doesn't suit their replace and force upgrade business model. Technically how they operate and their refusal to release official development tools or code is a violation of the open sources nature of Android. But google has yet to do anything serious about it. As far as I know, any code we have is from reverse engineering and leaks.
Android-UK said:
Not helped by the fact that MTK themselves aren't helpful or willing to support developers as it doesn't suit their replace and force upgrade business model. Technically how they operate and their refusal to release official development tools or code is a violation of the open sources nature of Android. But google has yet to do anything serious about it. As far as I know, any code we have is from reverse engineering and leaks.
Click to expand...
Click to collapse
Not true, I've met up with MTK engineers at DevCon and they do actually encourage development, they just seem to lately be wanting to protect their HAL's and drivers which as pointed out on the XDA portal article about this is sort of ridiculous. But then again it's proprietary code and not under the GPL so whilst we can say it's stupid we can't really contest it, it's their choice.
The code we have is completely official and not gotten from reverse engineering.
Jonny said:
Not true, I've met up with MTK engineers at DevCon and they do actually encourage development, they just seem to lately be wanting to protect their HAL's and drivers which as pointed out on the XDA portal article about this is sort of ridiculous. But then again it's proprietary code and not under the GPL so whilst we can say it's stupid we can't really contest ot, it's their choice.
The code we have is completely official and not gotten from reverse engineering.
Click to expand...
Click to collapse
I have seen many a leak before. But OK they support developing but at the same time they don't help provide any decent tools for troubleshooting or development.
Android-UK said:
I have seen many a leak before. But OK they support developing but at the same time they don't help provide any decent tools for troubleshooting or development.
Click to expand...
Click to collapse
Why do they need to? There's already great tools around for that, I know Qualcomm certainly used to provide a package for debugging the lower system levels but it wasn't widely available as the lower levels of the device booting process are not needed to be modified outside of OEM labs and manufacturing.
The lowest level we need is kernel debugging and the kernel already provides that via last_kmsg and desmsg etc, all other tools are already available as part of ADB, logcat etc. There are also a plethora of other tools readily available.
I would call it pretty dead now Well, if not dead then dying.
Let's hope for a Christmas special
So I really don't know what's going on and what's happening behind the stage.
Obviously alonsoj636 decided to discontinue and abandon his greatly admired LineageOS builds from the past months.
I haven't found any notes or statements as to why he finally has decided to do so and I was not able to reach him on xda because he blocked PMs. If you read this, maybe you want to be so kind and give us some hints what's happened!
Anyway...
we, as the RM10 LineageOS community, have to face reality and that means: currently there is no LineageOS rom build and maintained by anybody. That either means sticking with old versions, changing ROMs/GSI or switching the phone completely.
While alonsoj636's versions are still working very well, they eventually become outdated sometime.
This thread should be used to coordinate discussions about future LineageOS development (if there is enough interest and people).
You have 3 options.
Wait for another builder to pick it up
Build it yourself
Run Lineage GSI from AndyYan (guide here)
One more thing. Building a ROM for a device is never considered a development. What you're referring to, is maintenance. Lineage's development will never stop.
Alright, so the cat is out of the bag on this one:
While I'm really happy that Alonso kept maintaining the ROM for a while, the reality is that he wasn't interested to go official anytime soon and kept being vague about it.
As for me, I'm building up the courage to do MPK99 recommendation and go with GSI. Apparently GSI works like old ROMs, and it doesn't nuke TWRP, so that seems nice.
Try GSI. It's perfect.
MPK99 said:
You have 3 options.
Wait for another builder to pick it up
Build it yourself
Run Lineage GSI from AndyYan (guide here)
One more thing. Building a ROM for a device is never considered a development. What you're referring to, is maintenance. Lineage's development will never stop.
Click to expand...
Click to collapse
I'm pretty aware of that, however all new ROMs are tagged as development on this xda forum so I used this wording.
I think all 3 mentioned options are valid.
I could build it myself, however the time is the problem. Finding someone else building lineage in the future seems to be difficult. The past showed there aren't as many people interested and even less have the time and skill to build it.
GSI sounds like a wonder bag to me. while it's great to always have the latest updates, it might lack of the features LineageOS had for years. (i think of things like os-level online permission per app (wifi/cell), permission center, etc.). you can workaround that with 3rd party tools maybe, but it's cumbersome again.
Also GSi still sounds like a bit of an unpolished OS for this specific phone, with some kind of bugs and lack of features (compared to LOS). it's everybodys own decision to put priority on either that or on latest updates, though.
I might as well give it a try sometime, but I'll need enough spare time for experiments, so it won't happen soon.
my hopes are low, but maybe someone will step up and also build new LOS roms in the future.
Zirila said:
however all new ROMs are tagged as development on this xda forum
Click to expand...
Click to collapse
They're all namesake
Zirila said:
it might lack of the features LineageOS had for years
Click to expand...
Click to collapse
Lineage is lineage whether it's a gsi or a cusrom
Zirila said:
still sounds like a bit of an unpolished OS
Click to expand...
Click to collapse
Those are false claims. You need to use it before committing on it.
Zirila said:
I'll need enough spare time for experiments, so it won't happen soon
Click to expand...
Click to collapse
There's nothing to experiment, as user's experiments are logged on my thread. You can follow them. I'm myself a gsi user for an year long btw. As for the time, it'll take not more than 10 minutes. And I've laid out post configuration & fixes on the thread which'll be another 5 minutes.
well what I meaned with unpolished is what I've red in your thread about bugs like -don't touch screen while booting- etc. I haven't installed it so I solely say that by reading these posts.
and experimenting is synonymous with taking time to clean flash and reinstall everything again while learning and fixing problems with new OS/roms/GSIs.
I'll have a look sometime and I'm grateful there is progress.
Atleast I was transparent about the bugs on it.
Zirila said:
bugs like -don't touch screen while booting
Click to expand...
Click to collapse
Not touching the screen 'while booting' is an easy fix & you won't often reboot your device while work in the first place.
Zirila said:
learning and fixing problems with new OS/roms/GSIs
Click to expand...
Click to collapse
Just the procedure would be new. Rest of it would be your same old preferred AOSP derivative (lineage).
you did well. nothing to complain.
the more I dip into the topic the more I think it might be worth a try. don't count the time till I can focus on it, it'll take a while. but it sounds more and more promissing and the overall experience might as well get even better with time.
regardless of the GSI option, let's still have this thread and discussion opened for the case of some future LineageOS-CustomROM progress.
I'm very sorry for my abrupt decision to kill Lineage.
some personal and family problems made me think that I couldn't continue with this (nothing too big, don't worry... typical family fights)
after some messages I decided to get back to the action.
I will upload a new build with improvements once I unlock my bootloader (not very soon) as my RN10 is my only source of internet and I can't use the Mi Unlock Tool.
Thread will remain locked until the new build is done.
Thank you for your understanding and sorry for my bad steps ....
Regards
Thanks for the informational update
no worry, we are all human. as software engineer and project maintainer in troubled times it's often better to just keep calm, step back for a while, let the projects delay or freeze, that won't really hurt anyone. and then check back later to make a judgement if the project(s) really have to end.
It wasn't that bad for us either, in the meanwhile some of us learned a bit more of the GSI option which might also be a viable way to run LOS in the future. But everything has up- and downsides.
I'm glad we get to see a few more updates for the LOS custom rom.
lineage is alive again
new update is up ... waiting for shadowstep to open the thread again
Changelog
* Switch to SkiaGL Threaded
* Optimize package manager dexopt properties
* Kernel upstreamed to v4.14.295
* Kernel built with Clang 15.0.2
* Enable config_avoidGfxAccel
* wifi: Disable TDLS offchannel
* Disable few debug services
* Don't enable iostats
these are only for LineageOS 19.1
No changes for 18.1
Lineage OS for Mojito - Browse /Lineage at SourceForge.net
LineageOS for Redmi Note 10 (mojito/sunny)
sourceforge.net
Deleted.
Hi,
I am wondering if there is a common way on this forum to express support for the development of a specific custom ROM for a phone? Is there a commonly accepted way to do this? (Came here to see if I could +1 a LineageOs thread for the Zenfone 9)
Rik
bump
rainyskye said:
bump
Click to expand...
Click to collapse
haha is this a +1 of my wish to be able to give a +1 ?
Hey mate,
I was thinking to contact developers and pay them to build lineage OS and make it official!
Or the other alternative is Learn how to build it and submit it for review on LOS website..
If you have any suggestions?
cool, no idea how to go about that, but I would be happy to contribute as well. I'm sure others would be too - I am on a forum where there are multiple threads dedicated to finding a good small deGoogled phone (community.e.foundation). There must be a place where people can put up amounts for a development like this, right? Sort of like a Kickstarter for a bit of development? I will ask on the other forum too
Rik44444 said:
cool, no idea how to go about that, but I would be happy to contribute as well. I'm sure others would be too - I am on a forum where there are multiple threads dedicated to finding a good small deGoogled phone (community.e.foundation). There must be a place where people can put up amounts for a development like this, right? Sort of like a Kickstarter for a bit of development? I will ask on the other forum too
Click to expand...
Click to collapse
The problem with LineageOS is that when there is no more maintainer for a specific model the phone just goes to rubbish, no more security patch... same for the other custom rom... eOS depends on LOS repositories and even if lineage stop supporting a specific device eOS will keep updating their all supported devices... That's why I really like eOS. It doesn't matter if some features are unavailable... a phone is supposed to be used for call, text. Nowadays, everything seems to be sophisticated however it doesn't need to be... I'll start asking some recognised developers if they are willing to work on a LOS build for the zf9 for some money participation... maybe start a crowdfunding of an alternative without fraud!!
Bump
Hi bro,
Sorry got no time at the moment I ended up using a one plus 6 with eOS... I haven't started anything yet. I might need some help to organise something about crowdfunding..
Good luck and let us know if you have some ideas. Thank's