Difficult to develop for GS4?

Search This thread

Piaband

Senior Member
May 18, 2011
376
63
Do all these new sensors and proprietary software (camera features, gesture features, etc) make it more difficult to develop customs ROMs for the gs4? Or will we just get ROMs that don't use all these new features and sensors

Sent from my aokp_tenderloin using Tapatalk 2
 

cdmoore74

Senior Member
Aug 5, 2008
343
76
round lake
If it's anything like the Note 2 you will loss any Samsung tweaks if you go with a non-touchwiz Rom. Even GPS and bluetooth is a little hairy on Aosp or cyanogenmod Roms. But each phone/team working on the Rom is different. I'm actually sticking with a custom touchwiz Rom because I need the reliability for a business trip this upcoming week.
And it will be extreme luck if the IR sensor works without Samsung's framework. The IR port is the one thing I've been dying for to make a come back. I would actually pay $20 for a fully programmable IR app that has the same functionality of one of those expensive Logitech models.
 

GGXtreme

Senior Member
Dec 23, 2010
769
155
New York City
The development scene for Samsung phones has been huge and vibrant. Samsung is nice about keeping things unlocked and releasing source code, and while it may take time for AOSP/CM/AOKP ROM's to be fully functional and stable the S4 will have plenty of custom ROM's in its future.
 

cdmoore74

Senior Member
Aug 5, 2008
343
76
round lake
The development scene for Samsung phones has been huge and vibrant. Samsung is nice about keeping things unlocked and releasing source code, and while it may take time for AOSP/CM/AOKP ROM's to be fully functional and stable the S4 will have plenty of custom ROM's in its future.

I have no doubt that the S4 will get AOSP/CM/AOKP roms but the OP question was about the sensors. You got temp sensor, IR sensor, hover with finger sensor, and some of the camera tweaks. I don't think those Roms will have the sensor fully functionals. That's the issue I have right now on my Note 2. I love the cleanness of a stock Android Rom but I miss it when a note automatically pops up when the s-pen is removed. And battery life on touchwiz Roms appear to be better. These are choices we're going to have to make.
 
  • Like
Reactions: Piaband

Livebyte

Senior Member
Jul 14, 2012
537
336
Do all these new sensors and proprietary software (camera features, gesture features, etc) make it more difficult to develop customs ROMs for the gs4? Or will we just get ROMs that don't use all these new features and sensors

Sent from my aokp_tenderloin using Tapatalk 2

I assure you it will be huge and vibrant, for now....
Wait 1 year later.

S3 & Note 2 users will now experience what S2 and Note users experienced for the past year. Total nightmare and hell.
 

Piaband

Senior Member
May 18, 2011
376
63
I have no doubt that the S4 will get AOSP/CM/AOKP roms but the OP question was about the sensors. You got temp sensor, IR sensor, hover with finger sensor, and some of the camera tweaks. I don't think those Roms will have the sensor fully functionals. That's the issue I have right now on my Note 2. I love the cleanness of a stock Android Rom but I miss it when a note automatically pops up when the s-pen is removed. And battery life on touchwiz Roms appear to be better. These are choices we're going to have to make.

You hit the nail on the head my friend. I am looking to run stock android jelly bean on my next device.

I had a nexus s for my first android phone and I took it for granted how amazingly easy it was to flash not only roms but radios, kernels, basically anything. And I just love stock android.

I am now on an HTC rezound. While I do like it, I sorely miss stock android and flashing away at will. Already had quite a few flashing mishaps.

If I am forced to run touchwiz to use all these new features, then I'm not going to pay attention to the features when choosing my next device.

This wouldn't even be an issue if the LG nexus was released on Verizon.

Ugh, looks like I'm still waiting.

Rezound, s-off, loving it.
 

zoot1

Senior Member
Jul 17, 2011
2,674
2,458
Navi Mumbai
onurface.blogspot.in
Correct me if I'm wrong, but isn't that entirely part of the launcher and TouchWiz apps rather than the ROM?

Actually it depends on the feature.. Some of the features see baked into the framework apk others have individual apps... None of them are launcher dependent.. However all of these together make a ROM.. So I don't know you are referring to??

Sent from my GT-I9300 using Tapatalk 2

---------- Post added at 05:32 PM ---------- Previous post was at 05:31 PM ----------

Explain?

Sent from my s-off Rezound

He means all the devs will fly in droves to the new flagship device leaving the flagship devices of last year stranded..

Sent from my GT-I9300 using Tapatalk 2
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
Explain?

Sent from my s-off Rezound

Most experienced developers are leaving Samsung for manufacturers that don't treat them like **** (see the Superbrick fiasco), leaving only the "me-too" smali-hack-kangs and a very small number of experienced competent developers like Andrei.

Quality, not quantity - most of the stuff in the I9100 and I9300 forums is crap, people who took a Touchwizz base, themed it, made some build.prop hacks, and called it a whole new firmware package. They're lucky in that Touchwizz is so bad that it's easy to improve upon it.

Compare to, for example, the Xperia T where there are 5-10 or more developers all contributing as a team to something that only has two threads (One for CM10, one for CM10.1) There aren't many people working with Sony stock firmwares because, honestly, it's REALLY hard to improve upon them because they're so good to begin with. Most of the few things that can be improved are achievable with simple TiBu freezes, no smali hacking required.
 

Reviewers

Senior Member
Mar 5, 2011
4,147
1,671
Brooklyn, NY
I think it'll make AOSP (CM/AOKP) hard to develop but there super people! I'm sure they'll figure it out and help!
However Touchwiz ROM's could be pulled and edited! We won't lose any features/it won't be hard.
 

Livebyte

Senior Member
Jul 14, 2012
537
336
I think it'll make AOSP (CM/AOKP) hard to develop but there super people! I'm sure they'll figure it out and help!
However Touchwiz ROM's could be pulled and edited! We won't lose any features/it won't be hard.

Project Butter in Exynos 4210 devices (eg. Note & S2) is still broken until today and will never be solved.
A technically inferior Galaxy Nexus is superior to the Note. Take that for a change.
You have no idea how frustrated and angry are we people targeting Samsung in the Note & S2 forums.
I swore never to buy anymore Exynos devices after this fiasco.
 

browy

Senior Member
Apr 1, 2012
395
206
Zürich
Project Butter in Exynos 4210 devices (eg. Note & S2) is still broken until today and will never be solved.
A technically inferior Galaxy Nexus is superior to the Note. Take that for a change.
You have no idea how frustrated and angry are we people targeting Samsung in the Note & S2 forums.
I swore never to buy anymore Exynos devices after this fiasco.
And the S3 community, count it in. We're fed up with all those broken promises too.
 

tbong777

Senior Member
Do all these new sensors and proprietary software (camera features, gesture features, etc) make it more difficult to develop customs ROMs for the gs4? Or will we just get ROMs that don't use all these new features and sensors

Sent from my aokp_tenderloin using Tapatalk 2

Only for developers that want to wipe Samsung off the phone. Which I don't understand since most of the new hardware features require drivers Samsung rightfully will not release. For the longest time and to this day you could not get the FM radio to work on CM without buying a $10 Spirit radio app.

I'm sure there will be plenty of developers that will develop deoxed custom ROMs and great kernels with tweaks OCing etc. . Omega already to jump in. The only custom ROM's I've ever used were that of STOCK ROM development where features could be enhanced and drivers would not be a problem. CM always seems to have something missing or not working.

Why buy a Samsung device and then wipe it clean of all the great features? Just buy a Nexus 4

That said. I don't mind running an ASOP ROM on my Nexus 7 I will be glad to get rid of when Samsung releases the 6.5" Note 3.

For many a stock base is good enough with a custom launcher. This is a very very small community. I know at least 12 people with an S 3and 6 with Notes. None of them even want their phones rooted.

Sent from my GT-N7100 using xda premium
 
Last edited:

Phoneguy589

Senior Member
May 1, 2011
1,859
332
S.E. Florida
The real question I have is.. If the UK and the US get the quad core processor, Which device would have more developers....Exynos or Snapdragon?

Sent from my SGS3 using xda premium
 

howtomen

Senior Member
Jan 10, 2011
2,019
1,224
Brea CA
The real question I have is.. If the UK and the US get the quad core processor, Which device would have more developers....Exynos or Snapdragon?

Sent from my SGS3 using xda premium

Snapdragon always gets more aosp... So i assume more serious devs that are still in board will get Qualcomm

trolol and awayyy!! Expect typos this is my phone.
 

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada
Do all these new sensors and proprietary software (camera features, gesture features, etc) make it more difficult to develop customs ROMs for the gs4? Or will we just get ROMs that don't use all these new features and sensors

I think GS4 & Note3 development will be pretty similar to GS2, Note, GS3 and Note2.

AFAIK, for example, the AOSP based ROMs don't really support the S-Pen on the Notes, but that's more app specific.

Cameras have long been, and will likely continue to be a problem. Video capture rates may be lower, features like both cameras, sound in pictures, smart scroll may not be supportable.

As always, for stock features, there will be stock based ROMs. Take your choice, features or AOSP based.

As with all the other Galaxy S class devices, there will be two main variants: International Exynos Octa & US/LTE/Qualcomm. ROMs, XDA forum sections and many issues will be different for each.

I predict that many ROM devs will continue to complain about the lack of Exynos info and source code. But they will develop, as best they can. I'd like to see Samsung open up more, Sony and Qualcomm are better at open-ness.

And there will be at least one other group for the Qualcomm variants; I'd hope the US carrier variants will all be able to run the same ROMs, but previous experience is different I guess.


For the longest time and to this day you could not get the FM radio to work on CM without buying a $10 Spirit radio app.

1st post of my thread has links to free versions, as well as free alphas of Spirit2, with digital audio features for Galaxy S class devices.

I hope the proposed Android FM API will see success and provide more options.
 
Last edited:
  • Like
Reactions: Flint2

Phoneguy589

Senior Member
May 1, 2011
1,859
332
S.E. Florida
Snapdragon always gets more aosp... So i assume more serious devs that are still in board will get Qualcomm

trolol and awayyy!! Expect typos this is my phone.

Only reason I ask is that the i9300 get newer software updates vs the 8747 or t999. I was recently dead set on getting the i9500 but now it well be based more on development. The the ir blaster won't work km cm or aosp as it doesn't work on the note 10.1...Only touch wiz. Not really a big deal to me but I was Curtis as th where most devs are from that usually get the international ones. LTE to me means is reach my data cap sooner so hsdpa+ is plenty quick got me.

Sent from my SGS3 using xda premium
 
  • Like
Reactions: mw86

JaZart

Senior Member
Jan 8, 2012
1,037
210
Columbus
Most experienced developers are leaving Samsung for manufacturers that don't treat them like **** (see the Superbrick fiasco), leaving only the "me-too" smali-hack-kangs and a very small number of experienced competent developers like Andrei.

Quality, not quantity - most of the stuff in the I9100 and I9300 forums is crap, people who took a Touchwizz base, themed it, made some build.prop hacks, and called it a whole new firmware package. They're lucky in that Touchwizz is so bad that it's easy to improve upon it.

Compare to, for example, the Xperia T where there are 5-10 or more developers all contributing as a team to something that only has two threads (One for CM10, one for CM10.1) There aren't many people working with Sony stock firmwares because, honestly, it's REALLY hard to improve upon them because they're so good to begin with. Most of the few things that can be improved are achievable with simple TiBu freezes, no smali hacking required.

Yeah, I guess that's just for exynos based galaxy devices. My US S2 Variant has several 4.2.2 aosp roms. Aokp, cm10.1, pac, slim, rootbox etc. I assume the USA s4 will be similar.

Sent from my SGH-T989 using xda app-developers app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 101
    Nobody at team hacksung (the team behind galaxy s2, note, s3, note2, gtabs... official CM ports) plans to buy it, neither develop for it. There are two variants which will be a pain to maintain, the bugs we have on the s3 will probably be there on s4 too (camera), and we all know Samsung ability to release sources while staying in line with mainline. Yes qualcomm release sources, but exynos sources we had were far from actual galaxy products. I'm pretty sure the same will happen for this one.

    That's a uniform "no" from us (hacksung).


    EDIT: Don't get me wrong. There has been a huge flood of messages around the web about the support of CM and the SGS4. What I wrote above is JUST from my/hacksung opinion. CyanogenMod is a big organization with hundreds of contributors around the world. Even if me/codeworkx/entropy/... won't develop for it, other people can go ahead and do it. It's not the CyanogenMod project that decided that 'no' I expressed.


    Sent from my Nexus 4 using xda app-developers app
    31
    Explain?

    Sent from my s-off Rezound

    Most experienced developers are leaving Samsung for manufacturers that don't treat them like **** (see the Superbrick fiasco), leaving only the "me-too" smali-hack-kangs and a very small number of experienced competent developers like Andrei.

    Quality, not quantity - most of the stuff in the I9100 and I9300 forums is crap, people who took a Touchwizz base, themed it, made some build.prop hacks, and called it a whole new firmware package. They're lucky in that Touchwizz is so bad that it's easy to improve upon it.

    Compare to, for example, the Xperia T where there are 5-10 or more developers all contributing as a team to something that only has two threads (One for CM10, one for CM10.1) There aren't many people working with Sony stock firmwares because, honestly, it's REALLY hard to improve upon them because they're so good to begin with. Most of the few things that can be improved are achievable with simple TiBu freezes, no smali hacking required.
    15
    The Exynos Octa is going to be an absolute deal breaker in terms of full AOSP support. The core architecture with it's firmware controlled CPU handover is where the problems will lie. No way are Samsung going to release the relevant documentation given their history and the unique capabilities of this SOC. While AOSP code will ultimately make it onto the device, expect a broken implementation of it.

    Still. I never fully understood the major hate towards Samsung in regards to AOSP ROMs. Never have Samsung advertised the Galaxy S range as AOSP devices or AOSP friendly devices. You are ultimately hacking the device beyond it's advertised capabilities. You should be thankful they don't force you to legally sign away your warranty like HTC/Sony just so you can flash a ROM. I loved my S2, but ultimately missed the AOSP experience I had on my Nexus One and returned to Nexus range in the way of the Galaxy Nexus, a Samsung device, advertised and promoted as an AOSP device.

    Regards.
    They publicized their donation of three devices to the CM team VERY heavily.

    They promised they were "working hard" on Superbrick, and threw a grenade in our faces with XWLPM a month later with no warning.

    They promised to release updated platform reference source for Exynos4 - and regurgitated the same almost-a-year-out-of-date crap (it's now on the order of 1 year 3 months outdated) that was an issue in the first place. Their BABBQ promise was clearly just a stunt to sell more Note2 units.

    They lie on a regular basis... They say they care about the community to sell more devices, but their actions are the exact opposite of their words.

    They update fast because their update is also crap.
    Its poor in quality and buggy at most

    Free SGS2 to CM team was a publicity stunt.
    Yup. The only manufacturer who has donated FEWER devices to CM maintainers than Samsung is HTC and maybe Motorola.

    Jerpelea has more Sony devices than he has the time to support. (For various reasons, Sony asks that these donations don't get publicized too much). Arcee has received every LG device marketed in Europe to my knowledge (again, that's kept semi-quiet, partly because manufacturers don't want users to go out and buy a device then get disappointed if the CM bringup falters for whatever reason.)
    11
    Some of us have lived on Stock Rom development for years and actually prefer it over the always non working this and that on CM and CM based ROMS. The only device I owned/own that benefits from CM is the Nexus. Other than that I prefer EVERYTHING to work and not wait for some nightly and have to flash a new ROM every week.

    Cyanogen had their day. Manufacturers are making them obsolete with the hardware features they don't willingly release driver code for. Why should they? They WANT SAMSUNG stuff on Samsung phones. Stock developers do a great job of giving us a choice of WHICH Samsung apps we want and those of us who use the Pen on the Note like having it work as well.

    We get it. No CM ROM...Buy another brand, Samsung doesn't care, nor should they for the relative handful of their newer devices running CM Roms.

    Let's say it's May. Android 5.0 came by in Google I/O.
    6 months later, you're still on 4.2.2 because Samsung still hasn't updated their phones and sources.
    Okay there might be AOSP-based ROMs a week later.
    But none of them is fully working because the drivers from 4.2.2 is no longer working in 5.0
    You're telling me you won't get mad?
    What if Google came out with some super cool feature.
    Last year was Project Butter & Google Now.
    You're still telling me you won't get mad?
    If you say Samsung don't care, why should we care about them then?
    We're XDA because we develop amazing custom ROMs, not some themed **** with extra apps preloaded together with some build.prop edits
    7
    You guys do realise much of the work and bugfixes by CM are fed back to Samsung for improvement? Without the pool of highly talented developers to tinker with their product, there will be no talent to brainstorm with. Other than meaning Samsung doesn't care about the enthusiasts community, this also means Samsung doesn't care about the common user, because they are reluctant to hang on to the pool of talent they should work the most closely with for when fckups like the Brickbug occurs.
    Actually, we've tried to feed bugfixes back to Samsung for improvement, but they just sit and let things be broken for months on end. This is where a lot of our frustration comes from - we've tried as hard as we can to work WITH Samsung, and they treat their customers like crap. They absolutely refuse to take responsibility for any bug that gets discovered.

    Look at the MAX17042 fuel_alerted wakelock bug - Discovered in October 2011, reported multiple times back to Samsung (and the fix was literally ONE CHARACTER, replacing an == with >= in a comparison), and it didn't get fixed until January 2013.

    Compared to Sony, who have actively worked with developers here in terms of investigating bugs that are found. MANY of the issues we raised with ICS on the Xperia T were solved in Jellybean.

    I got a question.

    Is Steve Kondik a.k.a Cyanogen (founder of CyanogenMod) still working for Samsung?
    If so, I would like to know his toughts about the hate/love relationship of TeamHacksung with Samsung.

    Enviado desde mi GT-N7100 usando Tapatalk 2
    He's working for Samsung USA... He pretty much stays out of it. He's in a very tough position due to working for Samsung... He's stuck between us and the Koreans.

    There are a number of people at Samsung USA that care and want things to change, but upper management in Korea is 100% uncooperative.