yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Martin_Ro:
Grmpf,

tried to build it with gcc 4.9 but currently external_bluetooth_bluedruid fails for me on a big number of errors:

external/bluetooth/bluedroid/main/bte_main.c: In function 'preload_wait_timeout':
external/bluetooth/bluedroid/main/bte_main.c:308:47: error: unused parameter 'arg' [-Werror=unused-parameter]
static void preload_wait_timeout(union sigval arg)
^
external/bluetooth/bluedroid/main/bte_main.c: In function 'preload_cb':
external/bluetooth/bluedroid/main/bte_main.c:530:32: error: unused parameter 'transac' [-Werror=unused-parameter]
static void preload_cb(TRANSAC transac, bt_hc_preload_result_t result)
^
external/bluetooth/bluedroid/main/bte_main.c: In function 'postload_cb':
external/bluetooth/bluedroid/main/bte_main.c:554:33: error: unused parameter 'transac' [-Werror=unused-parameter]
static void postload_cb(TRANSAC transac, bt_hc_postload_result_t result)
^
external/bluetooth/bluedroid/main/bte_main.c: In function 'dealloc':
external/bluetooth/bluedroid/main/bte_main.c:634:43: error: unused parameter 'p_buf' [-Werror=unused-parameter]
static int dealloc(TRANSAC transac, char *p_buf)
^
external/bluetooth/bluedroid/main/bte_main.c: In function 'data_ind':
external/bluetooth/bluedroid/main/bte_main.c:660:44: error: unused parameter 'p_buf' [-Werror=unused-parameter]
static int data_ind(TRANSAC transac, char *p_buf, int len)
^
external/bluetooth/bluedroid/main/bte_main.c:660:55: error: unused parameter 'len' [-Werror=unused-parameter]
static int data_ind(TRANSAC transac, char *p_buf, int len)
^
external/bluetooth/bluedroid/main/bte_main.c: In function 'tx_result':
external/bluetooth/bluedroid/main/bte_main.c:692:45: error: unused parameter 'p_buf' [-Werror=unused-parameter]
static int tx_result(TRANSAC transac, char *p_buf, \
^
cc1: all warnings being treated as errors

And yes, i picked a number of repos from your project because you allready invested a big bunch of work into these to make it compatible with gcc 4.9... but also I picked bluetooth but this seems not to work :(

Maybe a compiler setting that you use different than me because I use original build repo of aosp ???
[Nexus 4 Original Android Development] sparksco:
I don't think after merging external/bluetooth I had to add any extra fixes...

I haven't gotten that far that yet. Still getting a couple building errors for cm privacy guard and breathing notifications... Have to get a successful ROM build first :(

As I said before once I get the time I'll take a look at it and see what the problems are.
[Nexus 4 Original Android Development] strapped365:
[MENTION=2394329]sparksco[/MENTION] Hey man I'm home for the night and just started a repo sync for SM.

I was thinking about trying to build and release something...but then I thought, it would be like the kajillion other ROMs out there. anyways I'm not doing anything but waiting on this sync so hit me up if you want me to do anything that you haven't gotten to and I can try when its done.

Sent from my NeXuS⁴
[Nexus 4 Original Android Development] sparksco:
Heh, it won't build right now but if you see something I did wrong in putting any of the features let me know. I'm doing some new things with settings this time.
[Nexus 4 Original Android Development] strapped365:
Well I did a fresh sync of JSS15J today and it wouldn't build either and it was all stock so I'm good with that.

I figured if I was going to try anything it would be with your source

Sent from my NeXuS⁴
[Nexus 4 Original Android Development] Martin_Ro:
Hm, tried to build with the gcc 4.8 version of your git, but this also runs into the same errors in bluetooth.

gcc 4.7 works fine....

Seems as if they made gcc 4.8 way more picky about that stuff than I thought...
[Nexus 4 Original Android Development] qwerty123321:
Can't wait for 4.3!

You'll need to do a clean wipe with 4.3 right?
[Nexus 4 Original Android Development] sparksco:
Well good news and bad news. Good news is I have a ROM built.

Bad news is its missing all the features from sm-1.0.1

I'll release a update probably today for 1.1.0 but I don't see any point in publishing the source til I add more or most of the features back that were in 1.0.1...
[Nexus 4 Original Android Development] miguepereira77:
Just take your time...while we wait, we are trying other ROMs just to realize how big and awesome your work is!! :laugh::good::good:
[Nexus 4 Original Android Development] resynx:
Will the kernel be STS kernel? :D or is it stock kernel for now?
[Nexus 4 Original Android Development] sparksco:
Thaks... I already had a problem with someone else's gapps couldn't sign-into google account. So I'm just going to make some...
[Nexus 4 Original Android Development] DontPushButtons:
I've had the best luck with the PA 4.3 GApps, so far. Droidtheory ones were hit and miss, sometimes requiring an extra flash to reconnect to Google services after having already downloaded some apps through Google play.. I only used banks once, but it worked in that instance.
[Nexus 4 Original Android Development] benrees21:
That's cool. Will wait it out though until most of the features are added back. I'm happy waiting for a ROM as good as this. It reminds me of the NSCollab ROM for the Nexus S, once I got on it, I weren't getting off!!!
[Nexus 4 Original Android Development] sparksco:
Awesome. I plan on making gapps. I just found out because no matter what gapps I flash I can't sign into my g account. So I think it must be something on the ROM side of things. Other than that everything else works great.
[Nexus 4 Original Android Development] DontPushButtons:
Try logging into Wifi if you haven't already, that seemed to boot Google services into working for me a few times.
[Nexus 4 Original Android Development] sparksco:
I was on wifi
[Nexus 4 Original Android Development] DontPushButtons:
Well, worth a shot. There are a few Roms for me (mostly 4.3) that upon first boot won't connect to Google services. I have to fanangle it or flash a kernel or connect to Wifi and services will then connect.

I don't use Wifi much, since unlimited hspa+/4g trumps my home connection
[Nexus 4 Original Android Development] miguepereira77:
U mean grey bars? I solved it cleaning cache and data from Gplay services

Enviado desde mi Nexus 4 usando Tapatalk 4 Beta
[Nexus 4 Original Android Development] DontPushButtons:
Not just grey bars, literally not being able to connect to Google play, maps, wallet, etc.. Regardless of whether data was connected or not (I could browse Google play store on the browser, for example) it just wouldn't connect to Google services. I tried any number of things, including full wipes/reflashes/return to stock etc. Wiping the app cache/data never helped in those occurrences.
[Nexus 4 Original Android Development] sparksco:
No I don't think you quite understand. It has nothing to do with WiFi or Google services...

Its something in the ROM that causes the setup wizard to force close when trying to sign into a account.
[Nexus 4 Original Android Development] DontPushButtons:
Can you bypass the setup wizard at the start and add the account manually afterward?
[Nexus 4 Original Android Development] derekr44:
Kalo 4.3 is set up that way.
[Nexus 4 Original Android Development] sparksco:
No...
[Nexus 4 Original Android Development] sparksco:
FYI I'm making SaberMod compatible with all gcc versions.

https://github.com/SaberMod/android_system_core/commit/98471a521b2e89e5251ae3a8bacda2de09c0699f
[Nexus 4 Original Android Development] DontPushButtons:
Well I'm out of ideas ;)

Rudimentary bandaid ideas, anyway..
[Nexus 4 Original Android Development] Martin_Ro:
Oh, I thought this changes effect only that repo ! If this works for all repos, even better ! Hope to find some time today !

Gesendet von meinem AOSP on Mako mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] sparksco:
This fix is the only fix I needed to add to build between 4.7 and 4.8/4.9

The rest of the fixes are on sm-jb-mr2. For instance Bluetooth.
[Nexus 4 Original Android Development] Martin_Ro:
Hm, I have your bluetooth in the manifest and synced it this morning but still get build errors inside of bluetooth regarding unused Parameters...
[Nexus 4 Original Android Development] Lownita:
Sparksco if you make your own gapps, a minimal one would be very nice :)
[Nexus 4 Original Android Development] machoua:
+1. I would also love it if you had your own gapps. Makes it easier for all of us who uses SABERMOD exclusively. Its like a one stop shop for all of our ROM needs.
[Nexus 4 Original Android Development] rodleung68:
so if I came from stock rom, i want to flash to sabermod rom i have to Perform a NANDroid backup of your current ROM.

Perform a data factory reset/wipe (Do not format data in twrp recovery!)

i am using twrp recovery, i just data factory not format !!!

so after the factory reset, all my data will be wipe ? so i have to back it up by using titanium back up or can I just use teamwin back up ? after that use it to resotre ? Can I ? or titanium back up is better ?

Also where can I download Gaap package ?

thank you
[Nexus 4 Original Android Development] sparksco:
odd, maybe you should sync SaberMod repo and see for yourself...
[Nexus 4 Original Android Development] DontPushButtons:
I'm a little confused by your post, but I'll do my best here.

This is what I do:

1) use titanium to backup apps and app data

2) boot into TWRP, make a nandroid backup of system, data, and cache

3) wipe system, data, dalvik, and cache

4) flash new Rom + gapps, also any other mods I may be adding

5) reboot system

6) setup Google accounts, download titanium Backup, then restore apps and app data (note: do not restore system apps or system data, it's more trouble than its worth

The end! Hope this helps!

Edit: gapps here http://xdaforums.com/showthread.php?t=
[Nexus 4 Original Android Development] sparksco:
Guys I noticed CWM recovery got updated to version 6.0.3.5

Just curious I was on version 6.0.3.3 before and my 4.3 ROMs wouldn't boot. Do you guys think the .3 version was bad and maybe that's why it wasn't out long? I had one successful 4.3 ROM boot but I think I was on the .3 version of CWM.

Oh and the full source is build able now for people that want to try.

[MENTION=3799866]strapped365[/MENTION]
[Nexus 4 Original Android Development] -viper-:
Try it.. Maybe......cmw updated to .3 @ leaked 4.3 rom, later updated to .4 with official image...and last got to .3.5 just right after jss15j.. It may be this

Sent from my neXus⁴
[Nexus 4 Original Android Development] obtained:
Is the source only for mako?
[Nexus 4 Original Android Development] strapped365:
Going to repo sync ( to fix what was missing) then hopefully start us a build.

I don't know wtf Google is doing to maps but Navigation will not work no matter what ROM/Radio/Boot loader I run.

[MENTION=2394329]sparksco[/MENTION] do you have the backup/restore done in the SM side of the ROM?

Sent from my NeXuS⁴

---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------

Nexus 4 Nexus 7 is all I know. There could be other devices im just not looking at the source right this second.

Sent from my NeXuS⁴
[Nexus 4 Original Android Development] sparksco:
Yes. I haven't had time to get the other devices caught up yet... Once the ROM boots and all that and seems somewhat stable I'll do the other devices.

Backup/restore is still there but I can't test it since the last time I had a booting ROM setup wizard would force close. And since I did a clean fresh install I couldn't authenticate adb to get a logcat. Next time I'll just disable adb secure if it happens again.
[Nexus 4 Original Android Development] strapped365:
****...I just thought about it. But I never switched from building sm-jb-mr1. I just always built based off your second post.

Do I need to do anything special to build the new 4.3.x?

Sent from my NeXuS⁴
[Nexus 4 Original Android Development] sparksco:
All I did was repo init to sm-jb-mr2 branch over the older source and repo synced. You'll have to do a clean build though most likely.

So in the instructions to build just change the branch from mr1 to mr2

Then

. build/envsetup.sh && lunch sm_mako-user && time make -j otapackage
[Nexus 4 Original Android Development] obtained:
I did a fresh repo sync (not over the old source) and all I get for lunch is "full-eng"
[Nexus 4 Original Android Development] galaxys:
Nice to have another N4 chef! Will take the rom for a spin...
[Nexus 4 Original Android Development] JmPTaz09:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

This rom seems really nice; would live to see quiet hours added (didn't see it on recent version) and ability to disable notification bar clock but still have time in upper left corner when you pull down notification bar (like to disable since I have a big clock widget like many on my home screen). Just wanted to throw that out there but the rom seemed nice and smooth with all the optimizations added :beer:
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

The option to hide status bar clock is on SaberMod settings. Quite hours isn't portable because CyanogenMod mashed that change up with a bunch of other changes when they put it into their github. So I have no idea what code goes with what change.
[Nexus 4 Original Android Development] Crimsonthunder:
AW: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Really nice and fast rom! Thank you for your work. I hope you willst let it lightweight as it is. I hope you will get your 4.8 kernel working.
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Like I said 4.8 is really beta and only works on the nexus 7 kernel. So don't count on that.
[Nexus 4 Original Android Development] Crimsonthunder:
AW: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Ok thanks. I am using trinity kernel and it's amazing fast with your rom.
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

And it uses GCC 4.8? :confused:

I doubt trinity kernel makes the ROM any faster. The kernel doesn't really do much for ROM performance.
[Nexus 4 Original Android Development] Crimsonthunder:
AW: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

No i don't want to say that trinity uses gcc 4.8. I meant that trinity and your rom are working very well together.
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Right. Don't get wrong I have nothing against other kernels I just don't support other kernels and can't help debug any issues if you use other kernels. Main reason is I don't know what type of experimental stuff might be in the kernels or how their built. That's why I've standardized all my kernels using toolchains I've built.
[Nexus 4 Original Android Development] Crimsonthunder:
AW: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Yes I know this. I would never ask a rom dev too fix a problem with other kernels ;)
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Huh? I meant any bugs you might encounter when using another kernel. A lot of people get confused with ROM bugs blaming bugs on Roms because their using other kernels. That's why if your using another kernel I won't take any unusual bugs you report into consideration unless it's a obvious ROM bug.
[Nexus 4 Original Android Development] Crimsonthunder:
AW: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

That's what I meant! I think you misunderstood my comment. So enough with that. I like your rom and I am looking forward to future updates.
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

New build is uploading now but I'm also uploading three other Roms and pushing new toolchain changes to github so it's going to take awhile.
[Nexus 4 Original Android Development] Chochiwpg:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Cool, does the new build come with your newest kernel or just regular stock kernel?
[Nexus 4 Original Android Development] jarjar124:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Looks like his new kernel
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

It has the new kernel with sweep2wake from bricked kernel in it. The feature is disabled by default but showp1980 said the TouchControl app will work with it to enable it :)

ROM manager upload is 50% done. Next will be goo

It will appear here first:

http://www.clockworkmod.com/rommana...ifest&name=sparksco&deviceName=Google Nexus 4
[Nexus 4 Original Android Development] casonswag:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Cant wait rom running smoothly
[Nexus 4 Original Android Development] strapped365:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Can't wait. This is by far the smoothest I have seen my Nexus run hands down.

Sent From a Freaked out Nexus 4
[Nexus 4 Original Android Development] casonswag:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Whoa thats weird i just rebooted and some of my photos are showing in a video format now idk how ?
[Nexus 4 Original Android Development] casonswag:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

These suppose to be photos?
[Nexus 4 Original Android Development] kptnk:
Sounds like a plan :) :good:
[Nexus 4 Original Android Development] sparksco:
Well I hate to bring up even more experimental stuff in the midst of all the testing currently going on with the kernel. But since GNU released a stable version of GCC 4.8 Google has started their own work on their own version of GCC 4.8 which they have been adding fixes to. I built a toolchain using their GCC source but we all know mako kernel is known for not booting when built with GCC 4.8. If anyone likes to test experimental kernels let me know.
[Nexus 4 Original Android Development] ctfrommn:
Ill test anything, always :)

BTW, kernel is running flawlessly so far. I even have been experimenting with UVing this new one and I am now not having any issues at the same voltage I has SOD's with on the earlier posted one. I wonder if something didint compile the same with the UV one? At any rate, it is an awesome kernel.

Edit: Nevermind....SOD at -100mv again. So odd, every other kernel is stable at that for me and most I run at -150mv. Rock solid at higher voltage though.
[Nexus 4 Original Android Development] sparksco:
GCC 4.8 works!

Guys I just built a whole ROM using the new GCC 4.8 toolchain based on Google's GCC source and the ROM boots up just fine 0_o

Testing more now.
[Nexus 4 Original Android Development] Roastmeat:
Just flashed the latest version

Whenever I got into settings>security, settings crashes
[Nexus 4 Original Android Development] sparksco:
That's not the latest version

http://www.clockworkmod.com/rommana...ifest&name=sparksco&deviceName=Google Nexus 4

If you really want to run RC2 you'll need the RC2 patch to fix security settings.

But if you want less bugs and more features just flash the latest experimental.
[Nexus 4 Original Android Development] sparksco:
I ran into a couple problems building mako with GCC 4.8 and bionic. So I had to switch mako over to use linaro string handling routines. Hopefully this shouldn't make anything break like Bluetooth, camera, GPS, things like that. It still uses krait optimizations. If anything it'll probably increase performance even more :) Uploading now to ROM manager then goo. It will need testing. The kernel should be more stable out of the box now. I'll also post a separate test kernel built with the new GCC 4.8 toolchain.
[Nexus 4 Original Android Development] sparksco:
GCC 4.8 toolchain built ROM

Here it is!

Please test things like camera, gps, bluetooth, and as many other things as you want :good:

I have a felling everything should go well though. New test kernel coming shortly

http://developer.clockworkmod.com/downloads/293/4758/sm_mako-1.0.1-1366255168-0418.zip
[Nexus 4 Original Android Development] johnson8cyl:
To be honest in my experience uv-ing is overrated. The actual benefit to battery life is extremely minimal and not worth the possible stability issues. Just drop the max speed down some or adjust settings to squeeze battery life out.

I'll test anything you got BTW.
[Nexus 4 Original Android Development] sparksco:
Yeah the ROM I just posted doesn't have a UV kernel. I really notice a major improvement in performance on my nexus 7 with the GCC 4.8 built ROM. Not sure if it's the ROM or the kernel or both being built with the new toolchain or what. Thanks bro let me know how it goes. Test kernel being built now but for now just try the ROM lol.
[Nexus 4 Original Android Development] sparksco:
Do not flash this kernel.
[Nexus 4 Original Android Development] johnson8cyl:
About to test. Will report back. Thanks

---------- Post added at 12:21 AM ---------- Previous post was at 12:01 AM ----------

Stuck at Google boot screen. Anyone else? Flashed over 4-14 build. Wiped both caches before and after flash.
[Nexus 4 Original Android Development] sparksco:
Try flashing the new kernel too unless you already did that that might be the reason. Other than that the only other thing I can think of is how bionic kept failing to build previously, in which case I'd need to look more into fixing that up some.
[Nexus 4 Original Android Development] kptnk:
Downloading now the rom and will test with a clean install.

Edit : so first flashed the new kernel, and stuck at the google logo. So i flashed the new rom but with your first kernel, and it boots fine.

As you said there's something with the kernel.....
[Nexus 4 Original Android Development] phillysmako:
Booted fine for me fast as hell to here's what I did....I formated system wiped factory data reset wipe both cache and flashed ROM and gaps rebooted.... Is the kernel you posted the same that's packed with the ROM?
[Nexus 4 Original Android Development] kptnk:
So I wiped data + system + dalvik & cache....and it booted fine \o/ !!!!!!

First 4.8 Rom !!!!

It seems the sysem wipe is necessary...or the 4.8 kernel posted alone has itself an issu...anyway, rocking this lightin' fast Rom :D !!!

Edit : seems the kernel baked in the new rom is 4.7.....
[Nexus 4 Original Android Development] sparksco:
No the kernel in the ROM is built with GCC 4.7. I wanted to be able to tell if the 4.8 ROM worked on a known stable kernel. Guess it does :)

The kernel I posted is a GCC 4.8 kernel.
[Nexus 4 Original Android Development] phillysmako:
Well the ROM smokes man its fast!! Great work man!!:) its smooth too I got butter dripping off my thumbs lol....I wanna play more but I'm at work :( one more hour tho then I'll be able to check everything out I really like this ROM :cyclops:

OK morfic made a 4.8 kernel for the nexus ten I'm using it on my n10 and everything is fine check this link out its post 633 I think idk if it will help but maybe can give you some ideas for your 4.8 kernel http://xdaforums.com/showthread.php?t=2083885&page=64
[Nexus 4 Original Android Development] sparksco:
Yes the kernel is 4.7 but ROM is 4.8

First 4.8 ROM :)

Still haven't heard about the 4.8 kernel I posted :(

Edit: saw your edit

Will leave kernel with 4.7 for now.
[Nexus 4 Original Android Development] kptnk:
Well done Sparks ! It is sooooo fast :cowboy:

You might want to change the OP and your thread's title....spread the news :)
[Nexus 4 Original Android Development] sparksco:
Sounds like your repo sync didn't complete successfully... Works fine for me.
[Nexus 4 Original Android Development] obtained:
I did repo sync again and now it is all there. :)