Related
i know its been asked but i'm starting the discussion. there has to be an easy way to flash all these great i9100 roms on to our tmobile t989. i would think its mostly a kernal difference and some hardware buttons. i say this because i love hyperdroid roms (mostly wanted s2 for use of his rom) .with the hd2 all builds worked on all phones (europe,asia,usa,etc) no matter the model number.
i am starting the discussion and will help to develop with my time and limited knowledge (i need people who know more about building these roms) a simple zip file to be flashed through cwm. most builds use a base version, then have roms and etc over the top of them. so there must be a way to find a base version you like for any i9100, flash over cwm, then flash a "kernal" of sorts that "adds in or takes out" what is needed for android to run on our t989.
any thoughts? anyone want to discuss this? i have the time (as much as possible, my gf keeps saying "why dont you just make your own and quit bit$%ing").
also i saw a kitchen for building roms for s2 but not sure if its t989 compatible.
lets get to work, our phone is new but the i9100 is already cooking along, we can piggy back and make our phones just as awesome!
Reading from the tittle of the thread, please dont do it! Just fall back..
Sent from my SGH-T989 using XDA App
So I understand you're not going to try to flash it but you're wrong about the major hurdle: Its the different processor. Since we have different hardware we're not talking about a slightly different radio, we're talking about two completely different devices branded as the same thing.
i realize its hardware, but isn't that all controlled by the kernal? it holds the drivers. it would be like "porting" take a rom everyone loves, make the hardware drivers work, then flash. like i said i'm limited knowledge but i want to start work on this. its a hardware thing i understand. but there must be something we can do to ease the process.
To sum up what Kevin said : It's like flashing a sensation rom on our sgs2...(Right?)
but sense has been ported to other non htc devices. my point is it can be done. we should talk about it and get a discussion going. i'd be more then happy to help "port" other roms that are out for s2 varients
cashyftw said:
To sum up what Kevin said : It's like flashing a sensation rom on our sgs2...(Right?)
Click to expand...
Click to collapse
kenVAN its my first and last name pushed together But yes.
letrain02 said:
but sense has been ported to other non htc devices. my point is it can be done. we should talk about it and get a discussion going. i'd be more then happy to help "port" other roms that are out for s2 varients
Click to expand...
Click to collapse
letrain02 said:
i realize its hardware, but isn't that all controlled by the kernal? it holds the drivers. it would be like "porting" take a rom everyone loves, make the hardware drivers work, then flash. like i said i'm limited knowledge but i want to start work on this. its a hardware thing i understand. but there must be something we can do to ease the process.
Click to expand...
Click to collapse
Porting sense to non-HTC phones requires massive amounts of work and open source. Yes, it is possible but whether or not its feasible is a different option. You're right that the kernel is the main difference but even so its much more work than simply adjusting the kernel since there are soooooo many differences. Cashy put it well: you're porting a ROM from effectively a Samsung device to an HTC device. The only similarities are the screen and touchwiz. If you want to give it a go, I'd wait until we have a full ODIN tar to help you recover your phone because you're going to get a few bricks.
Well good luck to us all.
got my T989 few days ago, and I find it much better than the usual i9100 that everyone have on every aspect, except for the lack of support and android development. I regret I based my decision solely on technical spec rather than checking the verity of available firmware and development.
I live and use this phone in Israel, and that stock T-mobile rom I got with it is loaded with lots of irremovable T-mobile apps. Those are irrelevant for me. But the real issue is about the RTL support. I now have to read Hebrew text backwards (taht ekil hpargarap eloh a daer ot yrT) in some text fields. And it won't let me use the mobile hotspot by saying my sim card is not supported. I can't see why it connects to the internet (it does, checked my APN settings twice and it configured right) but won't let me use that hotspot.
Can't these changes in the level of GUI be implanted from other equivalent roms as source code? Does these minor changes take so much work? Before overclocking my phone to 1.89 Ghz I would rather get the basic functions done.
And I'm willing to donate, and to help in any way to promote this project.
I tried a similar thing with my LG optimus 2x (I have model p-999 which is really t-mobile's g2x) by accident. Even though the variations are named optimus 2x and the specs are almost identical, firmwares just aren't compatible with one another.
I flashed a optimus 2x firmware (p-990) to my p999 and I bricked my phone. At this point, even clockworkmod could not recover it. I had to manually partition a t-mobile g2x recovery file one by one on DOS mode to fix this. Finding this solution was like finding a needle in a haysack. I thought there was a good chance that I flushed $400 down the drain when this happened.
So, lol I dont recommend it knowing that gs2 is even a higher price to pay. Hope this helped.
it's something that I almost gave a try and then decided to check in here to see what people say about flashing these roms.. lol. Thanks guys
Lol I actually did try to flash cm for the i9100 on this phone, but thankfully it only gave me an error and didn't actually go through with the flash. (I had literally gotten the phone the day before too lmao)
letrain02 said:
i realize its hardware, but isn't that all controlled by the kernal? it holds the drivers. it would be like "porting" take a rom everyone loves, make the hardware drivers work, then flash. like i said i'm limited knowledge but i want to start work on this. its a hardware thing i understand. but there must be something we can do to ease the process.
Click to expand...
Click to collapse
It sounds like youve got porting perfectly understood. The devs havent been able to do it, you should explain how porting works to them.
The problem is not just the kernel. The software is most likely compiled specifically for the processor. If you were talking about linux . . . it would be easy because the source code is there and you can compile it for whatever processor you want, but it seems Samsung is a a company who believes in leeching off off open source and mixing their proprietary crap in it then keeping the sources closed and giving the open source community the finger. Just look at how they handled the vertical lines screen issue. Its all about money to Samsung.
jim93 said:
It sounds like youve got porting perfectly understood. The devs havent been able to do it, you should explain how porting works to them.
Click to expand...
Click to collapse
Dude no need to be a punk, I seriously dislike people like you who make forums negative. He was asking a question and is trying to learn, which is more than some people do. Keep your negative comments to yourself. If you cant say anything nice don't say anything at all.
This thread was started in 2011, and hasn't been active in over 7 months. There is no need to bring it back from the dead to argue with someone.
Its not as impossible as it may seem(for the experienced dev) if u look in the dev section android88 has ported hellybean from the 9100. I'm learning & I've only gotten a bootloop at worse, haven't bricked yet lol.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
It is possible with a port. The thing that brocks your phone in flashing an i9100 ROM is the kernel. If you switched the kernels, you'll just have a boot loop or no boot. Flashing another devices kernel is the killer.
Sent from my Nexus 7 using xda app-developers app
letrain02 said:
i realize its hardware, but isn't that all controlled by the kernal? it holds the drivers. it would be like "porting" take a rom everyone loves, make the hardware drivers work, then flash. like i said i'm limited knowledge but i want to start work on this. its a hardware thing i understand. but there must be something we can do to ease the process.
Click to expand...
Click to collapse
Its not that easy. It the more similar to porting over a ROM for a Sony Xperia. Does that sound easy. Its just a name but inside very different
---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------
Tmogalaxys2 said:
It is possible with a port. The thing that brocks your phone in flashing an i9100 ROM is the kernel. If you switched the kernels, you'll just have a boot loop or no boot. Flashing another devices kernel is the killer.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Oh god not true at all people have already bricked their phone by flashing i9100 ROMS. Needs to be said before somebody bricks their expensive device.
---------- Post added at 10:48 PM ---------- Previous post was at 10:45 PM ----------
thefawns said:
Dude no need to be a punk, I seriously dislike people like you who make forums negative. He was asking a question and is trying to learn, which is more than some people do. Keep your negative comments to yourself. If you cant say anything nice don't say anything at all.
Click to expand...
Click to collapse
Its just logic. If its that easy try it and youll learn the inside out of why. Put in a similar amount effort you are asking the dev to put in by learning something about the challenges you are asking the dev to overcome instead of assuming devs arent putting enough thought into it
jim93 said:
Its not that easy. It the more similar to porting over a ROM for a Sony Xperia. Does that sound easy. Its just a name but inside very different
---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------
Oh god not true at all people have already bricked their phone by flashing i9100 ROMS. Needs to be said before somebody bricks their expensive device.
---------- Post added at 10:48 PM ---------- Previous post was at 10:45 PM ----------
Its just logic. If its that easy try it and youll learn the inside out of why. Put in a similar amount effort you are asking the dev to put in by learning something about the challenges you are asking the dev to overcome instead of assuming devs arent putting enough thought into it
Click to expand...
Click to collapse
i9100 roms port fine to t989 if you know what your doing. Getting BT to work is being a pita for me though
ThdDude said:
i9100 roms port fine to t989 if you know what your doing. Getting BT to work is being a pita for me though
Click to expand...
Click to collapse
Where are these ports?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.
there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on
I for one is not counting on it, frankly...
No matter how beautifully you phrase things, WE GOT NOTHING YET.
Sent from my SGH-T989 using XDA App
[A virgin sacrifice] =
SO FREK'IN EXCITED!!!!!
thanks for the info bro looking forward to it
jessejames111981 said:
there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on
Click to expand...
Click to collapse
the thing is, many of those are KANGed as in not officially supported by CM team
of the few that officially are supported is Nexus S i9020 and SGS i9000
even the "classic" SGS2 i9100 is not fully supported by CM yet, there's more bugs than... well it's not usable as a daily driver
that was just before the end of last year
they might have improved it a bit by now
even the Nexus S version of CM9 is still very buggy, that's why i have the stock official ICS4 instead on my Nexus S
Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium
iwasblown said:
Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I don't believe in idiots, can you make them all go away?
It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.
Why this statement?
From a glaxay better than yours.
tl;dr
I am basing my entire post on the fact that Steve Kondik has our device and should theoretically be working on it.
Click to expand...
Click to collapse
Steve Kondik aka Mr. Cyanogen also works for Samsung. I am sure he gets ALL Samsung devices...
corwest said:
It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.
Click to expand...
Click to collapse
It only takes 2 weeks to modify the stock rom or cm7/9.
Its the expectation that is built when people act like quantity is all that matters. There are basically only 2 people making roms; Samsung and CM team, everyone else just waits on these 2 so that they could tweak and modify one of those 2. The funniest part is that the use of the word "kanging" is thrown around among these other people.
housecat93 said:
I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.
Click to expand...
Click to collapse
I'd like to believe, I really would. And I hope this does come to fruition. However, even if it doesn't, the few ROMS we do have are pretty good, and our phone still outperforms almost anything else available right now, so I'll still be happy.
I do have one request, though. Can we figure out a way to make CM based ROMS happen without a virgin sacrifice? There are so many other things in life that require those, that they are starting to become scarce
The fact that lots of other phones have alphas and repositories available to even make kangs does not fare well for our device.
Sent from my HTC_Amaze_4G using xda premium
guys chillax..slayher already has it booting..and that's news from december
good to know, thanks
Great phone, needs more dev time and hopefully that comes along with it when ics hits.
We got shafted early with the nexus release so close to the T989 and a dev that promised things but ran away.
New year brings new hope. Great respect for the devs that care about our phone.
Sent from my SGH-T989 using XDA App
Let's hope the mods don't ban what little devs we have left...
Sent from my HTC_Amaze_4G using xda premium
AznDud333 said:
guys chillax..slayher already has it booting..and that's news from december
Click to expand...
Click to collapse
I don't follow, what do you mean by booting?
synergeticink said:
I don't follow, what do you mean by booting?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Booting
Our community seems small. How many developers do we have?
I'm getting ready to release my first ROM for this phone.
Sent from my HTC6500LVW using Tapatalk
Reefer Madness said:
Our community seems small. How many developers do we have?
Click to expand...
Click to collapse
More than enough. Not really small. We just don't have 30 copies of the same ROM like most lol.
Sent from my HTC6500LVW using xda app-developers app
cstrife999 said:
More than enough. Not really small. We just don't have 30 copies of the same ROM like most lol.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
This^ Previous phone was the GNex and it was unbelievable how many variants and kangs there were for CM10, AOKP, etc. I ran a lot of them but in the end there wasn't all that much that was different from the original rom. In a lot of cases, the variant ran worse.
Sent from my HTC6500LVW using Tapatalk
Quality is always better than quantity
Like was mentioned above, some phones have 200 Rom threads, but really what's the difference between the Rom? They (aosp variants) are 90% cm based with varying mods pulled from aokp source with pa stuff as well
Really, no disrespect intended those 3 aosp roms are all that matter as everything else is just mashed up and derivative of them
As for sense, you only really need a few roms as well; something stock for those who only want root and a few basic mods, some kind of aroma Rom with user configurable options, and or a rom with a lot if built in mods (well you don't need them lol)
Really imo if you have 5 or 6 roms that meet the above criteria you are set
Unless you have a need to flash a different rom every day that has 1 more bs script or 1 different mod in it
The end user doesn't always see the forest from the trees
I agree with what has been said already. Quality is better than quantity... My old S2 had about 194873 ^6 worth of different roms. Touchwiz this and AOSP that and don't forget the AOKP, with CM and a side of Sense ports. In the end I dropped myself on a really good rom called The Blu Kuban which was headed up by rujelus22 over in the Epic 4g Touch development forum. I ran that rom for about 18 months before I nix'd my device and went over to the red side here at Verizon. I heard he went forth to the S4 and has kept that rom's traditions alive. He was one dev who was helped by the many and made a rom that many made their daily drivers just like I did.
I know we have a good community over here as well as even before beaups dropped rumrunner on us we had a few devs tinkering with their roms.
Now remember! A community is only as good as the people around it. Support your devs any way you can if it's simple donations or a click of the thanks buttons. But most of all, be part of the community. List the bugs you find in the roms, mods, and tweaks. Help the devs make the best they can and we all prosper.
I'd still like to see old Sense on this phone. Like Sense 3 or 4.
I'd also like to see a CM variant built off Sense base. Like the old style ROMs that had all full Sense apk compatibility but no Sense launcher. Not sure if this is doable with Sense 5 though.
And last but not least, hopefully a dev will pick up Ubuntu Touch.
Just a daydreamin' wishlist.. lol
Can't port old sense to new hardware. Plus the old stuff was lower resolution.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button
tylerlawhon said:
Can't port old sense to new hardware. Plus the old stuff was lower resolution.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button
Click to expand...
Click to collapse
you could port sense4+ to this phone (someone did it on the intl one) as the kernel base is the same (3.4.x)
dont know why you would really want to, but its possible
nitsuj17 said:
Quality is always better than quantity
Like was mentioned above, some phones have 200 Rom threads, but really what's the difference between the Rom? They (aosp variants) are 90% cm based with varying mods pulled from aokp source with pa stuff as well
Really, no disrespect intended those 3 aosp roms are all that matter as everything else is just mashed up and derivative of them
As for sense, you only really need a few roms as well; something stock for those who only want root and a few basic mods, some kind of aroma Rom with user configurable options, and or a rom with a lot if built in mods (well you don't need them lol)
Really imo if you have 5 or 6 roms that meet the above criteria you are set
Unless you have a need to flash a different rom every day that has 1 more bs script or 1 different mod in it
The end user doesn't always see the forest from the trees
Click to expand...
Click to collapse
Consumer choice is always a win. I'd kill for a thread with five million views and fifty three thousand replies. Developers in different sections have had months to build their own form of paradise. Android Revolution HD has fullSnapdragon 600 (GPU) rendering. I want to try that.
Reefer Madness said:
Consumer choice is always a win. I'd kill for a thread with five million views and fifty three thousand replies. Developers in different sections have had months to build their own form of paradise. Android Revolution HD has fullSnapdragon 600 (GPU) rendering. I want to try that.
Click to expand...
Click to collapse
thats a bs mod that requires the deleting of a lib (and does nothing)
the end user might enjoy that, real developers know the work done in roms and can sort out the differences between fancy features in a changelog and real code changes and development
views and posts have nothing to do with the work that go into a rom....you can have a thread that explodes because it has a leaked version of sense, a large user base of a rom that drives discussion and hypes upcoming releases, massive bug issues that require help and dicussion, new hboots or firmware needed to run new updates and so on
thread views and # of posts, as well as individual member post count and thanks count is really deceptive and a TERRIBLE barometer of worth in the development community
the best and most important kernel, rom, root exploit, recovery and so on developers that exist in the android world often have a relatively low post and thanks count, whereas guys who release stock deodexed roms made with a rom kitchen in cygwin have tens of thousands of posts and thanks which leads new users and even more experienced ones to inflate their value and skillsets
developers can generally sort out whos who amongst themselves, but its unfortunate that the end user often cant; usually through no fault of their own
nitsuj17 said:
thats a bs mod that requires the deleting of a lib (and does nothing)
the end user might enjoy that, real developers know the work done in roms and can sort out the differences between fancy features in a changelog and real code changes and development
views and posts have nothing to do with the work that go into a rom....you can have a thread that explodes because it has a leaked version of sense, a large user base of a rom that drives discussion and hypes upcoming releases, massive bug issues that require help and dicussion, new hboots or firmware needed to run new updates and so on
thread views and # of posts, as well as individual member post count and thanks count is really deceptive and a TERRIBLE barometer of worth in the development community
the best and most important kernel, rom, root exploit, recovery and so on developers that exist in the android world often have a relatively low post and thanks count, whereas guys who release stock deodexed roms made with a rom kitchen in cygwin have tens of thousands of posts and thanks which leads new users and even more experienced ones to inflate their value and skillsets
developers can generally sort out whos who amongst themselves, but its unfortunate that the end user often cant; usually through no fault of their own
Click to expand...
Click to collapse
Perhaps you should stick to answering the questions you were asked. In any case, it would be smarter to back a winning horse.
Reefer Madness said:
Perhaps you should stick to answering the questions you were asked. In any case, it would be smarter to back a winning horse.
Click to expand...
Click to collapse
Not to start a war, but I'm going to give you benefit of doubt you probably don't know him. What he said is true.. And you probably just proved his point too.
His work on other devices is proof of that. Give it time, we will see more options now that the crowd is turning more s-off.
Sent from my Nexus 7 using Tapatalk 4
Reefer Madness said:
Perhaps you should stick to answering the questions you were asked. In any case, it would be smarter to back a winning horse.
Click to expand...
Click to collapse
He did .. You must have not read it...
Sent from my HTC6500LVW using xda app-developers app
cstrife999 said:
He did .. You must have not read it...
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Here I was thinking it was truly reefer madness...lol
Sent from my Nexus 7 using Tapatalk 4
dottat said:
Not to start a war, but I'm going to give you benefit of doubt you probably don't know him. What he said is true.. And you probably just proved his point too.
His work on other devices is proof of that. Give it time, we will see more options now that the crowd is turning more s-off.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I know what he said is true and I don't care. CPU vs GPU. That interests me.
When will we see a aosp rom for our note 3
Tomorrow when the clock strikes 12. I promise
Sent from my magic spaceship
When people stop asking for ETA's.
sent from my sm-9005.
Yerv Melkonian said:
When will we see a aosp rom for our note 3
Click to expand...
Click to collapse
When will we see people stop asking for aosp roms? Thats the real question, this phones barely a month old smh.
Sent from my note 2 ya bish!
d12unk13astard said:
When will we see people stop asking for aosp roms? Thats the real question, this phones barely a month old smh.
Sent from my note 2 ya bish!
Click to expand...
Click to collapse
We're just excited. Let us wag our tails and scratch at the door until our owner opens the door for us. So to speak. LOL!
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
dragonstalker said:
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
I would love to see that
Sent from my SM-N900T
Is there a Google edition or developer edition coming? Has that been confirmed anywhere? I too am really missing cm, aokp, pa, and especially pac man. Man, what I'd give for pac man on this beast! I REALLY hope we get some aosp love.
Sent from my SM-N900T using Tapatalk
dragonstalker said:
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
You sir have just explained the reason I fell in love with android, aosp, the rooting community. A lot of people don't get and are unappreciative of the works of ROM devs. So much greed and selfishness I've seen on xda since after the g1 days. Its always *****ing and bickering and this and that and demanding. Thank you to all the devs out there. Without you guys, android will be a Disney Land that never opened its gates
Sent from my SM-N900T using xda app-developers app
pathtologos said:
Is there a Google edition or developer edition coming? Has that been confirmed anywhere? I too am really missing cm, aokp, pa, and especially pac man. Man, what I'd give for pac man on this beast! I REALLY hope we get some aosp love.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
+24
CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
Why would you quote me and say exactly what i said in a long drawn out explanation. I'm guessing you missed the punctuation in my response. I mean you said everything i said, down to how the CM is a work in progress. Sheesh.
CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
DUDE I couldn't have said it better myself. You devs are wizards.
Usually when a New J series is out, our community of great developers are all over it finding ways to root and making rooms. Since the J4 has been out for a few months there hasn't been any sort of news or updates. Are there any teams working on it?
I'm afraid that the possibility is slim, since the J4 is not widely released (do correct me if I'm wrong) in the US, UK, or other big-market countries, but rather released in smaller-market countries in Africa, Asia, etc, and even so released rather quietly w/out major press releases. So unless the phone is widely released (relative to other Galaxy phones out there), I'm inclined to believe that such teams would have little to no access to the J4, and thus no development to progress for it.
(Believe me, I'm remaining optimistic that at least an unofficial recovery might be on the works, but there won't be much progress unless the J4 is more widely used/picked-up)
Or, you can learn how to do it yourself.
Not the TWRP porting, but you can definitely MOD your stock ROM to add features Samsung annoyingly disable for not being a "premium" device.
You don't need to know much of coding, you can learn as you go. When the J2 Prime was released (and even to this day) there aren't any custom ROMs so I had to teach myself and I've accomplished great things
Just wait for TWRP and then the doors will open, you'll see
;77491224 said:
Or, you can learn how to do it yourself.
Not the TWRP porting, but you can definitely MOD your stock ROM to add features Samsung annoyingly disable for not being a "premium" device.
You don't need to know much of coding, you can learn as you go. When the J2 Prime was released (and even to this day) there aren't any custom ROMs so I had to teach myself and I've accomplished great things
Just wait for TWRP and then the doors will open, you'll see
Click to expand...
Click to collapse
Huh, that's interesting; I'll surely take a look.
Could you further elaborate on the "features" that Samsung disabled? (I don't use a lot of Samsung G's built-in features, so I'm not too knowledgeable on such; tried Google-searching, only came up w/ disabling apps, so that didn't really help...)
Debstup said:
Huh, that's interesting; I'll surely take a look.
Could you further elaborate on the "features" that Samsung disabled? (I don't use a lot of Samsung G's built-in features, so I'm not too knowledgeable on such; tried Google-searching, only came up w/ disabling apps, so that didn't really help...)
Click to expand...
Click to collapse
For starters, things like edge screen or scroll capture (things that I use a heck of a lot)
I found it funny is that all it took as to change a bit of code here and there, add the right apps and edge screen was working perfectly on the J2 Prime (a very low-end phone).
Samsung went out of their way to delete this feature which is pretty ridiculous if you ask me.
Themes were also disabled for this device, but after reading a few guides I was able to implement a ROM control that allows the user to change the color to their liking
The dev community is always willing to lend a hand, just as long as you're not lazy and expect everything to be put out for you.
I feel the J4 can make a dev out of someone looking to add more functionality to their device (the J2 Prime made a dev out of me )
Ok, so the TWRPBuilder's experimental TWRP build (huge thanks to @yshalsager for this miracle) is on TWRPBuilder's site: twrpbuilder.github.io/downloads/twrp/
Like any TWRP builds, there is ABSOLUTELY zero guarantee that it would work (I tried the first one & it didn't work, haven't had the chance to test the latest one yet)
---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------
Ok, so the TWRPBuilder's experimental TWRP build (huge thanks to @yshalsager for this miracle) is on TWRPBuilder's site: twrpbuilder.github.io/downloads/twrp/
Like any TWRP builds, there is ABSOLUTELY zero guarantee that it would work (I tried the first one & it didn't work, haven't had the chance to test the latest one yet)
The J4 uses identical chipset as the J5 prime G570F/M/DS.
I have both and they are great phones for their segment.
Sadly neither are well supported by ROM developers, due to the Exynos chip, I think.
missioner said:
The J4 uses identical chipset as the J5 prime G570F/M/DS.
I have both and they are great phones for their segment.
Sadly neither are well supported by ROM developers, due to the Exynos chip, I think.
Click to expand...
Click to collapse
@yshalsager did a test custom recovery for J4 (via TWRPBuilder): https://twrpbuilder.github.io/downloads/twrp/
Have been unable to test it atm (stuck in 7-day jail); if you want to have a go at it & let him know the results, go right ahead!
but first we have to unlock oem.but the problem is no oem unlock in the settings
brownstyle said:
but first we have to unlock oem.but the problem is no oem unlock in the settings
Click to expand...
Click to collapse
Yeah that's the 7-day "jail" I was talking about - theoretically you have to leave your phone on non-stop (no reboots, no shutdowns) for 7 whole days straight, then the OEM Unlock option should become available in Dev Settings (it's a confusing security measure by Samsung on Oreo devices)
any update guys? im really bored with this phone now
up
guys can we root our device j4 using magisk?
#push
#push
#push
#push
Do not spam, if you don't get an answer then that means that nobody is working on it
up
brownstyle said:
up
Click to expand...
Click to collapse
Dude