yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] titanic_fanatic:
No, after much thought. I have decided that it's not worth the hassle. If I went that direction, the wipe dalvik cache feature of recovery will stop working and this is too important loose. It's a way to try and fix a bootloop or fix FC's. I will continue to modify the gapps package because of this.

Did you take it in for servicing to find that out? The strange thing is he's still able to use stock.

When the bootloop happens, try booting into recovery, then go to Advanced -> Wipe Dalvik cache. Does this get you back into android?
[Galaxy S II General] iDynamics:
Excellent release as always. :)
[Galaxy S II General] titanic_fanatic:
I still haven't had any lockups. It's running much smoother for me... You too?
[Galaxy S II General] danrobi:
It is running great so far. Only thing is when i press power button, the lockscreen comes on a little slughisly. I'll see after a reboot.
[Galaxy S II General] iDynamics:
No lock ups yet. Scrolling performance has really improved.

edit: This rom + Crossbreeder + Supercharger = Wow
[Galaxy S II General] slushee:
My first foray into cm as you all know now.

Question re: super su

I'm running your dec 31st build (will be installing your newest build in an hour). When I installed cm I immediately installed supersu from play store after initial setup.

Supersu then askes to update binary. I selected normal way and it shows success. I don't know the ramifications of this as you suggest using the CWM way.

I've been running it that way since I installed cm. The only root program I use though is es file manager and greenify.
[Galaxy S II General] titanic_fanatic:
This was only throughout the first and maybe second build as there were issues doing it the normal way. Doing it the normal way only means that it replaces the su binary while you are in android instead of cwm. It's the same thing really. There are two methods just in case one didn't work you try the other ;)
[Galaxy S II General] manfromgta:
Very good job TF!!!! No lockups here either. You've out done yourself once again. Thank you!

Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
[Galaxy S II General] danrobi:
I had forget to turn HW Overlay off, it fixed the laggy lockscreen problem. Had screen flickering in textra while using keyboard, gone too.

Best build so far, everyting is lightning fast.

Thanks Titanic! :)
[Galaxy S II General] Blazing Hornet:
Thanks TF for the new build! I have it running on the phone now and it certainly is faster than anything that's ever been on it, especially scrolling in the app screen. The app screen is so much smoother. I'm keeping track of the lock screen freezes/no shows but nothing has shown up yet (cross fingers)

Installed by:

Enter CWM

Factory Reset

Clear Cache Partition

Advanced>Wipe Dalvik

Mounts and Storage>Format /System, /Cache, /data

Install ROM and GAPPS

Reboot

Run through the setup

(Had some FC's)

Reboot to CWM

Advanced>Wipe Dalvik

Reboot

...

And now the phone is running smooth as can be. It's amazing how far this build has come in such short time. Thanks for all the hard work TF!
[Galaxy S II General] big_biso:
it is running much smoother to me too. the only issue I have is with Viber. still as before loosing the sound mid call. some time after 7 minutes some time within seconds. it looks like as if it lose connection with the speaker or some time it get stuck even though I can still see the call going. I need to exit the app and restart it. Viber support said they don't support custom rom like CM but it usually works. I will try to get you a logcat next time I use it.
[Galaxy S II General] sandhu6698:
I tried this i wiped dalvik cache but same i see a black screen after the samsung logo........................I tried installing another like SLim ROm ......same happens in slim rom also after 15 mint phone shut downs and blackscreen .......?? whats the problem rooting, Kernal, files what??
[Galaxy S II General] titanic_fanatic:
I'm starting to think it may be hardware related.

Unless, you are installing apps at that time. Maybe you are installing a specific app that might be causing corrupted files.

If your willing, I have an idea. Do a clean flash. When you get into a bootloop again, try re-flashing ONLY the ROM and do not wipe anything. This will reset all of your system settings, but should retain all your installed apps and data. If that's a success, awesome. The next part is to wait it out and see if it happens again even after re-flashing the ROM on top of itself.

My hope is that we can just get it past whatever process is causing the bootloop.

Just a little info on bootloops... Bootloops are usually caused by apps that are not compatible or corruption in the dalvik cache. This is usually fixed by clearing dalvik or uninstalling the app that causes it.

Sometimes bootloops can occur when setting the wrong permissions on system files and/or folders. If you haven't changed any permissions then it could either be the ROM maintainers mistake or maybe something else.

Also, bootloops can occur with hardware failure. That could be bad ram as another user suggested, malfunctioning drivers (rom maintainers responsibility). Not enough power is another possibility and is rom specific.

After actually writing this out, I think it might actually be bad ram because stock uses different memory allocations which shouldn't make a difference if there is no bad memory. But it's possible that the ram that stock was using is good ram and potentially with cm it's using the bad memory which was unused while using stock. Using bad memory slots could cause the device to reboot in the middle of an important process and cause corruption to any files open the time (you wouldn't see this or even know it's happening)

The best course still remains what I suggested above ;)
[Galaxy S II General] sandhu6698:
SIr tell me the point what should i do ??

but my ROm works great for 15-20 minutes why should there a a hardware problem....OR...if i restart the rom then after samsung Logo black screen screen comes if i restart also

plz tell me what to do ??
[Galaxy S II General] titanic_fanatic:
When you are in a bootloop, re-flash only the ROM without wiping. If that gets you to boot up again then we need to wait and see if it happens again.

Sometimes there are hardware problems from the factory. Bad ram chips are an example.
[Galaxy S II General] sandhu6698:
Tried this also but again that black screen...........there is another issue if i restart the Rom then also i see the blackscreen when phn starts.

plz help
[Galaxy S II General] titanic_fanatic:
It does sound to me like your hardware is failing since there is no reason why you should be in a bootloop in the first place.

Best thing to do, if you still have a warranty left is to return your device to stock and send it in for warranty repair. Hopefully they can determine exactly what is not working and fix it.
[Galaxy S II General] sandhu6698:
there is no hardware problem sir i have tried a trick nd it worked

i installed the Stock Rom with odin then i install Clockworkword Rec.

then i flashed this rom and there is no problem now.

its working fine from an hour and there is no Bootloop

just one problem now it is not rooted :rolleyes: plzzz tell me how to root this now
[Galaxy S II General] titanic_fanatic:
Excellent, I'm very happy to hear it's finally working for you.

Root is there, sometimes it just takes a little to get it to activate. When I have that issue, esfile explorer from the market seems to always help.

So, download esfile explorer from the market. Then open it and press the menu button to access the side menu. Press the tools menu item and then press the root file explorer button. This will request superuser permission, just accept and now your other root apps should also detect root ;)

If you flashed the slimbean rom, you need to enable root in the developer options. Developer options are hidden by default. To access them, go to Settings -> About Phone and press the Build Number 7 times quickly then go back to the Settings menu and you will see developer options. In developer options, you can set root to off, apps only, adb only or both apps and adb.

Once root is enabled in slimbean, follow my directions for using esfile explorer to initiate root for the first time ;)
[Galaxy S II General] sandhu6698:
Thanks all is working great there is no bootloop now but ROm restarts after some tym like 30 minutes only it restarts if i use it
[Galaxy S II General] EvilDan:
anyone else have this problem ?
[Galaxy S II General] titanic_fanatic:
Are you on the latest build 20140120? I applied a systemui fix on that build and haven't yet had this happen.
[Galaxy S II General] EvilDan:
I was on the previous build last time it happened, now i'm on the latest since yesterday.

I'll report back if I get this problem again.

btw I did a dirty flash and had to clear cache because I had an error when typing URL in the browser.
[Galaxy S II General] slushee:
Just installed your CM 10.2 dated Jan 20th, 2014

Did a full wipe/format clean install. After initial setup, settings set and installing outlook and supersu, I rebooted and wiped dlavik cache.

Out of the box the only thing i notice that is unusual is that when I press and hold the power button and press reboot, i no longer get the option to reboot into recover, it just say's "your phone will reboot" with OK or Cancel. (EDIT - Fixed by enabling in Dev Options, thanks guys!!)

Otherwise there were no FC's at all (EDIT - after installing 3/4 of all my apps, google play store FC'ed. Wiped Dlavik Cache and continued on), and so far everything appears to be running nice. I'll give the INTERACTIVE governer a chance for a few days before I switch back to performance :)

So far another great build.
[Galaxy S II General] sandhu6698:
Help plzz

In Stock Rom Games were running awesome without any lag .....,but in custom rom why games are a little bit slow???? plz FIx
[Galaxy S II General] sadowling:
You need to enable "Advanced Reboot" in Developer Options to get the "Reboot to Recovery", etc..
[Galaxy S II General] manfromgta:
In order to access advanced reboot options go to system settings/developer options and check advanced reboot. This will give you recovery option while rebooting. If developer options are not available in system settings go to about phone and repeatedly tap build number until it shows them. I believe its six taps. Hope this helps you out.

Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
[Galaxy S II General] big_biso:
Ok So I managed to get logcat while in a call in Viber. The issue happened again were it seems the app lose the sound. this time it took over 13 minutes to lose the sound. Attached is the logcat

Thanks So much for helping
[Galaxy S II General] titanic_fanatic:
Try changing your governor to ondemand and check the set on boot checkbox.

Settings -> Performance -> Processor
[Galaxy S II General] titanic_fanatic:
Thanks for the log. I see the audio derailment. It has to do with effects like noise suppression. I have an idea of where to look for the bug. I'll let you know what I come up with.
[Galaxy S II General] grandmaster_b:
Great job on the latest ROM so far its perfect for me.......time to move on to KitKat ? :)
[Galaxy S II General] titanic_fanatic:
I've already built kit kit, but it is still in beta because it's extremely buggy, and have not been able to successfully apply the vib fix to it. All of my latest kit Kat builds resulted in consistent system reboots :(

I've been watching our kernel repo because Steve is supposed to be updating it, but has not yet been done, so I'm certain it has to do with the kernel and missing hooks into the ROM. Circle me on g+ if you want to watch the post for new developments ;)
[Galaxy S II General] bijon440:
To boost the reluctant users who are wanting to use KK, but are worried about the stability, I've been using it as a daily driver for the past week or 2 and its been fine, but my phone doesn't see the kind of versatility that others may. Vibration and the odd reboot here and there is all. Don't be so hard on yourself TF, 'extremely buggy' seems harsh. I'm very happy with it.
[Galaxy S II General] formercontra:
I tried kk out yesterday, and there was a lot I liked about it but there were some graphic bugs and enough reboots to make me prefer the stability of 4.3. Unlock, screen was nothing but a mess of icons, freeze, reboot. It is a great rom, but it is in beta and I'll wait until it's declared stable. To each their own.
[Galaxy S II General] big_biso:
Battery Life

can you guys confirm if anyone suffering from significant battery drain with the latest build jan 20. i am averaging 8-10 hours now while on the older build from dec 31st i was averaging 15-16 hours. nothing changed in my use pattern. The battery is now at 9% with only 7.5 hours since lsst full charge. i have 1.5 screen time and about 16 minutes voice call. it seems most of the is spent in android os with over 4 hours keep awake.

the build is much smoother though.

i am using the ondemand govonor
[Galaxy S II General] titanic_fanatic:
I can't say for certain right now since I always have to give the system a couple of days to settle in, but I believe this may be the result of the modifications i made to the systemui.

See I'm my screenshot is the android os and included in the second list is the systemui. I'll have a better idea over the next day or so, but it may just be a trade off for better performance. We'll see how it goes though ;)
[Galaxy S II General] titanic_fanatic:
And the screenshot ;)
[Galaxy S II General] Brokensword098:
THx

thanks bro
[Galaxy S II General] Tronith:
Just giving my two cents. So I've only just updated to the Jan 20 build. Our of the box my Swift key still lags abit. I'm going to give the time a few days to settle and I'll get back about battery and so on. As far as I see though we are getting back to the smooth like butter interface :) I'll also let you know how the lock screen issue goes.

P. S. Dirty flashed.

Great job Titanic!
[Galaxy S II General] titanic_fanatic:
Your welcome ;)
[Galaxy S II General] sadowling:
LTE not default?

Just noticed that "GSM/WCDMA preferred" is the default in "Mobile Network Settings" ...and likely why I haven't seen the LTE symbol in a long time. Is there a reason for this setting default?
[Galaxy S II General] titanic_fanatic:
That's always been the default ;)
[Galaxy S II General] slushee:
I've noticed slower speed tests using LTE over H+ since I've started using Titanic's cm 10.2 on my s2 so I've stayed with H+.

I see much faster speed tests (WiFi and h+) on my nexus 4 using same Sim and Wi-Fi. I've just assumed it was a crappy radio in the s2 vs the nexus 4.
[Galaxy S II General] titanic_fanatic:
It must be the lte towers in your area, it maybe your proximity to them.

Although my LTE doesn't usually reach the speeds it should, I still get almost double the speed in most cases.

In my screenshot, the first 3 are on lte, the second 3 are on h/h+. All tests only had 1 to 2 bars of signal.

I notice the difference mostly when I'm uploading and I'm not connected to LTE. My upload speeds through h/h+ are really bad. I don't notice it as much when downloading though.

We should be getting speeds of about 20/Mbps but mine range from about 10 -17 depending on my proximity to an lte tower.
[Galaxy S II General] titanic_fanatic:
[MENTION=1691042]big_biso[/MENTION] just in case you didn't realize, I sent you a pm with a possible voip fix that I need you to test for me ;)
[Galaxy S II General] big_biso:
You are correct I did not see it. I will test it now.
[Galaxy S II General] danrobi:
Is there any way to make HW Overlay off check permanent, just realize that it as to set off after each reboot?:confused:
[Galaxy S II General] Screambloody:
MHL

Is MHL working with this ROM?

I want to buy it,but I don't know if it works...
[Galaxy S II General] manfromgta:
Are you using latest build? All my settings stick through reboot.

Edit: I stand corrected. I just tried to disable HW overlays and it did uncheck after reboot. My apologies. :eek:

Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
[Galaxy S II General] Alexander Kalinin:
Hello!

I have i757M with 4.04 and <3e> Recovery.

How do I flash CWM fo flashing CM?

Thanks!
[Galaxy S II General] titanic_fanatic:
No, I haven't figured it out yet. Cm apparently dropped it a while back and even though I have the drivers installed it didn't work.
[Galaxy S II General] Blazing Hornet:
Start with this http://xdaforums.com/showthread.php?t=1707126 to get a recovery on your stock phone.

**When following the previous guide you will need to make an adjustment as your phone will decide to recover its original recovery right after you reboot the phone from flashing CWM. This is because of a specific file as TF has pointed out to me. You have 2 options you can rename the file, or an easier way is when following step 7 in the previous guide you need to make an adjustment. **

It says:

7. In Odin, press Start. Your custom recovery should be flashed completely in a span of a few seconds, and then it should say "PASS" in Odin. If it doesn't finish and is stuck, then your file was either corrupted during the download or there was an MD5 mismatch (this is not a regular TAR file, it has an MD5 signature).

What you need to do is when you begin the ODIN thing, you press start ODIN begins doing its magic and will get to a point where you will see your phone power off and begin to reboot... the SECOND you notice this pay attention. It will vibrate as it always does when booting up. Right when you hear/feel the vibrate immediately hold down Volume Up + Volume Down at the same time. The moment you see the Samsung logo appear let go of both the buttons. This will get you into the CWM recovery you just flashed without letting the phone recover its old recovery,

Then afterwards follow the original post's instructions to update that CWM and flash the ROM.

You may see when you are all done and ready to select the reboot now in CWM it will warn you that the stock recovery may flash itself and it can prevent it from happening. Select Yes to prevent it if this comes up for you.
[Galaxy S II General] titanic_fanatic:
Give me about 15 mins, and I'll attach the init.d script that does this.
[Galaxy S II General] titanic_fanatic:
Download this file and remove the.txt extension, place it in /system/etc/init.d and give it the same permissions as the other files in that folder. This should now run at each boot and disable hw overlays ;)
[Galaxy S II General] :
Still the hardest working man in show business I see! ;)

Great work rom guru. Without you I doubt anyone would still own the bell s2. :)

Sent from my Moto X cellular telephone...
[Galaxy S II General] titanic_fanatic:
How's the Moto x treating you?
[Galaxy S II General] :
Amazing! I could go on and on about it. LOL

No custom roms really...just a few...but most prefer stock with exposed and mostly gravity box getting you all the options and customization found in custom roms.

And battery life is crazy! I average about 28 hours with 5 1/2 to 7 hours screen time. ;)

Glad I picked the phone I picked out of the top dogs out there now. :)

My mom has our i757m now, running your slimbean 4.3 I think it is? No complaints from her....especially compared to her older, bare bones, Motorola smartphone.

Sent from my Moto X cellular telephone...
[Galaxy S II General] Tronith:
Hello! So just giving my two cents on the latest update for the Rom. So I've ran the Rom yesterday and after 12 hours my battery drained to about 14%. Today I'm at 12 hours and I'm at 50%. This is with greenify and kickass 2 running. If it's doing anything. I also limit my processor at 1296mz. Auto brightness and about 2 hours of screen time.

So it's doing good so far.

Now I'm still getting a lot of screen flicker. And my lock screen still is invisible once in awhile.

That's all I got for my update :)
[Galaxy S II General] titanic_fanatic:
Did you ever try that app I found to connect mtp to Mac? Did it work?
[Galaxy S II General] Tronith:
No I haven't. But I will eventually. I also need mass storage because without it I can't listen to music through cable in my car.
[Galaxy S II General] titanic_fanatic:
I'll add the drivers back to the kernel and we can see if that will work.
[Galaxy S II General] Tronith:
That would be awesome. Thanks! (my thanks option doesn't show up on the app anymore :s )
[Galaxy S II General] Screambloody:
:(then,Do I have to use stock rom?
[Galaxy S II General] titanic_fanatic:
As long as stock has support for it. I'm not aware oh wether or not it does.

As for this rom, if I can figure out how to add it back, you can consider it done. I can't make any promises though, I just don't know what it would entail.
[Galaxy S II General] Alexander Kalinin:
Hi!

Flash CWM and CM - bootloop.

Flash ICS with aroma - bootloop.

May be flash factory ICS first?
[Galaxy S II General] titanic_fanatic:
Did you wipe your old rom before you flashed the new one?
[Galaxy S II General] Alexander Kalinin:
of cource

data/cache/dalvik/system/emmc

now 4.1.2 stock (not good without russian and root)
[Galaxy S II General] titanic_fanatic:
Maybe it's cwm recovery 6.0.39. Try using philz touch recovery to flash. You should only need to use the option clean to install new rom and that will wipe everything.
[Galaxy S II General] danrobi:
Hi, this is the second time it happens, an app, textra, has an update and at the intallation get the unsufficient storage space error( i'm not sure it is the right translation). Happened last week with ES explorer too.

Many other apps did update fine, and i eve installed some new ones.

Any idea anyone?

:confused:
[Galaxy S II General] titanic_fanatic:
This is due to our small cache partition which is where the play store caches downloaded apps before install. To fix, you can reboot into recovery and wipe dalvik-cache. Then reboot, android will do it's upgrading and you should be able to install the app. Wiping the dalvik-cache serves the purpose of removing unnecessary cache to free up space for these downloads.
[Galaxy S II General] danrobi:
Did not work, still get the same error message. As for the 91fixoverlay, i still have to set it off after every reboot. :(
[Galaxy S II General] titanic_fanatic:
For the play store, here are some suggestions from other threads, if the first one doesn't work, try the second and so on:

- clear play store data/clear Google play frameworks data and then update

- delete the app itself and reinstall

- delete your Google account, then add it back and update/reinstall.

For the 91fixoverlays script, depending on what file manager you used, you may have missed the user permissions part. Best thing to do is use esfile explorer to set user permissions to uid:root and gid:shell and 755 you can see a graphic representation of this in my screenshots.

The other method is to open the terminal and type the following:

That will set the correct permissions and then the script will run on boot.
[Galaxy S II General] titanic_fanatic:
Hmmm. Tapatalk is weird for attaching images. I had two selected???

Anyways, here's the second screenshot
[Galaxy S II General] danrobi:
OK Titanic, the first two solutions did not work, i have clear cache and dalvik trough recovery.

For HW overlays here is a screenshot.
[Galaxy S II General] danrobi:
I have set permission with root explorer since i cannot install ex explorer anymore.

Still have to try the third solution.

Then i guess i will have to reinstall doing a clean flash.
[Galaxy S II General] titanic_fanatic:
Yeah, root explorer doesn't let you change the user/group. Using the last method with shell would work.

Still looking for an alternate solution to the other problem though.
[Galaxy S II General] sandhu6698:
HElp me plz

How can we send files using wifi Direct in this ROm

We can send easily by Stock Rom but not from this ROm
[Galaxy S II General] titanic_fanatic:
Settings -> Wi-Fi then press menu button for Wi-Fi direct.
[Galaxy S II General] sandhu6698:
thanks.....
[Galaxy S II General] sandhu6698:
just want a thing....

Is there any thing i can enjoy multiwindow like note 2 or grand in my phone for this ROm any patch or anything ????
[Galaxy S II General] titanic_fanatic:
Cm doesn't support multi window.