yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] purezalbert:
Is anybody else getting, every so often, that Google car mode gets enabled, in the notification drawer? Bug?
[Galaxy S II General] titanic_fanatic:
Is this using Google home launcher?
[Galaxy S II General] purezalbert:
No this is using launcher 3
[Galaxy S II General] formercontra:
Don't want to spam feature requests with paranoid android features, but they made their Recents ui open source along with their dynamic system bars. If it doesn't work that's cool, but both features are pretty neat.

BLN not working for anyone else on the latest version? I can enable the lights, but they don't blink for notifications.
[Galaxy S II General] titanic_fanatic:
I will look into this. Maybe I can allow you to choose between the two.

Not sure what happened to bln this time though. Might have been the s2w. I'll investigate it ;)
[Galaxy S II General] TrueHD:
Help!

Wanted to try SAFE MODE which should be working for our device, according to official PDF:

http://mobilebusiness.bell.ca/_cont...3e2-11e1-ad47-0025903439d2/sgh-i757-ug-en.pdf

But boot animation is loading like forever. So i can't start the phone at all.

Recovery menu is working, but cleaning cash and dalvik cash will not help (i know, becouse i had this problem once, but haven't understaned it's nature back then).

Full reset will help, yes, but i don't want to do that: too much programs and their settings is important for me and i don't have a backup.

Any ideas how to make the phone running again, without Hard Reset? Or how to just cancell this Safe Mode?

P.S. Don't know which is causing the glitch, i am at the last Carbon build. When i had this problem last time, i was on previous build.

Upd: dirty flash also doesn't help. Weird. I just read that Safe mode should have be disabled after restart. So now i am trying to remember which other things i have done. And only 2 things came to my mind that could cause the problem:

1) I deleted the system keyboard, which was previously frozen for a few weeks with no problem on restaring. I use SwiftKeyboard anyway (made it system also).

2) I deleted or frozed (don't remember) the "About Carbon" app. It isn't do any usefull functionality anyway, just takes memory.

Any ideas how to revert the changes without Clean Flash?

For example, through Aroma File Manager in Philz Recovery? I have it installed and running pretty good.

Please, help!
[Galaxy S II General] RukusX7:
What about creating a backup of current setup in cwm and then restoring a previous backup? Then maybe you can dissect your backup to get wanted config.

Sent from my Oneplus One ...mmmm... bacon.
[Galaxy S II General] TrueHD:
Well after numerous attempts of cleaning cash/dalvik and restoring apps (LatinIME.apk, CarbonAbout.apk, Launcher3.apk) from firmware zip to System/app and System/Private-App using Aroma File Manager, i managed to receive somehow this behavior:

bootanimation ends with message "Apps updating 1-159", then i wait till all of them are updated and then i get a lock screen! But after unlocking - the system ask me which launcher to use? And offering Launcher3 or Google Now. But hey! Where is my Nova Launcher? I even made it System App few weeks ago, why it has dissapeared?

Anyway, if i choose any from those two - the phone falls back to bootanimation immideately. And everything happens again. I even managed to reach Settings throug Notification Panel, and yes, there were NO my NovaLauncher in apps! That's weird. Especially given that few days later after my battery run off i've got default blue wallpaper with moving bubbles after switching back my phone when i got home. This also happened a few times back in june and july (wallpaper changed to default by itself). So now i suspect it have someting to do with Nova Launcher. I couldn't found it among apps.

So i decided to send the apk for Nova Launcher throuh bluetooth from my notebook and when the phone gets it - choose Install, then Open. But, unfortunately, i decided to try just picking Launcher3 one last time (i cleared it's data, thought it's gonna work.) But the phone fell back to bootanimation again, and i never got to regular lockscreen again. It continues with forefer bootanimation again. Or just boots, "updating apps" from 1 to 159 and goes to bootanimation again.

I tried to do all i did before, but no luck, still i can't get even into lock screen...

But it backups th full phone, right? You can't shoose, which apps to restore and which do not, do you?

So i will get the same glithched system.
[Galaxy S II General] titanic_fanatic:
I'll have to see if I can find anything out about this. I can't imagine that anything should change permanently when going into safe mode, so as you mention, it should go back to normal after reboot.

My suggestion would have been to dirty flash the Rom, but hang on. Why not try dirty flashing both the Rom and gapps? Maybe it's the gapps that's causing the issue and not the Rom.

Aside from that, I'll look to see if I can find anything else out?
[Galaxy S II General] TrueHD:
Thanks, guys, problem dealed with. Factory reset.

Yes, i tried both - gaps and rom dirty flashing, none works. Also, safe mode seems to be, haven't been a problem.

After few clean flashes and playing with deleting systems app (i like to delete everything i don't use), it seems to be i found the problem - it was freezing Themes Provider app. I never saw this app providing me with any themes (always downloaded by myself) so i decided to freeze it yesterday morning. Never thought it would be so important to the system that the phone would be playing bootanimation forever.
[Galaxy S II General] purezalbert:
Just wondering, for anyone that has Google chrome beta as their default browser how are you coping with chrome beta always opening in windowed mode and dark display? Or if anyone has got a solution for this issue?? Any help would be appreciated!! ??
[Galaxy S II General] ksSGHI757M:
Chrome Beta

I couldn't find a direct way of fixing it but restored an older version us titanium backup. Have automatic updates disabled so I get the prompt but ignore it.
[Galaxy S II General] RukusX7:
Lollipop has gone aosp!

http://www.droid-life.com/2014/11/03/aosp-aosp-lollipop-time/

Sent from my Oneplus One ...mmmm... bacon.

---------- Post added at 09:00 PM ---------- Previous post was at 08:59 PM ----------

This actually doesn't happen on stock ROM for the Oneplus for some reason. I wonder why.

Sent from my Oneplus One ...mmmm... bacon.
[Galaxy S II General] purezalbert:
Could that mean cyanogen mod might be rolling out CM12??
[Galaxy S II General] RukusX7:
I read somewhere, DEC 1st.

Sent from my Oneplus One ...mmmm... bacon.
[Galaxy S II General] formercontra:
Well, take eta's with a grain of salt. There's probably going to be a bit of time in between "cm has built a successful nightly" to "cm has a 5.0 daily driver" to "i757 has a stable 5.0 rom"
[Galaxy S II General] RukusX7:
The s2 is getting dated anyway. You can purchase phones for under a hundred bucks now that equal nexus 4 in performance. Devs are working on cyanogenmod for mediatek devices right now. There is also even Cyanogenmod being developed for the Android One.

Sent from my Oneplus One ...mmmm... bacon.
[Galaxy S II General] formercontra:
Yeah, I'm looking at a 1+1 or the nexus 6 for an upgrade pretty soon.... I'd still keep this phone around for tinkering though. Once school stops being so crazy I'll sync up with cm12 repos.
[Galaxy S II General] titanic_fanatic:
I've actually decided to try a straight up aosp build of lollipop.

No promises though since all the Qualcomm code needs to be ported in order for it to work on our device.

I've downloaded the source and am in the process of modifying things to build with aosp.

After that, I will start the long build process of building until an error occurs and then fix it by comparing the repos of the affected code.

I'm expecting at least a couple of weeks before I can actually get it to fully build if I can get it to build at all.

As for cm12 and updated versions of other ROMs. I truly believe that they won't be updated for the next few months. They have a lot of work to do with merging the aosp code and then fixing and adding back their own features. With the kitkat source, I think it was 2 months until they got it fully merged and fixed.
[Galaxy S II General] RukusX7:
I'll let you guys know when I see the first lollipop release for my device.

Sent from my Oneplus One ...mmmm... bacon.
[Galaxy S II General] RukusX7:
Its here for the oneplus.

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

Android L: Discussions, Rumors, Android L Developer Preview Port Talk
[Galaxy S II General] titanic_fanatic:
I'm a little confused with their repos right now. It looks as if we're dropping the -caf repos, but I'm not entirely sure as the development had only just begun at the beginning of the month, so only time will tell what they're doing.
[Galaxy S II General] ksSGHI757M:
Ongoing problems

Wanted to check to see if anyone has found solutions to the problems that I have since I've rooted my phone and gone up to this build.

Flash resetting phone. I tried flashing the camera fix but my phone still restarts if I take pictures with the flash on. Not sure if it's related but my phone sometimes resets when I use the camcorder.

Netflix doesn't work. This is pretty minor for me. It's probably good that it doesn't work actually... It just would be nice every once in a while to be able to use it.

Thanks!
[Galaxy S II General] titanic_fanatic:
For the flash, I think [MENTION=4800121]Sultanxda[/MENTION] found a solution, I just need to build it into the kernel. Essentially, when the phone is with less than 35% battery, it will use an lp (low powered) flash. I think that will fix that issue.

For Netflix, use Netflix black. I dune have any issues with it ;)

On another note, I may have an android L build. It's currently building after spending all last night and all day working on it. It's a Frankenstein build though. I had to apply do many hacks, but we'll see how it goes ;)
[Galaxy S II General] m54:
Just wanted to mention, not sure 35% is low enough, i've had my phone around 50% and experienced a reboot using flash/camera.

PS: Amazing that 5.0 may be a possibility for this phone, great work and thankyou to you and everyone involved in keeping development going.
[Galaxy S II General] titanic_fanatic:
Cheers, we can always play with those values to see what works best for us. I think we'll start with the 35% and if someone has the issue then we'll increase the threshold until it doesn't happen anymore.

I don't really use the camera enough to be as aware of that as you guys do so thanks for sharing ;)
[Galaxy S II General] crdnick:
awesome rom, very happy considering i was about the shoot the phone because of lagging and hangups.

only question so far:

Why does chrome only take up 2/3rds of the screen, and why is the search bar light white and the rest dark?
[Galaxy S II General] formercontra:
The window mode is a bug in the Chrome app, people have it across different phones and roms. Temporary fix is to open it, then go to another app and open Chrome from recents.
[Galaxy S II General] crdnick:
alright one more.

usb mass storage not working for me, on either computer.

Installed the USB switcher app, complains that debugging mode is not on.. which it is. windows see's it as an android ADB device.

its handy to be able to plug in and copy files...
[Galaxy S II General] titanic_fanatic:
There are two methods, mtp or USB Mass Storage. Go into Settings -> Storage and press menu button then USB Computer Connection. MTP is best, but you can use UMS too.

MTP should work out of the box as long as it's checked. If using UMS, there will be a notification in your notification shade, click on it and click the button to mount UMS. Just the one extra step for UMS ;)
[Galaxy S II General] crdnick:
Sneaky.

i never thought of hitting the menu button.

Thank you!
[Galaxy S II General] iDynamics:
I finally moved to your latest carbon build but I am having an annoying issue. Systemui is crashing all the time for no apparent reason. Any idea what is causing this?

edit: sdcard doesn't mount in windows.
[Galaxy S II General] titanic_fanatic:
Could I get a logcat please ;)
[Galaxy S II General] titanic_fanatic:
Make sure mtp or ums is checked in storage settings. They're both unchecked in the last build for some reason.
[Galaxy S II General] crdnick:
alright, i need to bug you one more time.

my phone does not ring. started out strange as i got a couple of voicemails, but nothing in the phone log.

today, i tried to call myself from the work line.

its ringing in the ear piece. got to voicemail.

NOTHING appeared on the phone screen.

rebooted, thinking something silly happened.

still nothing. no logs, no movement from the phone at all. blocking unchecked in the phone app settings.

Can make calls without a problem.

what did i break?
[Galaxy S II General] titanic_fanatic:
Check this post and make sure the setting is in your build.prop

http://xdaforums.com/showthread.php?p=55837897
[Galaxy S II General] titanic_fanatic:
New Build is Up!

New build is now up... See the changelog below for the changes.

Most important in this build is the cpu overclocking that has been added. You can now overclock your phone to 1890MHz where we were previously limited to 1512MHz. Antutu scores have gone up by almost 1500 points.

Please note that I could not get antutu to complete while at 1890MHz (phone reboots), so I have it set to 1836MHz and antutu completes with no issues. Other than antutu causing the phone to reboot at 1890MHz, everything else seems to work perfectly at this overclock, so if your adventurous, you can use the 1890MHz OC. For those less in tune with how these things work should either leave the overclock at it's default or only increase it to 1836MHz.

If you notice any random reboots, lower the MHz by one step (although I have not had any random reboots that were not caused by antutu stressing the system).

Last thing, please watch the heat of your phone. Overclocking does cause additional strain on your hardware components and could cause the device to heat up very quickly. If this seems to be a problem for you, decrease the MHz back to the default CM setting of 1512MHz.

I use go power master since it sits in your notification bar and will tell you your phones current temp. I will only use my phone up to 40 degrees. When it goes above that, I turn off the screen and wait 5 minutes before using it again. I don't suggest using your phone if the temp is above 40 as you could start to damage your internal hardware.

The other important update here is the addition of low power flash in the kernel. This should help with the scenario where the camera flash causes the device to power off. This typically happens when the battery is below 35% (this happens on the skyrocket too). If the camera still causes this shutdown for you, please let me know the details such as what % of battery were you at when it occurred and anything else that might be useful. If needed, I'll tweak the threshold.

And now, the download details:

Download

Changelog
[Galaxy S II General] iDynamics:
Thanks for the new build.

A few issues.

1. Set-up manager crashes constantly. I couldn't get past set-up without deleting it via. Android Commander.

2. The home button is unresponsive. The phone vibrates when the home button is pressed but it doesn't take me to the home screen.

3. Cannot get to the quick setting tiles. Clicking the button doesn't work.

4. When I tried to sign into my google account this message appears "Unfortunately, Google Account Manager has stopped.". Don't know if it's because I removed set-up wizard or not.

This build feels much smoother than previous builds. Happy with the performance thus far. :)
[Galaxy S II General] titanic_fanatic:
Did you clean flash this one? I didn't get any of those problems and can't replicate them :(
[Galaxy S II General] iDynamics:
Yes I did a clean flash. I will try again.

edit: setup is still crashing

edit2: Home button and tiles now seem to be working

edit3: Google account manager is still crashing

I replaced everything in the libs and the libs/hw folder. Now google account manager works. May have been an issue with the wifi?
[Galaxy S II General] titanic_fanatic:
Can i get a log of the Google account manager crash please.

Which files did you replace with in the libs/hw folder? The ones from the last build?
[Galaxy S II General] iDynamics:
I will have to reflash the rom to get the log cat which I will do a bit later because I'm expecting a call now.

I replaced everything in the lib and lib/hw folder from the last build as a last resort. Some how it worked.
[Galaxy S II General] titanic_fanatic:
I tracked it down. It's the libwebviewchromium.so residing in /system/lib/libwebviewchromium.so. I'm not sure yet what is the cause, but am going to freshly build the rom since there was an issue with the build where deleting the intermediates folder allowed only that component to rebuild and I think it was actually in relation to this library. Temp solution, you kindof already figured out in a much more dramatic way. Just replace the libwebviewchromium.so with the one from the previous rom if you "NEED TO FLASH" ;) this right away, otherwise, wait for me to update the build with a good version of this file.
[Galaxy S II General] titanic_fanatic:
Just an update, the libwebviewchromium.so issue is fixed and added some other stuff in the process such as panel uv. You can now undervolt the display by up to 500mV which should hopefully help with battery consumption. I also added fast charge. Somehow, the vbus_present code worked it's way back into my kernel. It is now gone for good. New kernel version is 1.1.1 and is being built right now. Will post it after I wake up and test it ;)
[Galaxy S II General] titanic_fanatic:
Here is the Updated ROM/Kernel

Hey guys, not only did I rebuild the ROM, but I added yet again some new features. A big one is the panel undervold interface which allows you to undervolt your display by up to 500mV in increments of 25mV. Controls for this is not yet built into the Advanced Device Settings, but will be in the future. To change the panel uv, open your terminal emulator, and enter the following:

Where xxx should be replaced with a number from 0 to 500 in increments of 25 (ie: 0, 25, 50, 75, 100... etc)

Here is the new download link (I replaced the 20141119 build with this one) and the updated changelog:

Download

Changelog

EDIT:

Just noticed that the panel uv doesn't stick around between boots. To have it set to your value at boot, add a new text file named 92_setpaneluv (no extenstion) to /etc/init.d and inside, add the following:

Again, replacing xxx with your desired undervolt between 0 and 500mV in increments of 25. The blank line at the end of the script is important. Then make sure you set it's permissions to the same as the other files in /etc/init.d.

Now after rebooting, the script will run and set the uv for you at boot time.
[Galaxy S II General] androidman23:
sorry if this has been asked, but are you working on any 5.0 based roms?
[Galaxy S II General] titanic_fanatic:
Yes, as a matter of fact I am. Haven't got it to boot yet, but I know our device can handle it ;)
[Galaxy S II General] androidman23:
Sweet! I'm running it on my one plus one, it's amazing! I'm waiting to get this on my brothers s2 to give it new life again?
[Galaxy S II General] titanic_fanatic:
Try this new Rom. It's so speedy now with all the overclocking. Games are smooth now ;)
[Galaxy S II General] androidman23:
will do! You've done a great job developing for this device:good:
[Galaxy S II General] recordman:
The new ROM causes my phone to reboot just right after the apps are upgraded. The process repeats. I went back to the old ROM which is pretty stable.
[Galaxy S II General] titanic_fanatic:
Did you change any settings before you upgraded your apps?

What kind of reboot, did it freeze then reboot or a sudden reboot?

You say the process repeats, does it boot up into android and then reboot or does it not even get past the boot animation?

Lastly, did you dirty flash? This one has so many changes that you would need to do a clean flash.
[Galaxy S II General] recordman:
I installed the new ROM the same way I've always installed ROMs. I didn't mess with any settings. It freezes for a bit after the apps are upgraded (after the boot animation). The phone reboots and then it goes into the upgrading process again. Sometimes I get to the lock screen before it reboots by itself. I deleted dalvik and the cache before installing. Is that enough when upgrading from the Sept. ROM? I want to avoid having to do a complete wipe before upgrading just in case it doesn't solve anything and I'd have to re-configure the device all over again. If you're pretty sure the complete wipe helps, I'll try that. My daily driver is an N5, so I could use the 757 to help test. Thanks.
[Galaxy S II General] GrAt_On:
Same here

I have the same issue as Recordman, the phone kept rebooting when apps were upgrading, and I noticed it rebooting randomly when using the keyboard in google play store (I did a clean flash)

I went back to the previous build, which doesn't suffer from this issue.
[Galaxy S II General] titanic_fanatic:
This new Rom MUST be clean flashed. Backup your apps with titanium backup and restore only user apps not system apps.

This most definitely would be why you guys are having this issue.

There have been so many changes in this version and is the reason why you must wipe everything.
[Galaxy S II General] titanic_fanatic:
Play was the only app to give me issues. Try wiping it's data, and reboot. Also, you can turn the oc down to 1512MHz which is the stock cm oc.
[Galaxy S II General] titanic_fanatic:
For Rom settings, try Rom settings backup from the market. It supports carbon and Will allow you to backup and restore the settings for the Rom so you don't have to go through and do it all over again ;)
[Galaxy S II General] omar.kassam97:
The new build is running pretty good so far, just realized one bug. When setting up profiles in the settings menu, when I try to change the ringer, media or alarm value, none of the values will stick and they are all defaulted to 2. Otherwise another great build, thanks for the great work!
[Galaxy S II General] GrAt_On:
having issues...

My clockwork is the latest version (september release). I followed the instructions at the front page for a clean flash, i chose factory reset and then chose "clean to install a new rom". Then i flash the radio, then rom, and finally gapps. I also tried manually wiping cache and dalvik, as well as formatting /cache, /data, and /system .

I should also note:

1) When I chose factory reset and clean to install a new rom, i do get a "E:unknown volume for path [/sd-ext]" message in the bottom, but everything else proceeds successfully.

2) While Signature Verification is enabled, I am unable to flash the zip as it displays a messaging that it failed and is aborted. So i disabled it, in order to proceed.

3) I reduced the OC to default, and i wiped the data, cache, and defaults of the Play Store app.

4) I tried several gapps like cyanogenmod and including the one provided in this thread.

However, i still incur reboots in the ROM especially in the play store.

Any ideas???
[Galaxy S II General] titanic_fanatic:
A kernel log would be awesome. To pull one, right after the random reboot when the system is loaded, open terminal and run these commands:

This will copy the contents of the last_kmsg to your sdcard. Please post or email me the file and I'll take a look. A logcat won't do here since this Will be kernel related.
[Galaxy S II General] GrAt_On:
Alright, I'll flash the rom again in a few hours and will send you the log :)

Thank you
[Galaxy S II General] GrAt_On:
Here's the log :D
[Galaxy S II General] GrAt_On:
After installing all my apps, I realize the reboots don't only occur when using the Play Store. It happens randomly at any time, more frequently in the first few minutes of the phone booting up.