Database Info

[Q] Merging firmwares?

I've been thinking about the possibility of extracting the firmware from a Galaxy Tab 2 (ICS) and merging it with the kernel and build.prop from the 7 Plus (Honeycomb).
Technically I can't think of a reason that it wouldn't work, I'd think that the challenge would be getting the kludged FW back onto a 7 plus.
Would it be a futile effort? Maybe if Samsung releases ICS for the Plus, but who knows when that will be.
I don't have any experience on these two Android device other than in an end user capacity (though I have been reading) and very little on a few other Android devices so I dunno if it's feasible, but I thought I'd mention the idea.
Anyone with deeper experience on these things think it might be viable?

I know the devices have different hardware specs so I don't know if it would meld...

fewt said:
Technically I can't think of a reason that it wouldn't work, I'd think that the challenge would be getting the kludged FW back onto a 7 plus.
/QUOTE]
technically: different hardwares, the ics may need some changes on kernell itself to work, so you may not be able to use hc one.
besides the differences of one device to other is not just encapsulated on kernel, the dalvik virtual machine needs to be ported to every machine depending on aspects.
Enviado do meu MB525 usando o Tapatalk
Click to expand...
Click to collapse

leodfs said:
fewt said:
Technically I can't think of a reason that it wouldn't work, I'd think that the challenge would be getting the kludged FW back onto a 7 plus.
Click to expand...
Click to collapse
technically: different hardwares, the ics may need some changes on kernell itself to work, so you may not be able to use hc one.
besides the differences of one device to other is not just encapsulated on kernel, the dalvik virtual machine needs to be ported to every machine depending on aspects.
Enviado do meu MB525 usando o Tapatalk
Click to expand...
Click to collapse
Technically, it shouldn't as kernel interfaces don't change that much between releases. Since both processors are ARM, I wouldn't expect a problem with the Dalvik VM either but I guess I could be wrong there.
Would be interesting to see, but I can tell there isn't any interest in it. I've been trying to find a good reference on where to get started with this stuff, but it just seems like a hodgepodge of information sprawled all over the place.
Anyone have a solid guide to getting started building custom firmware that isn't the great google?

fewt said:
Technically, it shouldn't as kernel interfaces don't change that much between releases. Since both processors are ARM, I wouldn't expect a problem with the Dalvik VM either but I guess I could be wrong there.
Would be interesting to see, but I can tell there isn't any interest in it. I've been trying to find a good reference on where to get started with this stuff, but it just seems like a hodgepodge of information sprawled all over the place.
Anyone have a solid guide to getting started building custom firmware that isn't the great google?
Click to expand...
Click to collapse
I suggest you read the CyanogenMod 9 thread in development as you will experience the same problems porting this over without a working ICS kernel.
Here are some threads I've found useful on porting and building from source:
http://www.iphoneandroidtips.org/miui/how-to-port-miui-v4-to-android-phones/
http://forum.xda-developers.com/showthread.php?t=1153233
http://forum.xda-developers.com/showthread.php?t=1499411
http://forum.xda-developers.com/showthread.php?t=1169570
http://forums.androidcentral.com/ht...how-build-your-own-kernel-package-source.html
http://source.android.com/source/index.html
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
These threads are for all different models of phones and the methods may or may not work for our tablets but the principles are pretty much the same. In the instance of porting over MIUI 4 you have to start with a working CM9 ROM as it requires a working AOSP ICS kernel, which we don't have yet. Our devs are working their butts off trying to port one over from another device but its slow going without the proper source code that Samsung won't release.

I would think if it were as easy as combining the two, who would need XDA?

kzoodroid said:
I suggest you read the CyanogenMod 9 thread in development as you will experience the same problems porting this over without a working ICS kernel.
Here are some threads I've found useful on porting and building from source:
http://www.iphoneandroidtips.org/miui/how-to-port-miui-v4-to-android-phones/
http://forum.xda-developers.com/showthread.php?t=1153233
http://forum.xda-developers.com/showthread.php?t=1499411
http://forum.xda-developers.com/showthread.php?t=1169570
http://forums.androidcentral.com/ht...how-build-your-own-kernel-package-source.html
http://source.android.com/source/index.html
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
These threads are for all different models of phones and the methods may or may not work for our tablets but the principles are pretty much the same. In the instance of porting over MIUI 4 you have to start with a working CM9 ROM as it requires a working AOSP ICS kernel, which we don't have yet. Our devs are working their butts off trying to port one over from another device but its slow going without the proper source code that Samsung won't release.
Click to expand...
Click to collapse
This is awesome, I really appreciate you taking the time to write it up.

I hope you have success, either way you will learn, that's why we bought our android for.
I think there's a lot of interest, but this thing is dangerous, lots of devs have their devices bricked trying port or improve,.
My advice is not of an android developer, but of someone that has some experience of customizing or compiling the Linux Kernel. any little thing you forget render you with a system that will not boot. And even if they use the same kernel, ics may need some things activated that hc may not
Sent from my GT-P6210 using Tapatalk 2 Beta-5

KitKat 4.4

Sssooo.... According to what I read last night, KitKat is supposed to be able to be usable on pretty much all Android phones, all the way down to those with 512mb of RAM.
Any thoughts as to whether the Charge is gonna get some love with this (certainly, I know, NOT from Big Red)?
"I've got a revolution behind my eyes..."
--Battle Flag

There will be peace in the middle east first. :banghead:
Sent from my SM-N900V using XDA Premium 4 mobile app

Just because they say it could run on lower end phones doesn't mean it will run w/o lag and so on. I heard the chez won't be getting kit Kat so what does that tell you about the older phones.
Sent from my HTC6500LVW using Tapatalk

The only thing that will run on lower end devices is the new launcher and Google apps. The new ui is supposed to be included in the new launcher and make lower end devices feel and look more like newer ones.
Sent from my ADR6425LVW using Tapatalk

lazarus0000 said:
Sssooo.... According to what I read last night, KitKat is supposed to be able to be usable on pretty much all Android phones, all the way down to those with 512mb of RAM.
Any thoughts as to whether the Charge is gonna get some love with this (certainly, I know, NOT from Big Red)?
"I've got a revolution behind my eyes..."
--Battle Flag
Click to expand...
Click to collapse
The problem with an upgrade to any newer OS on the Charge is the radios. I don't see KitKat and an exception.:crying::crying:

Interesting how they had it where you could use Hangouts as your default SMS App with all the Emoji smileys on phones with Gingerbread including the Charge on the leaked version from the Nexus 5. It was fully working and I tried it. However, now that it's released to everybody through the Play Store, the SMS option is for Android 4.0 Only.

just got kitkat on my razr.... wish I knew how to port, b/c then I would attempt to port this great ROM over to the old Charge....

I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though

pyroman512 said:
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2284985
http://wiki.cyanogenmod.org/w/Doc:_porting_intro

pyroman512 said:
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
Click to expand...
Click to collapse
I think you're on the right track, though I think I'd stick with CM11 rather than CM10.2.

Well I am really interested in learning how to build. So I think I will run a few builds for the Fascinate and then see what I can do for the Charge. My programming experience is intermediate. I feel confident I can learn the process and at least get a semi functional kitkat build up and running and then maybe others could help work out the bugs

pyroman512 said:
Well I am really interested in learning how to build. So I think I will run a few builds for the Fascinate and then see what I can do for the Charge. My programming experience is intermediate. I feel confident I can learn the process and at least get a semi functional kitkat build up and running and then maybe others could help work out the bugs
Click to expand...
Click to collapse
good luck brother... i'd be glad to test for ya.
some tips that you may/may not already know:
my understanding is that OS 4+ require EXT4 rather than RFS, so it might help to start with a kernel that allows this conversion. there are a few floating around that work.
someone (JT) has successfully (and I guess relatively easily) ported ICS and JB to the charge, the key aspects not working though were mobile data and camera.
I'm told the key road block is the RIL for the kernel in order to get those aspects functioning properly.
as for me, I'd be happy with just a working camera, as the Charge is used by my son as a WiFi-only media player/gaming device. he likes to take pictures/videos, so this is the only thing preventing me from converting it the latest JB port.
again, good luck, and let us know how the progress goes!

Well I just started a new job and am settling into that so time will be scarce for a bit. I wouldn't even know how to start with the RIL. I would definitely want to get the camera working provided I can even successfully build CM11. I want to make it clear that I am new to this so it is a big undertaking for me and I have a lot to learn. Once I get a build enviroment set up I will see if I can make some fascinate builds for practice since it is very similar to the charge. Then i will reach out to sbrissen or jt1134 and see if they can give me any pointers. I forked their code on github already.

pyroman512 said:
Well I just started a new job and am settling into that so time will be scarce for a bit. I wouldn't even know how to start with the RIL. I would definitely want to get the camera working provided I can even successfully build CM11. I want to make it clear that I am new to this so it is a big undertaking for me and I have a lot to learn. Once I get a build enviroment set up I will see if I can make some fascinate builds for practice since it is very similar to the charge. Then i will reach out to sbrissen or jt1134 and see if they can give me any pointers. I forked their code on github already.
Click to expand...
Click to collapse
As a previous owner of a droid charge, I honestly hope I can squeeze some use out of it as a media device.

AOSP on Galaxy Tab 3 10.1

So, i opened this therad because there no persons pushing and Developing custom AOSP Roms for the Galaxy Tab 3.
I'm opening it here because the Android Developing forum is a bit AFK.
Also, my first question is,
Why we are not using the Android x86 source, put a little bit from samsung open source and Tab 3 binaries it, and compile it?
Its so hard?
We are the xda-developers, we can do it!

Curious..
superboom said:
Also, my first question is,
Why we are not using the Android x86 source, put a little bit from samsung open source and Tab 3 binaries it, and compile it?
Its so hard?
We are the xda-developers, we can do it!
Click to expand...
Click to collapse
Yes, I'm asking myself the same, the Galaxy Tab 3 is such a famous device and out since July, but still there are nearly no ROMs out. Are there any ROMs planned or will this device soon be moved to the low activity section? CyanogenMod officially supported the Galaxy tab and the galaxy tab 2, but it doesn't seem like they are planning to support the galaxy tab 3?
Is there a special reason for that?, I'm just wondering?

chaoskoch said:
Yes, I'm asking myself the same, the Galaxy Tab 3 is such a famous device and out since July, but still there are nearly no ROMs out. Are there any ROMs planned or will this device soon be moved to the low activity section? CyanogenMod officially supported the Galaxy tab and the galaxy tab 2, but it doesn't seem like they are planning to support the galaxy tab 3?
Is there a special reason for that?, I'm just wondering?
Click to expand...
Click to collapse
you know why we need developers who want to put some time in this device and at the moment we don't have much dev's around here so wait...

Willing to get my hands dirty...
safariking said:
you know why we need developers who want to put some time in this device and at the moment we don't have much dev's around here so wait...
Click to expand...
Click to collapse
The most device development I've done to date has been a simple android app, but I'm willing to get dirty on this one. I just came into possession of one of these devices over xmas, and I never let a good device go to waste. I do have 17 years of programming experience in multiple languages including C++ and Java, and a lot of web-based languages, so I'm hoping to come up to speed relatively quickly.
I'll poke around here and on the net over the next few days and see if I can teach myself, but if someone could point me in the direction of some quick start tutorials for building custom roms, I'll get started.

ush

AnthonyAlmighty said:
The most device development I've done to date has been a simple android app, but I'm willing to get dirty on this one. I just came into possession of one of these devices over xmas, and I never let a good device go to waste. I do have 17 years of programming experience in multiple languages including C++ and Java, and a lot of web-based languages, so I'm hoping to come up to speed relatively quickly.
I'll poke around here and on the net over the next few days and see if I can teach myself, but if someone could point me in the direction of some quick start tutorials for building custom roms, I'll get started.
Click to expand...
Click to collapse
Anthony, I think one thing that is holding people back on this device is a good recovery. The ones available now are painfully slow. I'm guessing there is some power saving mode on the x86 chip that needs to be tweaked to get it performing well. Once that was fixed, it would be a lot easier to experiment with ROMs. -- Bud

Also Interested
Anthony and all, hi and hello. Thinking of shaking the rust off, as I also just came into possession of a GTab3, 10.1 inch, over this holiday season. I haven't built anything in a long time, but anyone who ran a Vibrant a couple years ago around here, should recognize my handle. I maintained a rom for the Vibrant for quite a while, from Froyo to ICS, then life got busy.
Popping into here today, I'm kinda sad to see there's not much if any in the way of development on this device. Happy to have root, thats a start. cduced was right, we do need a better recovery option, at least one that is faster, though what we have now is workable. TWRP may be slow, but it's something. We were always hung up on doing pure aosp source build for the Vibrant, because Sammy is not known for making their kernel source easily and readily available. Working from an existing zip to kang it is easy, but really thats just the same rom, maybe stripped and repackaged. A source build is the desirable outcome.
Though I haven't begun looking into things for this baby yet, and my adb and build tools are far out of date, I am very interested in working towards a better set of options for this device. 4.2.2 still? I can't believe Sammy hasn't released a 4.3 update, that's sad, but goes to show the lack of support they give their devices, to anyone who's been there you know, but you also know, determined devs can make it a better world.
Anthony, and anyone else interested in trying to improve this device, feel free to PM me, I'm thinkin' we should make a Google Hangout or something, make it easier to communicate.

Br1cK'd said:
Anthony and all, hi and hello. Thinking of shaking the rust off, as I also just came into possession of a GTab3, 10.1 inch, over this holiday season. I haven't built anything in a long time, but anyone who ran a Vibrant a couple years ago around here, should recognize my handle. I maintained a rom for the Vibrant for quite a while, from Froyo to ICS, then life got busy.
Popping into here today, I'm kinda sad to see there's not much if any in the way of development on this device. Happy to have root, thats a start. cduced was right, we do need a better recovery option, at least one that is faster, though what we have now is workable. TWRP may be slow, but it's something. We were always hung up on doing pure aosp source build for the Vibrant, because Sammy is not known for making their kernel source easily and readily available. Working from an existing zip to kang it is easy, but really thats just the same rom, maybe stripped and repackaged. A source build is the desirable outcome.
Though I haven't begun looking into things for this baby yet, and my adb and build tools are far out of date, I am very interested in working towards a better set of options for this device. 4.2.2 still? I can't believe Sammy hasn't released a 4.3 update, that's sad, but goes to show the lack of support they give their devices, to anyone who's been there you know, but you also know, determined devs can make it a better world.
Anthony, and anyone else interested in trying to improve this device, feel free to PM me, I'm thinkin' we should make a Google Hangout or something, make it easier to communicate.
Click to expand...
Click to collapse
Hey I want aosp on this device too! At the very least, id like a custom kernel that I can overclock to reduce lag. Ive never created a rom, but I dont think roms are the issue...id be interested in porting roms that already exists...x-note for multiwindow features, or pac-rom for a highly customized device.
Are you still up for the projects? Lets heat these forums up!!!

Ideas4ya said:
Hey I want aosp on this device too! At the very least, id like a custom kernel that I can overclock to reduce lag. Ive never created a rom, but I dont think roms are the issue...id be interested in porting roms that already exists...x-note for multiwindow features, or pac-rom for a highly customized device.
Are you still up for the projects? Lets heat these forums up!!!
Click to expand...
Click to collapse
Thanks guys for give it a try, I'm like the other owner don't understand why there is no interest for this devise didn't check before buy and now start to regret

Meteore said:
Thanks guys for give it a try, I'm like the other owner don't understand why there is no interest for this devise didn't check before buy and now start to regret
Click to expand...
Click to collapse
There are some devs now they just relesed 2 but there tw based there trying it just takes awile because of lack of devs.

mylifeandroid said:
There are some devs now they just relesed 2 but there tw based there trying it just takes awile because of lack of devs.
Click to expand...
Click to collapse
It's ok I have already seen and tried them :laugh:. I understand the concept of work on something new and the lack of dev it's just that I was surprised because I thought tab 3 was like the others tabs so the development was more evolve.no problem.

Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style

Br1cK'd said:
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Click to expand...
Click to collapse
This is true but there is finally a bit of interest and may come up with some new goodies..... the reason they all have the same updater.script is because of the recoveries.... they need a little more work to get them to work with the x86 architecture
Sent from my GT-P5210 using xda app-developers app

Br1cK'd said:
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Click to expand...
Click to collapse
Hey PM me with any test builds of the kernels please.
Sent from my GT-P5210 using XDA Premium 4 mobile app

I think someone has to pm restl3ss!
http://forum.xda-developers.com/showpost.php?p=49126542&postcount=90
Let's see what can we do here!

Calcu said:
I think someone has to pm restl3ss!
http://forum.xda-developers.com/showpost.php?p=49126542&postcount=90
Let's see what can we do here!
Click to expand...
Click to collapse
Dont understand your post.... the link goes to one of his posts
Sent from my GT-P5210 using xda app-developers app

Because in this post (if i'm not wrong) he tells that is making a recovery with 4 guys more.
something needed here xD.
Enviado desde mi Note 2

Calcu said:
Because in this post (if i'm not wrong) he tells that is making a recovery with 4 guys more.
something needed here xD.
Enviado desde mi Note 2
Click to expand...
Click to collapse
Lol.... I see yeah... I am also in the process of building recovery but its a long time coming. Right now im reading a lot of material on how to build from source as that the route of the prob. Its this damb x86 architecture
Sent from my GT-P5210 using xda app-developers app

Maybe.... we can port something from here
http://www.engadget.com/2014/01/06/micromax/
Enviado desde mi Note 2

Push
If anyone have time, pm me and we can discuss about. I'm not a developer, but we can discuss ideas how to bring cm to the device

Whats the most sold KitKat Rom right now?

I'm on Gummy Nightly 4.4.2 and I'm looking for something more stable. Life is a bit hectic right now so I'm not able to constantly flash a new rom.
What has been the best 4.4.2 rom that you've had the most success with?

to each there own .
moderators dont like these types of threads cuz they cause arguments

Beanstalk and Liquidsmooth! Waiting for the Pac-Man release!

If life is to hectic to find a rom I suggest stock.
Sent from my SCH-I535 using xda app-developers app

I'm liking my PA 4.4 pa_d2vzw-4.0-BETA-20131208 that one it seems to be the only one with a functional camera so far.

GlitchMob said:
Whats the most sold KitKat Rom right now?
Click to expand...
Click to collapse
Define "most solid"...
All you are going to get is people's limited opinions. Plus, if someone has only used 1 or 2 different ROMs - vs ALL of the ones available - they really can't comment

hallstevenson said:
Define "most solid"...
All you are going to get is people's limited opinions. Plus, if someone has only used 1 or 2 different ROMs - vs ALL of the ones available - they really can't comment
Click to expand...
Click to collapse
I meant to say "stable" I just want a rom where the basic functions like Camera work and I'm able to use instagram etc without it crashing. Gummy is fine, but not being able to use the camera is a big thing. I would like a multi-window feature that Hyperdrive has, but I'd like to stay at 4.4.2.
Also, no I will never go back to stock. As for those who have used one or two different roms their opinions are still valid. They can say whether it was stable or not.

twistedillutions said:
to each there own .
moderators dont like these types of threads cuz they cause arguments
Click to expand...
Click to collapse
Lol what do all the nerds start typing in caps lock? its a thread dude in the appropriate area.

GlitchMob said:
I meant to say "stable" I just want a rom where the basic functions like Camera work and I'm able to use instagram etc without it crashing. Gummy is fine, but not being able to use the camera is a big thing.
Click to expand...
Click to collapse
A ROM with a non-functioning camera would never even get consideration from me ! Same applies to ROMs with no working data. Does the Gummy thread tell you the camera doesn't work ? I'd hope so !!
For what it's worth, I've tried the following KK ROMs (with my opinion/comments):
Beanstalk (Gideon's build) - good ROM, no complaints that I can recall.
Omni (Gideon's build) - too plain or simple (or boring) for me. Didn't have a few features that I've grown to like (I blame PAC for that !!). It was stable though.
LiquidSmooth (both the LS team version and Gideon's) - my preferred ROM at the moment. Runs fine, everything works, and has many of the features I like. Between two builds a week and a half apart, I see add'l things added too.
ParanoidAndroid (notta's build) - can't recall any details at the moment.

I suggest trying ParanoidAndroid 4.0 BETA. Yes, it is a beta but it is very stable. I have been using it since Notta switched to 4.4.x. The are still working out small bugs (like every other KK ROM), but like I said, it's very stable.
It does not have multi-window. For that I suggest Omni ROM. I've been using that on my ASUS TF300T and it works awesome!

As evident by some above commentary, XDA is not a support site and users are expected to test all Roms to make their own, independent, determinations as to what is stable for them.
Thread closed.

[LP Roms][Poll][Note3 Revive Team] Weekly Support Rom Vote, Which do you want?

Vote for your Favourite *Unsupported* Rom to be given weeklies!​
Please Note i will only support the N9005, hlte.
Why?
Currently the amount of lollipop AOSP/CM based roms for the Note 3 is running a tad short for my liking, i believe in choice and i believe that if you have the hardware to do it, why not? I will be running this poll for a week to see which Roms you guys want to see rolling out for the Note 3 and i will roll them out to you on a weekly basis, i can probably build a few roms in a day so the top few will be what i choose to support.
If you want a Rom added to the Poll just ask me and i'll add it, so what are you waiting for? Vote and i'll start rolling them out!​

Reserved for Results
Reserved for Results

Note3 Revive Team said:
Vote for your Favourite *Unsupported* Rom to be given weeklies!​
Please Note i will only support the N9005, hlte.
Why?
Currently the amount of lollipop AOSP/CM based roms for the Note 3 is running a tad short for my liking, i believe in choice and i believe that if you have the hardware to do it, why not? I will be running this poll for a week to see which Roms you guys want to see rolling out for the Note 3 and i will roll them out to you on a weekly basis, i can probably build a few roms in a day so the top few will be what i choose to support.
If you want a Rom added to the Poll just ask me and i'll add it, so what are you waiting for? Vote and i'll start rolling them out!​
Click to expand...
Click to collapse
This one probably is just wishful thinking, due to the fact that back on JB/KK it was very difficult for the dev, now with LP it will be even more difficult.
There used to be a ROM for the S4 named BlackBox.
It was a hybrid between TouchWiz and AOSP, the dev ported AOSP frameworks and libraries to work with TouchWiz. The ROM was SICK. And not easy to do. Not sure if the ROM had an altogether different kernel or any TW kernel could work.
Wishful thinking... :/

sirobelec said:
This one probably is just wishful thinking, due to the fact that back on JB/KK it was very difficult for the dev, now with LP it will be even more difficult.
There used to be a ROM for the S4 named BlackBox.
It was a hybrid between TouchWiz and AOSP, the dev ported AOSP frameworks and libraries to work with TouchWiz. The ROM was SICK. And not easy to do. Not sure if the ROM had an altogether different kernel or any TW kernel could work.
Wishful thinking... :/
Click to expand...
Click to collapse
That is probably beyond my skills as ive never ported, only built from source, however i'll get in touch with the developer of that Rom and see if he is willing to lend a hand to try get that going for the Note 3, i honestly thought there would be more interest on this thread thou..
Any AOSP/CM roms you want for weeklies haha?

Note3 Revive Team said:
That is probably beyond my skills as ive never ported, only built from source, however i'll get in touch with the developer of that Rom and see if he is willing to lend a hand to try get that going for the Note 3, i honestly thought there would be more interest on this thread thou..
Any AOSP/CM roms you want for weeklies haha?
Click to expand...
Click to collapse
As odd as it is, I got used to the close-to-stock TW ROMs. Don't mistake me, AOSP ROMs are fast as Hell, way more moddable, more beautiful, and I like that. However, for the way I use my Nope 3, close to stock suits my needs better.

sirobelec said:
As odd as it is, I got used to the close-to-stock TW ROMs. Don't mistake me, AOSP ROMs are fast as Hell, way more moddable, more beautiful, and I like that. However, for the way I use my Nope 3, close to stock suits my needs better.
Click to expand...
Click to collapse
It's rare you find a samsung device where people are actually happy with Touchwizz
So is no one interested in suggesting weeklies for an AOSP Rom? Or perhaps i should make a custom stock (Not that there are enough already)?
I honestly thought there would be more interest in this thread! What's going on guys??

Note3 Revive Team said:
It's rare you find a samsung device where people are actually happy with Touchwizz
So is no one interested in suggesting weeklies for an AOSP Rom? Or perhaps i should make a custom stock (Not that there are enough already)?
I honestly thought there would be more interest in this thread! What's going on guys??
Click to expand...
Click to collapse
I believe it might be something like this...
The user base needs something entirely different from the two (three if you count MIUI) options, we've got used to it. And some people might have the ideas for something different but lack the skills to do it. On one side you have AOSP (most of the AOSP ROMs function and behave almost the same; simple fact, not bashing the work of anyone, I don't have the knowledge to bash it ), on the other - TouchWiz. Both have their uses.
I lack the knowledge on how to do it, apparently the whole team of Samsung that makes TouchWiz doesn't (xDDDDDDDDDDDDD)... to combine all the functionality of the device at it's top performance with a really sleek UI implementation that's different enough to make the user treat and use the device differently.
Otherwise, I'd theme TW with black, grey, blue, holo colors n stuff and make the UI look like the control panel of some spaceship seen in sci-fi. The device itself carries the "Galaxy" moniker, ffs, and Samsung made it sound and look like a f***ing toy!
Making an AOSP ROM then stabilizing it, from what I've read, is no easy task for the whole Google team, it seems...
I am afraid that the Note 3 simply lacks the attraction to crackheaded devs who would tear Ubuntu Touch's a** in half, merge it with AOSP then slap that combination on top of whatever's left of TouchWiz. xD We have most of the major AOSP ROMs, can't tweak too much TW because of it's damn closed source, and... that's that. :/
Sorry if this was incoherent.
P.S. I am also sorry if any of this seems disrespectful, I don't mean it to be, given the fact that you're willing to actually build the ROM that's most demanded. Wish you luck.

Those are 2 recognize ROMs since my Nexus 5. :laugh:

ps000000 said:
Those are 2 recognize ROMs since my Nexus 5. :laugh:
Click to expand...
Click to collapse
Well when i hit 10 posts, and perhaps a little more interest is gathered in the thread then i can get these builds of vanir and nameloss rolling out to the community.
I am suprised thou i really am that no one seems to use AOSP/CM roms on the galaxy note 3!