Develop Bugs

[Q] optical trackball problem - any way to disable the sensor?

After some water exposal, bottom hardware buttons (along with optical trackball) refused to work.
I have fixed them with some precise inside cleaning, but the optical function (not the button himself) continues malfunctioning, which is not a big deal for me, but..
The exact problem: i spotted in dark environment, that the sensor inside continuously glimmers in all modes - scren-off, scren-on (without puting finger over him), etc.. In return, my battery drains extra aprox. 10-12 mA!
I have observed, that in healthy device, sessor glimms only when interacting with him..
Is there a chance to disable this sensor to avoid this? I hope in software manner

I don't think there is anything out there that will disable the optical pad. You could give HTC a call or your carrier and see what they say.

There is this thread on the forums about turning off the backlights.
Should work for trackball as well? Probably. Something about LED Hack on the first or second page. Seems to be something on the 3rd page as well.
Go have a read over here (I just skimmed. its 2am lol) http://forum.xda-developers.com/showthread.php?t=704977

@formformer
If you tell me your kernel version I will try to build a kernel without trackpad support!?

@Meaple 's post was sadly adequate and rips best hope in me ;( ..
@eden2812 I have using 2 led hacks from previous attempts to minimize energy consumption & eye comfort, and they shurely don't do the "trackpad sensor shutting" job..
@AndroidJaspie
it's so damn cool to offer this kind of experience. salute!
i have likely using latest Ginger Villain's compilation, but any recent rom-kernel set, with weak appetite fits my best.
i will be very patient to hear from you..
my current setup is:

OK I built a new kernel from the cyanogenmod sources now without trackball support. I tested it with GingerVillain 1.4 and it worked.
please make a backup and then give the update.zip a try.
Tell me if the new kernel solved your problem or not.
Jasper

Yes Jasper, obviously the sensor is shutted (no glimmering observes) and the xtra drain is all gone now!! I'm so pleased.
But i have found, that the bottom buttons (including the button under the optical trackpad) not waking the phone any more. Is this issue related?
And another, not so important question: Would be this kernel compliant with other Gingerbread releases? or.. could you give me some hint, if is possible to transform your "surgery" into a some kind of a patch, that will give me opportunity to enjoy any feature kernel/roms?
Again, BIG 10x for your respond in this custom problem so far! You make my life happier
karel

No problem i like it to work with things like that. So it's a good chance to improve my knowledge about linux and help other people at the same time.
Are you talking about the all buttons or only about the button around the optical sensor?
If you are talking about the one around the sensor then it's normal that it won't wake up the phone any more. But the others(home, menu, back and search) should work like before.
This kernel works only with cyanogenmod and GingerVillain. On other rom's like Oxygen it doesn't work. But you i can compile you the kernel you want.
At the moment it's only possible to disable the trackball only by editing the kernel configuration. But i will try to get it working without changing the kernel so that you can use every kernel you want.
Jasper

i told so, about the relation of shutted sensor and not working buton.., but yes, others buttons also not working in lockscreen-off mode, where they should or at least worked before. (volume butts still works for wakening..)
ps. a have barely no linux skills, but its interesting for me either!
and if editing & compiling is not so high level task, im going to try first steps right now!
Any way, disabling track sensor without editing kernel settings sounds like a dream..
k

hi, my fried
could you tell me, where in the config I can find the exact setting and how to change it?

hi
if you got the kernel source you can make menuconfig to configure the new kernel. To disable the trackball go to "Device Drivers" --> "Input device support" --> "Opticaljoystick". To disable the joystick press "n" to enable it press "y"
Don't know how to comile your own kernel?
here is a useful links that helped me, too:
-[HOW-TO] Build your own kernel package from source

huh.. 10x 4 the guides, they light me enough to get started week ago, but i get stuck just in the beginning (problems with MBR or something..). and at this moment i have absolute lack of time to deal with this interesting stuff. However.. can i have one more last ask from you: to compile for me an updated kernel.. (they says he has the ability to record 2way call conversations..)
Using the Ginger Villain rom, suppose with this richardtrip kernel. Guess CM will worx too..
Thanks anyway!

ok
a bit late but here it is
a new kernel version 2.6.37.2 from the richardtrip-sources.
kernel features:
-disabled trackball
I don't know anything about "Two-way call recording kernel support" but i will try to find out as much as posible to configure a kernel with it.
jasper

Hi AndroidJaspie, i've the same problem with the optical trackball of my desire. I use the miui rom with the kernel 2.6.37.6-cyanogenmod-g8913be8. Can i use the kernel in your last post? thx bye

Please use the Q&A Forum for questions Thanks
Moving to Q&A

[DEV] Color banding issue (CM7/MIUI/AOSP only) - SOLVED [9/11]

Hi all.
The issue has been SOLVED as of today (9 Nov), thanks to marc1706. He successfully identified a line in the kernel video drivers, which has completely eliminated the color banding from what I can see. There is no need for any other fix to be applied.
The thread for his kernel can be found here: http://forum.xda-developers.com/showthread.php?t=1282435. Be sure to thank him for his wonderful work!
For kernel devs interested in applying to fix to current kernels, his commit can be viewed here: https://github.com/marc1706/cm-on-wince-htc/commit/dfe41d02cac454e3e58c583cd4fa0c0825160d1f.
Thanks for all the support guys, glad it's finally solved.
MrP.

It's a great thread, but the kernel developers are already aware of this I'm sure

Thanks for the compliment.
I'm sure they're aware of it, but possibly not aware of its solution. Hopefully this can serve as a general thread to discuss its solution for all devs to benefit from.
MrP.
Sent from my HTC HD2 using XDA App

Developing on the hd2 will never stop

Eagerly waiting for a solution, I hope someone find a solution for this!
This is the last big issue left to solve...

One other thing - if anyone has any ideas of what the video incompatibility might be related to, please let me know and I'll play around with possible fixes.
MrP.

sbryan12144 said:
Ok. I'll tell before I release.
The old kernel was based off of the EVO 4G's 2.6.32 source right? -Yes
The new kernel is based off of the Desire's 2.6.35 source right? -Yes
Doesn't that mean we'd need actual Desire libs rather than others? -Yes!
I tested marc's 1e kernel with my OLD Bravo build that I made from the Desire's Official RUU (3.14) and CAM WORKS. So my theory is correct. I tested it on my RCMix3D Runny Build and it works as well.
Hope you guys are happy
Don't forget to credit the kernel builders and me for this fix!
Click to expand...
Click to collapse
Maybe this will help?
Sent from my HTC HD2 using XDA App from my HTC HD2 using XDA App

Thanks for the heads up.
I am aware of that post and I'm actually busy looking into it. The only problem with simply bringing the Desire libs over is that those libs are designed for Sense builds, so as sybryan12144 has mentioned, it will work for bringing those libs over to our Sense ports. The real problem is getting them working under AOSP builds. Shall take a further look never the less.
MrP.

The easiest way I found to reduce colour banding is to set the DPI to 217, although that means losing a lot of apps in the market with my rom.
I don't think we can ever fully eliminate due to our 65k displays...
Sent from my HD2 using xda premium

Contrary to popular belief, the color banding in Android is not necessarily due to a limitation of our 65k screens. Although the pictures in the OP are representing the fix for the notification pane only, there were no color banding issues that I could find anywhere in the ROM. It truly removed the issue completely.
If you'd like to test, you don't even have to reinstall your current ROM - just grab marc's 2.6.35 kernel, and warrenb123's 2.6.35 kernel. You should be able to install them over your current build, but you'll notice that warrenb123's kernel eliminates the color banding, probably due to the fact that it uses the Desire GPU driver. Marc's kernel, despite being a 2.6.35 kernel, does not solve this (yet).
MrP.

Try changing this in your build.prop...
debug.fb.rgb565=1
Works wonders for sense builds!
Sent from my HTC Desire HD A9191 using XDA App

tobiascrystal said:
Try changing this in your build.prop...
debug.fb.rgb565=1
Works wonders for sense builds!
Sent from my HTC Desire HD A9191 using XDA App
Click to expand...
Click to collapse
That only works if you already have the Desire kernel installed though...

I am using heiros kernel and it is working fine for me!
Sent from my HTC Desire HD A9191 using XDA App

MrPadie said:
Contrary to popular belief, the color banding in Android is not necessarily due to a limitation of our 65k screens. Although the pictures in the OP are representing the fix for the notification pane only, there were no color banding issues that I could find anywhere in the ROM. .
Click to expand...
Click to collapse
things like notification panes etc which have simple gradients can be nearly eliminated. But look at more complex ones eg photos of clouds. 65k is 65k and 'you cannae break the laws of physics.. .'
Sent from my HD2 using xda premium

http://forum.xda-developers.com/showthread.php?t=1268085

@consolation - no doubt, I agree with you. However maybe I should more clearly state that I am referring to the quality of ROM elements. 65k is 65k, and some gradients will be visible obviously, but the quality of ROM elements without the fix is somewhat disappointing.
MrP.
Sent from my HTC HD2 using XDA App

@famewolf - that doesn't truly solve the issue, nor does it work well with regards to ROM elements. Already tried it on typhoon, banding issue doesn't change in the notification pane at all.
MrP.
Sent from my HTC HD2 using XDA App

I belive that, as most android comming after 2.2 came with 250k+ colors, the gradient algo was not updated. Try this, on CM roms, add the music and the analog clock to your screen. Notice the heavy banding. Now, try to move them. Notice that a different algorithm is used whyle moving.
That algorith is probably used all the time on the gallery, solvind the banding issues.
That yellowish/blueish gradients on the background should suffer from the banding also.

Well put daedric. I am therefore assuming that this 'algorithm' then has been updated/fixed/implemented properly in the Desire GPU driver.
To everyone - I think what we need to understand here is that the issue exists, and it's main cause is directly related to the GPU driver. Yes, there are one or two things that possibly ease the issue (saturation fix and rgb565 flag in build.prop), but the proper, native fix lies somewhere in the Desire GPU driver. Now, seeing as I am not a kernel dev, I cannot pinpoint the cause/solution.
So, the main point that this thread should express is that the issue can be fixed, by applying the Desire 2.6.35 port. However what we are trying to achieve is using this port without breaking video/camera/camcorder compatibility.
MrP.

MrPadie said:
Well put daedric. I am therefore assuming that this 'algorithm' then has been updated/fixed/implemented properly in the Desire GPU driver.
To everyone - I think what we need to understand here is that the issue exists, and it's main cause is directly related to the GPU driver. Yes, there are one or two things that possibly ease the issue (saturation fix and rgb565 flag in build.prop), but the proper, native fix lies somewhere in the Desire GPU driver. Now, seeing as I am not a kernel dev, I cannot pinpoint the cause/solution.
So, the main point that this thread should express is that the issue can be fixed, by applying the Desire 2.6.35 port. However what we are trying to achieve is using this port without breaking video/camera/camcorder compatibility.
MrP.
Click to expand...
Click to collapse
Might just be a simple setting. Let us remember that there are no HTC drivers for the HD2 in particular. We got everything from the Desire and probably the Nexus.
Now, those two devices are 24bit color from ground 0, and the driver problably belives that we have a 24bit capable screen. Warren's driver must have something in it, that makes it behave nicely with RGB565 instead of RGB888.
I have a questions. The Desire came out in two versions, Amoled and LCD. How does the android finds out which type of screen is being used? Or is it transparent to the OS?

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

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.

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

For any issues you can use the following bug tracker.
http://bugs.andromadus.com/projects/vision-nightly
In the issue please include what version of the test build u are on and if another build gets released please flash and please update the issue saying the bug is still happening on 45 or whatever number.

Howdy.
Sent from my Galaxy Nexus using Tapatalk 2

Just d'loaded. Ill note down the major issues if there are any different from stable B2.
Sent from my HTC Vision using xda premium

cjward23 said:
Howdy.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
YOU!!!!!!!!!!! WHY?!!!!
darkspadez said:
For any issues you can use the following bug tracker.
http://bugs.andromadus.com/projects/vision-nightly
In the issue please include what version of the test build u are on and if another build gets released please flash and please update the issue saying the bug is still happening on 45 or whatever number.
Click to expand...
Click to collapse
Will this cover erectile dysfunction? That kid over there said he never said it had happened before he flashed flinny44..

Because.
Thanks to the andromadus devs for the opportunity!
Sent from my DZ.

So I am assuming there will be no changelog?

I found that this rom is not deodexed ?

shellin said:
So I am assuming there will be no changelog?
Click to expand...
Click to collapse
Correct and also note this comes without warranty. Flinny could post a rom that doesn't even boot. Its basically nightly build of our repos so you can use them without having to build.

So, when's the next one due? Where's the changelog? What's adb? Why would you want a lolcat? ... *snicker*
Just kidding around for a second. I'll flash, follow the updates and post if I find anything suspicious.
darkspadez said:
Correct and also note this comes without warranty. Flinny could post a rom that doesn't even boot. Its basically nightly build of our repos so you can use them without having to build.
Click to expand...
Click to collapse
Great, thanks!
Sent from my T-Mobile G2 using Tapatalk 2

Sup Flinny! /2nd page already
Sent from my HTC Vision using XDA

Unofficial changelog for Flinny44 (from beta2):
Fixed issue where power saving does not work on certain APs under certain conditions causing wifi to drop during sleep without notice. (credit to nyt)
Fixed Keyboard brightness backlight for hidden keyboard
Fixed Camera focus button
Added Statusbar IME Switcher toggle
Fixed speakerphone/on hold/mute issues
Optimized compiler CFLAGS
Russian keyboard fix
Fixed bootanimation resolution
Added camera button play/pause for music when screen is off
Merged in changes for webkit and updated to newest CM repos.
Merged in a whole bunch of camera HAL / qcom changes
Added expanded volume overlay
Those are just things I've been keeping track of, Flinny can expand on the things he's merged in himself

blk_jack said:
Unofficial changelog for Flinny44 (from beta2):
Fixed issue where power saving does not work on certain APs under certain conditions causing wifi to drop during sleep without notice. (credit to nyt)
Fixed Keyboard brightness backlight for hidden keyboard
Fixed Camera focus button
Added Statusbar IME Switcher toggle
Fixed speakerphone/on hold/mute issues
Optimized compiler CFLAGS
Russian keyboard fix
Fixed bootanimation resolution
Added camera button play/pause for music when screen is off
Merged in changes for webkit and updated to newest CM repos.
Merged in a whole bunch of camera HAL / qcom changes
Those are just things I've been keeping track of, Flinny can expand on the things he's merged in himself
Click to expand...
Click to collapse
Thanks for that
Some of those look intresting but sadly I can't be messing around with nightlies..

Posting to feel special
-Nipqer

I havent flashed a rom in a while. Its about that time me thinks, I will let you know if I come across any problems.

Nipqer said:
Posting to feel special
-Nipqer
Click to expand...
Click to collapse
You don't need to post to feel special. Those matter already know how 'special' you are Nipqer
Sent from my Galaxy Nexus using Tapatalk 2

nice

For those that haven't heard already, HTC has released the ICS kernels sources including for the Desire HD!
http://www.htcdev.com/devcenter/downloads

HD are 2.6.35 sources...
tarroyo said:
For those that haven't heard already, HTC has released the ICS kernels sources including for the Desire HD!
http://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse

[ROM][DISCONTINIUED FOR VIVOW] ~~ SenseMOD FlashONE v2.2 PUBLIC BETA~~ [HTC Kernel 3]

DROPPED SUPPORT FOR VIVOW.
As we do not feel comfortable anymore in these forums, we will definately drop support for the Incredible 2.
We were wanting to give you more then a fully working one V port (such as a full sense 4 port), but since we have the feeling the community doesnt want us here, we will leave Inc2 forums.
Sirencely,
djpbx, Floatshow, htc-phones.

DROPPED SUPPORT FOR VIVOW.
As we do not feel comfortable anymore in these forums, we will definately drop support for the Incredible 2.
We were wanting to give you more then a fully working one V port (such as a full sense 4 port), but since we have the feeling the community doesnt want us here, we will leave Inc2 forums.
Sirencely,
djpbx, Floatshow, htc-phones.

Woot first
Sent from my Incredible 2 using xda premium

Thanks, downloading now. Will the tools from the One X leedroid tweaks work?

72ls1 said:
Thanks, downloading now. Will the tools from the One X leedroid tweaks work?
Click to expand...
Click to collapse
Leedroid tweaks need to be ported, but they belong to full sense 4 so actually no use on One V rom

Downloading now. I expect the main bug to be the camera but will report any I find

Added some screenshots

i flashed it to see whats what...heres some observations:
no english us as option (english gb is there though)
no data, nor recognizing vzw as carrier
wifi is borked
no soft key lights
menu button doesnt function (keys werent remapped like in newer 1.56 ports)

nitsuj17 said:
i flashed it to see whats what...heres some observations:
no english us as option (english gb is there though)
no data, nor recognizing vzw as carrier
wifi is borked
no soft key lights
menu button doesnt function (keys werent remapped like in newer 1.56 ports)
Click to expand...
Click to collapse
Thanks for your report. i'm going to take a look at them
I think English US not appearing is normal, since it has been built from the EU RUU
Just two questions:
- Going to check about the data. is Verizon using CDMA or GSM network technology?
- What do you mean with borked?

djpbx said:
Thanks for your report. i'm going to take a look at them
I think English US not appearing is normal, since it has been built from the EU RUU
Just two questions:
- Going to check about the data. is Verizon using CDMA or GSM network technology?
- What do you mean with borked?
Click to expand...
Click to collapse
verizon uses cdma (although this is a world phone too), you ll need to update the build.prop's data path accordingly in addition to the correct reference-ril.so lib
wifi wont properly connect...since i was also using the virtuous prima kernel in my latest sense 4 port i ran into the same issues....my semi conclusion is that they included the wrong bcm module w/ the rom zip
english us can be added easily by modding the default.xml

nitsuj17 said:
verizon uses cdma (although this is a world phone too), you ll need to update the build.prop's data path accordingly in addition to the correct reference-ril.so lib
wifi wont properly connect...since i was also uses the virtuous prima kernel in my latest sense 4 port i ran into the same issues....my semi conclusion is that they included the wrong bcm module w/ the rom zip
english us can be added easily by modding the default.xml
Click to expand...
Click to collapse
Thanks. What kernel would you recommend to give the Inc2? CM9 kernels also work on the Desire S so it might work too on the Inc2.

djpbx said:
Thanks. What kernel would you recommend to give the Inc2? CM9 kernels also work on the Desire S so it might work too on the Inc2.
Click to expand...
Click to collapse
the cm9 or tiamat kernel is ok, but its not nearly as stable as the virtuous one unfortunately (i used cm9 in first 4 versions of mine) which lead to some sod issues, overheating, and freezes
virtuous kernel source isn't the easiest to to build from the way its set up on github, and i asked corcor to rebuild the kernel for me to get the proper modules, but it wouldnt boot...ill ask cjward or one of the guys for help with it next week if i remember to

Hotfix 1 attatched to this post.
Install this right after a fresh flash.
It has been tested and it works. It will be included in the next version.

djpbx said:
Hotfix 1 attatched to this post.
Install this right after a fresh flash.
Please report if it makes the cellular and data work.
if it works it will be included in the next version of SenseMOD FlashONE
Click to expand...
Click to collapse
I just tested this out for you and its working

gaby04 said:
I just tested this out for you and its working
Click to expand...
Click to collapse
I'm out of thanks for today so i'll just thank you the hated way
thanks mate! the fix will be in the new version.

Hey man digging the rom very nice work I'd stay but I need WiFi

Update time!
Bugs fixed:
- removed USB debugging notification from every device: (build.prop persist.adb.notify=0)
- Incredible 2: fixed no recognizing Verizon (WORKING)
- Fixed Inspire 4G Mic and sound
- Fixed installation of 3D rosie.
- Added Bluetooth Audio mod for SAGA
- Added Bluetooth Audio mod for ACE
- Added manual device selection in AROMA.
- Fixed home button problem for Desire S
- Fixed menu button problem for ALL devices.
- Desire Z bootfix
DOWNLOAD: http://sb-boardteam.nl/sensemod-flashone/SenseMOD_FlashONE_v1.2.zip

djpbx said:
Update time!
Bugs fixed:
- removed USB debugging notification from every device: (build.prop persist.adb.notify=0)
- Incredible 2: fixed no recognizing Verizon (WORKING)
- Fixed Inspire 4G Mic and sound
- Fixed installation of 3D rosie.
- Added Bluetooth Audio mod for SAGA
- Added Bluetooth Audio mod for ACE
- Added manual device selection in AROMA.
- Fixed home button problem for Desire S
- Fixed menu button problem for ALL devices.
- Desire Z bootfix
DOWNLOAD: http://sb-boardteam.nl/sensemod-flashone/SenseMOD_FlashONE_v1.2.zip
Click to expand...
Click to collapse
Damn. Just got done downloading the first one.. lol.
Sent from my Incredible 2 using xda premium

djpbx said:
Bugs:
WiFi tethering
Camera
Games like Temple Run
Click to expand...
Click to collapse
Are those the ONLY known bugs? (I know this sounds newbie but want to make doubly sure!)
I am trying this out today! Wanted to try some sense 3.5/4.0 like OpenSense4 but it has bucket loads of bugs. So I am very surprised that this is as good as AOKP, bug list wise... Thank you djpbx and Floatshow!!!
P.S: More people thanked post #2 than #1. Come on, people! Give the OP some love.. He worked on it too... (I expect equal # of thanks on both)

litetaker said:
Are those the ONLY known bugs? (I know this sounds newbie but want to make doubly sure!)
I am trying this out today! Wanted to try some sense 3.5/4.0 like OpenSense4 but it has bucket loads of bugs. So I am very surprised that this is as good as AOKP, bug list wise... Thank you djpbx and Floatshow!!!
P.S: More people thanked post #2 than #1. Come on, people! Give the OP some love.. He worked on it too... (I expect equal # of thanks on both)
Click to expand...
Click to collapse
At best this is as functional.as opensense
But it has all the same bugs (though pre 0.5 os has working Wi-Fi)
Just sharing my observations

[ROM][23-03-14][Flinny] Vision - Andromadus - CM11.0 [alpha5]

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.
Checkout http://andromadus.flinny.org for links/files/changelog's
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.

Current Build Changelog
Build 16
Rom
Should have fixed the zoom problem with browser some were having with large fingers/thumb presses.
Notification LED should be green again.
Disabled sliding picture animation when taking a picture for now.
Saga, rotation issue should be resolved again.
Everything else synced with CM.
Kernel
Patched to 3.0.66
Saga - S2W should be disabled by default on a clean install
Increased PMEM allocation on both SAGA and VISION as we were having out of PMEM issues sometimes when coming out of standby.
MDDI - sorry still need an updated kernel for you.
Checkout http://andromadus.flinny.org for previous changelogs

Looking forward to this

Flinny said:
Files still uploading...
Click to expand...
Click to collapse
Could you please reply back when you've made the files available? Thanks!

rubin110 said:
Could you please reply back when you've made the files available? Thanks!
Click to expand...
Click to collapse
Uploaded
Sent from my Nexus 7 using Tapatalk 2

rubin110 said:
Could you please reply back when you've made the files available? Thanks!
Click to expand...
Click to collapse
http://andromadus.codefi.re/ and sort by 'Date'

Wooo! Trying this
Can I flash directly over 4.1.2 build 129?
or would you recommend a clean wipe : ]

or check the link to the new website on the OP
I would suggest doing a wipe as Gapps etc are all different... if you do try an upgrade then I would suggest backing up... flashing rom/new gapps/wipe cache/dalvik at least.. then most likely finding it didn't work and having to wipe anyway
Nick.

Thx so much. I will try it.

Just tried installing directly over 129, rotation broke so I'm going to try from a full wipe. ( everything else is hunky dory really, although took a quite some time for the phone to calm down and get back to it's usual pace)
By the by, I notice the kill all icon from 129 is gone, is there anyway I can add that myself rather than wait for an update? ( as it's super handy!)
Thanks again flinny and Andromadus folks! My phone is even more woosh woosh and fancy than ever before.

Great job Flinny! You have done quite a lot.
just a question... what is the difference between the cm10.1 and the aosp 4.2? Is cm10.1 the beta release? or are they new test builds based off of cm and not just aosp?

jspina said:
Great job Flinny! You have done quite a lot.
just a question... what is the difference between the cm10.1 and the aosp 4.2? Is cm10.1 the beta release? or are they new test builds based off of cm and not just aosp?
Click to expand...
Click to collapse
ASOP is stock Android, CM10.1 is with Cyanogenmod and Andromadus tweaks. ( I.E more things to mess about with! yay)
Okay got all my apps reinstalled after a fresh wipe and this Rom is daaamn smooth.
All the default apps run without a hitch, and none of my extra apps have caused any issues either ( got 50 installed)
Just needs lock screen short cut tweaks, statusbar/notifcation tray colour/alpha picker and a kill all apps button and this would be puurrfect.
More than happy to use it as is though, runs great.

Pantherx12 said:
ASOP is stock Android, CM10.1 is with Cyanogenmod and Andromadus tweaks. ( I.E more things to mess about with! yay)
Okay got all my apps reinstalled after a fresh wipe and this Rom is daaamn smooth.
All the default apps run without a hitch, and none of my extra apps have caused any issues either ( got 50 installed)
Just needs lock screen short cut tweaks, statusbar/notifcation tray colour/alpha picker and a kill all apps button and this would be puurrfect.
More than happy to use it as is though, runs great.
Click to expand...
Click to collapse
Thanks. I know what the differences between the two are. I was just wondering if thats all that differentiated the two. And after looking at the titles its obvious that they are.

haha took me a few mins to realise this is the new cm 10.1 anyways good work as usual flinny downloading now
Sent from my HTC Vision using xda app-developers app

Am I being stupid or is there no developer menu item under settings? Additionally missing is the glorious Performance menu item too.
Also having some troubles connecting to wifi access points after the initial setup.

Flinny please make name theme more easy. It difficult to distinguish
Sent from my HTC Desire Z using xda app-developers app

rubin110 said:
Am I being stupid or is there no developer menu item under settings? Additionally missing is the glorious Performance menu item too.
Also having some troubles connecting to wifi access points after the initial setup.
Click to expand...
Click to collapse
Its missing in the settings menu for me also. And wifi works but sometimes it doesn't connect, everything else seems to work
Sent from my HTC Vision using xda app-developers app

Go to about phone and tap build number until it tells you that your now a developer....
Sent from my Nexus 7 using Tapatalk 2

Thanks flinny~~
It's so wonderful~
But I can't find the CM's function, like "Performance",
If the CM 10.1 have some function not implement??

Some features have not yet been ported to 10.1 by the CM team yet. But performance and developer are hidden in all 4.2 builds until you do the tap build number thing