I am aware that "HD2 ROM Development" is probably not the best place to post compatibility issues with WM6.5, however, since there is no WM6.1 ROM for the HD2, I hope that this concerns other folks too.
I have several for me quite usefull applications which worked very well on many devices up to WM6.1 Build 21054, which I guess is one of the last WM6.1 builds. These applications show now varous glitches under WM6.5, particularly with item and date selection. I have tried numerous ROMs of the 218xx and the 235xx builds from various cooks on several devices, my preference are the Energy Series Roms by NRGZ28 though. Some of my applications with compatibility issues are:
Agenda Fusion 8.70 Calendar Software
http://www.developerone.com/agendafusion/index.htm
True Term - Dictionary Software
http://www.trueterm.com/DL-WindowsCE.html
practically all Visual Basic Software
I upload an example of a nice Periodic Table. The required runtime library is here:
http://download.microsoft.com/download/e/6/7/e67b873f-7d9f-4ee0-9fde-364218fcfa95/msvbppc.armv4.cab
Is there any hope that more modern builds will be compatible with older software again?
Related
Not to sure if anyone has heard of Hexxeh before but here is a short wiki descript regarding Chromium OS builds: "By May 2010, compiled versions of the work-in-progress source code had been downloaded from the Internet more than a million times. The most popular version was created by Liam McLoughlin, a 17-year-old college student in Manchester, England, posting under the name "Hexxeh". McLoughlin's builds boot from a USB memory stick and included features that Google engineers had not yet implemented, such as support for the Java programming language"
Anyhow several Google videos show that he has successfully managed to boot one of his Chromium OS builds called "Flow" on a tablet. And was wondering if anyone has thought about doing this.
His main website: http://chromeos.hexxeh.net/
I've used Flow on a laptop. Not very useful on a tablet - it's basically just a back end for a web browser, with no (well, minimal) apps. Useful for giving to the kids to play web games without breaking your system. However, using the Android OS built for tablets you get access to all the apps.
Looks like someone is working on it!
http://www.geek.com/articles/mobile/chrome-os-tablet-from-acer-outed-by-bug-reports-20110428/
I have been looking for a good CM 7.1 based ROM and am having a hard time deciding on one. The main thing I am looking for is the advanced lock screen delay and timeout settings. I cannot tell if this is a difference between CM 7.1 and 7.0.3 or if it is just a setting that some ROMs have and some do not.
Can someone shed some light on this for me? Is there a way to add this functionality? (I care because work enforced a security lock on my phone for email access, but I don't want to have to type i tin EVERY time the screen goes off. iPhones and WinMobile don't. It seems to be a flaw in Android's ActiveSync).
Thanks in advance.
This feature is new in CM 7.1. However, other users have reported success using Delayed Lock + WidgetLocker apps from the market to effect the same functionality, though I am uncertain how well they play with the Exchange server's demands.
Alternately, if you really don't want this security lock feature at all then you can find versions of Email.apk that will just lie to the Exchange server about the phone's configuration. Then you can configure your lock settings however you like. Ah, the classic fallacy of a security model that trusts the client...
I actually like the security of the password. I just wish it behaved like ActiveSyns on every other type of device (Win Mobile, iphone, etc) and let you set a delay (defined by the system administrator) for when the device security locks, not every time the screen goes off.
I wish we had a good CM7.1 ROM. Oh Z, wherefore art thou?
Yeah, running a nightly (or a ROM that pulls from nightly) is currently the only practicable choice to get the feature.
I backported the feature's code to the CM 7.0.3 codebase and built a custom ROM for my own device. I wanted the feature but didn't want to run the unstable nightly on my primary phone. Well, "backport" isn't the correct term, because the feature was developed against 7.0.3 and was rebased to 7.1 for submission to the source repo. But you know what I mean (haha).
organophosphate said:
Yeah, running a nightly (or a ROM that pulls from nightly) is currently the only practicable choice to get the feature.
I backported the feature's code to the CM 7.0.3 codebase and built a custom ROM for my own device. I wanted the feature but didn't want to run the unstable nightly on my primary phone. Well, "backport" isn't the correct term, because the feature was developed against 7.0.3 and was rebased to 7.1 for submission to the source repo. But you know what I mean (haha).
Click to expand...
Click to collapse
Care to share?
rearview said:
Care to share?
Click to expand...
Click to collapse
You know, I realized after posting that I probably look like a jerk for not offering. I apologize. There are issues that seem to preclude this, however.
The target of the relatively minor code changes necessarily included one of the fundamental framework jars.
When I was developing the feature, I only compiled CM for the Droid Incredible. Didn't make sense to compile for platforms I can't use/test, especially given the next point.
It takes my machine 90+ minutes to compile a ROM for a platform.
I believe that if I gave you a flashable update.zip to replace the affected jars it would have a high probability of cacking your ROM and would result in bootloops. Not absolutely certain, but fairly concerned about the possibility. I believe you would have better luck running a nightly that people report as "relatively stable" in the forums (some nightlies are better than others).
When the feature was merged, I really thought CM 7.1 would be out soon. RC1 dropped a month *before* the new feature was merged. That sounds odd in retrospect, because most projects freeze feature additions before entering the RC phase of a release (ie. they accept bugfixes only).
I just assumed it was for an X10 since we were in the X10 forums. Since this phone isn't officially CM supported I'm at the mercy of ROM developers to make a nice CM7.1. There are a couple out there, and they all have issues. One is close, but the dev seems to have gone missing. I hope he returns soon.
Is modifying one jar file all that it would take? Which file? If I knew that I could possibly take the jar file from one of the CM7.1 ROMs for my device (which has issues) and put it into a 7.0.3 that works smoothly and be happy.
rearview said:
Is modifying one jar file all that it would take? Which file? If I knew that I could possibly take the jar file from one of the CM7.1 ROMs for my device (which has issues) and put it into a 7.0.3 that works smoothly and be happy.
Click to expand...
Click to collapse
I like your train of thought. Unfortunately, even if that were to work you would be unable to configure the feature, because the UI is in the CM Settings apk (ie. the apk that makes "CyanogenMod Settings" menu option appear in your Android settings). If you were to also grab the CM 7.1 settings APK and install it, then that would replace the old version. The CM 7.1 version has all sorts of changes, controls for other new features, and so forth; therefore, that would break much of your other functionality.
How conversant are you in software development? You may be able to join one of those CM 7-derived ROM projects for your platform. It should be relatively easy for someone with a CM dev environment configured for your platform to grab these patches via git cherry-pick and build a 7.0.3 "Gold Edition" with this feature added. Because it should be easy, you might be able to persuade one of those custom ROM developers to grab this feature and include it.
If you are interested, here are the links to my patchsets that were merged to implement the feature:
Framework Implementation
CM Settings UI
I believe the patches will merge "nearly cleanly" into a CM 7.0.3 derived branch. That is to say, if there are merge conflicts they will not be substantive and will merely involve wholesale cut/paste reordering of methods within the given class files rather than requiring a rewrite of any part of the actual implementation.
I know that this simple reordering is all I changed between my 7.0.3 development version and the 7.1-derived submission. Seems Steve Kondik did a little further rearrangement to accommodate other patches that had been accepted/merged while mine was pending. Same deal there: still should be relatively simple.
I'm not much of a developer, though I'm an IT guy with some unix background. I'll look at it.
*Moderator(s) I m sorry if this doesn't belong to this section ..please move it if u want ( and inform me please)
Guys I was just wondering why Google releases updates every year ...it doesn't bring any notable new features sometimes ( like froyo to gb = nothing new) sometimes some phones take a whole year to get the update and in the meantime a new update is announced
And then we have our manufacturers who refuse to update our phones( if u r looking at my signature and want to tell me that I should buy a high end phone lets talk about what happened to SGS 1 first ) and make the whole update sick
I think Google should convince the manufacturers to update all devices and Google itself should annonce less updates( less quality updates >>>> more quantity updates)
Or can someone explain Google 's strategy to me???? It sure doesn't make sense to me
Kind of agree with what you have to say.
In my opinion many people have low end devices, which don't really get the latest os updates anyway, thanks to the phone manufacturers. So you'll have a large chunk of the user base using the older versions. Which in turn results in a large amount of applications targeting the older versions too.
The_R said:
Kind of agree with what you have to say.
In my opinion many people have low end devices, which don't really get the latest os updates anyway, thanks to the phone manufacturers. So you'll have a large chunk of the user base using the older versions. Which in turn results in a large amount of applications targeting the older versions too.
Click to expand...
Click to collapse
+1 ...I just can't see why Google makes the fuss about updates ??? I mean "update " by its very definition means improving I.e. older phones getting newer os but android phones hardly get more than 2 updates! !!! Even if the hardware supports the new software! !!!
What do you mean no changes between Froyo and GB? From Wikipedia here are some:
v2.3
On 6 December 2010, the Android 2.3 (Gingerbread) SDK was released, based on Linux kernel 2.6.35. Changes included:
Updated user interface design with increased simplicity and speed
Support for extra-large screen sizes and resolutions (WXGA and higher)
Native support for SIP VoIP internet telephony
Faster, more intuitive text input in virtual keyboard, with improved accuracy, better suggested text and voice input mode
Enhanced copy/paste functionality, allowing users to select a word by press-hold, copy, and paste
Support for Near Field Communication (NFC), allowing the user to read an NFC tag embedded in a poster, sticker, or advertisement
New audio effects such as reverb, equalization, headphone virtualization, and bass boost
New Download Manager, giving users easy access to any file downloaded from the browser, email, or another application
Support for multiple cameras on the device, including a front-facing camera, if available
Support for WebM/VP8 video playback, and AAC audio encoding
Improved power management with a more active role in managing apps that are keeping the device awake for too long
Enhanced support for native code development
Switched from YAFFS to ext4 on newer devices
Audio, graphical, and input enhancements for game developers
Concurrent garbage collection for increased performance
Native support for more sensors (such as gyroscopes and barometers)
Click to expand...
Click to collapse
A lot of it is new hardware support to keep up with technology. The new audio effects it talks about make it possible for system wide EQ apps without root like Equalizer, before GB IIRC this was not possible. They've also made multitasking better so that task killers shouldn't be needed.
Their update strategy is to debut the new OS on a Nexus device and then release the source so others can use it. Personally I would like to see Google let developers in earlier in development so they can get drivers and upgrades done quicker. This is how Microsoft does things and is why OEMs can have the new OS ready on hardware on its debut day. But Google's strategy is quite a bit different.
spunker88 said:
What do you mean no changes between Froyo and GB? From Wikipedia here are some:
A lot of it is new hardware support to keep up with technology. The new audio effects it talks about make it possible for system wide EQ apps without root like Equalizer, before GB IIRC this was not possible. They've also made multitasking better so that task killers shouldn't be needed.
Their update strategy is to debut the new OS on a Nexus device and then release the source so others can use it. Personally I would like to see Google let developers in earlier in development so they can get drivers and upgrades done quicker. This is how Microsoft does things and is why OEMs can have the new OS ready on hardware on its debut day. But Google's strategy is quite a bit different.
Click to expand...
Click to collapse
Even I was thinking about your last point u know, when the update gets announced it should be released simultaneously ......waiting a whole year ( or 5-6months) sucks
That's why there's great community(s) like xda forums and projects like cyanogenmod. Linux is open. Android is based on Linux. Android isn't AS opem.
The developers are here to help remedy some of that.
After combing the internet for a couple weeks, since installing Ubuntu Touch on my Nexus 7 2013, I have yet to find an up to date video, review, or usable bug report for the layperson as an end user. This is desperately needed and would lead to speeding up developing apps and abilities of the OS and its application on various devices.
Using the OS on a daily basis I have seen sporadic new apps showing up in the "Available" section of the APPS Scope, mostly non-US types in some other language. I ave no idea where they come from nor who is submitting them, but evidently, folks in Germany and other Euro countries have the ear of the devs developement. Up until now, There's no porting of regular .deb applications such as Pidgin or even open source versions of Flash for video viewing. Yes, I can't even watch the nonexistent Youtube videos about my OS on the OS, itself.
Someone pick up the ball on this blazing hot mobile OS, please?! We could use some content about it and its developement!
There are some resources out there. The following is a list of the links I use most:
Build test results: http://ci.ubuntu.com/smokeng/utopic/touch/
Changelogs: http://people.canonical.com/~ogra/touch-image-stats/
Development info: http://developer.ubuntu.com/apps/
Bug reports are handled via launchpad: https://launchpad.net/
If you're unsure which package to report it against, maybe use this one: https://launchpad.net/ubuntu-touch-preview
Oh, and some porting is actually done: Trojita and Cantata
This is a pretty simple inquiry. Consider it an open poll. I am on the hunt for new SIP Softphone apps for Android. Paid and Free are welcome to be suggested. I would prefer, if they are free, that they either have no ads or can be paid for (one-time) to remove the ads entirely.
If someone has already suggested your favorite, give it an upvote and feel free to add comment to say why you love it. A focus on features will stand out. I will be personally reviewing each suggestion and posting my own comments as to its suitability - I work in telecom will be extensively testing all SIP features, including things like SRTP and SSL/TLS support against Asterisk based servers.
I'm already aware of favorites like CSipSimple (horribly outdated and a bit unstable on latest versions of Android), Zopier (has a wonky SRTP implementation), and Bria (subscription-based licensing for a SIP Softphone you still need your own server to use!?). I'm looking for lesser known and newer apps many people may not have heard of but are worthy of attention.
Thanks for your help!