Droid X Apps: Let's Port em' - Droid Incredible Themes and Apps

Ok so looking through this dump I have I see things like Swype...which I would love ported to the dinc and even the nexus. it looks really nice. the dock would also be cool...I know we don't have one but ya. It's all already 2.1 based so I think it might be as simple as some lines of code. I am not a app dev or any kind of dev so I am clueless but I am asking for help.
Below is the Swype.apk which will probably be the best thing to port.
http://www.4shared.com/account/file/5iNF36bP/Swype.html
FYI: Swype installs but gives up some nice FC's
I'll look threw it all and see if anything else stands out. Some of the icons are nice and so is some of the framework. Maybe work on a little resizing...that I know how to do

Heres the log of when u try to enable it. This is just the important bit
Code:
I/ActivityManager( 122): Start proc com.swype.android.inputmethod for service c
om.swype.android.inputmethod/.SwypeInputMethod: pid=14167 uid=10107 gids={}
W/InputManagerService( 122): Starting input on non-focused client com.android.i
[email protected] (uid=1000 pid=13631)
W/dalvikvm(14167): Exception Ljava/lang/UnsatisfiedLinkError; thrown during Lcom
/swype/android/jni/SwypeCore;.<clinit>
D/AndroidRuntime(14167): Shutting down VM
W/dalvikvm(14167): threadid=3: thread exiting with uncaught exception (group=0x4
001e178)
E/AndroidRuntime(14167): Uncaught handler: thread main exiting due to uncaught e
xception
E/AndroidRuntime(14167): java.lang.ExceptionInInitializerError
E/AndroidRuntime(14167): at com.swype.android.inputmethod.SwypeApplicatio
n.<init>(SwypeApplication.java:67)
E/AndroidRuntime(14167): at java.lang.Class.newInstanceImpl(Native Method
)
E/AndroidRuntime(14167): at java.lang.Class.newInstance(Class.java:1479)
E/AndroidRuntime(14167): at android.app.Instrumentation.newApplication(In
strumentation.java:957)
E/AndroidRuntime(14167): at android.app.Instrumentation.newApplication(In
strumentation.java:942)
E/AndroidRuntime(14167): at android.app.ActivityThread$PackageInfo.makeAp
plication(ActivityThread.java:518)
E/AndroidRuntime(14167): at android.app.ActivityThread.handleBindApplicat
ion(ActivityThread.java:3996)
E/AndroidRuntime(14167): at android.app.ActivityThread.access$2900(Activi
tyThread.java:119)
E/AndroidRuntime(14167): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:1901)
E/AndroidRuntime(14167): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime(14167): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(14167): at android.app.ActivityThread.main(ActivityThrea
d.java:4363)
E/AndroidRuntime(14167): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime(14167): at java.lang.reflect.Method.invoke(Method.java:5
21)
E/AndroidRuntime(14167): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime(14167): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:618)
E/AndroidRuntime(14167): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(14167): Caused by: java.lang.UnsatisfiedLinkError: Library Swyp
eCore not found
E/AndroidRuntime(14167): at java.lang.Runtime.loadLibrary(Runtime.java:48
9)
E/AndroidRuntime(14167): at java.lang.System.loadLibrary(System.java:557)
E/AndroidRuntime(14167): at com.swype.android.jni.SwypeCore.<clinit>(Swyp
eCore.java:570)
E/AndroidRuntime(14167): ... 17 more
I/Process ( 122): Sending signal. PID: 14167 SIG: 3
I/dalvikvm(14167): threadid=7: reacting to signal 3
I/dalvikvm(14167): Wrote stack trace to '/data/anr/traces.txt'

Trying something.
Edit: So it worked, u gotta put the lib from /system/lib into the apk or i assume /system/lib of ur phone.
it stopped force-closing n is working. Gonna try out some more before uploading.

Btw this swype is 1.55.29.7532 isnt tht kinda old ? whts the point ? Current versions floating around on the forum are 1.56.30.7625
Im ditching this no point.

one thing that might be worthwhile is the microphone icon included in this version. So we can do voice to text right from the keyboard...

gbenj said:
one thing that might be worthwhile is the microphone icon included in this version. So we can do voice to text right from the keyboard...
Click to expand...
Click to collapse
Is there definitely a mic key on the Droid X swype keyboard?
If so, we need that!

http://www.engadget.com/2010/06/24/swype-psyched-to-be-on-droid-x-fifty-total-devices-by-the-end-o/
Im pretty sure that's it. Its not an older version i think its a different one all together.

Check out the Engaget video in Honestly77's link above at about 3:28. The Swype keyboard clearly has the microphone button in the lower right corner. Let's get this working!
Here is a pic.

crawform said:
Check out the Engaget video in Honestly77's link above at about 3:28. The Swype keyboard clearly has the microphone button in the lower right corner. Let's get this working!
Here is a pic.
Click to expand...
Click to collapse
Wow, yes, we must get this ported over. I know you guys can do this!

i hope some1 can port these apps!

Hmmm. k then ill port it tomoro. ill keep u guys posted

There are some other apps like the Blockbuster app and also it comes with these apps called Arc Video Editor Lite and Arc Photo Workshop. They sound cool...and also maybe some browser differences...dunno. And how hard is porting the live wallpapers? The droid eye looks legit.

Honestly77 said:
There are some other apps like the Blockbuster app and also it comes with these apps called Arc Video Editor Lite and Arc Photo Workshop. They sound cool...and also maybe some browser differences...dunno. And how hard is porting the live wallpapers? The droid eye looks legit.
Click to expand...
Click to collapse
+1 for arc video editor lite and arc photo workshop!!! I installed arc video it installed but I dont see anything im on the htc evo

Ok heres wht i have so far. Voice is working. its running in limited functionality, but thts been fixed before so can be done. Still lots of layout issues.
K bad news. Seems it was a fluke, it was unusable in the sense due to layout issues. Im afraid the .so controls whether you see the mic icon or not and that is compiled hence cannot be edited

Lame...do you think you'd have similar layout issues with other apps? I am assuming because everything is based to run within blur and on a 4.3 screen that porting things to sense is gonna be a ***** correct?

Any chance touchwiz could also be ported? I'm not a developer just thought I ask while you were looking at the issue thank you

Touchwiz can't be ported from a moto rom...and I don't even know why you would want to put touchwiz on it. Even Samsung should just use vanilla. Touchwiz Android is a huge failure.

Sorry I ment from the Samsung galaxy s ROM. I think its already been posted on the nexus one part of the forums in development, unfortunately it was ported for 2.2 if not I can post tomorrow. Any help would be appreciated, thanks. Just in case I got it wrong I mean the Samsung galaxy s launcher.

Did I hear the Droid X is coming with some kind of DLNA app? Is that only to stream from the phone or to the phone? If it's to the phone that would be an awesome app to port over....

Im not sure if we have the drivers for DNLA...they'd probably need to be re-written to be compatible with our phone. Also it could be hardware dependent meaning if we dont have the proper hardware it will never happen.

Related

Touch Flo screen rotate idea

The hero screen wont rotating wont look right
Cant flip "Phone" Tab
http://advertisingmatters.files.wordpress.com/2009/06/htc_rosie_1.jpg
Why don't we make a few changes and use the ahome build
mobilemaster999 said:
The hero screen wont rotating wont look right
Cant flip "Phone" Tab
http://advertisingmatters.files.wordpress.com/2009/06/htc_rosie_1.jpg
Why don't we make a few changes and use the ahome build
Click to expand...
Click to collapse
1) This has been discussed many times. TouchFlo is designed to work in landscape mode, if we force it it look like crap and nothing will fit.
2) aHome is not a build >.>
If we were going to get landscape TouchFlo the image on the phone tab is the least of our worries.
why not try to disable the keyboard-open listener in rosie, since that seems to be the only problem? rosie"s not made to work in landscape, so disabling the listener is much easier than actually making rosie work with a physical kb
jubeh said:
why not try to disable the keyboard-open listener in rosie, since that seems to be the only problem? rosie"s not made to work in landscape, so disabling the listener is much easier than actually making rosie work with a physical kb
Click to expand...
Click to collapse
I like this idea. I don't know anything about android coding but I think it might be possible with baksmali and smail...right?
I just really want to know, why are people so obsessed with having TouchFlo in landscape?! HTC never designed for Rosie to work in landscape so even if we could get it to rotate nothing would fit on the screen vertically...
AdrianK said:
I just really want to know, why are people so obsessed with having TouchFlo in landscape?! HTC never designed for Rosie to work in landscape so even if we could get it to rotate nothing would fit on the screen vertically...
Click to expand...
Click to collapse
Yeah I agree it would look absolutley horrible in landscape because that's NOT WHAT HTC intended
except from what i've read places it will be available in landscape mode eventually. as the lancaster has a landscape version that will come out....I could be wrong but i'll see if i can find the post
i think its not that they want it to work in landscape per say, but they want it to not forceclose or crash when they accidently go back to home while the keyboard is open. so i like the listener idea. hope it gets fixed in future hero rom
Disagree with me
HtC Espresso
new ui same concept
Disagree with me
HtC Espresso
new ui same concept
by the way i meant to make a new app alternative like advanced launcher
took you 7 months for a comeback?

Honeycomb Design for 'Normal' Phones - glimpse on IceCream?

Hey,
I wondered if anybody yet stumbled upon this:
If you set your Virtual Device in Android SDK to 800x480 px, Target: Android 3.0 (API level 11) and hw.lcd.density to 200 (or 240), you don't get the "normal" Honeycomb design, but instead a more greyish and blue Version of a Gingerbread-like design.
Also you get some new features known from the tablet os.
There is also a Incognito function in the browser and a Youtube setting in Camera.
Like on Tablet, Some apps have big bars on top with their Icons (sometimes clickable) on front. (They probably won't make it to the final release, though as it wastes space...)
Plus screen rotation looks neat.
Also the Launcher app has 3d animations similar to the "normal" honeycomb launcher.
Settings don't work properly, though.
Also I cannot provide screenshots at the moment as I am at work.
Keyboard keys for navigating:
pos1 = home,
NUM 7 = turn screen (deactivate numlock),
Screen up = menu.
But as probably this has been Issued before (yet I couldn't find it in search), just ignore this thread.
Crud, you could've made Engadget like that other dude, how come nobody saw this earlier?
hackm0d said:
Crud, you could've made Engadget like that other dude, how come nobody saw this earlier?
Click to expand...
Click to collapse
They was no video support, thats why "how come" lol
petbede said:
They was no video support, thats why "how come" lol
Click to expand...
Click to collapse
Someone could have still been curious and asked for a video.
hackm0d said:
Someone could have still been curious and asked for a video.
Click to expand...
Click to collapse
Yeah so true but likely that the ones that read it just not concern 2 ask lol

Theme or ROM?

So I'm curious about looks vs. functionality
Each one of my little drawings here satisfy both.
First off, I apologize for being a retard and using cam scanner to make these images sideways (although they were right side up originally).
Seeing as I can't attach images directly from my phone onto this site, I had to email them to myself, download them and then re attach.
Also another retard thing, I made a home button (app) thing on both of them even though there is a physical one on the phone itself.
Have a look
Also clarify with me which is which (theme or ROM).
How hard is it to design/engineer this and actually have everything function properly?
Theme/ROM 1
Them/ROM
it looks like you want to pull the whole status bar to the bottom of your phone. i didnt think you could just move that stuff around. a Dev would would be able to give u a yes or no.
im leaning more towards a theme than a Rom. but you can only theme what the Rom has. and NO rom has that, that i know of. so its like a combination of both.
Those drawings appear to be a significant layout overhaul, a la Sense and Touchwiz
It would either be:
1) a full-blown ROM
2) A replacement for a number of system apps (but could be an add-on), at the very least the launcher and probably the lockscreen
More than just basic theming, that's for sure.
Well it certainly gives the phone a neater, "in my opinion more efficient" functionality.
The one with the radial app dial, that spins, (you guys probably could tell that already) can fit either 7 or 8 apps.
When you press the home button the phone app automatically aligns directly above the said home button (non physical assuming there are 7 apps not 8).
The apps that go on the radial thing-a-ma-jig are your primary apps.
However since that non-physical home button is not needed, then the phone would be in the center or perhaps you'd like the browser.
In any case whichever app you use most extensively (ie #1).
I certainly cannot do any of the ROM creating but I was hoping to spark interest with the ones who are able to do so with ease.
The one with the triangle side bars (next image) these have 1-3 icons on them, when you tap that icon the first time a box will come up over lapping everything else in the background (or with slight opacity) and that gives you more detail rather than just an icon.
I think it would be neat as hell if this was done.
So is it like, theme = aesthetics ; rom = function
In this case I'd like to do both.
Also the capability to assign any app in that 7-8 slot (radial) would also be nice.
Perhaps done through the command prompt.
This is a feature I picked up from a blackberry (ability to assign any icon to a specific design/theme).
Thanks for the interest, I'm going to try and fix the orientation.
Some of what you're looking to do (the home-dial concept) may be doable without any ROM development at all - after all, plenty of launchers are installable as apps and what you're describing there is a launcher concept.
Notification bar moving could be a lot harder though.
FYI I'm a kernel guy not an app developer, so I can't help you much other than say that I'm fairly certain one of the features you want to implement can be done as a launcher app for any ROM.
Alright alright, we're sifting through sonething here.
I have very little knowledge od 'kernel' 'launchable' 'rom' as far as developing them goes. Are there tutorials ? (search bar probably)
Thanks for your contributions
What about color (borders keys etc)
Nice drawings man
Sent from my SAMSUNG-SGH-I997 using xda premium
Hey thanks DevilDogAK
It's one thing to draw the idea by hand but to actually create it with code...
That's where the tires hit the road one might say.
I need to do some reading to get an idea of what I have to accomplish.
Thanks for the interest, as always it starts with a dream
I'll let you guys know whats up when I actually get to the point of dev
But team work goes a long way (hint hint hint)
sweet... great concept imo, & hey, cyanogen started with just a concept. wish i knew more to help you out, but we're with you in spirit nice drawings too lol
from Sams inFuse... inFused GB
About the launcher comment, does having two mean more computing power needed to run the first and second launcher or can I just do one primary launcher?
If I can just move things around, what about putting some notification components under the wheel? Components such as the wifi toggle and the data image or perhaps the data and battery.
Anyone smart enough to do that probably isn't dicking around on XDA. You never know though.
Well... I'm here
Haha just kidding, I do wish somebody with some experience knowledge (ie developer of Serendipity etc... ) a man can dream... a man can dream.

Anyone interested in a near-working Wildfire S "port"?

I found a guide that mentions basic Sense porting to another Sense device. I tried this with this Wildfire S ROM for a few reasons:
--I prefer the "standard" HTC Sense as found on any other device (ie. Black status bar, black apps, etc.)
--I wanted to see how well it'd run
--I wanted to see if there'd be any problems with anything
After following the above guide, I notice only the following bugs:
--Camera is upside down
--Rosie keeps force closing because of forced landscape orientation so I have to use an alternate launcher
--Lockscreen is always in Portrait no matter what
--Keypad backlights don't turn on
--Facebook button doesn't work (duh)
--(New)GPS doesn't work - need to mess with GPS libs when I have more time
--(New)The FM Radio app's graphics are messed up
To try and fix the Rosie problem, I tried copying over the Rosie.apk and Rosie.odex from the Chacha's 2.3.5 OTA, but no dice, the system doesn't even see it.
Anyone have any tips on how I could fix any of the above? I'm no dev, and I only tried this for (basically) the fun of it to see how it'd turn out and my "experience", so to speak, only goes as far as swapping files here and there - I felt like the Development forum was the best place to post this. Apologies if it isn't.
good attempt! nice to see to back into work. May be some developers can help you out.
I would like to apologize first, as it is 08:19 in the morning and I'm already drunk. lol.
Well, let's start with the easy bits:
1. --Keypad backlights don't turn on
Mainly the thing is that the Wildfire S ROM does not have support (or it is not activated) for a physical keyboard; therefore the need for backlight is redundant. To fix this you will either have to manually add the code lines or un-comment them. I suggest talking with adlx or xdbg since both of them have implemented this feature in the two custom ROMs.
2. --Facebook button doesn't work (duh)
As above, the ROM doesn't know (or doesn't want to know) about the physical keyboard. Same suggestions as above.
3. Landscape/portrait issues.
Well. The main problem here is the android system. By definition it detects the longest size on the display and sets it as the height. Therefore you'll have a tough time fixing the standard display to landscape. As above, I suggest speaking with the devs that worked on these roms and implement the ChaCha kernel files into the Wildfire ROM.
Aaaaaand that's about it I guess. I wish you good luck!
Drunk, this early??
Good effort!
Sent from my A810e using Tapatalk
qzfive said:
I found a guide that mentions basic Sense porting to another Sense device. I tried this with this Wildfire S ROM for a few reasons:
--I prefer the "standard" HTC Sense as found on any other device (ie. Black status bar, black apps, etc.)
--I wanted to see how well it'd run
--I wanted to see if there'd be any problems with anything
After following the above guide, I notice only the following bugs:
--Camera is upside down
--Rosie keeps force closing because of forced landscape orientation so I have to use an alternate launcher
--Lockscreen is always in Portrait no matter what
--Keypad backlights don't turn on
--Facebook button doesn't work (duh)
To try and fix the Rosie problem, I tried copying over the Rosie.apk and Rosie.odex from the Chacha's 2.3.5 OTA, but no dice, the system doesn't even see it.
Anyone have any tips on how I could fix any of the above? I'm no dev, and I only tried this for (basically) the fun of it to see how it'd turn out and my "experience", so to speak, only goes as far as swapping files here and there - I felt like the Development forum was the best place to post this. Apologies if it isn't.
Click to expand...
Click to collapse
Nice!
For the backlight, maybe you could try using system/lib/hw/lights.msm7k.so from the stock Chacha rom, or even from SuperOSR...
You cannot copy/paste an apk+odex file, it will probably never work. Try deodexing it first, then copy it.
I guess this is the right place to ask
adlx.xda said:
Nice!
For the backlight, maybe you could try using system/lib/hw/lights.msm7k.so from the stock Chacha rom, or even from SuperOSR...
You cannot copy/paste an apk+odex file, it will probably never work. Try deodexing it first, then copy it.
I guess this is the right place to ask
Click to expand...
Click to collapse
I copied lights.msm7k.so from SuperOSR, and the keyboard backlight works now.
I used an application on my laptop called xUltimate to deodex both this ROM and Chacha 1.54 stock, and the only things that wouldn't deodex are the Lockscreen and Rosie :/
Camera appears right-way round/up if a 3rd party camera app is used
Additional bugs I've noticed after trying it out a bit again:
--GPS doesn't work - I'll mess around with gps libs tomorrow when I have a bit more time
--The FM radio app's graphics are messed up
For gps try also to use stock chacha libsensors (or something like that)
the right names for the files are:
/system/lib/hw/gps.chacha.so
/system/lib/hw/sensors.chacha.so
try using the one from SuperOSR.
Is this ROM going to be official released anytime soon because I am working on a ROM from another HTC device aswell and was wondering if you needed any assistance on final touches?
TechMayhem
This would interest me greatly, as I really love the "standard" sense and was quite disappointed with the amount of white/light colours used in the ChaCha's version, and how it just doesn't seem to fit in very well at all with the HTC family. Would it be possible to use the Desire Z's rosie? As that supports landscape natively.
TechMayhem said:
Is this ROM going to be official released anytime soon because I am working on a ROM from another HTC device aswell and was wondering if you needed any assistance on final touches?
TechMayhem
Click to expand...
Click to collapse
Tbh, I haven't done anything on this for a while because I started flashing CM7/SuperOSR.
From what I can remember, the following things wern't working:
-Lockscreen - Always in Portrait, won't rotate
-Rosie - Force-close loop, had to replace with an alternate launcher
-GPS - Icon doesn't appear in the status bar
-FM/Dailer/maybe others - Graphics messed up due to forced landscape resolution
That's all I managed to check before I got caught up in crackflashing XD
I am by no means a dev - all this was done by replacing files in a Wildfire S ROM with ones from SuperOSR/stock Chacha
Atomix86 said:
This would interest me greatly, as I really love the "standard" sense and was quite disappointed with the amount of white/light colours used in the ChaCha's version, and how it just doesn't seem to fit in very well at all with the HTC family. Would it be possible to use the Desire Z's rosie? As that supports landscape natively.
Click to expand...
Click to collapse
Precisely why I tried this in the first place - I wasn't expecting all this white, which doesn't make the Chacha feel like an HTC as much to me - I already tried the Desire Z's Rosie - while it did work, all the icons were huge (because of it being scaled for HDPI screens). Dunno about widgets.
Once I find it amongst all the crap I have on my laptop, I could upload it if anyone might have an idea how to fix what's left and to see what else is broken?

[Q] Recoloring elements of contacts

Hey everyone,
First of all sorry if I posted in the wrong section, I'm very much new here, trying to find my way around the forums.
Now, for my question: I'm using an old but trusty Galaxy Ace with Nebulosity ROM, Nova Launcher and the Gummy Liberty Gold theme. Pretty much everything in my phone is colored yellow or black, except those pesky little blue triangles in the bottom right corner of the contacts icons. (See the attached picture and you'll know what I'm talking about.) It really keeps bugging me as everything else is pretty much unified color-wise. Now, the problem is that I don't really know where the system gets the resources for that particular item. I suspect I could switch the launcher's color theme, but it causes a crash on the current ROM I'm using and forces me to reinstall the launcher. Is there any way to recolor that particular element? How can I find and modify it without having to change the launcher's color theme (if it's even possible at all)? Something I have tried (bear in mind that I have very little programming background, I'm pretty much picking up everything as I go) was decompiling the Liberty Gold theme in hope of finding a little blue triangle somewhere along the assets so that I can recolor it, but alas, nothing like that - this is why I'm suspecting that that element might be part of the system itself instead of the theme.
These might all be stupid questions, as I said, I don't know half as much about these things as I should, but I would really appreciate if someone could elucidate me on the destination of that particular element (or just it's color source) so that I could recolor (either in photoshop or by replacing the color code) it and make the whole UI have the same color scheme. It's not too too big of a problem and I do not want to waste anyone's time, but if there's someone out there who happens to know the answer, please write, I'd really appreciate it.
Thank you in advance!

Categories

Resources