[ROM][09/12/11] Virtuous Unity Sense 3.0 based on Pyramid [2.37.0]

Search This thread

knaries2000

Senior Member
Apr 13, 2009
172
12
If what you said is true about the virtuous overlock app, the battery drain is not from the app that just changes the files, but from the disabling of the overclock daemon with setcpu being installed. I haven't read about battery drain from the vu overclock but it's worth testing it out.

That's a good point - but who knows? I'm not saying I know with 100% certainty that that's what caused the battery drain. I'm just saying that's what the DEVS said, and that since they removed it my battery life has doubled. The difference in battery life could be attributable to something else, but going just by the information available to me, it seems to have been the OC app.
 

Hindle1225

Senior Member
Jun 18, 2010
757
169
I found that unusual that an app that just changes 6 text files would be the cause of our battery drain woes.

Don't think that way.... Its not the text in any file that causes issues, its the code the text represents (what its it executing?)

To any programmer 1 number means a world of difference.

Sent from my HTC Glacier using xda premium
 

Elloco305

Senior Member
May 28, 2008
2,522
500
Miami
Guys I don't think you guys are either wiping correctly or letting the ROM settle in correctly.

My CRT animation works perfect,
My GPS locks on in seconds,
And i just recorded a 25 second MMS video and sent it through MMS.

Remember to let the phone settle 10 minutes or so, then reboot and let it settle for another 5 minutes to be completely sure.

Sent from my HTC Glacier using XDA App
 

manleyaudio

Senior Member
Oct 29, 2010
239
95
Seattle
You're signed into HTC Sense. That's what's doing it. It's constantly syncing. Try signing out, or changing the sync settings.

Sent from my HTC Glacier using XDA App

Thanks for the advice, my battery seems a lot better now!
Do you know why cell standby would be using a lot of battery? I tried searching but found no results.
 

marseillesw

Senior Member
Feb 15, 2011
1,453
344
Everywhere, USA
Guys I don't think you guys are either wiping correctly or letting the ROM settle in correctly.

My CRT animation works perfect,
My GPS locks on in seconds,
And i just recorded a 25 second MMS video and sent it through MMS.

Remember to let the phone settle 10 minutes or so, then reboot and let it settle for another 5 minutes to be completely sure.

Sent from my HTC Glacier using XDA App

+ 1on all points


Sent from my HTC Glacier using XDA Premium App
 

ethutch

Senior Member
Jul 8, 2008
127
15
New Bluetooth Peripheral Device

I have a problem trying to connect 2.35 to my PC via bluetooth.

I had gone through the considerable pain before of getting the "Windows Mobile-based Device Support" installed and with the stock TMOB ROM it all worked perfectly.

Now in Virtuous I believe it finds those previous BT devices OK (not certain of this but it looks pretty OK). However, the Virtuous build (Sense 3.0 I assume) adds at least one new services under Bluetooth Advanced Settings. I think FTP was there before, but I am sure Messaging Services (Email and SMS) were not.

HTC supplied an HTCDriver.exe on the root of the SD card that had the USB drivers for ADB (of course you know that). I believe if we could find an original HTC file like that it would have the missing BT device drivers in it. But I haven't been able to find such a beast.

As an aside when I turn on or off these BT services (FTP / Messaging) Sense seems to crash fairly regularly. (Virtuous logo restart not MyTouch logo)

This isn't the biggest deal at all, but I do sometimes use bluetooth for a few quick file transfers. Any thoughts appreciated.


Edit: Some info I've found implies, with more confidence than it should, that all I need do is look up the VENdor id and DEVice id in the online database and download the requisite drivers. But the Bluetooth info registered in Device Manager does not have any VEN or DEV tags.
 
Last edited:

BRKotucs

Senior Member
Feb 3, 2011
5,896
13,951
Houston, Tx
Last edited:

gjcamp

Senior Member
Jan 26, 2007
130
146
T-Mobile Caller Name ID

Anyone try the T-Mobile ID from the Doubleshot ROM? I've had no luck.

The APK is called "ECID.APK" I have had no luck installing this either. This alone will not enable caller ID. This will allow you to get the "City ID" Feature that you need to subscribe. If you have City ID you will also get the city that the incoming caller's number is associated.

By no means am I a ROM cooker and ALL Props to those who are. I have spent many hours reading and working towards figuring this out.

From what I have figured out installing the DoubleShot ROM is that the Caller Name ID (Caller NAme Presentation) CNAP function is embedded in the Phone.APK and the Android system itself which has dependencies that I have not totally figured out yet. Caller Name ID is invoked when you get any landline or Mobile caller NOT in your contacts already. (That is if their carrier or the caller provides outgoing CLI and CNAM information.) We all have that option.

The incoming call screen (Locked or Unlocked) is part of the functionality so when this works CityID, CNAP, CLI (CID phone number) will display on the incoming caller screens.

There is also a "Save to Contacts" that is enabled when this fully works that allows you to use the City ID, CNAP, and CLI information and save it to your contacts.

On the Virtuous (Beta 2.33) I have been able to get Caller Name ID on the unlocked screen to work but I broke ALL my data connections.

Ultimately, I would like to have the Caller Name ID, City ID working on the Virtuous ROM and have it ready as a MOD so when I go to the next version of Virtuous I can keep this functionality.

Keep in mind there are many applications for Caller Name ID that will simply go and lookup the number from "WhitePages.com" etc... This is not how CNAP works on T-Mobile anymore. T-Mobile is now sending this information within the call page messaging similar to how the phone company at home is doing. (With a subscription)

If anyone is willing to help me I would be glad to share what I have already tried and learned.
 
  • Like
Reactions: RangerLG

Elloco305

Senior Member
May 28, 2008
2,522
500
Miami
Is it running well for you? I'm interested in all the extra settings.

So I have it right wipe data and davlik then flash?
Thank you so much guys! This is one of the best forum groups I've been in, thanks again for the patience.

Sent from my HTC Glacier using XDA Premium App

It works well.
The CRT options didn't work for anyone plus me.
But aside all works.

I removed it by wiping cache and dalvik and flashing the ROM again.

I hated the ginger bread battery icon LOL

Sent from my HTC Glacier using XDA App
 

TheNarrowGate

Senior Member
Feb 12, 2011
85
7
Earth
Thanks for the advice, my battery seems a lot better now!
Do you know why cell standby would be using a lot of battery? I tried searching but found no results.

No problem! Glad it helped. I was worried my response got lost in the fray.

As far as cell standby, mine is 8% today on 13.5 hrs since unplug


Sent from my HTC Glacier using XDA App
 

manleyaudio

Senior Member
Oct 29, 2010
239
95
Seattle
No problem! Glad it helped. I was worried my response got lost in the fray.

As far as cell standby, mine is 8% today on 13.5 hrs since unplug


Sent from my HTC Glacier using XDA App

I had to let it settle in, apologies for the delayed response.

Good to know about the standby percent.

Cheers.


Sent from my HTC Glacier using XDA App
 

Top Liked Posts

  • There are no posts matching your filters.
  • 141
    virtuousunity-800.png


    Virtuous Unity is the first custom Sense 3.0 ROM, scaled for WVGA screens, to be based on an official shipping release from HTC (1.45.401.2).
    The entire ROM is brand new, taking no application or framework components from any prior Sense 3 releases.


    Unity is the result of a collaborative, team effort by the following developers:
    Screenshots

    unity1.png
    unity2.png
    unity3.png


    Features

    • Based on the official Sensation shipping ROM (1.45.401.2).
    • Ported for full functionality on each supported devices. Additional device support is being added regularly.
    • Resized for WVGA (800x480) displays, using a purpose built tool to modify HTC's proprietary m10 binaries, developed by Flemmard and Diamondback.
    • Heavily optimized for fluid performance and usability.
    • Overclocked kernels with numerous additional kernel modules.
    • Built-in screen state frequency scaling (1.2Ghz-245MHz/ondemand screen-on, 806Mhz-245Mz/conservative screen-off), via custom built Virtuous_OC C daemon.
    • Trackpad wake support (DesireZ/G2 and MT4G only).
    • WiFi calling (T-Mobile USA only).
    • Fully functional device hardware, including wifi, bluetooth, camera, camcorder, etc.
    • Market-sourced applications (Gmail, Maps, Voice, etc) automatically installed on first boot into /data/app for easy removal.
    • Bloatware and unnecessary applications removed.

    Supported Devices
    Porting Information and Credits

    Virtuous Unity, or any components therein, may not be ported to other devices without explicit email approval from the development team. We will be approving ports, presuming the develop of a given port is ready and willing to follow the same revision control and release processes currently employed existing devices.

    Important Notes

    • If you are experiencing random freezes and/or reboots, this is likely due to your device being incapable of handling our overclocking defaults. Download and apply this flashable patch, which will reduce the maximum CPU frequency to 1Ghz and likely eliminate this issue.
    • You must complete a full wipe prior to installing this ROM the first time. We also recommend wiping between upgrades, but you are welcome to try upgrading without a wipe. However, no support will be provided if you file a bug without having wiped prior to submission.
    Bugs and Errors

    To ease the process of reporting bugs to the team, we made a public bugtracker where you can report the bugs you found. Please make sure you read all the existing entries there to avoid doubling the errors.

    The bugtracker is located here.


    Device specific information

    BETA 2.33.0 based off the EU Pyramid 1.45.401.2, Android 2.3.4.
    Fixed updater for those who have downloaded 2.33.0 with the borked install script.

    Download :: Changelog :: More Information
    (Official Website of Virtuous ROM)​
    33
    Install instructions:
    1. Make a full wipe
    2. Flash ROM
    3. Reboot


    Recommended radio:
    Official Radio from T-Mobile myTouch 4G Gingerbread 2.3.4


    Addons for 1.26.0 and 1.27.0



    A few notes
    • To get support from the team a FULL wipe is required. Without a wipe we can't help you if you have problems
    • Some changes REALLY need a full wipe to fully work, you can try a non wipe install, but do NOT report any bugs until you wiped.
    • G2 users must change to the DZ hboot
    25
    Introduction to the new Overclocking Daemon

    This ROM features a completely new way of Overclocking and managing screen states.

    The History
    But before explaining it further, let's talk about previous solutions.
    There are several different approaches to achieve "screen-state-scaling".
    That means basically that the governor changes if you turn the screen off and changes back to normal when turning the screen on.

    This is mainly used to restrict the amount of CPU usage (the frequency in fact) during screen off. This can lead to a major battery life increase.

    The solutions so far were:

    • Apps like SetCPU, which change automatically the governor based on profiles
    • Integrated solutions in the governor itself

    Both these solutions have major problems.

    The one with a tuner app is always a little laggy right after turning on the screen because SetCPU (or any other CPU tuner) needs some time to change the governors (up to 7 seconds). This leads mostly to major lag in the lockscreen.

    The second solution is the smartass governor. It has already a screen-state-scaling included, so it reduces the frequency when the screen turn off.
    This could be a really nice solution but it has some problems too.
    Smartass most of the time is not really stable and has problems with its frequency scaling.

    State-of-the-art-solution
    So we (more precisely rmk40) thought of a better solution.
    He wrote a native C Daemon which changes the governors instantly without any lag.

    This leads to major performance improvements right after turning on the screen and in the lockscreen.

    But at the moment this solution is a little bit harder to configure. We are planing to make a GUI for this, so you get the same comfort as using SetCPU.
    Nevertheless you can even now adjust the daemon to your needs.

    Be aware that the daemon only works if all CPU tuner apps are deinstalled. Otherwise it deactivates itself.

    How to adjust the daemon

    The daemon is configured with 6 files in the folder /system/etc/virtuous_oc/.
    There are 3 files for the wake state and 3 for the sleep state. For each state one file for the governor, one for the minimal frequency and one for the maximal frequency.

    You can easily edit these files eg. with RootExplorer or any other app which can edit system files. So you can adjust the frequencies and the governor for each state just like with SetCPU.

    In order to get the available frequencies for the current kernel, just open your favorite terminal app and type
    cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
    You could also use adb shell to show the frequencies on your computer.

    To get the available govenors use a similar approach:
    cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors

    Please make sure, you are entering the right values in the daemon's config files.
    18
    Changelog

    Our changelog lives here.


    Supported devices

    • Desire HD (Ace)
    • Desire Z (Vision)
    • Desire S (Saga)
    • Incredible S (Vivo)
    • Inspire 4G
    • T-Mobile MT4G (Glacier)
    12
    For those with wifi calling issues, try this pushing this to /system/app and rebooting.