yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] spamtrash:
Why? You shall NOT ROOT your phone, if you want to be honest. and, if anyone would have a residual amount of so-called honesty, after rooting - no one should even think about giving the phone to the service for warranty repair, period.

By the comparison: if you have used your TV set as the rain protection while on camp, I'd say that it would be not very honest to claim 3 dead pixels, huh?:rolleyes:

And, you have presumably completely wrong info how the insurance works... read it, and then discuss (a tip: if I pay for the bank account which includes the insurance, if I put my moneys into the bank's account - guess who's paying for the insurance).

Contrary to above, it is sure that as Samsung's solely income is (in this case) by selling SGS's. Therefore, using your own argumentation, it is easily found that for any fraudulently rooted phone repair under the warranty - ALL buyers have to pay, because it is included in the purchase cost, which is paid by mass of the honest users, which even do not know about the phone's rooting possibility and consequences.

Of course, the above will be true unless you are not so naive to believe that Samsung did not included the repairs of some percentage of phones into this price.

Maybe are you thought that any warranty repair decreases the net Samsung's income? :laugh::laugh::laugh:
[Galaxy S III General] odoto:
Of course not, because the rain (which is your fault... well, not the rain itself, but the exposure) did kill the device, not the dead pixels. But in case of a rooted phone that died because of a hardware issue, the manufacturer is the one who screwed up, regardless of the software changes you did. If a device dies because of pre-existing hardware issues, what is the difference between custom rom and stock from the manufactures perspective?

I agree I don't know for sure how your specific insurance works (how would I?), but I know how those normally work. It usually works like that: some company wants to offer their customers an additional insurance. But they don't have the knowledge to do it themselves, after all they are not an insurance company. So they delegate it to one. They pay the insurance company a fee for every device sold (or some sort of flat fee if it is not device-bound). In return the insurance company is liable for repair/replacement costs if the customer kills his phone. And if people are abusing that insurance, the insurance company has to increase the fees (obviously they don't wanna loose money). So the company who is paying that fee also has to increase prices for their consumers, because they don't wanna loose money as well.

So at the and all customers are paying for it. It always works like that, no company wants to loose money.

True, of course. Like I described above the customers are always paying in the end (or switching to a different company).

BUT Samsungs repair costs are not higher because of rooting/custom software. If nobody would modify the software, Samsung would even have higher repair costs, because in that case they would have to pay for all repairs. If a portion of the repairs can be denied for whatever reason, they save money.

So the fact that some people modify the software does not add to Samsungs repair costs (except for the really rare cases where people actually fry there phone by overclocking all the way to the moon and back), but they still void there warranties, thus saving money.

But they are only saving that money by discriminating against custom software users, for no reason.

So it is not like all customers have to pay more because of custom software users claiming warranty. The contrary is true: at the moment all "normal" users are saving money due to custom rom users, because those get there warranty voided for no factual reason.

Of course Samsung (and other manufactures) state that there is a reason, that they would have higher repair costs because of custom software users. But I think that is a groundless claim, just made to safe money or because of missing knowledge. (I'm talking _hardware_ warranty here! Of course they would have higher costs if they would fix phones where people messed up the software). So because of the unfounded fear of manufactures that custom software users will kill lots of their devices, we get denied rights that all other users have. I'd call that discrimination.
[Galaxy S III General] TheCraig:
Try hard bricking it, It can't be hard, purposely disconnect the cable when a PIT flash operation is in progress?

Off course I would rather take a chance that it may not break for MONTHS instead of it breaking and Samsung may not replace it.
[Galaxy S III General] odoto:
1. we have an idea what subsystem is likely causing the problem... that's all.

2. you _might_ be able to advance faster towards triggering the bug by doing a lot of write ops, but that is just a guess (and certainly not immediately)

3. chances are good your phone can live a long and happy life with a fixed firmware, even if it got the buggy chip

4. you would risk getting another mainboard with an affected chip...

5. there is always a risk of Samsung not accepting your claim (happened to some people here)

6. if your phone doesn't encounter SDS within a 2 year warranty period, it probably never will

7. don't do it! your would risk ending up without a phone now, to avoid a small risk of loosing your phone somewhere in the future. if you can't stand having a phone that might brick (what I understand), sell your phone (or get a refund if you still can)
[Galaxy S III General] philgalaxs3:
Try it ... and let us know :laugh:

More seriously : thanks to odoto for this thread and for information on EU "law" limitations ..
[Galaxy S III General] odoto:
I know what you you meant, but that sounds almost like the EU law limitations are my fault :D
[Galaxy S III General] philgalaxs3:
Corrected , hope that sounds better. Sorry for my poor english .... und danke sehr :good:
[Galaxy S III General] odoto:
AW: some thoughts on warranty, custom roms and SDS

I just thought it was funny ;)

And your English seems totally okay, no worries :)
[Galaxy S III General] spamtrash:
Very simple. Please write here procedure for overclocking without the root, and I will tell that you're right immediately.

So what is the difference between the warranty?

It seems that you did not understood the rules at all. Therefore, just short comparison:

INSURANCE: someone is paying additionally to the price of unit to be covered against unintentional, caused by lack of care, or ANY OTHER DAMAGES,

unconditionally

.

WARRANTY: You are purchasing the Unit for a price, in which the free repair is covered

conditionally

, if you are obeying the T&Cs of warranty. It is your choice if you will, but, INTENTIONAL void of the warranty by rooting and then

trying to hide it is a fraud

.

Comparing to the cars, you can have comprehensive insurance, yes? This is your free will to buy it. and, you have the car warranty. If you are honest, would you claim the corrosion caused by driving your car on a seaside on the background of warranty or insurance? Looking at your posts, you probably would call the insurer aproach a fraud, same time cleaning mud, alga and fishes and shouting that your car never has been contacted with salt water and this ugly dealer have to repair it under the warranty.

Once again, this is your choice: apply warranty T&C's and then claim on base of such, or buy the additional insurance and do whatever you want.

Once again: please give me an example of overclocking without the root, first.

Secondly, you have of course the right to disagree with the T&Cs of warranty. It is very simple: do not buy the product, which is related with unacceptable by you warranty terms. You have even wider choiche: you can buy it and you have the free will to ignore T&C's. The fraud starts when you're voiding knowingly these T&C's, and then you are trying to use (violated by you) warranty.

Third, of course you can call it discrimination, but the manufacturer and seller has right to set the purpose of the device. This is not discrimination, but the AGREEMENT between the customer and seller/manufacturer. Same way you will most likely call discrimination the fact that most of manufacturers are putting the water damage indicators to their devices. (Funny thing by the way, years ago it was no such things in phones. But amount of people like you, who submerged their units into water and then claimed it under the warranty - enforced the manufacturers to do it).

As I said above, your screams are like: I have bought a BMW, then I tried to reach my friend in a yacht in the middle of harbor in it, but it become rusty in result, therefore I need it repaired under warranty.

Finally, I think that you should read the Chainfire's statement related to it on his portal.
[Samsung Galaxy Nexus] kickthefreak:
this look so promising, i'll give a try

awesome work dude.
[Samsung Galaxy Nexus] bananagranola:
I have been using an SR2 variant for half a day now. It runs beautifully; fast and smooth, yet incredibly customizable. (In the interest of full disclosure, though, I'm biased; I bugged synergye about creating one for maguro after using his Desire HD one for months). I have used both Franco's kernel and Lean kernel with it without problems.
[Samsung Galaxy Nexus] synergye:
I'll release a bug fix for the navbar settings FC when I get home. It only works if tabletUI is enabled currently.

sent from codefireX
[Samsung Galaxy Nexus] ak:
I want to try this rom ... i had a good feedback by my friend. :fingers-crossed:
[Samsung Galaxy Nexus] kongming:
Hi dev, just to report, beside the Navigation bar FC. The Gallery also FC after take a shot with camera.
[Samsung Galaxy Nexus] Tribes11:
Is there Led Customization options on this ROM?
[Samsung Galaxy Nexus] Justinhopaolo:
why does it say in download that it's 4.2?? is it 4.2 or 4.2.1?
[Samsung Galaxy Nexus] tarekh020:
4.2.1

-----------------------------------------------------------------------------------------------------

-----------------------------------------------------------------------------------------------------

What a great rom that makes Nexus smooth ,hopefully it keeps updated with the new upcoming enhancements

Just wonder , what the best VM heap size for maguro ? ,cause i swa in screen shoot that it's 512 but my phone is configured with 256
[Samsung Galaxy Nexus] darrenng_ff:
Navigation Bar setting FC
[Samsung Galaxy Nexus] tsuart:
Camera FC after shot.

But...

Great rom!!!
[Samsung Galaxy Nexus] RobBull69:
I can confirm that I have both of these issues. I didn't notice the camera one at first because I use Camera Zoom FX. Anyways, great to see this ROM for the GNex. I've been using it on the N7 and it has none of the 4.2 lag.
[Samsung Galaxy Nexus] schukje:
Hope the fc's can be ironed out. Then gonna try again. Looks so good mate!!!

grtz from the crazy basterd from holland. and i love maguro roms.!!.
[Samsung Galaxy Nexus] logi43:
It is a lightning fast rom, Cyanogen Kernel fluid is very good and quite fast but despite these virtues find very disordered control options of the rom and fcs are too important and obvious, hopefully the developer solves the problems. Thanks for the contribution to the community of this rom AOSP lightning.
[Samsung Galaxy Nexus] miqz:
also with me Camera FC after take a photo..i dont have FC with navigation bar

use franco r361 kernel..
[Samsung Galaxy Nexus] Mustaavalkosta:
I fixed the FC on navbar menu. Fixed apk and flashable zip here: http://downloads.codefi.re/mustaavalkosta/codefireX-Maguro/SR3

DISCLAIMER: Flashable zip has not been tested so use it at your own discretion.
[Samsung Galaxy Nexus] synergye:
Can someone get a logcat of the camera FC? Thank you.

sent from codefireX
[Samsung Galaxy Nexus] bananagranola:
https://docs.google.com/file/d/0B5tujVRMa7gURVpLLXVyNlZYQjA/edit
[Samsung Galaxy Nexus] psyonicus:
Hi.

I can vouch for the flashable zip. It works great.

I do have a small problem, let's see if anyone can reproduce it: long pressing on the home button shows recent apps and not the navring, as it should according to the navbar settings.

Best regards.
[Samsung Galaxy Nexus] tsuart:
Great!

tnx
[Samsung Galaxy Nexus] kuyam:
i'm eagerly awaiting a version of this rom with non FCing camera.. will try it out for sure. Do you recommend to stick with the supplied kernel or just the one you like generally among other 4.2 roms?
[Samsung Galaxy Nexus] tsuart:
Flashed Franco Kernel (r360).

It seems to work fine.

:good:
[Samsung Galaxy Nexus] bananagranola:
Unless you changed the defaults in CFXSettings -> Interface -> Navigation bar -> Button 2 longpress action, I believe the default behavior is that you need to swipe up from the navbar (not long-press on a button) to get the navring.
[Samsung Galaxy Nexus] psyonicus:
Thank you. Yes, swiping up does open the navring.

But check this out: set your long press behavior to empty ( blank) and try it: it behaves as the recent button does.
[Samsung Galaxy Nexus] bananagranola:
Interesting. Yes, it does. Is it supposed to not do that?
[Samsung Galaxy Nexus] psyonicus:
Sorry for double posting, but here is another issue:

The DPI wizard doesn't work. The last step doesn't actually changes the DPI, and the reboot button hangs the settings screen.
[Samsung Galaxy Nexus] logi43:
Where is the access to replace the themes, theme chooser?? I seen that applications are installed in system / app Thanks for your work
[Samsung Galaxy Nexus] bananagranola:
It's an app like any other (not in Settings). It should just be in the app drawer.
[Samsung Galaxy Nexus] tsuart:
Any news about gallery's FC?
[Samsung Galaxy Nexus] logi43:
You can install this file from its recovery under its responsability.

Yo I have no FC in the gallery.

http://db.tt/dlLpwHXs
[Samsung Galaxy Nexus] Mooks:
Tried it but still fc's using the cam... :(

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] tsuart:
Yes, still fc. :(
[Samsung Galaxy Nexus] latiszm:
https://bugs.launchpad.net/linaro-android/+bug/1075111

This site has some information on this. seems like a fix was submitted in december. memcpy error.

Can you please make a new build with this fix for us to try?
[Samsung Galaxy Nexus] :
Re: [ROM][AOSP-4.2.1][LINARO][4.7.3-Toolchain] [SR3] OFFICIAL codefireX Maguro Builds

Just follow all the steps and at the end edit the build.prop. I rarely use those wizards and interfaces.
[Samsung Galaxy Nexus] bboran:
So which build should i flash? There is a testbuilds folder in the link and it contains a build which is the lates i think (build yesterday). Can i flash this? Thanks.
[Samsung Galaxy Nexus] schukje:
Re: [ROM][AOSP-4.2.1][LINARO][4.7.3-Toolchain] [SR3] OFFICIAL codefireX Maguro Builds

Downloading right now. Crackflashers just try! :);)

grtz from the crazy basterd from holland. and i love maguro roms.!!.
[Samsung Galaxy Nexus] Mooks:
hi!

thx for this awsome rom!

vellamo html5 benchmark is even faster than the galaxy s3 :D

the batterylife is also great! still 72% left after 1.5 days with wifi and some phonecall!

vut please fix the cam ;)

edit:

it would be nice if you could make a "not working" section. a lot of user would appreciate this ;)
[Samsung Galaxy Nexus] tsuart:
I saw that for the desire hd has been released SR5.

I hope it comes out soon for the nexus, with the necessary bug fixes.

It will definitely be the rom that I will use daily.
[Samsung Galaxy Nexus] bananagranola:
Re: [ROM][AOSP-4.2.1][LINARO][4.7.3-Toolchain] [SR3] OFFICIAL codefireX Maguro Builds

I know that synergye is actively working on fixing the camera. I would guess that he wants to prioritize that before SR5, especially since SR4 and SR5 are mostly Ace-specific stuff and a tool chain update.
[Samsung Galaxy Nexus] tsuart:
R: [ROM][AOSP-4.2.1][LINARO][4.7.3-Toolchain] [SR3] OFFICIAL codefireX Maguro Builds

Tnx!
[Samsung Galaxy Nexus] tsuart:
Anyone knows when is scheduled a new release?

I'm very happy with this, but a fully functional rom will be perfect for daily usage.

Great work guys.
[Samsung Galaxy Nexus] scottx .:
Re: [ROM][AOSP-4.2.1][LINARO][4.7.3-Toolchain] [SR3] OFFICIAL codefireX Maguro Builds

Installed it on my n7 and was pleased to see a maguro build. This should be awesome.

Edit: when I try to enter navigation bat settings via the codefire app it crashes. I can't stand the standard navbar layout so its a deal killer for me. When it's fixed I'd love to come back.
[Samsung Galaxy Nexus] bananagranola:
Re: [ROM][AOSP-4.2.1][LINARO][4.7.3-Toolchain] [SR3] OFFICIAL codefireX Maguro Builds

Flashable zip to fix navbar here:
[Samsung Galaxy Nexus] scottx .:
Re: [ROM][AOSP-4.2.1][LINARO][4.7.3-Toolchain] [SR3] OFFICIAL codefireX Maguro Builds

Why thank you! I wish I had seen it before.

Edit: Great ROM. Nice and fast with all of the features I have come to expect from AOKP and then some.

Only bug I can see is recents doesn't work correctly. Shows the applications for a split second and then they vanish. Hitting the button to kill them all does nothing.
[Samsung Galaxy Nexus] mert2go:
Recents is working perfectly here! This rom is the fastest i've ever used :)

EDIT: Camera is not working
[Samsung Galaxy Nexus] tnicko:
Yeah, same here. Camera isn't working.
[Samsung Galaxy Nexus] tsuart:
I hope that the development of this rom did not stop.
[Samsung Galaxy Nexus] Persithis:
Yeah me too. I like Linaro builds so much!
[Samsung Galaxy Nexus] Mustaavalkosta:
Well, development of cfX didn't stop but latest news I heard about maguro builds are that camera is still broken thus no new builds. I don't do hardware support so this is one man enterprise on that front with several other devices to support at the same time. Give it some time and maybe synergye will come through with a fix for camera. :)
[Samsung Galaxy Nexus] crazyg4merz:
Re: [ROM][AOSP-4.2.1][LINARO][4.7.3-Toolchain] [SR3] OFFICIAL codefireX Maguro Builds

Is there a fastcharge toggle? And disable beep sound on volume up? Can't live without those things :)
[Samsung Galaxy Nexus] Nickamina:
There has been some serious work going down over at the codefirex git as of late.

I get the feeling we haven't seen the last of them. ;)

https://bitbucket.org/codefirex
[Samsung Galaxy Nexus] bananagranola:
Awhile back I built a copy with their new toolchain. Camera did not FC, but se linux was creating su problems for all cfX builds. They have since reverted back to partials, so camera FCs on maguro once again, but I think someone new is developing for tuna devices specifically last I heard. So we will see.
[Samsung Galaxy Nexus] Nickamina:
Interesting - cheers dude.
[Samsung Galaxy Nexus] bananagranola:
I personally built a copy with this commit and can confirm that with it (at least on my phone), the camera is fixed.

Note: there is currently no first-run setup. Accounts must be added from settings. But...crossing fingers!
[Samsung Galaxy Nexus] killersloth:
All I'm saying is...

Where's the toroplus love?

:)

Sent from my Galaxy Nexus to all you wonder nobodies!
[Samsung Galaxy Nexus] bananagranola:
I can give it a shot if you would like, but as it stands maguro isn't officially supported yet either; I just built a copy out or curiosity.
[Samsung Galaxy Nexus] bananagranola:
I have built personal copies of cfX for maguro, toro, and toroplus here. Features are in a flowchart by pnoire here. These are straight builds right off the codefireX source. If you use them, three caveats.

1. These are personal, unofficial builds that I did just for fun. I have confirmed that maguro boots and the camera does not force-close like it did before; killersloth has confirmed that toroplus boots; I have not confirmed that toro works in any way (I don't have the hardware). I have not tested them extensively, though I have been using the maguro build since it was built on May 1. I do not guarantee that these builds will not brick your phone or set it on fire or otherwise damage it. I do not guarantee download speed (since it's hosted on Google Drive).

2. I made no important contributions whatsoever to the code. This is entirely the work of synergye and the codefireX team.

3. The first-boot tutorial does not work. You will need to add your account and change your settings manually in the Settings app.

Official cfX support should be coming, but some bugs need to be ironed out before SR21 (for example, first-boot), though nightlies may be coming before that. I built this just because I saw the latest tuna-fixing commit and was too excited to wait. I'm sharing it in case anyone else has similarly twitchy flashaholic tendencies.

EDIT: apparently the newest builds include an appbar and pie controls. Newest maguro's now in the shared folder.
[Samsung Galaxy Nexus] sykomaniac:
Patiently waiting :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bananagranola:
If you're waiting for the newest unofficial maguro I mentioned, it's up here and so far it works for me. I didn't think I'd use the appbar and I don't usually use PIE controls, but it's actually handier than I expected.

If you're waiting for the nightlies or SR21, me too. :)

If anyone is using any of these, could you let me know? Obviously you don't need to clog up the thread with "me!" and "toroplus here!", but could you please shoot me a PM? I'd just like to know out of curiosity.
[Samsung Galaxy Nexus] sykomaniac:
Waiting for your unofficial build :) And thanks for sharing!
[Samsung Galaxy Nexus] Nickamina:
Great, I'll check it out later (maguro). Any noteworthy bugs we need to be aware of that you've found so far?

I'll update this post if I find anything personally.

Edit:

Been playing with it for a while,

- Very, very fast - Easily as quick as the fastest ROMs out there; AK47, EOS 4, VANIR. Maybe even a little quicker.

- Toolchain appears to be the codefirex 4.7.3 one still (for the kernel at least according to trickster mod). Was expecting 4.8?

- Pretty stable as far as I can see. Camera's working. No problems flashing (flashed ROM first, booted up and checked stuff out, went back into recovery, flashed GApps and Leankernel)

- Not quite as fully featured as I'm used to. No theme chooser was a surprise. Has PIE and plenty of statusbar/navigation mods however.

All round pretty nice. :good:
[Samsung Galaxy Nexus] bananagranola:
Theme chooser is an app. It's not in the settings menu. No idea about the toolchain though. I haven't seen any bugs so far. Oh! And the first-boot tutorial is back.

EDIT: according to bitbucket.org/codefirex/android/commits/3d1935c0cd0459807e554f79b0c76c0a610133fb the ROM is built with gcc 4.8 and the kernel with 4.7. If you look for newer commits it looks like 4.9 was used at some point but reverted back to 4.8.
[Samsung Galaxy Nexus] bananagranola:
The newest maguro is up on Google Drive. Links are in my signature. Toro is uploading, and after that's done toroplus will be built as well.

The new builds have a slide-out menu in the settings app. If you want to use cfx settings, don't forget to turn them on in the upper-right corner. Otherwise, the app won't do anything.

I'm thinking about setting up a build script on my home server and uploading them to Google Drive automatically. Please PM me if you would be interested in regular (probably weekly) builds and, if so, which one. If I get enough requests I'm going to set it up.
[Samsung Galaxy Nexus] bananagranola:
Maguro and toro are up. I'm building toroplus right now. But one question: I've gotten 6 thanks on my last post as of the time of this post (which is nice, thanks), but no PMs. I'm not sure how to interpret that with regard to the regular builds...?
[Samsung Galaxy Nexus] parkson:
Plz Delete
[Samsung Galaxy Nexus] killersloth:
I like cfx builds for toroplus. I'd throw you some thorough feedback but I work all the time now. Too busy and dependent on tether to flash a ROM right now. It sucks lol.

Sent from my Galaxy Nexus to all you wonder nobodies!
[Samsung Galaxy Nexus] bananagranola:
Toroplus is uploading right now. Thanks for the reply. I don't mean that I want everyone to give feedback, I'm just trying to gauge interest to determine whether I should script up some regular builds. I think I'm just going to set it up, though, more for the heck of it than anything else.