yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
I decided to nuke my android_device_samsung_jf-common repo, re-forked from CM, and merged in THIS commit from chenxiaolong, so credit is to him for the jf-common files.

my builds were compiling successfully, but not booting. i have also switched all of my work over to the "omni" branch as well, except for

android_device_samsung_jflteatt

the ATT specific repo, which i still have on the "omnirom" branch. i'll merge it over shortly, depending how much of the massive amount of classwork I have to do tonight. Damn you Drexel University for assigning so much BS all at once!! :crying::crying:
[Galaxy S 4 Developer Discussion [Developers-Only]] CNexus:
Check my post here: http://xdaforums.com/showthread.php?p=46664742
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
[MENTION=4913579]CPA Poke[/MENTION]

[MENTION=4645794]CNexus[/MENTION]

UPDATE
​

http://xdaforums.com/showpost.php?p=46673228&postcount=36​

USE THIS LOCAL_MANIFEST

http://hastebin.com/visoqahiwo​

just fork / add my github to local_manifest. use 'OMNI' branch for ALL except for android_device_samsung_jflteatt, which you should use OMNIROM branch. Profit.

Radio doesnt seem to work, should be a relatively easy fix.

Alright, so i got a booting build with Ktoonsez kernel, and it actually booted properly. i was able to setup my Google account and everything, but it was VERY buggy. texting worked, wifi worked, calling worked, but couldn't hang up the call. not sure what else. its pretty late and i have class in a few hours.

I have added a commit to the android_device_samsung_jf-common in hopes to have it build with the cm init binary for the ramdisk, per CNexus, but i dont know if it will work or not. i have a build set to compile while i sleep, so i can test it in the morning.

Secondly, I manually swapped the init binary in the compiled boot.img from omnirom with one from the latest CM-nightly. I dont know if i did it right or not, but regardless, i was able to split the boot.img, delete the init file from the ramdisk folder, paste the one from the CM boot.img ramdisk folder, repack the ramdisk, and then use the mkbootimg script to repack the boot.img. i unzipped the omni ROM .zip from the build, and repackaged it using 7z in the terminal. it packaged and flashed successfully. but did not boot until i flashed ktoonsez kernel, so either 1 of 2 things happened

1) I didn't swap the init files properly, hence the non-boot

2) that fix won't work for jf devices like it did for d2

depending how much crap i have to do for school tomorrow will determine the amount of time i can spend on this. i have an exam wednesday though so i for sure will be spending a majority of my time studying.
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
I got a booting build for jflteatt... but no radio. About Phone shows Baseband Version UNKNOWN.

any thoughts? i used chenxiaolong's commit to jf-common , and then made this commit to jf-common... to prevent having to swap the init binary to the ramdisk for every build.. http://goo.gl/HAueef

Wifi works, etc. Haven't tested bluetooth. Can't test calling/texting, obviously.

I'm going to put it into Airplane mode, start a logcat, turn off Airplane mode, see what i find ..
[Galaxy S 4 Developer Discussion [Developers-Only]] garwynn:
I have an S4... just can't test on it anymore - unless I want to sleep on the couch.

Flash failed, looking at today.
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
here's a logcat for the Radio..

http://hastebin.com/qukavunuve

if that doesn't work here's a link to the .txt file

radio2.txt

not sure what's up. never done this much "development" before, learning by trial and error. not sure whats causing the radio to fail though. not sure if anyone wants to take a little look at this logcat
[Galaxy S 4 Developer Discussion [Developers-Only]] garwynn:
Are you sure all the vendor blobs got pulled into the ROM?

It almost looks like it's not talking with the hardware correctly.
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
i would assume so,

i added the repository for the samsung vendor blobs to my local_manifest..

got a pretty cool wifi-only cellphone right now ;)
[Galaxy S 4 Developer Discussion [Developers-Only]] upndwn4par:
Nice work jake!
[Galaxy S 4 Developer Discussion [Developers-Only]] CNexus:
You know this is really interesting because RIL is also broken on the d2spr build, even though it boots up fine
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
Once again, I debased device/jflteatt BACK to CM repo. I figure if kernel, jf-common, msm8960-common and qcom-common are based on CM repos jflteatt should be too. Won't affect the manifest I posted, maintained branch name. Based it off utkarshgupta's N7100 bring up by the way. Its much cleaner now. And I added the omni.dependencies file so roomservice.xml will be generated to pull in all required repos except Samsung vendor blobs. I commented out all the lines until a working device tree is merged to omni source.

I'm really not sure what's going on with the RIL.

http://hastebin.com/visotohaqo

here's a new local_manifest for those who are working on jflteatt

should fix data. courtesy [MENTION=4645794]CNexus[/MENTION] and [MENTION=4932679]decimalman[/MENTION]

Thinking about it, to a certain extent, shouldn't we merge in a majority of, of not all of, the commits CM has for SamsungQualcommRIL in frameworks/opt/telephony? I havent looked at them all yet but im assing they would only increase performance/fix any outstanding bugs
[Galaxy S 4 Developer Discussion [Developers-Only]] garwynn:
I'm dumping my omni folder and will restart based on jake's progress. Seems to be the common direction and better for us to work together on this as much as possible.
[Galaxy S 4 Developer Discussion [Developers-Only]] CPA Poke:
Great idea. [MENTION=3878813]jakew02[/MENTION], did you go ahead and post the updated trees in the Omni thread? Might be a good place for other jf devs to find, in case they didn't see this thread.

Thanks, all, for your participation with this. I've learned a TON more than I would have participating in "the zoo" just by watching your guys' discussion. All hail [MENTION=3878813]jakew02[/MENTION]!! :cool:
[Galaxy S 4 Developer Discussion [Developers-Only]] garwynn:
Jake,

One thing I noticed when I set up based on yours - where's the copy for apns-conf.xml?
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
[MENTION=4194834]garwynn[/MENTION] , i noticed that. it's added in now. as well as gsm.mk in vendor/omni in their rightful places.

also, i got some help from some of the respected devs on IRC and i have a build compiling right now with frameworks_base frameworks_opt_telephony fixes and packages_apps_Phone, so i'm going to bed and it'll be done when i wake up . If RIL works and I can get signal, I'll post the device trees to the OmniROM device bringup thread as well as in the AT&T GS4 thread , once i clear it with the omnirom guys.

oh ya, i got a little frustrated/flustered doing this and uh, my github is a freaking mess. so needless to say it'lll be down at some point tomorrow, i'm going to backup all my files, nuke the account, and start over fresh, so it's organized and pleasant to look at. it'll still be jakew02 and the branch will still be omni. :highfive:
[Galaxy S 4 Developer Discussion [Developers-Only]] fkosa:
Hi Guys!

I am interrested in porting omni to S4 Active (i9295) based on S4 (i9505) repo. I succesfully built CM10.2 based on some other ports, maybe useful in porting omni. Any help is appreciated.

Thx
[Galaxy S 4 Developer Discussion [Developers-Only]] garwynn:
Were you going to push the changes back up and then we can work on it from there - or should I start resolving the missing objects on my own?

Know we're all busy so I can start on it again but would rather not if it's just doing the same thing you've already done.

Thanks again for all of your help!
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
I'm using this github as my "final" product. the jakew02 github will be my "experimental" one, and i'll be pushing finalized/verified working commits to omni-jf . hopefully we can make the omni-jf github an account that wil provide support for ALL jf variants, so send me pull requests to there!

https://github.com/omni-jf

Ive been working with SferaDev and we/he made some pretty good progress on getting SamsungQualcommRIL support added in to Omni. checkout fw/base and fw/opt/telephony commits on OMNI branch @ https://www.github.com/omni-jf

I tried fixing the ramdisk issue by manually merging a commit from decimalman, but it brought up Status 7 errors when flashing (atleast I THINK thats what caused the status 7 errors)

the only ramdisk changes on the omni-jf github , is that i pulled the init binary a CM nightly, and uploaded it to the github , and added it as a prebuilt in the Android.mk file for jf-common, you can see the commit
[Galaxy S 4 Developer Discussion [Developers-Only]] CNexus:
Status 6 / 7 are updater script errors
[Galaxy S 4 Developer Discussion [Developers-Only]] garwynn:
And that's good news because we should be able to see the error at that point!
[Galaxy S 4 Developer Discussion [Developers-Only]] garwynn:
He's an awesome guy to help with that stuff. I'm hoping to learn a lot by picking up the Nexus 5 and hoping to contribute to AOSPA when it and 4.4 come out. I'll change out to those repos this weekend, try another build and beg/plead to see if I can "borrow" the S4 for a bit of testing.
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
yea, for trying to flash a ZIP intended for a device that you're apparently not flashing on. i hadnt received this error yet, so i revert my CM init binary changes to system_core and just went back to my hacky way of implementing the cm init into jf-common, we'll see.

im getting port errors compiling with my build server so i gotta start a fresh one locally. setbacks.. :mad:
[Galaxy S 4 Developer Discussion [Developers-Only]] garwynn:
You can do more than identify assert errors. It's how I used to tweak ota zips before Chameleon changed the CSC integration.
[Galaxy S 4 Developer Discussion [Developers-Only]] garwynn:
Well... I think using the telephony and RIL resources for Omni - at least as they stand now - are a bust for me.

From the looks of it the CDMA RIL changes are not working in those repos.

Can't get it to build so I'm going to try using similar build setup for getting PA to build.

I should be ready to try again tonight and see what happens.
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
RIL is fixed.. Now to tackle the init issue..
[Galaxy S 4 Developer Discussion [Developers-Only]] garwynn:
Ok, finally got a build. Had to switch out two files in packages/apps/Phone but it finally built.

I'll get some testing done on it and let you know. Worst case I suspect it may need to use KT's kernel for the time being.
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
[MENTION=4194834]garwynn[/MENTION] Almost forgot!

There's quite a bit of commits for system/core that I'm pretty sure decimalman squashed into one HERE , just git remote add <remotename> then git fetch <remotename> then you'll be able to cherry-pick it into system/core..

I NEEDED this to get jflteatt to boot without a custom kernel. since we're the same device family i'd assume jfltespr would need it as well, but i could be wrong..
[Galaxy S 4 Developer Discussion [Developers-Only]] garwynn:
Well, good news - kernel included in build booted without issue. Bad news - no voice/data.
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
that's weird... the only device tree that we don't share is jflteatt and jfltespr ... everything else is identitcal... so why would jfltespr boot w/o that system/core commit.. but att variant wont? odd..

the voice/data is definitely a RIL issue.. samsungexynos3 RIL is still broken as well according to SferaDev..

hm.. where is your repo for jfltespr ? i want to compare to jflteatt.. because i must have borked something if i can't boot w/o the system/core commit and jfltespr can..

also, there's a few commits you'll need to cherry-pick if using CyanogenMod/frameworks/opt/telephony on omni's gerrit.. i'll grab the links for you in a sec
[Galaxy S 4 Developer Discussion [Developers-Only]] garwynn:
I'll stick it up on Github as soon as I can - the whole set (jfltespr, jf-common; msm8960-common and qcom-common were untouched from cm-10.2)
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
awesome, thanks!

Yea, i didn't touch:

- hardware/samsung from cm-10.2

- qcom-common from cm-10.2

I edited msm8960-common to make galaxyS3settings say galaxyS4settings, pet peeve :o

i edited jf-common from cm-10.2 for the following reasons:

- make OmniTorch work

- remove overlays for Trebuchet and Focal

- add overlays for Volume Wake option

i had to revert this commit from the kernel:

https://github.com/omni-jf/android_kernel_samsung_jf/commit/60be26252ab3de23b85f34b5faf3b489ed2a3e6f
[Galaxy S 4 Developer Discussion [Developers-Only]] hisname:
hi guys, I attempted to build omni just now and I met with a error. what could it be?

http://pastebin.com/kp7yYF1A

it has got to do with this

doing a little Google-ling shows that my naming convention is wrong. but I had ensure that all my names are jfltexx and ensured that paths are correct
[Galaxy S 4 Developer Discussion [Developers-Only]] CNexus:
It means you're missing the android_device_samsung_qcom-common repo

Just add this to your local manifest

<project path="device/samsung/qcom-common" name="omnirom/android_device_samsung_qcom-common" revision="android-4.4" remote="github />
[Galaxy S 4 Developer Discussion [Developers-Only]] garwynn:
Okay... I'm in the process of re-syncing for a new build but having issues. I'll be trying another build when resolved.
[Galaxy S 4 Developer Discussion [Developers-Only]] hisname:
anyone able to help me with this error?

http://pastebin.com/0mfAN41Q

I went to #omni on free node and asked for help. [MENTION=3544509]eagleeyetom[/MENTION] tried to help, but.... well, he couldn't...
[Galaxy S 4 Developer Discussion [Developers-Only]] garwynn:
What device repo are you using?
[Galaxy S 4 Developer Discussion [Developers-Only]] hisname:
well, I am using everything in the omni repo. From the core right to the kernel. to add on, there were some missing code in the repo, the rom refuse to build, so I added them. but I don't remember what is missing as I am not at home right now. I will post it here later.
[Galaxy S 4 Developer Discussion [Developers-Only]] Laggalot:
a quick question! : how far are we already with OMNI ? is it still a long way to go? ...? man our phone doesnt even have 4.4... the sgs3 has it already so i dont really get it -.-

sent from my i9505 or nexus 7(2013)
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
anyone that has made a booting build for omnirom 4.4 please let me know.. i can get builds to complete but not pass the boot logo... and i don't have adb to look into what the cause is..

my 4.3 builds are solid though! :good:
[Galaxy S 4 Developer Discussion [Developers-Only]] CPA Poke:
I think it's a ramdisk issue...maybe try using Albinoman's kernel source (Team-Hydra).
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
yea, it's the same issue i had on the 4.3 build initially, that was fixed with a few init commits to system/core ,, so i think i need to go thru and cherry=pick all the commits from the 4.3 system/core to 4.4 and see what happens..

because obviously there are commits from 4.3 that were merged prior to my start of a bringup,, so i never had to worry about finding them.. but now i need to find the commits on 4.3 that were already there that aren't on 4.4

---------- Post added at 02:00 PM ---------- Previous post was at 01:58 PM ----------

make sure you have all the dependencies in omni.dependencies, do a make clobber,, repo sync.. source build/envsetup.sh .. then breakfast jfltexx

you can just use this omni.dependencies file here: https://github.com/jakew02/android_device_samsung_jflteatt/blob/android-4.3/omni.dependencies

its the same for ALL jf devices
[Galaxy S 4 Developer Discussion [Developers-Only]] hisname:
i would also like to point out that /device/samsung/jf-common/BoardConfigCommon.mk is not complete.it is because i had to manually add this.

TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_CPU_VARIANT := krait
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
i never ran into any issues with NOT having those lines in BoardCommonConfig.mk on 4.3 omni builds...

push it to gerrit please

https://gerrit.omnirom.org

:highfive:
[Galaxy S 4 Developer Discussion [Developers-Only]] hisname:
ME??!!i know nothing,i just started learning such things few days ago,so a noob question,how do i do it?

edit:the BoardCommonConfig.mk is taken from CM repo,but CM managed to build it,but i could not.something is strange here
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
dude i don't see that code on CyanogenMod's BoardCommonConfig.mk for jf-common on 10.2 or 11.0 branches...
[Galaxy S 4 Developer Discussion [Developers-Only]] hisname:
that is why i said that it is strange.

i captured the log down.here it is.http://pastebin.com/0mfAN41Q

it is the one that you authored.https://github.com/omnirom/android_device_samsung_msm8960-common/

looking at the githuub code,i noticed you already had this.

TARGET_CPU_VARIANT := krait

edit: oh god,i am confused too.i have been debugging the whole day...
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
jfltexx

jflteatt

jfltecan

all working now for 4.4

just sync the repo and cherry-pick the following commits:

https://gerrit.omnirom.org/#/c/2357/

and you will get a fully functional and working build.

I need testers for jfltevzw jfltetmo and jfltespr please

If you are interested please send me a PM letting me know which device, that way I can keep track and send links once I get builds.
[Galaxy S 4 Developer Discussion [Developers-Only]] hisname:
yes, thank you. I saw the commits this morning. [MENTION=4189659]Tectas[/MENTION] was helping me out and showed me the link. The link Tectas showed me is this over here . so, is this included?
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
yup, the general fix/cleanup commit has been merged, so it will be applied the next time you do a repo sync.

the other commit that i posted (the disable some overlays one) is required to be cherry-picked. I asked them to NOT merge it in, since the 2 things that it disables will be getting added back in to the frameworks soon, so it's pointless to merge this, and then just have to revert it in a few days when it can just be cherry-picked by users.

so just cherry pick that one commit about disabling overlays and you'll be good to go :good:
[Galaxy S 4 Developer Discussion [Developers-Only]] Pump Ac7i0n:
willing to test for sprint
[Galaxy S 4 Developer Discussion [Developers-Only]] hisname:
hi there, its been a long time. I finally managed to compile omni, but it seems that I can't get it booting for 4.4 branch. the kernel was not even booting at all. using Philz and TWRP, there is this error saying something about error formating mmcblk027 after wiping omni rom ,a little seaching lead me to a thread saying that this is a hidden partition. I'm asking is this some kind of ramdisk issue and anyone got it booting?
[Galaxy S 4 Developer Discussion [Developers-Only]] Gandalf:
yea we've had everything booting and working fine on 4.3 and 4.4 for a while now, just working out minor details like camera, etc.
[Galaxy S 4 Developer Discussion [Developers-Only]] benjiboythelad:
Hey so dose omni ROM have it support. Otherwise theirs one bit off useless hardware . ano its a nightly but still. Plus can we use the flash bar apk i prefure that to the halo I mean at the moment omni ROM is just a faster cm. Cause with nightleys theirs no halo or any features is their I mean it works perfectly but theirs no extra.
[Galaxy S 4 Developer Discussion [Developers-Only]] CPA Poke:
Not too sure what you just said, but I'm fairly certain this is not the thread (or forum) for you.
[Android General] vinz89:
Hi This thread is for the New James Bond, Spice Pinnacle Pro, MI 535 Device.​

I have am consolidating all things related to spice mi 535 or Spice Pinnacle Pro into a single thread. There is lot of things going on but all scattered. I am trying to consolidate that. Credit does go to relevant users....

Whatever you do is at your own risk. Altough I try to provide tested and better content, sometime things may get wrong. So try at your own Risk. Post if you face a problem or doubt :angel:​

Device Highlights

Dual SIM Support

5.3 Inch QHD IPS Display

1.2 GHz Quad Core Processor

1 GB RAM

16GB On Board Storage

Micro SD Slot

32GB Micro SD Support

8 MP Camera With Dual LED

5MP Front Facing Camera

2550 MAh Battery

Drivers

Details Here for both 32 bit and 64 bit

ROOT

Rooting the device is fairly Easy 3 Step Process. It is based on the MOTOCHOPPER Utility.

1. Download Motochopper by clicking here

2. Enable USB Debugging in Settings - > Developer

3. run "run.bat" in the archive and follow on Screen Instruction (Press Enter when asked)

UnRoot

UnRooting is required if you are taking phone to service center or for any other reason. Its more simpler then rooting.

1. Goto SuperUser -> Setings -> Full Unroot

2. No Second Step. You are UN-Rooted...

CWM Recovery

Download Cwm_Recovery

Download Scatter File for Smart Phone Flash Tools

Download Flashable Cwm Recovery

Touch Based CWM Recovery Download & Instructions

Approach 1 (for rooted)

1. Copy cwm_recovery.img from above link in sdCard.

2. Install MobileUncle Tools from Play Store.

3. In MobileUncle, Select Update Recovery, Select the cwm_recovery.img and done.

Approach 2 (for non-rooted)

1. Run Smart Phone Flash Tools (SPFT)

2. Select Scatter File

3, UNCHECK all, Check Recovery

4. Select cwm_recovery.img

5. Download

For any help, post reply below

Approach 3 (flashable : NOT TESTED: Someone please confirm)

1. Download Flashable cwm recovery and put in sd Card

2. Start in recovery

3. Select the package

4. Restart

Stock ROM

To Be updated Soon, uploading single file

Custom ROMs for Spice Pinnacle Pro

Stock Based SPICEMOD_V1.0 for SPICE MI 535

Pandora ROM v2 (some efforts needed)

AROMA Based 4.2.2 Butterfly

MIUI ROM

Canvas 4 Ported ROM

Mahmood's~535™HDBeataV1.0

Other Articles

Unbricking Dead Device

Facebook Group

Credits: [MENTION=4694659]luminousin[/MENTION], Ansuman Mahapatra, vinz89
[Android General] vinz89:
RESERVED

If I missed any names, for credit, please post in reply. Also post any other relevant information that can be included in first post.

The other issues / discussions can be run along..
[Android General] vinz89:
Review

The handset even with the stock is MORE THEN SUFFICIENT you can expect in upto 20k phone.

The vitals are better then Samsung Grand

Battery is most awesome

All Games go in super swift and cool

GPS is best then any of 6 MTK phones I have used, Locks in 3-7 Seconds in major roads (even in balcony with one side open)

Navigation works too cool.

Camera is awesome in sunlight

Try MapMyIndia Sygic for offline navigation which is super simple...

COULD NOT find 1 issue in it.... Best handset for upto 21-25 k range....

10/10 for this lovely phone
[Android General] helloansuman:
Good work Bro...
[Android General] vinz89:
Official BBM Working Fine

Finally [MENTION=1168641]bbm[/MENTION] for Android..

Click https://play.google.com/store/apps/details?id=com.bbm to download now...

Tested.. Working OK
[Android General] Preshak:
Latest custom rom???