yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Android Development] Flinny:
Well firstly it's where CM is hedding anyway and secondly I thought it possible it would fix some of the issues we are having such as no volume after boot until you change it, sound blackouts that Saga users seems to get etc. Seems it didn't solve either but introduced a volume bug. The speaker is just TOO loud, so loud that even with it not at full volume it distorts, it's being pushed too hard.

It's possible that it's this driver or it could be the kernel driver change that caused this. It was basically a case of lots of audio changes all arriving at the same time and now I don't have much of an idea which change caused which problem/changed the problem. The easiest to switch back to is the old userspace audio driver and takes us back more inline with CM anyway. If we find that isn't the problem then we can look elsewhere.

Unfortunately too much volume through the DZ speaker to the point where it's distorting to hell :>

The communication with google wasn't a rom problem... :)

ALT key on which keymap? Have you changed any of the input settings away from use system language etc? or is it just in a specific app... for example chrome seems to be broken but since it's the only app I've had problems in I'm putting it down to chrome being crap at the moment.

T-Mobile Wi-Fi calling. Something I won't be looking at since I am neither on T-Mobile or anywhere I can use it/test it. Has anyone tried flashing the ICS package that worked on JB, what was the outcome?

On another note.

I'm not having a go at anyone here it's just the way things are for multiple different reason at the moment. I seem to be the only one of the Andromadus team with time to spend on the Jellybean/framework/device side of things right now. Fyodor is obviously being immense on the kernel side and making it do things I never thought I would see the good olde DZ do but we can only work with the time we have available so don't expect instafixes for everything at the moment. Unless somebody donates enough to start a full time development team or more people help out that's the way things will stay. If anyone want's to get involved with development come find us on IRC #andromadus on freenode.
[G2 and Desire Z Android Development] NoFatePPC:
Hello, wanted to know if there is a way to disable the screen on animation... the backlight is coming up to slowly for me :)

Thnx
[G2 and Desire Z Android Development] Haprog:
I just solved my problem that I've been having with the physical keyboard. Mostly that Fn button hadn't been working at all.

I have a Finnish Desire Z and in the Language & input -settings under Physical Keyboard section the first setting is "vision-keypad-nor" (nor as in "nordic" I guess; I've seen some people have "-wwe" here).

The default option here is well "Default" which works perfectly, but I had clicked on that and selected "Set up keyboard layouts" and then selected either "English (US)" or "Finnish", but when any of those keyboard layouts are selected, the physical keyboard is very buggy (mostly Fn key just doesn't work at all). So if you're in that menu, you need to make sure that all of the keyboard layouts are unchecked, press back, and choose the option "Default". This should already be set to Default though if you've done a full wipe.

For some reason I had always (atleast for some time) set the keyboard layout to Finnish right after wipe and flashing ROM without testing first, because I thought Finnish would be the correct setting since I have a Finnish/Nordic layout on the actual physical keyboard.

So what is this "vision-keypad-*" setting even supposed to do? Everything seems to work best when you just keep it at "Default". It's a bit confusing.
[G2 and Desire Z Android Development] nevermind1300:
I figured this out last night, too. I changed to English (US) from default and the ALT keys stopped working, changed it back and all is fine.
[G2 and Desire Z Android Development] Flinny:
Seems changing the language in that menu makes it use a system default keymap which just isn't setup for our hardware keyboard at all. Not had a chance to look into what needs to change to make those options work but for now... leave it at default.
[G2 and Desire Z Android Development] NeverGone\RU:
The problem is that this mode is using Standard keyboard layout.

I've already fixed this bug for Russian and English layouts (pull request is still open in GitHub. Flinny?), so I can add more language support if you give me the layout.

:)
[G2 and Desire Z Android Development] Flinny:
Yeah wanted to look at using an overlay instead of editing framework base directly. Also not sure what those changes (if any) those changes will have on the on screen keyboard.... Have been working on something out of the mainstream branches :)
[G2 and Desire Z Android Development] NeverGone\RU:
Yea, I was trying to find anything related in overlay but failed to do so :D

And by the way, it doesn't affect on-screen keyboard. It's a separate thing.
[G2 and Desire Z Android Development] GinoAMelone:
I tried it a while ago (probably somewhere in the vicinity of high-80s/low-90s build). The WiFi-calling app just keeps crashing. Pretty sure we were at that point with ICS at one time.
[G2 and Desire Z Android Development] lbcoder:
EMBED

tag.
[G2 and Desire Z Android Development] Flinny:
105 uploaded.

Reverted part of the audio change. Kernel updates. Battery should be better.

Will update the op when I get to a PC.
[G2 and Desire Z Android Development] johrie:
Well how about that.. flash just crashed on my laptop lol.

Anyway.. downloading the new build now :)
[G2 and Desire Z Android Development] EdWaRdW818:
Good news and bad news... Good news is that now with Build 105 the keyboard is working... Bad news is that it's a result of me accidentally doing a full wipe and now I'd have to reset my "daily driver" phone's preferences. But even after installing the Wi-Fi call it still FCs and doesn't work.

Also, do you know what's happening with the torch (LED light feature)? Sometimes it takes almost 30 seconds to get light and it hasn't been able high brightness mode since my first install (87). No big rush on this one, just would be nice to have more light when I need it.
[G2 and Desire Z Android Development] sp1980:
If SIP calling is important for you, you'd better stick with b103 (in b105 it's broken again). No major problem s with that version.
[G2 and Desire Z Android Development] sigitm:
How much total RAM memory do you have? (Settings > About phone)

In my G2 with Andromadous build it's 362 MB.

Why is it less than the nominal 512 MB?
[G2 and Desire Z Android Development] Flinny:
Oh? Native SIP was working with 103?
[G2 and Desire Z Android Development] Flinny:
512mb is what the phone has total. The radio uses a big chunk of that and then a little is reserved for screen/audio/video for things like screen buffers... video decoding etc. What you see is what's left for the os and applications.
[G2 and Desire Z Android Development] sigitm:
Oh, ok.

I was asking because a friend's optimus one (a LG phone with 512MB ram), with an experimental cm10 build based on kernel 2.6, has got more total ram in the about phone section (416MB)

So I was wondering about this difference...
[G2 and Desire Z Android Development] paja18:
Hello. I have problem with this and previous version of the ROM. Autorotate doesn't work. Someone had a similar problem, and solved it?
[G2 and Desire Z Android Development] nevyntanis:
I use the torch pretty often I and I don't have any delay, not sure about the brightness, seems fine to me, but will check it out tonight.
[G2 and Desire Z Android Development] lordevol:
Torch is ok for me, autorotare is ok with aphex launcher, only the home screen do not rotate
[G2 and Desire Z Android Development] dwardo:
Several of us have this issue. Read back a little to find us... And if you want to help upload a dmesg output right after booting.
[G2 and Desire Z Android Development] DJMartini:
Sorry if this was already asked before, but where are the new builds getting posted at? They aren't on Op 1st post and I've tried www.flinny.org/testbuilds/ which only has up to 99

Where's everyone getting 105 at?
[G2 and Desire Z Android Development] nevyntanis:
Flinny.org/cm10testbuilds
[G2 and Desire Z Android Development] lbcoder:
I'm starting to wonder just how many of these weird bugs, like autorotate not functioning correctly, are a result of software, and how many are a result of ageing hardware.... Gravitational sensors, accelerometers, switches... can all get "stuck".

I think it would be nice if someone who is experiencing autorotate problems would go back and try some install that is apparently not buggy. See if the problem goes away, or if it persists where it previously worked.

---------- Post added at 10:36 AM ---------- Previous post was at 10:31 AM ----------

Different radio hardware maybe. Different radio firmware. Different media hardware.

HTC has always been a bit unskilled with memory allocation. HTC Dream had 192 MB RAM. Only 92 of that was made available to Android. This was later increased to 115 MB through a radio firmware update, without any negative side-effects. Radio performance was equal, Android performance went WAY up, as you can imagine it would with a 25% increase in available RAM.
[G2 and Desire Z Android Development] davidrol:
SIP and 103

Yes, sip/voip worked perfectly in 103 for a short time, only. Haven't timed it, but lets say 1hr. Then, it reverts back to broken audio. I noticed that the proximity sensor impacts audio quality a great deal in this case. When the phone is held close the ear (screen shuts off) audio is broken. Held a few inches away from ear (screen on) audio is perfect.

Somehow, when initial sip credentials are applied, the audio is perfect. Then later some changes, unbeknown to me, occur to diminish audio quality. As you know CSIPsimple (my workaround) has a feature to prevent proximity screen shutoff for this reason. Versions previous to ICS native sip don't have this problem, e.g. cm9. Still, love your work!:good:
[G2 and Desire Z Android Development] Flinny:
Hmmm try pushing the audio_policy.conf from the last build into /system/etc and see if sip works again?
[G2 and Desire Z Android Development] MIkeRD03:
Just tested build 105 and found out Apollo music player with DSP manager is really fine AND more than loud enough..BUT now my Poweramp is MONO only. Regardless if audio is direct driven or not. And volume in Poweramp much too low. Did Dalvic + Cache wipe.

The problem is I HATE Apollo music player.. :->

gesendet von meinem HTC Desire Z
[G2 and Desire Z Android Development] heybobitsme:
I could see it being an issue with ageing hardware as mine is almost 2 years old. However, the sensors work fine in ICS. I would love to test earlier versions to see exactly which builds work or not, but I just don't have that kind of time.
[G2 and Desire Z Android Development] natabbotts:
Try installing build 105 after a full wipe, and only install power amp. If the problem persists take a logcat, and send us a link to a pastebin of the log, or attach it :)
[G2 and Desire Z Android Development] davidrol:
sip audio

Yes, it worked. I will monitor each 15min or so to see how long it takes for audio to degrade and become broken. Oh, and I have tried sip audio with a fresh install with no added apps/customizations with same results:good:.
[G2 and Desire Z Android Development] toyorg:
What's new in 105?
[G2 and Desire Z Android Development] NoFatePPC:
hello, what i notice in the 105 build, is when i open the email client, (not gmail), there is another screen flashing before the email list opens

that other screen is only visibe for a half seconds, seems like a homescreen filled with shortcuts and android logos, verry strange

any1 else notice this?

thnx
[G2 and Desire Z Android Development] davidrol:
Monitored every 5min and it took approximately 10 minutes to degrade to broken audio.
[G2 and Desire Z Android Development] MIkeRD03:
Poweramp problem solved. Obviously only a freaked out app here. Reinstall gave Stereo back. Sorry for bothering. Sound and volume is OK.

gesendet von meinem HTC Desire Z
[G2 and Desire Z Android Development] J-Hop2o6:
I never knew the radio has an allotment for RAM. I know the GPU reserves some RAM for itself since its shared memory (think integrated Intel graphics on your PC/Laptop), and some reserved for the system (screen/audio/video buffers, etc.). But why does the radio need RAM? Or even a big chunk of the reserved RAM like you say?

JB's camera/gallery app has to be loaded for the torch to work. So that's you delay. Doubt it takes 30 seconds tho. Should take no longer than 10 seconds for the G2.
[G2 and Desire Z Android Development] Flinny:
The radio is like a separate OS running alongside.. it need's ram just just Android needs ram... Why it needs quite so much I don't know!

As for the flash light I use a powermenu button to turn it on/off and it's instant every time... I'll look into the high power mode it's probably just a config setting somewhere. It's not been high on my priority list :)
[G2 and Desire Z Android Development] Indiwiz:
this is what "Phone Tester" shows for accelerometer (doesn't work at all)
[G2 and Desire Z Android Development] davidrol:
SIP and 103/5

Here's the results of ping while proximity sensor screen on vs screen off.

64 bytes from 192.168.15.107: icmp_seq=45 ttl=64 time=1.943 ms

64 bytes from 192.168.15.107: icmp_seq=46 ttl=64 time=2.053 ms

64 bytes from 192.168.15.107: icmp_seq=47 ttl=64 time=1.738 ms

64 bytes from 192.168.15.107: icmp_seq=48 ttl=64 time=1.974 ms

64 bytes from 192.168.15.107: icmp_seq=49 ttl=64 time=1.638 ms

64 bytes from 192.168.15.107: icmp_seq=50 ttl=64 time=2.265 ms

64 bytes from 192.168.15.107: icmp_seq=51 ttl=64 time=1.800 ms

64 bytes from 192.168.15.107: icmp_seq=52 ttl=64 time=1.951 ms

64 bytes from 192.168.15.107: icmp_seq=54 ttl=64 time=1635.812 ms

64 bytes from 192.168.15.107: icmp_seq=56 ttl=64 time=463.911 ms

64 bytes from 192.168.15.107: icmp_seq=57 ttl=64 time=1213.329 ms

64 bytes from 192.168.15.107: icmp_seq=59 ttl=64 time=45.470 ms

64 bytes from 192.168.15.107: icmp_seq=61 ttl=64 time=2315.487 ms

64 bytes from 192.168.15.107: icmp_seq=64 ttl=64 time=957.022 ms

64 bytes from 192.168.15.107: icmp_seq=65 ttl=64 time=48.734 ms

Here's an interesting read particularly post 32: Wi-Fi always enters Power Save Polling (PSP) mode when screen off, causing problems for some apps. http://code.google.com/p/android/issues/detail?id=9781

There is a patch: http://xdaforums.com/showthread.php?t=752856
[G2 and Desire Z Android Development] davidrol:
Wifi PSP

Advanced Wifi Lock seems to be working to keep wifi on with during screen off.
[G2 and Desire Z Android Development] nevyntanis:
Same here, widget button works instantly, tested brightness seems bright enough.

Anybody experiencing issues when playing movies? Wish I could figure out how you guys take screenshots, lol (hint, hint), using mx player I get a band of pinkish lines, almost like analouge TV reception when its bad...
[G2 and Desire Z Android Development] strip419:
How come on sum oder phones they get the exact ram specified like the S2 and 3 or their radios use less?....wish there was a way to free that ram.....more ram will make things faster to meet our overclocked cpus
[G2 and Desire Z Android Development] dwardo:
Same thing here. Works in GB & ICS, just not JB. See my old posts on the subject.
[G2 and Desire Z Android Development] nevyntanis:
Just a thought, could it not be different hardware?. In other words, when the device first came out it was released with hardware from manufactor A but later models have hardware from manufactor B, which then would require different drivers. My assumtion is based on how notebooks are built, example; one model will have a realtek ethernet card and the same model bought a few months later may have a gigabyte ethernet card.... just a guess really.
[G2 and Desire Z Android Development] Indiwiz:
I think this is the problem also. rotation worked fine for me until I got my new G2. I don't have the old one anymore to post what accelerometer is in it, but a few posts above this one shows the hardware in this G2. also note the X, Y, & Z display no data. the app I used was "Phone Tester" .

could someone with working rotation upload a screenshot?
[G2 and Desire Z Android Development] nevyntanis:
Mine work fine, I will install the app and post the screenshot for you, first gotta figure out how to take a screen shot tho, mental I know, lol...:laugh:

---------- Post added at 03:23 AM ---------- Previous post was at 03:16 AM ----------

My info using phone tester is exaclty the same as yours, my sensors work perfectly, so there's that theory shot to hell....
[G2 and Desire Z Android Development] Indiwiz:
maybe the drivers automatically assume its that brand or whatever. i may flash CM7 or something and see what it says later on.
[G2 and Desire Z Android Development] nevyntanis:
Mmmmm, that's a good point. There may be commands you can use in terminal session similar to linux that report the actual hardware ID, but I wouldn't know what they would be or if they even exist, maybe adb has something, it seems pretty powerful.
[G2 and Desire Z Android Development] olyloh6696:
How's battery life for you guys on the latest build?
[G2 and Desire Z Android Development] Flinny:
Did I miss a post or am I still needing a dmesg from straight after boot for this sensor problem?:)
[G2 and Desire Z Android Development] Flinny:
Try the attached bcmdhd kernel module see if it makes any difference to your problem.
[G2 and Desire Z Android Development] tatowaki:
Call recording

Hi guys, first I'd like to thank devs of this ROM for their great work!

Been waiting long for an stable 4.X ROM for my beloved DesireZ and seems I finally found it!

I only miss support to call recording. I've tried both Call Recorder and rVoix, and neither of them work.

I've been doing some research, and it seems this ROM doesn't install vocpcm module, neither has /dev/voc device(s)

Cyanogen 7 and other 2.3 ROMs supported this.

Any chance you can add support to it?

I don't know if 4.X makes call recording impossible or it's just a question of compiling the vocpcm against this ROM. I can help on doing if needed.

Regards
[G2 and Desire Z Android Development] heybobitsme:
You must have missed it. I made a new output: https://docs.google.com/document/d/1j3WrABm1qlWwlyeB-kfQ6jUCbGTZyCWNAJ7pYLue8kc/edit

I hope this helps. :)
[G2 and Desire Z Android Development] dcpathak:
Browser issue

Hi,

I've been using this beautiful ROM since test build #78 as daily driver. Now I'm on #105. One issue I'm facing from the very beginning is the whenever I try to use the stock browser, it automatically directs itself to 'bookmarks, history, saved pages' page. This make browsing a pain. Yes I can install some other browser but I love stock browser for its speed. Am curious whether I am alone with this issue or others are also facing it. Also the device is loosing touch sensitivity day-by-day. With sense based roms, the touch sensitivity is better. What may be the cause. And to make clear, I always install a new version after 'wipe them all'.

Thanks,

dcpathak

HTC Desire Z (Rooted, S-Off)

Andromadus Test Build JB CM 105
[G2 and Desire Z Android Development] natabbotts:
In browser, press Menu -> settings -> general -> set homepage

As for touch sensitivity, I've been with this ROM as a dd since its late teens and have had no degradation.

Are you restoring any system apps or settings after you reflash? you should only backup and restore user apps (I know, it's a pain, but it's better than having to rewipe when you get problems).
[G2 and Desire Z Android Development] abrakadabra_srb:
is build 105 legit for flashin? :)
[G2 and Desire Z Android Development] dwardo:
http://xdaforums.com/showthread.php?p=31582708
[G2 and Desire Z Android Development] Gana2k1:
I have noticed that my screen gets distorted since b103.

I always full wipe before loading rom. After flashing, I force gpu rendering on - is that the issue?

Attaching screen shot from b105.

Doesn't happen always.

Anyone know the fix?

Thanks.
[G2 and Desire Z Android Development] Zelych:
I have some problem in b103 in Opera mini.
[G2 and Desire Z Android Development] LordXeth:
where can I download b105?
[G2 and Desire Z Android Development] nevyntanis:
Check a couple of pages back.
[G2 and Desire Z Android Development] Indiwiz:
for the text issues, just hold back to kill. happens every now & then .
[G2 and Desire Z Android Development] nevyntanis:
Would I be correct in assume that this mainly happens when the device gets bogged down with running apps?
[G2 and Desire Z Android Development] LordXeth:
I can not found
[G2 and Desire Z Android Development] Formiak:
So do I
[G2 and Desire Z Android Development] Gana2k1:
www.flinny.org/cm10testbuilds

You will find all test builds including 105.

Also check the OP for gapps.
[G2 and Desire Z Android Development] Aresmar:
Thanks Flinny I will try as you say this weekend and see how often I can see the bug. ;)
[G2 and Desire Z Android Development] Formiak:
I saw only text corruption for 1 day , so you may be right that occurs just after a wipe.
[G2 and Desire Z Android Development] tronmech:
I saw text corruption in the messaging app just after flashing build 64 that seemed to survive force-closing the app with the back button. Did the hot reboot and all was well.

About to flash beta 3, it came out *right* after I flashed b64... Oh the joy of a rapid build pace.
[G2 and Desire Z Android Development] blk_jack:
The only time I've ever seen the corrupt text issue has been after a fresh wipe and rarely after a reboot. Rebooting to "fix" the issue isn't needed, though. Just force kill the offending app (or restart it) and it's smooth sailing from there.
[G2 and Desire Z Android Development] Aumkar:
I'd just like to say, I do have graphical corruption once in a while, but I've noticed that I don't even need to kill the app to get rid of the corruption. When it happens in the launcher, I don't bother. I just open up my apps and it goes away in a bit. I typically switch between the launcher, gtalk, messaging, phone, play music, twitter, some games, and that's about it.
[G2 and Desire Z Android Development] David Dee:
Just flashing this from 62...first time without a full wipe....

Update: Phone has not blown up! All is working great, so smooth, and no restoring apps!...thanks again guys!
[G2 and Desire Z Android Development] abrakadabra_srb:
This build is awesome, I restrained myself from flashing ICS for a while now, but this baby runs so smooth so I couldnt resist anymore! :) I found one problem, no matter which sound I choose for my SMS, Gmail and Talk notification, it always plays the default notification sound? Anyone experienced something similar?
[G2 and Desire Z Android Development] dikamilo:
Amazing and huge work guys ! I have flashed build 66 and all works just fine :) No problems with wi-fi, bluetooth, camera foto and video works just fine - no artifacts, good quality, working preview, 720p video.

Very fast UI (i forced gpu rendering in dev settings). I use Apex Launcher with it.

Only thing I can't find is video record quality - is forced to 720p (no problem for me). And Android can't display my phone number in settings but this is CM bug I think, because this only works for me on MIUI and HTC SENSE roms.
[G2 and Desire Z Android Development] MarkyG82:
all my test build flashes have been onto freshly wiped systems. This 66 build was onto cache wipes and all is good. Ill probably stick with full wipes in the future but wanted to +1 that all is hunkydory.

The last 3-4 build have all felt very similar, but that is probably due to the awesome work gone into backend tweaking. Just a little bit of speed increase each time. Loving it :D
[G2 and Desire Z Android Development] spjuggalojoe:
I flashed a couple of test builds over b2 and saw no text corruptions, but did have some horrible battery times. Flashed b3 today and saw an improvement in battery life, but corruptions are back. Its been 14 hours since I flashed. Also having gapps connection issues. Guess I wipe before I flash the next build. :-(