For context, I am a software developer but my Android experience is limited to writing a few apps, so I'm hoping to learn a bit more before diving in and breaking things.
Initially, I'm wondering what would be the realistic chances of bricking a Mi 5s if I dropped a OnePlus 3T (or other SD 821 based) ROM straight on to it. I understand that, say, the camera and fingerprint reader wouldn't work out of the box, but with the same SoC I would expect the kernel to retain compatibility between the two devices. Or am I being naïve? Are there bootloader issues that I'm not even considering here?
For that matter, what failure modes are likely to prevent me from getting back to TWRP and just putting the stock ROM back if the experiment doesn't work?
Assuming I could get something bootable without my shiny new Mi 5s irrevocably bricking/imploding/catching fire/gaining sentience and instigating a robot uprising, I feel like there would be plenty to learn from tweaking parameters and generally getting towards something usable - but I'm aware that unlike a PC I don't have the worst-case fallback of pulling the hard drive and wiping it in another machine if things go too far wrong.
MoonBuggy said:
For context, I am a software developer but my Android experience is limited to writing a few apps, so I'm hoping to learn a bit more before diving in and breaking things.
Initially, I'm wondering what would be the realistic chances of bricking a Mi 5s if I dropped a OnePlus 3T (or other SD 821 based) ROM straight on to it. I understand that, say, the camera and fingerprint reader wouldn't work out of the box, but with the same SoC I would expect the kernel to retain compatibility between the two devices. Or am I being naïve? Are there bootloader issues that I'm not even considering here?
For that matter, what failure modes are likely to prevent me from getting back to TWRP and just putting the stock ROM back if the experiment doesn't work?
Assuming I could get something bootable without my shiny new Mi 5s irrevocably bricking/imploding/catching fire/gaining sentience and instigating a robot uprising, I feel like there would be plenty to learn from tweaking parameters and generally getting towards something usable - but I'm aware that unlike a PC I don't have the worst-case fallback of pulling the hard drive and wiping it in another machine if things go too far wrong.
Click to expand...
Click to collapse
You would most likely be able to get back into recovery, but it will never boot this ROM, when Xiaomi release sources for this device we might be able to get CM working..
Interesting, thanks for the reply - do you know why it wouldn't work at all? Is it just drivers, or more complex than that?
Weidas said:
Software developer asking such questions? Sorry but lol.
Click to expand...
Click to collapse
Well, yeah... I don't see what's wrong with asking questions to learn about something I'm not familiar with.
Everythings different, its a different device, different blobs, kernel, partitions and so on. It will never work. And no one will be able to port until kernel sources are released.
Click to expand...
Click to collapse
And this is what I'm trying to understand: it has the same architecture, same ARMv8-A instruction set, even an identical SoC. In my experience, it's only necessary to recompile a binary from source when changing to a different instruction set; sure, drivers on the components that differ will likely be a problem, but the core components are the same. If it won't work at all, I was hoping to learn why.
MoonBuggy said:
Well, yeah... I don't see what's wrong with asking questions to learn about something I'm not familiar with.
And this is what I'm trying to understand: it has the same architecture, same ARMv8-A instruction set, even an identical SoC. In my experience, it's only necessary to recompile a binary from source when changing to a different instruction set; sure, drivers on the components that differ will likely be a problem, but the core components are the same. If it won't work at all, I was hoping to learn why.
Click to expand...
Click to collapse
Different OEM's, different implementations, although it may be easier to port it once we have the blobs and device tree. That's one of the first things we need to build a ROM from scratch.
Is there any ETA for when the sources will be released?
Weidas said:
Software developer asking such questions? Sorry but lol. Everythings different, its a different device, different blobs, kernel, partitions and so on. It will never work. And no one will be able to port until kernel sources are released.
Click to expand...
Click to collapse
Get ur snobbery out if here seriously this guy is just trying to learn and good on him for making the effort. It's not like u were born preinstalled with all of your knowledge so don't put people down just to boost ur own ego it isn't pleasant and it has no place on this website. At XDA we should work together as family.
bozy09 said:
Get ur snobbery out if here seriously this guy is just trying to learn and good on him for making the effort. It's not like u were born preinstalled with all of your knowledge so don't put people down just to boost ur own ego it isn't pleasant and it has no place on this website. At XDA we should work together as family.
Click to expand...
Click to collapse
+1 :good::good:
Anything can become obvious when you know the solution!
Related
Hey folks,
This is a very basic DL17 rom. It has been debloated, debinged, rooted, deodexed, and zipaligned. Does NOT include radio or kernel.
Download link:
http://www.mediafire.com/?wdv53fbgl18988i
This should serve as a decent base for folks to build their future roms.
Credit to bubby323 for providing me the DL17 system dump.
credit to Logan302 for testing in IRC.
Patch
------
http://dl.dropbox.com/u/2056318/update-template/email_continuum.zip This should fix email issues.
http://dl.dropbox.com/u/2056318/update-template/social_apps.zip Social apps.
use at your own risk. I am not responsible for anything you do to your device!
DD
Tested it, and it worked absolutely perfectly my market its even working again xP bonus
Thank you so much for your time and effort! xD
Thanks for sorting out the issues with the syslinks.
Sent from my SCH-I400 using XDA App
Flashed this, This morning and it works awesome. I also flashed the test kernal you provided a week or so ago and its working great together.
Thanks for this.
Well just noticed some sort of bug on my phone at least.
When i try to add a facebook account to my ticker it fails and when i click on adding an email to my ticker it locks up my phone and i have to pull my battery. It doesnt even get me to a enter email and password screen.
Honestly to me its not a big deal im not a big facebook or email guy so it doesnt bother me.
Also i was wondering if you knew if any of the themes for the fasinate will work for this? I doubt it just wondering.
Fascinate themes must be ported. I'll look into the facebook and email issue fi possible.
Patch added for email.
adrynalyne said:
Fascinate themes must be ported. I'll look into the facebook and email issue fi possible.
Click to expand...
Click to collapse
Any idea how i would go about porting them?
There are theme porters out there. I'll get some input from others.
CrazyKnight122 said:
Any idea how i would go about porting them?
Click to expand...
Click to collapse
adrynalyne said:
There are theme porters out there. I'll get some input from others.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=932856
the theme porters that are out there...well they most just copy images with the same (or very similar) file names over one another...the post i linked above is my horribly incomplete but still useful attempt at helping people get into themes for the fascinate.
all the tools neccessary are linked in the posts there.
since the fascinate dj05/dl09 update appears very similar to dl17 porting our themes shouldnt be difficult image wise...however there are several xml changes that must be made (especially for black menus)
if anyone is really interested in starting to theme for the continuum look through the above thread and feel free to pm me here with questions or hop into the fascinate irc...im usually in there during the week throughout the day...or others im sure can help too
i had briefly thought about throwing a theme together for the continuum for fun right before dl30 (froyo) leaked...but now i have too much on my plate reporting stuff
While posting an Android ROM, can you guys PLEASE mention what Android version it is? Is this Eclair or Froyo? 2.1, 2.2, 2.2.1...which version? DL17 might explain everything to a developer but not to a user who just wants to flash a ROM on his system and needs to know what Android version it is before actually flashing it.
With all due respect, if you aren't familiar with the naming convention, i.e. don't know what DL17 means, you have no business flashing a rom (until you do). You are gonna end up breaking your device.
2.1Update-1 is the only OS currently available for this device. So.. labeling is a bit redundant right now.
Hey, you guys made the news...
http://www.androidcentral.com/samsung-continuum-sees-its-first-custom-rom
Sent from my SCH-I400 using XDA App
adrynalyne said:
With all due respect, if you aren't familiar with the naming convention, i.e. don't know what DL17 means, you have no business flashing a rom (until you do). You are gonna end up breaking your device.
2.1Update-1 is the only OS currently available for this device. So.. labeling is a bit redundant right now.
Click to expand...
Click to collapse
Thanks for your response and the clarification and with all due respect, the standard naming convention for Android operating systems is in the format of Android <version number> <dessert codename>. I have been flashing ROMs to several devices before there was any Android and have been doing so on a dozen or so Android devices that I have for the past 6 months as well as guiding others in doing so by writing about it - I write about these for a living.
However, one can't be expected to know all about these non-standard or manufacturer-specific ROM naming conventions for all the Android devices out there and unfortunately, I do not have every single device available to test the ROMs on before I write about them. That is why just a few words by the developer in the OP mentioning what Android version it is make things a lot easier for many of us, plus there are several users who are just starting at the flashing business and it makes things more clear to them as well on what they are getting into. Simply saying that if one doesn't know about these non-standard conventions, one shouldn't be trying these things out is similar to saying if one doesn't know how to swim, one shouldn't be getting into the swimming pool. No offense intended. =)
All that being said, keep up the good work - I really appreciate all the hard work you guys put into what you do. Please don't take my comments as a flame - they are just my views on how things can be improved for a lot of us just by a tiny bit of effort from you guys. =)
It is well known that the continuum only has 2.1. Therefore unless there was a 2.2 leak for it (which would be noted) it can be assume by any reasonable person that its a 2.1 rom.
nitsuj17 said:
It is well known that the continuum only has 2.1. Therefore unless there was a 2.2 leak for it (which would be noted) it can be assume by any reasonable person that its a 2.1 rom.
Click to expand...
Click to collapse
Agreed but 'well known' can be relative =) What's well-known to the developer community for a particular device might not be well-known to many who are coming across the flashing scene for the device in question for the first time, despite their prior experience with other Android devices. And as leaks are not out of the question either, just adding two words about the Android version just makes things a bit more clear for everyone, that's all I meant to say.
Coverage
Here's some more coverage for you:
http://www.addictivetips.com/mobile/install-clockworkmod-recovery-on-samsung-continuum/
&
http://www.addictivetips.com/mobile/install-dl17-clean-rooted-android-2-1-rom-on-samsung-continuum/
HQRaja said:
Agreed but 'well known' can be relative =) What's well-known to the developer community for a particular device might not be well-known to many who are coming across the flashing scene for the device in question for the first time, despite their prior experience with other Android devices. And as leaks are not out of the question either, just adding two words about the Android version just makes things a bit more clear for everyone, that's all I meant to say.
Click to expand...
Click to collapse
That goes back to this:
adrynalyne said:
With all due respect, if you aren't familiar with the naming convention, i.e. don't know what DL17 means, you have no business flashing a rom (until you do). You are gonna end up breaking your device.
2.1Update-1 is the only OS currently available for this device. So.. labeling is a bit redundant right now.
Click to expand...
Click to collapse
If you don't know what OS your phone is already running, or how they're doing the naming convention, you are likely going to cause yourself massive problems soon. If someone can't figure out About Phone to compare build versions, they likely can't figure out how to get CWM on their phone to even flash this, so it doesn't matter if the OS version is in the title. Once Froyo drops, then it may be different, but until then, you have a very thin argument at best, regardless of how many ROMs you may or may not have flashed in the past.
imnuts said:
That goes back to this:
If you don't know what OS your phone is already running, or how they're doing the naming convention, you are likely going to cause yourself massive problems soon. If someone can't figure out About Phone to compare build versions, they likely can't figure out how to get CWM on their phone to even flash this, so it doesn't matter if the OS version is in the title. Once Froyo drops, then it may be different, but until then, you have a very thin argument at best, regardless of how many ROMs you may or may not have flashed in the past.
Click to expand...
Click to collapse
In my experience, not knowing the device-specific naming conventions has never bricked any of the dozens of devices I have flashed, as long as I have known that it is a ROM meant for the particular device in question. However, knowing what Android version the ROM is based on without having to ask only makes sense. This isn't about this one device in particular - the Android scene isn't similar to the iPhone scene where there is just one developer (Apple) rolling out just one OS for all the devices on the market. Android is quite fragmented and I believe simply mentioning the Android version with the ROM regardless of whether any other version is out *yet* or not only makes sense as one never knows when a newer version or a leak might be available.
It is all for the purpose of keeping things as clear to someone at first glance, as possible. Now I do know that no other version but this one has been out for the Continuum but that has been after this discussion. All I am requesting is that the OPs should consider mentioning it with the post so that even a newbie wouldn't have to ask for information as basic as this.
What I fail to see here is why this simple, rather humble request should be seen as such a debatable topic by you guys, when it doesn't even require much effort. Heck, all it requires is typing 'Android' followed by the version number. Is it asking for too much?
Okay, this is getting really off-topic and degenerating fast. There are plenty of other threads saying what DL17 is so just hopping out to the Android Development forum would have answered your question. That said, Android ROMs do often include the version, but not always.
It's not that big of a deal. Let it go.
Sent from my SCH-I400 using XDA App
http://forum.xda-developers.com/showthread.php?t=1827256
http://forum.xda-developers.com/showthread.php?t=1483332
http://forum.xda-developers.com/showthread.php?t=1957219
I know this is a question but I'm hoping to get some help on development for this and the info I gather may be usefuluseful for other ROM development
I guess what I'm mainly asking for is someone with dev experience to help me walk through setting up my environment and getting this going, and someone who doesn't mind endless newbish questions. And possibly doing a little bit of development along side of me if I run into something I can't handle
idontwanttobeanoob said:
I guess what I'm mainly asking for is someone with dev experience to help me walk through setting up my environment and getting this going, and someone who doesn't mind endless newbish questions. And possibly doing a little bit of development along side of me if I run into something I can't handle
Click to expand...
Click to collapse
I should have a disclaimer that I am not a full developer really and anything I say can and should be corrected by a real dev but I tend to know a good deal more than the average end user so therefore I try and help where I can
That said, from what I've seen from other devs getting the ROM on the device isn't that hard once you know how and assuming it's not some tricky ROM meant for a specific device (that said, MIUI is the kind of ROM that to me seems like it should be easy to get on a wide number of devices). So, if you want MIUI, it's probably best to ask for someone to port it and if it isn't too hard (I don't think it is) it's just a matter of the dev being nice enough
Teaching you to compile the ROM on your own though, may actually take a lot more time and effort. If you want to learn to make ROMs, which actually is rather easy compared to other parts of developing if you're not making your own from scratch, you could learn to do that, but it's probably better to learn the basics and go to a thread for it.
If you just want MIUI for your KF2, it's probably easiest to ask a dev to do it for you.
As always, any dev feel free to correct me if I'm wrong
iytrix said:
I should have a disclaimer that I am not a full developer really and anything I say can and should be corrected by a real dev but I tend to know a good deal more than the average end user so therefore I try and help where I can
That said, from what I've seen from other devs getting the ROM on the device isn't that hard once you know how and assuming it's not some tricky ROM meant for a specific device (that said, MIUI is the kind of ROM that to me seems like it should be easy to get on a wide number of devices). So, if you want MIUI, it's probably best to ask for someone to port it and if it isn't too hard (I don't think it is) it's just a matter of the dev being nice enough
Teaching you to compile the ROM on your own though, may actually take a lot more time and effort. If you want to learn to make ROMs, which actually is rather easy compared to other parts of developing if you're not making your own from scratch, you could learn to do that, but it's probably better to learn the basics and go to a thread for it.
If you just want MIUI for your KF2, it's probably easiest to ask a dev to do it for you.
As always, any dev feel free to correct me if I'm wrong
Click to expand...
Click to collapse
I'm actually finishing up my college work then I'm setting up my environment. I don't believe getting at least an alpha build up and running will bentha hard, I just need someone to double check my work so that no one is bricking their device due to a mistake I make
On the note of questions, is it possible to make a suitable Linux environment with the wubi installer?
Setting up Ubuntu now
base and port rom downloading now, ill keep everyone up to date with progress
Any update? para would be a nice port also! I tried but couldn't get it to boot...
Chrisbabs85 said:
Any update? para would be a nice port also! I tried but couldn't get it to boot...
Click to expand...
Click to collapse
Biggest issue I'm having is finding the tools and getting the drivers to work on Ubuntu. Its a bit of a learning curve but no worries I'll get this baby working. Also got a project I'm helping a friend with for the nook.
idontwanttobeanoob said:
Biggest issue I'm having is finding the tools and getting the drivers to work on Ubuntu. Its a bit of a learning curve but no worries I'll get this baby working. Also got a project I'm helping a friend with for the nook.
Click to expand...
Click to collapse
Also what device does para run on? Easiest way to port a ROM is make sure its one that already works on a similar device ( porting miui for kindle fire to the kindle fire 2) also the ROM your trying to port should have the same screen density. The three links up top seem to be excellent sources of information
for anyone thats interested i believe im almost done with an alpha version of the port, im asking a few newbish questions as im teaching myself as i go and im gonna try to have some people take a look at what i did just to make sure theres no insta brick on flashing it.
idontwanttobeanoob said:
for anyone thats interested i believe im almost done with an alpha version of the port, im asking a few newbish questions as im teaching myself as i go and im gonna try to have some people take a look at what i did just to make sure theres no insta brick on flashing it.
Click to expand...
Click to collapse
Hi mate, I'll test it! thanks for links going to check them out, I know paranoid runs on nexus 7 I will have to check
Cheers!
Chrisbabs85 said:
Hi mate, I'll test it! thanks for links going to check them out, I know paranoid runs on nexus 7 I will have to check
Cheers!
Click to expand...
Click to collapse
Once I get some help with the update script and have someone take a look at the files to see if they can see any major issues I'll upload it and send you a link. However basic disclaimer around here applies.... If the world ends etc I take no responsibility. Ie don't sue me lol. But that being said can't wait to finish this.
idontwanttobeanoob said:
Once I get some help with the update script and have someone take a look at the files to see if they can see any major issues I'll upload it and send you a link. However basic disclaimer around here applies.... If the world ends etc I take no responsibility. Ie don't sue me lol. But that being said can't wait to finish this.
Click to expand...
Click to collapse
Oh wow. Nice progress! It's good to see more development around here! I'm glad you found the help you need and everything went smoothly (so far)
Best of luck!
iytrix said:
Oh wow. Nice progress! It's good to see more development around here! I'm glad you found the help you need and everything went smoothly (so far)
Best of luck!
Click to expand...
Click to collapse
Thanks
So far I'm stuck until I can either a figure out update scripts myself or I get some help. Everything seems OK but till I can try to boot this myself I can't really tell. Also once the HD codec issue is fixed I'll be merging that, I'll also be taking suggestions for fixes.
idontwanttobeanoob said:
Thanks
So far I'm stuck until I can either a figure out update scripts myself or I get some help. Everything seems OK but till I can try to boot this myself I can't really tell. Also once the HD codec issue is fixed I'll be merging that, I'll also be taking suggestions for fixes.
Click to expand...
Click to collapse
Update script should be fairly easy just compare the base and port I guess?
I got Ubuntu set-up and I'm going to begin porting paranoid. Also don't worry I have a few test devices
idontwanttobeanoob said:
Thanks
So far I'm stuck until I can either a figure out update scripts myself or I get some help. Everything seems OK but till I can try to boot this myself I can't really tell. Also once the HD codec issue is fixed I'll be merging that, I'll also be taking suggestions for fixes.
Click to expand...
Click to collapse
Oh I forgot about HD....hmmm. I am not sure how difficult patching things from other ROMs in is, but it seems like the next hascode release should fix most if not everything majorly wrong and I think that would be a better base point for building ROMs. It could be easy though and the thing is pretty damn stable. I've only ever had one issue beyond HD and re-flashing fix it so, possibly this is a good build to work off of
Yeah, it seems no one is really on right now but later they may be able to help, especially in IRC
Chrisbabs85 said:
Update script should be fairly easy just compare the base and port I guess?
I got Ubuntu set-up and I'm going to begin porting paranoid. Also don't worry I have a few test devices
Click to expand...
Click to collapse
One would assume but with semi limited knowledge on them I come to two assumptions, first off is the simple fact that I know the partition tables are different. So if the script tries to send something somewhere it doesn't belong it could be bad, second I see some differences in the scripts that I don't understand and there for do not want to mess with them until I do or someone who does will explain.
My goal is to not brick any testers kfires just seems bad for business
idontwanttobeanoob said:
One would assume but with semi limited knowledge on them I come to two assumptions, first off is the simple fact that I know the partition tables are different. So if the script tries to send something somewhere it doesn't belong it could be bad, second I see some differences in the scripts that I don't understand and there for do not want to mess with them until I do or someone who does will explain.
My goal is to not brick any testers kfires just seems bad for business
Click to expand...
Click to collapse
:good:
Chrisbabs85 said:
:good:
Click to expand...
Click to collapse
After looking more in depth at the update script I saw one major difference...
Which is to do with the dev/block
So I went with the previous ROMs update script and I'm making the zip for initial testing now.
Fingers crossed
idontwanttobeanoob said:
After looking more in depth at the update script I saw one major difference...
Which is to do with the dev/block
So I went with the previous ROMs update script and I'm making the zip for initial testing now.
Fingers crossed
Click to expand...
Click to collapse
Good luck mate, if you think it's OK send me the link for testing...
Cheers!
Waiting for the sources that is, what are porters planning on sticking on this? Personally I want the sources to attempt to port Sailfish, only reason I bough the phone. I currently have the Nexus 5 and the OS runs buttery smooth thanks to the porters over at #sailfishos-porters
Am even wondering did I make a mistake buying this device when the Nexus 5, is more than enough omph to power the OS. But I've got it and gotta try, to atleast expand my own knowledge base.
also do you guys know how chainfire managed to build the kernel for it without the sources?
WTF?
The phone has been out for less than a month. Have some patience or start learning to develop yourself, rather than creating a useless thread, just to whine.
I got my 5x last Tuesday and forgot how little I like "pure" android. I think the usual progression is flash aosp then flash cyanogenmod once the nightlies start to stabilize. I know I'm in the minority but the nexus phones usually have too much Google on them for my taste. I like the hardware, but the software is another story.
At any rate, I'm also waiting for the binaries and device tree so that I can start building my own.
m4r0v3r said:
Waiting for the sources that is, what are porters planning on sticking on this? Personally I want the sources to attempt to port Sailfish, only reason I bough the phone. I currently have the Nexus 5 and the OS runs buttery smooth thanks to the porters over at #sailfishos-porters
Am even wondering did I make a mistake buying this device when the Nexus 5, is more than enough omph to power the OS. But I've got it and gotta try, to atleast expand my own knowledge base.
also do you guys know how chainfire managed to build the kernel for it without the sources?
Click to expand...
Click to collapse
If you knew much about how android works, you'd know that chainfire didn't make a kernel. He took the boot image and modified some fstab, prop, and sepolicy stuff, repackaged it, and released it. He didn't build his own kernel.
In any case, I'm curious about this, how long does it usually take google to release their sources?
Sent from my Nexus 5X using Tapatalk
sn0warmy said:
WTF?
The phone has been out for less than a month. Have some patience or start learning to develop yourself, rather than creating a useless thread, just to whine.
Click to expand...
Click to collapse
oh yeah Ill just go and create a kernel, and while am at it, I may as well write my own drivers. Maybe I'll call my kernel linox, and adopt this policy of sharing my source code so other people could collaborate. Maybe using some sort of version control, call Hit or something, maybe on some website called HitHub.
Yeah that sounds like a good way to develop it...Or Google could hurry the **** up and release the sources and binaries so I wouldn't have to.
Well if you read my post you'd see I was curious about what people wanted to port.
drsn0w said:
If you knew much about how android works, you'd know that chainfire didn't make a kernel. He took the boot image and modified some fstab, prop, and sepolicy stuff, repackaged it, and released it. He didn't build his own kernel.
In any case, I'm curious about this, how long does it usually take google to release their sources?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Not make but people have been saying it was built with forceencrypt disabled so I thought he built the kernel with that flag, (ie he had the sources). But it seems thats not the place to change it
Wow the self-entitlement is real nowadays, patience bro. You cant have everything instantly when you want it.
m4r0v3r said:
oh yeah Ill just go and create a kernel, and while am at it, I may as well write my own drivers. Maybe I'll call my kernel linox, and adopt this policy of sharing my source code so other people could collaborate. Maybe using some sort of version control, call Hit or something, maybe on some website called HitHub.
Yeah that sounds like a good way to develop it...Or Google could hurry the **** up and release the sources and binaries so I wouldn't have to.
Well if you read my post you'd see I was curious about what people wanted to port.
Not make but people have been saying it was built with forceencrypt disabled so I thought he built the kernel with that flag, (ie he had the sources). But it seems thats not the place to change it
Click to expand...
Click to collapse
timjp692 said:
Wow the self-entitlement is real nowadays, patience bro. You cant have everything instantly when you want it.
Click to expand...
Click to collapse
what to expect an open source based phone to have the sources with it?
No I know I can't have everything when I instantly want it, but really what could be the reason for the delay. Since am already pretty pissed about the force encryption.
m4r0v3r said:
what to expect an open source based phone to have the sources with it?
No I know I can't have everything when I instantly want it, but really what could be the reason for the delay. Since am already pretty pissed about the force encryption.
Click to expand...
Click to collapse
I'm sorry, but you sound like a whiney little 12 year old who is used to having everything they want RIGHT when they want it. Kind of sums up the turn this forum has taken over the past couple of years.
In the real world you'll learn that good things take time. The phrase, "patience is a virtue" holds true merit.
Offer a bounty if you're that impatient.
sn0warmy said:
I'm sorry, but you sound like a whiney little 12 year old who is used to having everything they want RIGHT when they want it. Kind of sums up the turn this forum has taken over the past couple of years.
In the real world you'll learn that good things take time. The phrase, "patience is a virtue" holds true merit.
Click to expand...
Click to collapse
Apology accepted.
bblzd said:
Offer a bounty if you're that impatient.
Click to expand...
Click to collapse
For what exactly? Someone to break in Google servers and take the source code? lol
m4r0v3r said:
For what exactly? Someone to break in Google servers and take the source code? lol
Click to expand...
Click to collapse
I'm waiting too- it's not like google is still working on the binary drivers and just building the production rom with hacked up device trees until they get the real ones. I could be mis-remembering, but in the past, I thought the factory roms and binary drivers were available the day the devices were released.
I can certainly understand being patient with devs who are working on roms (for free/beer/donations), but google is done with the rom and has already released it to production. The factory image for the 6p was delayed as well. It's not a secret- they are going to push it to every one who bought a phone. My conspiracy theory is that google is trying to bury aosp, and merging android and chrome will be another stab into the heart of both privacy and freedom.
and its outtt
m4r0v3r said:
and its outtt
Click to expand...
Click to collapse
Waiting for some real nexus thing then
Hello as we all know rhe future of the galaxy note 4 depends on arm64 and unfortunately Samsung has decided to run the device in 32 bit only mode so can anybody pick this project up ?
https://forum.xda-developers.com/no...ers-only/wip-64bit-build-exynos-5433-t3090926
Cilekcigs said:
Hello as we all know rhe future of the galaxy note 4 depends on arm64 and unfortunately Samsung has decided to run the device in 32 bit only mode so can anybody pick this project up ?
https://forum.xda-developers.com/no...ers-only/wip-64bit-build-exynos-5433-t3090926
Click to expand...
Click to collapse
Apparently you're a junior around and don't know much about this 32/64 bit thingy.
The answer is no, no one is able to do anything about it, the 64 bit will never happen.
The kernel is 32 bit locked. Why? Ask Samsung.
And did you read and understand this sentence from AndreiLux ?
"You can't simply make a 64bit kernel because it won't work due to the hypervisor and AArch64-specific exception models. The whole lower level bootloaders need to be adapted, and that's not possible."
Another answer is - how on earth do you think is Samsung seeing the Note 4 from the ROI (return of investment) and sales and marketing poin of view?
When every manufacturer is consumption oriented?
w41ru5 said:
Apparently you're a junior around and don't know much about this 32/64 bit thingy.
The answer is no, no one is able to do anything about it, the 64 bit will never happen.
The kernel is 32 bit locked. Why? Ask Samsung.
And did you read and understand this sentence from AndreiLux ?
"You can't simply make a 64bit kernel because it won't work due to the hypervisor and AArch64-specific exception models. The whole lower level bootloaders need to be adapted, and that's not possible."
Another answer is - how on earth do you think is Samsung seeing the Note 4 from the ROI (return of investment) and sales and marketing poin of view?
When every manufacturer is consumption oriented?
Click to expand...
Click to collapse
Hello yes I'm new and no I'm not saying Samsung should just go out and make a 64 bit kernel. I always thought that people make custom ROMs because they love their phone not for just a temporary solution before you get a new phone (I know ROMs like linage and RR are made for many devices not one). Thanks for the explanation.
Cilekcigs said:
Hello yes I'm new and no I'm not saying Samsung should just go out and make a 64 bit kernel. I always thought that people make custom ROMs because they love their phone not for just a temporary solution before you get a new phone (I know ROMs like linage and RR are made for many devices not one). Thanks for the explanation.
Click to expand...
Click to collapse
Well, most of the times people make custom ROMs out of passion and a thrilling sensation of sharing knowledge. Most users of these custom ROMs are the beneficiaries of a temporary solution before getting a new phone. Some love their phone which is still good and has features which newer phones don't have. And other reasons. We shouldn't generalize.
Somehow this activity became less and less possible. Locked bootloaders are the more popular. Consumerism is the daily driver and this affects the existence of custom ROMs.
It's sad to see android devices of 1-2000$ getting only 2 major updates. And then you need to invest again in a new device.
I see a bunch of ROMS over here on the PRO side.
Can a OP9 type dude get some love...... Dang! Lol.
Haha, thanks to all the developers regardless. You guys are awesome. I'm just a typical flashaholic. Maybe I need a meeting. Syke. Time to flash more
Yeah it would be nice to see some of these over there. I started trying to figure out how to port them myself but I need someone who's willing to help me get a working device tree because I was confused as to what source I should be using.
I was following this.
[Noob Guide][Blind-copy-guide][Android 11]Build Custom ROM in windows 10 (WSL2)
1. Requirement 1. Windows 10 version 20H2 update. 2. Internet. 3. Google search ability. 3. Patient.!! 2. Credit Send me a coffe: 0x10Bcc550e1Ac7E7c68D867ef7379C51847300eE3 3. Main step 1. Setup Ubuntu 2. Configure Environment 3. Install...
forum.xda-developers.com
I might have to learn how to do that. And I could join you.
Maybe you should consider donating a device to OP9 Pro Devs, they might make a ROM or two for you.
Shoot I could do that. I flip phones for a living.
illusiveairforce said:
Shoot I could do that. I flip phones for a living.
Click to expand...
Click to collapse
My point too, the same goes for the devs. They don't own the device, they won't build ROMs.
ekin_strops said:
My point too, the same goes for the devs. They don't own the device, they won't build ROMs.
Click to expand...
Click to collapse
There's not that many differences between the 9 and 9 Pro to account for though. I mean you can flash the complete 9 Pro firmware to a 9 (many of us have unfortunately had to cross-flash to the Indian 9 Pro firmware after the device got fussy and didn't flash properly) and it boots and functions fine, just the camera cutout is in the wrong place. It really should largely come down to the kernel.
EtherealRemnant said:
There's not that many differences between the 9 and 9 Pro to account for though. I mean you can flash the complete 9 Pro firmware to a 9 (many of us have unfortunately had to cross-flash to the Indian 9 Pro firmware after the device got fussy and didn't flash properly) and it boots and functions fine, just the camera cutout is in the wrong place. It really should largely come down to the kernel.
Click to expand...
Click to collapse
The kernel isn't the only "issue" with making a unified build.
ekin_strops said:
The kernel isn't the only "issue" with making a unified build.
Click to expand...
Click to collapse
Of course not but there shouldn't be too much that needs to be changed is my point, it's not like this is an entirely new device, over 90% of the hardware is shared.
EtherealRemnant said:
Of course not but there shouldn't be too much that needs to be changed is my point, it's not like this is an entirely new device, over 90% of the hardware is shared.
Click to expand...
Click to collapse
Well, the majority of the devs from the OP9 Pro are not willing to do it without owning the device. It's understandable, it's their free time. Blind building, waiting for the feedback, logs, etc... It's pain.