Related
i dont know why this is happening but every do often my icon text in the app drawer gets thrown off to the right. Any idea why this would happen? Im using the latest cyanogen mod with kspec theme. My phones only having that problem along with the 3g/EDGE issues, but im no business person that has to have 3g all the time so my main concern is the alignment with the icon text. I will try to get a screen shot if possible on here. But anyone know what I can do about this?
Thanks!
has been happening for me since stock. Unsure why, reboot usually fixes it for me.
Mine too, it happens sometimes and it fixes itself sometimes. (Had to reboot sometimes too) Does the rooted user has any experience with these ? Mine is stock
This is a pretty common problem with near all N1s, looks like an update from google is needed
I restart the device and everything become alright. Thanx all
Yes my N1 is rooted and i am running CM 5.0.5 i have the latest Amon Ra Recovery (Green Care bear) and i have the black Menu bar installed...come to think of it i didn't have these problems before i installed the black menu bar, but that might just be me being picky. who knows.
stock N1 does this, usually it messes up the text on an application that has just been installed
give it a try for yourself
eventually it seems to fix itself
Heh, remember this happening the first time when I installed Cyans rom. Scared me a little, but yeah, never had a time when a reboot didn't fix it.
Mine is stock, happens to me all the time but lately every app in the drawer goes bonkers. Just add it to the list I guess, I do hope the copious software bugs are fixed before any big update come out (like flash/ 2.2 in general) . Im going to really love this phone once the UI is stable.
Hi there everybody
I've installed [ROM][ICS 4.0.3][Unoffical Port] AOKP Build23 by vibranturk ROM.
Problems I found
1. android.media.process crashing always /almost every minute/
2. cant get in to market /meaning couldn't install any app yet/
3. cant get in to gallery
4. cant get in to music player
4. cant take secreenshot by default setting
5. sound is enabled but doesn't work. /not even play ringtones /
6. screen brightness not enough for day light
7. cant take photo by camera /android.media.process crashing/
Actually ROM is amazing. But without market its feels nothing.
Has anybody have same problem and about how to solve etc?
PS: I flashed 2 times.
You should start from fresh cuz not one problem that you stated has occured to me.....only bug is that when i reboot the batt % is off..
market works perfectly
...everything does atually
idk but just start fresh and wipe wipe wipe between flashes
i wipe before and after the flash
even flash twice just to make sure
***Dont mind the sig pic... im running this rom at the moment and its working flawlessly
jayRokk said:
You should start from fresh cuz not one problem that you stated has occured to me.....only bug is that when i reboot the batt % is off..
market works perfectly
...everything does atually
idk but just start fresh and wipe wipe wipe between flashes
i wipe before and after the flash
even flash twice just to make sure
***Dont mind the sig pic... im running this rom at the moment and its working flawlessly
Click to expand...
Click to collapse
OK. I'll try tomorrow. Thanks for quick reply.
I've been fighting with this 2 days. Today is day off for me.
Well. Today I installed again. This time it works fine. Everything went normal. Only one unusual thing is my cappy feels slow. asphalt 6 freezing sometimes. is there any way speed up my ICS?
ganaa1221 said:
Well. Today I installed again. This time it works fine. Everything went normal. Only one unusual thing is my cappy feels slow. asphalt 6 freezing sometimes. is there any way speed up my ICS?
Click to expand...
Click to collapse
Use Glitch v14, the included has some slight lag and glitch fixed it up. You can also LiveOC which allows for overclocking of the CPU and GPU.
signal
Has anyone found the solution for the gray\blue signal switching? So far as I can tell it is caused by the wifi; whenever I go from mobile network to wifi data, the signal bars go gray. The only work-around has been to switch airplane mode on and off. Would switching to the newly released glitch kernel do the trick?
EDIT: I have found out the Google services problem (gray vs. blue signal) is only happening when I join a network which requires a redirect authentication OR if the power saver is enabled.
Just got this phone and flashed it with - AOKP Build23 by vibranturk ROM
I have been reading for awhile now before I received the phone. Thanks vibranturk for all the development here! Excellent roms!
1) When I start the camera app from app on homescreen and from unlock - the phone goes into a black screen
The camera app worked fine again after a reset (just turning off and back on) but after awhile it does the same thing - black screen.
During the black screen, I can press the home button to return back to homescreen
** Resetted again, and all seems well at the moment and still fine after 1 hour!
2) I am not sure if this is the rom or just my screen. Did not notice it at first when i flashed the rom. Turning on the screen to unlock the phone, ie when the light starts, i get this bright green full screen flash for like a second. It does not happen everytime and no pattern of when it happens either.
Anyone else having these problems?
Can someone please update the 'AOKP thread in Captivate Android Development' with my issues, just trying to help with the development.
For the signal blue/grey thing, Seems like it goes blue for me when i have data signal coming in, either wifi or data enabled - lights up both wifi signal (only if wifi is on) and signal bars blue.
I have power saver is enabled as well.
My only issues so far are: vibrate + sound doesn't work, touch screen is over sensitive on certain games, and sometimes using Swype in messaging doesn't input if app was already in foreground when replying.(can be fixed by minimizing and reopening the app) otherwise it's works great. fast/smooth and great battery life.
So I just installed the Holics Rom yesterday and I love it! The only problem seems to be that it crashes very often. I've had to battery-pull it probably 8-10 times in the past 24 hours. It seems to happen most often when I lock the screen and then try to open it up quickly. Any one else run into this problem? Or could this be a problem with the AOSP locksreen?
Also, side question about the AOSP ICS lockscreen, is it customizable with widgets and shortcuts? It is beautiful, but I may switch back if I can't add shortcuts or get my music to pop up while locked.
lonehunter65 said:
So I just installed the Holics Rom yesterday and I love it! The only problem seems to be that it crashes very often. I've had to battery-pull it probably 8-10 times in the past 24 hours. It seems to happen most often when I lock the screen and then try to open it up quickly. Any one else run into this problem? Or could this be a problem with the AOSP locksreen?
Also, side question about the AOSP ICS lockscreen, is it customizable with widgets and shortcuts? It is beautiful, but I may switch back if I can't add shortcuts or get my music to pop up while locked.
Click to expand...
Click to collapse
Yes, I've been getting this issue on Holics pretty often during screen wake-up. I'm running 1.2 but had the same issue on 1.0 and 1.1. It will occasionally freeze when waking up with the power button. It also freezes when the screen attempts to turn back on after a call. It's very frustrating, bucause it's a very good rom, but this issue is driving me crazy.
I may have also had this issue on my stock rom with faux123 kernel. Maybe the Faux123 code is to blame. My lock screen is the ring by the way, so I don't think it's the AOSP lockscreen.
The phone never freezes randomly, it's always when the screen is waking up / trying to wake up. I have a feeling it may have to do with the single core 192 UC from the faux rom, unless the holics rom did away with that.
Miniloaf said:
Yes, I've been getting this issue on Holics pretty often during screen wake-up. I'm running 1.2 but had the same issue on 1.0 and 1.1. It will occasionally freeze when waking up with the power button. It also freezes when the screen attempts to turn back on after a call. It's very frustrating, bucause it's a very good rom, but this issue is driving me crazy.
I may have also had this issue on my stock rom with faux123 kernel. Maybe the Faux123 code is to blame. My lock screen is the ring by the way, so I don't think it's the AOSP lockscreen.
The phone never freezes randomly, it's always when the screen is waking up / trying to wake up. I have a feeling it may have to do with the single core 192 UC from the faux rom, unless the holics rom did away with that.
Click to expand...
Click to collapse
Do you know if devs are aware of this problem or working on it at all?
That's the only reason why I switched to DeSensed. It got annoying after a while.
I have been using 1.2 since it came out, and I have not experienced any random reboots or issues. I am using his kernel and am S-ON.
Sent from my HTC PH39100 using xda premium
I'm s-on and I've flashed with wcx recovery. Ive tried different methods of flashing the boot.img. Flashing it before and flashing the sd card copy afterward. I have also tried flashing either before or after. I did not select any UV. I chose the nonsense version of the install and am running apex launcher pro. I selected vram during install and disabled s2w. My CPU range is 384-1512 on setCPU, I am not running any profiles. I do use juicedefender ultimate and avast full time. I also have adaway installed. I can post a list of my other installed apps too if that would be relevant. Does any of this raise a red flag? Would the sense version of the Rom be more stable? Can anyone recommend another kernel if you believe that may be an issue? Any help would be appreciated as I do not have enough posts to state this problem in the dev forum.
Hi there,
I have a C6903 with 16GB of storage. Baseband 8974-AAAAANAZQ-10270045-39. It ran fine under CM12.1 from last year. I recently updated to a CM12.1 nightly from August of this year. After that I started having problems with random crashes.
The phone would either freeze during operating, not responding to any input. I had to hard reset by holding the power button for a long time. This shuts the phone down. Then I start it and it boots up. Or the crash happens, when I am not using the phone, resulting in a black screen and an unresponsive phone. The fix is the same, shutting the phone down with a long press on the power button and then starting it up.
I switched from CM12.1 to AOSP Jaguar LP 5.1.1 from August (I haven't updated to September yet). I was crash free for three weeks, but now I am back with the same crashes. I found four crash logs in /data/anr, but I can't make much sense of them. I have them attached to the post.
The change in behavior when I install a new rom makes me think this could be software related, but getting the same crashes with two very different roms makes it look like a hardware issue.
What do you guys think? I don't want to go back to stock for testing, because I value privacy a lot and XPrivacy is so much work to set up right, IMHO. I like the privacy managers included with Jaguar or CM12.1 a lot. They are so much easier to use. But if I have to, I will go back to stock. Any other ideas? Can anyone interpret the crash logs? Is there anything useful there? Should I test something else?
Please help. Thank you for reading this post.
SpGG said:
Hi there,
I have a C6903 with 16GB of storage. Baseband 8974-AAAAANAZQ-10270045-39. It ran fine under CM12.1 from last year. I recently updated to a CM12.1 nightly from August of this year. After that I started having problems with random crashes.
The phone would either freeze during operating, not responding to any input. I had to hard reset by holding the power button for a long time. This shuts the phone down. Then I start it and it boots up. Or the crash happens, when I am not using the phone, resulting in a black screen and an unresponsive phone. The fix is the same, shutting the phone down with a long press on the power button and then starting it up.
I switched from CM12.1 to AOSP Jaguar LP 5.1.1 from August (I haven't updated to September yet). I was crash free for three weeks, but now I am back with the same crashes. I found four crash logs in /data/anr, but I can't make much sense of them. I have them attached to the post.
The change in behavior when I install a new rom makes me think this could be software related, but getting the same crashes with two very different roms makes it look like a hardware issue.
What do you guys think? I don't want to go back to stock for testing, because I value privacy a lot and XPrivacy is so much work to set up right, IMHO. I like the privacy managers included with Jaguar or CM12.1 a lot. They are so much easier to use. But if I have to, I will go back to stock. Any other ideas? Can anyone interpret the crash logs? Is there anything useful there? Should I test something else?
Please help. Thank you for reading this post.
Click to expand...
Click to collapse
Your attachments show only general info about OS, but nothing related to freezing/crashes. Based on the fact that you were problem free on Jaguar for about 3 weeks, you might have the following:
You installed an app or mode that's causing this; you might have set up something in Kernel Adiutor (such as cpu voltage or what have you) that's causing problems; you might have restricted something in wakeblocker or an app like Xprivacy or any other Xposed module. Just think of what you did at the end of the 3-week-period. In Kernel Adiutor, untick apply on boot and reboot, so that default values could be loaded. If that doesn't help, disable wakeblocker...
optimumpro said:
Your attachments show only general info about OS, but nothing related to freezing/crashes. Based on the fact that you were problem free on Jaguar for about 3 weeks, you might have the following:
You installed an app or mode that's causing this; you might have set up something in Kernel Adiutor (such as cpu voltage or what have you) that's causing problems; you might have restricted something in wakeblocker or an app like Xprivacy or any other Xposed module. Just think of what you did at the end of the 3-week-period. In Kernel Adiutor, untick apply on boot and reboot, so that default values could be loaded. If that doesn't help, disable wakeblocker...
Click to expand...
Click to collapse
I didn't change anything. Same thing when I went for a new nightly of cm12.1 I did nothing out of the ordinary. Since I did not have new problems since the above mentioned, I didn't delve any further. Today I had another, interesting issue. No one was able to call the phone and I wasn't able to call out, even though the network showed up as fine with full bars. This lasted for several hours. I went into flight mode and back out of flight mode and the issue was fixed. Several SMS arrived about calls missed. And again, I have no idea if this was caused by the hardware, an issue with the software or even the network.
And that is the frustrating thing: How can I find out who the culprit is? Are there good system crash diagnostic tools? Because so far I haven't seen anything.
Hi all, lurker here.
I've been having an issue with my OP3T that hasn't really phased me until now. From time to time my phone would lock up and crash (phone shuts down unexpectedly). I would have to manually reboot the phone by holding the power down button.
I am running on OOS Beta 10, rooted with Magisk 13, EX Kernel and whatnot. This has happened prior to being on beta channel and root as well. I've read somewhere that this is a hardware issue that arises from SD821 clocking up to max Freq which causes the crash but I think even with the custom kernel and underclocking I am still experiencing lock ups.
If there is a log I can provide for you guys I can post it, just don't know which one.
Thanks.
I too was experiencing lockups and reboots, turned out to be caused by Substratum theme engine, removed it and now phone works like a watch ?
pitrus- said:
I too was experiencing lockups and reboots, turned out to be caused by Substratum theme engine, removed it and now phone works like a watch
Click to expand...
Click to collapse
I don't have Substratum installed
Yes , am also facing similar issue...
I am getting a blank black screen.,that confusing me that it get locked up or does it switched off...
I think the problem is in beta system updates....
shivagajavelli said:
Yes , am also facing similar issue...
I am getting a blank black screen.,that confusing me that it get locked up or does it switched off...
I think the problem is in beta system updates....
Click to expand...
Click to collapse
Damnn, i've got the same problem.. blank screen with white light notif then off, when 3T not get random shutdown they give me random restart every 2-3mins, aarrgggghhh really annoying!
same problem with my devices
And then whats the solution for these problem? Arrggghhh
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
dhuynh94 said:
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
Click to expand...
Click to collapse
Anyway which kernel?
I have the same with stock and beta OOS, stock and bluspark kernel. Never rooted. I though that maybe i just press power button in my pocket but then it happend on the desk as well.
Similar issue, sometimes black screen with unresponsive buttons (they do vibrate), sometimes I can unlock it via fingerprint to the home screen but touch is unresponsive, only appswitch via recents button works but can't exit the app with home button, sometimes it just reboots.
Never had these issues from dirty flashing from open betas but now when I started clean these things began lol. Seems more laggy too.
dhuynh94 said:
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
Click to expand...
Click to collapse
I just clean flashed all stock, pure without UBL, root but still same. Then tried to UBL, MAGISK + Franco Kernel, and still the same condition...
Ahhh i hate this phone! Really sucks
Hmm yeah I've had another crash but this just happened during boot.
Still have no idea what the possible cause is. Not aure why it's just us few that are experiencing this.
Maybe faulty hardware? Who knows
I used to have this problem when running the open betas for the 3t, I moved over to RR and there hasn't been any problems especially after the latest update
Edit. Also when turning on the phone the bootanimation (the two dots spinning around the thingy) it would freeze constantly, also fixed after moving to RR
My phone was crashed few times when using cameraMX application. I do not know reason, maybe last update fault? I have simple question, why we have beta version? Where is stable
Yeh I've had it freeze on multiple accounts while booting up. It would crash while the two dots are spinning and would need a hard reset.
Many times it would crash when entering my PIN for smart lock or lock screen as well..
Issue seems to have popped up again., after flashing OOS OB 14.
Most frequent symptom is after entering pin or unlocking device, at random times it would lock up Android and crash (shut down, not reboot). So I have to boot my device again by holding down power button.