I have tried various ics roms. But seems everyone with tegra d00 cant seem to get it going. So decided to start a thread for if someone figures out how to get d00 going with any ics rom. The screen tear and cant turn screen off and get it to come back seems to be the problem i get with all the different ics roms. So from what i read its kernel issue. so any d00 fixes or tweaks please post in here.
I have the same and there is no solution for that until a proper kernel is written/ported.
Sent from my MB860 using xda premium
I have two Atrix with same tegrapart and almost same serial number (was bought and delivered together, from same shop). One of them works with the ics rom, other don't (have the screen lock corruption bug).
i have d00 with no screen tear, main problem was battery ...
i have D00 also...
no problems to get the ROMs work...
now using AtrICS v2...
except of fast battery drain, no probs so far...
same here AT&T version with d00 and no problems apart from fast drain and heating
So the real problem is not the tegrapart type? What is it then???
I can not use any of ICS roms due to screen tearing and black screen issues.
Sent from my MB860 using xda premium
dedebekri said:
So the real problem is not the tegrapart type? What is it then???
I can not use any of ICS roms due to screen tearing and black screen issues.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Mine is a d00 with same problems. I gave up using leak based ROMs for now.
I'm using Th3Bill's ParanoidAndroid latest build and that is an awesome ROM. No fingerprint, no Chrome and no VPN, but the rest works pretty well and, using the Tablet UI all the time (with 160 DPI) I have a good lapdock experience also.
[URL ="http://www.updatemymoto.com/"]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL]
---------- Post added at 05:23 PM ---------- Previous post was at 05:15 PM ----------
epinter said:
I have two Atrix with same tegrapart and almost same serial number (was bought and delivered together, from same shop). One of them works with the ics rom, other don't (have the screen lock corruption bug).
Click to expand...
Click to collapse
Epinter, do you have any clues about the real reason of those problems?
[URL ="http://www.updatemymoto.com/"]
[/URL]
I have the d00 tegrapart. I've tried both AtrICS 1.0 and v2.0. Functionally everything worked great except for the short battery life and excessive heat but it had continuous reboots. The reboots would get progressively more frequest with time to where after about three days it would start rebooting about every five minutes with it just laying on my desk without me even touching it.
Lately I've been going back and forth between 2.3.6 stock and CSROM...patiently waiting for a stable build.
I don't know if anyone else has had this exact experience but I've been able to run several of the roms based on the ICS leak and as long as my atrix is plugged into my computer via usb, the roms seem to be fairly stable. Within 5 to 10 seconds after I've unplugged it, it reboots and continuously bootloops. The weird thing is that even when it's plugged into a stand alone charger it bootloops, it has to be a computer for it to be stable at all.
I have d00 and I am currently using ICS MROM. It works great so far. Battery is not draining that much.
epinter said:
I have two Atrix with same tegrapart and almost same serial number (was bought and delivered together, from same shop). One of them works with the ics rom, other don't (have the screen lock corruption bug).
Click to expand...
Click to collapse
hmm so maybe tegra part has nothing to do with it working or not. is there any other # or even clockwork version we can compare from working/nonworking d00 user?
Related
I installed the cm7 with gapp and ec09 modem yesterday. Battery was draining so I went back to stock and installed it again today morning. Around dinner time today, I heard a soft ringing coming from my phone. So soft that I could barely hear it. Nothing worked so I did a battery pull and it went away. About 2 hours later, that ringing came back.
Can anyone tell me what's wrong and a solution to get rid of it?
Thank you~
A few other people have experienced the phantom ring, but last I heard it was gone for most people using CM7 test 11. What kernel are you on, and did you come from DL09 or EB01?
I had this problem back when CM7 was in its early test builds. The problem was (supposedly) remedied back in build 6
*** Update 07/04 ***
fixed deep sleep wake-up issues
updated to latest CM code
attached fixed recoveries below
Click to expand...
Click to collapse
As stated above if you could post the build number (test #) along with your kernel that would give us a starting point.
Like JT said it was an issue with the phone not waking from a deep sleep state when receiving a call. I can tell you that on my phone with the current CM7 build, ED05 modem, and Glitches V11.1 kernel I have not had this issue surface once.
Sorry to necro this thread.
I am running CM7 on my fascinate, nightly #34, jt kernal, and using ED05.
About once or twice every ten phone calls my phone does this described continuous ringing, except its quite loud. It doesn't stop until the phone call ends, and usually I have to tell them I'll call them back so I can hear them.
Has anyone had any similar issues? I wanted to report in the CM7 thread, but cannot.
Thanks
cb3ck said:
Sorry to necro this thread.
I am running CM7 on my fascinate, nightly #34, jt kernal, and using ED05.
About once or twice every ten phone calls my phone does this described continuous ringing, except its quite loud. It doesn't stop until the phone call ends, and usually I have to tell them I'll call them back so I can hear them.
Has anyone had any similar issues? I wanted to report in the CM7 thread, but cannot.
Thanks
Click to expand...
Click to collapse
I had the same problem, I think the last nightly I had #27. that and call volume forced me to go PWGB
PWGB
xAirrick said:
I had the same problem, I think the last nightly I had #27. that and call volume forced me to go PWGB
Click to expand...
Click to collapse
Good Job mate
I just experienced this last night on JT's Vanilla Gingerbread v7 using his included Kernal. Had to pull the battery. So far it has only happened once.
I get it right before the ringtone. I had it happen when my phone was on vibrate. I have had it happen when I answered the phone it kept ringing. I am running OMFGB nightly 8/25 with Glitch's V12 beta kernel. It has only happened a couple of times but goes away. Not much of a problem.
quite annoying. my phone is on vibrate most of the time, and this happens often enough that it drives me insane.
To clarify what I mean by "it":
1. Phone continues ringing after i pick up the call
2. phone rings on its own, usually when someone is trying to reach me, but I don't actually get the incoming call. Phone keeps softly ringing till I reboot it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had that happen once or twice on build 35. You mentioned being on CM7 and ED05, so I assume you're referring to the ED05 radio only, correct? If that's the case I recall reading here or on rootz that since CM7 is GB-based, it is advisable to use the EC09 radio with it; ED05 is Froyo. Can't guarantee it'll solve your problem, but I personally haven't gotten a phantom ring since...
Sent from my SCH-I500 using xda premium
Holy crap, not 10 minutes after posting that, I got the phantom. Consider my previous advice worthless.
Sent from my SCH-I500 using xda premium
I installed Powerwashed GB and the phantom ring has yet to return after 5 days. I used to have it every day on CM7
... about two weeks ago and I love it so far, best phone I've ever owned hands down. The only problem I've experienced is the battery... for example after a full charge, I surfed the web non stop on 4g (hspa) for an hour and 30 minutes and my battery is already down to 65%. Is this normal? My brightness wasn't even high, it was slightly less than half... seems kinda weak considering just about everyone says this phone has the best battery life of all high end Androids.
I'm on 2.3.6
My kernel version is 2.6.35.7
My build number is GINGERBREAD.UCKK6
Thanks in advance!
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Hour and a half of screen on time, not to mention data consumption, yeah that's about right. It's all based on how much you use the phone. Here's a screenshot of my battery life:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Light use
Miui 2.1.6
Siyah 2.6.6i kernel
Supercharger V6 1000hp script
I average 20hrs of battery life, this was just a test to see how good the battery is.
Sent from my SGH-I777 using xda premium
It may be some other stuff as well. Look in the link below to see if you have any of the known battery drainers. I was suprised at what was causing a lot of my battery drain and after deleting the offending apps/services, I'm getting great battery life.
http://forum.xda-developers.com/showthread.php?t=1308030
2.3.6 on the GS2 has known battery life issues. You can Google "2.3.6 battery life issues" to find links that I'm unable to post here. When originally on 2.3.4, I experienced great battery life - on par with my old iPhone 4. When I upgraded to 2.3.6, battery life was significantly reduced whenever I was connected to wifi (battery drained with the screen off as though I was actively browsing on it).
I concur with what audiotweaker states. You can always go back to a 2.3.4 kernel, easiest way is bundled with a ROM that currently loads that kernel.
jermneedscoffee said:
I concur with what audiotweaker states. You can always go back to a 2.3.4 kernel, easiest way is bundled with a ROM that currently loads that kernel.
Click to expand...
Click to collapse
Um, kernel has NOTHING to do with it. UCKK6 or UCKH7, they all use a 2.6.35.x kernel. Changing the kernel will do NOTHING to change the drain - it's a problem somewhere in the system image, not the kernel.
I did a simple root without any custom ROM using this method: http://forum.xda-developers.com/showthread.php?t=1311081
I had auto upgraded to 2.3.6 from 2.3.4. Using the method in that thread will root your phone + downgrade the OS back to stock 2.3.4.
I am having better battery life since then because of
- ability to better optimize the battery after rooting (Titanium bkp, access to Alarms log through BetterBatteryStats, ability to disable auto start of certain tasks using Super Manager, etc)
- OS 2.3.4 instead of 2.3.6
- misc other battery optimization techniques floating around on xda
Technically, 2.3.6 in general isn't the problem - it's the UCKK6 build specifically.
I don't think the I9100 2.3.6 bases have as many issues - BTHID still broken, but at least it seems like they have less drain issues.
Entropy512 said:
Technically, 2.3.6 in general isn't the problem - it's the UCKK6 build specifically.
I don't think the I9100 2.3.6 bases have as many issues - BTHID still broken, but at least it seems like they have less drain issues.
Click to expand...
Click to collapse
(This was about the first week when I got the phone before I rooted)
I actually was able to talk to a few people at my local AT&T retail store. A few of my friends actually work there as well. I was talking to them about the battery life and they told me it wasn't actually 2.3.6, it was the build that comes with the phone (factory).
Then I got home, flashed a CFW. Battery now lasts about 2 days with just basic web browsing and texting.
So i recently got my S2 a few weeks back. before this had.an Optimus One.
I put my hutch sim in this one and for the past 1 week my bars keep fluctuating between 0 to 4.
Now i am on vodafone and my entire family uses the same.
Neither of them have a problem.
Also I never had a problem on my P500.
Also recently I had received an OTA of about 20mb, still on ICS though.
After that update I have been getting random freezes, cant change lockscreen wallpaper, not even with quickpic. TwWallpaper keeps crashing and this signal trouble.
Adding a few screens.
Taken on the same spot. Also right now my sister is getting constant full bars!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So i was wondering what should I do?
1. Replace my sim?
2. Visit a service center?
3. Rollback the update, if yes, how?
Also I'm on Stock, non-rooted. ICS 4.0.4.
SGS2, send this you must!
Given it's a new phone, your problems have been caused by a carrier pushed update & your warranty is still good, the 2nd option (tho if it were me I'd probably mess with it anyways because I don't really care about warranties).
Re: S2 Network/Update issues.
So most probably its a software issue?
If so I guess I have my reason to root and install a recovery coz even I couldn't care less about warranties..
one thing though, like my P500, once rooted, the root can be reversed as well, right?
Also is there any way without root to rollback this update?
SGS2, send this you must!
Re: S2 Network/Update issues.
Hey vj the signal drop problem is a common issue on Vodafone network if you want you can try to change your s2 modem to see if will gonna improve your signal .
Use this thread http://forum.xda-developers.com/showthread.php?t=1656005
Or you can try to root your phone using this method that I used http://forum.xda-developers.com/showthread.php?t=1501719
Then you can try another Rom
Sent from my GT-I9100 using Tapatalk 2
thanks man!
I switched to GSM only since 3G plans are way expensive here anyways, also since I'm on wifi usually.
And haven't seen a drop since then, hope it stays so!
Also network issue aside I sometimes find the metal around the camera getting hot while gaming for more than 30-40 minutes.
Is it normal or should I go ahead and flash that modem, since it boasts of nominal temperatures at all uses?
And OT, are you also an ex-P500 user? I seem to remember you seeing around on xda. And I have been on OT & P500 forums only prior to SGS2
that heat is a normal effect for our s2 when we play a game or a movie and if you gonna flash that modem your phone signal will gonna increase and the heat will lower (tested by me)
OT : yes i'm an ex p500 user you'll gonna see some work for it in my signature and an rom port (not in my sig )
Hey all,
My battery life has gone to sh*t in the last couple days, and I have noticed in my battery usage settings that the top contributor to its demise is always "Shell" (screenshot below).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here are my specs:
----------------------------
Samsung Galaxy S4 AT&T
Cyanogenmod 10.2 (09/22/2013 nightly)
Rooted
Sometimes when I reboot, "Shell" does not appear for a while, but I have not been able to pinpoint what triggers it to start. I tried wiping and reinstalling CM, but it still shows up. The battery drain is so bad, in fact, that unless I use the original wall charger that came with the phone, the battery life still decreases while charging.
I am posting this in general Android questions because I literally have no idea what is causing it. It could be a CM bug, it could be an app I installed that's doing something malicious (Lookout doesn't think so, however), or it could be something else I haven't thought of. I just wanted to see if anyone else has experienced this on any version of Android and get some help debugging. Even if you have ideas for how I can pinpoint the app/service that is causing this, I would really appreciate it.
Thanks!
aptbosox said:
Hey all,
My battery life has gone to sh*t in the last couple days, and I have noticed in my battery usage settings that the top contributor to its demise is always "Shell" (screenshot below).
Click to expand...
Click to collapse
I am experiencing the same trouble with my LG Nexus 4 with CM 10.2 nightly.
Edit: Actually it was the case with 20131001, but it seems Ok with 20131007.
Orome70 said:
I am experiencing the same trouble with my LG Nexus 4 with CM 10.2 nightly.
Edit: Actually it was the case with 20131001, but it seems Ok with 20131007.
Click to expand...
Click to collapse
Yea pretty sure it was a CM bug. I reverted to stable 10.1.3 and haven't seen the issue since. I guess that's what I have to expect for living on the bleeding edge I haven't seen anything about it in the changelogs, but if you say it's fixed, maybe I'll try the latest nightly.
aptbosox said:
Yea pretty sure it was a CM bug. I reverted to stable 10.1.3 and haven't seen the issue since.
Click to expand...
Click to collapse
I have a stock Nexus 4 ROM (rooted, but still stock), and I'm seeing 76% in "Shell" today as well, so it's presumably not related to CM.
Stock Nexus 5 and I had 55% drain over 5 hours today... What in the world is causing this? Never had this problem before.
1 day old stock nexus 5 and I'm having this issue...
Here's my post from another thread with screenshots:
http://forum.xda-developers.com/showpost.php?p=47257309&postcount=413
Anybody have a solution to this yet?
EboMike said:
I have a stock Nexus 4 ROM (rooted, but still stock), and I'm seeing 76% in "Shell" today as well, so it's presumably not related to CM.
Click to expand...
Click to collapse
What version of Android are you on? 4.3? 4.4?
aptbosox said:
What version of Android are you on? 4.3? 4.4?
Click to expand...
Click to collapse
There is no official 4.4 for the Nexus 4 yet. I'm on 4.3, JWR66Y.
Hi all,
I am currently using AntonX's unofficial CM11 for the P769, and its great except that like CM10.2 seems to be broken. In CM10.1 it worked perfectly and same with the stock ROM as well. So I decided to pull a few files from the stock Jellybean ROM and create a flashable zip that installs the old files that have to do with GPS. It seems to work pretty well as I was able to get a pretty good fix from a cold start in less than a minute using device only location settings, but it doesn't seem to work nearly as well as CM10.1 and stock. Does anybody have any ideas on how to fix this problem (I have already tried using different gps.conf files to no avail)?
Attached below is a screenshot of my latest GPS fix in less than a minute and the flashable zip that I created.
Thanks!
View attachment GPSFix.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think your files are the same as the ones already in the ROM.
What's wrong with GPS in CM10.2 or CM11 anyway? It never fails me, I always get a fix within a minute, even on a cold start.
As far as I remember GPS in CM10.1 was a little strange. I think I noticed that sometimes GPSTest was showing yellow bars but accuracy was in hundreds of feet, which actually indicated not a good lock. I may be wrong though, been a while.
Still a Problem
AntonX said:
I think your files are the same as the ones already in the ROM.
What's wrong with GPS in CM10.2 or CM11 anyway? It never fails me, I always get a fix within a minute, even on a cold start.
As far as I remember GPS in CM10.1 was a little strange. I think I noticed that sometimes GPSTest was showing yellow bars but accuracy was in hundreds of feet, which actually indicated not a good lock. I may be wrong though, been a while.
Click to expand...
Click to collapse
Yeah I think you're right that they're the same files because I was testing GPS again today and it would lock for maybe a second and then if I even moved, it would instantly drop. But this problem is definitely here because on CM10.1 and stock I would instantly have about 13-14 satellites in view, and be able to lock to about 7-9 of them in seconds, whereas now it takes about 1-2 minutes to get 10-12 satellites in view and lock to just five which instantly lose lock when the device is moved about 10ft. This is using the device only method of getting GPS so there is no use of wifi or cell signals to get the location because I have very spotty coverage. I just wanted to point this problem out as I've noticed it on other ROMs too such as BobZHome's CM11.0 and leolawliet's PenberRom5 which is also based on 10.2. Other than this little problem the ROM has been great and I thank you for your work AntonX!
On my P778g, i also noticed a diference between CM10.1.3 and CM10.2/CM11. But after some testing comparing to stock (my father has another p778 with stock rom) i discovered that the only diference is the signal strength: Under a clear sky the GPS works exactly the same but inside a house the roof is too much and the signal seems to be too weak, so it takes a lot more time to fix compared to stock. Keeping in mind that i never use the GPS inside my house this is not a big deal after all. I bet that no one is testing the GPS outside... try it.
If it wasn't winter and I paid my phone bill I'd be happy to go out now and test the GPS on my p769. I'm running omnirom tho, and I don't think it's cm based so I could have different results.
I'll post back here when I get a chance. By the way, the GPS on AOKP wasn't any better.
Sent from my LG Optimus L9 running OmniROM using Tapatalk