yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] two_cents:
First off I'd like to say im a recovering flashaholic from galaxy nexus/tbolt/nexus 7 but i've been good lately I'm happy with sense 5 in its simplicity.

but here is my issue... on all the joel based sense 5 roms(hatka, digital dream m7, stock joel port) i get screen wake on incoming messages and I can't figure how to turn it off... i do not get this behavior on newts roms(up thru 1.6, didn't try 2.0 yet)

I always do a full wipe and fresh installs from TiBackup with no system data and I can't find it in settings on messages or system setting

I hope I'm missing something stupid but I have looked everywhere and its really the only thing wrong with the roms and I like the themes
[HTC Droid DNA] th3_g00b:
I dont have a fix for that problem. I would recommend using Handcent as a default messaging system. It has all those options and more so that should fix ur problem if ur willing to try it out :)
[HTC Droid DNA] two_cents:
I used handcent on my thunderbolt and my galaxy nexus but I stopped using it because why install an extra app for something that your phone already does fine... I don't use the extra customization
[HTC Droid DNA] th3_g00b:
Well, in that case I hope you find a fix. GL
[HTC Droid DNA] two_cents:
sorry that i sounded rude... I did install handcent and turned off stock notifications and it stopped... I'll use it for now and maybe I'll try to find a stock mms app and uninstall it and install a modded version
[HTC Droid DNA] Jrocker23:
This may be a dumb answer but did u uncheck the notification preview option in the stock app "menu-settings-notification area" ?
[HTC Droid DNA] two_cents:
yes the only thing that stops it is turning off all stock notifications
[HTC Droid DNA] los1223:
I'm running Hatka Supreme 1.1.0 and the Screen Wake on SMS was an option in the Aroma installer when you flash the ROM. I don't know how to change it after the fact...
[HTC Droid DNA] two_cents:
I'm on digital dream m7... I locked up aroma twice installing so I may have missed it... Will try a dirty flash to see if I can fix it

Edit: no aroma on digital dream... I guess I had a lock up on my nexus 7 the other day... I'm going back to newts ... I switched just to try out something new... Love the theme and everything but handcent seems so slow
[Sprint Samsung Galaxy Note II] patrickjaden:
Hi, I want to flash a custom rom for a family member but they're not too tech savvy so I'm looking for something similar to stock touchwiz but with wifi tether etc, also something that provides decent battery life. Also if anyone has any info on kernels that would be helpful. Thanks!!
[Sprint Samsung Galaxy Note II] TMPOOLE:
Forgive my assumption, but your information shows your a Tmobile guy. Is the family member you are trying to flash with Sprint and is their device a Note 2? You might be in the wrong place.

If not, the stock experience is quite good out of box. If they don't know what they are doing, I'd skip setting them up with a custom rom unless you know what you are doing and are close so you can fix any problems that come up. I have the same challenges with my family and since they can barely use their phone's capabilities as delivered, it just isn't worth setting them up with a custom Rom until they at least have mastered the basics of what they have originally received.

If you are looking for the standard tweaks available, just about any of the Roms in the Android Development forum will work. From what I've read, we've got a great bunch of developers working on the Sprint variant of the Note 2. I use Whomp 3.4 presently, and possibly forever, but I read great things about almost all of them. Just don't have the time to evaluate once I found one that met my needs.

As for kernels, the stock kernel works great out of the box. I've tried others, but the need to Tweak between updates was a time sink that I decided to skip for the future. Best is the enemy of good enough, and when good enough is actually great, what's the point? Particularly if your installing for a family member. They won't thank you for causing their phone to reboot randomly.

Good luck.
[Sprint Samsung Galaxy Note II] patrickjaden:
I used to have sprint but canceled my service with them. TBH the only reason they want a custom rom is because WiFi tether just can't seem to work
[Sprint Samsung Galaxy Note II] patrickjaden:
bump
[Sprint Samsung Galaxy Note II] not.plugged.in:
you can keep the phone stock rooted and just use treve wifi mod, thats what i do. you cant actually use the phones built in hotspot menu in the setting but just run it like an app and you have wifi hotspot. there are even settings in it where you can set up passwords and see a list of who has jumped on your network and whatnot

I just followed the advice from qbking77 and it was pretty simple

http://www.youtube.com/watch?v=JGWqLRNoJLg

---------- Post added at 02:42 PM ---------- Previous post was at 02:25 PM ----------

also an all in one spot area to root/unroot and a few other small tweaks that got me started, might help you out a bit too

http://xdaforums.com/showthread.php?t=1969947
[Sprint Samsung Galaxy Note II] patrickjaden:
Thanks I'm gonna do this over the week and see how it turns out
[Sprint HTC One (M7)] azbigmike1369:
I am looking for an apk for a blue themed quick boot 4 in 1 power app. I really liked it when I had my Evo 3d, but I thought I had it saved on my computer. I guess I don't. Hope someone sees this and points me in the right direction.
[Galaxy S 4 i9505 Original Android Development] garwynn:
Post Updated from Original

Cyanogen has posted a i9505 common device tree.

It is based on his working configurations for US T-mobile.

There are two ways to get this:

1) Clone these repos:

https://github.com/CyanogenMod/android_device_samsung_jf-common

https://github.com/CyanogenMod/android_kernel_samsung_jf

https://github.com/CyanogenMod/android_device_samsung_jfltetmo

2) Set up your CM environment and "breakfast jfltetmo" to pull the 3 repos above.

The first 2 are the common device and kernel. The third can be used as a base for your device.

(So fork it to your own repo and start making changes)

Hope this gets other variants up quickly! Thanks again to Cyanogen for the work to get it this far so quickly!
[Galaxy S 4 i9505 Original Android Development] Entropy512:
Since it's Qualcomm based - First thing you should do is fork https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=summary

Then go to Qualcomm's CAF release list at https://www.codeaurora.org/xwiki/bin/QAEP/release and go through the tags for your SoC and Android version. Check each out one by one. I'm fairly certain you are APQ8064T. Whcih is odd, there are no tags for the T variant...

git checkout <TAG>

Drop the Samsung tarball on top of the checked out tree, and diff it.

git diff > ../<TAG>.patch

Keep going until you find the patch that is the smallest. This is likely the CAF base that Samsung started from.

Two other things:

Be warned, Samsung hacks the **** out of their bases

Also, try to coordinate with cyanogen himself, I believe he'll be working on either the AT&T or T-Mobile variants.
[Galaxy S 4 i9505 Original Android Development] mithun46:
What if i need to make 1 for I9500
[Galaxy S 4 i9505 Original Android Development] garwynn:
Thanks for the starting point, Entropy! I'll start on that during my lunch break.

I'm keeping up IRC on the build box but just sent an alt contact in case anyone else you know is interested in collaborating.

I'm guessing that they're not differentiating (yet) between the APQ8064 variants.

So I'll start pulling standard APQ8064 and hopefully get lucky.
[Galaxy S 4 i9505 Original Android Development] Entropy512:
might want to look at cpu_is_apq8064ab related stuff in the jb_2.5 branch to get an idea of where stuff is - The APQ8064T may be referenced as APQ8064AB in kernel sources. Not sure.

Still doesn't answer which tag to follow.
[Galaxy S 4 i9505 Original Android Development] cerj:
We are lucky to have such a driven Dev. Thank you gawynn, for all you have done, and all that you will do.

Kudos from the E4GT community.
[Galaxy S 4 i9505 Original Android Development] garwynn:
No but it does allow me to thin out the list.

Every build that I have seen so far is March so we should be able to rule out any April builds.

So once I get access to my build box again (TV died yet again...) I'll start at the bottom and work my way up.

(Edited post) So far the above (AFAIK) addresses kernels. Still haven't addressed device.

Thinking we can still use this for graphics base:

https://github.com/CyanogenMod/android_device_samsung_msm8960-common

I almost want to fork d2-common for the jflte common device and start replacing S3 with S4 details.

I have that 9505 system dump on my build box so I can start extracting stuff from there.

More as I keep reading and digging.
[Galaxy S 4 i9505 Original Android Development] cdss:
Looking forward to development for S4 , planning on getting it as soon as my renewal will allow .
[Galaxy S 4 i9505 Original Android Development] garwynn:
Cyanogen found kernel already, head is jb_2.5, didn't get the branch point but says he knows what it is.

In the meantime I went ahead and stripped d2-common and used that as a shell for jflte-common device.

Future status updates on this will be placed here at Cyanogen's request:

https://jira.cyanogenmod.org/browse/QSDB-25

Feel free to take a look there for progress reports.

Will be requesting thread lock for now.
[Galaxy S 4 i9505 Original Android Development] Entropy512:
As far as graphics base you'll almost surely have the same flags as any other caf-display device.

Sound can get a bit more funky... I'd look at mako, Sonys, and Oppo Find5 for inspiration there as those are the current non-T APQ8064s.
[Galaxy S 4 i9505 Original Android Development] garwynn:
i9505 Latin JB source has Alsa audio folder in the platform side - wouldn't be able to use that?

You know what? Seeing as OSRC pulled it (for now) I'll make a repo for both the kernel and platform side and add the links here in a sec.

Edited:

https://github.com/garwynn/i9505_latin_jb_platform

https://github.com/garwynn/i9505_latin_jb_kernel

Hopefully we get the L720 stuff here soon so I can compare ROMs and kernels against the ones I have already.

Should give a good idea as to what can be common vs. proprietary.
[Galaxy S 4 i9505 Original Android Development] garwynn:
Had to change my search for the kernel based on a misunderstanding of where to start.

So I started with the jb2.5 head and pulled this list from it.

As you can see I've been trying a "divide and conquer" method to figure out where the branch point is.

Tried checkout method after cloning the repo but can't seem to get it to pull the branch source.

So for now I'm resorting to a rather tedious process of clone branch, diff, delete, repeat.

Also doesn't help that I lost the build box for a day but hopefully will be fixed by 7 pm.

So while I wait for the build box to come back I'm going to see if that AT&T dump is different from the i9505 one I have.

If so should shed some light on what in the ROM will be common and what won't be.
[Galaxy S 4 i9505 Original Android Development] ilabs:
I don't know much about porting and building CM but I noticed there was some confusion about the chipset model. I'm wondering if this might help you in any way:

http://www.anandtech.com/show/6914/samsung-galaxy-s-4-review/3
[Galaxy S 4 i9505 Original Android Development] Entropy512:
That isn't useful. We are fully aware of which chipset is in this device. What we're not entirely sure of is which release tags/branch in CAF it corresponds to (unlike most other qcom processors, there is not a direct match between the chip's identifier and any CAF tags. That said, it is starting to seem like CAF is using the apq8064 releases for both apq8064 and apq8064t)
[Galaxy S 4 i9505 Original Android Development] garwynn:
As embarrassing as this may be for me, let my facepalm teach others...

Read advice from mentors well.

And if not sure, read it again. And if still not sure, read it

again

.

Bold and italics below are my emphasis.

Why does this matter? My diffs went from 24MB to 4MB and is a lot easier to see what may be going on.

When we do get to find the branch point it will make a huge difference when I pull a more recent version and then want to apply that patch to the newer version.

Entropy, had another question... In stock kernels I would normally patch Linux before doing anything else.

I'm assuming I'll want to grab the latest jb_2.5, patch Samsung's mods in first and wait until we get stable before patching Linux versions?

Just because we add Samsung's mods in doesn't mean everything will work perfectly as-is... and that logically would need addressed before anything else.

And still waiting for my build box to come up - the host is having their ISP issues addressed. Thankfully the home dual boot works great for simple things like these kernel diffs.
[Galaxy S 4 i9505 Original Android Development] Entropy512:
You mean pull in patches from kernel.org? I personally don't do that any more - it usually causes more problems than it is worth. The only time I've done that was a situation when I had to match d2's wifi backport on 4412 devices.

So far, devices in CM are a mix of two approaches:

1) The old (and usually quick) approach of taking the manufacturer tarball and dropping a bulk update from mako onto it. Since this is a MUCH newer CAF base and is 4.2.2 - this may not be necessary. You may just be able to get the kernel running CM10.1 with not much modification.

2) Chunk up the manufacturer's diffs and rebase them onto the latest jb_2.5 - d2 has done this, HTCs are in the process of doing so, and Sonys are probably going to do so in the next month or two. Same for Oppo Find5 - we used approach 1 initially, but are switching to 2.

For your sanity, you probably want to chunk up the manufacturer's diffs into smaller parts if you can. The workflow I used was:

Check out the closest CAF tag once you determine it.

Check out a new branch at this point using

git checkout -b <branchname>

In my case, I named the branch for find5 find5_CAFTAGHERE so I would always remember the tag.

Drop the kernel tarball on top of the CAF tag

Commit the whole big mess

Now, here's the fun part:

Unstage some files out of the commit. For example, if you want to unstage drivers/media/video out, do:

git reset HEAD^ drivers/media/video

Then

git commit --amend

This will remove the changes from drivers/media/video from the megacommit

Then

git add drivers/media/video
git commit

Commit just those changes. Try to find associated headers if you can from include/

Now, if you just split out one commit:

git rebase -i HEAD~2

to switch the order so the megacommit is the last commit for further chunking.

It's time consuming but makes the chunks much easier to analyze.

When I get home, I'll post my bash alias 'gitshowfiles' which shows a list of all files changed by the last commit. It's hightly useful.

When you're done, you'll have a nice reference like:

https://github.com/Entropy512/kernel_find5_reference/commits/find5_A8064AAAAANLYA101034
[Galaxy S 4 i9505 Original Android Development] garwynn:
With the build box back in business I finally got to the point Entropy was talking about.

For reference here is the commit:

https://www.codeaurora.org/gitweb/q...it;h=b5075e02c2ff1d959c589552c62329c4797b0535

And I've attached the diff file so those following along can keep doing so.

(I've posted the same stuff on CM's Jira as well)

So I'll start 2 repos next.

1) Fork current CAF jb_2.5 to a new repo.

https://github.com/garwynn/kernel_samsung_jflte

2) Fork above version to this repo:

https://github.com/garwynn/i9505_CAFDiff

...where I'll start the process of splitting the big diff into smaller ones, just in case they are needed.

Now it's possible that Sprint's kernel could have branched off differently but there's an easy way I can think of to check that. Take the i9505 kernel source I have now, drop Sprint's on top and run a diff to see how different they really are.
[Galaxy S 4 i9505 Original Android Development] garwynn:
And just an update. Sprint's GS4 is making its way to folks today. One person already has and I'm trying to get what I need to really get going.

Update 1:

Odin mode shows "Write Protect Enabled" - wondering if this means bootloader is locked.
[Galaxy S 4 i9505 Original Android Development] garwynn:
Few updates while I get things moving.

A second look at that LA kernel had what seems to be everyone's defconfig. Added and pushed to common kernel.

You'll probably need to combine your specific additions still to jf_defconfig to get a full one.

At least the Sprint one identifies an Audience audio chip and binary that should be there.

Did an initial push of common device folder after confirming Sprint's fstab matches common i9505.... so I'm guessing they're all the same. It's very rough so wouldn't try using it yet... just want access to it in case I pull to my home box. Now working to get a device specific one up enough to try a CWM build. Going to have to hold testing anyhow until we get a full restore and figure out about that write protect.
[Galaxy S 4 i9505 Original Android Development] garwynn:
OK, for those not following the SPH-L720 thread, I'm doing test builds of CM/CWM at the moment to see what I can get working before I move over to the kernel.

I tried including msm8960-common and it failed on kernel issues. Think I'm going to leave it out for now and try just getting the CAF jb_2.5 to build successfully first. I can leave in qcom-common and that seems to at least play nice.

CWM working for SPH-L720 but users reporting that moving up/down requires 2 key presses to get it to move. Alpha 5 was reported as losing External SD card functionality - not sure why as I didn't change the fstab. i9505 users reporting that it didn't work, suggesting there may be a difference. We better nail that down and if need to move something from common to variant, do so before others start building off of it.

I'm starting to read the Find 5 configs as it seems one of the only ones with the Adreno 320 config. But again, I've got to get the kernel to build before I start really getting into this stuff.

I'll push updates to repos tonight after I get another successful build.
[Galaxy S 4 i9505 Original Android Development] victorator:
New thread here

Do as the instrucions tell you before complaining :)

Thumbs up? :)
[Galaxy S 4 i9505 Original Android Development] Entropy512:
Not a good idea. This usually leads to a race to be first, with some people taking nasty shortcuts that cause them to get the donations even if they might not be able to take something to the finish line...
[Galaxy S 4 i9505 Original Android Development] victorator:
I know you despise what I did there, but honestly I do it for fun and for satisfaction, I don't give a rat's ass what anyone thinks. People are lazy and didn't do a thing since Steve Kondik made the jfltetmo build working... Well, I did it.
[Galaxy S 4 i9505 Original Android Development] blesio:
And it's great that you did, working like a charm

Sent from my GT-I9505 with CM 10.1 by victorator
[Galaxy S 4 i9505 Original Android Development] daylight95:
How do I actually flash the rom? It's a .rar. Do I use odin or what?
[Galaxy S 4 i9505 Original Android Development] Warm_ice:
So you think victorator don't deserve a beer? Instead of hitting a bull to work why not give him a handful of stuff to get him do his best. His effort whether a failure or not, is already a sweet thing my friend. He gets the reward.

Cheers!
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
No Andrew isnt saying that Victorator doesnt deserve a beer for building from source. He is trying to warn everybody not to make a contest out of it before bricked devices pop up everywhere.
[Galaxy S 4 i9505 Original Android Development] moriansafas:
I thank u very much for your work and I apreciate your lonely efforts. It is the first step needed.

Yet I am still concerned about cm getting official on the s4...

Edit:

Any news from cm devs?
[Galaxy S 4 i9505 Original Android Development] ilabs:
I'm still trying to understand everything, but does the I9505 version at least have everything needed to make aosp roms? I know the kernel sources are available which generally always are, but other stuff like binaries and drivers?
[Galaxy S 4 i9505 Original Android Development] om22:
is there any hope for 30fps 1080p recording? because currently on cm10.1 it has only 18 fps. 720p even has 16 !! fps
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Where is DOC? Any news on official cm builds?

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Wrong.

I get 1080p AND 30fps.

You have to use another camera app.

I use snap camera. One of the best!

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] TheMrCaveman:
Any progress?
[Galaxy S 4 i9505 Original Android Development] moriansafas:
Any news on official support?

Edit:

Sent him a pm, no answer yet.
[Galaxy S 4 i9505 Original Android Development] :
Nice to see you here as well :) last time I saw you was on galaxy s2 but just to ask how's cm on galaxy s4? I know it's probably easier to get everything fixed on qualcom. But I ain't sure
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
I ditched my S2 a month ago.

Qualcomm is MUCH easier than exynos (thanks to docs and stuff).

But it will take a while.

The early cm builds on S4 are really good. Most things work (nfc doesn't and a few other minor things) and it's nice to see cm on a 1080p screen. But it lags more than stock samsung roms atm. But it will be fixed. ;)

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] :
Probably because they haven't set it to hardware acceleration as default. I think they usually do so and it works like real butter. Not sure though. We'll at least it works :)

Congrats Victor to make it boot and happy your working on it as well. :)
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Hw acceleration works..

But it's something else I guess.

But once that is fixed cm10.1 will fly on this phone.

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] moriansafas:
Just got the pm back from D.O.C.

He's saying that he has not had time till now and that he will get to it if he finds time to do it. I thanked him.

I am sure real life is more important than cm on the s4. :p
[Galaxy S 4 i9505 Original Android Development] D.O.C:
Well, actually I havent found the time and will get into it when I find the time. But, regardless of this, victorator already pushed some commits to cm and was waiting for approval no? Maybe I am mistaken?

D.O.C

Senior Moderator

XDA-Developers
​
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
At least he can do it :). Great to hear!

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] Lazy79:
I am not sure.. as far as I remember, vic said he would like to but they would reject it (of course) because so far there is no trunk/branch for the euro/intl version, just tmobile usa and canada, and thus, specific commits would be rejected if they were for the I9505 intl... just normal. or am I wrong?
[Galaxy S 4 i9505 Original Android Development] garwynn:
What I'm doing is hosting my device specific changes and I manage that on my own. Jf-common and others in cm repos can be submitted through Gerrit.
[Galaxy S 4 i9505 Original Android Development] Lazy79:
thanks for clarification garwynn! :)
[Galaxy S 4 i9505 Original Android Development] -sandro-:
One question, when Google releases the source code for the s4 nexus edition developers will be able to use those aosp sources to get a perfect cm10.1 right?

It should be the same hardware from what I know.