[ROM][06-02-13][Flinny] Andromadus - CM10[133]

Search This thread

otariq

Senior Member
Feb 17, 2012
1,447
151
Are the functions to skip music with volume or pause with camera when screen is off working in latest build? I'm on 45 and they're not working
And I asked this earlier but does the new build let u customize lock screen with additional shortcuts i.e. mms or gmail
Sent from my HTC Vision using XDA
 

blk_jack

XDA Labs & Feed Dev/RD
Jun 7, 2010
3,307
11,443
Toronto
Are the functions to skip music with volume or pause with camera when screen is off working in latest build? I'm on 45 and they're not working
And I asked this earlier but does the new build let u customize lock screen with additional shortcuts i.e. mms or gmail
Sent from my HTC Vision using XDA

Not sure if they were in 45, but in 54+ you can skip tracks and play/pause with the camera button. Make sure you enable them in Settings -> Sound.

Sent from my HTC Vision using xda premium
 

otariq

Senior Member
Feb 17, 2012
1,447
151
They're enabled maybe it was just a bug but I dont like the new keyboard so I'll just stay on 45

Sent from my HTC Vision using XDA
 
  • Like
Reactions: youbadguy
H

hoffmas

Guest
building question

yesterday i made a build again and i had some problems:

i got a error related to the inline kernel building (im building on a fedora 64 bit system - gcc 4.6.3)

then i removed the commit in the boardconfig.mk and everything worked fine again...

so my question is the following: is this related to my operation system or does the inline kernel building not work?

thx in advance :)
 

blk_jack

XDA Labs & Feed Dev/RD
Jun 7, 2010
3,307
11,443
Toronto
yesterday i made a build again and i had some problems:

i got a error related to the inline kernel building (im building on a fedora 64 bit system - gcc 4.6.3)

then i removed the commit in the boardconfig.mk and everything worked fine again...

so my question is the following: is this related to my operation system or does the inline kernel building not work?

thx in advance :)

Inline kernel building has been fixed as of the 22nd.
 

otariq

Senior Member
Feb 17, 2012
1,447
151
Anyones clock freezing up on any of the test builds?? Kinda sucks when ur pulling all-nighters for exams and realize its an hr ahead of what the phone said lol

Sent from my HTC Vision using XDA
 

MarkyG82

Senior Member
Oct 26, 2010
805
93
Anyones clock freezing up on any of the test builds?? Kinda sucks when ur pulling all-nighters for exams and realize its an hr ahead of what the phone said lol

Sent from my HTC Vision using XDA

I can see how that could cause brain ache :) no issues here I'm afraid. Try a full wipe and reflash.

Sent from my HTC Vision using xda premium
 
H

hoffmas

Guest
video recording

ok, i think i found a fix for different resolution in video recording:

1. i changed the 720p bitrate to 600000 and 420p to 300000 (i think these are the bitrates our device is made for - at least that are the cm7 configurations)

2. all fps to 15

3. and thats the trick - i changed weight and height for all bitrates to 720 & 480

...dont know if this is a proper fix, but it works :) (you can see the difference between qvga and 720p)

i attached the media_profiles.xml - push the file to /system/etc and restart the phone

EDIT: after some more testing - it seems to be related to our phones display resolution = 600000 bitrate with 800 & 480 also works perfectly (i changed the attachement = 720p = 800 x 480 :))

EDIT2: maybe i fixed the timelpase for qvga

...maybe this helps for a real fix.
 

Attachments

  • media_profiles_2.zip
    2.3 KB · Views: 7
Last edited:

C.Flat

Senior Member
Anyones clock freezing up on any of the test builds?? Kinda sucks when ur pulling all-nighters for exams and realize its an hr ahead of what the phone said lol

Sent from my HTC Vision using XDA

This isn't unique to 55 it had done it on very early alpha builds too. Just open and close the keyboard and the clock will reset to normal

Sent from my HTC Vision using xda premium
 

philippecr

Senior Member
May 27, 2008
372
30
http://xdaforums.com/showthread.php?t=1564205

Can kindly check tis issue out too? ;)

---------- Post added at 05:46 PM ---------- Previous post was at 05:11 PM ----------

On a fresh boot (or hot boot) could you do:
logcat -d | grep vision

It will tell you what file it's loading for your keyboard. Once you have that file I can see that it's patched for the next release.

Thanks! :)

Code:
I/EventHub( 6163): New device: id=2, fd=110, path='/dev/input/event5', name='curcial-oj', classes=0x9, configuration='/system/usr/idc/curcial-oj.idc', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

D/EventHub( 6163): No input device configuration file found for device 'lightsensor-level'.

D/EventHub( 6163): No input device configuration file found for device 'vision-keypad-sea'.

I/EventHub( 6163): New device: id=4, fd=117, path='/dev/input/event3', name='vision-keypad-sea', classes=0xc3, configuration='', keyLayout='/system/usr/keylayout/vision-keypad-sea.kl', keyCharacterMap='/system/usr/keychars/vision-keypad-sea.kcm', builtinKeyboard=true

D/EventHub( 6163): No input device configuration file found for device 'proximity'.

i think this few lines is all u need? :)
 
Last edited:

Flinny

Recognized Developer
Nov 22, 2011
2,253
8,399
48
Sunderland
Sony Xperia 1 III
ok, i think i found a fix for different resolution in video recording:

1. i changed the 720p bitrate to 600000 and 420p to 300000 (i think these are the bitrates our device is made for - at least that are the cm7 configurations)

2. all fps to 15

3. and thats the trick - i changed weight and height for all bitrates to 720 & 480

...dont know if this is a proper fix, but it works :) (you can see the difference between qvga and 720p)

i attached the media_profiles.xml - push the file to /system/etc and restart the phone

EDIT: after some more testing - it seems to be related to our phones display resolution = 600000 bitrate with 800 & 480 also works perfectly (i changed the attachement = 720p = 800 x 480 :))

...maybe this helps for a real fix.

funky, I will take a look shortly. I know Fyodor had done a load of work on the kernel and ported new vidc drivers etc I just hadn't had a chance to try anything yet :)
 

Flinny

Recognized Developer
Nov 22, 2011
2,253
8,399
48
Sunderland
Sony Xperia 1 III
nope timelapse qvga is broken still not sure why it's doing that tbh as it'll record at qvga no problem. I'll disable it for now until I get a chance to look at it properly.
 

virtualflyer

Senior Member
Mar 16, 2011
352
46
http://xdaforums.com/showthread.php?t=1564205

Can kindly check tis issue out too? ;)

---------- Post added at 05:46 PM ---------- Previous post was at 05:11 PM ----------



Code:
I/EventHub( 6163): New device: id=2, fd=110, path='/dev/input/event5', name='curcial-oj', classes=0x9, configuration='/system/usr/idc/curcial-oj.idc', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false

D/EventHub( 6163): No input device configuration file found for device 'lightsensor-level'.

D/EventHub( 6163): No input device configuration file found for device 'vision-keypad-sea'.

I/EventHub( 6163): New device: id=4, fd=117, path='/dev/input/event3', name='vision-keypad-sea', classes=0xc3, configuration='', keyLayout='/system/usr/keylayout/vision-keypad-sea.kl', keyCharacterMap='/system/usr/keychars/vision-keypad-sea.kcm', builtinKeyboard=true

D/EventHub( 6163): No input device configuration file found for device 'proximity'.

i think this few lines is all u need? :)

Am I the only one getting no output from this?
Sent from my HTC Vision using XDA
 

Top Liked Posts

  • There are no posts matching your filters.
  • 304
    Andromadus - 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.
    35
    Build 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 myself
    31
    Yes 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 2
    28
    Latest 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