Related
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.
Hi
Looked for this issue on the forum and can find instances of it happening occasioinally, but not with the frequency that i have. Symptomns are that the screen will stop responding to input. I.e the screen stays painted but does not respond to my pokes or pros. Flicking the screen on and off for a split second fixes it. I believe its related to software or resource usage -sometimes i can go for ages without issues, however in the last half an hour this has happened around ten times. please help!
I have tried isolating it down to a particular app with no success, and also changed the CPU governance settings, asgin unsuccessfully. I have no such issues in WebOS.
Thanks.
ps running CM9 alpha 2, but had same issue on 0.6
flash the latest nightly.
screen unresponsive281]flash the latest nightly.[/QUOTE]
Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...
Thanks
the latest nightly offers quite a few fixes.....
including vibration from sleep and tons of other stuff. not much can go wrong.
Andysan said:
Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...
Thanks
Click to expand...
Click to collapse
There has been loads of improvements in CM9 wifi has been fixed sound distortion when the screen off is fixed many speed fixes we now have themes working
Do a nandroid backup in CWM then copy that to your pc for safety then wipe system partition DO NOT FACTORY RESET OR WIPE DATA or you will lose you data, then flash latest nightly and latest gapps then wipe dalvik cache/cache partition's then in advanced fix permission's and reboot system
Well.... I dip my hat to you guys.
Went ahead and installed the latest nightly - even if it doesn't fix my issue, I was suprised by how polished it felt compared with Alpha 2. Typically with bleeding edge stuff I'd have expected to have more issues, but alls I had to do was reinstall YouTUbe and flash the gapps-fixer zip for my Calender sync, plus I see lots of lovely new settings to play with.
Will report back if the screen hangs again, here's hoping...
Frustratingly this issue has started happening for me again running 31 May nightly - touch screen has become unresponsive half a dozen times in the last ten minutes.
Maybe trying wiping it and doing a brand new flash from the latest nightly. (I know it sucks to reinstall stuff, but maybe there are some leftover codes that is causing trouble.. )
i agree either to wiping data or up your min cpu speed as it might the amount of apps you have installed that auto start/resume when turn on the screen..
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
I only had that problem once. Rebooted by holding home and power never had it again.
Sent from my YP-GI1 using XDA
Had this issue yesterday for the first time since installing cm9 6(?) months ago.
Tried a nightly build as suggested, but given the rarity in the first place, can't be sure it's fixed
This happens to me all the time across all ROMs I have tested.
This happens in OaT's and turning the screen off/on, fixes it temporarily.
This happens in Butta, but turning the screen off/on does nothing. I have to reboot using power/home.
I have also been unable to find a specific app that causes it, but it does seem to occur more often in graphic intensive games.
I can go for days without it happening, then BAM, it stops responding to touch, from that point forward, no about of reboots or full shutdowns seems to fix it for several hours. I'll reboot and sometimes it'll be immediately, sometimes it will be 3-5 minutes, but it will happen again.
Then a few hours later it'll stop happening and I'm good for a few more days.
Do those of you using CM9 find that screen off/on fixes it, or do you need a full reboot?
I am running the night lies and have to say that the only time I experienced this was with the may nightlies. I have not experienced any issues with the 7/04 nightly.
Sent from my cm_tenderloin using Tapatalk 2
Interestingly enough I think I found out what causes the screen to stop responding. When the TouchPad is locked in landscape and then I turn it portrait while its still locked, then the screen becomes unresponsive. Does that make sense?
Sent from my Touchpad using xda app-developers app
I take it back. The screen became unresponsive even in landscape mode. There goes my well formed and thoroughly investigated theory.
Sent from my Touchpad using xda app-developers app
---------- Post added at 07:54 PM ---------- Previous post was at 07:22 PM ----------
I've been using Nova Launcher ... I switched back to Trebuchet and it appears to be working normally. Of course I may be spouting this half-cocked like I did before. What launcher are you using?
I run SPB 3D launcher and do not experience any response issues with the latest nightlies. I use my touchpad constantly as a laptop replacement so mine gets a workout every day. To my knowledge, no one was ever able to find any one app that was responsable for this behaviour but it was noted in earlier builds.
,
Sent from my cm_tenderloin using Tapatalk 2
I too still have this issue - as per others, fine for days, then it will occur consistently and I keep having to screen off/on and eventually it stops of its own accord. Am sure its a software issue, but someone here says they also had it in WebOS and HP provided a replacement.
http://rootzwiki.com/topic/20740-screen-unresponsive-in-cm9/
For me as simply flapping the screen on/off fixes it and I've never had the issue within WebOS, it has to be software - this started as soon as I first installled CM9.
Bump - still no fix identified for this by anyone with this issue please?
To anyone still following on, followed nevertells advise and completely started again from scratch and it happened after about twenty mins of using the stock browser. I think i've tried not using that app before so am just going to assume that this is either a software bug or a hardware issue that only manifests itaelf within Android
I´m having quite a frustrating problem. Tried to search the net for hours, only finding a handful of people with the same issue but no solution. So, I wondered if anyone can help me out here? The problem is that my clock is not updating while screen is off. Naturally, this affects all alarms and notifications as well.
20:15 -> I adjust alarm to 20:30 and put the screen off. I press power right after the screen has gone off, and see the lockscreen.
Lockscreen informs it´s 20:15 and the alarm is set at 20:30.
20:30 -> Nothing happens.
20:45 -> I press power. Clock says 20:15 for a second. After one second, it shows 20:45, and the alarm starts ringing.
So the problem is quite easy to identify- the clock doesn´t get updated when screen is off. The moment I switch it on -seeing the lockscreen- it gets updated and acts accordingly if any alarms or notifications were to ring at the period it was not updating. However, it´s much less easy to find out what´s behind it. Could anyone spare me a hint here?
I´m running a rooted P7300 with CM10, 30/10 build. Using Tasker to underclock while the screen is off in order to preserve battery life. I thought that caused the problem, but while leaving the CPU untouched....
01:00 -> Switching tablet off, putting alarm at 9:00
09:10 -> Wife wakes me up instead of the alarm. I press power.
Clock says 8:48 for a second. After that second, it gets updated, shows 9:10, and the alarm starts ringing.
I´m getting a little clueless here, so any help would be appreciated.
Running rooted P7300 with CM10 (30/10 build).
Cheers, Henu.
EDIT: Ok, I´ve come to the conclusion that this freezing happens when entering Deep Sleep. If that could give anyone any clues?
Works on CM10 version 11-11
Hi,
I can confirm that it works correctly in CM10 from 11-11.
I only have one weird problem left: the device drains more power when turned of than in standby.
I have been running the 11_11 build since it was released and had not had clock issues until today. I am not overly technical and have no clue why it is happening again. But for as smooth as this rom is I will live with it.
When mine gets confused on time it will not reset itself once i wake the tablet up, it stays messed up until I manually fix it.
Sent from my GT-P7310 using Tapatalk 2
Launcher ?
Do you use the stock launcer? Mine did strange things when using the apex launcher. No problems with stock launcher from cm10.
I am using the stock launcher but have installed nova and thinking about giving it a try
Sent from my GT-P7310 using Tapatalk 2
You could try the clock sync app from the play store. It worked on my phone when it had clock sync issues with a rom. Unfortunately, i'm new to xda, so I can't post the link, but just go to the play store and search for clock sync. It's by Sergey Barinov.
Thanks, but unfortunately none of this methods helped- I´m still having the same issue even with the 11/11- build, running Clock Sync as well. Anyone could shed any light here? I wish I wouldn´t have to go back to some (yuck) stock version.
I don't know if this will help but I just resolved this issue for myself. I did a factory reset. And also wiped all caches and system before flash. Then immediately after flash before rebooting system I wiped everything again except system. And then I started up and there was no issue with the clock. I'm running cm 10. I hope this helps.
Sent from my HTC One X using xda app-developers app
Sounds like voodoo but I´m all in for trying even that. I will post the results tomorrow.
To confirm:
1) Basic superwipe procedure (factory reset/ system, cache, dalvik)
2) flash OS -> don´t boot yet up to OS like normally
3) wipe cache & dalvik
4) THEN reboot -> to OS?
Voodoo, baby.
It worked. Seriously, what the hell. My wild guess is that some file(s) might be corrupted in the actual package- and when the system notices they are missing at the first boot, it will replace them with working ones. Then again, I´m no Android/ Linux expert.
With a clean install, I ran alarm after 8 hours. Worked. Then I added Apex Launcher, waited 2 hours. Alarm went on. Installed everything again with Titanium Backup, put alarm after an hour. Still worked. So I can confirm that it´s not app- dependant but OS- dependant. However, it worked, so thanks a goddamn zillion!!!
Congratulations. Just happy to help.
Sent from my HTC One X using xda app-developers app
I´m going to snap this piece of junk into half soon.
The problems came back, no reason why. I´m now trying one more thing, which is completely disabling Tasker, as it´s basically the only thing running while the screen is off. If that doesn´t help, i´m clueless.
EDIT: What a surprise, it didn´t help. So, it´s either non- functioning CM10 or stock ICS. I could had settled with CM9 easily, but that gave me the battery bug after two weeks. Seriously, this whole me- buying- a- tablet- and- getting- it- to- work has been a living joke. I just would love to have a stripped down OS with a Kernel supporting "all sorts of stuff" like processor speed, running app restriction, tweakable backlight etc.
Ok, so I wiped cache and dalvik and it worked for a couple of hours. Then last night the clock froze again. And this was quite interesting..
Alarm set at 10:30
I wake up 11:15 (hey, it was New Year´s Eve )
I press power and the clock says 11:15 and next alarm is set "tuesday 10:30".
Two seconds later the alarm hops into "wednesday 10:30".
Two hours later I press power, and the clock is 11:15 for a second and jumps to real time. So it´s definitely broken again.
I was just wondering- maybe I could try replacing the clock with another kernel´s version, would that be possible? Any help would be much appreciated.
EDIT: I also tried -once again- without automatic time& date (as my connectivity is set to cut off while the screen is off) and it still didn´t alarm me until I manually pressed the screen on.
EDIT2: Ran A1 kernel, no effect, still bugged.
EDIT3: Ran Tracid´s official ICS. Worked for a day, then bugged. Same thing with A1 kernel. I also had some serious issues with MTP connection and bootloader, so I restored stock and brought it back to the store where I got it for warranty repair. They think it´s a faulty MoBo.
I´m shamelessly bumping this. I ran the stock firmware with Odin and took it to the repair, as I wrote earlier.
Got the tab from warranty repair, seems that the only thing they had performed was "software update" . Very useful for someone who is constantly switching ROMs etc... like I hadn´t tried that before.
After returning to stock and all, I installed CM10 again. And "surprisingly", the problems started again. With or without apps, launchers, cachewipes, younameit. I´m now giving this a test with the stock ROM for a couple of days. I actually hope it doesn´t work, because that would be the only reasonable thing now. If it works with the stock ROM, I´m getting clueless. Does that mean I have some sort of issue which happens only in flashed ROMs instead of the stock one? That would be just....awkward.
Dear Xda Forums
I have to say this is the first question that I post, after some years of use of this forums, but I couldn't find what I looked in the search section, perhaps I didn't search correctly.
Long story short, I had a Xperia X10 which was easy enough to root, but with the Samsung Galaxy S3 it was a total madness, specially since I forgot to backup my IMEI, rom and kernel problems, etc...
After testing some ROMs, I settled with the stock ROM, which I quite like and used the Boeffla 5.2 Kernel for Android 4.3.
The perfomance improved greatly, however, sometimes the device just freezes in a black screen, just like it was locked, and the odd thing is that the LED that flashes when a notification is pending, still is flashing, like the device is in perfect condition. I try to unlock it with the home key, wait, then with the power key and wait again, and nothing.
Sometimes it just freezes in the contacts or message apps.
UPDATE: I now see that one of the most serious problems is that the device freezes (black screen+flashing green light) when charging, which is very troubling because I charge it through the night and it is my alarm clock.
The only changes that I made to the stock rom (apart from root and kernel change) was to install Yahoo's Aviate.
Maybe it was very n00by of me to change the Kernel in the stock rom, but if indeed I was, is there any way to flash the Kernel again? Or is it a problem between SuperUser and Knox? ( I have used the terminal to disable KNOX and the problem persists).
Thank you.
OmniROM
Lollipop - Android 5.x
A new "unified" Galaxy Tab 2 section was added to our forum because we don't make a difference between p31xx an p51xx specific roms.
Please use the Thread here for Omni 5 related questions and feedback
Reserved
Downloads:
Unofficial Builds by me
ROM Downloads for all supported devices can be found here
SuperSU http://download.chainfire.eu/supersu
GApps:
by @Deltadroid http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
or http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
Can't wait to try this out. Loved omnirom ROM 4.4.4 on my tab until I tried your recent SlimLP ROM on it
Sent from my Nexus 5 using Tapatalk
New builds late this evening
Send from OnePlus One using Tapatalk
Android-Andi said:
New builds late this evening
Click to expand...
Click to collapse
Will definitely try this out - Omni 4.4.4 was perfect - I expect nothing less here (over time of course). Thanks Andi.
Builds are up
Send from OnePlus One using Tapatalk
FYI... Cant get it to boot! First tried with dirty flash from SlimLP then a clean... But no luck. Get stuck on bootscreen...
cheeseous said:
FYI... Cant get it to boot! First tried with dirty flash from SlimLP then a clean... But no luck. Get stuck on bootscreen...
Click to expand...
Click to collapse
Likewise with a P5113 here, booted first time after clean flash with pico Gapps and supersu 2.40... but after first reboot and 2 force reboots... still hanging on boot screen with a blank faced android blinking and wondering. Black to SlimLP for now. Thanks again Andi.
Lolli!
I installed the latest build and its working great in my P5110
I didn't even had any major bug yet (Only clock app not working)
Android-Andi said:
Builds are up
Click to expand...
Click to collapse
Reporting: Did an update from last years version.
Wiped C + DC
Flashed Rom + SuperSU
Rebooting .... took approx. 7 minutes ... done
Settings done,
Reboot,
Stuck at boot logo ... left for about 15 minutes
Wiped C + DC again,
Rebooted successfully this time.
Used for an hour or two, than reboot again, stucked at boot logo again...
After wiped C + DC again without no apparent reason: Booting successfully.
Restoring SlimLP with TWRP. Will test next build Andy when available.
@Gregzi thx for testing. I'll run new builds tonight...
Send from OnePlus One using Tapatalk
Testing Build 20150107
Testing latest build:
- Clean flash Rom + Gapps + Supersu 2.40
- Boot time reduced to 3 minutes
- Setting everything
- Noticed that SuperSU is this time correctly pushed into the system (in previous builds I had two:
one in Launcher and one in Settings ==> sometimes problems with root - TBackup)
- Shutting down the tablet
- Booting - again stuck at Omni boot animation (left it for about 10 minutes)
- Force reboot to TWRP (with two button combo)
- Reboot into the system from TWRP without cleaning anything
- Booting normally in 1 minute
When OC the frame rate is now 32,8 fps (Nenamark2), so better than previous builds, so certain progress is done.
The tablet feels smoother - especially noticeable when opening app drawer.
BR
installed over omni 4.4.4 without wipe.
first boot took about 40 mins, updating 173 apps.
some bugs:
firefox beta won't run
home button does not work
still collecting experience, but it doesn' t look too bad ?
Cheers and thanks alot, s.
sent over omni
sebastel23 said:
installed over omni 4.4.4 without wipe.
first boot took about 40 mins, updating 173 apps.
some bugs:
firefox beta won't run
home button does not work
still collecting experience, but it doesn' t look too bad
Cheers and thanks alot, s.
sent over omni
Click to expand...
Click to collapse
Home button gets fixed by flashing Gapps!
DarKnighT916 said:
Home button gets fixed by flashing Gapps!
Click to expand...
Click to collapse
thanks, but actually i had flashed Gapps (pico) already just after the ROM.
however, i'll try again later. :fingers-crossed:
in the meantime, i re-flashed gapps, with no change in behaviour.
for the time being, i'm back to 4.4.4.
bt issues
cannot connect bt headset. other features working fine, any toughts
only a question
I have a p5110 and runs pretty well but I've a problem with the minimum brightness it's very dark I can't see anything. any solution?
I loaded the 1/29 build last night on a clean install (with the latest Nano PA Gapps and SuperSU install zip, all on Andi's latest TWRP build). So far so good, here's a few observations:
-The first boot took a pretty long time but from what I've read this is normal. I didn't reboot again until the next day but for the second boot, the bootanimation never loaded, it just went straight from the brand logo to the launcher, long black wait in between. After that, all fine. Later I loaded the stock lollipop bootanimation I had been using previously (I do like the omni one a lot, though), and it used to lag a bit at the end on 4.4.4 but now it runs smooth all the way through, so that's encouraging.
-Turning the screen off (or letting it time out) is usually buggy, the screen flickers on/off for a second instead of any type of animation (I believe Lollipop is supposed to do a monochrome fadeout?) Edit: On closer inspection I see it is doing the monochrome fade, but then the screen flashes at the end of the animation.
-Re-installing apps was painfully slow and seemed to hang if I let the screen turn off (I'd find it sitting on the same install several minutes later). Downloading seemed a lot slower than KitKat ever was, too. I looked at the stats in settings->apps->running at on point in the process and the Play Store was listed as Restarting, perhaps this indicates poor memory management? Running the app in the foreground didn't seem to help at all, though.
-The material updates to the stock browser app are pretty swanky, I'm a fan. (I saw that in the gerrit and got excited. Not done yet but looks great.)
-Cast screen doesn't seem functional, doesn't find my chromecast. I've tested both Netflix and Localcast to connect just fine, LocalCast was a bit finicky the first time I tried but I think that may have been a network issue.
-I was testing a video call in in Hangouts and tried to mute the sound (was testing with my phone in hand and there was audio feedback loops because of that), but couldn't. Using the volume buttons, it wouldn't go all the way down, and if I dragged the bar the rest of the way it just wouldn't stick. Not sure exactly which volume control that was (lollipop's sound settings still confuse me in general), but I think it must be a bug of some sort that it wouldn't go down to mute.
-I had only just got around to trying to use my tablet's IR blaster (P5113) for TV control a few days earlier, and I found that the top several smart remote apps in the store don't work at all. Peel actually forces a soft reboot when it gets to the "push this button to test turning the device on" step, consistently. I did get one app working, which only includes remote IR support as a secondary function, TV Guide by Mini Group. Unfortunately the app isn't quite polished enough to be useful to me, but it was notable that it just worked where the others all get nothing. I didn't re-test all of the apps on lollipop but the ones I did(both of the ones linked here and a couple of the others that didn't work) behaved the same way.
-Visual performance generally seems a bit laggy but overall performance is fine (i.e. animations may freeze or lag but the tasks they're covering up don't suffer). Maybe all the animations in lolipop are just a bit rough on older hardware? I find them a bit overdone now that I've played around with things a bit more, personally (not that this reflects on the ROM). I don't really like stuff like shadows bouncing around as I scroll menus, though some of them are a nice subtle touch.
Overall I was happy with KitKat, but I think I'll let lollipop grow on me, these quirks are all minor. Idle battery life seems a bit worse but it's hard to make that call, I've been fiddling with the tablet more than usual to test things anyway.
Edit: Actually after letting it sit overnight unplugged, the idle battery is better than I was ever getting on KitKat. Granted, I made a point of closing all apps before and I think on KitKat I was having issue with casting apps holding wakelocks overnight and that's yet to be tested, but 1% over 12 hours is a pretty damn good baseline. Not sure what caused that wifi drop towards the end, after holding the connection (it gets a good strong signal) for about 11 hours, though.
Hey together!
Seems like we have some faulty eMMC chips, some reports of broken devices appeared.
I pushed a commit to address the issue and prevent other devices from damage.
I will recompile latest Lollipop roms and recoveries within 1 week.
For more information please read http://forum.xda-developers.com/showthread.php?t=3016879
Follow the instructions please to check your eMMC information.
Best regards and wishes!
Andi
Send from OnePlus One using Tapatalk
Internet sharing (mobile hotspot) doesn't work