yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] FandangoL:
Hello. I want share my experience. I moved from stock because i want try 4.2 new features, specially widget on lockscreen.

I first tryied cm 10.2 but battery drained quickly and gaming was so sloooow.I tryied then cm10.2 linaro but experienced 4-5 reboot a day. Now I'm back on cm10.2 hoping that the guy working on exynos drivers will bring good news. In the meanwhile I will try gustavo or apolo kernel that seems the most stable kernels
[Galaxy S II General] Fadil56:
Waiting S4 UI port into i9100G ...
[Galaxy S II General] hellco:
I have found only 2-3 Roms that can be used

I can say that i have installed allmost all posible ROMs. For me every rom whit verson of android above 4.1.2 just didn't work ( i have SD CARD problems in most of the ROM's in other i have encored camera problems or bootloops ) The only ROM working realy good is snapdragon and s4fors2 .

IF ANY ONE KHNOWS HOW TO SOLVE MY SD-CARD PROBLEMS ON ANY ROM WITH ANDROID VERSION ABOVE 4.1.2 PM me PLS
[Galaxy S II General] ryderpavan:
CyanFox Rom is the most stable and worked for me as well. Give it a try!!

For Battery Backup, maybe you can use Voltage Control Pro App, Underclock to 1 GHZ if you are not a hardcore gamer. You can also decrease voltage,more Options over mv are also available in Pro Version, Decreasing Voltage will help lower power consumption of CPU.

You can also install Siyah Latest Kernel and do all of this using S-Tweaks!

Thanks!

[MENTION=5482312]hellco[/MENTION] what exactly is your sd card problem?? Can you elaborate??
[Galaxy S II General] CrisR82:
The more I look at it, the more I'm convinced that the problem is the ROM devs themselves - seems like most rush ahead and as soon as a new Android version pops out - scrap bug-fixing what they made so you can have a fully stable version and move straight to a new one, bringing all the old bugs along with a ton of new ones.

I have to be honest, after some replies and PMs I decided to use dual-boot and try some other stuff...and I'm convinced the ROMs that can be classified as "stable" are less than 5...total. All others seem to have some type of issue that can screw over a person's daily life in one way or another.

Am I the only one that feels this way?
[Galaxy S II General] :
I don'y see the problem being the developers, but all in all I can support your opinion.

Just quickly wanted to show you that battrry life on the jelly bean stock rom sucks
[Galaxy S II General] CrisR82:
I believe the problem you're having is a wake-lock (some app, most likely media-scan, is keeping the phone constantly working even when you turn off the screen).

I've had that problem the first time I flashed a Jelly Bean Samsung ROM...not sure if you have the same issue, but back then I solved it by:

1. format USB storage

2. go in recovery move - wipe Data, wipe Cache

3. restart phone from recovery mode - as soon as you see Samsung logo, remove the battery

4. connect the phone via USB and go in download mode

5. flash again the Samsung JB ROM with Odin

That solved it for me back then, not sure if it'll help you, but if you have nothing better to do, you can give it a try before buying a new battery I guess

P.S. as I mentioned in a different thread, "the problem are the devs" was pretty harsh for me to say since it's not really a "problem" or so to speak...poor choice of words on my side, I apologize to any devs that might be offended by it.
[Galaxy S II General] :
The funny thing is, before flashing the Samsung ROM, I had formatted every single partition on the phone (excepting efs) :) I also flashed a media scanner fix for my phone, but it didn't help at all. I left the phone alone for about ten minutes with the screen off, and boom, 3% of my battery life magically disappear.

I'm also having battery issues on AOSP based ROMs, but just not as extreme as it is on the Samsung JB one.

In my opinion, the problem is Samsung itself. We have to blame Samsung for not updating the S2 to KitKat, since the hardware wouldn't be the problem at all. We also have to blame Samsung for keeping the Mali and Exynos sources closed. As seen on the official CyanogenMod page, the Galaxy S, S3 and up do have CM11 nightlys, but the S2 and original Note are stuck with the CM10.2 nightlys. I don't like to say this, but I have to, I doubt that the S2 will be getting any sort of official stuff coming from the CyanogenMod team regarding KitKat. Pretty hard to say that about a device which is not even 3 years old and actually runs KitKat fine. However, I have a small piece of hope left for the S2 to get KK either from Samsung or from the CM team. But well, nobody will be able to predict that.
[Galaxy S II General] Maik3550:
Since most developers are just teenagers doing all this in their free time and for mere enterteinment, of course all or at least, most of the ROM will suck. My main problem for not trying out any so called custom ROM (despite the fact that I rooted my phone week after I got it) is that they all have at least one major bug. Touchwiz is buggy too, but bugs are not in your face so to speak.

I always wanted to know if there was a rom where sgs2 works just like with the stock rom regarding media playback, camera and such things but didn't find the definite answer.

Regarding battery it's funny you people complain about it. Sgs2 batter was **** from the very beginning. It's just 1650mA what do ou want? If it had at least 2100 mA or more then it would be strange when I phone loses few percents each hour.

Now, my 2 years old sgs2 loses about 1 percent each or every two hours. With WiFi turned on. So overnight it's like 8-10 percent max.

Sorry for slight offtopic.
[Galaxy S II General] CrisR82:
MIUI is probably what you're looking for then...it's a heavily modded (mostly UI) Samsung stock ROM...though I believe in the Galaxy S2's case, they'll never update the Android version above 4.1.2 (from what I can tell all they update is MIUI component and not the actual Android OS so far)...so far the only problem I've had with it is that SCR Screen Recover is completely unusable.

CyanogenMod is also quite good, but expect 3-5 phone features to never work on it (MHL/TV-out for example, which is a big problem for me).

I'm considering trying CyanFox soon since I heard good things about it, if I do, I'll share my experience with it here.
[Galaxy S II General] dwegener:
Unfortunately no custom rom is flawless and it comes with a bit of a hassle to install. But in my experience the latest stock touchwiz software was really slow while taking pictures but with CM10.2 (nightlies) it's usable again.
[Galaxy S II General] Dr AM:
Yes it is almost perfect .. I use it and love it .. Install it with android tweaker 2 and you'll get the best performance ever on 4.4.2 ROM
[Galaxy S II General] :
I have no idea why that happens, but a friend of mine who also owns an S2 has had the same problem, but he fixed it somehow.

If I flash a ROM that's 4.3 and up, let's say a CM10.2 nightly or CM11 unofficial build, the first boot is perfectly fine. However, if I hit restart, the phone doesn't even get to the bootanimation. It just stops at the Galaxy screen with the yellow triangle :confused: If I flash something like the CM10.1 stable, everything is fine.

Sorry for offtopic, but I thought it might fit in here.
[Galaxy S II General] Dr AM:
Just try after installing the ROM clear data ,cache and dalvik cache
[Galaxy S II General] :
That's the standard procedure I'm doing everytime when flashing a new ROM. Cache is cleared automatically when you wipe the data, I've also wiped the dalvik cache several times.
[Galaxy S II General] Dr AM:
Don't know !! I had the same problem and I just wiped everything and the ROM is working .. I had the problem after flashing miui v5 and once on cm10.1
[Galaxy S II General] :
When i have some time tomorrow, I will try and flash and wipe once again. If it works, that'd be great. If not, I will have to figure it out. When I find a solution I will let y'all know

Sent from my Galaxy S2
[Galaxy S II General] :
Okay guys, it seems that I have found the solution. For flashing KK, I had always used the Gustavo CM Kernel recovery, because... well, I had the zip on my sdcard anyway. I just tried another recovery, the CWM-KitKat Compatible recovery from here: http://xdaforums.com/showthread.php?t=2546597 and it works. Reboot is fine now :)
[Galaxy S II General] rtorres0106:
You can try slimsaber by fusionJack stable 4.3.1 is the best for me battery and performance wise plus stability. you can also go to his 4.4.2 using ART also works good for me though not all features included but best for daily driver I must say.:good:
[Galaxy S II General] shuriknandroid:
Kitkat Kernel for S2

Hey can anyone suggest me a good kernel that supports Kitkat roms. Thanks:victory:
[Galaxy S II General] Raagh:
he is right, maybe you have tried the wrong roms, try slimsaber by fusionjack. 4.2.2 version is stable(most stable one if you want a ranking), also 4.3.1 its good for daily driver.

if you

1 format system

2 wipe data

3 wipe cache

4 wipe dalvik

5 flash rom

6 flash gapps. in that order you ll not have any issues. i promise. they work like a charm.if you dont follow this steps your problem.

an alternative its to format system and flash ROMNUKE(mayor cleaning script with all the other steps involved), then flash rom and gapps

gustavo cm11 kernel with stweaks support works great, if you want another you can also try dorimanx 4.4 betas or apolo 7.0 betas :)

im currently running beanstalk 4.4.2 and cm11 gustavo kernel and its great
[Galaxy S II General] lucasbox:
Thank you!!! :good:
[Galaxy S II General] shuriknandroid:
Thanks a lot!

going to try CM11 Gustavo kernel :good:
[Galaxy S II General] clock51:
suggerimento

hai provato la pac-man 4.3.1 e la slimsaber 4.4.2 ?
[Galaxy S II General] hellco:
My problem is that in Android version higher than 4.1.2 my sd card don't works at all or the phone dosn't start up ( goes in boot loop ) if you have some good solution i will install 4.4.1 on the moment :D
[Galaxy S II General] ryderpavan:
Hello Hellco,

It should not go in boot loop..You can wipe dalvik cache and try again...SD Card also works but you wont be able to see it in File Explorer Directly.. You have to click on the Bookmark like Symbol in Lower corner of File Manager to Select Memory Card.
[Galaxy S II General] :
Meanwhile I've switched to a rooted 4.0.3 Samsung stock ROM. This is giving me by far the best battery life atm. However, I realized that my battery is definitely damaged since I completely drain in 13 hours without any usage. I've ordered a new one, I expect to see the battery life getting better.
[Galaxy S II General] Mr.RainBurn:
Gingerbread still tops in battery life.
[Galaxy S II General] :
Gingerbread definitely tops, but however on any GB build I get the weird bug where "Android OS" just shows up at the top of the battery usage stats. Currently, I'm on CM10.1 stable + dorimanx 9.14, if i should flash back to GB anytime soon I will provide some screenshots.
[Galaxy S II General] doctor_droid:
I agree wid op...

But u cant/shouldnt blame the developers...

Remember they do it for free and they do have a life of their own...

So its upto them to develop on which android version.

However I still prefer stability over newer android versions..:)

Btw nice concept of the thread... and op buddy u r improperly naming 10.1.3 as 10.3 ;)
[Galaxy S II General] :
Here's what I meant when talking about the Android OS battery bug. I'm going to keep an eye on it, if it would seriously drain my battery I have no option but staying on CM10.1 stable with dorimanx on board.

Sent from my Galaxy S2
[Galaxy S II General] NEzverins:
RR Kitkat 4.4.2 - nice looking rom, could customize as i want, problem was the big battery draining.

RR JB 4.2.1 - same as 4.4.2 + i like the dorimax kernel, where you could add some DB to the sound, as we all know samsung has problems with the loud earphone sound. Had an ipod for music and it was much more geat experience.

And which i set and will keep is - stock ROM JB 4.1.2. - battery keeps well (i have 2000maH original samsung replaced). In the start it had some bugs like Samsung keyboard crashed all the time and Whatsapp too, but in the end, after few reboots it's working pretty well..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RidleyofZebes:
(My first post on the forums! You guys have helped me out so much in the past, and I'm excited to finally communicate with you. Wish me luck!)

I recently installed the 4.3 OTA update on my Samsung Galaxy S3, using the zips and instructions from these threads:

http://xdaforums.com/showthread.php?t=2387423

http://xdaforums.com/showthread.php?t=2538991

It went perfectly, without a hitch. Everything was running great, and I was loving everything about stock, de-samsungized 4.3, root and custom bootloader.

I was very interested in the dSploit app, and installed it, found out I needed Busybox. I installed it using the busybox installer. This is where the trouble begins. SuperSU needed a binary update after I installed busybox for some reason, even though I was fairly certain I already had the latest binaries. I tried running it through the automatic update with my teamwin bootloader, but it only booted into recovery and nothing installed. After googling it for a bit, decided to re-flash SuperSU. Suddenly, I began recieving the message "Unfortunately, SuperSU has stopped working" every time I tried to access anything requiring root priviledges. Anything that had already been granted root access (including Titanium Backup, thank goodness) seemed to work fine as long as it didn't need to request additional privileges. Unfortunately, I'm now locked out of ES File Explorer and the xposed framework (all prior installed modules continue to function though)

My initial thought was to wipe and reload using the process I used to get here in the first place, but I'm running 4.3 now, and I understand that downgrading is impossible now, and no flashable 4.3 stock roms seem to exist.

So I'm lost, guys. I need my root back somehow... If I forgot any information you think would be relevant and/or helpful, let me know and I'll provide anything you need. I've been googling and searching the forums for days, but I haven't found anyone with this exact problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dntesinfrno:
Have you tried uninstalling and reinstalling SuperSu?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RidleyofZebes:
Since SuperSU was flashed to the device via Odin, it is registered as a system app. The app store only has the open option, and I can't access the app in the system folder without root privileges, which it won't give me, so...

Yeah. Unless there's a script I can run through recovery, that's a dead end.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jimchee:
there is a zip of SuperSU you can flash from recovery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RidleyofZebes:
I've tried this. In fact, that was when SuperSU began force-closing. I just need to completely uninstall it and start fresh, I think.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pre4speed:
Have you tried the cleanup/unroot options inside supersu settings? Then starting over?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RidleyofZebes:
I might not have stated this directly before, but the SuperSU app won't launch. I tap on it and immediately get the "Unfortunately" error. I have no way of accessing anything within the app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pre4speed:
Ok well then find one of the 4.3 roms in development that you can use. I'm on s3rx 3.0 and other than some hiccups (still a wip atm) that are liveable, its pretty stable. You can flash this safely in recovery without the bootloader/modem package since you already took the OTA without risk of bricking. Its prerooted so no worries there. Good luck
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RidleyofZebes:
Thank you for that. It's always good to have a fallback option.

I'm still wondering though, is there a script I could flash that would completely remove SuperSU / BusyBox / superUSER (CWM) to scratch and allow me to re-flash CF-Autoroot? Barring that, how difficult would it be to code one myself?

FIXED IT.

Apparently, flashing the latest version of SuperSU from the developer's website (1.86) will not work on Android 4.3. I flashed version 1.65 as provided in the original 4.3 Rooting Guide, then updated it in the Play Store followed by a binary update and re-installed BusyBox, and everything is back to running order. Thank you all for your help and advice!
[Verizon Samsung Galaxy S 4] wtherrell:
IMHO it's never good to take an OTA
[Verizon Samsung Galaxy S 4] decaturbob:
I agree. Odin not difficult to use
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] ehaalandtluk:
Hello everyone,

In the last 4 months I have been using a foreign SIM card. Last night I came home, and I cannot return to CDMA mode and resume use of my normal Sprint service. I cannot change the network type in the settings (screenshots attached)

I was told that I might need to do a complete factory reset, but honestly I would hate to do that and find out that my foreign SIM card will no longer work for some reason.

My question: Is there any way to reset the mobile network settings to Sprint factory defaults? I have a feeling that the foreign SIM modified settings unbeknownst to me.

Attachments:

In the first picture, you can see that the menu has the option to change to CDMA EVDO LTE, but once that's selected, it doesn't enact any changes. I am not able to revert to CDMA mode.

Hope you guys can help! :) Thanks in advance.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] ehaalandtluk:
Another symptom:

All ##****# hidden menus no longer work.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] imbmiller:
Try *#0011# instead. It will present you with a debug screen. Press the left soft key (menu button that glows) and select "key input", type the number 1 and press OK, the press the left soft key again and select "back". Repeat this until the screen changes to a different menu. Once at the new menu press the left soft key and back one more time. You should see a selection for cdma, press that then select common. Press next page twice and on the third page there should be an option for "pref mode set", select that, then select cdma/lte (or something similar I can't remember off the top of my head), reboot the phone and you should be back to norm.

However if your phone somehow took an update when you got home from traveling and Is on mja now, you might have to to a clean wipe and odin a full modem/kernal/rom.

Let me know if this works!
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] ehaalandtluk:
Dude you're a lifesaver. PM me your paypal information you saved me hundreds of dollars.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] imbmiller:
Excellent man, stoked it worked for you! I don't PayPal but my btc is 1EECaxqfMX17yqX7Y4ecphHWwUenvbXvXC. Don't stress though, I help because I love, Merry Christmas!
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] ehaalandtluk:
Ah, regretfully, I never got in to bitcoins!

Anyways, I had another question. How do I revert to stock completely? I would like to get to the point where I can use the original dialer codes (still won't work). I do have data now, but 3434 or 3282 don't work. Also, cannot update profiles OTA/download updates. (See screenshot)

Also, what is the magic OTA that locks your phone? MJA? I'm still on MDL, but I wouldn't mind upgrading if it would benefit me at all.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] ehaalandtluk:
Oh, I'm not out of the woods yet.

Cannot receive calls/texts, but I can make them. Also, cannot attempt to re-activate the phone, saying there's no network.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] daniel4653:
Try over WiFi ##72786# if your dialer codes work now.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] ehaalandtluk:
Didn't work either.
[JAMin, XDA Neo, S200 General] wig:
I grabbed the wizard cab for Cingular and it got me going, but it's still not right. Plus, I'd like to flash this thing such that the cingular option is in the 'hard reset startup' screen ... you know, then one that lets you choose your carrier.

Any kind soul have this done already? If not, any newbie guides for how to dump the rom, unlock it, mod it, and put it back?

I've been a pocket pc guy since the beginning of time, but this is the first non-network device I've bought.

thanks in advance!
[JAMin, XDA Neo, S200 General] kevroc:
I'm not sure you can "cingularize" it. What you've already done is about it, other than custom settings to setup mms maybe if it isn't already. I don't think you'll see it in the startup since it's not designed for the us. It's really better this way though isn't it? No need to "overbrand" it :) Usually Cingular adds too much junk on their phones anyways.
[JAMin, XDA Neo, S200 General] wig:
So the carrier thing really only sets up the mms, wap and gprs stuff as well as branding and carrier-centric apps? nothing to frequencies or PRLs? If that's it then who cares?!

thanks!
[JAMin, XDA Neo, S200 General] kevroc:
Yes, exactly. The nice thing about the cab files is that it saves you having to type in all the settings. From there though you are on your own. There is a registry edit that will display the E versus G if you're in Edge coverage, stuff like that you can do which would probably be on a cingular branded phone, but it's nice not having any restrictions either that cingular would place on it.
[Nexus 5 Q&A, Help & Troubleshooting] gpvecchi:
It seems that I can't watch 1080p videos on my N5 because of an horrible stutter.

I tried remuxing the videos, and it seems that play is smooth only removing audio.

Any hint, please?
[Nexus 5 Q&A, Help & Troubleshooting] coorsleftfield:
I've been using bsplayer with 1080p videos fine. Other players I tried had the stutter problem.
[Nexus 5 Q&A, Help & Troubleshooting] mpgrimes:
Or try mxplayer and turn on hw+ rendering, hasn't been a 1080p mkv I can't play yet
[One (M7) Q&A, Help & Troubleshooting] vRS Carl:
Hi

As per the title I'm using the ARHD 40.3 ROM and for the first couple of days I had no issues. However over the past 24hrs I've had sense stop working 11 times where a pop up appears on screen. A further 4 Times to this it has frozen mid sentence and locked the phone up. I've had to boot into the boot loader and reboot the phone from there.

Is this a common problem and is there a solution. I haven't installed any apps apart from all the ones I had previously and it happens on the internet, texts, email, Facebook app etc.

Thanks in advance.

Carl.
[One (M7) Q&A, Help & Troubleshooting] x4n0n:
Did you flash it the right way? Never seen or experienced those types of problems.
[One (M7) Q&A, Help & Troubleshooting] kamilmirza:
try clean flash

maybe you messed something with Sense Toolbox
[One (M7) Q&A, Help & Troubleshooting] vRS Carl:
I'm assuming I flashed it right as it loaded up. The first couple of times I had issues loading Google accounts. So I did a full cache wipe etc and it went on and worked fine for the first couple of days.

I'm assuming by clean flash you mean delete everything, wipe the cache/dalvik again and then reflash. Then reinstall all apps again?
[One (M7) Q&A, Help & Troubleshooting] vRS Carl:
I've just flashed the latest Firmware too from here http://arhd.onedroid.net/db_mirror/Firmware/index.php?dir=HTC/HTC_One/1540/

Using the 4.06.1540.3 file. Will see if that brings any changes.
[One (M7) Q&A, Help & Troubleshooting] vRS Carl:
I've just seen that ARHD 41 is going to be uploaded so fingers crossed that helps.
[One (M7) Q&A, Help & Troubleshooting] x4n0n:
It is out now! Going to flash that baby tomorrow :)