yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Android Development] ashwinmudigonda:
I have learnt to wait for 3 days before posting my opinions on the ROM ;)

The ROM is more responsive than 1.2.x. I used to have many issues with even waking the device before. Now it seems fine. Coupled with Ed's 3.1 updater, my radio strength is stable and switching out of WiFi is almost instantaneous. The status bar power widget that sets the screen timeout is printing the timeout now, but it appears only for one of the 3 settings (30s).

However, the AOSP chains are still locked around the ankles. Phone.apk/Contacts.apk performance is still abysmal (I really wish they would fix this. I thought it's our phone's hardware that is unable to keep up with the demand, but it doesn't explain why it takes almost 5-8s after hanging up on a call to return to the call log). Updating/downloading apps is turning out to lock up the phone more than before. It even rebooted a couple of times when I tried to hit the back button from the Play Store. I have set up a Tasker profile to leave the screen on when the Play Store is launched and I set my phone down for a few minutes.

I normally do a clean wipe (data and all), but this time I was a bit lazy. I will do it for the next version. Thanks, blk_jack and EdKeys, for supporting our device. BTW, have you heard of the new Motorola phone full H/W keyboard - Photon Q? Please don't abandon us for that!

---------- Post added at 09:43 AM ---------- Previous post was at 09:37 AM ----------

Download 4EXT and install it. It will go through a reboot (it's been a while, I don't remember) and replace CWM with 4EXT. Reboot into recovery now and make a backup. It will be an EXT3 backup because you haven't yet converted your system/data/cache to EXT4. Flash Mimicry and gapps and reboot. Try out the ROM and see if you like it. If you think you might want to use it, then reboot again into recovery, convert your EXT3 to EXT4 (it should be under tools) and you should be good to go.

Alternatively, you can do it all in one swing where you get in, backup, convert, flash and reboot into your new ROM. Either way it is recommended that you switch to EXT4 partitions for performance boost. 4EXT will give you suggestions such as if you are experiencing difficulties, then you can convert your EXT4 back to EXT3. You will not brick or be stuck with it, if that is your concern.

I would suggest that you start off by making a Titanium Backup before you do any of the above. At worse, you can always flash your 7.2 and return to stable state.
[G2 and Desire Z Android Development] piruzinho:
Thanks much! I am doing it all right now.

---------- Post added at 05:21 PM ---------- Previous post was at 05:13 PM ----------s.

---------- Post added at 05:56 PM ---------- Previous post was at 05:21 PM ----------

Wow, this amazing so far. I have one "bug" to report, after combing through different menus: haptic/vibrate feedback on dialpad isn't happening, even if "vibrate on touch" is checked. this is on pin entry on lockscreen, and also when dialing.
[G2 and Desire Z Android Development] astriaos:
On this note as well, JuiceDefender unfortunately bugs the heck out on ICS for Vision. Since this is such an unusual and niche OS/Device combo I doubt the developer/bugtesting team actually has any experience with it.

To elaborate: Juicedefender works fine on moderate settings, however will have great difficulty turning wifi back on after it has been shut off. There is a visual bug most of the time where the wifi icon won't turn blue as it connects to google services. Between that and its seeming inability to always re-connect when you relight your screen, that makes things quite irritating.

Fundamentally JD isn't a bad application. It just happens to work better on Gingerbread. If you're finding that it is doing more harm than good then you need to examine your settings in greater detail.

I bumped back to Cm7.2 Stable a while back because of the issues with app related bugs. Mimicry is by far the current top tier of ICS roms for Vision, however there are far to many application related bugs. Juicedefender freaks out. LBE Security loses root constantly and the protection service must be restarted. Swiftkey 3 is still borked and probably won't ever be fixed if my contact at Touchtype is to be believed. All in all a discouraging time.

Now that I've said my bit, back to your regularly scheduled development chat.
[G2 and Desire Z Android Development] philosophics:
I'm using swift key right now to type this message on my vision running mimicry, so.....
[G2 and Desire Z Android Development] palmwangja:
performance setting best practice?

I know there is no silver bullet on this issue, but I just want to know what other people are experiencing with their own setup.

What would be the best practice for mimicry on the performance settings?

Virtuous OC?, zRAM?, KSM?, ... etc... :confused:
[G2 and Desire Z Android Development] kbeezie:
At this time, zRam won't actually do anything for you. In theory it would improve performance in the same manner swap would (Except it's done in-memory). But right now the changing of the setting doesn't actually enable/initialize the zram block yet.

I would say the default setting of SuperCharger + Virtuous OC (unless you use another CPU tool like SetCPU) would probably be your ideal no-frills setup.
[G2 and Desire Z Android Development] jevring:
Hi. I've been using this since 1.1.2, and am now on 1.3.1. I'm experiencing random reboots. Often when the phone is just sitting on my desk, but also occasionally when I'm in the middle of something. I'd say it happens 1-2 times per week, for apparently unknown reasons.

Is this a known bug, and/or is there a known fix/workaround?

Edit: Also, when it has restarted, it will invariably tell me that it needs to restard for some carrier reason (I forget now what it actually says). At first I clicked "restart" in this dialog, but now I just press "back", and it works perfectly fine
[G2 and Desire Z Android Development] blk_jack:
Not a known issue. Sometimes android will hot reboot if it's oom panicking, but this only happens under heavy active memory use.

Since it's happening after you've wiped clean I'm thinking it may be a hardware issue.
[G2 and Desire Z Android Development] Sheikmans:
I have no reboots or whatsoever. Rom is performing as it should be. I did however a full wipe/format.
[G2 and Desire Z Android Development] jevring:
I've tried other roms in the past, mostly sense 4 roms (well, only 2 of them, actually), and I had no reboots. Similarly, no reboots on stock GB or Froyo.

That said, my phone will be 2 years old in November, so things may have deteriorated...

I've at least had to do considerably fewer battery pulls with this rom than with others, though. I think I've only had to pull the battery 2 or 3 times with this one, compared to slightly less often than daily with the sense 4 roms, so you've really made something solid here. =)
[G2 and Desire Z Android Development] heathenasparagus:
been happening to me too. I assumed it was a hardware issue (phone has suffered water damage)

While we are on the topic, this could be related to corrupt memory (had similar issues with PC's in the past).

Is there some kind of memtest86-like app to check both onboard storage and device memory ?
[G2 and Desire Z Android Development] kbeezie:
I don't know of a memtest but check to see what emmc chip you have. (search the g2/dz forums for the emmc poll to see if you got the "good" chip like in my signature or the bad one mentioned in the poll)

The "bad batch" had often been the ones found when the internal memory died.

Sent from my T-Mobile G2
[G2 and Desire Z Android Development] DJMartini:
SMS's getting missed and not properly sending

I've been having a really annoying problem since I came over to CM9 from CM7 I'm wondering if anyone else is experiencing or if it might just be my service with T-mobile considering my area.

I use Handcent SMS for the look/features, but ever since I switch over to CM9 I've been experiencing bad problems with trying to send SMS's that won't go through until I keep my phone on to ensure the circle for sending them completes. I also came into work this morning and found that I received a new SMS from someone than it post that it was sent last night? It seems this continues to be an issue. I've never had this problem on CM7.

I'm currently on the latest radio 12.62.60.27_26.13.04.19 and matching ril's ... My APN settings I've never changed from CM7 to CM9 and I can send message through and receive them still which doesn't lead me to believe that's the issue. I was having same problems with Jerl92's CM9 Rom as well.

Any suggestions? It's really getting annoying for me. Should I switch radios?

Thank you,
[G2 and Desire Z Android Development] blk_jack:
These reboots (where a SIM error pops up) aren't actual reboots, they're hot reboots. They're often caused by misbehaving apps that cause OOM-related panics. When this happens you'll get a hot reboot rather than your entire system freezing up. Since generally speaking Android doesn't just do that to itself, pinpointing which app is causing this to happen is crucial. The usual Watchdog/logcat methods are always good to employ for testing & fixing. Though if you wish to follow up with debugging, do so in the QA Forums.

I've never heard of this before.. does this happen when you don't use the lib-RIL updater on Aroma (or EdKeys' package)? There's the possibility that it's your APN settings since you've wiped /data clean since coming from CM7. Lastly, this is happening to you in version 1.3.0 onwards with wifi calling disabled, yes?
[G2 and Desire Z Android Development] palmwangja:
..., even full wipe didn't help a lot let alone cache wipe. I still have a sudden disappear of exchange contacts/calendar. :eek::silly:

I'll disable facebook contacts sync as a last resort... let's see.
[G2 and Desire Z Android Development] DJMartini:
Without the lib-RIL updater it takes forever to find a single normally. Guess I can go back to CM7 backup I have and verify the APN settings. I just thought that 'performance' wouldn't be an issue for APN settings as if they aren't right it just wouldn't work at all.

I'm still on 1.3.0. Haven't updated to 1.3.1 yet. I've got WiFi calling installed, but not turned-on when all this crap is happening.

I'm going to backup, re-flash CM7 and gather my APN settings. Full wipe and fresh install 1.3.1 and see if it helps any. I'll post back.

Thank you blk_jack
[G2 and Desire Z Android Development] blk_jack:
Sounds good. Beware of a small bug right now in Aroma that affects 1.3.1 with wifi calling. If you install wifi calling from a fresh wipe (on 1.3.1) it won't flash the kernel (!) and errors silently. So the work around is this: when you flash 1.3.1, don't select wifi calling/lib-RIL updater. After it finishes, flash 1.3.1 again and select wifi calling.

It'll be fixed in 1.3.2, which will be coming out soon(ish), but for now you'll need to use that workaround :o
[G2 and Desire Z Android Development] DJMartini:
Thank you for the heads up. When I flashed 1.3.0 I chose 'No' to the Wifi calling app and just manually flashed Edkey's v2.1 .zip.

To help with all of this I'm going to install v1.3.1 without WiFi calling and without matching .ril's and see if if it has any improvement.

I just got my APN settings from CM7, so heading back to flash now. I'll keep you posted.
[G2 and Desire Z Android Development] kbeezie:
Ps I never had a problem with it not flashing the kernel with the ril selected only with wifi calling option.

Sent from my T-Mobile G2
[G2 and Desire Z Android Development] blk_jack:
Okay good. I'd forgotten if the lib-RIL option also caused it from our testing, so I was erring on the side of caution. :)
[G2 and Desire Z Android Development] piruzinho:
I haven't been getting K-9 notifications, or getting them super sporadically, even with permissions fixed - anybody else have this problem?
[G2 and Desire Z Android Development] Formiak:
Well , everything runs perfect and I can;t glom onto anything but batter life is really low , don;t know what is causing this... 6hours since I finished charging to 100% and now it;s 30 % with only 55 minutes on screen. I have .19 radio and checking with watchdog cpu usage and can;t get to know what is causing this.
[G2 and Desire Z Android Development] blk_jack:
Read the OP, it has info on battery drain
[G2 and Desire Z Android Development] Formiak:
I've turned off google backup service and hope it will get better.

Wysyłane z mojego HTC Vision za pomocą Tapatalk 2
[G2 and Desire Z Android Development] blk_jack:
It could be any app abusing wakelock. Yesterday exchange went nuts on me and used an hour of wakelock before I had to manually kill it. The point is you should consult the battery stats in settings as well as apps like betterbatterystats in order to diagnose the problem.

The rom itself won't abuse wakelock, it's always an app.
[G2 and Desire Z Android Development] Formiak:
Thanks for helping , got that app and seems like maps are causing this , am I right ?(I haven't been using maps today)

Wysyłane z mojego HTC Vision za pomocą Tapatalk 2
[G2 and Desire Z Android Development] Ditamae:
Try posting a dump in the betterbatterystats thread. For details see the OP. Chamonix and company are pretty helpful...
[G2 and Desire Z Android Development] blk_jack:
What does the partial wakelock say in particular?
[G2 and Desire Z Android Development] otariq:
Need help. Wifi seems to be broken on the latest version. It just says wifi is turning on but never does. Tried switching to airplane mode and turning it off but doesn't do anything
[G2 and Desire Z Android Development] tarroyo:
Didn't see much of a response so I'll bring this this issue again, seeing it on a clean install after superwipe.

Not sure what's going on but the sense 4 recent apps preview icons are somewhat squashed/resized didn't seen this issue present on the last version of Mimicry.
[G2 and Desire Z Android Development] blk_jack:
Are you running wifi calling in 1.3.1? If so look up my post earlier about wifi calling and the workaround involved with flashing it twice.
[G2 and Desire Z Android Development] blk_jack:
I'll look into tjis, but out of curiosity are you running the stock dpi?
[G2 and Desire Z Android Development] otariq:
Yeah I was thanks I'll look at the earlier post

Edit: reflashed and everything's working perfect. This roms awesome works super smooth thanks
[G2 and Desire Z Android Development] tarroyo:
post deleted
[G2 and Desire Z Android Development] Deathmehr:
Talking about battery lifetime, I'm going for my personal record on this phone. It's running for 2,5+ days and still 30% of capacity. But I'm a minimalist, I manually manage power.
[G2 and Desire Z Android Development] Formiak:
I've never achieved so long battery life as yours maximum was 1 day ( on gingerbread) , but I;m almost using all the day wifi at school and later at home.
[G2 and Desire Z Android Development] kbeezie:
Normally using 100% screen brightness helps quite a bit too.

Sent from my T-Mobile G2
[G2 and Desire Z Android Development] chan1628:
Not sure how to take this...

quadrant score dropped by about 100ish pts, after going from 1.1.2 to 1.3.1.... but user experience is way better with the latest update... very responsive, no more long lags... stable & snappy, just how I like my ROMs :)

Edit: haven't really had a chance to test battery since I haven't been able to put down the phone after the update... once I go back to normal usage, I like to see if I can get more than a day with a single charge

"there is no spoon"
[G2 and Desire Z Android Development] tarroyo:
yes, stock dpi.
[G2 and Desire Z Android Development] demkantor:
more than likley this is because benchmark scores have little to do with real world situations. they mostly only make you feel good/bad
[G2 and Desire Z Android Development] whistler4ever:
1.3.1 is amazingly fast and responsive! I like it a lot!!!
[G2 and Desire Z Android Development] Formiak:
My battery yesterday lasted for 14hours with 6h wifi and 3hrs on screen so result is better. I turned off agps and gps and backup google service.

There is another problem now , when someone is calling me I have to wait 3-5 sec to see who's calling me cuz screen dispalys only pure phone number. It has nothing to do with cpu speeds. Any ideas?

Wysyłane z mojego HTC Vision za pomocą Tapatalk 2
[G2 and Desire Z Android Development] ashwinmudigonda:
It's an AOSP Phone.apk problem that has not been fixed. Or somehow, our phone's hardware cannot handle this (and the Contacts.apk) app properly. Either way, it's a known issue and not a Mimicry/Andromadus thing.

Hopefully CM10/JB will fix it. In that light, devs, are you seeing any improvement in your test builds with regards to this issue?
[G2 and Desire Z Android Development] DJMartini:
Everyone is so lucky to get this much battery time. I have to have 2! 1500mAh batteries just to get through HALF a day! I only have 70 apps, removed Facebook (hog of battery!) and have one home screen for widgets (Beautiful Widgets (weather) and Stock app). I keep my screen brightness @ 25% and don't use auto (drains battery more). I leave GPS on as I've found it's given me a little better battery life. I've notice I loose 10% of battery without ANY use every hour normally. I verified no 'wake' issue as the battery status shows no 'Awake' blue/color for long periods of time which is normal for me.

My biggest complaint about the battery is when I go to the gym to listen to my music. I use Apollo, walk into the gym with 100% battery. Listen to my music for a good solid 2hrs with minimal txt and some e-mails for work (through Touchdown) and walk out with < 30% battery. By this time I have to go home and swap out batteries.

I only WISH! I could get as much battery as everyone else has.

Edit: I've also tried a day removing backup google services without any difference in battery life =(

I have this exact problem as well! It's annoying! After about 2-3 rings it has a delay before the picture or even callID itself comes up on my screen and sometimes I miss the call. I'm at 1248MHz and changed it with no difference. If anyone has a suggestion it would be nice.

Edit: Thanks Ashwinmudigonda for posting reply I missed regarding this =)
[G2 and Desire Z Android Development] Roolio:
I came across a bug. When I'm being called, and I got my keyboard opened, so I'm working in some app in landscape mode, I don't see who's calling. The phone screen is black with the unlock 'animation' in place, but nothing else. No photo, no phone number, no name or anything. When I close the keyboard I do see who's calling, but the 'unlock button' (to answer the call) is in far right position already instead of in the middle.

Everything else is working just fine, love the JB animations!
[G2 and Desire Z Android Development] J-Hop2o6:
JB has improved the Phone+Contacts apk's including CallerID load. I have to keep testing on the percentage of fails (more than 1.5-2 seconds). ICS is about 85% of fails (takes more than 1.5-2 seconds to load Caller Info), and JB is about 5-10%. These are not official tests, just from memory.
[G2 and Desire Z Android Development] blk_jack:
Sounds like your radio is likely killing the battery? You need to troubleshoot if anything is using wakelock and what kind of reception you're getting (Settings-> Battery-> Click the graph and observe the signal quality bar). If I were you I'd open a QA thread on it as it's not related to the rom.

After 6h off the charger and 1h15m screen on time I'm at 75% battery, which is inline with the typical battery life I've always gotten on Andromadus / ICS.
[G2 and Desire Z Android Development] DJMartini:
I'm on T-mobile in US, however I do get crap reception in a lot of places. You think I should flash an older radio? I'm currently on 12.62.60.27_26.13.04.19
[G2 and Desire Z Android Development] GinoAMelone:
Signal strength is generally the single largest factor in consistent poor battery life. A simple example. I started a new job this week. At the old job, I'd have a dead battery by mid-afternoon. I'm sitting on 80% an hour before leaving time today.

I suspect your gym has horrible signal. Try going into airplane mode while there.
[G2 and Desire Z Android Development] kbeezie:
This is exactly why I do wifi calling at home. That plus a "always on" wifi sleep policy saves a lot more battery than the radio constantly looking for good reception.

Sent from my T-Mobile G2
[G2 and Desire Z Android Development] H4rry:
blk_jack

Just gotta say thank you for your work on this. Been using 1.3.0 and lovely ROM. Updating to 1.3.1 as I type.

The ROM is mostly perfect. My only issue is the lag wrt to phone and contacts but as you've mentioned that is really an ICS issue. Still version 1.3.0 was a huge improvement in this area for me. Thanks again.

Looking forward to trying out 1.3.1, almost finished installing.
[G2 and Desire Z Android Development] shapr:
I would, once again, like to say, this is amazing work.

Also, kbeezie's rip of nick3r's swap/apps-ext mod is working famously, in conjunction. Well done fellas. Well done.
[G2 and Desire Z Android Development] austriker27:
Does anyone use a task killer with this? I remember it being a raging debate back when I had GB but dont know if its good or not for ICS to be running something like ATK. I do have the search function setup to bring up recent apps and swipe them away when I am not using an app to make sure its a smooth experience..
[G2 and Desire Z Android Development] demkantor:
still the only task killer worth using is watchdog, there is a free version in the market. mimcry has a supercharger script along with other tweeks, so between what blk_jack has done and what android already does force kills should be few and far between. don't set up any autokills just see if anything is using too much cpu then decide to force kill or remove it all together
[G2 and Desire Z Android Development] kbeezie:
Well minfree configurations tend to trump any kind of 'task killer' now days, SuperChargerV6 for example for the most part doesn't do much more than set up the systems flags, limits, and other things to allow the system itself to close apps as needed. (even without Superchargerv6 there's always the underlying defaults).

Throwing Task killer on top of that could just get messy.
[G2 and Desire Z Android Development] Oni-Musha:
First, compliments for this rom is great!

Second, i want notice you that Camscanner doesn't work because the camera is broken =(
[G2 and Desire Z Android Development] blk_jack:
Thanks, and yes, non-stock camera apps generally don't work (or will cause a lot of issues) on 2.6 kernel ICS roms.
[G2 and Desire Z Android Development] kbeezie:
Camera related issues are pretty much the same on all ICS roms (though the one in Virtuous Infinity full Sense 4.0 behaves a bit nicer).
[G2 and Desire Z Android Development] tronmech:
Are you using ebay batteries? I have a pair of "1500mAh" batteries that last only half as long as my oem batteries. Try getting an oem one. You may find that it is your batteries and not your ROM..

Also, lithium ion batteries tend to degrade with age, so if they are getting on 2 years old, fresh batteries would be another good step.
[G2 and Desire Z Android Development] ajhavery:
Asphalt 7 heat doesn't works, it always stops working...:(

Please fix if possible.
[G2 and Desire Z Android Development] blk_jack:
Logcat or bust!
[G2 and Desire Z Android Development] ajhavery:
Sorry, I switched back to cm7, will get a logcat as soon as I loose my control for trying ICS again.
[G2 and Desire Z Android Development] kbeezie:
I'm using a 9$ 3500mAh "ebay" battery that actually last a couple of days, and actually measured out to 3450mAh .

So I wouldn't just simply chalk it up to that, even though it could be a possibility (even 'more expensive brands' sold on ebay or their own website can be faulty).

---------- Post added at 12:52 PM ---------- Previous post was at 12:52 PM ----------

Asphalt 7 has been working fine on my phone with this rom for the last few days.