yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] titanic_fanatic:
Excellent, well, not that it happened but that you got the logs

and screenshots. I would like to say post them in g+, but you can't attach logs and such and it may just be easier to create a zip of the files and post here. Thanks for asking ;)

I'm sad to report that it still isn't working right. It started off alright, but then all of a sudden everything started fc'ing. I fought with them to turn off art ;) I just got notification on g+ that the gaps are being updated though so I'll do some more art testing after those updates roll out.

Still no reboot, so I'm petty confident now that this is definitely more stable than the older build ;)
[Galaxy S II General] titanic_fanatic:
Excellent, thanks again. I'm looking into this right now ;)
[Galaxy S II General] bijon440:
the locat and screenshots sir.
[Galaxy S II General] titanic_fanatic:
Good news, Been running cm-11 for the better part of 2 days with no random reboots. It's quite stable now. Also, thanks to [MENTION=4896139]Socim[/MENTION] for pointing me in the right direction to fix the lte. It was simple actually, I just needed to add the overlay for the telephony service with the enable lte option set to true :)

The calendar is still not working, neither does the camcorder and art as I explained earlier is causing all the gapps to fc, but everything else seems to be in working order and the vib fix has been applied to this build and works as expected.

Oh, almost forgot. I have not yet added my custom bln settings to the advanced device settings, but will for the next build.

This build is being uploaded to androidfilehost as I write and will now be posted to it's own xda thread.

I'll post the link in all my threads when it's ready ;)
[Galaxy S II General] titanic_fanatic:
Thank you kindly. Did this only happen once? It looks to me like a rotation issue which there have been some fixes for since the build that you are on. I'm inclined to say let's see what happens with the new build, or rather hopefully it will no longer happen.
[Galaxy S II General] sandhu6698:
Sir Can you provide me link for the 4.4 ROM .......want to try ..really Exited
[Galaxy S II General] titanic_fanatic:
I will post the link in all of my threads when it's done uploading and I create the thread.
[Galaxy S II General] sandhu6698:
GOOD SIR .....please Create this in Slim Rom also
[Galaxy S II General] titanic_fanatic:
CM-11.0 for the SGH-I757M

Alright, for those of you who are ready to make a jump to CM-11.0 Kit Kat. It's here, and you will need to have Philz Touch Recovery flashed to your device or you will not be able to flash Kit Kat. This rule will apply to all Kit Kat based ROMs whether it's CM, Slim or PA. The Recovery is backwards compatible and will let you flash older ROMs that have their update-binary replaced with one from Kit Kat. All of my ROMs have their update binaries updated and will be compatible.

Even if you read it once before, it never hurts to read the instructions from top to bottom since I modify each slightly as required for the ROM. Don't forget to take your nandroid backups ;)

[ROM][CM11.0][KERNEL][DEV][SGH-I757M]UNOFFICIAL CM11.0 For Bell SGH-I757M

ENJOY!!!
[Galaxy S II General] fab-4ever:
Hello titanic_fanatic,

Can you tell me what is the difference between CM11 and CM10.2? What is good about this new release? I don't quite understand what is kitkat and everything else, but just that the official ROM of Samsung is **** so I really like your ROMS, but I'm not sure if I should stay on CM10.2 or upgrade.

Thank you for such a hard work! Without you this phone would have been trash since a long time!

Envoyé de mon SGH-I757M en utilisant Tapatalk
[Galaxy S II General] bijon440:
Ya just the once, and after the screen timed out and I unlocked again, all back to normal. Ill run the new build later today anyway to check it out. Thanks muchly! And well done on okay!
[Galaxy S II General] EvilDan:
I get the same result on stock rom so it has to be the battery, not the rom.

Is the developpement on cm10.2 over now with the new cm11 build ?
[Galaxy S II General] RukusX7:
How's the cm11 kernel ;) I've already begun to daydream my commits.

---------- Post added at 09:55 AM ---------- Previous post was at 09:52 AM ----------

Bijon440 what theme is that?
[Galaxy S II General] titanic_fanatic:
The difference between cm11 and cm10.2 is mostly in the UI and the addition of art (which isn't working properly right now).

Kit Kat is designed to consume less memory and is supposed to be better in terms of performance. Right now, without the ability to use art they are about the same in terms of performance.

There are also a couple of things that don't work yet such as the calendar doesn't let you associate a Google account. The camcorder also doesn't work right now.

If you don't mind not having those things for now then it might work for you. You can always take a nandroid of your current cm10.2, test the new rom and see it's suitable for you. If you don't like it, you can restore your nandroid, if you do, then just start restoring your apps and such.

Development will not stop on the other roms as long as there are updates from cm. For example, development has stopped on jb4.1/cm-10 but not cm10.2 ;)

Without media-caf it seems to be operating pretty well. I also added exfat support, but I think I still need to set the module to load on boot before it will work fully.

How about your build, hire is that going? I haven't been by your repo since I checked it out a couple of days ago. Have you add any commits I should look at?
[Galaxy S II General] bijon440:
That theme is called 'reborn' off the playstore. I'm using it in conjunction with bazooka launcher from the avatar team.
[Galaxy S II General] sadowling:
What is this?

Does anyone know what the biq white "Q" with arrows bar is doing over the keyboard in the messaging app? I installed GO Launcher and a Touchwiz theme and it has appeared since. Appears over keyboard in GMail too (have not checked other apps). And how do I get rid of it (short of uninstalling everything)? Thanks.
[Galaxy S II General] titanic_fanatic:
Which keyboard are you using? Aosp, Google? It looks like it's part of the keyboard. Notice how the message line is above that bar. That's why I think it's actually the keyboard although I'm not sure what would cause that. I'll give the keyboard your using a try to see if I get the same results.

You could try turning off the theme and test to see if it's still there to completely rule out the theme as being the issue. I don't think it's go launcher because that is a very solid app, use it myself and haven't had the same happen, at least not yet ;)

EDIT:

So I just tried both Google keyboard and aosp keyboard. Both have a blank space at the top of the keyboard where your word prediction is supposed to appear. My guess is that the theme is causing this because I do not have the Q or arrows in either of my keyboards. First try disabling the theme as suggested above to confirm this. If this is the case, the course of action would be to send the developer a bug report with screenshot like you have here ;) if that's not it, try switching from Google to aosp keyboard or from aosp to Google.
[Galaxy S II General] RukusX7:
Yeah, I updated the defconfig for our phone. But It says in the defconfig..... that its not to be updated and auto updates somewhere else.... Is it okay I updated manually? That would be my own personal commit so far.... I want to have a few more soon.

Skyrocket doesnt seem to have much development on its kernel left and it seems the legacy deviced are only getting roms. I'll have to get creative to find what other commits from other msm8660 devices I can add to our kernel. I am looking into putting together my own little flavor.

Heads up on our kernel, it will not have oc/uv right off the bat. I think the benefits of tweakin your kernel to how you want it, outweigh the benefits of uv/oc. I want to see if modifying mpdecision in our kernel is possible like it is in the Nexus 4. Mpdecision (make-poor decision) is Quallcomms mecanism that controls your second core, and apparently its not very tweakable. Ive read that some kernel developers leave it alone, and others will implement their own method to control the 2nd core, disabling mpdecision alltogether, which I understand helps keep the phone cooler, more efficient and make the battery last longer. This. All I care about is battery life. I am hoping its this that will help us out. I am led to beleive that Mpdecision is responsible for setting our second core to come on as a different governor as our first core.

If there are any suggestions for anyone, or something you would like to see.... please feel free to blurt it out, I'll see what I can do.

I'm 100% open to suggestion on our new kernel
[Galaxy S II General] sadowling:
I re-applied the theme and all seems fine now, not sure what the problem was. I will contact the developer with the details. As always, thanks for your efforts...looking forward to CM 11.0.
[Galaxy S II General] titanic_fanatic:
What config options did you change? Did you change them directly in the defconfig? You can edit it manually no problem and the changes should take, even without make clobber your out dir so making a change should be pretty quick to test. And you can always use one of my boot only zip as a template for flashing only the boot.img for testing. Very handy, and if you take a nandroid before flashing so as to backup your current boot.img, you can also restore only the boot.img if it causes a bootloop. This is how I test my tweaks to the kernel.
[Galaxy S II General] RukusX7:
Yeah I've been using one of your flashable zips. I haven't bothered to upload a kernel to test as of yet because the governors aren't working right and battery life seems poor. So no real improvement's yet. I manually edited the defconfig. Perhaps there is a different way I can configure things so it makes what I want in the kernel? Until I edited the defconfig's CPU governor section, I was unable to add the new governors.

Thanks for the tip about the boot.IMG backup. I hadn't considered that. :)
[Galaxy S II General] Socim:
MPdecision is working. You can cherry pick the commit from hellybean's repo.
[Galaxy S II General] titanic_fanatic:
So for governors and io schedulers, there is a descent tutorial over on xda university:

XDA University: Adding features to your kernel

It explains the ins and outs of adding governors and io schedulers. a nice trick that I use after adding the governors is to update the defconfig automatically like this... These commands should be run from WORKINGDIR/kernel/samsung/msm8660-common

the first command uses the current defconfig and adds any new configuration items to it and saves it in .config at the root of the kernel dir. The second command essentially echo's every line in the .config file using the cat command and then outputs it to the cyanogenmod_celoxhd_defconfig. The last command cleans the kernel directory or you will run into build errors.

If you want, before you run the second and last commands, compare the .config with the defconfig to see what changed, you can even update your defconfig in that manner instead of using the second command, but you still need to run the last command to clean the kernel directory.
[Galaxy S II General] titanic_fanatic:
Philz touch cwm was just updated and now uses a new exfat module for mounting the sdcards. It's supposed to be faster than the fuse alternative. This version also fixes the resolution of the background image, the software buttons and the vibration.

http://xdaforums.com/showthread.php?t=2552634
[Galaxy S II General] RukusX7:
Is there anything I can add from your repo?
[Galaxy S II General] Socim:
I only changed something related to dali series, so please look at the commits on hellybean's msm8660 repo, almost all commits were picked from there. Please note in kernel thermald won't work and will cause SODs for dali, I am not sure if it works for celoxhd.
[Galaxy S II General] WapGiovan:
Just wanted to say thanks to OP for his assistance and patience. ROM works great without any problems.

I'm now a happy user of the SGH-I757M aka SII HD LTE without any Bell Apps or other junk.
[Galaxy S II General] slushee:
Is it possible to set up a custom boot pic or animation?
[Galaxy S II General] manfromgta:
The boot animation resides in /system/bin I believe. Replace it with one of your liking.

Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
[Galaxy S II General] iDynamics:
Replace the bootanimation.zip file in System/Media.
[Galaxy S II General] RukusX7:
DIABLO KERNEL 2.8 FOR THE SGH-i757M CM-10.2

Unofficial CyanogenMod10.2 ​

​

Just like the CM team.

"Your warranty is now void. We are not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at any of us for messing up your device, we will laugh at you. Collectively, and at the same time."​

Bugs.

Should be the same as [ROM][CM10.2][RECOVERY][KERNEL][DEV][SGH-I757M]UNOFFICIAL CM10.2 For Bell SGH-I757M​

Installation instructions

1. Download ROM

2. Reboot into recovery, You must use CWM 6037+

3. Please back up your ROM before you begin!.

4. Wipe System, Data, Cache, Dalvik.

5. Flash the ROM

6. Flash 4.3 gapps

7. Reboot

8. Let it sit a while.

9. Enjoy CM11

YOU MUST USE A JELLYBEAN RADIO!​

PLEASE USE TRICKSTER MOD TO CHANGE KERNEL SETTINGS.

(Other Kernel tuning apps may cause RRs and they do not allow you to use all of the features)

Diablo Kernel Features:

- Kernel version 3.0.101

- I/O schedulers CFQ, BFQ, ROW, NOOP, DEADLINE, SIO, VR, and ZEN

- Governors Intellidemand, InteractiveX, Ondemandx, Lazy, Wheatley, Smartass, Badass, Lionheart, HYPER, Samsung and normal Stock options too.

- CPU OC - 1836 MHz

- GPU OC to 320 MHz for 3D & 266 MHz 2D

- MSM_Mpdecision (non-stock) - Showp1984

- Thermal - Showp1984 - Keeps your phone from overheating while Overclocked.

- Fsync Toggle - "Turn it off for better performance but be aware that you may encounter data loss if your phone crashes"

- USB Fast Charge

- Sweep2Wake

- Voltage Control

- Frandom Lag Reducer

- Smaller sized kernel due to XZ compression

- IO Boosters

- Frontswap Support

- Fixed Annoying Bluetooth Wakelock

- CD Rom Emulation - (Use DriveDroid or something similar)​

Kernel Source

Rukusx7

ROM Sources

titanic-fanatic

CyanogenMod

Special thanks goes out to:

* [MENTION=4859152]titanic_fanatic[/MENTION] - For his continued development of Cyanogenmod and other great ROMS. Most importantly for staying dedicated and helping me learn along the way! If it was not for him, this could never have happenned!

* [MENTION=5105835]Cl3Kener[/MENTION] for his Kernel

* CyanogenMod Team - ROM Base

* [MENTION=673068]dsixda[/MENTION] - Initial port of CM9/CM10 for SGH-I757M

* [MENTION=4974935]Strange Peer[/MENTION] - Continued development of CM10

* [MENTION=4435341]bijon440[/MENTION] - Contributor

* [MENTION=4036181]kj2112[/MENTION] - Contributor

* [MENTION=5077807]Tronith[/MENTION] - Contributor

* [MENTION=3651088]Zippy Dufus[/MENTION] - Contributor

* [MENTION=5411569]formercontra[/MENTION] - Contributor

Download DIABLO Kernel Unofficial CyanogenMod10.2 for the SGH-i757m
​
[Galaxy S II General] RukusX7:
New build is up.
[Galaxy S II General] grandmaster_b:
Found a bug in MMS if I try and send an oversize pic e.g 2mb it won't resize at all so therefore won't send this is first time I have had this issue.
[Galaxy S II General] RukusX7:
So I've increased my /cache partition to 300MB. But i had to do a lil work to get that.

We plan on releasing a tutorial on how I made this happen. We've simplified and we've devised a way that we can get a 250MB cache partition working on any one of your phones. The skill level should be considered intermediate. Meaning I expect you to know what you are doing, but its not that difficult to understand or do if you do things correctly.

This is great news for our phone and the gapps package and even general performance!!

---------- Post added at 03:57 PM ---------- Previous post was at 03:46 PM ----------

i'm now running the official gapps package. Looks like we needed at least 118MB. so 250MB is more than enough!

;)
[Galaxy S II General] iDynamics:
Great news!
[Galaxy S II General] Socim:
Pit?
[Galaxy S II General] RukusX7:
I pulled the pit from my phone directly and its actually identical to the celox.pit, except for some partition size differences. But the pit i pulled from my phone doesnt match what is actually on my phone for partitions....

So decided to flash only the pit I pulled from my phone. I got this error on my download mode screen on the phone:

SECURE CHECK FAIL : PIT

Then i tried the celox.pit and same thing. This one I didnt expect to work. Its odd the one i pulled from the phone wont work....

Maybe I need to pair that with a rom to flash??? I didnt want to, so i partioned manually with parted in adb. it was real simple actually. Releasing a tutorial soon.
[Galaxy S II General] slushee:
I'm confused. Are you taking over for this ROM from titanic?
[Galaxy S II General] iDynamics:
Is the pit file you pulled from your phone the one that's in your android file host folder? I can try flashing it if you'd like.
[Galaxy S II General] RukusX7:
No. I am not taking over. If you look at the special thanks to in this rom, Ive always been part of the team. Ive just learned a lot, and now Ive been able to build roms and kernels from source. :) As well as a few other tricks along the way Ive learnt.

My rom that I've built, (you can go back a few posts and click the link) is based on titanic_fanatics, which is based on CyanogenMod. But all in all its basically CyanogenMod. I needed his device files and vendor files, as they are specific to this phone, and he has maintained them so that they should work. I was able to compile a kernel that is based on skyrocket and hercules kernel source, which is almost identical to the source required to our phone. Identical enough that everything works, and every tweak I need is working properly.

Lots of roms out there have a team behind that maintains it. All in all said, its titanic_fanatics rom in the end. I just help with the little things when I can.

---------- Post added at 09:14 PM ---------- Previous post was at 08:57 PM ----------

Yeah celoxhd.pit was pulled from my phone. You can flash that. AT your own risk of course. ;) I see no risk tho.... you can also try celox.pit I never uploaded it. but the partioning is identical. other than some partition sizes. Thats ESPECIALLY at your own risk. The celox.pit holds the partioning for the Skyrocket. which.... is the same as our phone in that aspect.
[Galaxy S II General] titanic_fanatic:
I'm still here, just been busy with building the new pa and getting my business off the ground. There will be fresh builds coming up soon synced to the sources that is.
[Galaxy S II General] iDynamics:
Got the same error message as you rukus.
[Galaxy S II General] RukusX7:
One of us should get bored and try flashing an official firmware with that pit. ;)
[Galaxy S II General] iDynamics:
Lol. Alright I will try it.
[Galaxy S II General] RukusX7:
haha. you're a good man,
[Galaxy S II General] iDynamics:
Well it didn't work. :(

View the attached image to see if I set it up correctly.
[Galaxy S II General] RukusX7:
You did things correctly.

What was the error on the phone itself?
[Galaxy S II General] iDynamics:
It gave me a check fail message in red text.
[Galaxy S II General] RukusX7:
I have not done much research on this error message yet, but it appears that somehow flashing the pit is locked. I felt it was suggested the other solution was to get in their with some elbow grease and make the partitions yourself.
[Galaxy S II General] titanic_fanatic:
Since it's all done using the parted binary, it could probably be scripted and automated somewhat.

How you ask, you include the script in a flashable zip to be extracted and run in recovery. That will only work if we can specify the default settings on the command line since no user interaction will be able to take place.
[Galaxy S II General] RukusX7:
How is it specified to the phone which mmcblk partition holds our fat32 storage partition?

I was thinking, if we do the mod we are thinking, we lose a partition, moving our fat32 storage partition from mmcblk28 to mmcblk27.

For anyone who wants to help, here is the guide I've written. Please do not use. Its not complete and there is chance you could brick your phone if done improperly. I just want feedback. If you do choose to go in elbow deep, please know what you're doing.

Increase /cache size of celoxhd through partioning
[Galaxy S II General] titanic_fanatic:
Vold takes care of that using the fstab.qcom file in the msm8660-common repo. It's physically specified as mmcblk28 the external is set to auto so it will take the next one in sequence.
[Galaxy S II General] RukusX7:
So this is an issue?
[Galaxy S II General] titanic_fanatic:
I can't see a reason why it would ;)
[Galaxy S II General] RukusX7:
You said it physically points to 28 for the fat32 storage partition. With our mod, our fat32 storage storage partition will be at 27. This is not an issue?

Also, you have duplicate commits for the screen unlock fix in your kernel. Which ones should i commit to fix the screen delay in my kernel?
[Galaxy S II General] titanic_fanatic:
Are you certain that it's been reset to 27? Can you access it with a file manager?

The duplicate commits are my screw up. Just use the latest commit, they're all the same ;)
[Galaxy S II General] titanic_fanatic:
I'll diff your new layout with the old one a little later on to see clearly the end result.
[Galaxy S II General] RukusX7:
I am certain because thats the nature of how it works. if you have 28 things and you take one away, you have 27. each block counts up from 1. No blocks get skipped. So if it expects to find something at block 28 and the partioning ends at 27.... well i think it explains itself.

so use this commit?

Disable FEATURE_BRIGHTNESS_DELAY_AFTER_WAKEUP

and

Fix Screen Unlock

---------- Post added at 11:10 PM ---------- Previous post was at 11:07 PM ----------

The guide is not a representation of my partition layout. I put the preload/tombstones partition back to maintain layout integrity so each block is where each mount points to. i have a 28th block.

With the method I posted in the guide, it allows you to make your changes without having to format your fat32 storage partition, by making two partitions into one larger partition. If you look at your ORIGINAL table before modifications, this will be the space between the end of block 25 and beginning of block 28.

Just a thought. the method can still work. The space between 25 and 28 is about 250mb. Just make a 248MB mmcblk26 and a 2MB mmcblk27 as just a placeholder. Problem Solved. We get to maintain partition layout.
[Galaxy S II General] titanic_fanatic:
As far as I know this is how vold works. I'll have to look at the code for it to understand what it's doing, but vold takes the fstab and uses it's settings to setup the Mount points, and the internal card is specified as 28.

I just looked at your new layout again and see what your talking about, so my only question is can you acces that partition by file manager, if so, I can't think of any repercussions.

Can you post your output from the mount command from terminal just mount with no arguments. It shows information about the mmcblk mappings
[Galaxy S II General] RukusX7:
Keep researching, you'll understand. You wont learn anything from my phone or partition layout that you cannot from your own. Its not any different other than partition sizes.

The difference is in the imagined partition layout in the guide. Which makes use of 27 partitions instead of 28. Mount points and partitions are not two of the same thing.

---------- Post added at 11:48 PM ---------- Previous post was at 11:21 PM ----------

I've updated the guide to maintain partition layout. That way you won't need to rewrite the code for the phone.

http://pastebin.com/qRHUDxWq