Related
Hey I have recently upgraded my G1/dream on t-mobile to cm lastest stable and after the up grade it says I have 3G signal and when I load the market I can see the featureed apps
Ps it was working the first time I flashed and I was running DRC92 downgraded to RC7 then flashed to cm
Thanks
Net Connectivity Problems?
I'm also having issues this morning with getting on Market, as well as web pages thru browser... and come to think of it, I haven't gotten any Gmail notifications either.
I'm on T-Mo w/ Nexus One running CM 5 beta 3 (2.6.29 non-memhack'd), but I don't think the custom ROM is the issue.
Can anybody else verify connectivity issues on T-Mobile this morning?
i've had this issue... but mine stuck. i was hopping between dwang and cm. they were both nandroid backups and i was testing themes on them to see what worked and what didn't. anyways i got done and restored my cm build and market just wouldn't connect. however if i opened it and hit menu > downloads quickly it showed them briefly before saying there was an error connecting which i take as it meaning there was a connection, but there was something interfering with it. only way i was able to fix it was wipe and reflash cyanogen. :/
hey i had droid wall installed, un-stalled it then it was working again i think it was either a problem with t-mobile or droidwall was stopping it
Yesterday I upgraded from nightly 28 to 35. My GPS was working fine, but after the upgrade I don't even get the icon in the notification-bar.
To get it working earlier (some build before nightly 28) I had to boot into a Sense-ROM, get a fix and boot into cyanogenmod again. Do I have to do this again now? Or should I do some other trick?
Fixed it by flashing the radio from this thread: http://forum.xda-developers.com/showthread.php?t=1008384
Did a search but have not seen any thread on this, so apologies if I have missed something.
I've just encountered this today and not sure what to make of it. i9000 been on CM9 nightly without issues until I woke up this morning, backlight was on (nothing unusual, just emails overnight), but it will not wake up no matter what I pressed (home button, power button etc.). So ended popping the battery out and start it up again.
This is when the strangest thing happen, loaded the usual Galaxy logo screen, then into the CyanogenMod screen, seconds later, it restarted. This boot loop went on forever. Doing VOL UP + HOME + POWER does not get me back into recovery. At this stage, I am on CM9 nightly 20120707, with CWM 6.0.0.3 (I think).
I ended up having to Odin flash back to GB 2.3.6 (XXJVU) and start over again. And I thought that was the end of it. Picked up the latest nightly 20120728 and RC2, and I ended up with the same symptom. I.e. post WIPE (Data / System / Cache) and loaded CM9 of both version (plus Gapps loaded), all ended in the aforementioned bootloop. Have also tried fixed permission as well in between tries to load CM9.
Spent a bit more time on this and I am now on the unofficial CM10 (not that I am complaining ), but this is very strange to me. Has anyone ever experienced this? It seems that I have no way of getting back in CM9.
I was running cm9 nightlies until I flashed cm10 (which is amazing ) and had no issues with it what so ever :S
I don't think I've heard of any cases of what happened to you, happening elsewhere
I'd just stick with cm10
Happened to me, too. I solved the problem flashing a previous build of CM9 and a previous build of Gapps - it seems like Gapps was the problem.
After popping out battery, insert batt., start download mode, Odin flash Semaphore ICS kernel as PDA, re-partition unticked.
Enjoy
The Semaphore dev has a thread about this. A number of people have experienced what you say with a combination of different ROMs and kernels. Check it out on development thread
Sent from my GT-I9000 using xda premium
Cheers for the reply fellas. Will check out Semaphore. Interesting though as I've always thought "stock" CM9 was just easy as.
Hi,
I'm switched over to the latest OmniROM nightly (Currently 20140125) for my Find5 but discovered a bad wakelock I never experienced before. It keeps the phone in a wake state like 95% of all the time.
sns_periodic_wakelock
Google and Forum search for it showed up several possiblitys, I tried to eliminate them all. Today I completely wiped my phone and installed the latest Omni nightly on a blank device with TWRP + Core Google Apps without installing any other additional app to it.
And still the sns_periodic_wakelock was there. So it must be caused by something related to google core apps or omnirom itself.
Did anybody discovered something similar with Omni Rom on find5? I never had this before on non kitkat roms.
EDIT: THIS WAS RESOLVED IN THE NEW 20171231 NIGHTLY, EVERYTHING WORKS PERFECTLY NOW!
So I have this problem with Lineage OS 13 on my N10, so I flash the following packages:
Super SU 2.78
Busy-box
Open Gapps 6.0 nano
Lineage 13 10/14/17 nightly
The first boot is successful, I install some apps, watch some videos, normal tablet stuff. The problem is when I reboot, every time I reboot it ends in a boot loop. The tablet just won't boot up after I reboot it. The first boot works great, but nothing works after-wards.
Doesn't work on mine either, with CM13 20171017 build. I also made comment on the CM14 build thread here on XDA. I couldn't complete the initial setup using the CM14 build. I'm going back to stock.
I have the same problem with 20171021
I was able to reproduce the Error and attatched a logcat.
The bootloop always started while installing the App "immobilienscout24".
Hope someone can examine my logcat. I attached 2 (split) files, because I don't know, what is relevant.
Best regards
In my case the "BlueMail"-App cause the bootloops. After a factory reset LOS13 works fine, at the end of the install process of BlueMail Android restarts and bootloops. Deleting the bluemail-folder via TWRP solves the problem.
Frank
BerlinOtto said:
In my case the "BlueMail"-App cause the bootloops. After a factory reset LOS13 works fine, at the end of the install process of BlueMail Android restarts and bootloops. Deleting the bluemail-folder via TWRP solves the problem.
Frank
Click to expand...
Click to collapse
So basically I have to pick my apps wisely or lineage will reboot? **** that noise I'd rather run stock lollipop, lineage on my N10 is awful.
Again bootloop at the current nightly version. Official Lineageops version is slowly evolving to crap. I switch to the unofficial nougat version!
I have the same issue of constant boot loops. I tried several LOS nighly build w/o any success.
Funny thing is, after i rolled back to an old CynogenMod backup (v13.0 snapshot from 21.12.2016) it started to boot loop too, after I started updating my apps with Playstore.
So the bug must be very old, and it must be in CM/LOS, not in some specifiy app...
Folks, there is a defect open in the official lineage bug tracking system. please add your comments there - maybe this needs some more support to get looked at:
https://jira.lineageos.org/browse/BUGBASH-1075
Marktplaats causes boot loop
In my case, 'marktplaats', a dutch app, caused the boot loop. At some point I decided to upgrade to Lineage. I never had any issues on Cyanogenmod 13.
There seems to be a solution for this Problem in the newest nightly, See
https://jira.lineageos.org/browse/BUGBASH-1052
I've done a test Installation with my two Problem apps and it works fine for me.
I0tacle said:
Again bootloop at the current nightly version. Official Lineageops version is slowly evolving to crap. I switch to the unofficial nougat version!
Click to expand...
Click to collapse
All the problems were fixed in the in 20171231 nightly, running it without hitch no, stable and fast MM with CM theme support, finally