To-Do List For our device :) - HTC Desire C

Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI(fix lockscreen)
-CM7
-Sense 4.1
-cm10.1 WiFi and Bluetooth
-cm10 WiFi authentication issue
-S-OFF
-Roms for cdma version
-Sense 4.1.2
Just pop requests underneath and ill update reguarly.

Shad0wPanda said:
Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI
-CM7
Just pop requests underneath and ill update reguarly.
Click to expand...
Click to collapse
Sense 4.1 (If possible)

Shad0wPanda said:
Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI
-CM7
Just pop requests underneath and ill update reguarly.
Click to expand...
Click to collapse
Hahaha, heres an LG UI Rom, iv'e had it for a while, just lockscreen doesnt work at all! so slide down NC and hit settings to unlock, then install a custom locker such as holo locker! I'll post in the dev threads when i can be bothered, but test that out..
http://d-h.st/2V2
Click to expand...
Click to collapse

i think gettin bt and wifi implemented in cm 10.1 should be a good place to begin

lead3r1 said:
i think gettin bt and wifi implemented in cm 10.1 should be a good place to begin
Click to expand...
Click to collapse
+1
but we really need the devs to go back to work

CM7 FTW
CM7 first ... it would be super buttery smooth for us ...

How are you so certain it'd be "buttery smooth"? Cuz I'm not sure, if not totally negative on that matter.

How are you so certain it'd be "buttery smooth"? Cuz I'm not sure, if not totally negative on that matter.
Click to expand...
Click to collapse
Brnt you don't have to flash cm7... What's with all the gingerbread hate??
Sent from my HTC Desire C using xda app-developers app

I suggest we go back to XP then. It's going to run so much better on our new PCs!
It's not hate, you just get overexcited over nothing without even putting some though into it. Go on, prove me gingerbread will run smoother than JB/ICS, but without these facts your words are nothing.

brnt said:
I suggest we go back to XP then. It's going to run so much better on our new PCs!
It's not hate, you just get overexcited over nothing without even putting some though into it. Go on, prove me gingerbread will run smoother than JB/ICS, but without these facts your words are nothing.
Click to expand...
Click to collapse
I think you have your analogy wrong. Going from a newer version of Windows to an older version of Windows is pointless because...well...it's still Windows.
However, if you were to go from Ubuntu to, say, Slackware, you would definitely see a boost in performance because Slackware is far less taxing on the available resources. The same could be said about going from JB to GB. GB requires less resources and can therefore run smoother/faster on hardware designed for a higher version of Android. This is a well known fact throughout the Android community because nearly every JB or ICS based device has GB ROM development in some form or another.
It's still Android. Roughly 90% of the differences between JB/ICS and GB lie in the overall appearence, not the functionality.

IDEA
Or lets make CM10 even better
Like eliminate WiFi problems and hotspot problems etc :fingers-crossed:
What do you think?

S off would be good.
Not first priority though
sent from CM10'd Desire C

Phenziox said:
S off would be good.
Not first priority though
sent from CM10'd Desire C
Click to expand...
Click to collapse
It would be very useful though but it's more HTCs job
Sent from my HTC Desire C using xda premium

@soupmagnet, i agree entirely with that statement, however, where is the desire coming from for having GingerBread Roms? if it was desired so much, then why not buy a gingerbread phone in the first place? Would've been cheaper and there are still devices on the market, some with faster processors then the Desire C, if you wanted GingerBread, should've bought a GB Device, you don't go buy a brand new Windows 8 PC to deliberately downgrade it to a legacy OS like vista and limit the features you have access to. It lacks all logic in all honesty.. You don't go to sell a phone after use being all like, Yeah it has 2.3.5 GB on it, or brag to your mates, yeah my device is android 2.3.5, fact is 4.2.2 is the best android so far, Android has only improved over time, GB on our device is like an i7 with vista, you just don't do that kind of thing..

penguin449 said:
@soupmagnet, i agree entirely with that statement, however, where is the desire coming from for having GingerBread Roms? if it was desired so much, then why not buy a gingerbread phone in the first place? Would've been cheaper and there are still devices on the market, some with faster processors then the Desire C, if you wanted GingerBread, should've bought a GB Device, you don't go buy a brand new Windows 8 PC to deliberately downgrade it to a legacy OS like vista and limit the features you have access to. It lacks all logic in all honesty.. You don't go to sell a phone after use being all like, Yeah it has 2.3.5 GB on it, or brag to your mates, yeah my device is android 2.3.5, fact is 4.2.2 is the best android so far, Android has only improved over time, GB on our device is like an i7 with vista, you just don't do that kind of thing..
Click to expand...
Click to collapse
The problem with your logic is that Gingerbread based devices (with a few exceptions) only have hardware that is capable of meeting the low demands of Gingerbread.
For many people, the worth of their device is in its functionality, not its "bragging rights". I will never have Windows on my computer simply because of the features it provides. I use Linux, because of it's speed, stability and and overall functionality. ICS and JB do have some nice additional features, but at a noticeable cost of available resources and stability, and the overall functionality is still nearly the same. While higher versions of Android do provide some "improvements", they are mostly linked to the user interface (which many people don't necessarily like) and there are very few performance improvements. So for you to say that it "lacks all logic" is, well, illogical in itself.
While you may like what JB and ICS have to offer and prefer that for your daily driver, I don't think it's fair to ridicule others' personal preference in Android versions, considering the majority of changes between these versions are exclusive to the UI and not Android itself.

Off-topic... naughty naughty
Sent from my HTC Desire C using xda premium

Getting back on topic...
It would be nice to see more CDMA support though. I have a shell script, based on bin4ry's exploit, to root the CDMA variants, but it needs to be converted over to Windows' batch scripting language. If anyone wants to have a go at it, just let me know.
As far as ROMs are concerned, we can use the existing GSM ROMs, but a patch will need to be made. It wouldn't be that difficult to implement and would be much easier than creating all new CDMA ROMs.
The biggest problem would be getting a working recovery. I tried unpacking the existing (GSM) recovery and replaced the kernel with the phone's stock kernel but it didn't work out very well. I think a new recovery would need to be built from source, but I'm running into strange compile errors when compiling the stock kernel from source. I don't have experience building custom recovery so it's going to be challenging trying to figure everything out, but I think I can handle it.
Clearly, the need for CDMA support is low, but it's far from non-existent. I'm more than willing to take the reigns on this project, but I may have to take advantage of some of the experience around here, assuming there are those willing to lend a hand.

soupmagnet said:
The problem with your logic is that Gingerbread based devices (with a few exceptions) only have hardware that is capable of meeting the low demands of Gingerbread.
For many people, the worth of their device is in its functionality, not its "bragging rights". I will never have Windows on my computer simply because of the features it provides. I use Linux, because of it's speed, stability and and overall functionality. ICS and JB do have some nice additional features, but at a noticeable cost of available resources and stability, and the overall functionality is still nearly the same. While higher versions of Android do provide some "improvements", they are mostly linked to the user interface (which many people don't necessarily like) and there are very few performance improvements. So for you to say that it "lacks all logic" is, well, illogical in itself.
While you may like what JB and ICS have to offer and prefer that for your daily driver, I don't think it's fair to ridicule others' personal preference in Android versions, considering the majority of changes between these versions are exclusive to the UI and not Android itself.
Click to expand...
Click to collapse
I stand corrected, thankyou for clearing that up for me, i never thought to look at it in this way, however, when you do get a working recovering, i do so believe i added cdma support in SHTD, the rom was both configured for cdma and for gsm, as it is in the build.prop also!, however a cdma aosp kernel would be needed

cm10.1 wifi bluetooth fixed would be a cool rom... Devs plz fix it... We noobs will be greatfull to you......:laugh::laugh::good:

akashgartia said:
cm10.1 wifi bluetooth fixed would be a cool rom... Devs plz fix it... We noobs will be greatfull to you......:laugh::laugh::good:
Click to expand...
Click to collapse
Don't rush them. They have other stuff to do. If you want it done, you could learn and try it yourself.

Related

Where have all the ROMs gone.....

Not to get on a rant here guys, but I came from Win mo and those guys really work it over there......
Roms galore of every size and shape. I kinda expected that from this really open platform.
No new looks , no new feel.
Wassup, are we waiting for things to shake loose or what.
Must every one roll their own?
Just asking......
Sent from my SAMSUNG-SGH-I897 using XDA App
ryoung101 said:
Not to get on a rant here guys, but I came from Win mo and those guys really work it over there......
Roms galore of every size and shape. I kinda expected that from this really open platform.
No new looks , no new feel.
Wassup, are we waiting for things to shake loose or what.
Must every one roll their own?
Just asking......
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=786532
Where is your rom?
Have you read anything on this forum?
And fyi, you can dl launchers and home screens to change looks without a rom right from app store. Search = friend
Sent from my SAMSUNG-SGH-I897 using XDA App
Also, I doubt much ROM development will happen (except for a few champions of the people, like DG) until the Samsung official Android 2.2 comes out, and more importantly, the source code for that 2.2 version is released.
But to be honest, with a piece of hardware this capable, even the 2.1 ROMs are pretty sweet. That and other projects are currently ongoing. Take for example the Vodoo project, which basically has entirely scrapped the default filesystem, and gone with EXT2. And will soon be coming with other tweaks and options for the awesome SAMOLED screen in our phones. Those aren't exactly simple bits of code being whipped up.
Yes, I come from the WinMo side of XDA as well, but around here, it's quality not quantity that counts.
Yikes.
http://forum.xda-developers.com/showthread.php?t=786532
http://forum.xda-developers.com/showthread.php?t=787194
http://forum.xda-developers.com/showthread.php?t=787194
just some ideas... when froyo gets to the captivate, im sure they will start cranking them out even more...
When ryoung checks in again in a year there will surely be more roms.
Sent from my SAMSUNG-SGH-I897 using XDA App
Everyone is so mean to the OP. He cant help it he is sofa king we tar did.
It's actually understandable why the OP is asking. I too spent a lot of time with WinMo and was used to having 10+ ROMs available. But I quickly realized that WinMo NEEDed modified ROMs just to give it functionality and performance. When I got my HTC Touch HD I thought I had the pinnacle of mobile phone technology, but yet I was still always trying new ROMS because I wasn't satisfied with the performance and functionality.
This Captivate is my first Android phone and from what I can tell we don't actually NEED a ROM to make the phone awesome.
WinMo needed ROMs to be a good experience, hence there was a lot of people focused on that aspect of development.
Android, and especially our awesome phone, doesn't need a new ROM to be a good experience so most of the genius developers are able to focus on other projects like various applications rather than just simply trying to get our phones to function.
WinMo required lots of hacking and ROMs to get the same functionality that our phone has by simply installing a new widget or app.
So to the OP, if you ever check back, you don't see a ton of ROMs because frankly they're not required. Welcome to Android! It's a much smoother and satisfying experience than your previous WinMo experience. I can say that because I was just like you just a couple months ago.
sschrupp said:
It's actually understandable why the OP is asking. I too spent a lot of time with WinMo and was used to having 10+ ROMs available. But I quickly realized that WinMo NEEDed modified ROMs just to give it functionality and performance. When I got my HTC Touch HD I thought I had the pinnacle of mobile phone technology, but yet I was still always trying new ROMS because I wasn't satisfied with the performance and functionality.
This Captivate is my first Android phone and from what I can tell we don't actually NEED a ROM to make the phone awesome.
WinMo needed ROMs to be a good experience, hence there was a lot of people focused on that aspect of development.
Android, and especially our awesome phone, doesn't need a new ROM to be a good experience so most of the genius developers are able to focus on other projects like various applications rather than just simply trying to get our phones to function.
WinMo required lots of hacking and ROMs to get the same functionality that our phone has by simply installing a new widget or app.
So to the OP, if you ever check back, you don't see a ton of ROMs because frankly they're not required. Welcome to Android! It's a much smoother and satisfying experience than your previous WinMo experience. I can say that because I was just like you just a couple months ago.
Click to expand...
Click to collapse
and not all of us know how to make a rom quite yet
tbae2 said:
and not all of us know how to make a rom quite yet
Click to expand...
Click to collapse
Yeah, I don't doubt that there WILL be more ROMs. Especially with the scrabble to get Froyo before Samsung releases it. This is a new phone after all. I just know that with my old WinMo phones the first thing I would do with them is feel unsatisfied and attempt to install some hacked ROM to feel a little less satisfied.
With this phone I'm just happy right out of the box. Of course I don't use the GPS so maybe if I did I'd grumble a bit. But otherwise I think this phone is just incredible.

The Honeycomb Conundrum

Let me preface this by saying that I have nothing but the utmost respect for the dev community (NC and otherwise) and I really don't mean to step on any toes with this. I'm fairly new at all this and I've got some questions.
Alright, so as we've all heard by now, Google (whether their reasons are benevolent or not) are withholding the AOSP release of Honeycomb and that kind of rains on everyone's nook color parade. We've got a mostly working port of HC that kind of sags in the performance area. Its almost been enough to make me flash Gingerbread but there are a few things - namely the browser, email app, soft keys and notification system - that I'd miss. The new + screen is nice, but I've been using launcher pro as it runs seemingly faster than the stock launcher, so I'm already missing out on that.
Now, from what I understand, and feel free to correct me if I'm wrong, deeperblue's HC port uses parts of Gingerbread to make everything all hunky dory.
My question is this; would a viable solution to slow HC performance be to make a new rom and pump MORE Gingerbread in? i.e. Take HC's notification system replace GB's phone-style notification pane. Make it mostly gingerbread with some tablet friendly nip/tucks here and there.
I realize there are things like softkeys and the bottom taskbar mod, but HC's handling of the android buttons and the new notification system is just so appealing. Its making the choice of which rom to run unduly difficult. And while I can't cook a rom, I'm hoping someone who can sees this and runs with it, if it is feasible, that is.
Truthfully... It's up in the air like everything else, unless a DEV directly comes out of the shadows and saids, hey i'm going to do it... Then we just won't know. Honestly, I'm sad that we won't see HC right around the corner, but CM7 is pretty awesome. And the Xoom is scheduled to drop down to $599 (Wifi only) today, making it a lot more competitive than the 3g.
That's not to say that I personally have $599 to drop and go buy a new tablet, but it does mean that you'll probably see them on craigslist or ebay in a few months for a bit cheaper. =\
The honey comb preview is awsome but to many apps don't work.
Tyfighter said:
My question is this; would a viable solution to slow HC performance be to make a new rom and pump MORE Gingerbread in?
Click to expand...
Click to collapse
That was kinda the plan. CM7 development was going in a way that all the improvements (Bluetooth, partially working DSP, an accelerated interface) were going to be directly ported to Honeycomb once the source released. But without the source, that can't happen.
Basically Google has completely screwed any Nook Color fans wanting Honeycomb.
The only improvement that can be made is that a ROM could be made from the final SDK. That would be just as laggy, and will lack new features (Bluetooth, DSP, etc.), but it would be able to use Android tablet apps.
From the conversation about Google's move on the net, many are saying there won't be a Honeycomb source at all, and the next source dump will come with Ice Cream months from now.
So Honeycomb fans have a choice- either try out the CM7 modification that you talked about to make CM7 more Honeycomb-like, or start saving up for that Xoom...
[email protected] said:
The honey comb preview is awsome but to many apps don't work.
Click to expand...
Click to collapse
what apps dont work? most of the major ones have worked for me so far...
im finding that the hc rom is very usable for a daily driver...although bluetooth and dsp support would be very nice...
nolook said:
what apps dont work? most of the major ones have worked for me so far...
Click to expand...
Click to collapse
Any Tablet app that requires the final SDK version (aka all those Xoom apps) won't work on our preview build.
poofyhairguy said:
Any Tablet app that requires the final SDK version (aka all those Xoom apps) won't work on our preview build.
Click to expand...
Click to collapse
Thank you for your informative reply.
It seems now that my best bet is going to be t see what the cm7 guys cook up. Hopefully this aosp business will spark some of the innovation that the android community is known for. I'd love to help, but its not exactly my forte
With regards to what apps aren't working, my marketplace only seems to intall apps when the stars are right. I often have to attempt an install upwards of five times to have it succeed, if it even does. Otherwise i get insufficient storage errors or indeterminate error 18
sorry if i am hijacking this a bit, but i had thought that android was 'open source'. why the change in the plans to not release hc? is this to protect the hw manufacturers like mot who have hc on the xoom, and freeze out users who want it ported non supported platforms? Otherwise, I can't understand the logic.
I got the nc cause i had thought it had the best $/performance of any android based tablet. For half the price of others, it had great screen, and forgetting bt, etc., nice hw specs. With hc, it would be fantastic!
How else to counter ipads if not to get hc on as many tablets as possible?
I wonder if the fact that the playbook is running our apps has anything to do with it. If so, I don't mind anything that makes it rough for RIM.
Sent from my Desire HD using XDA App
jbinbi said:
sorry if i am hijacking this a bit, but i had thought that android was 'open source'. why the change in the plans to not release hc? is this to protect the hw manufacturers like mot who have hc on the xoom, and freeze out users who want it ported non supported platforms? Otherwise, I can't understand the logic.
Click to expand...
Click to collapse
It is open source and it WILL be released however at this time they don't think it's ready for final release (I've heard of various tweaks they need to make in the xoom) and are working those out prior to releasing it to devs

i dont understand, why so many ics roms based on an alpha?[rant]

already about 5 ics roms not counting the cm9 alpha, why??
they all have the same bugs
they all have the same things working
super ics kangorama?
http://forum.xda-developers.com/showthread.php?t=1360567
koush's + launcher pro added..
nexus mv ics?
http://forum.xda-developers.com/showthread.php?t=1364411
koush's + glados kernel + v6 supercharger
ultimate ics?
http://forum.xda-developers.com/showthread.php?t=1363765
koush's + some extra wall papers + file explorer
all these things are just a completely alpha ics build with some hacks thrown in.. why?? why not just make a post in the ics thread (either by kwiboo or koush) saying "hey guys use launcher pro if you feel its buggy" or "here is link to glados kernel" instead of making "New ultimate sweet fast ICS rom" when all you are doing is downloading one of the actual source built ics roms and opening it with 7zip and dropping in a new boot.img in there then asking for donations :/
/rant
It is no different than the numerous GB/CM based ROMs. Who cares?
Bounced off a tower to a forum near you!
I think that He ( OP ) won't be happy until they say Beta.. its alpha for a reason. so many bugs much more than beta. just sit happy with GB and give it time. I rushed it and lost the ability for Google Wallet, nothing can fix what went wrong with my phone.
xjreyes said:
I think that He ( OP ) won't be happy until they say Beta.. its alpha for a reason. so many bugs much more than beta. just sit happy with GB and give it time. I rushed it and lost the ability for Google Wallet, nothing can fix what went wrong with my phone.
Click to expand...
Click to collapse
What happened? I had wallet set up and ready to go, tried it at rite aid and wouldn't go through...
Sent from my Nexus S using XDA App
these people couldn't be taking part in a hobby for them, could they be just trying to learn the ins and outs of android, heck they couldn't even be kids learning to code and all are getting excited to show off what they complied.
Last time I checked you were not required to flash every rom in the Dev section. So lets take a step back I don't like miui nothing wrong with it but should I be complied to start a thread asking why we have topics about when I don't care for it.
icecoldbong said:
/rant
Click to expand...
Click to collapse
You said it....
Chill out. We have to get AOSP working bug-free in the first place, then they'll start looking different. Even CM9 doesnt have any CMsettings or anything special. We're sorry that something that we're beating Google at (ICS release for NS) currently is not to your standards.
In due time.....in due time.
I see where the OP is coming from, but I disagree. The fact that the devs work hard to bring the OS to our devices is pretty appreciated. They pretty much do Google's work for free by modifying the code.
Sent from my Nexus S using XDA App
icecoldbong said:
already about 5 ics roms not counting the cm9 alpha, why??
they all have the same bugs
they all have the same things working
super ics kangorama?
http://forum.xda-developers.com/showthread.php?t=1360567
koush's + launcher pro added..
nexus mv ics?
http://forum.xda-developers.com/showthread.php?t=1364411
koush's + glados kernel + v6 supercharger
ultimate ics?
http://forum.xda-developers.com/showthread.php?t=1363765
koush's + some extra wall papers + file explorer
all these things are just a completely alpha ics build with some hacks thrown in.. why?? why not just make a post in the ics thread (either by kwiboo or koush) saying "hey guys use launcher pro if you feel its buggy" or "here is link to glados kernel" instead of making "New ultimate sweet fast ICS rom" when all you are doing is downloading one of the actual source built ics roms and opening it with 7zip and dropping in a new boot.img in there then asking for donations :/
/rant
Click to expand...
Click to collapse
you missed these two.. http://goo.gl/bdy4w and http://fitsnugly.euroskank.com/sammich/crespo/
i can probably find you a few more if you would like more variety
simms22 said:
you missed these two.. http://goo.gl/bdy4w and http://fitsnugly.euroskank.com/sammich/crespo/
i can probably find you a few more if you would like more variety
Click to expand...
Click to collapse
lol im not mad that they are all buggy, im mad that people are "deving" with a buggy base and just adding to it. why not be a little patient, if you cant create it/build it from source, wait til the base you will be using to 7zip and copypaste into your rom becomes stable. dont use an alpha build to promote your name
icecoldbong said:
lol im not mad that they are all buggy, im mad that people are "deving" with a buggy base and just adding to it. why not be a little patient, if you cant create it/build it from source, wait til the base you will be using to 7zip and copypaste into your rom becomes stable. dont use an alpha build to promote your name
Click to expand...
Click to collapse
I don't think you quite understand how it works currently. There is no buggy base. They're attempting to adapt AOSP source code to compile and execute correctly on the Nexus S. This is way more complicated than you think. Almost all "bugs" you see are byproducts of tinkering with configurations, compile-ations, etc, in an attempt to get it working properly.
To put things in perspective, ICS development for the Nexus S is light years ahead of all other devices. For that reason alone, we should be grateful. Others are still struggling to either boot, or get somewhere AFTER boot.
If you don't like the way it's done, then wait for the official ROM. You have a choice, after all.
nickmv said:
I don't think you quite understand how it works currently. There is no buggy base. They're attempting to adapt AOSP source code to compile and execute correctly on the Nexus S. This is way more complicated than you think. Almost all "bugs" you see are byproducts of tinkering with configurations, compile-ations, etc, in an attempt to get it working properly.
If you don't like the way it's done, then wait for the official ROM. You have a choice, after all.
Click to expand...
Click to collapse
yes, two roms are getting built from the source on xda; kwiboo and koush. then all the others.
both kwiboo and koush thread is full of bug reports of people using a different rom like brainmaster, ultimate ics, kangorama ics, etc.
all this does is add confusion from the rom chef adding things to the original rom developers work
what im suggesting/ranting is that if a rom chefs should be a little more patient in making more spinoff roms that don't really add much besides to confusion for noob users
Your argument makes a LOT more sense now. I agree, if people are posting bugs in Koush/Kwiboo sections when running brainmaster or other tweaked versions, then that's bad.
Your original argument didn't really point this out.
Not much can be done about that, aside from aggressive moderation. Tweakers will be tweakers.
nickmv said:
Your argument makes a LOT more sense now. I agree, if people are posting bugs in Koush/Kwiboo sections when running brainmaster or other tweaked versions, then that's bad.
Your original argument didn't really point this out.
Not much can be done about that, aside from aggressive moderation. Tweakers will be tweakers.
Click to expand...
Click to collapse
Most of the bugs posted are not even valid. One in particular is known issue even on the GNexus.
The biggest issue I see is code optimization at this point.
One thing I think no one has mentioned is ICS may never be super fast on the NS. I will be much faster on dual core hardware
Bounced off a tower to a forum near you!
RonnieRuff said:
One thing I think no one has mentioned is ICS may never be super fast on the NS. I will be much faster on dual core hardware
Click to expand...
Click to collapse
This is one thing that has been bothering me as well. Every single one of these ROMs are not truly as smooth as Gingerbread. In no way do they even reach the fluidity found in Gingerbread ROMS. The hardware acceleration helps, but even then you can still feel the difference between the two Android releases. I have yet to hear a proper explanation as to why this is happening and I was hoping that the fix for this would be Google releasing the official Ice Cream Sandwich update.
Is it is code optimization as you say? Or is there more to it than that? I want to believe that hardware doesn't play a significant role here.
Eclair~ said:
This is one thing that has been bothering me as well. Every single one of these ROMs are not truly as smooth as Gingerbread. In no way do they even reach the fluidity found in Gingerbread ROMS. The hardware acceleration helps, but even then you can still feel the difference between the two Android releases. I have yet to hear a proper explanation as to why this is happening and I was hoping that the fix for this would be Google releasing the official Ice Cream Sandwich update.
Is it is code optimization as you say? Or is there more to it than that? I want to believe that hardware doesn't play a significant role here.
Click to expand...
Click to collapse
Agree 100% no released rom before ota is even out is worth running.. I ran koush or w/e and it worked but felt like I was holding a brick.. ruff! Brainmasters straight looks like android donut.. but so does cyanogens.. no disrespect to any of the above.. but htcclay is god..
Edit: wasn't brainmaster it was some one else.. sorry
Sent from my iPhone 4S using Siri
BLEEDCOLORYOU said:
Agree 100% no released rom before ota is even out is worth running.. I ran koush or w/e and it worked but felt like I was holding a brick.. ruff! Brainmasters straight looks like android donut.. but so does cyanogens.. no disrespect to any of the above.. but htcclay is god..
Edit: wasn't brainmaster it was some one else.. sorry
Sent from my iPhone 4S using Siri
Click to expand...
Click to collapse
Strange, I've found that Koush's latest (CM9 Alpha 11) is plenty fast, not significantly slower than GB. Definitely Kwiboo v2 was slow as molasses, but then again it came out days ago (a long time when it comes to how fast things are moving). BM v5 is pretty fast but buggy. Also, it seems that adding franco kernel to any of these also speeds things up significantly, but I haven't tried it with CM9 Alpha 11 yet.
oakamil said:
Strange, I've found that Koush's latest (CM9 Alpha 11) is plenty fast, not significantly slower than GB. Definitely Kwiboo v2 was slow as molasses, but then again it came out days ago (a long time when it comes to how fast things are moving). BM v5 is pretty fast but buggy. Also, it seems that adding franco kernel to any of these also speeds things up significantly, but I haven't tried it with CM9 Alpha 11 yet.
Click to expand...
Click to collapse
I found kwiboo's to be a lot more stable than koush's. although koush's had more functionality.. my bluetooth didnt work, and i got many errors.
Understand that we are using old binaries. ICS will run just as good as gingerbread, if not, better. These will make a world of difference
RonnieRuff said:
One thing I think no one has mentioned is ICS may never be super fast on the NS.
Click to expand...
Click to collapse
I'd kind of disagree with this. In its current early state here on the NS, I've gotten it running butter smooth and highly responsive, on a 1.1 OC/UV kernel. This is WITHOUT tweaks to filesystem, etc. If certain apps would just display properly when GPU Rendering is turned on, and some battery stuff worked out, I'd be 100% content.
Now granted, I've seen it running on the SGS2 and Galaxy Nexus and they're clearly speedier, but in my experience, my apps run just as fast as they did in GB.
On a side note....wanna see slow? It's been ported to the T-Mobile G1! HA! The first, original android phone!
I agree. there was actually a recent article on android police about this. There is no problem with people making their own roms but don't clog up the development section with "roms" that really all they do is bundle some easily downloadable market apps and some wallpapers and call it a new rom.
What the SGS2 xda forum actually did was split the dev section into 2 . One for original dev work and one for spin offs.

Is there really any need to flash a custom Rom on the One?

Firstly, please don't get me wrong here. Im not trolling in the slightest and I really appreciate all the work the devs do here.
With the HTC One having such high specs is there really any need to flash custom Roms? In my opinion all of them seem the same and don't look or feel any different to the stock rom on the One. The only benefit I can see is for Root access.
Im sure there is a lot of "under the hood" tweaks that are done but are these really noticeable or beneficial to the end user? Other peoples thoughts would be interesting.
dr9722 said:
Firstly, please don't get me wrong here. Im not trolling in the slightest and I really appreciate all the work the devs do here.
With the HTC One having such high specs is there really any need to flash custom Roms? In my opinion all of them seem the same and don't look or feel any different to the stock rom on the One. The only benefit I can see is for Root access.
Im sure there is a lot of "under the hood" tweaks that are done but are these really noticeable or beneficial to the end user? Other peoples thoughts would be interesting.
Click to expand...
Click to collapse
Actually yes, I wish to get CM working fully on HTC One.
It gives us an alternate experience than what HTC wanted us to.
Best of all, you don't have to wait so long for HTC to update their phones.
Especially when they abandon the One, we rely on CM.
But I'm really hoping for the success of the One, nobody could resist the look and feel of the One.
Livebyte said:
Actually yes, I wish to get CM working fully on HTC One.
It gives us an alternate experience than what HTC wanted us to.
Best of all, you don't have to wait so long for HTC to update their phones.
Especially when they abandon the One, we rely on CM.
But I'm really hoping for the success of the One, nobody could resist the look and feel of the One.
Click to expand...
Click to collapse
I totally agree the updates and the benefit of getting rid on Sense if you dont like it is a real benefit. But is there a need for multiple Sense custom roms?
dr9722 said:
I totally agree the updates and the benefit of getting rid on Sense if you dont like it is a real benefit. But is there a need for multiple Sense custom roms?
Click to expand...
Click to collapse
That's subjective I guess. But for something like example HTC DROID DNA or Butterfly, Sense 5 gets ported before HTC did. So I guess it's also a huge benefit.
Earlier updates is the main reason why I will be rooting, these phone networks take ages to update it's unavailable!!
Also there are some very nice skinned roms out there
I won't be unlocking my bootloader for a while. Not until I am at least sure that my device is working 100% and that will take a couple of weeks. I was eager to root it etc but I was reading about HTC's warranty and it seems as though it is a very long winded process. Maybe you wish to do the same?
m00moo said:
I won't be unlocking my bootloader for a while. Not until I am at least sure that my device is working 100% and that will take a couple of weeks. I was eager to root it etc but I was reading about HTC's warranty and it seems as though it is a very long winded process. Maybe you wish to do the same?
Click to expand...
Click to collapse
yep ill be in no hurry either.
when i finally get a device im happy with yea i will root and flash custom rom, but not CM - Sense 5 is great and IMO is much better than stock JB - there are a few minor things I would like added, but I have no doubt they will be added to custom sense 5 roms in due course.
to me, there is no point in being a flashaholic. flash the latest stable base, and then keep up with custom kernels for battery.
thats me, idk bout u guys
Personally something that will push me over the unlock bootloader line is when either when A) IF the HTC logo can become mapped as a button, or B) A full relock becomes available lol
For me, absolutely. I consider some features (such as long press vol key to skip tracks) essential. There are also always some visual things I like to change no matter how well it is made
I just need root to enable volume key wake, and ill want to remap the keys. Everything else looks flawless
Sent from my ADR6425LVW using xda app-developers app
do you need root etc. to install flash on ONE ?
ChazyChaz said:
do you need root etc. to install flash on ONE ?
Click to expand...
Click to collapse
No. To my knowledge, the built in browser has flash support.
What about Wi-Fi hotspot support?
Sent from my Galaxy Nexus using xda app-developers app
While there's obviously no NEED, a lot of people will prefer to flash ROMs for a variety of different reasons.
I'd say the main reasons are;
*The ability to have a pure AOSP look which is preferred by a lot of people (especially those who come from a Nexus device). Also, a lot of people don't like the look/feel of Sense and will therefore want to change the UI to something which is more preferable to them.
I, for example, have never tried Sense before and could quite possibly hate it once I finally test it. On the flip side of that, I may love it but at least custom ROMs will give me the ability to completely change the UI whilst giving me a ton more customizations and optimizations than a custom launcher would do.
*As mentioned at the end of the first reason, customization is a huge part of what a lot of people do with their devices. For example, when I had my SGS2 I used to love the ability to flash a simple ROM and have a ton of customization at my fingertips, so I could edit the look of my phone to my hearts content.
*Some people are simply flashaholics and have ORD (Obsessive ROM-flashing/updating Disorder). I'll normally flash every ROM in sight if the device is new and there aren't many ROMs available yet. This way it gives me a good early decision as to what type of ROM I'd prefer on said device. However, once the device starts getting more development and more ROMs start appearing in quick succession, I'll then make my mind up about which ROM to choose and generally won't change ROM for the vast majority of the devices lifetime.
Got a HTC? Join the HTC Hangout Thread
I unlocked, rooted and flashed now because in a few months time the phone will be setup perfectly; all the right apps, all the right data, all in the right place (and HTC might of discovered a way to do a Sensation on us (S-Off))
With the phone rooted I can be relatively confident of getting it back to my currently backed up state after any major updates (and, when I finally install some games, get their progress restored as well)
Sent from my Tricked out HTC One via xda-developers application
Sense means HTC. I don't see any reason to buy HTC if I'm not gonna use sense.
Because HTC makes great hardware. I buy HTC exclusively, but I rip sense off it ASAP and put AOKP or CM or something without sense. Nexus devices are generally not top of the line hardware, they're supposed to be a benchmark for development (i.e. midrange). That said, N4 has more impressive specs than usual, but I can't imagine buying an LG phone. I have never realized LG even made smartphones, only flip phones until the N4 was released.
Still, HTC makes best hardware, I just generally don't like sense. That said, sense 5 does look interesting.
Sent from my EVO LTE using xda premium
Having options is nice!
Dharkan said:
Sense means HTC. I don't see any reason to buy HTC if I'm not gonna use sense.
Click to expand...
Click to collapse
To a certain extent, yes, I agree with you on that statement. However, sometimes you just need a change and it is nice to have the option of running AOSP roms as well. I would much rather go back and forth between Sense/AOSP than TouchWiz/AOSP after having my GS3.
No. Roms are for old devices. Lol
Sent from my C6603 using Tapatalk 2

Rom Port Team Effort - Let's bring a diversity of roms to our P880.

Rom Port Team Effort
Hello P880 community.
This post has the purpose to put together a group of users / developers, who are willing to participate into bringing a different set of roms into our community.
These set of roms that I'm thinking, can range from complete Sense ports to more customized and maybe less popular roms (like ColorOS, LiGux, FlymeOS, FluidUI, etc..).
What's valid on this thread:
- CM / AOSP (any base we already have) themed (like Samsung TouchUI, Optimus, Blur, etc..). So you can grab any rom (with author authorization), theme it (i mean, not just shove an apk as default theme, I mean neat theming ).
- Ports from other devices (evert port needs to have clear authors permission to port it).
- All users are very welcome, everyone can participate, users with porting / developing skills are needed as well.
The idea is simple, we're not going to use this thread to post the work, this is just a thread to talk about possible projects.
We can start by listing which devices are hardware compatible and the port is "easily" possible.
Roms that can be used as a base for eventual future ports.
CM10.2 - thanks to laufersteppenwolf for compiling this build promptly for this purpose
http://goo.im/devs/laufersteppenwolf/CM10.2//cm-10.2-20140305-UNOFFICIAL-p880.zip
- - - - -
I strongly recommend the use of MultiRom for testing ports and other roms. That way you can maintain your working rom and whenver feeling adventurous you can without going through the hassle of backup / restore / yada yada yada that we are all too familiar with.
http://forum.xda-developers.com/showthread.php?t=2655988
- - List of Devices with hardware similar / close / identical to the 4X - -
- HTC One X
- HTC One X +
- More ??
- Possible roms to port:
Right now would be nice to see a OEM rom, such a touchwiz or Sense
Work in Progress
N/A available
(awaiting sugestions
So, what do you guys think? ? Any users with good porting skills ? I know we have good developers! Ideas? Sugestions?
Write away
A few guides from XDA - They may not be all you need to get the job done, but a LOT of important information is written here. Don't forget to thanks their authors
Guides / Tutorials
How to Port Roms by @saywhatt
How to Port Manufacturer Rom. by @GalaxyUser
How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs by @Peteragent5
PS - Every work that is possible to port and if someone decides to invest time in it, it needs explicit authors permission.
Sure if a few people want a particular rom i can bring it to our device, but i would much prefer helping first time rom builders do this own their own then they can maintain it also
JoinTheRealms said:
Sure if a few people want a particular rom i can bring it to our device, but i would much prefer helping first time rom builders do this own their own then they can maintain it also
Click to expand...
Click to collapse
Well, I though about some sort of "voting" to bring a "specific" rom.
Personally, I'd love to have Sense on our device. I had two HTC's before and I miss that Sense interface :b
But far as I'm aware, isn't an easy thing to port.
About your offer, this thread stands mostly with learning. The idea is everyone being able to contribute and more users start bringing roms as their first times. So, thank you so much for lending your help and know how, I'm sure we'll have a fine list of possible ports and then we can talk about how to port them over
Everyone can ask for help and the idea is to everyone who is able to - help.
I like the idea of this thread, but what would also be quite usefull is a list of available ROMs and their maintainer(s).
Also the list should include ROMs someone is working on ATM, so it cannot happpen that 2 devs are working on the same ROM
However, your idea is good, but porting a ROM not from sorce is quite hard, and might need some smali "hacking" in order to resolve bugs.
But well, we're a community, and I guess we can help each other if needed, right
laufersteppenwolf said:
I like the idea of this thread, but what would also be quite usefull is a list of available ROMs and their maintainer(s).
Also the list should include ROMs someone is working on ATM, so it cannot happpen that 2 devs are working on the same ROM
However, your idea is good, but porting a ROM not from sorce is quite hard, and might need some smali "hacking" in order to resolve bugs.
But well, we're a community, and I guess we can help each other if needed, right
Click to expand...
Click to collapse
That's correct! :good:
The main point is to learn helping each other who knows in a month or so, today's whiners are tomorrow's contributors
Jokes aside, the first post will be edited in order to structure and add information.
I'm gonna start with compatible devices (the ones that allow porting in a easy way). Ideas? Besides the HTC One X ? I'm guessing the grouper (N7 2012) besides having the same soc, doesn't have the same screen...
PS - (this would be better with an experienced porter) - Maybe we could start with a easy one, and go on from there
I know we have "how to port" threads all around xda ,but each port is different so we can't use "one hat to fit them all" ... or a ring to rule them all, so we should treat each port differently.
However.. I'm gonna put some xda links about porting to bring some light into the matter for who is "new" on this subject... or for whom's feeling adventurous and can't wait to have "their" rom on "our" device
Oh yes finally, have been waiting for a thread like this for a long time me as well would love to see a sense rom on this phone
cm/aosp roms are not that hard to port most of the time u only need the same screen resolution for it to work. (ported a nexus s touchwiz rom over to my old lg optimus 2x) but would have loved to see some oem roms ported over as well, even though it would be a lot harder to port over. but as a wonderful community as this is we might be able to pull it off
MidnightDevil said:
That's correct! :good:
The main point is to learn helping each other who knows in a month or so, today's whiners are tomorrow's contributors
Jokes aside, the first post will be edited in order to structure and add information.
I'm gonna start with compatible devices (the ones that allow porting in a easy way). Ideas? Besides the HTC One X ? I'm guessing the grouper (N7 2012) besides having the same soc, doesn't have the same screen...
PS - (this would be better with an experienced porter) - Maybe we could start with a easy one, and go on from there
I know we have "how to port" threads all around xda ,but each port is different so we can't use "one hat to fit them all" ... or a ring to rule them all, so we should treat each port differently.
However.. I'm gonna put some xda links about porting to bring some light into the matter for who is "new" on this subject... or for whom's feeling adventurous and can't wait to have "their" rom on "our" device
Click to expand...
Click to collapse
You can add the HOX+ to the list as well
About porting, you need to seperate it in two halfs, porting from source, and "winzipping". TBH, I'm no fas of winzipping at all, but some stuff (like sense or TW) can only be winzipped...
BTW, if you need a 2nd/3rd post, just let me know
Personally, I'd like to see a GFlex or even better, a G2 (/mini) ROM for our phone (KitKat, of course )
This thread has potential
I'm new to this forum,so i dont know whats going on about roms,i see there are few devs working full time.
I think this is the best way to go: Port ALL open source roms,such as we have already,but we need them all.
Second,make a badass kernel,with all features and customizations,possibly 3.4.
Third,and just a suggestion,Make a community ROM?
I really like this thread,and i even more like this OX4 community,you all get along,and i've missed that,i was on a forum that has no frendly people whatsoever.
And,about the roms,the idea is awesome,but i always think of the clash of clans rule,max everything out before going on a higher level.
Sent from my LG-P880 using XDA Premium 4 mobile app
Regarding stock roms, it's an interesting thing, but I'm guessing stock roms are more trouble to port comparing to AOSP or CM.
I remember on the HTC Sensation forums the headaches sense brought to many developers and porters, the bunch of files that needed to be edited, kernel changes (aosp kernel is different from stock / sense kernel in that case).. so Stock roms are maybe harder to port fully.
Right now we have some apks from the G2 (lock screen, messaging, etc..), maybe someone will port some things from the Flex, but the whole base.. hum
@DeHuMaNiZeD , thanks for your reply
The other roms based of AOSP and CM, in my opinion, unless they're different (modded, themed, customized - etc..) but if not, if they are "clean" roms with no changes, then - we have them already I believe you'll agree. (Unless the idea is to test something).
A 3.4 kernel would be something, but perhaps a developer can shed some light here - what benefits would we have from a 3.4 kernel ?
A community rom is indeed long due. This thread is a different subject because it's about *several* roms, ports and tutorials, maybe you would like to create a thread here on General about that? You can start with votes (i believe it's a proper way to do it) with which base should we use (Cm, AOSP, Stock, etc..), included apps (or not), possibly aroma maybe and so on
DeHuMaNiZeD said:
This thread has potential
I'm new to this forum,so i dont know whats going on about roms,i see there are few devs working full time.
I think this is the best way to go: Port ALL open source roms,such as we have already,but we need them all.
Second,make a badass kernel,with all features and customizations,possibly 3.4.
Third,and just a suggestion,Make a community ROM?
I really like this thread,and i even more like this OX4 community,you all get along,and i've missed that,i was on a forum that has no frendly people whatsoever.
And,about the roms,the idea is awesome,but i always think of the clash of clans rule,max everything out before going on a higher level.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, this sounds quite good, but the real problem is: this is a hell lot of work. Also, it needs resources. The sourcecode of a ROM is ~25-30GB. When it's compiled it's about double the size, and takes my PC (8 cores @ 4GHz) about 75Min to compile. Not to mention the time 'til the sources are Downloaded. My 500GB HDD is near to its limit very soon, so sooner or later I will need a new HDD, then I might be able to get another ROM ported, but right now, hard...
Also, why do you need a 3.4 kernel?
MidnightDevil said:
Regarding stock roms, it's an interesting thing, but I'm guessing stock roms are more trouble to port comparing to AOSP or CM.
I remember on the HTC Sensation forums the headaches sense brought to many developers and porters, the bunch of files that needed to be edited, kernel changes (aosp kernel is different from stock / sense kernel in that case).. so Stock roms are maybe harder to port fully.
Right now we have some apks from the G2 (lock screen, messaging, etc..), maybe someone will port some things from the Flex, but the whole base.. hum
@DeHuMaNiZeD , thanks for your reply
The other roms based of AOSP and CM, in my opinion, unless they're different (modded, themed, customized - etc..) but if not, if they are "clean" roms with no changes, then - we have them already I believe you'll agree. (Unless the idea is to test something).
A 3.4 kernel would be something, but perhaps a developer can shed some light here - what benefits would we have from a 3.4 kernel ?
A community rom is indeed long due. This thread is a different subject because it's about *several* roms, ports and tutorials, maybe you would like to create a thread here on General about that? You can start with votes (i believe it's a proper way to do it) with which base should we use (Cm, AOSP, Stock, etc..), included apps (or not), possibly aroma maybe and so on
Click to expand...
Click to collapse
For stock ROMs to work, it's your best bet to use AOSP as your base, and then look for what's missing/broken. This, however, means you need an AOSP base first to work with. And AOSP is not always the easiest thing to get properly running.
About the benefits of an 3.4 kernel: None IMO. All you get is a higher version-number, and that's it. We actually already have some 3.4 features backported, and also tweaked the 3.1 kernel quite a lot. So the actual benefits are all in your head (well, except you count bugs as benefits )
Community ROM? Meh, what for? We have so many ROMs already, so everyone should find the one that suits him/her best
BTW: Thread stuck
laufersteppenwolf said:
Well, this sounds quite good, but the real problem is: this is a hell lot of work. Also, it needs resources. The sourcecode of a ROM is ~25-30GB. When it's compiled it's about double the size, and takes my PC (8 cores @ 4GHz) about 75Min to compile. Not to mention the time 'til the sources are Downloaded. My 500GB HDD is near to its limit very soon, so sooner or later I will need a new HDD, then I might be able to get another ROM ported, but right now, hard...
Also, why do you need a 3.4 kernel?
For stock ROMs to work, it's your best bet to use AOSP as your base, and then look for what's missing/broken. This, however, means you need an AOSP base first to work with. And AOSP is not always the easiest thing to get properly running.
About the benefits of an 3.4 kernel: None IMO. All you get is a higher version-number, and that's it. We actually already have some 3.4 features backported, and also tweaked the 3.1 kernel quite a lot. So the actual benefits are all in your head (well, except you count bugs as benefits )
Community ROM? Meh, what for? We have so many ROMs already, so everyone should find the one that suits him/her best
BTW: Thread stuck
Click to expand...
Click to collapse
Why dont you set up that build server,i think they're cheap atm,or someone could borrow you? It would take a lot less time and effort. that's why i think offical rom support is important,once it's merged to the build bot,its their responsibility.
Sent from my LG-P880 using XDA Premium 4 mobile app
DeHuMaNiZeD said:
Why dont you set up that build server,i think they're cheap atm,or someone could borrow you? It would take a lot less time and effort. that's why i think offical rom support is important,once it's merged to the build bot,its their responsibility.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's not as easy as you might think
I do have access to a buildserver, however I only have 100GB as it's a shared one, so this is genious for official builds, or quick tests/ports. But it isn't ideal for the long terms.
Also, having it official doesn't mean you're done you need to update it, and also fix it when it's broken. 'cause when it's broken, it can mess up the whole build process of the buildbot
But in general, you're right, having it official does help a lot
{fd}ware said:
Does anyone of you have a link to the latest CM10.2 (Android 4.3) for our device?
It seems like it's not anymore on get.cm and I wanted to start porting a TouchWiz (Note 3) ROM to our phone when I have free time
Click to expand...
Click to collapse
I can't find them either, but I'm on a tablet so I can't look properly. 
 @laufersteppenwolf, do you have any *spare* 4.3 build?
MidnightDevil said:
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
Click to expand...
Click to collapse
LOL, no, I do not, but gimme a few hours and I'll have one
Syncing right now
laufersteppenwolf said:
LOL, no, I do not, but gimme a few hours and I'll have one
Syncing right now
Click to expand...
Click to collapse
Thank you
{fd}ware said:
BTW, did anyone tried to port a ROM this way? http://forum.xda-developers.com/showthread.php?t=2245786
Click to expand...
Click to collapse
Nope, I actually never "winzipped" a ROM
Lot of things to comment on here. Very good initiative I have to admit. I'm sure I'll have more ideas as the discussion evolves.
Similar hardware: You can add HOX+ as laufer said. Very minor differences are there only.
What I would personally prefer is TouchWiz, at least Nature UX 2.0, but new S5 UI is also really awesome. I liked Sense till 4.5, but 5.0+ versions are now out of my 'inner circles'. Especially what I don't like is the UI.
Few suggestions:
FlymeOS (from Meizu MX) - I got 2.0 booting last summer, but had touchkey issues (they were freezing the device lol) and never released it. Nobody ever booted 2.0+ on other Android devices yet.
Porting LG roms might be the best start, I think porting full Optimus G system wouldn't be that hard. Just a pain in the *ss merging process.
What we mainly need is same screen size (unless you wanna resizing 100+ apps ). Similar SoC is a good extra, but that's very limited. Also, it's better to avoid Qualcomm SoCs to port from, it's extremely hard, there are a lot of code changes in low-level code which just make the device get into deep segfault cycles. :cyclops: Even Exynos is easier to port from, trust me. I got SGS3 leaked 4.2 booting on the O4X last autumn.
Big issue we have to note: In 4.2, Google radically changed graphics libraries code. We have old, 4.1.2 blobs and those need hacks in libgui.so and libsurfaceflinger.so to function properly (in 4.4+ libEGL.so, libGLES_v1_CM.so and libGLES_v2.so also need a change). Here comes the problem: Manufacturers do change these libraries, mainly adding Wi-Fi display and HDMI support code which other blobs rely on. Of course we can't just replace these libs, graphics wouldn't function that way. Either we have to guess those function signatures and reimplement some stub in the code, or use new blobs, i.e. what I did in Omni. But y'all now those are not perfect _yet_.
Regarding newer kernels: If, I emphasize, IF it's properly ported, it would cause a noticeable effect on overall performance, battery life, etc. What do I mean by proper porting: All machine-specific code must be updated to Nvidia/Google upstream, no excuses! I don't say anything for sure, I didn't check it much, but kholk didn't do this merge. His kernel still uses 3.1 files with slight modifications to be 3.4-compatible. What I mean would be a very long and painful process, but would surely benefit after all. 3.4 has no Android branch, mainline Nvidia Tegra kernel does only have Linux support, it might be even harder. 3.10 is maintained by Google for Android, issues I have found so far: No graphics driver support for T2 and T3, have to forward-port it and I didn't find core Android components like wakelocks, earlysuspend, etc. Weird.
A little related story: I initially started working on MultiROM so I can test and port different roms while I can keep a stable rom for myself and there'd be no need for reflash then. That's what I can suggest. Use MultiROM, it has so many capabilities! Maybe it's better with kernel sharing so you don't have to wait for hardboot on every reboot (which one needs a lot if porting). @MidnightDevil you could add this to the OP maybe.
MidnightDevil said:
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
Click to expand...
Click to collapse
Here you are! Compiled this because wanted to start porting from Note 2, but finally worked on Omni more and abandoned it.
{fd}ware said:
BTW, did anyone tried to port a ROM this way? http://forum.xda-developers.com/showthread.php?t=2245786
Click to expand...
Click to collapse
That's way too generic unfortunately.
Quick suggestion for you port: Use Note 2 base with Note 3 features. Note 2 has the same resolution and you won't need to resize.
Adam77Root said:
Lot of things to comment on here. Very good initiative I have to admit. I'm sure I'll have more ideas as the discussion evolves.
Similar hardware: You can add HOX+ as laufer said. Very minor differences are there only.
What I would personally prefer is TouchWiz, at least Nature UX 2.0, but new S5 UI is also really awesome. I liked Sense till 4.5, but 5.0+ versions are now out of my 'inner circles'. Especially what I don't like is the UI.
Few suggestions:
FlymeOS (from Meizu MX) - I got 2.0 booting last summer, but had touchkey issues (they were freezing the device lol) and never released it. Nobody ever booted 2.0+ on other Android devices yet.
Porting LG roms might be the best start, I think porting full Optimus G system wouldn't be that hard. Just a pain in the *ss merging process.
What we mainly need is same screen size (unless you wanna resizing 100+ apps ). Similar SoC is a good extra, but that's very limited. Also, it's better to avoid Qualcomm SoCs to port from, it's extremely hard, there are a lot of code changes in low-level code which just make the device get into deep segfault cycles. :cyclops: Even Exynos is easier to port from, trust me. I got SGS3 leaked 4.2 booting on the O4X last autumn.
Big issue we have to note: In 4.2, Google radically changed graphics libraries code. We have old, 4.1.2 blobs and those need hacks in libgui.so and libsurfaceflinger.so to function properly (in 4.4+ libEGL.so, libGLES_v1_CM.so and libGLES_v2.so also need a change). Here comes the problem: Manufacturers do change these libraries, mainly adding Wi-Fi display and HDMI support code which other blobs rely on. Of course we can't just replace these libs, graphics wouldn't function that way. Either we have to guess those function signatures and reimplement some stub in the code, or use new blobs, i.e. what I did in Omni. But y'all now those are not perfect _yet_.
Regarding newer kernels: If, I emphasize, IF it's properly ported, it would cause a noticeable effect on overall performance, battery life, etc. What do I mean by proper porting: All machine-specific code must be updated to Nvidia/Google upstream, no excuses! I don't say anything for sure, I didn't check it much, but kholk didn't do this merge. His kernel still uses 3.1 files with slight modifications to be 3.4-compatible. What I mean would be a very long and painful process, but would surely benefit after all. 3.4 has no Android branch, mainline Nvidia Tegra kernel does only have Linux support, it might be even harder. 3.10 is maintained by Google for Android, issues I have found so far: No graphics driver support for T2 and T3, have to forward-port it and I didn't find core Android components like wakelocks, earlysuspend, etc. Weird.
A little related story: I initially started working on MultiROM so I can test and port different roms while I can keep a stable rom for myself and there'd be no need for reflash then. That's what I can suggest. Use MultiROM, it has so many capabilities! Maybe it's better with kernel sharing so you don't have to wait for hardboot on every reboot (which one needs a lot if porting). @MidnightDevil you could add this to the OP maybe.
Here you are! Compiled this because wanted to start porting from Note 2, but finally worked on Omni more and abandoned it.
That's way too generic unfortunately.
Quick suggestion for you port: Use Note 2 base with Note 3 features. Note 2 has the same resolution and you won't need to resize.
Click to expand...
Click to collapse
Dang, you've beaten me but mine's as fresh as it could be
HERE you guys go, for all who need the newest CM10.2
laufersteppenwolf said:
Dang, you've beaten me but mine's as fresh as it could be
HERE you guys go, for all who need the newest CM10.2
Click to expand...
Click to collapse
Just don't delete the sources, you might need them in the close future.
I think we should create a schedule about what to do. As you all know, good buildings all have good grounding. So let's get started from the very beginning I say. First fix remaining bugs in MultiROM, then create a unified kernel so users don't have to choose. Very likely this is not possible as people think different so just make all kernels hardboot compatible. After these we have a solid base for starting all the work. Of course this cannot be done if not everybody is involved. Both devs and users should share a part in this magnificent journey.
(High expectations, I know. )
Sent from my OmniROM-powered LG Optimus 4X HD

Categories

Resources