Related
Just received this:
Please can you read the information below and confirm whether you wish us to continue with the dispatch of your order.
We are now pleased to be able to update you regarding the situation on the Galaxy Nexus and the issue regarding volume errors on some devices.
We tested the devices yesterday when they arrived and we did find the error in some of the phones but it appeared only to affect devices in poor signal areas using 900mhz frequency.
This was obviously of great concern so we were in discussions with various people and specialists yesterday morning to clarify the situation. We did not wish to make an announcement until a clear solution had been given by Google.
We can now confirm that Google were alerted early to this issue and have been working on a fix. It is software related and as you may have seen from various forum and blog posts this morning, they are now able to confirm that they will have a fix. It is NOT hardware related. We cannot yet say the precise date that this fix will be released but it is expected very soon.
The software update will be pushed out to devices by Google, free of charge, the moment it is available.
Given the discussions we had and this soon to be released update, we were happy to despatch our devices, we simply could not make any official announcement until we had a clear solution.
We of course pride ourselves on the communication that we have with our customers and we were aware of the large number of enquiries we were getting about this yesterday from various media sources.
We hope however you will understand that we wanted to give you clear and confirmed information before we made the announcement. We will of course update you as further information is released.
Regards
Sales Team
Clove Technology
This is also posted on their blog: http://blog.clove.co.uk/2011/11/23/samsung-galaxy-nexusbug-fix-update/
Not surprised. Most things can be fixed via a software update. Also if it was a hardware bug Samsung would have stop shipments to distributors or ordered a hold on the stock. Samsung would have also delayed the launch of the phone on bell/virgin which is set for next week.
I don't see anything new that couldn't be found online from their post.
- Google software fix - reported by P3Droid and oscillik (via chat with android developer).
- Google were notified about this issue - from their bug report page.
- Google will push update - same report by P3Droid
- It is NOT hardware related - this one is new and very hard to believe.
I'm still waiting for Google/Samsung announcement.
So, basically what they are saying is that it is a software issue that will be fixed with a patch but they still ask you if you wish to receive the device?
Sounds fishy to say the least. If patch will be released you'd expect them just to dispatch all of the outstanding orders.
Clove are telling an outright lie. Neither Google, nor Samsung have made any public statement to say that this is not a hardware issue. The only statement that has been made has come from Google, and it is the following:
We are aware of the volume issue and have developed a fix. We will update devices as soon as possible.
Click to expand...
Click to collapse
All this statement says is that Google are working on a software fix, and that they are aware of the problem. Says absolutely nothing about the cause of the problem.
Handtec reporting that Samsung stopped shipping the phones:
http://twitter.com/#!/handtec/status/139328485121458176
Samsung stopped shipping so 48hr delay - we may need to cancel some tracking (if it does not showed picked up)
Maybe the software fix is not the best solution.
Sent from my Nexus One using XDA App
Sent from my Nexus One using XDA App
oscillik said:
Clove are telling an outright lie. Neither Google, nor Samsung have made any public statement to say that this is not a hardware issue. The only statement that has been made has come from Google, and it is the following:
All this statement says is that Google are working on a software fix, and that they are aware of the problem. Says absolutely nothing about the cause of the problem.
Click to expand...
Click to collapse
But so far that is what information we have! I'm not trolling ya, but you spent a great deal of time convincing people it was hardware! And I must say, your argument was quite convincing
oscillik said:
Clove are telling an outright lie. Neither Google, nor Samsung have made any public statement to say that this is not a hardware issue. The only statement that has been made has come from Google, and it is the following:
All this statement says is that Google are working on a software fix, and that they are aware of the problem. Says absolutely nothing about the cause of the problem.
Click to expand...
Click to collapse
Can you find a Google source for this statement? All articles seem to point back the Verge rather than the primary source from google. Need the official link as I'm going to call Three and say im happy to keep it on the basis that they will release me from contract if Google do not promptly release the promised fix. Best to get it logged before my 2 week return period is over.
KiNG OMaR said:
But so far that is what information we have! I'm not trolling ya, but you spent a great deal of time convincing people it was hardware! And I must say, your argument was quite convincing
Click to expand...
Click to collapse
tell me, where in Google's statement does it say that this is a software issue?
oscillik said:
tell me, where in Google's statement does it say that this is a software issue?
Click to expand...
Click to collapse
Exactly!!
Google 'allegedly' (no actual source yet) state they have a fix. Im not surprised Google are able to develop a software patch to treat the symptoms but the underlying problem could still be hardware.
From what I see on here is people are happy to take a few words and interpret as they please. Remember when Samsung kept saying the launch is on the 17th and it is not delayed? Everyone (incl loads of blogs) took this as prrof that the handset would be available from most outlets on that day. No one expected it to be just one branch of one store (regardless of whether or not you claim there is additional battery drain or whatever). In that case, Samsung were technically correct but it was what they DIDNT say that was important!!
Likewise, here we should note that Google (if indeed they did make this statement at all) DIDNT say it was hardware or software, just that they are working on a fix.
My prediction: there will be no recall, a software patch will appear to have resolved the issue, at least to the point you have no rights to return the unit. There may or may not be a different (improved) hardware build in coming months.
KiNG OMaR said:
But so far that is what information we have! I'm not trolling ya, but you spent a great deal of time convincing people it was hardware!
Click to expand...
Click to collapse
No kidding. Rule #1 on forums is anyone with a lot time to gab on a forum probably doesn't know what they're talking about.
TiltedAz said:
No kidding. Rule #1 on forums is anyone with a lot time to gab on a forum probably doesn't know what they're talking about.
Click to expand...
Click to collapse
please, tell me where in Google's official statement does it say that this is a software issue?
Take your time.
I love the way they say FOC to repair an error...
Update:
I did notice some users pledging, but didn't realized we actually got something going on, I'll be updating with an estimated pledge sum, I'm not naming individuals but at least summarizing this, the ball is rolling and hopefully the purpose of this (which is attract developers in a good, respectful and rewarding way) will pay off!
Dear Fire Phone owners:
We are looking very disorganized and scattered on efforts, we also have GOOD but limited dev support due to the quantity of Fire Phone owners and so the quantity of them that actually visit XDA is even lower.
So let's join efforts, I see @madushan1000 doing effort to unlock the bootloader and willing to blow his own qfuses for it, on his hard earned money.
If you know a developer, or are a developer, we must seek answer for the following answers:
1.- How many phones do you need to play around until you blow up the right qfuse?
(If the answer is n <= 10, I don't see why we can't all join a bounty *paid upfront* for that developer to buy the damn 10 phones ~$1350 dlls, if he gets it done on the first attempt, he deserves the remaining hard earned money solely for rewarding, and even more.)
2.- Is there any exploitable bug on the qcom trustzone that can at least trick into thinking the phone is unlocked? What would be needed to do so?
(If all that's required is a time and effort to do it, I don't see why we can pledge on a *serious* bounty and paid the developer $1000 dlls when done, if he is a reputed developer and has evidence or prior work, I don't even see why we can't paid upfront either.)
3.- Are you interested in a bounty for fixing the camera code on the existing CM11 rom? What would be the required incentive for it? (can you do it @ggow, @madushan1000?)
We should be able to brainstorm and just think in joining efforts, even if my questions or ideas are the wrong ones, hell! then just tell everyone out loud which idea or process is the right one! Let's work together people!
I just saw 13,000 fire phones sold in Ebay, what the hell?, 1000 fire phone owners that visit XDA can't pledge $1000 dlls?
If this is seriously not doable I will just delete the post right away, but let's at least seek some developers and show them we can organize a good offer, we might find some interesting results.
I will pitch in for an unlock. Not sure of amount until it happens.
The Fire Phones on ebay are still going for over a 100 each. With the new tablets announced today and as people forget the fire phone, the price should drop VERY soon... I hope. I would love to pick up a spare.
Got mine on eBay on $57.50, i hope devs can unlock the bootloader fix the camera and the NFC
Wow, I'm glad to see something like this going on. But I'm afraid I'm not going to be able to do any serious work until next month or so. My final exams coming up. And next I have to find a job.
Anyway, I'm working on a kexec module my spare time, Provided that it works, We can start developing a boodloader unlock. People with already bricked phones might be able to help too by trying to unbrick their phones following something like this http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ . If someone finds a working method it would help very much for the development.
As per hal issues I proposed to have tow sets of libraries on the rom to bypass the amazon liblog.so issues. May be @ggow is working on it? I don't have to proper knowledge about android build system to do it, or the resources.
madushan1000 said:
Wow, I'm glad to see something like this going on. But I'm afraid I'm not going to be able to do any serious work until next month or so. My final exams coming up. And next I have to find a job.
Anyway, I'm working on a kexec module my spare time, Provided that it works, We can start developing a boodloader unlock. People with already bricked phones might be able to help too by trying to unbrick their phones following something like this http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ . If someone finds a working method it would help very much for the development.
As per hal issues I proposed to have tow sets of libraries on the rom to bypass the amazon liblog.so issues. May be @ggow is working on it? I don't have to proper knowledge about android build system to do it, or the resources.
Click to expand...
Click to collapse
- Bypassing the liblog issues unfortunately is only one part of the problem - that in itself is tricky to do. A mega amount of changes required to the android stack.
- The camera issues require the HAL source code from Amazon or they need to be written from scratch.
- I am currently looking into what can be done about the camera. I have started looking at the binaries to see if they can be patched.
- I have also been studying the bootloaders, @madushan1000 I'll message you separately when I have a spare moment.
Thanks, I'll try to help you with the hal stuff in the future.
We should see a flood of people joining this forum due the eBay sales. 120 plus a year of prime was what made me buy. I'd pitch in a bit if it were unlocked. After tax and shipping, the phone has only cost me $31. Better than a Windows phone as a spare I would surmise even without seeing my package delivered yet.. Should be here any minute from USPS.
And I'm still driving this to get more people to say I'm up with $XX for the bounty, seriously no one was replied with a quantity WTF?
If anyone is reading this and still doesn't understand, a "bounty" is to get your offering of money for our developers @madushan1000 and @ggow for helping us get our Fire Phones with an unlocked bootloader or with a decent camera on CM11
Example: I'm in with $30 for the bounty
count me on $20 for bootloader unlock
Thread cleaned.
Please discuss other subject matter elsewhere and keep on topic here.
Also, keep it respectful.
Thanks,
Darth
Forum Moderator
I needed prime and a phone and made an impulse decision I immediately regretted after I learned there is a locked bootloader. Put me in for 20.
Also, I have a small coffee roasting shop and if either of you devs are coffee drinkers send me a pm me and I'll ship you some good stuff. That's not a bounty, it is an effort to increase productivity.
I'm in for $20 if somebody can handle this. I'd like to have a solid phone to hack on that's not my main.
I pledge 20.00 US dollars to this.
Sent from my Fire Phone using XDA Free mobile app
I'll pledge 100 for an unlock bootloader.
I will throw in $20
I through in 30$ i am looking forward to it ?
I will throw in a new phone with prime and $100.
i will throw in $20 and been waiting for it
I would give another $20. It looks like Amazon has no plans for it. I emailed them a few days ago:
" Hi,
I understand that you want us to provide the steps to Unlock the bootloader for your Fire Phone device.
I'd like to bring to your kind attention that unlocking your phone’s bootloader will cause you to lose all the data from your phone and voids your phone's warranty. That is the reason why currently we don't have plans of releasing a bootloader unlock for the fire phone.
However, I've forwarded your message to our development team for consideration as we make further improvements. Customer feedback like yours is very important in helping us improve the Fire phone experience."
Hi There I have scoured the XDA forums for up to date information on either the LDU S10 or Note 10 device range. Unfortunately there seems to be very little information on hand, which is unusual considering there are loads of threads about previous Galaxy S series LDUs and retail mode disabling.
If anyone has information about disabling retail mode on the current generation devices, your help is much appreciated.
Note: The password 5444 trick that used to work no longer does, which would allow factory reset and MDM removal. Now I don’t plan on taking a gamble using ODIN to try and flash stock N975F onto my N975X device for fear of bricking. I have successfully flashed S6 devices in the past but I’m a bit more reluctant with the lack of info on hand.
Any help is much appreciated, those of you who might be inclined to post ‘This is a retail device, you shouldn’t have it’ - I would politely state I bought this on ebay as a legitimate listing and would like to use it for Android Studio App development for my final year college project. I have used LDUs in the past as an access point to development on Android as my daily driver is iOS and I wanted to break away from Xcode for a different challenge. I do computer science and have a passion for smartphones so spending 1200€ to do App testing on a Note10 Plus is not an option when I paid similar for my daily driver.
To clarify when I say a ‘legitimate ebay listing’ - if I can purchase on ebay with my own money that is my business and clearly satisfies eBays user agreement. Thanks in advance, all info welcome.
Same here
Hey Stephen, Please let me know if you have any developments with this as I am in the same boat as you
Will do bud ?
Hopefully hear something soon.
JAMOS1 said:
Hey Stephen, Please let me know if you have any developments with this as I am in the same boat as you
Click to expand...
Click to collapse
i heard from note9 and below you cannot flash stock firmware or it will brick the phone. but note 10 is okay to flash with stock firmware, but the imei#00000000 which u cannot use it as a normal phone untill you repair the imei.. hope this hellp..
Hi guys, I found in another posts these codes to be used to remove demo mode... any of you has ever tried?
galaxy
ruletheair
rethink
demomode exit
instoredemo
unlimited
remove cod
nationwider
As we discussed xxxx I decided to prepare the bounty for anyone who will unlock 5G support for most/all countries. Feel free to support it (because Google doesn't want to...). You can find it there:
xxxxxx
Introduction and details are either in link or below in citation.
Hello everyone! I'm Sebastian and I'm part of XDA Community since 2010 (XDA profile)
Actually, It's not the first time I tried to encourage people to donate for anyone who will make a modification for an Android phone: Back in 2012 as LG 4X community we tried to either force LG to unlock bootloader by petitions or collect a bounty for possible developer who would do that unofficially.
Ten years passed and again me and other people faced a problem with a company which blocks the features on a phone for no reason. This time it's 5G for Pixel 6 (Pro), codename oriole/raven. My carrier (Orange Poland) uses basically the same 5G band/parameters as Magenta Austria (which is officially supported) and I can't use 5G because Google doesn't allow me just because. This is sad and disgusting.
For now at least we have working VoLTE/VoWiFi Magisk module which can be found here but that's it. Tensor SoC makes things even worse, because previous Pixels could be unlocked via Qualcomm tools.
I've tried to reach a few modders/devs by myself but either they have no idea or don't care...so I hope that money would be the best motivator
Okay, so now simple rules:
- All collected money goes to the person who will share a working software mod (Magisk/Xposed module, modem patch or whatever works), either for me on private message on XDA (and then we can share it for private testing for the ones who donated) or just share for public testing on XDA thread
Then after either private or public tests, bounty gets finished and the money will be sent.
- If we don't succeed or Google will come with official solution (doubt), I will cancel this campaign and contact the support to force the refund. In case of any problems, I recommend to leave any contact (email) while you donate to this bounty.
Also keep in mind that the modification will most likely require unlocked bootloader and/or root (although the less invasive solution, the better.
PS: Feel free to spam Google about that abomination here or other Support Google threads. It's time to them to finally explain to us why we can't use Pixel phones' features even if they are supported.
Click to expand...
Click to collapse
MOD EDIT: Links removed.
thanks for setting this up
Thanks Sebastian!
Already donated. Hope the campaign will succeed.
If the campaign fails, what happens to the money raised?
I think it's woth noting on your post.
itamargs said:
Thanks Sebastian!
Already donated. Hope the campaign will succeed.
If the campaign fails, what happens to the money raised?
I think it's woth noting on your post.
Click to expand...
Click to collapse
I will delete/cancel it and contact support to force the refund. Also if anyone has any doubts, he can suggest me how i could "authenticate" myself even more. I'm here for 12 years already and had a history with mods, TWRP and custom ROMs, I have not violated anyone's trust.
Edit: added description on campaign site, I will polish this thread a little after I take my PC
Edit2: Okay, everything is done. I'm about to make a thread on Oriole section as well as make some posts in threads related to 5G which I was looking on. Might try to share the info on some Telegram groups too
Have to consider your carrier's coverage, what bands they use for 5g and if they have a band whitelist just connecting to any 5g band won't do jack for you
maxius4 said:
Have to consider your carrier's coverage, what bands they use for 5g and if they have a band whitelist just connecting to any 5g band won't do jack for you
Click to expand...
Click to collapse
Well, I have an 5G antenna around 10m from my flat... I talked with my carrier about it, they tried to do anything but they couldn't. It's only Google's fault, every other manufacturer somehow supports 5G when modem supports it, but Google just won't do that.
I have also donated, fingers crossed this will eventually work. Thank you for your work!
reas0n said:
Well, I have an 5G antenna around 10m from my flat... I talked with my carrier about it, they tried to do anything but they couldn't. It's only Google's fault, every other manufacturer somehow supports 5G when modem supports it, but Google just won't do that.
Click to expand...
Click to collapse
Have to take into account this is more a carrier issue than googles, the issue is you not buying the phone from them but from Google and they are not going to go out of their way to support a phone that was not purchased from them
Thank you. You should also be posting same on pixel 6 forums to get more attention.
maxius4 said:
Have to take into account this is more a carrier issue than googles, the issue is you not buying the phone from them but from Google and they are not going to go out of their way to support a phone that was not purchased from them
Click to expand...
Click to collapse
Google doesn't even sell P6 in Poland. Also as I said in description: hardware supports it, my carrier uses same band/frequency as other carrier in Austria which is supported. If you still don't believe: take a look on Pixel 5 forums, they have a 5G unlock with Qualcomm tools. 100% it's Google's stupidity.
In the past I bought some Chinese phones and with global ROM they just worked..
The issue is the carrier and Google can not sell a phone with everything unlocked as it would run across a world of hurt from every country's on earth regulators that deal with spectrum use. Sure you can "unlock" it but with age of a phone comes vulnerabilities and fw updates to fix issues also your carrier / someone may care more than you want them to about you essentially breaking your country's communications/spectrum laws. Honestly, is it really worth all the trouble to make it work how you want it to or get a phone from your carrier with the support you want?
MOD ACTION:
Thread closed.
@reas0n
Please await my PM.
My Android TV lost power during a firmware update and is now in a bootloop. In the case of the 5000 Series TV's, Philips removed the built in hardware feature(Standard on all Android Devices) to boot into bootloader/fastboot or recovery using hardware buttons on the TV. Why I ask? They don't disable that on their European model TV's, so why only in the US? when i should just be able to boot to bootloader and reflash the firmware myself, I now can do nothing and my TV is an expensive brick. I'm not a baby and I can work on my own stuff Philips, no need to disable standard features and render my device junk for no reason other than from a bad update flash! Their website claims to have the update file but of course they give a dead link. Customer support says they have no updates to give and that the update they claim to provide on their website doesn't exist(still claims to be available on their support website). They also claim that the low level flashing mode used by their updates, explained in their update instructions, again, don't exist and I made it all up. I was repeatedly told they couldn't help me, when asked to be put into contact with someone who could help me, I was simply asked if there was anything else they could help me with and the same cycle repeated, at which point I terminated the call. When i asked to speak with a supervisor in hopes of escalating the issue to someone that was in a position to have an actual conversation with me, I was told they were all busy and that I would be called back. I was never called back. After my own testing and extensive research, I found that the blue upgrade screen explained in their update instructions from their website, does indeed exist, as I was able to rename a zip to the naming scheme the tv wants, and the blue upgrade screen comes up, but because I don't have the proper signed .pkg file, the reflash fails. Multiple attempts with customer service has done nothing, they are all programmed, braindead robots and I just wanted to scream into the phone from frustration, that's how ridiculous the interactions were. It was clear to me that these customer service people are payed to not think or use any sort of logic and instead just continue reading off their rhetoric on the screen in front of them. It was a very toxic environment from the moment someone picked up and it was akin to some sort of warfare tatics I would imagine are being used by the likes of the CIA and such. I called customer support for support, instead of support what I got was the runaround, felt belittled and bullied into the belief that I am wrong, when the information presented to me, as well as personal testing has shown otherwise, not to mention my own extensive knowledge of the Android ecosystem. At the core, this TV is just an Android device with a giant non-touchscreen. I have an update file from another user on XDA in zip format, but without the ability to boot into the bootloader or recovery, I can't use it. I would need the untouched upgrade_loader.pkg file for this tv to be run from usb in order to reflash the TV and recover from my brick. If anybody was smart enough to grab any files from the tv, any of the updates, ota updates, .pgk files, anything that could possibly help me get this TV going again, please reach out to me.
[email protected]
Luckily, this TV is still under warranty and if I can't get this fixed myself following the proper channels, then I will def be getting it either repaired under warranty or just telling them I want my money back and going to a more customer friendly company. If Philips wants to be Anti-Consumer and disable standard built-in hardware features, offer non-existent files on their website and then treat their paying customers like crap with their dodgy customer support practices, then fine, they can pay for the damages caused by their practices and decisions, and never again will I spend another penny to support or help keep this company afloat, and I encourage others to rethink their purchases as well, across the board.....
I strongly encourage Philips to rethink their position and to stop stiff-arming their customers and instead work with them. When I call to inquire about an offered firmware file on their website, I don't expect to be asked why I want the file. The fact I want it, their website claims to have it available for download and just the plain old fact that I want the file for my $900 TV for my own personal archive for instances such as this, I don't feel any explanation is required. I have no issue taking this over to YouTube and placing my terrible experience with this into the proper hands of somebody that will get this info out there to the masses and attempt to get several million more sets of eyes on this in the hopes of maybe putting some pressure on these people to stop being so trivial and petty about dumb things. I need the .pkg file to fix my TV, Philips, not a big deal, stop pretending it is please.....
TV Webpage: https://www.usa.philips.com/c-p/75PFL5604_F7/5000-series-android-tv-with-google-assistant
TV Support Webpage: https://www.usa.philips.com/c-p/75PFL5604_F7/5000-series-android-tv-with-google-assistant/support
why? because planned obsolescence is not forbidden per law