I flashed a CM nightly several weeks ago and my phone went to h*ll. I had to go back to square one and re-root, unlock again, etc. to get the phone back to operational.
Can anyone tell me if they have the current CM working normally on their SIII these days? I tried to look at reviews through ROM manager but that doesn't seem to be working.
I know everyone's experience will be a little different. Just tossing this out to see if it generates a bunch of little replies with experience.
Thanks!
******* EDIT ***** I just found the long CM 10.1 thread... I'll try and find my answer in that. Sorry if this counts as a "duplicate post."
Hey guys,
My phone has been acting weird lately. It starts by, lets say, lagging.
I reboot the phone and it gets stuck into a reboot cycle... Great. The only way to fix this is to restore a back up.
I tried reinstalling the rom a couple of times, which resulted into the same problem after a couple days of use.
I've also tried the bubba kernel which, again, resulted into the same problem.
Some specs:
S-OFF, Supercid, HBOOT 2.15, RADIO 1.11
Not sure which ones are actually relevant, but I mentioned it anyways
Any suggestions/questions are welcome. Anything. Thanks for reading.
Well, since you have SuperCID and S-Off you clearly have a basic knowledge of what you are doing. I can only think that it is the kernel or the ROM. I'd never mess around with a kernel, because that is probably the only thing I trust HTC on, that's why I've kept stock. Have you tried another ROM? You might be madly in love with the appearance and the functionality of the ROM, but if it is laggy and is causing you to have to repeatedly restore backups, then you are best off using a smooth one. I also use the CM10.1 nightlies, and I agree with that. If you are seeing screen tearing, then that is not your phone being a retard, that is a known bug that they are going to address. However, some suffer worse than others. My One S is at the grand age of one year and is suffering quite badly from it, yours may not. Also, if you're talking about the RAM dropping from around 350MB at boot to around 150MB in 24 hours, that's pretty normal too.
The screen tearing is rarely noticeable, its actually almost non existent.
Im running the cm10.1 kernel that came with the rom.
I did try ViperOneS but it wouldnt even go further past the splash screen throughout the first reboot after installation in Aroma. Did flash clear fastboot cache and flash boot.img but it didnt work so I gave up on that, lol.
This morning I decided to back up my current rom and restore it after wiping everything, something I only do when installing a new rom. So far my phone is behaving like it should.
I just opened the thread to get help when needed and to get idea's as to why it's behaving like that.
Thank you for your response
Sent from my One S using xda app-developers app
Somebody who has a greater knowledge on this subject than me, most likely usaff, will pop up within the next couple of days and give you some better help than I could. I've only known what I'm doing for a couple of weeks, so I'm new at it, but since I'm a bit of a noob I can give advice that noobs will understand. Since you're clearly not a noob, I didn't help that much.
Maybe some more info is/can be helpfull.
Wich nightly you running?
You say it runs for few days, then you get problems, So it runs correct after initial install.? If So, what programs do you install/use (wich might cause tot make it unstable)
Can you tell how you install the ROM in steps.
Verstuurd van mijn HTC One S met Tapatalk
I haven't experienced this problem in a while anymore. I think a full wipe/reset did the trick before restoring a back up. Thread may be closed
Hi, This I my first post at XDA and also my first custom rom, so forgive me if I am less than detailed..
I recently flashed the above Slimbean Rom to my phone, barring some changes, it has been great, except for this one issue. The phone kept rebooting quite often (almost ~1 per day), and over the last week I have come closer to what I think is causing it.
During uninstall/updating apps, if the app in question is running, or in memory, it is quite likely that the phone will crash n reboot.
Is anyone else having this issue? Any way for me to fix it? Not a major issue for me, but still frustrating nonetheless..
Hey guys been away from the XDA scene for a while, first I got my Galaxy S1 a year or two back and knew nothing about android, a bad 2.3.3 update brought me through the bricked phone Nightmare which I was able to fix on my own with some help from this forum. Since that day I've been playing a lot with these devices had a lot of fun fixing them, and modifying them.
I had already been running Cyanogen for a while on my S1, and picked up an S2 i9100M last year for about 30$ from a friend, great condition but the 2.3.3 was something I had got used to not using anymore. Installed CM on the S2 and been running it since.
The phone runs really well but I have some recent concerns I noticed while traveling and such. Specially the WIFI reception is one of the biggest things I noticed a huge difference with more recent devices running stock roms and IPHONES that all get stable 2-3 bars when I struggle to get reception.
Is this linked to a weakness in CM? Is this just a device that is starting to get a little old for today's wifi appliances? Bear with me here, I notice the custom roms section has a bunch of roms but CM is not listed. Have people moved on and CM is a thing of the past? What are the biggest differences I might experience when changing to a whole complete CUSTOM ROM, what things might I dislike?
Thanks for taking the time to clarify things with me!
Hi all,
Firstly, I have a Motorola 4G LTE peregrine.
Over the last couple of days I've followed the guides to the best of my ability to be able to install a custom ROM.
I unlocked the bootloader via the official Motorola way, rooted the phone, and installed TeamWinRecoveryProject. I'm trying to install a variety of ROMs but having no luck.
The only ROM I could install was Slimkat (SlimRom). I would like to use eithe SlimRom or CarbonRom for their no-nonsense simple firmware and for maximum battery life.
However I'm finding continuous issues. The biggest is that there's a constant moving flickering line that runs down my screen on TWRP and the SlimKat rom.
Slimkat also does struggle to load as well. The first time I flashed it, i got through to the first time setup menu but got bombarded with Google service failures. The second time, it now seems to be stuck in a boot loop of just flashing the logo.
Anyone know anything about this flickering line and why ROMs are failing to install?
This is very frustrating. I am not a phone user who wants to spend hours trying different roms. I liked when phone's were phone's and not much more. The sheer level of micking around I've had to do to get here and have outcome is frustrating and ridiculous as it is. I loved Kitkat and my phone auto upgraded me to Lollipop which I hated - Lollipop ruined my phone and made is borderline unusable. Right now, I just want to have a phone that's simple and trouble free.
Really appreciate any help here. Please treat me like an old nan of yours who doesn't know technology too well. I'm still learning. Sorry kids! (even though I'm 24 Lol).
Thanks folks!
upgrade to the latest bootloader with this tool
the flicker will dissapear
or just lock and unlock your device