yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Android Development] Authorita:
Does anybody else have problems with the battery meter? Mine doesn't like to charge higher than 92%. I've replaced the battery even. Is there some way to change the "full level" to make it scale properly?
[G2 and Desire Z Android Development] davidrol:
There a few settings needed to smooth things out:

in System settings/Developer options/

1. Disable HW overlays selected

2. Force GPU rendering selected

3. Don't keep activies selected and

4. Background process limit should be set to At most 2 processes. ( Must be reset after every boot)

in System settings Processor/

1. CPU governor INTERACTIVE

2. Minimum CPU frequency 768

3. Maximum CPU frequency 1401

You could play with the CPU settings to find the best performance/battery life that suits your needs.

in System settings/Memory management/

1. zRam should be disabled

2. Allow purging of assets selected

3. Kernel samepage merging selected

I think thats all...
[G2 and Desire Z Android Development] 00sand00:
successfully installed AOSP2.4[5] and used it for a whole day... It frose at some point while I was using it and tha phone got bricked (I suppose that radio flashing in order to get sim to work got him)

Now I'm running cyanogenmod 7 from SD card and everything works ok but would really like to install AOSPv5 (and other builds) on the phone since it's already bricked.

Any help would be very welcomed
[G2 and Desire Z Android Development] Authorita:
Ok, there is definitely something wrong with the battery reading.

One moment its reading 4012 mv, 90%, next moment its reading 4039 mv, 84%. This is wrong, its jumping all over the place.

The 2.6 kernels worked correctly for voltage/percentage. The switch up to 3.0 changed something in this regard.

Interesting....

CONFIG_BATTERY_DS2746=y for the 2.6 kernel, UNSET for 3.0.

Some of those ds2764 files seem to be related to the relationship between voltage and "full level".
[G2 and Desire Z Android Development] Zelych:
For some time I used the build 129 (clean install) and the battery life was the same as other ROM, then I tried 4.2 and after restoring build 129 battery disappearing quickly and the phone heats up and sometimes even when I have it in a case.

Odesláno z mého HTC Vision
[G2 and Desire Z Android Development] davidrol:
Never had that problem. Which radio and how did you flash?
[G2 and Desire Z Android Development] Flinny:
Interesting... Wonder if there are different batteries with different chips in them... I don't seem to have any problems getting readings out of mine.

I can build you a boot.img with a kernel in with this enabled if you want to test it?

Nick.
[G2 and Desire Z Android Development] Vauvenal7:
*push*

Flinny?^^

Greets Vauvenal7

Sent from my HTC Vision
[G2 and Desire Z Android Development] Authorita:
I'd appreciate it if you could. I've been trying to compile it myself, but having no luck making it boot...

I'm following these steps;

- cloning https://github.com/Andromadus/htc7x30-3.0.git

- modify vision_andromadus_defconfig

$ make ARCH=arm CROSS_COMPILE=arm-linux-gnu- vision_andromadus_defconfig

$ make ARCH=arm CROSS_COMPILE=arm-linux-gnu- -j13

..

$ split_bootimg.pl boot.img (from build 5)

$ mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel ../new/zImage --ramdisk ./boot.img-ramdisk.gz -o newboot.img

$ fastboot boot newboot.img

Phone then craps out at the HTC logo.

Any ideas?

I'm thinking that it might be my compiler. New to cross-compiling.

Edit: DUH, it apparently IS my compiler... which is arm-elf, not arm-eabi.

Edit2: So apparently it does the same damned thing even with the *right* compiler from https://android.googlesource.com/platform/prebuilt

Edit3: AH HA! --base 0x04000000 !!!! My kernel now boots! :D

I'm going to try this config change for a couple of days and see how it goes.

Edit 4: Seems different already. 95% at 4046 mv. I NEVER saw over 92% with the last kernel.
[G2 and Desire Z Android Development] ivomitov:
Is there a way to disable the dynamic range compression? It seems built in 4.2 and the music sounds awful, always changing the volume up and down, it's not like that on ICS builds.
[G2 and Desire Z Android Development] natabbotts:
It isn't possible for a ROM to kill your battery, as far as I'm aware.
[G2 and Desire Z Android Development] Authorita:
That isn't necessarily the case. Read the last few posts that I've made. These drivers that I'm working with seem to have an effect on the relationship between voltage, power level (percentage reading), charging, type of charging (rate), etc. I believe that this minor oversight in the kernel config for 3.0 kernels on Vision DOES have the potential to cause damage to batteries.

My preliminary findings with the DS2746 battery config enabled, is that for the FIRST TIME EVER (on 3.0 kernel), my phone correctly charged to 100%, and is correctly switching between charging modes. However, I only installed this kernel late last night and am still testing.

And I'm sure that this must be my imagination, but with this kernel, the phone feels like its about 100 times faster.... :eek:

-- I wonder if it is possible that the kernel was choking on the battery driver???

Probably my imagination.
[G2 and Desire Z Android Development] Bapf:
You have to consider that the 4.1 build is CM, the 4.2 is AOSP. Since CM has the DSP Manager built in and this schould still be the case for CM10.1/4.2 once it hits the repos there i think there is no point in bugfixing sound issues at the moment. (At least not to do too much work in this direction.)
[G2 and Desire Z Android Development] Authorita:
Ok, now here is something I wasn't expecting to see from this; for giggles, I opened up cpuspy. I'm reading 10 hours of deep sleep with a total state time of less than 11 hours. The thing was in deep sleep while on the charger all night! :good:

Edit: I've attached a boot.img with my modified kernel and associated modules in case anybody is interested in testing it. The boot image is based on AOSP4.2.1 build 5, the kernel is from Andromadus GIT as of yesterday, the ONLY modification is that I set the config parameter CONFIG_BATTERY_DS2746=y (from previously unset = not built).

EDIT: Don't waste your time with this if you're using 4.1 build 130+ or 4.2 build 6+, since it is now incorporated from those builds.
[G2 and Desire Z Android Development] tv2177:
does any one of auto-rotate problem? I am currently on build 128 and has been bothered by no auto-rotate since build 126, can anyone help? I have always checked auto-rotate undre settings.
[G2 and Desire Z Android Development] Skarj:
Guys, since i updated to build 5 with new gapps, i lost Picasa sync in gallery. Is It normal ?
[G2 and Desire Z Android Development] pauldacheez:
If it's the same problem I had, try doing a nandroid backup, flashing a Sense ROM, and restoring from your backup. If not, well, uh... wipe or somethin'.
[G2 and Desire Z Android Development] Bapf:
For me, wiping /system before updating did resolve this.
[G2 and Desire Z Android Development] Pantherx12:
Would this be compatible with 129 as well?

( if it is necessary for 129)
[G2 and Desire Z Android Development] Authorita:
Flinny: though I'm not done testing this just yet (battery is still at 60% from overnight charge), I can say for FACT that building in the DS2746 makes a BIG difference in the battery reporting and how it charges. The battery graph is smooth and linear from 100% down to current 60%. No weird notches, no jumps upward. I wiped the battery stats last night before booting it up, so it isn't contaminated with old data.

Now about the structure of the DS2746 files; they do NOT represent a driver that gets loaded *if* a DS2746 happens to be detected. It is a declaration that a DS2746 *is present* and to treat the battery as such. Without this, its going to take its best crappy guess about the battery. It will report *something*, but not always right and not always consistent. It basically fine tunes the battery handling.

I think you should enable it for all kernel builds. It will make a lot of people happy.

---------- Post added at 02:34 PM ---------- Previous post was at 02:32 PM ----------

AFAIK, all builds with 3.0 kernel (which includes 129).

The kernel itself should be approximately the same. I don't know about the ramdisk though. You can try those I packaged, if they don't work, take the boot.img from 129 and repack it with the zImage from my boot.img.

Edit: You can TRY it out without writing it to your phone. Boot the phone into fastboot mode, then run "fastboot boot boot.img" -- it will load the boot.img and run on that without writing it to flash. This requires engineering bootloader of course.
[G2 and Desire Z Android Development] Flinny:
be patient... updating 6 threads :D
[G2 and Desire Z Android Development] Pantherx12:
Oooh I'm excited!
[G2 and Desire Z Android Development] Authorita:
So looks like 4.1 build 130 and 4.2 build 6 are up...

(if you know how to find them...)

And with the battery patch :D

https://github.com/Andromadus/htc7x30-3.0/commit/cf20f6bc08f73de223766de74b3ed299e48429d2
[G2 and Desire Z Android Development] Flinny:
The link to the new website in the op?:)
[G2 and Desire Z Android Development] Authorita:
Seems that somebody's using a fancy new subdomain.
[G2 and Desire Z Android Development] blackknightavalon:
Yup. Running a Nandroid of 129 now.
[G2 and Desire Z Android Development] farris:
AOSP keyboard FCs in build 130... can anyone verify this?
[G2 and Desire Z Android Development] LexxLol:
Yes, same here.

Full wiped, clean install.

Deinstalled it, flashed gnufabios 4.2 keyboard, works like charm.
[G2 and Desire Z Android Development] jspina:
I had this happen but only because I flashed the 4.2 gapps by mistake
[G2 and Desire Z Android Development] Authorita:
Wild. In case anybody is interested, I'm testing out different USB chargers. I have a total of 5 different USB chargers. I've tested out 3 of them so far. The HTC charger that the phone came with, one that says "made in china" (china black) -- which I think may be from a RIM phone, one "Shenzhen Huajin Electronics Co Ltd" (china white). Remaining are the Nook ST and the Nook Tab chargers, which I will get to when I can find them.

Of the three I've tested so far, the HTC and the "china white" charger allow the phone to go into deep sleep while charging. The "china black" does not.

Now obviously, a deep sleep will allow you to charge somewhat faster and more consistently. I suggest testing your chargers to verify deep sleep.
[G2 and Desire Z Android Development] davidrol:
Aren't the gapps posted the same? If so, therein lies the problem.
[G2 and Desire Z Android Development] NeverGone\RU:
Could anyone explain what is this for?

@Flinny: what about removing this "SpeechRecorder.apk" from builds? It's absolutely pointless IMO.
[G2 and Desire Z Android Development] 00sand00:
I flashed 26.10.51.26 and it worked ok for while the phone was working.
[G2 and Desire Z Android Development] Sefy:
I've recently purchased from eBay a 3$ charger which appears to be Nokia's and i compared it to my HTC Charger which came with the phone and saw the HTC has 1000mA and the Nokia had 1200mA, and with the Nokia i charge in about 3 to 4 hours from 0 to full! using computer or other regular chargers (most are 500mA) it takes me over 6 hours to charge the phone.
[G2 and Desire Z Android Development] davidrol:
Shouldn't you be using the latest? 12.62.60.27_26.13.04.19
[G2 and Desire Z Android Development] sp1980:
Cell Broadcast

Is it possible to install cell broadcast for this rom? I tried install this CellBroadcastReceiver.apk to /system/app, but I didn't succeed. Is there someone who has installed it and working on this rom?
[G2 and Desire Z Android Development] davidrol:
Yes. Keyboard on 130 FCs. Greyed-out in settings. Installed 4.2 keyboard on top... the same results.
[G2 and Desire Z Android Development] Flinny:
Keyboard fcing is a bit weird.... Latinime hasn't changed in a month. Can I ask which gapps you installed?
[G2 and Desire Z Android Development] Flinny:
Maybe a logcat of the problem?
[G2 and Desire Z Android Development] SRIBrian:
Briefly tried both Andromadus CM10.1 (4.2 AOSP with CM10.1) and Andromadus CM10 (Build 130). Thought CM10.1 worked very well...seemed faster and "crisper" than 130 and I liked the ui, but I could not get it to work with my Pro Plantronics BT headset. (connected well, but only heard static when tried to communicate) Build 130 worked with my BT headset, but voice dialer still does not work. (a must for using BT while driving in New York State, USA) Thanks for all your work, Flinny.:D:o
[G2 and Desire Z Android Development] blackknightavalon:
Try flashing the 4.1 gapps. I'm not having that problem.

Sent from Spaceball One.
[G2 and Desire Z Android Development] davidrol:
The gapps posted along with 130. Try upgrade, then a fresh install...with the same results.
[G2 and Desire Z Android Development] pauldacheez:
The gapps posted along with 130 are for 4.2. On 130, you should still be using the 20121011 gapps, as shown by goo.im's graph: http://goo.im/gapps
[G2 and Desire Z Android Development] ashwinmudigonda:
I want to try out the builds, but I just cannot seem to get gapps-jb-20121130-signed.zip from goo.im site. Could someone be kind enough to temporarily host it somewhere? thanks.
[G2 and Desire Z Android Development] Flinny:
The gapps I posted with 130 were 2012011.........
[G2 and Desire Z Android Development] davidrol:
I have the plantronics voyager pro. Hands free works using Google Now. Even then, you have to speak into the phone's mic, not the headset.

Heres a workaround. Using Bluetooth Control app, you can remap the headset button to launch Google now's voice dialer. First, disable native voice dialer.

Button for everything else works, e.g.; end call, answer call, previous call.

---------- Post added at 09:29 PM ---------- Previous post was at 09:25 PM ----------

Yes, I caught that. Same problem with *1011 gapps. I thought the keyboard is not packaged in gapps.
[G2 and Desire Z Android Development] 00sand00:
That's a US version and wasn't working well per experience of some users here in Europe. The one that I'm using was better for everyone that replaced 26.13.04.19 with this EU version.
[G2 and Desire Z Android Development] pauldacheez:
I noticed that after I posted, yeah. v_v

Keyboard's not FCing for me, though, and I had the 20121011 gapps previously installed.
[G2 and Desire Z Android Development] davidrol:
Thanks. I'll redo the upgrade.

---------- Post added at 10:53 PM ---------- Previous post was at 10:23 PM ----------

Apparently, I have a corrupt file, here. Sorry I didn't checksum before reporting. I'll download again.
[G2 and Desire Z Android Development] Transmission3000:
This may sound dumb, but...how do I reboot to the recovery screen on AOSP 4?

-Nevermind.
[G2 and Desire Z Android Development] amp:
Sad how one asked a civil question about an unknown app and he's responded in complete respect... yet he respectfully defends himself and once again... is insulted. Let's keep this positive fellas.
[G2 and Desire Z Android Development] chrisstavrou:
Flinny and all, thank you very much for this excellent rom.

As a tip for faster charging when using wall mounted chargers:

some are identified as ac chargers and phone can withdraw more than 0.5mA. Example is the htc charger.

Some others are identified as usb chargers and phone can withdraw only up to 0.5mA charging of course the phone slower even if the charger can deliver more Amper.

There is a usb plaque witch can convert a usb charger to ac and allow the phone to charge faster.

As this is out of topic pls contact me if you need more info.
[G2 and Desire Z Android Development] dexim:
I've noticed that I can get mobile data while I'm on the phone when using the ASOP builds, but not when using the CM based builds. Is this expected behavior? Is it possible to fix it? BTW, I'm on T-Mobile US.
[G2 and Desire Z Android Development] Transmission3000:
Installed CM10.1 last night, I'll take it for a drive today.

Thanks again, man!
[G2 and Desire Z Android Development] EdWaRdW818:
Dumb question

I know that this is a dumb question and the answer is probably within this thread (but I'm about to hop onto an international conference call in about 10 minutes and doing 5 things at once already)...

But I installed AOSP 4.2 v6 last night and so far I'm not experiencing any major problems (except for FCing when I edit a picture and a bit of confusion adjusting to some new features LOL)... But when is this project going to be merged with CM? There are LOTS of creature comforts (e.g. silence during night hours, T9-style contact search, etc.) that I'm used to with the CM-optimized version that I kinda miss and only noticed that it was gone when I flashed it (I was under the impression that those features were all standard?)

Sorry to pester and thanks in advance.
[G2 and Desire Z Android Development] natabbotts:
Could you post this here? http://xdaforums.com/showthread.php?t=2031671 You're more likely to get a relevent and helpful reply there :)
[G2 and Desire Z Android Development] dexim:
There is already a CM 10.1 posted. Check Flinny's site.
[G2 and Desire Z Android Development] EdWaRdW818:
I see... Sorry about that.

Yeah, that's where I got the ROM from.
[G2 and Desire Z Android Development] ashwinmudigonda:
So I flashed 4.2 Build 6 and have been running it for a day now.

For one, it is relatively slower than the 4.1 AOSP that fyodor had posted. I only restored 20 apps and let the stock launcher be. It was still much less responsive than 4.1. I found that the lockscreen widgets to be the slowest. Right after I wake the phone, swiping left or right does nothing. I have to wait a few seconds before I can swipe around.

However, after setting max background processes to 3, the ROM is speedier. But for this, I really like the ROM. Thanks, flinny.
[G2 and Desire Z Android Development] LAMER_CZ:
google ears

FINAL EDIT:

==========

OMFG .... I'm in CZE and google disabled this app for my region, I finally got it .... it detects my region from WIFI IP ..... this is just *ucked up !!! This ****ing stupid google mobile system cost me so much time (almost as much as linux did:) .... I should not regret the money and throw android phone away a long time ago! And I will, when affordable WP8 phone (preferably with HW keyboard) appears in my country.

Anyway, thanks to guys here on xda creating custom roms, it makes android a little more bearable system ..... so thanks for that, since android 4.1 it seems that it is almost usable system:) .... I'm looking forward to a new awesome ROM from andromadus:)

-------------------------------------------

Hi,

I have strange problem. When I install this ROM with SIM card, I can't get google ears widget (but according to titanium backup, it is installed on the system). When I install without SIM card (and without wifi login), I have this widget and then I can plug SIM card and it works OK.

But the even more strange think is, I have market and google ears and google thinks like that even without installing gapps. I tried to wipe my phone every possible way in recovery, but it still have this issues ..... and of course, I deleted SD card as well.

So, do I need to install gapps at all?

And another very odd thing is that if I install some very old build (flinnycm10_3x_78.zip), I have the same problem. And I'm 100% certain that 3 months ago (or so) when I installed this, I got "what's this song" thing on the main screen from beginning .... but now I don't and I can't find it in widgets as well ......

The problem is definitelly with my phone (or with me:), how can I delete whole phone before flashing?

I run ROM manager and install ROM from SD card ..... then I check buttons at wipe data, cache and dalvik and install rom ..... then (optionally) I install gapps (without checking wipe checkboxes), but as I said, I see no difference with installed gapps (the number of application is the same, I can sync with google and everything) .....

So, can enyone help me with this? Thanks.

(HTC Desire Z)

EDIT:

------------

I even downloaded some wipe script and nothing ....... I think always I flash rom, it behaves differently (one time there is language for select after flash, another time it is not ..... one time it is as select menu, another time it is as swipe carousel) .... If I'm in state where "sound search" widget is available ..... when I log to my wifi (not even selected and filled any google account! .... ), the sound search widget "magically" disappear .... and never appear again, no matter what!

I tried to remove sound search with titanium backup .... but it is not possible to reinstall it again ...... I'm totally lost .....

Is there any way how can I totally and complete delete my desire z??? Because I believe there is something somewhere on some hidden partition ........

BTW: Is rom manager part of this rom? Because sometime it's in there but another time when I reflash, it isn't:)
[G2 and Desire Z Android Development] nevyntanis:
@Lamer_CZ, try superwipe http://forum.cyanogenmod.org/topic/19959-superwipe-for-g2-w-gps-fix/ or you can try this http://xdaforums.com/showthread.php?t=1924078
[G2 and Desire Z Android Development] arpitnathany:
Battery life is pretty good in 130

40% battery left after 2 hrs screen on time.

36 hrs standby
[G2 and Desire Z Android Development] Flinny:
The speakerphone thing maybe I don't understand the steps to make it happen. I start a call from my phone, click on the speaker phone and the mic is muted (again I see the reason for that personally) I unmute the mic and it works? Give me exact steps to reproduce please :)
[G2 and Desire Z Android Development] MarkyG82:
As you say, on a call, hit speaker and it pops up muted, hit speaker again to send it back to normal and it stays muted.

On a school boy error front I didn't realise you could unmute it. On the other hand it should unmute when going back to normal speaker, no?

Also, why do you like it to mute when on speaker. Seems counter productive to me.
[G2 and Desire Z Android Development] blk_jack:
I use speakerphone every single day for meetings, however, I almost never actually speak while I'm on it. I always use it for phone meetings when I'm not talking and need to be handsfree, then when I'm speaking I'll pick it up & unmute. As soon as I done I put it back on speakerphone & immediately mute it.

I agree with you though, but I think maybe that's where Flinny is coming from.. Corporate IT ;)

---------- Post added at 12:11 PM ---------- Previous post was at 11:35 AM ----------

I just tested the hell out of speakerphone/mute & unmute and couldn't reproduce your issue at all. Both speakerphone, mute and even hold work exactly as expected, in combination with each other, etc etc. Do I need to turn off the screen while on a call or something else that I haven't tried?
[G2 and Desire Z Android Development] MarkyG82:
Ok. I guess its good as is. The main issue is it not unmuting when turning off speaker phone. Ill do a quick test just to be sure.

Edit: Just tested by calling my land line. It seems that the problem is not there in build 75. Apologies for taking up your time. Ill let you know as soon as it comes back (if).
[G2 and Desire Z Android Development] David Dee:
I want to confirm that my previously mentioned touchscreen problems were not rom or software related. I just had a new digitizer installed and my touchscreen now works perfectly. :) After the $60 investment (warranty expired), I guess I have committed to Vision for awhile, so thanks again Flinny/Blackjack for your awesome work in keeping this phone up to date!
[G2 and Desire Z Android Development] yozgatg:
I don't know if it's the qcom patches but build 75 definitly feels slower in scrolling

I reverted to 74 and opening the app launcher and scrolling is buttery smooth
[G2 and Desire Z Android Development] Flinny:
I reverted a couple of qcom patches that are currently being discussed again on the cyanogenmod gerrit, the change will be in the next build.
[G2 and Desire Z Android Development] mesaj:
Is GTA3/MC3/Shadowgun working or phone still reboots? Does Andromadus team fixed it?