[Q] Blurry Icon Text (sometimes) - Samsung Galaxy Nexus

It's sort of hard to reproduce, but once in a while my icon text would become blurry. This is sometimes combined with blurring of the clock. (See attached screenshots for details.) The blurring clears itself within a few seconds, and usually clears when I force a refresh (by opening new window or by rotating the screen), though not always.
I'm using the Codename Android ROM, but I suspect this has more to do with my sim card; the blurring started right when I started using the new one. Is it possible for sim card to have anything to do with this? Or is this definitely a hardware/software issue?
More to the point, should I be worried?
My clock apps are:
https://market.android.com/details?id=factory.widgets.SenseClockDark&feature=search_result
https://market.android.com/details?id=factory.widgets.SenseClock&feature=search_result
https://market.android.com/details?id=nl.jsource.retroclock.android&feature=search_result
Thanks everyone.

I don't see how the SIM card could ever create this.
It looks like corruption of the launcher. What launcher is included in that ROM? It looks exactly like the issues we had on alpha ICS ROMs for my G2. It was the launcher getting corrupted. I think it was a mix of issues with the GPU etc.. It always fixed with a launcher reload. Sounds similar to the issues you're having.

martonikaj said:
I don't see how the SIM card could ever create this.
It looks like corruption of the launcher. What launcher is included in that ROM? It looks exactly like the issues we had on alpha ICS ROMs for my G2. It was the launcher getting corrupted. I think it was a mix of issues with the GPU etc.. It always fixed with a launcher reload. Sounds similar to the issues you're having.
Click to expand...
Click to collapse
Darn, I see. According to the release notes for Codename Android:
Common: Launcher based on Trebuchet (nebkat) but with extra tweaks and changes - codenamedroid
Click to expand...
Click to collapse
Do you have any suggestions for how I might go about fixing this? (To be honest, I'm pretty much a noob with a new phone, so anything you could point me to would be appreciated!)

You should be checking to see if its a known bug for the release of the ROM you're running. If its not then you have to go and diagnose from there. Its probably a problem with how the launcher and GPU are rendering things.
You should post this in the ROM's thread to see if anyone else has this.

Thanks! I'll be doing that.

Related

Aqtrans' CM-5.07 port for Kaiser/Vogue! [v1.2] [5/27]

This is my port of Cyanogen's latest Eclair build, v5.07-stable.
It is basically mssmison's 5.07-test3 build updated, I used the same process he did to port this one.
Included Apps:
-Connectbot
-Astro
-RogueTools
-LinPack
-HomeSwitcher
Notes:
-No major problems found so far (besides Eclair-specific problems like the Camera not working).
-Speed is comparable to other Eclair builds, maybe even a bit zippier at times.
-It should be fully compatible with any themes/mods made for Cyanogenmod v5.07-stable. (Although my attempt at flashing this theme sent my phone into an "android.power wakeup" loop, so be cautious!)
--Darkstar theme isn't working either, thx for trying @thebulletfromhell!
-It is set to 120DPI by default, so if running anything other than 320x240, you'll have to use RogueTools to adjust it. I am currently running it at 320x240x120dpi and haven't experienced many problems, except the top and bottom of the Dialer are cutoff, button's still reachable though. (If someone wants to help me fix this, please do, I just don't know where to start)
-Wifi support for the Kaiser is built in, should work out of the box!
-Starting with v1.2, Userinit.conf is added to the root of your SD, by default it has 16MB of Compcache, but this can be adjusted by editing the file.
Download! [Last updated on 5/29/10]
Changelog:
v1.3
-Removed userinit.conf, now everything is run directly from /system/bin/userinit.sh
-32MB Compcache by default
-Removed overclocking from the get-go. You can set it manually via RogueTools.
-Userinit.sh now renice's com.android.phone to try and improve ringing delay.
v1.2.1
-Removed redundant wlan.ko
-Replaced wlan.ko with kallt_kaffe's
-Reverted a change to userinit.sh that was causing awful performance
v1.2
-Removed Dropbox, Speedtest, Twicca, Shazam, 3Banana Notes, and LiveWallpapers
-Added Camera back (Fixes FC when trying to crop a wallpaper)
-Fixed Facebook Sync
-Userinit.conf is added to the root of SD card on first boot. This allows you to control Compcache, swap, and many other settings.
Click to expand...
Click to collapse
Thanks go out to mssmision for his port+quick guide to porting, Cyanogen for the build, and all the other developers that worked on getting Android running on this phone! You guys have made this phone so much more usable.
Woah, it's weird being in a different forum.
What is updated in this new version (1.1)? I'm still running the first one you posted in the Vogue forums (on a Vogue) and it's working great.
Cool!
Gonna try this one out.
Thanks a lot!
pastaeter said:
Cool!
Gonna try this one out.
Thanks a lot!
Click to expand...
Click to collapse
Let me know how it goes.
drkow19 said:
Woah, it's weird being in a different forum.
What is updated in this new version (1.1)? I'm still running the first one you posted in the Vogue forums (on a Vogue) and it's working great.
Click to expand...
Click to collapse
The updated version has wifi working for Kaiser, and some compcache tweaks done to /system/bin/userinit.conf. The first version I think I disabled compcache entirely, and it really showed once you got the build fully loaded.
any screens? how to install themes on Kaiser? Little guide please...
just downloaded going to give it a try
all live wallpapers dont work and show force close (exclude polar clock)
but its cool and fast (default it set at 450MHz and i set it to 500MHz)
Bench at 500MHz: MFLOPS:2.141
Times: 2.53s
Norm Res: 3.36
Precision: 2.224...
Maybe you add-in many of not neccessary app..
and one very good thing.. i have i think 320x428 and 120DPi in RogueTools. and its less blurry than thats sets in myn
Congrats for good rom.
exist CM with sense 2.1 on kaiser?
Compared to super eclair it has a few advantages:
-language dutch is included and fully working
-more options: look at call settings.
-market is fully working (for now), but no paid apps (super eclair market broke after using a time, not all apps can be found).
But less free ram.
Not really worth upgrading for me (I have 2 kaisers).
i've installed this build on my kaiser and it works great.
tested the wifi, the market, both work great. bluetooth turns on but i haven't had the chance to send or receive any files or to connect it to my wireless headsets.
did not test the data yet.
installed helix launcher and i think it moves a little bit faster than the regular home screen.
thank for the upload
mazz8y said:
any screens? how to install themes on Kaiser? Little guide please...
Click to expand...
Click to collapse
Here's a guide to installing to NAND. The build is not themed at all, so you can check out the official Cyanogen thread for screenshots, they should look identical (besides a smaller res).
Michga said:
all live wallpapers dont work and show force close (exclude polar clock)
but its cool and fast (default it set at 450MHz and i set it to 500MHz)
Bench at 500MHz: MFLOPS:2.141
Times: 2.53s
Norm Res: 3.36
Precision: 2.224...
Maybe you add-in many of not neccessary app..
Click to expand...
Click to collapse
Yeah I just noticed the Live Wallpapers crash, didn't try this out before. Not sure if it's possible to fix it, I don't remember them working on any other Eclair builds.
Also, I noticed that /system is running low on space, so I will definitely try to trim some fat by removing pre-installed apps.
Michga said:
exist CM with sense 2.1 on kaiser?
Click to expand...
Click to collapse
Not that I know of. But there is a QVGA Android phone with Sense coming out sometime this summer, and I'm sure someone will attempt to port it.
From the vogue thread...
Great build, I'm running it right now, and it thus far seems to be fast and stable! (bumped up the o/c to 500)
Two pieces of feedback...
If you can get facebook sync to work with the most current facebook app (the one with the "inbox" button rather than the "take photo" button it would be amazing. As of now, the only way to get facebook sync to work is to run the Moto Droid apk, which is the previous version.)
Anyway to get full market from the getgo? I have marketenabler working, but it isn't always consistent.
That being said, amazing build. Good work.
Click to expand...
Click to collapse
@GeJohnO: Looks like this is a known issue with the original Cyanogen
A few known issues;
* Facebook from market breaks sync for Market users (see forum for alternative apk) - only on Dream, Sapphire is OK. Blame Facebook.
Click to expand...
Click to collapse
I'll look into including whatever alternate APK in the next build.
Also I found that taking out the Camera app causes Gallery to FC when trying to crop a wallpaper, so I'll fix that as well.
I just got a text message from the 24th of this months with super ecalir lite, I don't know if this version hzs those issues too?
aqtrans said:
This is my port of Cyanogen's latest Eclair build, v5.07-stable.
It is basically mssmison's 5.07-test3 build updated, I used the same process he did to port this one.
Included Apps:
-Connectbot
-Twicca
-3banana Notes
-Astro
-RogueTools
-Dropbox
-LinPack
-Speedtest
-MetaMorph
-HomeSwitcher
(I will probably cut this down a lot in future builds, kind of made this for my own personal use and threw in all the Apps I usually reinstall)
Notes:
-No major problems found so far (besides Eclair-specific problems like the Camera not working).
-Speed is comparable to other Eclair builds, maybe even a bit zippier at times.
-It should be fully compatible with any themes/mods made for Cyanogenmod v5.07-stable. (Although my attempt at flashing this theme sent my phone into an "android.power wakeup" loop, so be cautious!)
-It is set to 120DPI by default, so if running anything other than 320x240, you'll have to use RogueTools to adjust it. I am currently running it at 320x240x120dpi and haven't experienced many problems, except the top and bottom of the Dialer are cutoff, button's still reachable though. (If someone wants to help me fix this, please do, I just don't know where to start)
-Wifi support for the Kaiser is built in, should work out of the box!
Download!
Thanks go out to mssmision for his port+quick guide to porting, Cyanogen for the build, and all the other developers that worked on getting Android running on this phone! You guys have made this phone so much more usable.
Click to expand...
Click to collapse
Add the darkstar theme to not working as well. It put it in a permanent loop
thebulletfromhell said:
Add the darkstar theme to not working as well. It put it in a permanent loop
Click to expand...
Click to collapse
The darkstar theme hasn't been released for 5.0.7 stable. The most current release is for test5. This may be why it's not working for you
I tried mssmison's test 3 out, and it was problematic. A lot of stuff would end up resetting the phone, back to the start up animation. Haven't tried this one yet, but my experience with Eclairs have been bad so far.
Wish there was a way to run Android on both NAND and SD cards. That way, I can test them out on the SD card, without destroying my NAND installation.
Running this port since yesterday and I must say I'm really impressed. Fast, responsive and also it seems not to drain battery as fast as other builds.
Any chance of getting Corporate Calendar in the next version (currently Exchange sync works only for Mail and Contacts in this build).
Version 1.2 posted! Changelog in the OP.
I tried adding the modded Market, but it kept FC'ing whenever an app would go to install. Looking at the thread, it seems like a known issue, without a fix that I could find
robuser007 said:
I just got a text message from the 24th of this months with super ecalir lite, I don't know if this version hzs those issues too?
Click to expand...
Click to collapse
I haven't experienced any such issues. As far as I know, I've been receiving texts on time, without delay.
thebulletfromhell said:
Add the darkstar theme to not working as well. It put it in a permanent loop
Click to expand...
Click to collapse
Added a note to the OP about this. Thanks!
aqtrans said:
Version 1.2 posted!
Click to expand...
Click to collapse
Suggestions for 1.3
- Remove /system/etc/wifi/wlan.ko (not needed)
- Replace wlan.ko /system/lib/modules/wlan.ko with the attached version (I believe it works better for Polaris users)
I was about to suggest increasing the wlan scan interval but I noticed that you hade allready done that.
I've had problems with builds that have sensors.msm7k.so all by itself so I added the sapphire sensors before I installed v1.1 as a precaution but I'll try without doing that once I reinstall with v1.2 and I'll let you know how it goes.

[Q] Launcher Pro/ADW running slow/choppy with widgets...

As title states, both launchers run pretty slow and choppy when running several widgets. I'm running last night's "nightly' with Pure Messenger and Pure Calendar widgets, along with stock news widget and feedr widget. After first reboot all is smooth, but after several minutes things become really really slow/choppy. I'm guessing it's a memory issue, but what specific settings do I need to adjust to smooth things back out? I'm sure I'm not the only one to experience this.
thanks guys,
Alan
Definitely sounds like a memory issue. You might have to cut back on a few things.
But first, try running the Snap kernel (I'd recommend 7.5-925) and see how that works for you.
drmacinyasha said:
Definitely sounds like a memory issue. You might have to cut back on a few things.
But first, try running the Snap kernel (I'd recommend 7.5-925) and see how that works for you.
Click to expand...
Click to collapse
Yea, I'm pretty sure it's memory related although I don't have that issue with Fresh's latest rom. I will try the snap kernel to see how that does...worth a shot.
thanks

Screen Artifacts

Here's a weird one....
Samsung Galaxy Nexus...unrooted,
I downloaded Beautiful Widgets and for the first time used there live wallpaper(open gl version),
Noticed today a lot of screen artifacts ie. Letters being dropped and unreadable,
I've factory reset the phone and all seems OK now,
What the hell happened ?
Cheers in advance
Sent from my Galaxy Nexus using Tapatalk
I think I might be having the same issue. It seems if my phone is running and I lock it for a while. Then unlock it after it's been sleep. All of my widgets are showing garbled pixels all over the screen. Then when I reboot the issue is gone. The next time it happens I'll take screen shot and see if you or anybody else is having the same issue as me.
Also using BW but reading this I'm scared to use their LWP, let us know how it goes, did BW cause any reboots? Fishing here because I'm not sure if BW is to blame or not.
Mine has rebooted a few times but I've found nothing to blame it on yet.
BTW no artifacts.
Sent from my Galaxy Nexus using xda premium
Hello mate...it was probably more of a coincidence than anything, I'd had bw on for 24hrs then this happened so very possibly a very big coincidence
I found after a factory reset it spot on again....
Maybe I'll try the bw lwp again and see how it goes.
Sent from my Galaxy Nexus using Tapatalk
Hey. This is kinda old but I am having similar issues.
I also have BW but Ive had it for about 3-4 days and just started experiencing this today. Only changes I have made today was auto-flashing franco-r116. This could just be a coincidence I suppose.
I managed to catch a screenshot. Its tough because it comes and goes rather quickly, mostly when im scrolling through stuff.
Really dont want to reflash
I just posted in a different thread with the same issue and I'm also running Franco nightly 116. I guess I need to revert back to M2.
Sent from my Galaxy Nexus using XDA
Good to know. Ill reflash M2 aswell and report back here if problem persists!
If you are running R116 and you are getting artifacts then maybe your gpu can't handle the overclock, one version is 384mhz and the other is 512mhz. If 512 gives you artifacts use 384, if 384 gives you artifacts then you will have to use a milestone Franco kernel because that is stock gpu, 307mhz.
This was my first thread (screenshots included).
Since then it's been an intermittent problem on Apex and Nova Launchers. Not on launcher 7, however, and not on the new miui launcher, and (as far as I can remember) not in any app besides the launcher. The problem also seems to be exacerbated by having lots of widgets, though naturally it's hard to measure since it only happens intermittently.
aLogCat also comes up with "OpenGL is out of memory!" when these things occur. The problem seems to transcend kernels and GPU overclocking (my device seems to be bad at CPU overclock, and I've never tried it seriously).
I think that narrows it down to: launcher issue, widget issue, usage issue (maybe it's being strained too much at a particular time), or some combination.
My current best hypotheses (or suggested solutions, sort of):
1) http://stackoverflow.com/questions/9412662/how-can-fonts-cause-opengl-out-of-memory-error i.e. certain widgets have fonts too big. This fits with your usage of BeautifulWidgets and my large clocks. But it doesn't always cause an issue, or for everyone.
2) Large grid (in my case, 5x4). One of the common denominators for Apex and Nova, but not MIUI, is resizable grid. As such, I'm currently in the process of testing 4x4; it seems to be able to handle more strain, but since it's intermittent I'll have to try for longer time to be sure.

touchwiz micro stutters

Hi guys I got my Rogers Galaxy S3 2 days ago (i747M). For the most part it is buttery smooth. But I notice that sometimes touchwiz has some micro stutters when moving between home screens. I also notice that while switching between home screens, before entering the home screen that has the Gmail widget, theres a quick minor stutter. Can anyone replicate this?
The way I did it was, first use the internet browser for a bit then go back to the home screen. After start moving between home screens and see if you have and stuttering before entering the home screen with the Gmail widget.
Is this a problem with the widget?
Extra information: I am on stock, un-rooted.
This is normal. I also experienced this with stock ROMs. Something that will help mitigate this issue is if you flash a custom ROM that has the scrolling cache disabled (such as Kyan ROM. There are others, but I know this one off the top of my head because I have personally used it). Though they do not go away fully even with the new ROM, the fluidity of the interface if greatly increased.
The only way that I know of to make this go totally away is to flash AOKP or CM10 as they have implemented project butter with great success.
caveman999 said:
This is normal. I also experienced this with stock ROMs. Something that will help mitigate this issue is if you flash a custom ROM that has the scrolling cache disabled (such as Kyan ROM. There are others, but I know this one off the top of my head because I have personally used it). Though they do not go away fully even with the new ROM, the fluidity of the interface if greatly increased.
The only way that I know of to make this go totally away is to flash AOKP or CM10 as they have implemented project butter with great success.
Click to expand...
Click to collapse
This may be a bit off topic but, I know nightlies for CM10 are out.. But do you think we will get the stable version of it? I notice for CM9 we didn't get the stable version.. That kinda worries me a bit because I like cyanogenmod and the progress they made with CM10.
big_doubleT said:
This may be a bit off topic but, I know nightlies for CM10 are out.. But do you think we will get the stable version of it? I notice for CM9 we didn't get the stable version.. That kinda worries me a bit because I like cyanogenmod and the progress they made with CM10.
Click to expand...
Click to collapse
I wouldn't worry about it. We haven't gotten a stable version of CM9 yet because the Galaxy S3 came out after CM was well into its development cycle. Also, with the release of Jellybean source code, there isn't a huge incentive for the CM team to continue working on getting a "stable" build released (stable is in quotes because a lot of their nightlies are actually pretty stable). I have been running task and ktoonsez's AOKP for a while now and I have to say that their 8/20 version is quite superb. It offers much more customization that CM10 currently has and I would highly recommend it.
Yes I have this issue as well, I also am flashed on KyanRom, there isn't as much stutters, but they still happen here and there, even when I close an application, sometimes my widgets on the page it goes to look as though they've disappeared, but come back. I also experienced this while being unrooted. So far, don't know anything that can fix the issue to the fullest. I think lowering down on the amount of widgets on the home screen can help. But who doesn't love widgets?
Papaniz said:
Yes I have this issue as well, I also am flashed on KyanRom, there isn't as much stutters, but they still happen here and there, even when I close an application, sometimes my widgets on the page it goes to look as though they've disappeared, but come back. I also experienced this while being unrooted. So far, don't know anything that can fix the issue to the fullest. I think lowering down on the amount of widgets on the home screen can help. But who doesn't love widgets?
Click to expand...
Click to collapse
Guess will have to wait till Jelly bean comes out. I'm sure project butter will get rid of 99% of lag and stuttering.

Lockscreen Lag

Hi,
I'm on the Tmobile H811 G4.
I have a rooted custom rom, and i've debloated most of my non-essential apps by freezing them via Titanium backup. I also use a custom launcher, (Action Launcher) which doesn't lag at all. Generally I don't have any lag issues. However, it's only on the lockscreen. B/c of work requirements, I have to use the PIN security login, and when I tap the buttons for the PIN, it lags. I'm talking maybe a 1/3 of a second, but strangely for the last 3 or 4 digits (out of the 6) that I'm using. There's a lag also when I press the OK button.
It doesn't happen all the time, just once in awhile.
I used to use a oneplus one with CM12.1 and compared to that fast, smooth lockscreen login, there's definitely a noticeable lag.
Btw, I do also have the force GPU rendering on as well.
Is anyone else experiencing this? If you have in the past, and resolved it, any tips?
Other than this, I really like the G4. I've tweaked it also with the G4 tweaks, and overall it runs well.
Thanks in advance.
I'm seeing the same lockscreen lag. Seems insane that entering four digits should produce such stutter.
Not really seeing any lag or stutter elsewhere (on Google Now launcher), except perhaps ad-intensive pages in Chrome, but that's true of most phones. Oh, and when I use tap to wake (whatever it's called), I double tap once, nothing happens, double-tap another time, and presto it wakes up. Every time, the first attempt fails.
Overall my stock N5 seems a bit snappier, but no real complaints with the G4.
Mostly I just miss the perfect size of the N5.
I too am experiencing the same issue. Seems that I can finish typing a full sentence on the keyboard before I can enter 4 digit pin! I do not get it this phone has 3 gigs of ram and it still lags.
alextop30 said:
I too am experiencing the same issue. Seems that I can finish typing a full sentence on the keyboard before I can enter 4 digit pin! I do not get it this phone has 3 gigs of ram and it still lags.
Click to expand...
Click to collapse
You can have 32 GIgs of RAM, if the software which handles the operations has flaws. This issue is caused by LG's software mods most likely the launcher.
davebugyi said:
You can have 32 GIgs of RAM, if the software which handles the operations has flaws. This issue is caused by LG's software mods most likely the launcher.
Click to expand...
Click to collapse
You are right, I should know this as a software developer! It is funny when I call LG about my issues they tell me that there are no known issues with the phone (lag and missed taps being the most prevalent). They also will not acknowledge that their software is crap, this is why vanilla android is better - I think I trust Google developers a bit more than LG - which I have come to the realization that the only thing I will trust them with is to make my next TV.
alextop30 said:
You are right, I should know this as a software developer! It is funny when I call LG about my issues they tell me that there are no known issues with the phone (lag and missed taps being the most prevalent). They also will not acknowledge that their software is crap, this is why vanilla android is better - I think I trust Google developers a bit more than LG - which I have come to the realization that the only thing I will trust them with is to make my next TV.
Click to expand...
Click to collapse
Missing taps are because of the touchscreen firmware is buggy, which is mostly noticeable on the JDI panels, rather than the own LGD (yep, LG using two different display manufacturers - which is very common by every OEM nowadays, some even use 3). That said, having a LG's own display panel with the latest firmware I never had a single missing tap.
On the other hand, if you want unique features in your software, you have to pay the price. Still, Samsung is worse at it than LG (that's why I changed from a S6 - 920F).
But back to the topic - I stopped experiencing the lag (and operation lags in general), once I switched to my all-time favorite Nova Launcher Prime. LG's default launcher is great in terms of functions (more functions than Touchwiz and Sense Launcher IMO), but had re-draws and lags here and there probably because of the poor code.
They can ship without a default launcher TBH, since I always change to Nova in the end (Also did on my HTC M7, Z3compact, Oneplus One, S6).
However, this still does not change the fact that LG needs to improve a bit on their debugging and performance optimization.

Categories

Resources