dont try to change qvga timelapse to m4v = bootloop
heh didn't bootloop.. yet didn't work also strange how qvga itself works... might just disable qvga completely for now.. not sure why anyone would want to use it tbh
[ROM][06-02-13][Flinny] Andromadus - CM10[133]
- Thread starter Flinny
- Start date
heh didn't bootloop.. yet didn't work also strange how qvga itself works... might just disable qvga completely for now.. not sure why anyone would want to use it tbh
H
hoffmas
Guest
qvga
the right values for qvga (or actually vga): width 640 height 480 bitrate 128000
summary: 480p and vga works... 720p is a fake
the right values for qvga (or actually vga): width 640 height 480 bitrate 128000
summary: 480p and vga works... 720p is a fake
Last edited:
I just had one issue with build 55 and connecting to the bluetooth car audio (Ford). Every time I enter the car, it asks me for a new code. Also, I have to enter the code twice for it to work. Once connected, it will stay that way until I go out and come back to the car. Bluetooth audio (calls) does work when connected.
Have not forgotten about this, have been busy and working on stuff that isn't ready for the big wild world yet 56 is still the build I'm running as a DD
Nick.
Nick.
Do check out the Asia SEA keyboard too. I've attach the logcat on one page b4 tis.
It's about some hw key map error,
Fn+? Give me ) but it's should be "
And SYM does nothing.
Sent from my HTC Vision using XDA
It's about some hw key map error,
Fn+? Give me ) but it's should be "
And SYM does nothing.
Sent from my HTC Vision using XDA
Last edited:
Do check out the Asia SEA keyboard too. I've attach the logcat on one page b4 tis.
It's about some hw key map error,
Fn+? Give me ) but it's should be "
And SYM does nothing.
Sent from my HTC Vision using XDA
SYM works with Italian, fn+? doesn't too
gonna make a zip within some minutes...
Is it just me or was camcorder working in b2? It was broken in 55, but that seemed to be the only thing I found wrong. I even tested voice and video chat in gtalk. Both worked (video only worked in b2), just at a reduced volume, which gives me hope for wifi calling, with or without the help of HTC or Tmo.
Here goes 56, and thank you again to @Flinny @DarkSpadez and the rest of the team.
Sent from my HTC Vision using XDA
Here goes 56, and thank you again to @Flinny @DarkSpadez and the rest of the team.
Sent from my HTC Vision using XDA
Last edited:
Here it is, the improved keychars (as a matter of fact only that bug is removed). I DON'T HAVE THE PHONE to try it and it will be like this for a week or so, so I can't test it and I can't be sure if it works or the zip doesn't burn your phone. If anything goes wrong flash this http://android.mimic.ca/static/andromadus/Audacity-Camera_Button_Focus_Fix.zip thanks to blk_jack
Last edited:
That problem is pretty well universal to AOSP 4.0.x. The solution is to modify your MMS APN and delete the contents of the "apn type" field. That will make the MMS APN "selectable". When you want to MMS, select the MMS APN. When you're done MMS'ing, re-select the data apn.
and do u think it's possible for us to flash the Chinese IME from the Galaxy Nexus to this build?
Build 62 up.. don't ask what happened in between, many very alpha things that have not yet made the repo/may never see the light of day
Removed the old volume lock completely and put an early build of the CM lockscreen mods in instead.
Apart from that some other stuff CM added in the meantime.
The codebase is getting closer and closer to CM9's codebase as they implement some of the stuff we borrowed from elsewhere in the meantime
If the camera/video cam FC's when you first open it clear the camera data or wipe. Should be as B2 at least.
Nick.
Removed the old volume lock completely and put an early build of the CM lockscreen mods in instead.
Apart from that some other stuff CM added in the meantime.
The codebase is getting closer and closer to CM9's codebase as they implement some of the stuff we borrowed from elsewhere in the meantime
If the camera/video cam FC's when you first open it clear the camera data or wipe. Should be as B2 at least.
Nick.
I upgraded from build 56, wiped cache and camera data and all works well
seems a tad smoother than before
also, since the build that fixed temple run, my touchscreen finally doesn't go haywire when charging (in gingerbread, even on official htc builds, my touchscreen would go crazy when connected after using it for a couple of minutes, a touch event in the left lower corner would get stuck)
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
304Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Current Changelog below
Checkout http://andromadus.flinny.org for links/files/previous changelogs
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.35Build 113
Kernel patched to 3.0.46
BFQ v5 I/O sheduler added
Lots of CM display patches
Synced with CM
Circular battery icon with/without a % is now an option
Lots of Display patches. Overlay is automatically turned off for video now so no need to turn HW overlay off manually anymore.
Fixes video playback and panoramic preview by default until we get some new props from qcom with them fixed properly I expect.
Once this audio bug is sorted I think I'm almost happy to release a beta
As for the touchscreen...
touch.pressure.calibration = amplitude
touch.pressure.scale = 0.01
is what the .idc for the touchpad currently.. it's possible chaning it to 0.001 makes it more responsive... Will give it a try myself31Yes I know 4.2 is out... currently trying to compile it. I would like to get a beta out at 4.1.x level but we shall see how big the merge process is. I expect I will be releasing both 4.1 and 4.2 builds for a while whilst the dust settles at least.
Sent from my HTC Vision using Tapatalk 22928Latest version changelog.
CM10 build 133
There was an issue with the backup tool in the last build that will break gapps and your account's etc when flashing this build, the solution is to re-flash gapps at the same time as the rom and you should be fine. This build should fix it so that the next build will work as it should
Changes.
Synced with CM - Again not many changes upstream.
Basically everything relevant to our phones up to the 4th of February in the following has been merged
http://review.cyanogenmod.org/#/q/status:merged+branch:jellybean,n,z
Kernel updated to Andromadus Current - 3.0.62
