yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] sparksco:
4.3 update.

Looks like cm did the merge thing this time... PA hasn't merged for halo yet. Maybe I'll try and add it back once they do. For now I'll leave it out and try to merge the rest.
[Nexus 4 Original Android Development] MBQ_:
Just waiting for someone to ask if they can dirty flash over it from 4.2.2 hahahahaha
[Nexus 4 Original Android Development] DonJuan89:
*troll mode on* can we? :)
[Nexus 4 Original Android Development] MBQ_:
Oh. Yeah. Totally.

Heard if you flash Android 4.3 over 4.2.2 without flashing, Kate Upton shows up at your house.
[Nexus 4 Original Android Development] DonJuan89:
You sir just made my day. Anyway, looking forward to having the saber-toothed squirrel on the N4 again. Much appreciated.
[Nexus 4 Original Android Development] MBQ_:
Heh.

Me too. Except I don't have a mako. (Crap)

Luckily they bless us with this sweet ROM on the Grouper. (N7)
[Nexus 4 Original Android Development] sparksco:
First stage done...

https://github.com/SaberMod/android_frameworks_base/commit/271c05b46bfb339d2ee3d7033f1a5a0513c6c644

Looks like quick unlock and/or lock screen pattern might be broken and probably will be removed.

Cc: [MENTION=4617326]jarjar124[/MENTION] [MENTION=4429892]Martin_Ro[/MENTION] [MENTION=4711514]rustyjay[/MENTION]
[Nexus 4 Original Android Development] Martin_Ro:
Currently I'm fighting with problems regarding the blobs.... But thanks for the info :)

Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] myzar:
But the source is still not supposed to compile ? i've tried out of boredom

build/core/dumpvar.mk:94: *** "endif" non pertinente. Arresto.

** Don't have a product spec for: 'sm_mako'

** Do you have the right repo manifest?

HEAD ora si trova a 92f280d Merge tag 'android-4.3_r2.1' of https://android.googlesource.com/device/lge/mako into sm-jb-mr2

HEAD ora si trova a 91f8984 mako: prebuilt kernel

Finished!
[Nexus 4 Original Android Development] sparksco:
I haven't tried yet...
[Nexus 4 Original Android Development] benrees21:
OK a fresh flash and I'm back in business! Only installed apps that are a must, just to make sure it don't happen again!
[Nexus 4 Original Android Development] strapped365:
Holy ****....396k additions and 5.3 million deletions and 3600 file changes is a ton of work. And I'm sure its not even close to being done.

I just gained a whole new level of respect for source maintainers and source developers such as yourself.

Sent from my NeXus⁴
[Nexus 4 Original Android Development] sparksco:
Running first build now :) (fingers crossed)
[Nexus 4 Original Android Development] eep2378:
Need testers :)
[Nexus 4 Original Android Development] derekr44:
/raisehand
[Nexus 4 Original Android Development] jyuuken:
Raises hands too!
[Nexus 4 Original Android Development] machoua:
I want to volunteer also but I'm a noob and probably won't know what to do when it have problems.
[Nexus 4 Original Android Development] ngoralph:
ready to become a tester :)
[Nexus 4 Original Android Development] resynx:
Testing?

:cyclops::D:p Keep up the good work sparks! Everyone is patiently waiting :)
[Nexus 4 Original Android Development] AgentCherryColla:
Im also willing to test any builds . I knows the LogKitties.
[Nexus 4 Original Android Development] Martin_Ro:
Ok, after I finally managed to build an aosp 4.3 (no spare time till now :crying:) I currently have a build running with the mentioned changes from [MENTION=2394329]sparksco[/MENTION] .

If it works, I can publish an vanilla aosp 4.3 with only Extended Powermenu (Reboot etc.), Busybox and some other small optimizations (removed some old stuff that you also could get via playstore thanx to [MENTION=4617326]jarjar124[/MENTION] for his repo, saved me some time to collect stuff).

Sadly koush hasn't release a working su for 4.3 so we still need to use chainfires solution. Will reimplement koush solution as soon as it's working again because I like the embedded solution way more :good:
[Nexus 4 Original Android Development] eep2378:
https://plus.google.com/110558071969009568835/posts/4RRRUedDssF

Looks like Koush merged it to 4.3, maybe its not finished?
[Nexus 4 Original Android Development] strapped365:
See, for me the kush way makes zero sense. I shouldn't have to constantly hit back to exit the su app after something requests su. Its simply asking yes or no, so why load all the way into the app, and not just a popup like SuperSU?

Sent from my NeXus⁴
[Nexus 4 Original Android Development] sparksco:
I need to get a working build first. Looks like system core is breaking the builds. Most likely I'll just ditch superuser and go back to using supersu again. I agree with strapped, it's kind of buggy the way superuser behaves.

Running the test builds now trying to get this thing to build :) [MENTION=3799866]strapped365[/MENTION]
[Nexus 4 Original Android Development] strapped365:
Yeah I haven't seen my laptop since I synced googles source and then decided to make for mako before extracting binarys.....see what happens when you smoke and try something new.....the system.img and everything is still in my our dir.

I'm sure since nothing was extracted it would be pointless to flash.

But the ****tiest part about all this, is I'm stuck on 4.3.3.

I had flashed the Bootloader and Radio from the factory images and then decided 4.3.3 wasn't for me, so o restored SaberMOD but my GPS was broken and being a driver I needed it. So now I have to make a special trip home just to grab my laptop to get back in working order for SaberMOD 4.2.2.
[Nexus 4 Original Android Development] benrees21:
I always prefer SuperSU. For me, including the Koush superuser in the ROM is annoying. It should be up to the individual to decide what Superuser app they wish to use.

EDIT: Not saying you're wrong for including it, I just personally hate it.
[Nexus 4 Original Android Development] sparksco:
I'm on stock also. I'll probably be on it til I start flashing sm 1.2

I managed to fix system core it looks like and pushed the source to github, but the new bionic keeps failing with the 4.9 toolchain :mad:

So I'm building a new android toolchain based on gcc 4.8.2 for now to see if that'll work or not.
[Nexus 4 Original Android Development] strapped365:
Hopefully its just the toolchain man. I'm very excited for 4.3 BUT its in no way shape or form anywhere close to SM.

All the options and smoothness just makes it that much more rewarding.
[Nexus 4 Original Android Development] RiThBo:
In official CM, Koush's superuser is perfect, you don't have to press the back button to exit. What you describe is a bug in SaberMod...
[Nexus 4 Original Android Development] sparksco:
It's not a bug in SM... SM uses the open source superuser from koudh's github. CM uses their own version that works with their Roms. It's a bug in SU...
[Nexus 4 Original Android Development] chappy824:
Did you run into the smux_debug errors while compiling kernel with linaro toolchain? If so...any fix?
[Nexus 4 Original Android Development] sparksco:
No. I do t use linaro toolchain...
[Nexus 4 Original Android Development] RiThBo:
Sorry - I didnt realise CM used a different version.
[Nexus 4 Original Android Development] Martin_Ro:
Did it bug out while compiling or did it fail in Boot because it compiled fine with the two commits you mentioned earlier. Haven't have time to download it from buildserver to test....

Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] sparksco:
It craps on on cm bionic. Is that what your using? I'm going to try AOSP bionic now.

Edit: Doesn't work on AOSP bionic. Not sure what's going on :(
[Nexus 4 Original Android Development] Lownita:
Couldn't you just flash old bootloader and radio .zips?

Just tested it, I can get a GPS fix with last sm nightly and 4.3 bootloader and radio. What exactly is the problem for you?

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] Martin_Ro:
Hm, I basicly have build a 100% aosp, only implemented busybox, extended powermenu and your 2 commits for 4.9 toolchain.

Build just fine, and also booted without issues.

The only remaining "bug" I currently can see (beside the lag of build in su) is a warnung "No file context" while installing the rom.

Also I have to check if it's really build with 4.9, so maybe this is the reason while it's building for me and not for you :silly:

But as the size change (10 MB less) I think it's an different toolchain then my fist build...

Edit:

Ok, that's why it build for me and not for you maybe...

Seems as if the two commits are not enough because mine still was compiled with 4.7 :(
[Nexus 4 Original Android Development] sparksco:
Hmm. That is strange mine builds with custom toolchain everytime. I decided to merge the build repo this time. I think I fixed bionic. I will know soon.

Edit: this should fix it but I'll have to build a new 4.8.2 toolchain...

https://github.com/SaberMod/toolchain_build/commit/3d280ef5e7e1cd290a9d260c5cce87040a540642
[Nexus 4 Original Android Development] derekr44:
Just fyi, that "no file_context" message happens in cwm all over the place, so I don't think it has to do with the Rom.
[Nexus 4 Original Android Development] strapped365:
I could flash them zips, but to be on the safe side of things I only use bootloaders and radios I personally extract from the stock images. So flashing isn't an option for me.

Also I could get a lock within the Google maps app, so it wasn't exactly GPS. But the second I turned on Navigation it would lose me and show me in the middle of the projects. That's where I work is in the hood, so not the best place for turn by turn navigation to be broken.

In no way was it a complaint though, more like a compliment to the awesome work sparksco does. If I'm willing to make a special stop out of my way (even though its home) to prepare for SM...that's something! I've never ran home for any other android reason lol
[Nexus 4 Original Android Development] Martin_Ro:
I tried to add the GCC config variable now to the Android.Mk of Android_build (i currently build with aosp vendor aosp_mako-userdebug) but still it seems to compile with 4.7 instead of 4.9 :(

Gesendet von meinem AOSP on Mako mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] sparksco:
Yeah I'll have to do more testing. BTW I fixed that annoying bionic error. There's also other bionic fixes on githib now.

https://github.com/SaberMod/android_bionic/commit/cb273d6a4e480d2300a596f6f3bcfe9371c4a18b
[Nexus 4 Original Android Development] cowst:
How does the bug look like?

I am on saber and I think I get the prompt to allow, push continue and it goes back to the app.

Am I mistaken or it could really be a dirty flash over cm?
[Nexus 4 Original Android Development] sparksco:
It only happens with certain apps as far as I know. Don't know what causes it.
[Nexus 4 Original Android Development] reicute789:
may i ask what build yiu guys use as base. im just curious since i read this.

http://xdaforums.com/showthread.php?p=44052881
[Nexus 4 Original Android Development] sparksco:
You guys? I'm the only one working on anything for this ROM... Its based on AOSP.
[Nexus 4 Original Android Development] reicute789:
errr. sorry. i thought rusty and martin are building from source too. nice to know. thanks2
[Nexus 4 Original Android Development] sparksco:
I'm the only one working on sm and the whole gcc 4.9. Martin has his own ROM. And rusty just builds whatever. I'm getting close to a full finished ROM build though :)
[Nexus 4 Original Android Development] reicute789:
great news since im back to saber from 4.3. i'd be willing to test. :D

edit: does your 4.3 build include 4.3 sts too?
[Nexus 4 Original Android Development] sparksco:
No sts :(

I couldn't merge the new kernel I to the old one. I'll have to rebase everything because they changed the prima drivers. So for now its stock.
[Nexus 4 Original Android Development] reicute789:
no problem man. im still willing to test sm 4.3. sts is the dessert that will come after the main course. :D
[Nexus 4 Original Android Development] Martin_Ro:
Yepp, right, there is only one brillant Mind behind sm :) I'm only a visitor too, like all the other here. I only pick some cherries [MENTION=2394329]sparksco[/MENTION] is willing to share :)

Gesendet von meinem AOSP on Mako mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] -viper-:
take your time sparks....
[Nexus 4 Original Android Development] AgentCherryColla:
I've tried ever single (popular) Rom on this forum. But I CAN NOT find one that can match the speeds, and stability of this one. Some ROMs seem stable, but all of sudden you get system ui crashes from conflicting mods. R.A.L (Random Ass Lag). I don't how you do it, or what this mythical beast known as "cm_bionic" is. But keep it up. You guys rock with your socks off non stop.

®∅@®
[Nexus 4 Original Android Development] jyuuken:
If thats the case then. all hail sparksco!!! :)
[Nexus 4 Original Android Development] Martin_Ro:
Grmpfgrml...

Now, that I'm near to finish first version of my new rom, the f*cking hoster of my buildserver has some bl**dy problems with their server...

Hope they will fix it real soon, so I could test koush new su version (yes, I still prefere koush's solution :p) and hope that using [MENTION=2394329]sparksco[/MENTION]'s build repo will fix my problem with building 4.9er toolchain version...
[Nexus 4 Original Android Development] dumber89:
Frankly, I kept using this ROM quite long, about a month, and after several days trying Purity ROM, I really miss this. Take your time, Sparksco, we believe in your modded 4.3 :good:
[Nexus 4 Original Android Development] Ishtakh:
Had the same bug, seems to be Trinity-related, ROM works just fine with default kernel but loses connectivity as soon as I flash Trinity
[Nexus 4 Original Android Development] carepack:
This is the best n4 rom out there. Take your time to build a equal 4.3 rom. Thanks for your rom!
[Nexus 4 Original Android Development] shadymouse:
Definitely agree. There isn't a ROM that matches the consistency and speed of this SaberMod ROM. I will only update if you do. I would be open to testing 4.3 as well

Sent from the KiNG Nexus - - XDA Premium
[Nexus 4 Original Android Development] sparksco:
The first ROM is almost finished :)

Should be done today. Then after that little minor thing's probably.
[Nexus 4 Original Android Development] eep2378:
Nice! [MENTION=2394329]sparksco[/MENTION] you considering the new nexus 7? I just picked one up. Would love to have saber on it. I know you have a OG N7. I might look into porting it to the new one. Still waiting on binaries to drop.

Sent from my Nexus 4
[Nexus 4 Original Android Development] jyuuken:
Take ur time! We appreciate it! :)
[Nexus 4 Original Android Development] machoua:
I haven't been around for a huge update like this. When we update to 4.3 is it just going to be like any new update? Or some extra flashing needs to be done?
[Nexus 4 Original Android Development] derekr44:
I get the feeling that I'm not going to be getting much work done today...
[Nexus 4 Original Android Development] strapped365:
And I'm getting the feeling that someone's going to crush their hosting server once SM makes its 4.3.3 debut lol
[Nexus 4 Original Android Development] kptnk:
Hum, I have the feeling that I'll be disturb by a Flash while watching my movie tonight...:D
[Nexus 4 Original Android Development] sparksco:
Yeah sorry I haven't published the full source yet. Once I get a working build up and running I'll go through my sources and make sure github is update. Just want to get something out first :)

I'm hoping for today but not for sure.
[Nexus 4 Original Android Development] ScumDroid:
You can flash the new 4.3 radio and bootloader if you want, but its not a necessity afaik. Definitely do a clean install for 4.3.
[Nexus 4 Original Android Development] benrees21:
You watch me get away with a dirty flash! :P
[Nexus 4 Original Android Development] sparksco:
Dirty flash from previous SM ROM should be fine. I plan on it.

Looks like there's more building errors in frameworks/base than I initially thought... I'll have to look into it more when I get home later.
[Nexus 4 Original Android Development] benrees21:
Ahhh man the wait is killing me!!! Massive respect for the work you're putting into it! Oh well, it's ready when it's ready. Might not be a bad thing, I still will have to wait on my chosen kernel to update as well.
[Nexus 4 Original Android Development] ScumDroid:
Didn't you run into issues a week or so before that required a clean flash to sort? Or was that someone else?
[Nexus 4 Original Android Development] benrees21:
Yea, some app had obviously auto updated and was causing a System UI crash, over and over. I have clean flashed and only install my must have apps to make sure it don't happen again. I can't think for the life of me what app it could of been. I should be OK to dirty flash 4.3 SM, I have loads of experience dirty flashing! I was doing it before it was even known as a dirty flash! My biggest achievement was dirty flashing MIUI on top of CM7! And I got it to run perfect Lol. Anyway too much OT. Can't wait for 4.3 SM!!!
[Nexus 4 Original Android Development] sykomaniac:
How's things going sparksco

Sent from my Galaxy Nexus
[Nexus 4 Original Android Development] sparksco:
Meh. I had a setback with the merge conflicts in frameworks/base and settings. So for now I'll start with fresh repos for those. I pushed all the source and it should be buildable by tomorrow. There won't be many features to start. I'll add more things over time hopefully :thumbup:
[Nexus 4 Original Android Development] Martin_Ro:
Jepp, even to build frameworks/base with GCC 4.9 is a fight as the existing merges for the alias errors create conflicts. Therefore I even need to Start with GCC 4.7.

Btw.. Using your build repo brings the 4.9 to work, so there Seem to be more commits needed than the two you mentioned. Only fyi if you plan to make a "how to make it 4.9"guide (that I think would bring you hundreds of thanks).

Anyway take your time. I have had some looks into your git and you're really hard working on that :)

Gesendet von meinem AOSP on Mako mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] sparksco:
I also had to fight with other Rom errors for gcc 4.9. Bionic and frameworks/rs. You can find all the new strict-aliasing patches on github. That's what I've been doing.
[Nexus 4 Original Android Development] Martin_Ro:
Thanx for the info.

I looked into your git. In your vendor_SM I see two things:

You removed the Target_GCC_Version, so you will build with 4.7 ?

And your Product Name override indicates your using JWR66V instead of JSS15J, but your BUILD repo indicates that you're using JSS15J... So maybe there's something wrong ?
[Nexus 4 Original Android Development] sparksco:
I don't know about the gcc right now. Default is 4.6. I don't think that way was working before trying to get the 4.9 to get used. Maybe I'll ask jbq how to use TARGET_GCC_VERSION variable. Any ideas?
[Nexus 4 Original Android Development] Martin_Ro:
Hm, sorry, no, as I didn't get it working till I used your BUILD repo, I don't think so.

But I'm confused because while I have tried to get 4.9 working I saw 4.7 as toolchain in my build :confused:

So maybe it uses the variable but don't know about 4.9 and therefore used 4.7 as fallback ?
[Nexus 4 Original Android Development] Ishtakh:
Does anyone have the last build working with Trinity TF152 ?

The ROM runs just fine with default kernel, but if I flash latest Trinity, I lose all radio (no more wifi or 3G)
[Nexus 4 Original Android Development] alen1901:
I think 4.7 is default google toolchain in Jelly Bean 4.3, someone mentioned that.

Sent from Pure Nexus 4
[Nexus 4 Original Android Development] benrees21:
Sorry if this is a bit cheeky to ask but will Navbar DPI and Status bar settings still be available on the first new build? I hate the stock navbar, it's far too big! I know your really busy with 4.3 so I apologize for asking but just want to know what's going to be missing. Keep up the good work! :)
[Nexus 4 Original Android Development] sparksco:
Last time I checked it said 4.6...
[Nexus 4 Original Android Development] alen1901:
Hmm, maybe googles kernel is made with 4.7? If not, some dev doesnt know what he is talking then. :D

Sent from Pure Nexus 4
[Nexus 4 Original Android Development] Martin_Ro:
Ok, I don't know what's default but:

busybox strings surfaceflinger | grep -i gcc

gives me:

GCC: (GNU) 4.7

on my SiMaRom (4.3 JSS15J)

and I use the default Build Repo that comes with aosp (look @ https://github.com/SiMaRom)...
[Nexus 4 Original Android Development] sparksco:
Hmm, looks like I missed this change so your right 4.7 it is.

https://github.com/SaberMod/android_build/commit/5011dd80ee4aff6254bd5600429b3ced1e52f792

It still doesn't explain why when I set TARGET_GCC_VERSION to 4.9 it still uses 4.7.. I think this new feature of AOSP is not working.
[Nexus 4 Original Android Development] sparksco:
OK so it looks like I'm having much better luck starting fresh on frameworks/base and settings. Only thing I have left to fix is MMS auto retrieval and breathing missed calls/SMS notifications. I already fixed cm privacy guard and the charging led options. These will be the only features in the ROM to start off with as they are the bare minimum to get SaberMod building from source right now.

After that I need to figure out how to make the gcc 4.9 work. So sorry guys don't think it will come today. I'll work on more later and see if there's any more features missing needed to make this ROM build.

For the builders that might have more time than I. If you can mange to forward port the breathing missed calls and SMS notifications into frameworks/base and settings you might have a fully functional SM 4.3 ROM before me :)

For the MMS auto retrieval a cherry-pick from the sm-jb-mr1 branch should work fine.

Oh and don't use the build scripts. Just do this.

. build/envsetup.sh

lunch (pick sm_mako-user)

make -j otapackage

[MENTION=3799866]strapped365[/MENTION]

[MENTION=4711514]rustyjay[/MENTION]
[Nexus 4 Original Android Development] Martin_Ro:
I think I found it:

In build/core/combo/Target_linux-arm-mk there is this sequence:

ifeq ($(strip $(TARGET_GCC_VERSION_EXP)),)
TARGET_GCC_VERSION := 4.7
else
TARGET_GCC_VERSION := $(TARGET_GCC_VERSION_EXP)
endif

And that's the point:

You don't have to set TARGET_GCC_VERSION but TARGET_GCC_VERSION_EXP to 4.9 and then it works :good:

So add, for instant in "build/config.mk" this row:

TARGET_GCC_VERSION_EXP := 4.9

and it will compile with gcc 4.9 (after fixing all this nasty bugs :( )
[Nexus 4 Original Android Development] strapped365:
I don't have anything SM synced. Im currently building an aosp build with some cherry-picks so I can try to see it go from stock to whatever...

Sent from my NeXuS⁴
[Nexus 4 Original Android Development] sparksco:
Awesome thanks! Yup I missed all that, but I haven't really looked into much yet, since for now I just want it to build with strict-aliasing and other compile failures.

As for busybox I cherry-picked the cm commits into mine to fix 4.3 and also latest bb upstream changes :highfive: