yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] sparksco:
SaberMod arm mode is out! This increased benchmarks on nexus 5 on antutu by about 4,000

It also fixes the setup wizard crashes when using gcc 4.9 for the ROM.

https://gitlab.com/SaberMod/android-vendor-pa/commit/e56ded23054a0ba016f088b8737334edb8d0d914

https://gitlab.com/SaberMod/pa-android-build/commit/6b8b804bd5e421b11661114787287d261b6d20ce

https://gitlab.com/SaberMod/android-external-libpng/commit/76aae4dc81ad1b78a5857a22dd80ae3a2d89b597
[Android Software/Hacking General [Developers Only]] deepongi:
have anyone successfully compiled with sabermod on ubuntu vivid vervet (15.04)..? i get build breaks and segmentations faults with the toolchains, on both codes (rom and kernel)

like these:

CC drivers/media/platform/msm/camera_v2/sensor/flash/msm_led_torch.o
CC drivers/tty/tty_io.o
CC drivers/uio/uio.o
LD drivers/switch/built-in.o
CC drivers/tty/n_tty.o
CC drivers/tty/tty_ioctl.o
../../../../../../kernel/sony/msm8974/drivers/staging/android/binder.c: In function 'binder_thread_read':
../../../../../../kernel/sony/msm8974/drivers/staging/android/binder.c:2548:1: internal compiler error: Segmentation fault
}
^
0x77fdbf crash_signal
../.././../gcc/gcc-SaberMod/gcc/toplev.c:337
0x4b7185 bitmap_elt_clear_from
../.././../gcc/gcc-SaberMod/gcc/bitmap.c:280
0x4b7f7e bitmap_and(bitmap_head*, bitmap_head const*, bitmap_head const*)
../.././../gcc/gcc-SaberMod/gcc/bitmap.c:938
0x52568b df_live_init
../.././../gcc/gcc-SaberMod/gcc/df-problems.c:1549
0x51f6af df_worklist_dataflow(dataflow*, bitmap_head*, int*, int)
../.././../gcc/gcc-SaberMod/gcc/df-core.c:1153
0x51fd51 df_analyze_problem(dataflow*, bitmap_head*, int*, int)
../.././../gcc/gcc-SaberMod/gcc/df-core.c:1212
0x51fe6c df_analyze_1
../.././../gcc/gcc-SaberMod/gcc/df-core.c:1262
0x707b47 peephole2_optimize
../.././../gcc/gcc-SaberMod/gcc/recog.c:3602
0x707b47 rest_of_handle_peephole2
../.././../gcc/gcc-SaberMod/gcc/recog.c:3838
0x707b47 execute
../.././../gcc/gcc-SaberMod/gcc/recog.c:3872
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <mailto:sabermod.team@gmail.com> for instructions.
/home/infected_/cyan_12/kernel/sony/msm8974/scripts/Makefile.build:307: recipe for target 'drivers/staging/android/binder.o' failed
make[5]: *** [drivers/staging/android/binder.o] Error 1
make[5]: *** Waiting for unfinished jobs....
[Android Software/Hacking General [Developers Only]] sparksco:
I haven't had a chance to update yet but I will.

[MENTION=1077833]infected_[/MENTION] did you compile the toolchains or did you use the prebuilt ones?
[Android Software/Hacking General [Developers Only]] deepongi:
used the toolchains i compiled on 20150407 , and tried your prebuilts. same result.

going to restore my clonezillla image, and try to compile fresh ones on the 15.04 environment, using the mentioned package then.

ill report soon if it worked. and thanks for the tip, once again! :)
[Android Software/Hacking General [Developers Only]] sparksco:
What versions of toolchains are you using? Could be that gcc 4.9 is required.

Also maybe a issue with your art repo?
[Android Software/Hacking General [Developers Only]] deepongi:
4.8 for rom, and 4.9 for kernel. i think its not issue at the rom "sauce" code. it builds fine on 14.10 and 14.04 with sabermod, even with the fresh ones i compiled in 15.04
[Android Software/Hacking General [Developers Only]] sparksco:
Try 4.9 for the ROM. Working fine here. I'm still debating if I want to upgrade to 15.04 or just stay on 14.10...
[Android Software/Hacking General [Developers Only]] deepongi:
using 4.9 for ROM code i was able to build and boot on 14.04.. on 15.04 ive tried all of i could think of, but no luck.. its a toolchain compatibility issue with 15.04

external/vixl/src/a64/disasm-a64.cc: In member function 'virtual void vixl::Disassembler::VisitConditionalSelect(vixl::Instruction*)':
external/vixl/src/a64/disasm-a64.cc:427:1: internal compiler error: Segmentation fault
}
^
0x83ff1f crash_signal
../.././../gcc/gcc-SaberMod/gcc/toplev.c:337
0x7edf81 elimination_effects
../.././../gcc/gcc-SaberMod/gcc/reload1.c:2989
0x7ee16f elimination_effects
../.././../gcc/gcc-SaberMod/gcc/reload1.c:3131
0x7f1e2d elimination_costs_in_insn
../.././../gcc/gcc-SaberMod/gcc/reload1.c:3686
0x7f29ab calculate_elim_costs_all_insns()
../.././../gcc/gcc-SaberMod/gcc/reload1.c:1635
0x72527e ira_costs()
../.././../gcc/gcc-SaberMod/gcc/ira-costs.c:2198
0x71f683 ira_build()
../.././../gcc/gcc-SaberMod/gcc/ira-build.c:3429
0x717ebf ira
../.././../gcc/gcc-SaberMod/gcc/ira.c:5311
0x717ebf rest_of_handle_ira
../.././../gcc/gcc-SaberMod/gcc/ira.c:5565
0x717ebf execute
../.././../gcc/gcc-SaberMod/gcc/ira.c:5594
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <mailto:sabermod.team@gmail.com> for instructions.
build/core/binary.mk:619: recipe for target '/home/infected_/build_output/cyan_12/target/product/sirius/obj/SHARED_LIBRARIES/libvixl_intermediates/src/a64/disasm-a64.o' failed
[Android Software/Hacking General [Developers Only]] Ross Korolov:
Hi mate)) Im successfull builded and building on New Ubuntu 15.04 use default toolchains (with full flags)SaberMod for all my releases (rom & kernel) every time without any problems.

PS=: build for Qualcom devices. Cheers!
[Android Software/Hacking General [Developers Only]] deepongi:
i find that a bit odd... do you care to share the packages you installed? and sure you were using sabermod?
[Android Software/Hacking General [Developers Only]] sparksco:
Good to know thanks.
[Android Software/Hacking General [Developers Only]] Ross Korolov:
Of course, Im Resurrection Remix Lollipop official Developer&Maintainer. About packages Im upgrade my distro from 14.10 to 15.04 also just clone from git lab master branch arm-eabi-4.9 and linux-androideabi-4.8 Next before build I do export PATH for kernel toolchain and build. Another toolchains like 6.0 and 5.0/5.1 dont use coz it need to dellete -graphite flags on my rom.
[Android Software/Hacking General [Developers Only]] sparksco:
FYI if you put graphite flags in CC += you won't have any errors or issues. If you use KBUILD_CFLAGS you will. See the kernel source on gitlab.
[Android Software/Hacking General [Developers Only]] deepongi:
ok... got the bastard to build..! it was one of two things, or both.

1- had to give +0.05v into Ivy vcore, because of the +1.1Ghz OC (4.6Ghz current)... strange is that on 14.04 is stable.

2- maybe i was missing packages. i was initially following official android guide on the google pages.

anyway, glad its solved.
[Android Software/Hacking General [Developers Only]] ZION959:
[MENTION=2394329]sparksco[/MENTION]

Many Thanks for all the works .SaberMod Optimization and SM4.9 is Awesome . Everything work out of the box , Include Bluetooth ,The performance is unbelievable. Thank you
[Android Software/Hacking General [Developers Only]] ZION959:
[MENTION=2394329]sparksco[/MENTION]

It's a lot nicer now. Thanks
[Android Software/Hacking General [Developers Only]] ZION959:
Delete
[Android Software/Hacking General [Developers Only]] sparksco:
Thanks. I'll be adding strict as a option for flag info soon. But you beat me to it lol.

Bluetooth quit working again for me... I hope disabling vectorization flags for it fixes it..
[Android Software/Hacking General [Developers Only]] ZION959:
Yup. Bluetooth also quit working for me as well. I recompiled it now with your new fixed. I keep you updated. Thanks
[Android Software/Hacking General [Developers Only]] sparksco:
There's really nothing else it could be except -pthread which there's a list to disable for already.
[P3300, MDA Compact III  upgrading etc.] anoir:
hi everyone,

i have an artemis (mobile5) and the OS in my computer is VISTA, i tried to install activesync 4.5 but it told me cannot run on this computer, i downloaded the activesync for vista from microsoft website, but nothing....

Please if anyone know how to sync, send me a message

thank you in advance
[P3300, MDA Compact III  upgrading etc.] varvocel:
I don't use Vista, but I think you should try Windows Mobile Device Center which is designed for replacing ActiveSync in Windows Vista.
[P3300, MDA Compact III  upgrading etc.] Gajet:
Hmmmm yes if you have Vista, like I do, then it's not Activesync, but Windows Mobile Device Centre. Have you downloaded this?

When connecting my Artemis to Vista, it connects, but then takes a good 30 seconds before it begins synicing, but then completes very quickly.

If you have WMDC, what firewall are you using? Is WMDC and Sync Centre blocked?
[P3300, MDA Compact III  upgrading etc.] anoir:
thank you for your help, i already have wmdc but i think the problem is from the firewall, i sould disable it . i will try when i arrive home. thank you very much
[P3300, MDA Compact III  upgrading etc.] debully:
anoir - have you now resolved this?
[P3300, MDA Compact III  upgrading etc.] roadrunner_:
my vista notebook does not sync with my p3300!

no reaction at all from windows mobile device center!
[P3300, MDA Compact III  upgrading etc.] mospantagruel:
try go to settings - connections -USB to PC and uncheck "enable advanced network functionality"

this worked for me. started to sync after 10 sec
[P3300, MDA Compact III  upgrading etc.] Sul05:
Thank you did the trick
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
To be honest, it sounds like you had a failing battery. It happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
theres an xposed app called amplify that helps to block some wakelocks , startups and alarms. it might help.

"all i can really do , is stay out of my own way and let the will of heaven be done"
[Nexus 4 Q&A, Help & Troubleshooting] dmanww:
I just got a used Nexus 4 and checking it out before I hand it over to a friend.

The first issue I've found is the pull down doesn't work. After installing the full version of Nova Launcher it works on every home screen but still won't work from apps or the lock screen.

Using Test Your Android it looks like the top bar is not sensitive at all. The same area has a problem when screen is rotated. (can't post a link to a pic yet)

When I got the phone it was already factory reset.

I don't have a SIM card installed.

It's running stock 5.0.1
[Nexus 4 Q&A, Help & Troubleshooting] copong:
To rule out a software issue, have you tried a complete wipe (including /data and "sdcard") then reinstalling stock, or maybe a custom rom?
[Nexus 6  General] rester555:
http://www.droid-life.com/2015/03/09/android-5-1-factory-images-available-for-nexus-devices/
[Nexus 6  General] rester555:
Anyone know if there is a new radio or a new bootloader img?
[Nexus 6  General] beachbum40:
Look at this.http://www.androidpolice.com/2015/0...gs-android-5-1-ota-roundup-for-nexus-devices/

---------- Post added at 06:53 PM ---------- Previous post was at 06:52 PM ----------

Its an Australia build from what I'm seeing. Maybe an international build?
[Nexus 6  General] rester555:
Thank you sir
[Nexus 6  General] cmh714:
ah hell, the radio is back to the 95 version......what gives with that?
[Nexus 6  General] darren.wlsn1:
i would assume that for the aussies its best radio.
[Nexus 6  General] buschris:
are some people not satisfied with the Nexus 6? Mine runs perfectly. there is no holy grail smh
[Nexus 6  General] roaddaw9:
Thinking about flashing this on my Nexus while on at&t, but think I may not flash radio and use radio from previous build. Any thought or suggestions sound this approach?
[Nexus 6  General] darren.wlsn1:
these updates are the exact reason people buy the device, we get update (bug fixes) first and were free to flash different radios ect to improve whats near perfect.

best to flash all radios imo BUT this image has the older radio.
[Nexus 6  General] italia0101:
Just because abradio has a higher build number doesn't mean it's better.
[Nexus 6  General] gee2012:
I would have expected the 47M build to be posted rather then 47I.
[Nexus 6  General] asutton13:
I've flashed this update without flashing the radio that came with it, and can confirm that everything seems to be working fine so far. I upgraded from LMY47E to LMY47I.
[Nexus 6  General] casonswag:
Are u on tmobile and what radio u have?
[Nexus 6  General] asutton13:
I'm not on T-Mobile, I'm on Rogers in Canada. I was under the impression that the T-Mobile version was LMY47M, but perhaps I'm wrong. I'm using the radio from the previous build, specifically the baseband is reported as MDM9625_104446.01.02.98R.
[Nexus 6  General] PunishedSnake:
Yup
[Nexus 6  General] the_rooter:
radios depend on where ur at the 98r radio works much better for me than the 95.
[Nexus 6  General] darren.wlsn1:
radio does not even have a higher build #, like i said it hasn't changed.
[Nexus 6  General] rockinroyle:
Running I on T-Mobile n6. Was on E since Saturday but 98 radio was causing continuous clicking on the phone any time I called someone with another n6? 95 seems much better for me and noticed that my battery hadn't decreased as much on my ride into work this am as much as previous few days. May be nothing and just my experience but figured I'd share. Also both were full flash and wipe through fastboot
[Nexus 6  General] manup456:
I have had better luck with 95r where I am on at&t and stock LMY47I.
[Nexus 6  General] buschris:
again, higher Letter build is not specifically better. Each carrier has it's specific build. People are too hardheaded to get this. Bug fixes from Google will have numbers, not letters.
[Nexus 6  General] ogarlen:
So, being on Verizon, is it better to stay on E or install I? The comments below from a commenter on Android Police seem to make sense to me...?

"People! You don't have to be on the latest build!

D = International version

E = Verizon version

I = Australian carrier version

M = T-Mobile version

If you're on AT&T, you probably want to remain on the D build.

With that said, all builds work on all networks. Specific builds are optimized for the specific networks listed earlier. Don't stress over not being on the latest build. As Android Police stated elsewhere. All of these builds/optimizations will probably be rolled into one update later on. Almost all of the changes on these different builds are SIM related for specific carriers.The D build was released through OTA and factory images to unlocked N6's. The E build is only being released on new N6's that come from VZW (no OTA yet, but the factory image has been released) and has the ability to use VZW's VoLTE calling. The M build was released as an OTA for N6's on T-Mo (no factory images yet) and has the ability to use VoLTE on T-Mo. The I build was released as an OTA to N6's on Australian networks (no factory images yet). I don't know if the I build activates VoLTE for Australian N6's, but I bet it does.

The interesting thing though, is how the D build and M build both use the radio ending in 95R. While the E build (VZW) uses the radio ending in 98R. So, even though the M build is presumably a later build than E. It uses the older radios, 95R. My 'theory', is that the 98R radio (the E/VZW build) has some CDMA or VZW specific tweaks and 95R radio (D/M builds) are more for GSM, with the M build activating VoLTE on T-Mo.

I haven't looked into the I build or the radio yet, because I don't live in Australia."
[Nexus 6  General] buschris:
Exactly. If it's any indication that Verizon phones shipped with "E" version, and John Doe got an OTA to "abc" version, then it stands to reason from logic that certain carriers have different versions. Some people are just not very smart and I've tried to explain this till I'm blue in the face.

Since I will never get an OTA because I run a custom ROM, I will stick with the radio/baseband and version based ROM on my phone.
[Nexus 6  General] Smallsmx3:
I'm on tmo, I had volte on D&E & now M. So don't say M is to get volte.
[Nexus 6  General] R4INS:
It does have a number its 5.1.0_r3. The r is for bug fixes and merges that don't deserve a full number increase. The Linux/Unix version numbering goes X(major update).X(minor update).X(batch of bugfixes). The R is for steps along the way before a 5.1.1 update is released. They can't change the version number every time they submit a fix to aosp or we would end up with 5.1.99999999.

As AOSP source shows, there IS new code so this IS a new code base not just a "carrier build".
[Nexus 6  General] buschris:
"The interesting thing though, is how the D build and M build both use the radio ending in 95R. While the E build (VZW) uses the radio ending in 98R. So, even though the M build is presumably a later build than E. It uses the older radios, 95R. My 'theory', is that the 98R radio (the E/VZW build) has some CDMA or VZW specific tweaks and 95R radio (D/M builds) are more for GSM, with the M build activating VoLTE on T-Mo."

The "D" and "E" radios have the same build date, so neither is "newer". Could possibly be the same said for "M" and "I". Anything newer will likely be released with the next Android versions...
[Nexus 6  General] aergern:
I CAN not stress this enough. This is the proper info. The OP is right .. there ARE no carrier specific builds.

I grabbed this new build and the only img I flashed was system.img because it's the only part of the gz file that was needed. The radio was old and the version in the E release seems to work the best. The bootloader hadn't changed so why mess with it. I use TWRP so recovery.img didn't mean anything. This isn't complicated. Either flash what you need .. stay where you are or whatever suits you as the use best.

I will say that the new sim card handling code seems to have made some difference. I was at 1 bar and kind of a ****ty LTE connection in my office building. Today .. 4 bars and a very fast connection. Normally in my livingroom I get around 18mb/6mb as far as network speeds ... last night after flashing the system.img with the fixes I consistantly got over 40mb down and over 20mb up. So it appears those "minor simcard" fixes and the rest did do something useful.

Bottomline .. flash it if you are having issues and would like to or don't flash ... and carry on. It really is that simple. :good:
[Nexus 6  General] cam30era:
I saw a short post on Android Police that confirms this. It went further to state that the "I" build was a bug fix for the "D" build. Not sure about that, though....
[Nexus 6  General] R4INS:
Most people don't understand how this stuff works. Google merges fixes and changes daily but we don't see them. It would be a waste of data to push a system update every day its easier to pack em all in one "service pack" you could say and ship that, example would be 5.1.1 vs 5.1.0. If the Australian market needed changes made, and they were added say a week away from the E build then it would also include tons of other fixes warranting it a new build letter and new r number.

They don't just build the same code as D, change the letter to I and ship it. Its had merges and fixes and updates along the way. Yeah a carrier may have triggered this earlier than usual build when normally it would wait till 5.1.1 but that doesn't mean that this build isn't the best build for all users. I guarantee it has all the same things as the builds before it plus more. And minus that crap 98 radio I wouldn't be surprised if that was pulled all together. Yuck.

So, everyone run the newest system image, its the best for every nexus. As far as radio run the one you feel best in your area. Google isn't all knowing on how your cell area is :P
[Nexus 6  General] :
All we can do is speculate until there's an official announcement from Google. I am on Sprint, I was on "D" and installed factory image for "I" this morning. While I do lean towards the theory that "E" is Verizon's and "M" is T-Mobile's there isn't really solid proof direct from big G. Google has announced that it will have a unified build eventually. I'm gonna start the rumor train and say it will be 5.1.1!
[Nexus 6  General] buschris:
I will run the version that gets pushed to Verizon phones, just to be sure I am getting the best reception. I could care less about the ROM itself, it's all 5.1 and they all have the same damn bug. I'll wait for 5.11 or whatever

---------- Post added at 08:09 PM ---------- Previous post was at 08:00 PM ----------

I think I am confusin people with this build stuff. I am more specifically referring to the radio on the builds, I am using 98R which is for Verizon. I am actually using a 5.0.2 based ROM, BlissPop which is the best one out there at the moment.
[Nexus 6  General] slider112:
Well put. So you're running the 98R radio with 47I not 95R? Who is your carrier?
[Nexus 6  General] rester555:
Having a Verizon N6, I followed the advice of Post 3 (Android Police link). My phone has the 98R running LMY47I system image and all is swell.
[Nexus 6  General] roaddaw9:
At&t running build I with E radios. Been solid, no problems
[Nexus 6  General] iainaaldrich:
What build is being pushed to Sprint? D or E? I manually flashed E and it works bit if D is designated for Sprint then maybe I should use that.
[Nexus 6  General] tom1807:
I cannot agree with your statement, for me the 98 radio gives me higher speeds on LTE than the 95 Radio.

And what I am seeing here is the comparison between Sprint, T-Mo, Verizon, etc.

I have the worldwide model, located in Asia and yet 98 radio is definitely better for me.

I can use band 3 and 28 (1800Mhz and 700Mhz) and 98 is definitely an improvement.

So for you, 98 Radio is maybe crap, but that's too generic, there are others who benefit from this radio
[Nexus 6  General] doitright:
I corresponds to source revision 5.1.0_r3, whereas D corresponds to source revision 5.1.0_r1

Also, these letters are being assigned BY Google.

These letters are NOT "carrier builds".

The only part of any of this that is carrier specific is the 98 radio, which is a HACK/COMPROMISE/EMERGENCY fix for VERIZON.

Just the radio, not the whole build.

---------- Post added at 03:25 AM ---------- Previous post was at 03:21 AM ----------

No. These letters have NOTHING to do with carrier or region. NOTHING AT ALL.

That website you found that on pulled that OUT OF THEIR ASS. No facts supporting it, only circumstantial observations.

If you are on Verizon, you are best off with the RADIO that ships with the E build. You can mix that with any newer build you like, including I.

They aren't including the 98 radio with I because it has an emergency hack in it.

---------- Post added at 03:36 AM ---------- Previous post was at 03:25 AM ----------

He doesn't mean crap as in "good for nobody", he mean crap as in "hack". The only reason there are two reasons, is that somebody needed a hack that wasn't good for *the majority*. Later on, the hack will be merged into the common radio with a conditional branch running the hack under some conditions.
[Nexus 6  General] slicknsxy:
I'm with tmo and i flashed 47l and i don't see any issues so far
[Nexus 6  General] SilkyJohnson:
To all the people in here asking or curious to which build to flash to their carrier, the answer is:

FLASH EM ALL!!! YOU OWN A DAMN NEXUS, YA SISSIES.
[Nexus 6  General] wright_ac:
Here's one little thing I noticed on the Factory Images page LMY47I can't be carrier specific because if you look for example at the Nexus 5 Factory Images the 4.4.4 Release 2 is purposely labeled as carrier specific, reckon if it was so important to flash one specific ROM per region the Factory images page would say "only for X or Y region", just something I thought worth mentioning.
[Nexus 6  General] mijkz:
Nicely put :)

We got 47D in the UK OTA, so that's what I've flashed. Nothing's broken - everything works fine. I see no reason to flash anything newer just to get a later build number in the system details screen...
[Nexus 6  General] compuw22c:
I keep trying to tell my girl build i is the latest

But she just wants the D ;)