yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] blonkster:
I've come from a Galaxy S to the S3 and I'd like to use all my lovely new screen.

However, the icon spacing is too large, the actual areas available for icons and widgets does not extend to the top and bottom of the potentially usable area, and the gaps above and below the icon shelf are also too large.

If you slowly swipe between screens you can see the gaps around the rotating area - IYSWIM. Also the Google search widget doesn't even reach the top of the above area!

I assume this is not just on my phone, but on others too. If so, is it something that Samsung are likely to address, or do I have to get another launcher?

Thanks

Blonkster
[Galaxy S III Q&A, Help & Troubleshooting] androidpixar:
Your best bet is a launcher, the likes of Nova, Holo or Apex.
[G2 and Desire Z Android Development] adamz667:
Good one, grats :)
[G2 and Desire Z Android Development] zibiss:
Time to test. THX :)
[G2 and Desire Z Android Development] Dushaine:
Wow... NICE !

Thanks ! ;-)
[G2 and Desire Z Android Development] jspina:
Congratulations on your OWN rom! I have not seen so much put into a rom in a long time! Bravo. It has the best of everything :D
[G2 and Desire Z Android Development] blk_jack:
Thanks guys!

I need to note though that while I am maintaining a separate code fork with these new features & additions, that I am still a part of the Andromadus team and that the team's efforts as a whole make this ROM possible. Credit given where credit due. :)
[G2 and Desire Z Android Development] Pickx:
Great job. Flinny can't update Andromadus as often as the flash-oholic in me would like and it's nice to see someone taking over in that regard

also I just can't get over how useful statusbar shortcuts and power button flashlight are. I just can't overstate how useful these two features are, seriously.

Now if only you added an option to change ICS multitasking to GB-style "dumb" multitasking. I'm pretty sure it exists in AOSP because apparently it's a keyboard shortcut in some Android tablet/slider I can't remember. ICS multitasking is horrendously slow, at least on the Vision.

Oh and... an option to make the date text in the status bar shorter?
[G2 and Desire Z Android Development] EdKeys:
Congrats on the new release! Appreciate all the work you've put into this blk_jack.
[G2 and Desire Z Android Development] blk_jack:
That GB style Recent Apps does definitely exist in the code. For fun hit FN+TAB on your hardware keyboard ;) Recent CM patches have actually forced the ICS style over the old one in parts of the code, but you can get to it. It wouldn't be too difficult to implement either....

First new idea of the thread! Thanks Pickx :)

As for the date.. I've been playing w/ a few Statusbar customization options. I'm on vacation this week (19th) so maybe I'll have time to tinker w/ Android now that I'm free from work and at a cottage w/ new highspeed access :D
[G2 and Desire Z Android Development] blk_jack:
Thank you sir, your help and efforts are also much appreciated!
[G2 and Desire Z Android Development] heybobitsme:
I applaud your efforts, sir! The OP and subsequent posts are a shining example of how a ROM developer should post. *sniff* *wipes tear away* It's beautiful! :D

Anyway, I'll test this out as soon as I can.
[G2 and Desire Z Android Development] mrvanx:
Flashed and testing now.

Will follow this ROM with interest ;)
[G2 and Desire Z Android Development] J-Hop2o6:
Subscribed! You finally got this great rom (based on CM9+Andromadus) out of alpha/beta and made a public release! Even the alpha/betas we're flawless (even a bit better than Andromadus :eek: ;)). This rom has a great future ahead of it.

One feature I can think of right now is to add a toggle switch to enable/disable the Android Debugging icon out of the status bar/notification slide and add the toggle in the Dev Options. Its a waste of space (I already know its enabled!). I remember this feature in CM7. Would be great if u can add this blk!

I feel the same way at what u said in the first half. And great idea for the ones that want the pre-3.X/4.X Recent Apps back. I won't use it, but its a neat idea (since the ICS version isn't the fastest for our dated phone). I was glad when CM7 added in the option to expand from 8 to 12 & 16. Hopefully u can add in the option for more recent apps shown for them blk.

LOL. But yea, I agree.
[G2 and Desire Z Android Development] etp23:
Will this work if I just try flashing over my cm9 from I got going I want v6 but I just switched to the latest cm9 beta 13 :/
[G2 and Desire Z Android Development] blk_jack:
Your mileage may vary. They're both based on the same code but Mimicry adds new features that might cause issues. You could try, I think you'd have more of an issue if you were going from Mimicry to another ROM though rather than CM9 -> Mimicry. Mimicry automatically flashes dalvik and /cache for you on installation so you would just simply need to flash the zip and gapps over your existing setup.

Make a backup first!
[G2 and Desire Z Android Development] blk_jack:
I just added a Suggested Ideas area in the OP where I'll put any ideas people suggest in the thread. If you like an idea or can think of some way to elaborate on it please say so so I can gauge the popularity of things.
[G2 and Desire Z Android Development] etp23:
Alright than man :)
[G2 and Desire Z Android Development] virtualflyer:
have you modified lcd density?
[G2 and Desire Z Android Development] amogil:
Not to sure about things that don't work on this rom cause everything is working like stated , just no 720p pictures but hey at least the camera works, any way to not have super nova as default...
[G2 and Desire Z Android Development] dxaxn:
No, what is density? I can't even find any setting for that. Is it hiden somewhere in screen options? Thx

No one else with play store compability problem?
[G2 and Desire Z Android Development] terrormattie:
Another reqeust by me is having the trackpad ligth work as an notificator.

See this for clearnes: http://www.youtube.com/watch?v=EpMdn8ZzmJc

Thanks again for this awesome rom!
[G2 and Desire Z Android Development] csolanol:
That feature is included now i think.
[G2 and Desire Z Android Development] terrormattie:
Thanks for your reply.

On my phone it is not active, do I need to set it up or something?
[G2 and Desire Z Android Development] Aumkar:
Check the profiles. There are options for it in each notification type in each profile.
[G2 and Desire Z Android Development] =JKT=:
Thanks blk! This is the first ICS ROM that I've used as a DD and not been irritated!

Thanks to the devs from AOKP, Andromadus, and Cyanogen for all their incredible work! I think I'm finally not going back to GB :D

I would add an option in Aroma to not install DSP Manager as well.
[G2 and Desire Z Android Development] terrormattie:
Thanks!

I still cannot figure it out, for clearety: I mean the trackpad.
[G2 and Desire Z Android Development] tvdang7:
great rom i am not having any slowdowns anymore i am assuming its the supercharger script thing doing good on the ram usage because before i would slow down alot due to no more free ram.
[G2 and Desire Z Android Development] blk_jack:
If you're upgrading versions of this rom you shouldn't even have to wipe or manually format anything. The installer automatically wipes /system and both caches. I typically flash the new zip and gapps over and I'm good to go.

That said, by the very nature of good ol' android, sometimes for seemingly no reason things go wrong and fc or there's weird lag and you need to wipe /data and restore from default. I personally haven't had to do that too often though, only twice since January. Granted I've only used Andromadus based roms, but it's different for everyone.

Hope that helps -- I may add a section to the OP on upgrading/migrating from other roms, but honestly the same rules apply to any rom.
[G2 and Desire Z Android Development] Aumkar:
I have an update. Battery life seems decent for right now.

https://twitter.com/AumkarIyer/status/215383922861801472/photo/1

4 hours of calls, 2 hours of screen on time, and plenty of Gtalk/Whatsapp/Twitter.

---

However, as my battery got lower, my phone got slower. At 10-11%, there was tremendous lag and all that, and my free RAM often varied from 23MB-xxx KB. Since I switch on my screen and start using the phone immediately, I think the upper limit for the screen off profile in the Virtuous OC daemon is far too low ( 368Mhz IIRC ) and I'm thinking 768Mhz is much better. Phone is more responsive from the start.

---

I thought my Nova Prime setup was taking up too much memory since it doesn't show up in the regular apps menu so I minimized that too. Dropped my homescreens from 3-5, reduced the number of shortcuts and widgets on screen, etc.

Another thing was, I had plenty of notification tray toggles ( I think 11 or 12 ), so I dropped that down to 6 and left my notification shortcuts for tweeting from the tray and Soundhound's track id along with the app switcher and settings shortcut.

So I'm hoping this takes up less memory. I'd much rather my phone be fast and responsive than bogged down to get to all my toggles without changing too many screens.

This will be my second charge cycle, so I'll keep updating my battery life changes. But since charging and rebooting, phone's been okay so far.

Oh also, as I was making my system stuff ( the notification tray toggles, shortcuts, lockscreen shortcuts etc ) minimalist, I had a hot reboot =/. Hasn't happened in months. Logcat was running at the time, but I didn't think it was a bug as much as it was me just stressing the phone too fast. Gotta remember that it's not a desktop or a laptop :P.
[G2 and Desire Z Android Development] tronmech:
Well, I haven't had one graphical glitch yet while using this Rom. That's definitely a bonus. Lags are way down from the Audacity test builds. And I haven't had the mysterious volume drop that I get on the current Audacity test builds.

Going to stay on this for a while.
[G2 and Desire Z Android Development] palmwangja:
Yes!, it was due to the fact that I somewhat changed *.kl myself and missed this part

key 211 FOCUS

key 212 CAMERA
[G2 and Desire Z Android Development] blk_jack:
Give 768 a try and let me know how it fares for you. I actually used to have it as that when I first released the Virtuous OC tweak and eventually lowered it to 368 as the lower frequency seemed to cause less idle drain without any negative effects. It's been set to 368 at this point since alpha13 or so.

As for the "more responsive" from the start (on wake?). It's important to remember that smartassV2 automatically jumps to 768mHz on wake and will immediately clock up or down depending on usage. It has a separate frequency it uses for screen on so the screen off frequency should have no effect on the responsiveness for on wake.

Finally, beware of rogue processes causing lag and drain. Yesterday I was looking up movies with Movies (by Flixster) and I went to view the trailer. It gave me an error about not being able to play the movie and so I closed Movies and went about my business. It seemed a bit laggy so I looked at a process list and couldn't find anything abnormal. Then I opened logcat and was getting mediaplayer/mPlayer error spam over and over. I actually had to manually kill the process by using the pid in logcat. Once I did that the lag and drain were gone, but it's still one of those things to consider whenever something seems "wrong". It's almost always an app, widget or service causing it.

Thanks for the feedback!
[G2 and Desire Z Android Development] demkantor:
Watchdog allows you to see system processes that are running, you can kill them from there a bit easier as well
[G2 and Desire Z Android Development] blk_jack:
Yea, I used to use Watchdog w/ GB but ever since switching to ICS I've stopped. It was giving me a lot of warnings when running regular apps that just happened to briefly spike. Even when setting the cpu threshold fairly high. Maybe I should give it another go though.
[G2 and Desire Z Android Development] J-Hop2o6:
What's wrong with DSP Manager?
[G2 and Desire Z Android Development] GinoAMelone:
I've been using OS Monitor for a long time now and am very happy with it for general process monitoring.
[G2 and Desire Z Android Development] blk_jack:
Thanks I'll check it out!
[G2 and Desire Z Android Development] blk_jack:
The reason www/.com isn't working is because you selected Enhanced Keymaps in Aroma when you flashed the rom. Reflash and unselect it for that key.

Fn+ delete works as intended except you need to longpress delete instead of tapping. This is to prevent accidental line deletions, so just hold it a bit next time.
[G2 and Desire Z Android Development] costipl:
There's one tiny glitch with the feature of changing the statusbar color/transparency in 1.5.0:

After a reboot, the statusbar is black, no matter what is set in the options. I need to go into the settings and change color/transparency even a little bit, then it chatches up, applies the setting and I can go back to my usual setting.

It's nothing serious, though, just letting you know.
[G2 and Desire Z Android Development] strikey17:
blk_jack, with respect tot he Bluetooth issue I an one other user have described, attached please see the logcat. Hope this will help you to identify the issue. If not, let me know and I will make another logcat or whatever else may be necessary. I use nokia Hf-310 carkit and Nokia Bh-216 headset and have the same problem with both. Thank you in advance!
[G2 and Desire Z Android Development] PhantomLord:
Phone app closing

Hi

First of all - Mimicry is great, the only ROM that I use for longer time and don't feel like changing it.

However I have one question.

Is it possible to give higher priority to phone app in the rom?

The problem I experienced is that whenever I use some apps and then want to make a call, the phone app takes a while (2-3sec.) to launch. Of course if I use phone app after making a call it launches instantly, so for me it is simple - it has quite small priority to stay in memory and system is closing it down to free some RAM.

Is it posible to make it stay (like a forcing launcher for instance). This would be helpful for me as calling is...well main feauture of the phone ;) .

Once again thank you very much for such fast and stable ROM.
[G2 and Desire Z Android Development] Kéno40:
it was possible with the V6 supercharger Bulletproof option.

You can try it I think.
[G2 and Desire Z Android Development] palmwangja:
I experienced this sort of BT/voice call issues, let's say, since around 1.4.x? This was very new problem to me.
[G2 and Desire Z Android Development] salimbaba:
I am experiencing a strange problem , if wake up my desire z (trackpad or power button) the touch screen doesnt work the first time so i turn off the screen (Power button) and turn it back on again (power button or trackpad) and the screen starts working again.

I did superwipe before flashing mimicry.
[G2 and Desire Z Android Development] blk_jack:
Thanks, I'll look into it.

I'll look into this too!

This is actually an issue with ICS AOSP and affects all ROMs. There have been a number of discussions in the thread about it already. I would suggest searching for them since they suggest why it happens and ways of lessening the lag.

Definitely don't try to use V6 Supercharger to bulletproof the app. Android priorities are reset by the system almost immediately, and the script doesn't change them permanently. So what happens is people run the script every X minutes (seconds?) to set an app priority and then Android almost immediately resets the app priority back to system default.

The only thing that really happens is you waste a ton of battery since your phone will abuse wakelock running the script constantly.

There's no way for a user to permanently lock an app in memory.
[G2 and Desire Z Android Development] XVI Ames:
Well, I'm back in business! I guess it "was" (hoping it's really over) an emmc issue, but I wonder how it could happen...

I read here and there that we should NEVER remove the battery... I might have done it at critical moments, I don't know... but the most often, it is because my phone is freezed, and when I'm in my car, I just cannot plug it into a computer to run an adb reboot command ^^

But my question is more specific to the rom: one thing I did change a few days before my tragic crash, was activating the option to longpress kill running app...

The problem is that it sometimes killed apps when I did not want to (eg the phone is not responsive, I just tap the back button, but it doesn't get that I did release it... and it kills the running app... on other times, it killed the running app, and the launcher too.

And the specific to this rom part: what is exactly doing to "remove all running apps" option, in recent apps? Is it the same as swiping all of them one by one (but quicker), or it is "really" killing them?

Actually, I'm wondering if killing apps in a too agressive manner and maybe at critical moments could not be involved in the emmc issue I have had?
[G2 and Desire Z Android Development] oVeRdOsE.:
Well, I was about to post something about this.

Blutooth work with some devices, not all. With affinity I was able to connect all my blutooth devices, now with this rom only one is working.

It says ''paring'' forever. It never connect.
[G2 and Desire Z Android Development] blk_jack:
The things you changed have no effect on your emmc. Killing app processes is done by the system all the time constantly without you longpressing & such. Android just kills apps when it needs memory, so I don't see how forcefully doing that would cause issues. As for the Remove all Recent Apps feature, that will close the app without killing it. It's the exact same as swiping away all apps on that list. I just empty out the container's UI View and close each process in the array, using the existing methods provided in the framework.

From what I've read in your thread though it might not have been a fried emmc right? If your emmc was fried you wouldn't be able to reflash roms & such. Perhaps it was a corrupted cache?
[G2 and Desire Z Android Development] blk_jack:
Wish I could reproduce this on any Bluetooth devices myself. I've used Bluetooth on various cars (I rent & use car sharing services constantly), as well as with my FM transmitter and bluetooth speakers and never had an issue on any of them. One time I've had to toggle Bluetooth on/off after it seemed to be paring for a longish period of time, but it worked immediately after without issue.
[G2 and Desire Z Android Development] oVeRdOsE.:
Alright then, its maybe the phone.

Because with my milestone or my brother sII I had no problem to connect my devices.

- Devices for music are working (blutooth aux, car radio, wireless headphones)

- devices other than music are not, i.e. : OBDII readers, scala rider motocycle helmet blutooth device, handfree jabra, pc asus dongle, etc)
[G2 and Desire Z Android Development] XVI Ames:
I don't know, something corrupt somewhere, apparently...

Thank you for you answer!
[G2 and Desire Z Android Development] blk_jack:
Try this site here. The site is a mess but it suggests that those types of Nokia headsets store a total number of 2 "phones" and that you need to clear out that memory in the headset itself. I couldn't find anything specific in the logcat, so that might help.
[G2 and Desire Z Android Development] strikey17:
I will look into it. But the carkit is brand new and it works at first then just cuts out, disconnects...thanks for the link.
[G2 and Desire Z Android Development] redspeed:
Anyone having trouble with themes not applying to the lock screen? I downloaded several CM9 themes and it seems to theme everything else, but the lockscreen is remaining the same white color.

The strange thing is that when I go into the menu then lock screen setting and go to slider shortcuts, the theme does show up there...

Is there a fix for this in the works or a common bug with CM9?
[G2 and Desire Z Android Development] TauPan:
Did some Experiment today:

- full wipe, then install 1.5.0: no problem

- restore system settings via titanum: problem reappears

- fiddle with statusbar settings (in "system" and "andromadus" sections): problem disappears

- restore my backup before the wipe, install 1.5.0 over that: problem appears (no surprise)

- fiddle with statusbar settings again (see above): problem disappears

I can´t narrow it further down to one or more specific settings that might have been problematic, the statusbar stopped closing after I went through all the settings and changed + reverted them manually.

My conjecture is that the statusbar f/cd because one of my stored settings was incompatible with new statusbar code in 1.5.0.

I don´t have a logcat which probably would contain a useful backtrace. I´ll capture the log if the problem reappears for some reason (which I doubt), but for now Iḿ happy finally with 1.5.0. :)
[G2 and Desire Z Android Development] blk_jack:
This should go without saying and maybe I'm misunderstanding you, but it's common knowledge that you should never ever restore system settings through Titanium backup.
[G2 and Desire Z Android Development] Sketch85:
Hi guys. Is there a way to activate the Trackpad light for notification of new messages in ICS?
[G2 and Desire Z Android Development] TauPan:
That was just a step to reproduce the problem which appeared when I simply flashed 1.5.0 over the previous version without wiping.
[G2 and Desire Z Android Development] strikey17:
Bluetooth issues continued

I was wondering if, perhaps, the kernel may be to blame - CM 9.1, HTC Pyramid (Sensation) users reported that the Bluetooth cuts out when the phone goes to sleep.

http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority

Is this a possibility, and if yes, should I use OC/UV beater to raise the stock kernel's speed during sleep to try to fix this? Maybe, I'm just mixing things up. Thanks.
[G2 and Desire Z Android Development] blk_jack:
When the phone is sleeping it shuts off the cpu (deep sleep) so it doesn't matter what you set as a minimum frequency. Do you encounter this issue with the new JB test builds?

I just read that issue. If bluetooth is active the phone doesn't actually sleep, it remains awake for bluetooth. You could try switching governors with the OC/UV beater when screen is off to ondemand to see if it's a frequency issue.
[G2 and Desire Z Android Development] blk_jack:
Gotcha. Well, I think it was likely due to bad system data, something a full wipe would fix. But since you don't seem to suffer from it anymore after saving new settings it's not still a persistent issue, correct?
[G2 and Desire Z Android Development] strikey17:
Thanks, I'll try th3e ondemand governor and (maybe) narrow down the issue. But since the music streaming over Bluetooth works no matter what state the phone is in, I assume it's more of a profile or just general incompatibility issue with Nokia fw for its bluetooth head/ car sets. I'll try a JB test build sometime soon, need my phone for now with all the info loaded on it. Will report back.
[G2 and Desire Z Android Development] TauPan:
Yup, didn't see it again today. Thanks!
[G2 and Desire Z Android Development] DooSHeK:
I have one issue with the newest Mimicry. If I turn off "Mobile transfer" and turn it on after few hours it won't turn on. In settings it's shows that "Mobile transfer" is turned on but there is no transfer at all, no E,G, 3G or any icon symbolizing data transfer. I have to turn on and off airplane mode to get "Mobile transfer" back. I have newest radio and EdKeys .19 Radio lib-RIL/GPS updates.
[G2 and Desire Z Android Development] tarroyo:
Can anyone link me to the thread that explains how to use adb and logcat? I'm seeing frequent reboots, I think its due to underclocking too low and not overclocking being that I'm at 1024mhz under interactive governor, also seen this occur under smartass as well.
[G2 and Desire Z Android Development] demkantor:
Apps in the market if you'd like to use logcat on the fly, otherwise just plug your phone in with debugging turned on, open cmd and type

adb logcat

On a side note, simply typing

adb

Will give you a list of commands