Related
If this is in the wrong section please move it instead of deleted it. Thanks y'all are awesome
So, what I want to is make my own Ice Cream Sandwich ROM.
I want to take stock android and:
-Make everything work right (camera, buttons, drivers for proper graphics and stuff, etc)...
-Use a good boot animation (I already have in mind which one)
Stuff like that. Would my old server with a dual dual-core Intel Xeon CPUs (total of 4 cores), 6GB RAM, and RAID SCSI disks be good enough, to compile it? Do I even need to compile it? or just unzip and zip?
Thanks!
PS: can I use Windows or would Ubuntu work better? I've also got a MacBook Air that I guess I could use
I won't touch on the driver thing (simply because it's not an easy thing as you suggest). Not only are there various 'work arounds' for the camera issue... but... eh.
Also, I will say that boot animations are nothing more than a text file and a bunch of images... no compiling done there. Just google around and you'll find the 'needed' format VERY easily... and probably even suggested software to make it easy.
Be careful, as you have a condescending style about how things that are easy but aren't, and aren't easy but are... while you haven't even really done any research. These things... they do not go over well here.
Ok as stated it is not as easy as it sounds. Compiling from source is not easy and making everything work is not easy either as the drivers are not released for this device. As all the source is ported from another device. Some of the best minds on XDA have been working for months trying to get the camera to work but with the new rules to the AOSP source from Google it is a huge undertaking. No longer can you build a full working rom from AOSP as the OEM drivers are no longer included due to being closed source and not released.
There are walk thru videos out there but like the Gentlemens above me said it is not a simple task. If you look at the developers it's a collaboration of several members making a team just for one ROM. But you can play around with several ROMs like I did:
Some Ice Cold Sandwich with a little salt from Redemption and a little pepper from Zues and BOOM my perfect ROM for me. (My Frankenstein)
BUT!!!!!!!!!!!!!!!!!!!
1. Dont get me wrong I'm not saying you can take bits and pieces from different ROMS and create your own and offer it here cause thats stealing from developers without their permission. But only for your enjoyment and PLAY AT YOUR OWN RISK.
2. you can't ask for help from developers when you alter their ROMs.
GOOD GOD!!!! Hope my phone don't die with so much flashing and testing (lmao)
Sorry if I made it sound like I didn't realize how huge of an effort good ROM development is. I do!
However, if I just take AOSP then attach the device drivers then add the features I want, I can release it as mine, right?
I'm bored with web design and development, so I figured hey let me try android stuff!
Maybe I should learn how to make an Android app first I have a feeling my basic Java knowledge won't be enough.
Would it be better to start with that, then progress to the more complicated stuff?
And I appreciate the time you are all taking to answer my random questions
I wish I could make Android apps with HTML, CSS, PHP, and Javascript. LOL!
Reinaldo33897 said:
GOOD GOD!!!! Hope my phone don't die with so much flashing and testing (lmao)
Click to expand...
Click to collapse
HAHA yeah sometimes I wonder if it's bad for it
But I've dropped it about 20 times and it still works no damage except for a tiny scratch in the screen so I'd say flashing ROMs is much safer for it than dropping it. LOL!
Installing CM used to be wonderful! I remember a time when went to get.cm, connected my phone to the computer, clicked one or two buttons and watched everything else happen automatically. THAT was an experience worth noting! Perfectly simply and jaw-dropping!
Nowadays, I have to read through several pages of an article, click multiple links, concentrate heavily on the contents, do EXTRA research on Google, YouTube and other how-to pages, use lots of trial-and-error, endure a bunch of frustration and when I'm lucky, after several hours or sometimes days of work, I can get CM working on a phone.
This is unacceptable to a medium-experience user in the year 2016! (Note that I'm not your cookie-cutter idiot user. I have been able to repair MacBooks and phones using only internet tutorials, I have lots of experience using computers, I understand how to code)
1st experience (back in 2013 on my Nexus 5):
Perfect!
2nd experience (S3 neo, 2014):
Horrible! (got it to work, however)
3rd experience (late 2015 on LG G4):
- waited for a new CM supporting my device forever, although a quick CM had been promised
- read though pages and pages of forum threads
- decided not to risk my warranty and get a bad photo app by installing CM rather than an excellent one from stock LG android
- overall, a bad experience again
4th experience (yesterday on an HTC One M7)
- just as bad as before with the exception that I quit out of frustration
It's absolutely incredible how much effort still needs to be brought the the table in order to install CM! I mean seriously now:
1) Installing adb and fastboot (not idiot-proof on Mac OSX)
2) unlocking dev mode on the phone
3) using terminal commands to move files on sdcard (didn't work for me)
4) using bootloader commands on trwp
…
… and so on and so on (lots of errors and problems on the way)
These are all not things that people don’t know how to do EVEN IF THEY HAVE DONE THAT BEFORE 1 OR 2 YEARS AGO!!!! What happened to all that simplicity from the nexus 5 2013 era? I know what you are going to say in response to this, things like: "Google/Android makes it much harder to unlock bootloaders/root on the phone/and yadayadayaaaa...."
All of this might be true but in reality the user still could be cared for so much mor in the installation process. I mean if you at least provided a proper step-by-step instruction with clean English phrases which explains everything with screenshot and/or a video, that would be acceptable. But the way it work right now takes to much time and effort from users.
Do you not have any benefits from a larger user base? Do you not want to make CM spread to as many phones in the world as possible? Come on now, you can do SO MUCH better than this!
Well, if you want an elite community with only very few noobies bugging you for support, well then I can understand that. But if not, this thing is just annoying and extremely frustrating discouraging a lot of users from adopting an otherwise great OS!
Snüber said:
Installing CM used to be wonderful! I remember a time when went to get.cm, connected my phone to the computer, clicked one or two buttons and watched everything else happen automatically. THAT was an experience worth noting! Perfectly simply and jaw-dropping!
Nowadays, I have to read through several pages of an article, click multiple links, concentrate heavily on the contents, do EXTRA research on Google, YouTube and other how-to pages, use lots of trial-and-error, endure a bunch of frustration and when I'm lucky, after several hours or sometimes days of work, I can get CM working on a phone.
This is unacceptable to a medium-experience user in the year 2016! (Note that I'm not your cookie-cutter idiot user. I have been able to repair MacBooks and phones using only internet tutorials, I have lots of experience using computers, I understand how to code)
1st experience (back in 2013 on my Nexus 5):
Perfect!
2nd experience (S3 neo, 2014):
Horrible! (got it to work, however)
3rd experience (late 2015 on LG G4):
- waited for a new CM supporting my device forever, although a quick CM had been promised
- read though pages and pages of forum threads
- decided not to risk my warranty and get a bad photo app by installing CM rather than an excellent one from stock LG android
- overall, a bad experience again
4th experience (yesterday on an HTC One M7)
- just as bad as before with the exception that I quit out of frustration
It's absolutely incredible how much effort still needs to be brought the the table in order to install CM! I mean seriously now:
1) Installing adb and fastboot (not idiot-proof on Mac OSX)
2) unlocking dev mode on the phone
3) using terminal commands to move files on sdcard (didn't work for me)
4) using bootloader commands on trwp
…
… and so on and so on (lots of errors and problems on the way)
These are all not things that people don’t know how to do EVEN IF THEY HAVE DONE THAT BEFORE 1 OR 2 YEARS AGO!!!! What happened to all that simplicity from the nexus 5 2013 era? I know what you are going to say in response to this, things like: "Google/Android makes it much harder to unlock bootloaders/root on the phone/and yadayadayaaaa...."
All of this might be true but in reality the user still could be cared for so much mor in the installation process. I mean if you at least provided a proper step-by-step instruction with clean English phrases which explains everything with screenshot and/or a video, that would be acceptable. But the way it work right now takes to much time and effort from users.
Do you not have any benefits from a larger user base? Do you not want to make CM spread to as many phones in the world as possible? Come on now, you can do SO MUCH better than this!
Well, if you want an elite community with only very few noobies bugging you for support, well then I can understand that. But if not, this thing is just annoying and extremely frustrating discouraging a lot of users from adopting an otherwise great OS!
Click to expand...
Click to collapse
None of those issue are Cyanogen's, they are a result of how the hardware and firmware are designed by the manufacture.
In most cases the Manufacture does not want their devices/firmware hacked, rooted, or bootloaders unlocked.
If you want a custom firmware, do some research first, before buying a device.
rooting right now is fairly difficult too. so to answer your question, installing custom roms needs rooted devices. and whilst installing recovery img is difficult nowadays. you will really find a hard time esp when there's rom mismatch
I have been trying ROMs for years now in my string of Motorola phones, and every single one of them has had one set of showstopping bugs or another. I haven't been able to find any firmware that I could actually live with for any length of time.
I am currently on AOSP Extended v3.3 and it can not give me notifications! My phone just vibrated with a phone call but it was not in vibrate mode! There was no phone with jiggly wires on the sides and when I turned the ringer up it was already at max! Yet no ringer.
I've missed appoointments because the calendar notifications don't work, I miss texts all the time because it can't manage out a tone.
All of us here keep upgrading to the next version in hopes of shedding one or more show-stopping bugs, but it's a dream continually unrealized.
Can any qualified developer tell me why this is so hard? Why can Android not get the basics right, even now that we have reached Oreo? Why is this advanced OS not able to do the little things a phone must do? Never-mind the advanced features like pie controls -- I'd learn those if I trusted this thing. But even on the best phones (my prior was a Moto X) I cant get a phone I can rely on.
PS - I tried an Apple phone for work a couple years ago and it worked, but I just hated it.
Lineage 14.1, Official. Installed the 'official way' (motorola unlock code). Not rooted. For me, working like a charm
You should try a different rom. AOSP Extended is based on AOSP-CAF. When I used a different ROM but also based on AOSP-CAF (purenexus) I faced the same problem.
Right now I’m on unofficial Lineage 15 (it still has some issues: random reboots sometimes but that seems to be an upstream issue as Pixels are also rebooting and having to use Footej camera to record video).
As @krondar said official LineageOS should be your best choice even though it doesn’t have some other more advanced custom ROM features. (Or just stock ROM from Motorola if you’re OK with Marshmallow)
Quantumstate said:
I have been trying ROMs for years now in my string of Motorola phones, and every single one of them has had one set of showstopping bugs or another. I haven't been able to find any firmware that I could actually live with for any length of time.
I am currently on AOSP Extended v3.3 and it can not give me notifications! My phone just vibrated with a phone call but it was not in vibrate mode! There was no phone with jiggly wires on the sides and when I turned the ringer up it was already at max! Yet no ringer.
I've missed appoointments because the calendar notifications don't work, I miss texts all the time because it can't manage out a tone.
All of us here keep upgrading to the next version in hopes of shedding one or more show-stopping bugs, but it's a dream continually unrealized.
Can any qualified developer tell me why this is so hard? Why can Android not get the basics right, even now that we have reached Oreo? Why is this advanced OS not able to do the little things a phone must do? Never-mind the advanced features like pie controls -- I'd learn those if I trusted this thing. But even on the best phones (my prior was a Moto X) I cant get a phone I can rely on.
PS - I tried an Apple phone for work a couple years ago and it worked, but I just hated it.
Click to expand...
Click to collapse
AOSP Extended is one of the best you can find here. But the version you are using is very old. I would recommend you clean flash the latest version and I believe you will love it.
I tryed Cyanogenmod 13 and it was awesome, and now I'm with Lineage 14.1 and everything is ok... no bugs,
Over the years I've tried every firmware from MIUI to Paranoid Android to CarbonROM to Cyanogenmod to ResurrectionRemix, and all have one set of basic problems or another. And worse, seem to deteriorate over time!
This should never, never happen with an advanced OS in the 21st Century. So I moved to the AOSPs and find the same syndrome! This implies a basic problem with Android -- after so many years it can not be gotten right. It's alarming.
Why is Lineage better? What is it based on? How is it different that it doesn't have these problems? How do you find out that one ROM is working better than all the others?
I've been using purenexus ROM for a few month and never faced any issue,not even a little one. It was 100% stable for me and the perfect ROM for a daily driver. AEX Is very good though and lineage OS 14.1 too.
Actually I'd installed PureNexus right after my post above. It's 4 times faster than AOSP Extended v3.3, although I have yet to put it through the wringer. Time will tell.
Quantumstate said:
Actually I'd installed PureNexus right after my post above. It's 4 times faster than AOSP Extended v3.3, although I have yet to put it through the wringer. Time will tell.
Click to expand...
Click to collapse
Why where you using such an old version of AOSP Extended? Currently version 4.6 (nougat) is available and work on Oreo has begun.
Latest Stock Android 6.0.1 with @squid2 r20 kernel works flawlessly on my Moto G3 (xt1548). Two consecutive months of use and not a single bug found.
V-Droid said:
Why where you using such an old version of AOSP Extended? Currently version 4.6 (nougat) is available and work on Oreo has begun.
Click to expand...
Click to collapse
Why? Because I don't have time to be bit-twiddling every other day on my phone. I need to use my phone as a phone, since I am an adult.
Checking, my version of AOSPExtended was 9 March, 2017. You see 5 months, as old? What's the matter with you?
And no matter HOW old, why is it ever acceptable to you that it would sit silent as my phone calls, texts, appointments go by, and it forgets which keyboard I've chosen repeatedly? With this 13th generation of Android, the mission-critical fundamentals are completely busted? It was quite a feat to accomplish that.
Thankfully so far PureNexus is working. I hope that lasts more than 5 months without deteriorating.
Quantumstate said:
Why? Because I don't have time to be bit-twiddling every other day on my phone. I need to use my phone as a phone, since I am an adult.
Checking, my version of AOSPExtended was 9 March, 2017. You see 5 months, as old? What's the matter with you?
And no matter HOW old, why is it ever acceptable to you that it would sit silent as my phone calls, texts, appointments go by, and it forgets which keyboard I've chosen repeatedly? With this 13th generation of Android, the mission-critical fundamentals are completely busted? It was quite a feat to accomplish that.
Thankfully so far PureNexus is working. I hope that lasts more than 5 months without deteriorating.
Click to expand...
Click to collapse
If you don't have time to be 'bit-twiddling' on your phone then why did you bother on unlocking the boot loader and flashing a custom firmware?
Personally I haven't tried pure nexus, but it is very possible that 5 months ago pure nexus had the same bugs as AOSP Extended. Since they are custom firmwares, they are susceptible to bugs, that's why mainteiners push out weekly or monthly updates.
If you think that pure nexus or any other rom will deteriorate over time then you should probably restore the stock firmware of whatever device you are using, well... That of you have time, if not than don't blame maintainers remember they are not being paid for anything.
I don't have time to be bit-twiddling because I have actual work to do. But I want the extra features in custom firmware. Is that unusual? Is that not why most of us do this?
It doesn't matter whether PureNexus had the same bugs 5 months ago. I am using it now. In the real world one can not disprove a negative. Susceptible to bugs? Like the frickin' phone not ringing? And it forgetting basic settings? That should never, never happen. Again, these are mission-critical functions of a *phone*.
The maintainers are doing it for fun and recognition. But those maintainers who lazily emit schlock and dreck should be outed. That is not been happening, and it is time is does, for the protection of users.
Quantumstate said:
I don't have time to be bit-twiddling because I have actual work to do. But I want the extra features in custom firmware. Is that unusual? Is that not why most of us do this?
It doesn't matter whether PureNexus had the same bugs 5 months ago. I am using it now. In the real world one can not disprove a negative. Susceptible to bugs? Like the frickin' phone not ringing? And it forgetting basic settings? That should never, never happen. Again, these are mission-critical functions of a *phone*.
The maintainers are doing it for fun and recognition. But those maintainers who lazily emit schlock and dreck should be outed. That is not been happening, and it is time is does, for the protection of users.
Click to expand...
Click to collapse
I'm not making this statement because of my obvious bias of being employed by Motorola Mobility. But nobody knows better how to create ROMs for Motorola devices better than Motorola. I totally understand your points and agree with your logic on many of the shoddy custom ROMs put out for Moto devices. Cobvetsely, however, I have to give much deserved credit to some of the XDA pioneer developers who have a passion for both Android and our beloved Motorola devices. @lost101 stands out, as well as @superR, @squid2, @Sands207, and the great @Buzbee2 just to name a modicum of these dedicated individuals.
If all else fails your expectations, go with a pure stock build, with root, busybox, debloating, with the custom ROM type flexibilities and customizations provided by deodexing, Xposed Framework mods & tweaks, etc, etc. You don't necessarily need a custom build to enjoy the perks and customizations of your Android OS, Grab yourself a stock build of your choosing and mold it like a piece of clay, and be your own architect. As a brilliant attorney once stated, "at the end of the day, my client is ultimately the captain of his own ship."
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
Quantumstate said:
I don't have time to be bit-twiddling because I have actual work to do. But I want the extra features in custom firmware. Is that unusual? Is that not why most of us do this?
It doesn't matter whether PureNexus had the same bugs 5 months ago. I am using it now. In the real world one can not disprove a negative. Susceptible to bugs? Like the frickin' phone not ringing? And it forgetting basic settings? That should never, never happen. Again, these are mission-critical functions of a *phone*.
The maintainers are doing it for fun and recognition. But those maintainers who lazily emit schlock and dreck should be outed. That is not been happening, and it is time is does, for the protection of users.
Click to expand...
Click to collapse
I'm not making this statement because of my obvious bias of being employed by Motorola Mobility. But nobody knows better how to create ROMs for Motorola devices better than Motorola. I totally understand your points and agree with your logic on many of the shoddy custom ROMs put out for Moto devices. Conversely, however, I have to give much deserved credit to some of the XDA pioneer developers who have a passion for both Android and our beloved Motorola devices. @lost101 stands out, as well as @superR, @squid2, @Sands207, and the great @Buzbee2 just to name a modicum of these dedicated individuals.
If all else fails your expectations, go with a pure stock build, with root, busybox, debloating, with the custom ROM type flexibilities and customizations provided by deodexing, Xposed Framework mods & tweaks, etc, etc. You don't necessarily need a custom build to enjoy the perks and customizations of your Android OS, Grab yourself a stock build of your choosing and mold it like a piece of clay, and be your own architect. As a brilliant attorney once stated, "at the end of the day, my client is ultimately the captain of his own ship."
I am with you on Motorola, MotoJunkie01. No one else makes water-resistant phones, and is that not just a basic common-sense feature for something we carry with us?
But few seem to have common sense.
I've owned Motorola phones since cellphones began. I experimented with HTC, Nokia, and Samsung, but over time each one gave me reason to distrust the brand. Always came back to Moto.
I was afraid that Motorola had discarded the water-resistant feature, but the new X4 is at least IP64, so that will be my next phone. There are no custom firmwares for it yet but I'll make a note of the devs you cite. I do enterprise infosec, and rigor and quality are vital -- given my job and my nature it's why I'm so perturbed with these lackadaisical devs who learn only enough to knock something together and don't have enough sense to fix it. It's like spreading pollution...
I wish Whirleyes would bring his amazing multiboot feature -- no software enhancement comes close to being as useful and important to me, but impetuous people here pissed him off. There is some kind of multiboot available now, but it is not compatible with the XT1540.
For hardware features I rank waterproof first, large battery second, and dual SIM third. I've got to research whether the Asian Moto X4 will work in the US on Credo Mobile. (Verizon)
For software, security is of course number 1. I'd want to configure my phone like the Blackphone2, except with a hidden interface. We may soon be compelled to unlock our phones at borders and by police (which no matter what the Supreme Court says, is unConstitutional), so I'd like to unlock my phone, but have another (hidden) unlock for another side of it; another phone or at least storage place, with the two sides completely secure from one another and distinct.
The supposed "Crypto" rom here is nothing of the sort. He's just using a gee-whiz name, amusingly. Doesn't realize how silly he looks.
I've left my phone out overnight in the rain at least twice, and what a relief it is to have this protection.
And true, stock firmware can be relied on, although I wish it had some of the nice features of customs. And I wish it got security updates over time -- that's a key reason I move to the next releases of Android.
Quantumstate said:
I am with you on Motorola, MotoJunkie01. No one else makes water-resistant phones, and is that not just a basic common-sense feature for something we carry with us?
But few seem to have common sense.
I've owned Motorola phones since cellphones began. I experimented with HTC, Nokia, and Samsung, but over time each one gave me reason to distrust the brand. Always came back to Moto.
I was afraid that Motorola had discarded the water-resistant feature, but the new X4 is at least IP64, so that will be my next phone. There are no custom firmwares for it yet but I'll make a note of the devs you cite. I do enterprise infosec, and rigor and quality are vital -- given my job and my nature it's why I'm so perturbed with these lackadaisical devs who learn only enough to knock something together and don't have enough sense to fix it. It's like spreading pollution...
I wish Whirleyes would bring his amazing multiboot feature -- no software enhancement comes close to being as useful and important to me, but impetuous people here pissed him off. There is some kind of multiboot available now, but it is not compatible with the XT1540.
For hardware features I rank waterproof first, large battery second, and dual SIM third. I've got to research whether the Asian Moto X4 will work in the US on Credo Mobile. (Verizon)
For software, security is of course number 1. I'd want to configure my phone like the Blackphone2, except with a hidden interface. We may soon be compelled to unlock our phones at borders and by police (which no matter what the Supreme Court says, is unConstitutional), so I'd like to unlock my phone, but have another unlock for another side of it; another phone or at least storage place, with the two sides completely secure from one another and distinct.
The supposed "Crypto" rom here is nothing of the sort. He's just using a gee-whiz name, amusingly.
I've left my phone out overnight in the rain at least twice, and what a relief it is to have this protection.
And true, stock firmware can be relied on, although I wish it had some of the nice features of customs. And I wish it got security updates over time -- that's a key reason I move to the next releases of Android.
Click to expand...
Click to collapse
Friend we share similar views and sentiments on this subject. We also seem to share in the philosophy that The Due Process Clause, Equal Protection of the Law, and safeguards against unreasonable searches and seizures have essentially all been trampled through the mud when it comes to our privacy and expectations to privacy with respect to our smartphones. Law enforcement having the authority to compel a man (or woman) to unlock their device without constitutional safeguardsl, is synonymous of the police being permitted to kick down the door to a man's house upon a "whim" or a "hunch". Or a cop conducting a traffic stop and subsequent warrantless search of the driver's person and vehicle merely because the cop feels like it. I take great pride in knowing with 100% certainty that any law enforcement who attempts to track or trace my mobile IP, or tries to monitor anything about incoming or outbound data packets on any of my devices is chasing Casper the Ghost. But, anymore I can't be so certain about John Q Law's legal authorization (or ability) to stick his long snout into my device's internal storage. I'm working the final kinks out of a simple process that will completely wipe and heavily encrypt the wiped storage with multiple layers of random binary (with the morbidly numerous anticipation that they actually can and will spend countless man hours and resources on decrypting utterly blank and random blocks of binary jibberish). All with a self determined series of keyfob button presses.
Yeah I know I'm ranting and perhaps being a bit overzealous. But, just like you said, regardless of state or federal appellate court adjudications giving authorities such authorizations, such decisions run afoul of a handful of the most rudimentary tenets of constitutional safeguards.
Word.
Most have given up and acquiesced. But not me. Never. I use Tor to get here, and just about everywhere else. Because I know what can be done.
Most will say that their words are not important enough and so they don't worry. But they do not know that what is Ok today, may not be tomorrow. I used to be in intelligence, and most here would not believe what can happen (and has happened in other nations).
BTW, there is an excellent TV series called The Americans, which I think is as good as the old Mission Impossible series (which came way before Tom Cruise). Although it can never compete with the old Secret Agent ('Danger Man') series, and the John LeCarre series', it is a high-grade and carefully-wrought storyline.
I agree with you that seems no ROM is stable; In fact if your phone is important for you as production device, I would suggest you stick with stock ROM or keep testing until a ROM which works for you and stay there! New version introduce new bug, that's the usual case on Software side, there is no way to avoid.
If you are so sensitive to bugs then stick onto stock rom instead of blaming the developers. Your fault that you can't keep meddling with your device. If you want a totally bugles device then you try to develop a rom by yourself then you will understand what it is to be a developer
MotoJunkie01 said:
Latest Stock Android 6.0.1 with @squid2 r20 kernel works flawlessly on my Moto G3 (xt1548). Two consecutive months of use and not a single bug found.
Click to expand...
Click to collapse
Better than my XT1540, rooted, no other mods except modified host file for ad removal, stock kernel. I have an average 1 bug report a week.
Hoping this is the right section since its not device specific.
Experienced or not, it doesn't matter. I've been on XDA for a number of years. And am noticing things from my own experience and talking to others. Its hard to get help sometimes. Not all devs want to talk. Teach. Or help people all the time. Devices are being dropped from support. Maintainers are leaving the scene. Currently I have an Oreo and pie ROM for s6e+ and note 5. With the list of devices being dropped, and surprising amount of people reaching out to me for support, I decided it may be beneficial to recruit a few people who want to develop ROMs. This is a great chance to learn. I would like to pick up at least partial support for several more devices, and need some help to do it. My goal in this endeavor is to continue to provide ROMs to people who need them, while teaching other users to develop. This will help to bring fresh life to the scene, and allow support for more devices to be added. If you are interested reply below or inbox me. There is a google hangouts set up, and other methods of team communication will follow. I also have a home server with a 24/7 connection and no data limits on my internet, and an ftp set up to host files directly and not need third party sites.
so basically you have good intentions, no plan and a home server )
what we really need is a unification of all the different but not really different roms and their devs,
then its possible to see a future for long term support for all devices, or at least many.
anyhting else is jsut another project that will or will not die, based on good will and free time of the maintainer, mostly not even reckognized
due to the chaos of fragmented android and even more fragmented custom rom scene.
godkingofcanada said:
Hoping this is the right section since its not device specific.
Experienced or not, it doesn't matter. I've been on XDA for a number of years. And am noticing things from my own experience and talking to others. Its hard to get help sometimes. Not all devs want to talk. Teach. Or help people all the time. Devices are being dropped from support. Maintainers are leaving the scene. Currently I have an Oreo and pie ROM for s6e+ and note 5. With the list of devices being dropped, and surprising amount of people reaching out to me for support, I decided it may be beneficial to recruit a few people who want to develop ROMs. This is a great chance to learn. I would like to pick up at least partial support for several more devices, and need some help to do it. My goal in this endeavor is to continue to provide ROMs to people who need them, while teaching other users to develop. This will help to bring fresh life to the scene, and allow support for more devices to be added. If you are interested reply below or inbox me. There is a google hangouts set up, and other methods of team communication will follow. I also have a home server with a 24/7 connection and no data limits on my internet, and an ftp set up to host files directly and not need third party sites.
Click to expand...
Click to collapse
I respect your Idea but I don't think something like this is required.You see I had been using linux for 4+ years and was pretty adapted to it when I switched to a Note 3.Recently I discovered the Modding part of it and the huge development of custom roms and kernels.and despite having no clue what I was doing I could easily develop a Kernel without a hassle.I went even one step further and made a halium port for it.Sure it didn't boot the first time but by using methods on xda already discussed in detail I was able to make it work.So,the main thing is that someone like me who has no experience could make a ROM in 3 hours without any complications(Except those who could be solved by googling).Then anybody could do it.Currently there isn't a ROM bug or a issue that hasn't been discussed on either xda or other android development sites.But that doesn't mean we shouldn't help newcomers.But it is rare for someone to look on the other side of development and there is enough documentations for him to do it.Maybe too much.qq
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I respect your Idea but I don't think something like this is required.You see I had been using linux for 4+ years and was pretty adapted to it when I switched to a Note 3.Recently I discovered the Modding part of it and the huge development of custom roms and kernels.and despite having no clue what I was doing I could easily develop a Kernel without a hassle.I went even one step further and made a halium port for it.Sure it didn't boot the first time but by using methods on xda already discussed in detail I was able to make it work.So,the main thing is that someone like me who has no experience could make a ROM in 3 hours without any complications(Except those who could be solved by googling).Then anybody could do it.Currently there isn't a ROM bug or a issue that hasn't been discussed on either xda or other android development sites.But that doesn't mean we shouldn't help newcomers.But it is rare for someone to look on the other side of development and there is enough documentations for him to do it.Maybe too much.qq
Click to expand...
Click to collapse
You can't just make a ROM for any device is 3 hours. It doesn't always work that way. Especially not if building from source
godkingofcanada said:
You can't just make a ROM for any device is 3 hours. It doesn't always work that way. Especially not if building from source
Click to expand...
Click to collapse
I just followed a guide.On an XL VPS. With maybe 22GB ram and 16 xeon cores
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I just followed a guide.On an XL VPS. With maybe 22GB ram and 16 xeon cores
Click to expand...
Click to collapse
I don't disagree sometimes it is easy. But what if lineage or GitHub don't have all necessary files for the build? And then you need to extract them from your phone manually, or if build won't boot up and needs modifications to the kernel.. fixing drivers that do not work. It's not always so simple as build, flash and finish.
godkingofcanada said:
I don't disagree sometimes it is easy. But what if lineage or GitHub don't have all necessary files for the build? And then you need to extract them from your phone manually, or if build won't boot up and needs modifications to the kernel.. fixing drivers that do not work. It's not always so simple as build, flash and finish.
Click to expand...
Click to collapse
I did face issues.The End of the guide covered the basics of logging stuff and finding things.They were just as same as debugging a linux OS but yeah you're right as I did face the extracting files(dunno what was supposed to do).So I wrote "extract proprietary vendor code from ROM" and boom lineage gave it to me.Also the guide was only for devices that exist on lineage and sometimes we need to start from scratch.And maybe We both are,Who knows what the future might bring,BTW have you heard about Google's new Boy Fuchisa or something like that.I wanted to talk someone in the field of development about this but nobody was bringing up the non-linux version of Google's OS for smartphones.
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I did face issues.The End of the guide covered the basics of logging stuff and finding things.They were just as same as debugging a linux OS but yeah you're right as I did face the extracting files(dunno what was supposed to do).So I wrote "extract proprietary vendor code from ROM" and boom lineage gave it to me.Also the guide was only for devices that exist on lineage and sometimes we need to start from scratch.And maybe We both are,Who knows what the future might bring,BTW have you heard about Google's new Boy Fuchisa or something like that.I wanted to talk someone in the field of development about this but nobody was bringing up the non-linux version of Google's OS for smartphones.
Click to expand...
Click to collapse
Yes I heard about it. I stumbled across it by accident looking for a way to shim the s6 edge plus cam on my pie rom. It lead me to reading about vulkan, which showed me a new Google os. It looks nice
godkingofcanada said:
Yes I heard about it. I stumbled across it by accident looking for a way to shim the s6 edge plus cam on my pie rom. It lead me to reading about vulkan, which showed me a new Google os. It looks nice
Click to expand...
Click to collapse
Well It seems that it uses a Different type of kernel "microkernel".For someone as stupid as me I don't get it what was the difference between a microkernel and monolithic one on an android device(or a low powered arm processor based board that has a screen attached to it)Will it be performance,Faster loading,Efficiency.I can find a million articles on microkernel vs monolithic but they are in latin for me.But you can just give me the crash course in maybe 3-4 lines.
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
Well It seems that it uses a Different type of kernel "microkernel".For someone as stupid as me I don't get it what was the difference between a microkernel and monolithic one on an android device(or a low powered arm processor based board that has a screen attached to it)Will it be performance,Faster loading,Efficiency.I can find a million articles on microkernel vs monolithic but they are in latin for me.But you can just give me the crash course in maybe 3-4 lines.
Click to expand...
Click to collapse
Device drivers, protocol, file systems moved from kernel to user. It's got less code, more lightweight. And it was created with embedded systems in mind. In theory it should be faster, and more suited to small devices like phones with embedded systems. Giving devices their own dedicated kernel finally instead of butchering a Linux kernel to suit their device needs. It's also universal in terms of cross platform
godkingofcanada said:
Device drivers, protocol, file systems moved from kernel to user. It's got less code, more lightweight. And it was created with embedded systems in mind. In theory it should be faster, and more suited to small devices like phones with embedded systems. Giving devices their own dedicated kernel finally instead of butchering a Linux kernel to suit their device needs. It's also universal in terms of cross platform
Click to expand...
Click to collapse
Now that's more like it.I was afraid that android was finally going to commit close source(or suicicde).But since it's open source and I hear good things from you and 4 other guys who have experience in doing stuff I think,Hope and Pray that it might be a good change.Also thanks for using plain English and being a Open guy.Currently I am thinking that 5 years from now someone gonna run into this post and have a little smirk on his face for you who is reading this,Quote and tell me was it good?Was we good?
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
Now that's more like it.I was afraid that android was finally going to commit close source(or suicicde).But since it's open source and I hear good things from you and 4 other guys who have experience in doing stuff I think,Hope and Pray that it might be a good change.Also thanks for using plain English and being a Open guy.Currently I am thinking that 5 years from now someone gonna run into this post and have a little smirk on his face for you who is reading this,Quote and tell me was it good?Was we good?
Click to expand...
Click to collapse
I think the changes appear good. Less stuff locked away in private, more easily accessible to all. Treble has the vendor stuff available to roms that aren't stock, this will make the kernel tiny and easy to build. One by one the barriers people have to overcome to build their own roms are being taken away.
Hi all,
i own a Tab S6 T860 (non-lte) for quite a while now, about 6 months.
There are some downsides like the horrible unbuffered screen tearing that you'll get with fast-scrolling, but the overall device is pretty premium-sided, and it's got a decent processor, a great display (color/resolution wise) although im missing 2160p in youtube.
Question is as i (until now) didnt bothered developing for a new device, since i had my hands full with the MiPad4, some alcatel devices and are Maintaining official LineageOS for three legacy devices, should i develop for this one if the community still wants it.
The lead-dev of the MiPad left it so im thinking about developing for the Tab S6 now.
I would only develop LineageOS, starting with 16.0 then doing 17.1 and then 18 but idk how long it would take, since ive no real knowledge of the newest platforms and how they are built, so i'd be reading/trying out stuff a LOT before some release nightlies. The "latest" i developed for was the MiPad4 with a sdm660 btw but i mainly do legacy (e.g 8953/8952/8926).
So please leave your feedback or any other opinions/questions, if we reach a decent amount of people who still want it i'll start right away when im back home from my vacations on 18th.
Best Regards!
Edit: Since theres no real telegram group, and i MAINLY talk via telegram i made one so you can contact me quickly.
https://t.me/joinchat/Bn6f-VKeQfZfiKXo69h3Mw
#reserved 1
I would LOVE to have LOS on my Tab S6 (SM-T860) WiFi-only tablet!
Don't even care about stuff like fingerprint, external keyboard, Widevine, Bluetooth, any 'functionality' similar to what Samsung 'provides' like, you name it.
I've spent sooo much time, and a few dollars, trying to get preinstalled stuff to *not* work! but still be able to boot—Knox bull****, anyone?
And having telephony **** on my WiFi-only tablet, either. Something that has baffled me for years is why a 'custom' ROM for a Wifi-only device has software that trys to interact with nonexistent hardware, using up cpu as it continually tries...on a bit of a rant, there.
So yeah, I'm all in. FWIW, I helped write the instructions, and did a *lot* of testing for rooting the Tab S5e, so I ain't scared to test out stuff; check it out, here:
https://forum.xda-developers.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806
TiTiB said:
I would LOVE to have LOS on my Tab S6 (SM-T860) WiFi-only tablet!
Don't even care about stuff like fingerprint, external keyboard, Widevine, Bluetooth, any 'functionality' similar to what Samsung 'provides' like, you name it.
I've spent sooo much time, and a few dollars, trying to get preinstalled stuff to *not* work! but still be able to boot—Knox bull****, anyone?
And having telephony **** on my WiFi-only tablet, either. Something that has baffled me for years is why a 'custom' ROM for a Wifi-only device has software that trys to interact with nonexistent hardware, using up cpu as it continually tries...on a bit of a rant, there.
So yeah, I'm all in. FWIW, I helped write the instructions, and did a *lot* of testing for rooting the Tab S5e, so I ain't scared to test out stuff; check it out, here:
https://forum.xda-developers.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806
Click to expand...
Click to collapse
Thanks for the info about the S5e, i was unaware of how well it is supported.
I would definitely do stuff like fingerprint, widevine, Bluetooth (PEN) and stuff.
But idk about those keyboards samsung offers and how they function since i cant test it on my own.
Same goes for the LTE but im pretty sure i can just use the same blobs.
BTW anyone has a firehose package for the tab s6 by chance???
I too would love LOS in this device. Samsung UI is cluttery, lagging (on mine), and an absolute mess. My PocoF1 gives me better Honkai Impact 3 (a gatcha action fighting game) performance than this tablet, and the poco is an SD845, with lite LOS. So yeah, I'd love to have this. My warranty is void anyways (because samsung decided so I haven't done a thing to void it), so it'd be great to have a reason to take advantage of that.
Chiming in for a plea to get a Lineage build for the Tab S6.
Such a gorgeous piece of hardware beset by such a ****ty software implementation. Why does Samsung insist on abusing its customers? I'd gladly pay for a Lineage or AOSP rom for our device.
Alright, a little update:
Kernel is done -> link found below
It has to be handled with care as of now. Installing it on my running rom resulted in a crash when unlocking the device. A quick factory reset fixed the problem but keep that in mind when installing this on your device.
Rom will follow up hopefully till next month - but i cant promise anything.
T-860:
https://dl.keksla.wtf/boot_t860.img
T-865:
(uploading)
Thargorsson said:
Alright, a little update:
Kernel is done -> link found below
It has to be handled with care as of now. Installing it on my running rom resulted in a crash when unlocking the device. A quick factory reset fixed the problem but keep that in mind when installing this on your device.
Rom will follow up hopefully till next month - but i cant promise anything.
T-860:
https://dl.keksla.wtf/boot_t860.img
T-865:
(uploading)
Click to expand...
Click to collapse
i would love to have custom kernel for samsung rom, but i don mind if you can make enhancements to the kernel like under volt or to solve the graphics lagging issues. it was just tiny changes involved in the past to make it work for both stock and LineageOS but for android 10, i have no idea
i have long inactive in both rom and kernel developments and i doubt how long should it take to get familiar with changes from android 7 to 10
ps i am still on pie, too lazy to upgrade due to my csc is tgy, which lacks updates as usual, and i dont wanna reinstall everything as to switch to dbt and to re-enter all my passwords
btw, may i ask if the stock android 10 fixed the problem with fast scrolling? i have experiences lags and graphics distortions with the samsung browser which was way toooooo unacceptable for a top device like tab s6
ykkfive said:
i would love to have custom kernel for samsung rom, but i don mind if you can make enhancements to the kernel like under volt or to solve the graphics lagging issues. it was just tiny changes involved in the past to make it work for both stock and LineageOS but for android 10, i have no idea
i have long inactive in both rom and kernel developments and i doubt how long should it take to get familiar with changes from android 7 to 10
ps i am still on pie, too lazy to upgrade due to my csc is tgy, which lacks updates as usual, and i dont wanna reinstall everything as to switch to dbt and to re-enter all my passwords
btw, may i ask if the stock android 10 fixed the problem with fast scrolling? i have experiences lags and graphics distortions with the samsung browser which was way toooooo unacceptable for a top device like tab s6
Click to expand...
Click to collapse
nope, sadly we still suffer from those issues on Q .
I dont have any good knowledge of how to apply those undervolts as i never done it before (lineageos requires stock govenors for official) but if you can point me to the correct commits i can look at it
Thargorsson said:
nope, sadly we still suffer from those issues on Q .
I dont have any good knowledge of how to apply those undervolts as i never done it before (lineageos requires stock govenors for official) but if you can point me to the correct commits i can look at it
Click to expand...
Click to collapse
oh...
there were some cpu/voltage tweaks for the same cpu before for my old devices. and for our tab s 6 there are a few devices with the same cpu like one plus. you can search the cpu model in github and then you can find the code name of it and those devices which use the same cpu. i used to get those tweaks for modifying kernels for my previous devices. however for our 855, sadly there's no port for the samsung devices afaik, so you may need to make some more changes in order to port them
---------- Post added at 05:54 ---------- Previous post was at 05:35 ----------
just found this one https://github.com/kdrag0n/proton_bluecross/releases
it should be a 855 with some oc according to the change log, but unfortunately i couldnt load the changes with my browser so i couldnt find the relevant commits
may be you can take a look at that
Thargorsson said:
Hi all,
i own a Tab S6 T860 (non-lte) for quite a while now, about 6 months.
There are some downsides like the horrible unbuffered screen tearing that you'll get with fast-scrolling, but the overall device is pretty premium-sided, and it's got a decent processor, a great display (color/resolution wise) although im missing 2160p in youtube.
Question is as i (until now) didnt bothered developing for a new device, since i had my hands full with the MiPad4, some alcatel devices and are Maintaining official LineageOS for three legacy devices, should i develop for this one if the community still wants it.
The lead-dev of the MiPad left it so im thinking about developing for the Tab S6 now.
I would only develop LineageOS, starting with 16.0 then doing 17.1 and then 18 but idk how long it would take, since ive no real knowledge of the newest platforms and how they are built, so i'd be reading/trying out stuff a LOT before some release nightlies. The "latest" i developed for was the MiPad4 with a sdm660 btw but i mainly do legacy (e.g 8953/8952/8926).
So please leave your feedback or any other opinions/questions, if we reach a decent amount of people who still want it i'll start right away when im back home from my vacations on 18th.
Best Regards!
Edit: Since theres no real telegram group, and i MAINLY talk via telegram i made one so you can contact me quickly.
https://t.me/joinchat/Bn6f-VKeQfZfiKXo69h3Mw
Click to expand...
Click to collapse
I'm in at 17.1 level and up. Don't want to go back...
YES! Yes please please please! I have been dreaming and hoping LOS would come to the Tab S6 for SO long now. So yes, please make a rom for it. Please.
I would love to have LOS rom support on the Tab S6! The lack of Lineage OS support was the one thing holding me back from purchasing the Tab S6, compared to the Tab S5E, but I wanted the faster processor, storage, and larger memory capacity.
That said, if you develop a working LOS rom, that would be a huge win for all Tab S6 users!
I don't think there is a person on XDA with the tab S6 that would not want to see a custom lineage Rom built. I do want a working Spen though. Im on stock 10 One UI 2.5 and samsung is extremely slow at releasing the kernel source code for the 860. Its definitely worth it to use to build one if you can. Thanks for developing on the tab S6.
LOS for T-865 ?! Yes, absolutely
P.S: Working pen would be great of course.
Still On The Fence.
lucgardos said:
LOS for T-865 ?! Yes, absolutely
P.S: Working pen would be great of course.
Click to expand...
Click to collapse
I would support a ROM for this device, but I am leery about past issues and previous devices. I had 3 smp600 units, and all three were beaten to the edge with constant testing of all the ROMS I could grab. But, only ONE of those tabs choked on something from a pure LOS build. Then it hit a brick wall. I could never find a way past a Nov 18 build. So, now with two smt870 units, I will tread lightly. And, big question: WHY are we STILL stuck with ODIN for this process? I know nothing of the process of coding and writing these great ROMS, but having to drag out a WINDOWS laptop to update my android device seems like many steps backwards. I have no NEED for a laptop save for praying for Odin to even run properly. Wish there were better ways for us old farts who've forgotten more tricks than new ones have been taught. But, I am on board to get the Sammy off of my tab. Thanks for your errors.
;-DeanoD
DeanoD said:
I would support a ROM for this device, but I am leery about past issues and previous devices. I had 3 smp600 units, and all three were beaten to the edge with constant testing of all the ROMS I could grab. But, only ONE of those tabs choked on something from a pure LOS build. Then it hit a brick wall. I could never find a way past a Nov 18 build. So, now with two smt870 units, I will tread lightly. And, big question: WHY are we STILL stuck with ODIN for this process? I know nothing of the process of coding and writing these great ROMS, but having to drag out a WINDOWS laptop to update my android device seems like many steps backwards. I have no NEED for a laptop save for praying for Odin to even run properly. Wish there were better ways for us old farts who've forgotten more tricks than new ones have been taught. But, I am on board to get the Sammy off of my tab. Thanks for your errors.
;-DeanoD
Click to expand...
Click to collapse
Well if your not rooted you dont need odin you can install official release update. If you mean to install custom rom like lineage you again dont need odin after you install TWRP.
Actually, on debloated rooted stock ROM I don't see any problems so far..Device is holding it solid and sound.
Flavour of Lineage is absolutely welcome, but personaly I wouldn't use it because a lot of bugs and non functional addons.
Personally...this tablet without pen is like Ferrari without fuel.
Rooted debloated stock is miles ahead of Samsung's incompetent shadow apps. But even as stripped down as I can make it, the ROM still lags and burns battery in the background. I've tried everything and can't get this beautiful expensive piece of hardware to perform to its specs. I respect others who love it as is, but I've never gotten comfortable with the pen and just want a light, fast tablet with a beautiful screen that doesn't overtax its battery.
I'd switch to Lineage on this device in a heartbeat.
this project still alive? seems dead for me.