I for one like MotoBlur, it looks and feels great and is appealing and easy to use. I love the enhancements included in BlurHome2, and I'd love to see it on the Droid X.
Now, my Android "developing" hasn't gone farther than theming, so I don't even know where to start if I wanted to port this over.
My question is, is this even possible? If so, how would I go about doing so?
As far as I've heard (I'm no developer) this isn't feasible because of the elements of the blur framework that need to be in place...that also can't be ported without causing the phone not to boot.
This MAY have potential in 2nd-init, however?
I've no idea.
Jubakuba said:
As far as I've heard (I'm no developer) this isn't feasible because of the elements of the blur framework that need to be in place...that also can't be ported without causing the phone not to boot.
This MAY have potential in 2nd-init, however?
I've no idea.
Click to expand...
Click to collapse
Well I've heard the same thing. I figured it'd be easier to do this on a Droid X (rather that a non-moto phone) due to Blur already being present. BlurHome2 depends on updated frameworks found in newer Droids, so when/if I get this started, I'll have to start porting the newer frameworks to the DX (which may not even be possible).
Only one way to try
It is possible (although 2nd init would have to be used), but would be very difficult as the code for Blur isn't open source.
Sent from my DROIDX using XDA App
shobon said:
I for one like MotoBlur, it looks and feels great and is appealing and easy to use. I love the enhancements included in BlurHome2, and I'd love to see it on the Droid X.
Now, my Android "developing" hasn't gone farther than theming, so I don't even know where to start if I wanted to port this over.
My question is, is this even possible? If so, how would I go about doing so?
Click to expand...
Click to collapse
You have to go to the droid x 605 update deodexed and apply the droid 3 theme then you put the lib files for BlurHome2.apk to /system/lib after that you change the permissions of them, then you put the BlurHome2.apk to /system/app/BlurHome2.apk and change the permissions to rw-r-r- and if you want you can put the new blurcamera into the system
Related
I just watched a video on you tube of the Motorola Droid X. each widget you can long press and then resize the widget too any size on the screen and it automatically adjust. any chance of anyone working on this for our EVO's? I would be the first to donate.Here is the link. Starts at 2:27 into it.
http://www.youtube.com/watch?v=FMG0Wjnuq3I
Proprietary code
I'm no expert, but if Motorola made their widgets the same way HTC made their's, then the widgets are tied to the launcher and their won't really be any way to extract them. Obviously someone could program something similar, the same way many HTC widgets have been replicated, but a true port of the software is probably impossible. Keep in mind these guys encrypted the bootloader on the device, so I don't think they are too keen on our Android hacking community to begin with, so extracting those widgets is probably impossible without Moto/Ninja-blur.
Thats definitely a cool feature for ADW Launcher to aim for.
i didnt exactly think they could steal that exact one but someone could make a similar option. Actually i was looking at some of cyanogens work and in one of his roms, he does have a resizer built in, not exactly as smooth as the droidx but would still be awesome to see on the EVO. And word is that he is building a rom for the evo now. He does some excellent work and i cant wait to see what he dreams up for the Evo.
Now that we have our recovery files and root would anyone have any mods to suggest? For one thing I would love to go to Android stock 2.2 and get rid of all the Motorola stuff. I would also love to snatch up the Samsung dialer app. Besides new mods does anyone know how to do this?
If you tried a new mod or have been able to get rid of blur please enlighten us.
If it's possible I'd like to at least go to the stock Android 2.2 theme because the Blur theme makes some apps display incorrectly that are expecting a stock theme:
Cyanogenmod or bust.
i too would love to get rid of MotoBlur and run stock 2.2 or a fast mod
Yeah, I'd just like to get a vanilla version built from source. Although I wouldnt mind being able to have a few of the moto tools already installed on the device.
I know we are somewhat limited by the bootloader, but I too would like to get back to stock android, I just don't care for the moto stuff at all.
I'd love to get rid of the moto crap... I'm new to the android scene and I feel like I bought a name brand PC loaded with ****. Can we revert to a stock android OS?
I for one would love to see MIUI portedto the Droid 2. Where's the Team-D2 MIUI???
Bump +1 on CyanogenMod too. I miss CM from my old D2 :'(
Hey I was wondering if there was any way that someone could make a sense rom for the droid 2 and if it would even run on it. Also why wouldn't it work it is just additions to the system/app and system/framework.
Please explain what a locked bootloader restricts. I know it means that you can't use un-official kernels but does that mean you can't change it to sense?\
I would love to have the new sense from the desire HD for the droid 2.
****BUMP****
from what i understand the big thing holding back alot of the dev work for stuff like that on the droid2 is the motorola locked bootloader.... so far i've seen themes and the like with alot of the motoblur taken out/turned off but nothing beyond that (not even an aosp) but i know that its being worked on by some good people and I am holding my breath for the goods to start flowing for both the 2 and the X.... in fact i would really like to have it by the big tx bbq.... kinda soon but i can dream
ljbaumer said:
Hey I was wondering if there was any way that someone could make a sense rom for the droid 2 and if it would even run on it. Also why wouldn't it work it is just additions to the system/app and system/framework.
Please explain what a locked bootloader restricts. I know it means that you can't use un-official kernels but does that mean you can't change it to sense?\
Click to expand...
Click to collapse
i adapted somehow htc sense to our Milestone (Droid 1 EU edition) , it works, but lacks speed due to the limited 256MB RAM available, secondly no-one has written a driver that emulated the bcm4329 hardware, so making bluetooth working ok is another major "not working".. even on older htc phones they had problems.
anyways i can say its possible is i did the reverse and put MotoBlur on Milestone, it works but somehow also lacks 512MB RAM here too.
to end this quick note,
HTC sense is not just an addition to the framework, its a different releas of the framework, every vendor does this, so like EU motorola did many updates on the milestone, but only first found now in droidx,droid2...
and porting it is not so simple, but i would think its possible, but i guess its too early for droid2 to have anything running as no real recovery exists, which loads before any os.
the one you got has a live /system when you open recovery, which means you can easily mess up your phone when you start modding to use sense, and pretty much make it unbootable, so a new sbf needs installed, which again means alot of testing before you actually get it working, and then backup? another problem to work with when you make small changes..
its not easy task without a real unlocked boot or a good recovery solution..
ok so technically what would I have to do to put sense on the droid 2?
ljbaumer said:
ok so technically what would I have to do to put sense on the droid 2?
Click to expand...
Click to collapse
It will never work 100% of even close enough to have the phone fully functional. People have been trying since the Original Droid. It's also tied into the RIL of phone.
Out of the blue question
What about just theming the home screen menubars to get the sense menubars only? Is that possible?
that should be possible, as a few themes available right now have already altered those files with success. Now you just have to grab a Sense based ROM form a Droid 1 and start copying and modding image files mostly i think. to make a deodexed hybrid of Sense and MotoBlur.
Is is possible to just to have the speed-dialer/contact app working the D2(that is the only real thing I will miss if I go with the D2)?
I'd move to the D2 right away if you can get the HTC keyboard mixed with the multitouch keyboard of the D2, and then add contact app(and all that comes with it), and music app. That all I really like out of my Eris.
If the D1 was able to get a sense port(from what i have seen) how come we cant get it on the D2?
Mackattack said:
If the D1 was able to get a sense port(from what i have seen) how come we cant get it on the D2?
Click to expand...
Click to collapse
the original Droid ran stock android, but the droid 2 has a custom framework (MotoBlur) and a locked bootloader.
Makes logical sens thanks
Sorry if this has been asked before, but I did search and found nothing:
I had an Inc. before, and traded to the X for the screen, and physical buttons which I like.
However, as we all know the X blows in comparison to the Inc. in terms of development; so I have to ask since I'm trying to decide what to do:
1) Is the kernel responsible for preventing us from things like notification toggles, notification recent apps, etc... ?
2) When Gingerbread/Ice Cream comes out, are we pretty much at moto's will w/o being able to modify the kernel?
3) What are the chances of seeing CM6 on the X specifically? I'd love to see it, but am no longer hopeful I guess
4) I saw that ccvp (or something like that) was able to hijack moto's init. Is this pretty much dead, or is there still work for it?
I don't really care that birdman stopped dev work on the X (he was responsible for a lot, i know) but will tear if more devs switch to other phones.
Any Ideas?
Again, sorry if all this was already covered.
P.S. I have programming, and Java experience so I WAS thinking to start trying to do some sort of cracking on this myself, but too afraid to brick my only phone
dreamersipaq said:
Sorry if this has been asked before, but I did search and found nothing:
I had an Inc. before, and traded to the X for the screen, and physical buttons which I like.
However, as we all know the X blows in comparison to the Inc. in terms of development; so I have to ask since I'm trying to decide what to do:
1) Is the kernel responsible for preventing us from things like notification toggles, notification recent apps, etc... ?
2) When Gingerbread/Ice Cream comes out, are we pretty much at moto's will w/o being able to modify the kernel?
3) What are the chances of seeing CM6 on the X specifically? I'd love to see it, but am no longer hopeful I guess
4) I saw that ccvp (or something like that) was able to hijack moto's init. Is this pretty much dead, or is there still work for it?
I don't really care that birdman stopped dev work on the X (he was responsible for a lot, i know) but will tear if more devs switch to other phones.
Any Ideas?
Again, sorry if all this was already covered.
P.S. I have programming, and Java experience so I WAS thinking to start trying to do some sort of cracking on this myself, but too afraid to brick my only phone
Click to expand...
Click to collapse
The inability to boot a custom kernel is the one and only roadblock to full custom ROMs like Cyanogenmod. And while I would never say 'never', I would not count on a hack showing up soon. Just go check in on the Milestone people (same bootloader)
Having said that, I would encourage you to go look at what's being done in the dev subforum. Roms like Tranquility, Apex, Zapx and the early Rubix roms are very solid, but removing much of the blur stuff.
Most recently, Fission & Rubix 1.0 are building just about the entire base from AOSP, using almost none of the motorola blur overhead.
Also, hacks have been recently released to overclock the processor.
All in All,there are certainly some limitations imposed by the kernel situation, but there is also still quite a bit happening.
I'd also like to add that it is virtually impossible to truly brick the DX now since the official OTA 2.2 SBF has been leaked.
The only thing we don't have on the DX is custom kernels. However, with all we do have at our disposal, I don't really care at all. I can fully theme, overclock, use all the root apps, etc...
I don't know whether or not the DX will get Gingerbread. It certainly is a possibility. However, I will be upgrading to the newer device designed for Gingerbread. When I say this, I mean a phone that's display can do 1024 by 720 resolution. Also, many of the top-end upcoming phones are going to have autostereoscopic 3D displays. Did I mention that many Gingerbread phones will have dual-core CPUs and GPUs with graphics which rival the PS3 and xBox 360? Well, they will
Remember, Verizon is going to probably do the same thing they did with the DX. They will let people get the 2-year account renewal price for the best upcoming phone even if you just renewed your 2-year contract this year. If someone renewed their contract with the DX and got it for $199, they will be able to do the same thing in December/January with the top-end Gingerbread phone most likely for $199 too
lmao no not really. Nobody is going to make anyone a KitKat ROM.
But holy crap, I forgot just how much I *LOVE* and *MISS* KitKat.
That was the last great Android platform for all-out customisation.
It's been all downhill since then.
Google has said "FU" to customisation in support of higher security and a whole lot of other stuff we don't need. Or uh,, that I don't need.
You sure as heck won't catch me banking on a freaking cellphone even if I were running stock unrooted.
I'm setting up an Odroid XU4 (think Raspbery Pi, but more bad-ass).
And its stock ROM is a currently developed KitKat 4.4.4.
And I'm having a bunch of fun installing all the COOL old apps I used to use.
I've already installed like 25 Xposed modules. Many of which can't be used on Lollipop or newer, let alone Nougat.
SOoooooo much customisation can be done to KitKat.
And even a default black theme. How cool was that. :good:
Theoretically speaking, would it be possible to build a KitKat ROM for the Pixel XL? Or any device for which the oldest source code available is newer that 4.4.4?
I would never actually install KitKit on my Pixel XL, but I'd be interested to know if there is a process for this sort of thing.
I'm not a dev but what little I've dabbled around with ROM's tells me that your source code needs to match the OS version you're trying to port (or at least be similar).
I'm sure someone may come along and tell me I'm wrong though.
CZ Eddie said:
I'm not a dev but what little I've dabbled around with ROM's tells me that your source code needs to match the OS version you're trying to port (or at least be similar).
I'm sure someone may come along and tell me I'm wrong though.
Click to expand...
Click to collapse
I'm here to tell you that you are wrong. XD - In all seriousness, you could with enough time and backporting probably make a 4.4 ROM for the Pixel using the drivers from whatever it came with ?7.0?. It wouldn't be easy and I can't say I have the skills and I don't have the time or willpower, but that's essentially what they did for some of the OG android devices to get them running on newer versions than what was released. The Motorola CLIQ comes to mind, they ported 2.1 on to the 1.6 drivers.
I'd give it a run, if some genius made one.
Sent from my Pixel XL using Tapatalk
Definitely possible, but nobody with the skills has time for that. Lol