Related
We have had alot of activity over the last few days, what with the first 2.0 releases from the main players and now even some 2.1 builds. Which is excellent.
Maybe I am not 100% up to speed on the whole thing, but if AOSP 2.0 is "released" by google, then surely things like sync issues, etc shouldn't be in the source code?? I mean, the code should be as "bug free" as possible, so anything obvious like that would strike me as odd.
The reason I raise this point, is because I dislike the Rosie/SenseUI on my Hero, I would rather have the good, old Android standard like I had on my G1 - just what I prefer. However there are only beta versions of the AOSP eclair for Hero.
Would it be possible to build an AOSP eclair firmware, using the Qualcomm? proprietory drivers from someones leaked 2.1 image (working on an assumption that 2.1 has the same kernel base?) to produce a fully working Eclair 2.0 for Hero?
If I am way off the mark with this, please say, I'm just trying to think it through with the help of the people in the know.
Ditto. I am all for AOSP 2.0
richbayliss said:
Maybe I am not 100% up to speed on the whole thing, but if AOSP 2.0 is "released" by google, then surely things like sync issues, etc shouldn't be in the source code?? I mean, the code should be as "bug free" as possible, so anything obvious like that would strike me as odd
Click to expand...
Click to collapse
I think part of the "issue" is that whilst Google have release some 2.0 code to AOSP, it is not currently complete (see here). In addition, many of the Google apps (e.g. Gmail) are closed source, so you have to rely on prebuilt components which may, or may not, be compatible.
The long and short of it is that Lox is already doing what you are asking. The prerelease of HTC's 2.1 has possibly served as a distraction to the AOSP 2.0 build, but I'm sure once Google properly drops AOSP 2.1 code that work will be of direct relevance to the AOSP project.
Regards,
Dave
yeah exactly. just sit tight and wait for Lox_dev to finish his 2.1 Then he might look after the AOSP 2.0. and as AOSP 2.0 is running pretty fine without much hassle its fine if Lox takes some time before working on AOSP 2.0 . cheers
I'm with this idea!
I mean, just compare the 2.1 and 2.0 aosp videos; android 2.0 has much cleaner, and better transitions imo.
Design choices in 2.1 by HTC are, imo, bad as usual; the transparent notification drawer for example; what is the purpose? It's only jerky. And so on..
I suggest suspending judgement on HTC's 2.1 until they've actually released final code! Remember this is a leaked internal build - what ends up in the final ROM may be quite different.
Regards,
Dave
I think I have a clearer picture now, thanks guys.
I just wish that we could be in a scenario where we could flash a standard AOSP build onto our Hero's, sans the whole SenseUI, and have a basic usable phone.
I really dont get the whole "gmail is closed source" crap with Google. I mean, I can have Gmail on WinMo, S60, etc - but only on Android IF I have a license?? WTF! Crazy! Luckily, now that Gmail does support Exchange Activesync I don't need the standalone app anyway.
So the word on the street is wait.... which I guess is what we will have to do
I am keen to be able to build from source so I can start on a project I have in mind. Think along the lines of SenseUI, but a bit different.....
richbayliss said:
We have had alot of activity over the last few days, what with the first 2.0 releases from the main players and now even some 2.1 builds. Which is excellent.
Maybe I am not 100% up to speed on the whole thing, but if AOSP 2.0 is "released" by google, then surely things like sync issues, etc shouldn't be in the source code?? I mean, the code should be as "bug free" as possible, so anything obvious like that would strike me as odd.
The reason I raise this point, is because I dislike the Rosie/SenseUI on my Hero, I would rather have the good, old Android standard like I had on my G1 - just what I prefer. However there are only beta versions of the AOSP eclair for Hero.
Would it be possible to build an AOSP eclair firmware, using the Qualcomm? proprietory drivers from someones leaked 2.1 image (working on an assumption that 2.1 has the same kernel base?) to produce a fully working Eclair 2.0 for Hero?
If I am way off the mark with this, please say, I'm just trying to think it through with the help of the people in the know.
Click to expand...
Click to collapse
Forgive me if I'm missing the point, but we already have a fully working AOSP Eclair image for the HTC Hero. I've been using it for over a week, on a daily basis and other than the looping sync issue (which we are working on) it works fantastic..
jnwhiteh said:
Forgive me if I'm missing the point, but we already have a fully working AOSP Eclair image for the HTC Hero. I've been using it for over a week, on a daily basis and other than the looping sync issue (which we are working on) it works fantastic..
Click to expand...
Click to collapse
I wasn't aware that all issues apart from the syncing were fixed. I thought we still had issues with camera stability etc?? Is this not the case??
There are some minor issues with stability, but it's absolutely useable on a daily basis. I guess it would be better for you to list what your problems are or concerns, rather than making (what appears to me) to be a grand claim for concentrated work on something.
There are a number of us who are solely focused on getting AOSP Eclair working 100%.. but we're very nearly there. Having people contribute constructive information about what doesn't work would be the best.
jnwhiteh said:
There are some minor issues with stability, but it's absolutely useable on a daily basis. I guess it would be better for you to list what your problems are or concerns, rather than making (what appears to me) to be a grand claim for concentrated work on something.
There are a number of us who are solely focused on getting AOSP Eclair working 100%.. but we're very nearly there. Having people contribute constructive information about what doesn't work would be the best.
Click to expand...
Click to collapse
Believe me, I'll come back to AOSP soon with great things
That's an awesome news ! Thank you Lox !
Lox_Dev said:
Believe me, I'll come back to AOSP soon with great things
Click to expand...
Click to collapse
Thanks Lox, appreciated.
Lox_Dev said:
Believe me, I'll come back to AOSP soon with great things
Click to expand...
Click to collapse
Great news man! Thanks a lot! Holding my breath...
jnwhiteh said:
There are some minor issues with stability, but it's absolutely useable on a daily basis. I guess it would be better for you to list what your problems are or concerns, rather than making (what appears to me) to be a grand claim for concentrated work on something.
There are a number of us who are solely focused on getting AOSP Eclair working 100%.. but we're very nearly there. Having people contribute constructive information about what doesn't work would be the best.
Click to expand...
Click to collapse
I agree. The only reason I am now using Lox_devs Hero 2.1 1.4 instead of the pure Eclair one is that Eclair does not sync my exchange calendar. I just cant see why the calendar has been left out.
FroydVillain 1.3/2.x roadmap
EDIT: Due to unforeseen issues rapidly accelerating the release of 1.3 (more framework changes), I'll edit this roadmap to reflect 1.4 as well as what we hope to accomplish depending on how many of the 1.3 promised features make it into the accelerated release. Thanks for your patience.
Now that FroydVillain 1.2.x is somewhat stable we can concentrate on the next releases.
First, any and all "WHENNNNNNNNNNN???????!!!!!111oneeleven" posts will be ignored. As usual, "when" = "when it's done".
Features/items in this roadmap are things you can definitely look forward to unless otherwise stated, ie, something happens that renders that feature impossible. Like an asteroid hitting my house, for example.
First, the preliminary work.
I promised the guys over at Cyanogenmod that my new build profile for the Hero (and other MSM7xxA based phones, so the Dream, Slide, G1, etc etc) will be tidied up and offered up in a pull request. I will be cleaning up my tree and submitting my changes before I begin work on the next release of FroydVillain. The main reason for this being, the closer the CM tree is to my tree, the less work involved in keeping the FroydVillain tree up to date with upstream fixes.
Right, so the changes.
Version 1.3.x:
Obviously it is customary to break some **** with each major revision just to give me an excuse to release another release after that broken release.
So for 1.3.0 I nominate, umm...nah I'll let you find out. A release post isn't complete without at least 20 posts asking if anyone is having xxxxx problem and a further 20 posts complaining about the said problem after I post that we're aware and we're very sorry and those responsible shall be flogged.
FroydVillain 1.3.x:
Further changes to the build base and source code to move Froyo-on-Hero further away from reliance upon Eclair libraries. We aim to be building a native libcamera.so in the same vein as the D/S guys are. This combined with already eliminating proprietary liblights makes it easier to...
Switch over to the Froyo prelink map. If you don't know what prelinking is, don't ask. Either don't worry about it or do some Googling. The upshot for you the end user should be better stability and maybe even some added performance improvements.
Along with the addition of the CPU profile to the CM base I'm hoping to get VFP support fixed in the kernel and in the dalvik source. VFP is your phone's ability to offload number crunching to a dedicated number crunch piece of hardware. The cpu the Hero has supports it, however support for VFP on ArmV6 architecture is a bit...well, pants. Accomplishing this should also give another measurable boost in dalvik performance since currently the only enhancement to dalvik, is the optimised binary, the source itself still trudges along with only armv5te support which again rather pants.
Giant /data partition. Thanks Maxisma and co. I'm not going to bring this in until we next need to do a wipe, ie, 1.3 since it resizes the mtd partitions. Coupled with old school apps2sd there should never be a single whine about space on /data ever again. Even dkelley could fit all of his dalvik cache data on it with his encyclopaedic collection of apps. Be aware this will be accompanied by an updated recovery.img so the different layout is supported. You have been warned.
Debugged Exchange support. I can't promise that this will appear in a 1.2.x update but I will get it in for 1.3. I don't use Exchange and so have to rely on others to help find the cause of the issue, debug it and test it. I can't believe after nearly 10 years dodging it, I'm back troubleshooting Exchange bollocks again.
Theme revival. Because Google were kind enough to provide no theming engine what so f**king ever (cheers lads) theming is a pain in the behind that involves hacking the framework. However because we now build from source rather than trying to crowbar bits in and out of a prebuilt HTC tree, it's significantly easier to produce themes from the newly built source tree. I'm working with Alex24 on a project to go with 1.3.x which will put Themes back into the OTA app and they'll be available at the same time as the new releases are. This also allows us to easily add more themes over time.
CMSettings/CMParts. After having a chat with the folks at Cyanogenmod they're more than happy for me to make the menu entry in settings feel more at home within FroydVillain instead of looking like a kicking and screaming rip off from the Cyanogenmod ROM itself. So those of you that have been hopping up and down for CMSettings functionality, it's coming.
Better GPS functionality/better radio functionality overall. For various reasons, changes made by Google, the fact we'll never have official "Froyo supporting" radios, bugs creep into the OS when it comes to using newer Google based apps that make use of the radio. We'll have some fixes for the slow GPS locking and the random reboot/crash when looking for a GPS signal. We're hoping we have mobile data+gps properly nailed down as well.
We're also going to look into different Gallery implementations. Gallery 3D is annoying as hell and the bugs with it are likely due to us relying on the Eclair GL libs. So no further ground is likely to be made until/if/when another MSM7xxA class phone gets Froyo which if any will likely be the Legend. That's a big if though. Imagine if you will, 50 metre tall letters I and F, draped in neon coating with a flashing, strobing sign above them announcing "THIS IS A BIG IF." But no whining if the best you get is the old 2D Gallery as I'm really struggling to find any decent Gallery implementation. Which is somewhat surprising. Perhaps we should offer a bounty for a new decent one.
Add further language support
That's all for 1.3.x for now I think. I'll update this as new things occur or as things appear to be impossible.
FroydVillain 2.x:
Kernel 2.6.34.
What? That's not enough? Wtf is wrong with you? Ok fine.
2.6.34 will provide official support for the newer Froyd features such as in built Tethering and no more annoying bull**** surrounding connecting a simple USB phone to a simple USB port on a simple Windows system. Apparently the Windows driver stack is easier to confuse than a 90 year old Alzheimers suffering dementia patient.
We'll also be looking to bring the Hero Froyo platform closer in line to the more complete Cyanogenmod D/S platform. There's really no reason why we shouldn't be able to especially once 2.6.34 is available since as far as the hardware is concerned the phones are practically identical.
More will be added to the 2.x branch as we discover it. Don't be surprised if in the course of working on 1.3.x some features get pushed back to the 2.x release due to practical limitations or it just making more sense.
Now is the time for feature requests from you the user. 1.2.x is now critical bugs only, I do not want to have to make you wipe/flash 1.2.x now until 1.3 hits so any fixes involving a framework rebuild won't appear until 2.x. 1.2.x is now considered feature complete in the scope of features we want to have supported. New features will appear in 1.3.x or 2.x depending on the work required to make them appear.
So the forum is now yours, dear users, to get those feature requests in. We'll endeavour to get as many implemented as we can. Any ridiculous or unobtainable goals will be identified as such as quickly as possible so people don't get their hopes up only for me to dash them like an abusive husband.
Thanks for all of the Froyo deliciousness you've provided us with! I myself will be waiting with baited breath for the next installments of Froyd.
p.s.
If you need more people with access to Exchange, or if you'd like an Exchange environment to play around with, let me know. I've got an Exchange 2010 machine sitting next to me.
Looking great! Hope you'll get that all working!
acolwill said:
Thanks for all of the Froyo deliciousness you've provided us with! I myself will be waiting with baited breath for the next installments of Froyd.
p.s.
If you need more people with access to Exchange, or if you'd like an Exchange environment to play around with, let me know. I've got an Exchange 2010 machine sitting next to me.
Click to expand...
Click to collapse
Ah, now that -would- be useful. [email protected] if you want to hit me up on GTalk.
maxisma said:
Looking great! Hope you'll get that all working!
Click to expand...
Click to collapse
Cheers bud! Check your PMs.
wow keep on the great work...
Flash? 10char
dpi295 said:
Flash? 10char
Click to expand...
Click to collapse
Impossible, it doesn't work on ARMv6 CPUs.
Ah, now that -would- be useful. [email protected] if you want to hit me up on GTalk.
Click to expand...
Click to collapse
Req sent. Gimme a nudge
dpi295 said:
Flash? 10char
Click to expand...
Click to collapse
Best we can do is see if we can hack over the Flash Lite stuff from Sense, but don't hold your breath.
In fact, you all should start a campaign and hammer the **** out of Adobe to provide an armv5te or armv6j version of the flash library. It's their fault, make them fix it.
Hacre said:
Best we can do is see if we can hack over the Flash Lite stuff from Sense, but don't hold your breath.
In fact, you all should start a campaign and hammer the **** out of Adobe to provide an armv5te or armv6j version of the flash library. It's their fault, make them fix it.
Click to expand...
Click to collapse
They won't do that, they aren't powerful enough..
I'd appreciate it if you would make an optional patch for people who want their phone unlocked by double clicking menu button.
Amazing work! Data Partition, Themes, VillainSettings... cant wait!
As for Feature Requests, +1 for a quick 2D Gallery
Nice post ninpo.
Thanks for your great ROM. I'd love to see better rtl language support in your ROM.
Really lame request, and probably easily fixed just by finding the pictures myself, but could you put all the nice wallpapers you had back into the releases?
It's obviously a very trivial request, but the wallpapers were always exceptional compared to my attempts of being sophisticated. I always ended up with either breasts or something Xbox related...
mobydeek said:
As for Feature Requests, +1 for a quick 2D Gallery
Click to expand...
Click to collapse
+1 for the standard 2D Gallery.
Tanks guys for your hard work.
Sent from my HTC Hero using Tapatalk
Woah, that's a lot of things to do, and some big ones too. Good luck on that, would be awesome to see these things done in the next months, though, take your time, no rush .
As for Feature-Requests: I only have one, and I don't have any idea if it's already done (I don't test many ROMs that often, I'll prefer to stay on my 2.1 Vanilla ROM ) or if it's even possible, so sorry for my Noobishness in advance. Now, I would love to be able to control the Music Player with the volume keys. Short presses change the volume, like before, and long presses skip the songs.
Screatch said:
I'd appreciate it if you would make an optional patch for people who want their phone unlocked by double clicking menu button.
Click to expand...
Click to collapse
Blue-K said:
Woah, that's a lot of things to do, and some big ones too. Good luck on that, would be awesome to see these things done in the next months, though, take your time, no rush .
As for Feature-Requests: I only have one, and I don't have any idea if it's already done (I don't test many ROMs that often, I'll prefer to stay on my 2.1 Vanilla ROM ) or if it's even possible, so sorry for my Noobishness in advance. Now, I would love to be able to control the Music Player with the volume keys. Short presses change the volume, like before, and long presses skip the songs.
Click to expand...
Click to collapse
We'll be putting a modified CMSettings back into FroydVillain in 1.3, so these features will be there automaticallymagically.
Yeah, it's a fair bit of work, but with HTC pretty much ditching the Hero we can take the project and make sure it's all done and done right.
There's collaboration with other developers on other projects for a lot of this, it's not just me or Team Villain making it all happen. I'll be pushing the fixed cpuprofile up to cyanogenmod and they can then work on it too, I'm working with Elemag on the 2.6.34 port, Maxisma brought the repartitioning stuff to everyone's attention for the Hero, etc. Proper open source development at its best.
It's well worth it too. Look how different the Hero runs with FroydVillain 1.2.1, I'm quite frankly disgusted that HTC never, ever, tapped all that potential.
I can't believe it, my hero will never die!
This is indeed great news and I can't wait!
I just wanna thank everyone involved, all the developers are doing a fantastic job bringing us things i never thought was possible on the hero, and I totally agree Hacre, it's a real shame that HTC ditched ther hero when there's still juice left in it!
Cheers!
e2zippo said:
I can't believe it, my hero will never die!
This is indeed great news and I can't wait!
I just wanna thank everyone involved, all the developers are doing a fantastic job bringing us things i never thought was possible on the hero, and I totally agree Hacre, it's a real shame that HTC ditched ther hero when there's still juice left in it!
Cheers!
Click to expand...
Click to collapse
Not to mention juice they never, ever bloody gave us. Grr.
There are some things I can't get my head around.
From the screenshots of all the cool user ROMs and themes available it's clear they've been designed by clever people who use their phones a lot. So why does it appear from these shots they use the Sense launcher, and their default home screen has a big Sense clock and hardly any apps?
Presumably, like me, these people are pulling their phones out their pocket and putting them back there many times a day. Presumably also, like me, these people use a number of apps and widgets in a day that hits two figures. With this in mind, I want to be able to get to those apps and widgets easily and quickly. I.e., with as few swipes/clicks/screen presses as possible. I'm sure these people do too, right?
So that rules out the Sense launcher doesn't it, with its 4x4 grid limitation and non-resizeable widgets. Not to mention its time-consuming spin-in carousel effect every time the phone's security screen is unlocked. I haven't found anything useful the Sense launcher does that another launcher can't, at least after downloading other apps.
Furthermore, who really keeps that big clock on their home screen, when 1. you probably wear a watch; and 2. you can see the time on the top right. It seems like a silly amount of screen 'estate' to use.
Or is it that these people in fact have a more practical default home screen and it's just tradition to post the screenshots they show?
Finally, why do so many of these otherwise brilliant ROMs not mod the battery icon to show how much battery is remaining, percentage-wise? Appreciate this can be modded using the kitchen website. But surely everyone wants this info from the off, so is it not included?
Well, I'd never call myself a hardcore user - although I believe that term should be defined too, because I'm not sure it's interpreted the same way by everyone. That aside though, here's what I think on tinkering with the launchers. You buy an Android phone - be it of any manufacturer. In general, and especially considering the top level models, it can be said that there isn't much diversity hardware-wise. What does make a difference is the UI, the services integrated and how the phone handles them. (And let's exclude synthetic benchmarks for now, I don't believe they represent real-life scenarios.) So, someone knowledgeable going for an HTC device (meaning it's not chosen because of price or because of how "pretty" it is), imo, means they're attracted to Sense: those little nuances that do make the difference. Ditch the launcher and you've pretty much ditched at least about half of what Sense - of what HTC is about. But then, why did you go for HTC in the first place? And the same can be said with Samsung and SE as well, those who quite heavily modify the Android UI. Sure, you can do it, you can dump the whole customized everything...but can doesn't mean that you should: if you're a "hardcore user", however we define the rest of it, you know you'll have an easier life with a phone that runs stock Android, there's no point in choosing something customized (read: more complicated), with risk of locked bootloaders and whatnots.
And you're right: you can get the puzzle pieces from the Market (or elsewhere) to create a Sense-like experience. That's because Sense offers so many good things in one package that ppl are aiming at re-creating it, but ask this: if you want to re-create it, why not spare yourself the hassle and use the real thing right out of the box?
As for the clock: I haven't even owned, much less worn a watch for at least about ten years, nor do I feel the need. Actually they seem pretty redundant now that mobiles have become as complex as they are and being carried everywhere. But as for the battery percentage - I couldn't agree more, I wish I knew why HTC itself doesn't make it available at least as an option.
In addition to the great points made by breathlesstao, I'll add the following:
Many devs concentrate on performance, stability and removing bloat when developing their ROMs, so if you want UI mods like battery percentage etc then the option is there for you to do it yourself. It would be nice if HTC could add percentage but they do have a battery widget that shows it.
As for on screen icons, I suppose many people like a sleek looking interace with not a lot of clutter. Plus, the more you have on the homescreens the more likely you are to experience lag when scrolling between the screens. Personally I have every app I use often on one of the 7 screens and if I need anything else it's only a few presses away in the all apps menu. I like it to be set up with each page having similar types of app, so on one I have music / media related stuff, another tools / settings type stuff... etc. See my helicopter view screenshot below for an example. My screen aren't crammed, but then they're not too sparse either.
I actually like the flipclock as it integrates local weather and just generally looks cool... I also haven't had a watch since the 1990s.
Choice and the ability to customise things are part of the many joys of Android, you set it up your way and use it your way.
The replies are right in. As for the launcher I have people coming to me all the time cause their phone is slow and lagging and whenbi unlock screen they have dozens of shortcuts all over the screen. Of course its gonna be slow when it need to reload a the launcher and all those Widgets. I swear some look so much like an icrap with all the shorcuts when I see it I have to double check. Lmao
As for the battery icon, you have to edit the coding for the file to add the extra 150 images that make up the % battery and charging icons and the bigger the file......
Now the clock well to be honest I remove the clock from the top bar any chance I get as I see it as pointless. We have Widgets for that.
As for sense it has its pluses like everything is prebuilt in. Social networking (not sure as I don't use FB at all) built into contacts and all the other handy apps that it comes with. I mostly run a senseless Tom my self but that is only due to it be long a resource hog. But the contacts and dialer work so well together that I have not found a better dialer/contact combo. The sense 3 lockscreen is just too good. I have widget locker but prefer the sense lock screen
Some very good replies, and here is my take, i've been modding my phone(s) now for a few years now (Since the Windows Mobile 5 Genre) and I would say function is not the only thing i look for. I want "coolness", "graphics"... I love the way the flip happens when you unlock a Sense ROM ..I strive to make it smoother !
Having said that I do resort to simplicity at times however, and you can too. have a look at Cyanogenmod and get Launcher Pro.. Ain't nothing simpler than that with the most "Function".
The ROM above will satisfy anyone who loves Function over Heavyness and also it has the option of showing percentage battery amongst plethora of other customizations neatly laid out in the settings menu.
But sometimes that just isn't enough for me..I want a ROM with More......Sense framework is probably the best Integration of everything I've ever seen. Yes its huge ! But then...this phone ain't that weak either...It is a beast
That is why you have an "option" my friend...an option to choose non-sense ROM or a Sense ROM. You could go for a Sense ROM (if you like all the integration of sense) and get yourself a different launcher from the market if you choose..customize it with the battery percentage mod.... yourself... The Dev's like to leave the option customize some aspects of their ROM's to the users... mostly because its personal preference.
The Sense Rom cooks, mostly, give u the most basic thing... A highly optimized ROM with a stock-like UI. You can choose to customize it the way you like ! After all thats what XDA is all about ..do it youself modding..
Hi all,
Your responses are appreciated and it's nice to have a polite conversation about this!
You're right breathlesstao, what the hell's a hardcore user. I just meant anyone who'd flash a ROM, root their phone, perhaps mod some element themself.
So I guess many of you - suprisingly for me - are happy to swipe between screens to get to their apps or widgets. You like what less clutter for doing this. Can see your point of view! I don't experience any lag though, zelendel, for packing my homescreens.
I suppose it was assumed that if you're more knowledgeable you'd be aware of apps and widgets with more options and functionality than the Sense launcher and its own widgets, and choose to use the former instead.
To be clear, I do like using other HTC features such as their contacts and dialler. It's just the homescreen layout I'm ranting about.
In particular for me, a good GUI, as well as looking pleasant, is as simple and quick to to use as possible. So when, for example, I'm going for a lunchbreak at work it's satisfying to be able to put my music or podcast-player on in a second without having to hunt it down.
i keep meaning to try a non sense rom but i like virtuous unity 2.39 sense 3.0 rom so much i´m loathe to part with it.
i know it only takes twenty minutes to go back to it but i just find it does everything in such a pleasant manner.. its smooth fast responsive and most of all it looks the buisness. plus as others have said you dont have to use all that sense stuff if you dont want to.
for music i do tend to use the stock player but i have been playing with other ones of late same with video but things like the clock and weather widgets for me are much more polished on the sense versions than anything comparible available from the market. plus i´ve not had any problem running low on ram or anything, the dhd is more than capable of handling sense 3.0 and whatever else one cares to throw at it without any hiccups
Circle launcher 1x1 widgets are the best
Sent from my Inspire 4G using xda premium
killersloth, thanks for the heads up - it looks very useful.
ponk2k, you know I also use VU (2.39) but with Launcher Pro - have uninstalled the Sense widgets that aren't connected to anything else. You probably think what's the point! To answer my own question, I wanted a custom ROM for things like battery life optimisation, and the VU team's branding has seemed more user-friendly to me than the non-Sense ROMs. Though maybe I'll try one soon. While I've got you though, can I ask if you have a problem with the brightness dimmng slowly on command in most scenarios with that ROM version? More info in my question here:
http://forum.xda-developers.com/showthread.php?t=1292894
Capys runny 1.5 is perfection
Sent from my Inspire 4G using xda premium
killersloth said:
Capys runny 1.5 is perfection
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
100% bug free? I was thinking of trying it.
CitizenLee said:
100% bug free? I was thinking of trying it.
Click to expand...
Click to collapse
Just a fair warning man. No rom will be 100% bug free. That is what the stock roms are for. The roms here are for learning and trying new things. So there will always be bugs that need to be fixed. Plus some things that one person may see something a a bug while another sees it as a feature.
zelendel said:
Just a fair warning man. No rom will be 100% bug free. That is what the stock roms are for. The roms here are for learning and trying new things. So there will always be bugs that need to be fixed. Plus some things that one person may see something a a bug while another sees it as a feature.
Click to expand...
Click to collapse
Thanks lol.
&by 'perfection' I definitely don't mean bugfree but it is everything I expect in a good rom. From the improvements to audio, the good battery life, and now decent skins too...
If it was bugfree what would be the fun in developing with it ?
Sent from my Inspire 4G using xda premium
zelendel said:
Just a fair warning man. No rom will be 100% bug free. That is what the stock roms are for. The roms here are for learning and trying new things. So there will always be bugs that need to be fixed. Plus some things that one person may see something a a bug while another sees it as a feature.
Click to expand...
Click to collapse
I meant with the basic day to day phone functions and stuff like WiFi, video playback etc. To me that's an expected level of functionality for any non beta ROM. I've flashed and tested many over the last 2.5 years of owning Android handsets so my standards are quite high
CitizenLee said:
I meant with the basic day to day phone functions and stuff like WiFi, video playback etc. To me that's an expected level of functionality for any non beta ROM. I've flashed and tested many over the last 2.5 years of owning Android handsets so my standards are quite high
Click to expand...
Click to collapse
It is fully functional. I believe there is the bug in camcorder still where you have to watch play.the video in the same orientation you recorded it.
Sent from my Inspire 4G using xda premium
I haven't had any problems with vu dimming slowly no. I do find that the dimming settings on the ROM are a bit brighter than on the stock ROM though but with no noticeable battery drain incurred.
Thanks will have to investigate further.
zelendel said:
Just a fair warning man. No rom will be 100% bug free. That is what the stock roms are for.
Click to expand...
Click to collapse
...aaaand potentially not even those. I mean, they're made by humans as well, and humans are bound to make mistakes, aye? It happens.
The most productive thread i ever encountered !!! Thanks to OP
hello developers,
i had an idea and a request
why not you guys work on other custom roms to make them compatible for WFS????
its a good idea coz there are many cool Roms out there...
like Xperia,walkman series rom,acer got a cool rom too....even Dell got a cool looking GUI
people have different tastes....CM7.2 is a simply great rom....but people may not like the GUI
sense GUI is faar better than CM7.2
why not developers work on custom roms from other android phones?? ))
that will be great ^___^
plz dont consider my post as spam..i just suggested this thing....starting a poll ...if people will like my idea they'll support it..
i dont know if i'm the only one to love the custom rom's GUi o.o
+
There is another request...
in market(public market not android market)
windows mobile 7 is quite popular these days...
why not developers work on windows mobile 7 OS compatible for WFS
since unlocking boot loader = we can install all the OS
being an WFS developer and WFs user we should have many options
like i said everyone have different tastes...who knows who likes what?
users should have many options in there hand like what to install.....
you cant because of different hardware configurations and kernel. its like porting sense to samsung which cant be done. next time post in general section.
If you're just looking for GUI. download launchers like launcher 7, go launcher ex.. something like that.
blackpearlisuchiha said:
hello developers,
i had an idea and a request
why not you guys work on other custom roms to make them compatible for WFS????
its a good idea coz there are many cool Roms out there...
like Xperia,walkman series rom,acer got a cool rom too....even Dell got a cool looking GUI
people have different tastes....CM7.2 is a simply great rom....but people may not like the GUI
sense GUI is faar better than CM7.2
why not developers work on custom roms from other android phones?? ))
that will be great ^___^
plz dont consider my post as spam..i just suggested this thing....starting a poll ...if people will like my idea they'll support it..
i dont know if i'm the only one to love the custom rom's GUi o.o
+
There is another request...
in market(public market not android market)
windows mobile 7 is quite popular these days...
why not developers work on windows mobile 7 OS compatible for WFS
since unlocking boot loader = we can install all the OS
being an WFS developer and WFs user we should have many options
like i said everyone have different tastes...who knows who likes what?
users should have many options in there hand like what to install.....
Click to expand...
Click to collapse
if possible u go ahead and start work don't give these types of ideas
Mindhexer is right. Good dream though. Get you a HD2 if you want a windows &/or android phone; although, porting to android may knock out your volume toggle :/ honestly very very hard to port to a new os, but you'd have a slightly easier time of it going from open source to open source [ie hp touchpad; and that's not easy by any means]. Basically you will have to find in many cases drivers that work or have a decompiler [thousands of $] and a lot of programming knowledge [and free time]. Simply not feasible for our device; even though, I love to say anything is possible; I'd bite my tongue, hope you were Richie Rich, and point you toward some brilliant dev teams; Again though, you'd probably have another device that started windows [definately closed sources] and got ported over. I have yet to see one go the other way and it would probably open the door to legal issues to attempt :S So, in short, nope.
Sent from my HTC Marvelc using Tapatalk
insink71 said:
Mindhexer is right. Good dream though. Get you a HD2 if you want a windows &/or android phone; although, porting to android may knock out your volume toggle :/ honestly very very hard to port to a new os, but you'd have a slightly easier time of it going from open source to open source [ie hp touchpad; and that's not easy by any means]. Basically you will have to find in many cases drivers that work or have a decompiler [thousands of $] and a lot of programming knowledge [and free time]. Simply not feasible for our device; even though, I love to say anything is possible; I'd bite my tongue, hope you were Richie Rich, and point you toward some brilliant dev teams; Again though, you'd probably have another device that started windows [definately closed sources] and got ported over. I have yet to see one go the other way and it would probably open the door to legal issues to attempt :S So, in short, nope.
Sent from my HTC Marvelc using Tapatalk
Click to expand...
Click to collapse
hmmmmmm...i just thought it would be a good ides coz i saw a video on youtube.....his Xperia X8 was running Htc sense......
o.o
Xperia is overrated man. [IMHO]
Use your lovely phone while you can, like the other hundreds of us.
Its not possible to do any of those ports. End of story
I do wanted WP7 on my WFS but our phone doesnt clear few minimum specs..........we could use the WP7 port of the HD2 but because of the difference in the processor(and the shipped OS)....only an EXTREMELY TALENTED dev can accomplish this feat
BTW,we can try ubuntu can we???
djpc said:
Its not possible to do any of those ports. End of story
Click to expand...
Click to collapse
yes correct, end of story.
Possibility to use launchers themes looks like WP or Xperia.
If its just the looks, just use some launcher, there are many themes/skins... or make them yourself, its far easier than doing what u suggested, and it would be too much job for something that is not that big from my point of view.
m1ndh4x8r said:
you cant because of different hardware configurations and kernel. its like porting sense to samsung which cant be done. next time post in general section.
Click to expand...
Click to collapse
Pretty sure they ported Android 2.2 to the Samsung Omnia II (Windows 7 mobile)...
Maybe i'm going to make a CyanUX for the WFS ;-) (CyanogenMOD / Sony mix)
I will maybe make MIUI for WFS (based on CM7, fully themed, debloated and lots of MIUI apps).
Anything is possible, but porting one rom to a different phone is a never ending battle. Beside the the only real benefit would be a performance port, gui can be accomplish as mentioned in above post. If you really want to see this happen pick your favorite dev and put him or her on payroll, truthfully they should be getting paid for the work their doing now.
djpbx said:
Maybe i'm going to make a CyanUX for the WFS ;-) (CyanogenMOD / Sony mix)
Click to expand...
Click to collapse
please do...and must make it look cool .....atleast the GUI
and functionally better,...dint liked the look and way of working of CM as compared to sense...o_o
All the things you need
blackpearlisuchiha said:
please do...and must make it look cool .....atleast the GUI
and functionally better,...dint liked the look and way of working of CM as compared to sense...o_o
Click to expand...
Click to collapse
For Xperia Sony style, you dont need a whole new rom.
Two things, and cm7 will look totally different:
Xperia Launcher
Xperia Theme, install and choose it from the theme chooser app
Hope this helps, click thanks!
Henry_01 said:
I will maybe make MIUI for WFS (based on CM7, fully themed, debloated and lots of MIUI apps).
Click to expand...
Click to collapse
MIUI will take a lot of GUI resize work, I think. But can be done.
Best to wait for latest MIUI release with ICS after CM9 is ported by the WFSDEV guys.
No resizing needed for miui, I use cm7 and theme it and add miui apps which are ported and confirmed working.
For CM9, I'm part of the devteam, and it will take some time for a working cm9.
The "real" MIUI will never come to WFS, due to hardware (screen and cpu).
I have to say it isn't that great in all the aspects either.
There aren't many languages supported, you dont have the cyanogenmod settings and its sometimes slow and battery hungry.
The best I think is to combine the power of cm7 with the beauty of MIUI.
Henry_01 said:
No resizing needed for miui, I use cm7 and theme it and add miui apps which are ported and confirmed working.
For CM9, I'm part of the devteam, and it will take some time for a working cm9.
The "real" MIUI will never come to WFS, due to hardware (screen and cpu).
I have to say it isn't that great in all the aspects either.
There aren't many languages supported, you dont have the cyanogenmod settings and its sometimes slow and battery hungry.
The best I think is to combine the power of cm7 with the beauty of MIUI.
Click to expand...
Click to collapse
Yeah, guess you are right.
BUT, I CAN'T GET THE DAMN STATUSBAR TO BE TRANSPARENT. I've tried everything.
I just went from BAMF to Paranoid Android 4.2 and for the life of me I can't figure out why so many people are talking up this ROM, could someone please explain it to me because I need to be missing something.
The only thing that looked interesting was the UI features which do not work correctly. The Opaque Statusbar and Taskbar do not work. Randomly they will go back to solid black then never goes back to Opaque. The Tablet UI seems awesome but the Taskbar buttons are way to small. So I figured I would change the DPI but it makes the Statusbar clock huge and the notifications area pop-up moves half-way off the screen rendering it unusable.
So after those features are taking away there really is no custom / developer settings on the ROM so it's pretty much pointless.
A lot of people like a tablet UI but don't like the smaller DPI or visa/versa et cetera.
Jubakuba said:
A lot of people like a tablet UI but don't like the smaller DPI or visa/versa et cetera.
Click to expand...
Click to collapse
The Tablet UI is awesome but very poorly implemented it seems.
Shuino said:
So after those features are taking away there really is no custom / developer settings on the ROM so it's pretty much pointless.
Click to expand...
Click to collapse
I came from AOKP milestone 1 to PA 2.99.5 and while I like the 4.2 I'm thinking it might be time to go back to AOKP. I thought the Phablet UI was interesting but when I tried it... it didn't work correctly. I do like the per-app customization but I'd rather customize other areas of the phone with my time. Add I miss my integrated weather on the lockscreen.
illegalsmile said:
I came from AOKP milestone 1 to PA 2.99.5 and while I like the 4.2 I'm thinking it might be time to go back to AOKP. I thought the Phablet UI was interesting but when I tried it... it didn't work correctly. I do like the per-app customization but I'd rather customize other areas of the phone with my time. Add I miss my integrated weather on the lockscreen.
Click to expand...
Click to collapse
You are pretty much in the same boat am I. I was just hoping something happened during my install of Paranoid and that's why it wasn't working or features were missing or something. I'm glad I'm not the only one who thinks this ROM is defiantly lacking.
I am staying hopeful though. Once they get this ROM out of beta maybe Tablet UI will be working, and they will include some basic customization.
I do not see any problems with PA 2.99.5 whatsoever.. It works perfectly fine..smooth, good battery life, no lags, everything works as it should.. Once again, it is a matter of preference.. You putting up this thread was a matter of preference.. But once again, it is advisable that you do not complain by making a new thread.. Just post in the PA thread.. Molesarecoming is always open to constructive criticism..Once again, the word is "constructive criticism" the diversity of ROMs in the Galaxy Nexus community is what makes many stick with the nexus. so before bashing other ROMs, please just remember you not liking it, doesnt mean it's the same for others. If you hate it so much twitter it or fb it or something. >.<
Leemur89 said:
I do not see any problems with PA 2.99.5 whatsoever.. It works perfectly fine..smooth, good battery life, no lags, everything works as it should.. Once again, it is a matter of preference.. You putting up this thread was a matter of preference.. But once again, it is advisable that you do not complain by making a new thread.. Just post in the PA thread.. Molesarecoming is always open to constructive criticism..Once again, the word is "constructive criticism" the diversity of ROMs in the Galaxy Nexus community is what makes many stick with the nexus. so before bashing other ROMs, please just remember you not liking it, doesnt mean it's the same for others. If you hate it so much twitter it or fb it or something. >.<
Click to expand...
Click to collapse
I'm not bashing anyone work at all, honestly I just wanted to know if I was missing something from the ROM since so many seem to use it. I have used it for 2 days now and none of the UI tweaks are functional, or do not work properly or are just way to small with no functional way to increase size. But the ROM is smooth and quick with insane boot speed.
Here is info on PA 2.99+ in a nutshell. First and foremost, you all downtalking tabletui need to realize that it does not actually exist in android 4.2, the paranoidandroid team found it deactivated by google in the code for 4.2 and they spent their time making it available again, it is in no way a finished product, if you want to see it work good then download a version of PA with an android 4.1x base ( i.e. PA 2.54 or before). Now onto people that cannot see the big deal, well anyone that tried the pre 4.2 PA knows that there is more customization available in PA than any other rom put together. Now PA 2.99+ are all AOSP based instead of CM based so they basically are building this rom from scratch to improve speed, performance and battery life for everyone, this means that a lot is not even integrated back into the rom yet. Simply trying out the newest PA will not give you a feel for why it is hands down the best rom out there. As for transparency, that only works on the homescreen and in order to properly utilize it you must A. be using a compatible launcher which has the homescreen backgrounds drawn correctly ( i.e. Apex, Stock or Holo etc, NOVA does not work) B. Choose a correct transparent hexcode or slide the transparency bar to where you would like it for that said Launcher in the "apps" section of paranoid preferences. I am on 2.99 Beta 5 and have full transparency with no issues that you speak of (Photo included as proof), in fact, Beta 5 has added almost everything I want back into the rom and fully functional, I can hardly wait for v3.0, seriously, I cannot see ever using another rom after using paranoidandroid, it just has the edge on everything else out there. AOKP and CM have nothing on it especially when it's at 100% again, which will be in the next couple weeks at the rate it's awesome devs work at!
tabUI is not existant in 4.2, what you see right now is raw honeycomb. if you want to see how good it was install 2.54, thats still based on 4.1. but right now i got to make my hands dirty with this. i know that on xda most people do not understand the difference between developing and kanging, and they wonder "why's this rom slower than others" but someones gotta do the dirty work and im okay if crackflashers avoid ours. they avoid cm for the same reason.
as for hybrid engine, i dont think you have understood it yet. it works flawless and it gives you more customization than all roms on xda combined, IF you can handle it. yes, you are able to make a button pink in this and that rom, but hybrid can transform thousands of apps and components to the better, with practical implications that are unheard of. the apps that are running on your huge 720p screen were not optimized for it, they're in the same layout that applies to pocketwatches or stone age miniature phones like the htc wildfire.
as for opacity, no app, obviously, draws underneath the bars - why would it. the launcher can do it, but again - not all do. nova has even a bug that offsets the wallpapers which leaves a black gap. our launcher works, apex works, holo works and perhaps a bunch of others. no rom does it differently, simply because its impossible.
the real difference is that we are producing features that push androids boundaries, we are sick of a homogen rom culture that hasnt really moved one inch for a couple of years now. all these roms are the same, do you realize that? kanging has produced one grey mass and nothing stands out. when we are done with our beta we will of course bring in all the essential features aswell, but new features have greater priority. and these blow everthing related to it clean out of the water.
compare build.prop hacks with hybrid engine, its like night and day. this is quite possibly the biggest rom scene improvement android has ever had.
compare rom scene color tweaks with per-app-color, its like night and day. normal roms are static, they give you one color and thats that. our colors shift from app to app.
compare extended desktop (which also came from us) with per-app-fullscreen
compare our recents with clearall implementations,
we had the most versatile toggles on android in 4.1 (right now we're implementing a new panel which will come in beta6)
etc.
but you got to understand that this stuff takes alot of time. i know i could just rename an open source rom, call myself "founder," post in 30 device forums and make craploads of money here on xda, but i chose not to and im happy i found a few guys that think in the same way. im content with the few people that use PA and the support i get from those, i dont see myself competing with any other rom for that matter. i dont feel like i have to stop all my work now just because this and that rom has a minor option that we dont have at the moment.
molesarecoming said:
tabUI is not existant in 4.2, what you see right now is raw honeycomb. if you want to see how good it was install 2.54, thats still based on 4.1. but right now i got to make my hands dirty with this. i know that on xda most people do not understand the difference between developing and kanging, and they wonder "why's this rom slower than others" but someones gotta do the dirty work and im okay if crackflashers avoid ours. they avoid cm for the same reason.
as for hybrid engine, i dont think you have understood it yet. it works flawless and it gives you more customization than all roms on xda combined, IF you can handle it. yes, you are able to make a button pink in this and that rom, but hybrid can transform thousands of apps and components to the better, with practical implications that are unheard of. the apps that are running on your huge 720p screen were not optimized for it, they're in the same layout that applies to pocketwatches or stone age miniature phones like the htc wildfire.
as for opacity, no app, obviously, draws underneath the bars - why would it. the launcher can do it, but again - not all do. nova has even a bug that offsets the wallpapers which leaves a black gap. our launcher works, apex works, holo works and perhaps a bunch of others. no rom does it differently, simply because its impossible.
the real difference is that we are producing features that push androids boundaries, we are sick of a homogen rom culture that hasnt really moved one inch for a couple of years now. all these roms are the same, do you realize that? kanging has produced one grey mass and nothing stands out. when we are done with our beta we will of course bring in all the essential features aswell, but new features have greater priority. and these blow everthing related to it clean out of the water.
compare build.prop hacks with hybrid engine, its like night and day. this is quite possibly the biggest rom scene improvement android has ever had.
compare rom scene color tweaks with per-app-color, its like night and day. normal roms are static, they give you one color and thats that. our colors shift from app to app.
compare extended desktop (which also came from us) with per-app-fullscreen
compare our recents with clearall implementations,
we had the most versatile toggles on android in 4.1 (right now we're implementing a new panel which will come in beta6)
etc.
but you got to understand that this stuff takes alot of time. i know i could just rename an open source rom, call myself "founder," post in 30 device forums and make craploads of money here on xda, but i chose not to and im happy i found a few guys that think in the same way. im content with the few people that use PA and the support i get from those, i dont see myself competing with any other rom for that matter. i dont feel like i have to stop all my work now just because this and that rom has a minor option that we dont have at the moment.
Click to expand...
Click to collapse
Wonderfully said.
Sent from my Galaxy Nexus
PA 2.54 on epic 4g touch
I just flashed to this rom yesterday and really like it so far. I am interested in flashing to the newest 2.99 version. Where I can get the correct download for my phone, and do I need to update my recovery and if so, where do I get the link for that?
Thanks
btvolta said:
I just flashed to this rom yesterday and really like it so far. I am interested in flashing to the newest 2.99 version. Where I can get the correct download for my phone, and do I need to update my recovery and if so, where do I get the link for that?
Thanks
Click to expand...
Click to collapse
I think the new 4.2 based PA roms might only be available for the Nexus series phones and tablets currently since the developers have started over building it from the ground up using AOSP source instead of CyanogenMod. I am not certain if the code is out there for other devs to build on their particular devices yet though.