yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] sgt. slaughter:
Not mistaken in the slightest were talking phones here...not the one MOTO tablet....no MOTO phones have the unlockable bootloader cept the dev Razr...least HTC lived up to what they said and gave a solution....MOTO flat out lied and said they were giving devices unlockable bootloaders like what's on the xoom and has yet to do so since stating such....
[HTC EVO 3D] WatermelonSlim:
Did you not read the link in the post right before yours? It said the razr on verizon has s-off. In the same article it says the gsm razr was released with s-off.

As I said before, the only phones Motorola locks down are the ones the carriers request be locked down. The rest are unlocked.
[HTC EVO 3D] notasimpleway:
QFT! Not to mention, they are not obligated at all to give us ways to unlocking or rooting our phones. But they did! Also, they aren't obligated to give us source code of proprietary drivers(camera). Someone correct me if I am wrong.

Sent from my iPhone with the bigger GeeBees.
[HTC EVO 3D] GrimReaper24:
My guess is since some new line of phones are coming out at sprint.. ICS won't get here till after some of the new phones come out.. So people will buy em and be droolin over ICS .. After that we will see some Lice Cream Sandwich .
[HTC EVO 3D] Snowled:
https://twitter.com/#!/MajorDickDanger/status/192348470634491904/photo/1
[HTC EVO 3D] hemelsw:
That's a automatic reply, check my post with HTC's Communication Manager, thats the guy responsable for all outgoing info!

This was my post:
[HTC EVO 3D] ngagephone:
Wrong I had MOTO atrix unbranded unlocked and bootloader was locked down.
[HTC EVO 3D] ckoadiyn:
HTC EVO 3d no longer on their site for sale makes me wonder if it hit eol
[HTC EVO 3D] powduh09:
Nice... Create an entire thread dedicated to that assumption, and then still post it in this thread... SMDH...

sent from my downgraded hboot 1.50 3vo running ZR3D injected with anthrax... s-off HTC, thanks to the real developers, I now have control of my device again ;)
[HTC EVO 3D] ckoadiyn:
Not everyone checks the general section some people just add a thread as a favorite n only check those ones hence.the reason to mention it in here as well.
[HTC EVO 3D] sgt. slaughter:
Yes I know kholk and his group worked their extreme magic over there on the device...but still that's not MOTO releasing a way to unlock the device nor making it easy either for them as the method still doesn't work for all yet...

And I prolly should of been more specific earlier as my commentary on being dev friendly are concentrated toward those released on US carriers as those are the only ones that matter to me personally...and in regards to being US carrier dev friendly HTC kicks MOTO by long shot, not even debatable.

Now back to topic though, my bad OP for straying so far off in the thread...
[HTC EVO 3D] powduh09:
Just saying... No sense in posting that comment in its own thread, then posting it in anothet discussion... Besides, who cares that sprint isn't selling the 3vo anymore?,this thread is about the update to ics, not whether or not I or anyone else can go get a nee 3vo... And now back to regular scheduled programming...

sent from my downgraded hboot 1.50 3vo running ZR3D injected with anthrax... s-off HTC, thanks to the real developers, I now have control of my device again ;)
[HTC EVO 3D] ckoadiyn:
I would assume eol means less updates that's all if we even get it HTC is saying yes but Sprint hasn't said anything. Sprint does get the final say not HTC
[HTC EVO 3D] Kaanardo:
Only htc watch update.

ICS, for the end of the year (autumn or winter)

http://www.htc-hub.com/htc/actualites/htc-evo-3d-mise-a-jour-disponible-htc-watch/

So, ics don't "comming soon"

f*ck htc !!
[HTC EVO 3D] EclipseX:
Htc Rezound have the same ****ing probleme =/

but maybe rezound is getting at 09/05...maybe

http://www.droid-life.com/2012/04/1...-and-verizon-xoom-on-59-and-423-respectively/

about the Evo 3d....we don't know yet, but maybe can be between this and xoom

kannardo, I think this guy on htc don't want talk with you lol

not the end of the year its confirmed until final summer
[HTC EVO 3D] loscassapalle:
i remember for HTC Legend that froyo came 5 month after the first announcement date.

someone should work on camera and 3d drivers. We will need them also for JB...
[HTC EVO 3D] Kaanardo:
Lol, its not my conversation, other guy ^^

What is your source about the confirmation ? Do you have a link? Thx
[HTC EVO 3D] EclipseX:
Not really, i just talk with the guy os usa, france, uk and Portugal and the answer is the same....update umtil final summer
[HTC EVO 3D] WatermelonSlim:
Yes the Atrix was locked down. Then the dev community freaked out and Motorola promised future devices would have a way to unlock them. They then said they would still luck down the devices that carriers wanted locked down (probably because Verizon was threatening to drop Motorola at the time, and Motorola was for sale so they couldn't afford to lose any carriers).

Since then, the only Motorola devices locked down are the ones the carriers request.
[HTC EVO 3D] nate2665:
In taiwan i asked htc for evo 3d updates two days ago.and htc comfirmed that they are testing the ice and sense3.6 right now,and will release soon
[HTC EVO 3D] sgt. slaughter:
Which has been every Moto device in the US CDMA released since....
[HTC EVO 3D] WatermelonSlim:
They are just as "unlocked" as HTC devices. You just can't get s-off on them. Which brings me back to my original point, it's hypocritical to say HTC is dev friendly but Motorola is not when you get the same level of "unlocked" on both of their devices.

And at least Motorola is clear that the only reason they are locked down is because that is the only way a carrier would pick up the device, while all their international or "unlocked" devices are actually unlocked (or at least unlockable). HTC devices are locked down, regardless of carrier, and regardless of if the device is international or not.
[HTC EVO 3D] diestarbucks:
Motorola only has two devices in any region for which they themselves offer an unlocked bootloader. The Xoom and the RAZR Developer Edition.

http://developer.motorola.com/products/bootloader/
[HTC EVO 3D] WatermelonSlim:
Well according to these guys:

http://androidcommunity.com/droid-razr-locked-bootloader-gets-an-early-work-around-20120414/

Motorola unlocked the "international GSM RAZR."

Don't know if that is the same phone you're talking about or not. Either way, the 2 devices you mentioned is still 2 more than HTC provided s-off for.
[HTC EVO 3D] SoraX64:
HTC provides a way for almost ALL of their phones to be unlocked in a safe and official way. S-OFF isn't necessary. It's nice to have, but it is safer to not have it. Just allowing you to unlock the security would lead to a lot of bricks and returns to stores.
[HTC EVO 3D] WatermelonSlim:
I don't need anyone to protect me from myself.

Bricks are easily fixed. We know this now that we have to brick the Evo 3D in order to get s-off. If HTC released info on this, more people would be able to fix their own bricked devices.
[HTC EVO 3D] SoraX64:
But many many many other people do. Just because you think you're competent enough to handle yourself, doesn't mean that everyone is. It baffles me that you think providing what HTC does is not enough. It gives you a way of flashing custom ROMs, and you don't have to worry about updates because HTC will make sure the method keeps working.
[HTC EVO 3D] sgt. slaughter:
Can't reason with everyone...though I agree with you compared to MOTO HTC is 100x better in the dev friendly dept...its not even a debate. If carrier is the reason for MOTO locking then why are some HTC devices unlockable on same carrier?....
[HTC EVO 3D] WatermelonSlim:
They aren't any more unlockable than the motorola devices on that same carrier. You act like you can't root or flash ROMs on a motorola device.
[HTC EVO 3D] WatermelonSlim:
If someone is comfortable trying to unlock and flash a ROM, they'd be just as comfortable unbricking their phone if HTC actually released the tools and instructions. And these tools and instructions obviously exist if a dev in the community figured it out.
[HTC EVO 3D] sgt. slaughter:
Ummm they are 100x more unlockable...HTC gift wraps it for em while MOTO devices have to wait for a root exploit...and we can flash kernels too....big diff between the two.

I'm sorry HTC has rubbed you the wrong way but the constant negativity isn't really needed over here in this section about them...
[HTC EVO 3D] WatermelonSlim:
And Motorola also releases fully unlocked devices (s-off) whereas HTC does not.
[HTC EVO 3D] sgt. slaughter:
Nice backtrack. Lol.

We were talking about one carrier not overseas or gsm devices.

You stated it didn't matter bc MOTO locked devices could get root and flash roms and it was carrier that makes them lock it down...if that's the case why are HTC unlockable on VZ while MOTO locked up? No kernel flashing on those morose like you can VIA HTC method...

Outa respect to the OP I'm done playing these games with you though. We are way off topic and its clear you want nothing to do with HTC...everyone here understands that at this point, so please stop the constant negative HTC posts...its like me going over to SGS2 and constantly saying how much I hates the device which I also own...its just poor taste to do such.
[HTC EVO 3D] WatermelonSlim:
I'm not back tracking at all. Motorola phones, which are considered locked down, are just as "unlocked" as HTC devices. Motorola also releases fully unlocked (s-off) devices, which work just fine on USA carriers. HTC does not do anything with s-off, whether you buy it from a carrier or not.
[HTC EVO 3D] snxxxxx:
Wew..

What are you talking about??
[HTC EVO 3D] PlayPetepp:
The release of ICS for E3D next year. :D

-. typewrited .-
[HTC EVO 3D] NewZJ:
you have high hopes.... next year? can HTC do it that quickly?
[HTC EVO 3D] snxxxxx:
Lol.. i just can wait until 21 dec 2012..

After that..

I would sell my phone..
[HTC EVO 3D] SoraX64:
You're like a broken record.
[HTC EVO 3D] EclipseX:
Soo verizon have confirm update for rezound and xoom....soo, ptoblably EVO 3d will het it too next month xD
[Samsung Galaxy Nexus] BruceWayne133:
So first a little bit about my phone:

It's a GSM Galaxy Nexus on Telus in Canada. It's rooted and running AOKP M4. I had just flashed Franco Kernel M2, but that's when my trouble started to I just wiped my data, reflashed AOKP M4 and restored from a back-up from before I flashed that kernel. I've never flashed a new radio.

The problem is as follows: when the screen goes to sleep, I lose signal altogether. I don't receive calls, I don't receive texts, nothing. But as soon as I wake the screen, the signal comes back (and it's strong - 3 or 4 bars so it's not a service issue).

Has anybody else had a similar problem? What's the fix?

Any help would be appreciated...thanks!
[Samsung Galaxy Nexus] warhummer:
------------UPDATE--------------

Confirmed that I had no issues after flashing back to 4.0.2 stock. Went back to stock 4.0.4 and the problem surfaced again. Tried B29 of AOKP and utilized a minimum CPU setting of 700 MHz which resulted in no issues with the phone signal after going to sleep. I was able to duplicate the problem when I set the CPU to a minimum of 350 MHz. Went back to 700 MHz minimum and everything is working fine.

I'm wondering if the stock 4.0.4, in an effort to squeeze more battery life, lets the processor speed dip down below the threshold require to keep the phone "listening".

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

I've had the same issue after upgrading my phone to 4.0.4. It started life as a 4.0.2 GSM GNex with the Samsung ICS build on it. I flashed the Google version, then manually updated to 4.0.4. I've been searching the forums and found quite a few people with the same problem, but no real solution yet. I'm going to try a few things before taking a swag at a new radio.
[Samsung Galaxy Nexus] memoreks:
I have the exact same problem

I have a GSM Samsung Galaxy Nexus on Vodafone, and within about 2 minutes of the screen sleeping, it loses connection to the network. When awakened, it will re-establish the connection within 5 seconds or so, but it is intensely irritating as I have missed lots of phone calls with this bug.

It has occurred on both my 4.0.2 patched to 4.0.4 and a clean install of 4.0.4 from google's website

I am about to revert back to 4.0.2, but if anyone can fix it in the meantime I would be eternally grateful.

-------------------------------- UPDATE ---------------------------------------------

I concur with warhummer. After rooting my Nexus again after the 4.0.4 update, and installing CPU Tuner from the Market place, I increased the minimum CPU speed to 700mhz (up from 350mhz) and it appears to be keeping its signal now. This would also tally with the fact that while my Nexus was doing things in the background it would maintain signal, but as soon as it was idle, within a few minutes the signal would die.

--------------------------------------------------------------------------------------
[Samsung Galaxy Nexus] warhummer:
I've confirmed a fix (for myself anyways) that if you can get a CPU app that can modify the processor speed, try that via the stock 4.0.4. I'm going to flash mine now.
[Samsung Galaxy Nexus] mephissto:
I have the exact same problem. I was on a Rom stock 4.0.2 with root, and after flashing the OTA, I had the problem when the screen is off.

To be sure I flashed the factory image in 4.0.4 but I still had the problem.

I looked at logcat and I had this error that seems to be the problem:

03-30 15:58:16.639 E/ConnectivityService( 186): Exception trying to remove a route: java.lang.IllegalStateException: Unable to communicate with native dameon to add routes - com.android.server.NativeDaemonConnectorException: Cmd {interface route remove rmnet0 default 10.114.222.1 32 0.0.0.0} failed with code 400 : {Failed to remove route from default table (No such process)}
03-30 15:58:16.639 E/ConnectivityService( 186): Exception trying to remove a route: java.lang.IllegalStateException: Unable to communicate with native dameon to add routes - com.android.server.NativeDaemonConnectorException: Cmd {interface route remove rmnet0 default 0.0.0.0 0 10.114.222.1} failed with code 400 : {Failed to remove route from default table (No such process)}

I'm going to send my phone to repair and hope they change it, or if someone has a solution.

Right now I flashed the 4.0.2 factory image to be able to use my phone.

PS : maybe someone know how to contact a Google dev ? To report the problem to them ?
[Samsung Galaxy Nexus] memoreks:
SetCPU fixes it

How to sort out the problem of losing signal when GNexus goes into Standby:

1. Install 4.0.4 Stock ROM

Either use the OTA patch or do a clean 4.0.4 install from the Google Stock ROMs page.

2. Root your GNexus

There's lots of info about rooting you GNexus. I used CWM to root mine.

3. Install SetCPU

4. Run SetCPU, and raise the minimum CPU speed from 350mhz to 700mhz. Then tick "Set on Boot". (see attachment)

This should now mean your phone functions perfectly well again, and you benefit from the other good stuff in 4.0.4.
[Samsung Galaxy Nexus] mephissto:
Thank you for the solution, but I don't want to achieve it that way :D for me there is a real problem with probably a hardware piece or something.

I contacted Jean-Baptiste Queru on Twitter, and he said that he will see who can talk to for this.

In the meantime, my Galaxy Nexus is going for repair in the hope I will have a brand new one :)
[Samsung Galaxy Nexus] ceejay83:
i'm having this problem too. but would it be a hardware problem? i don't remember this happening in 4.0.3. you might just be returning it for another phone with the same problem if you update to 4.0.4
[Samsung Galaxy Nexus] mephissto:
It might be a harware problem caused by a some code that was not in Android 4.0.2

I tried CyanogenMod 9 which is on Android 4.0.4 (same bootloader and radio as stock 4.0.4) but AOSP and I had the same issue.

It's really stranged because there are not a lot of people that have this issue.

Let's hope we will have news from Google soon
[Samsung Galaxy Nexus] adrynalyne:
I stopped having this problem in 4.0.2 and 4.03, when I updated to 4.0.4.
[Samsung Galaxy Nexus] ceejay83:
then that's called a software problem lol
[Samsung Galaxy Nexus] krex:
I also have exactly the same errors in logcat.

Sent from Galaxy Nexus
[Samsung Galaxy Nexus] memoreks:
I have raised a bug report with Google

I have raised a bug report with Google.

Unfortunately I cannot post a URL, so you need to go to:

code.google.com/p/android/issues/list and search for issue 28133

It might help if those of you who are experiencing this problem add comments to the post, try and raise its profile with Google somewhat.
[Samsung Galaxy Nexus] mephissto:
@ceejay83 : I know, but only a few devices have this issue, that's why I assume it's also related to hardware.

@memoreks : Thanks for the link, I'll go there to also post a comment.

---------- Post added at 11:17 PM ---------- Previous post was at 11:08 PM ----------

Here is the link to the issue on Google code : http://code.google.com/p/android/issues/detail?id=28133

Please star this issue so Google notice it :)
[Samsung Galaxy Nexus] rob61280:
I've starred the issue at the link posted, and I'm trying radio UGLC1 from the link below to see if it helps to use a newer radio.

http://xdaforums.com/showthread.php?t=1405345&page=37
[Samsung Galaxy Nexus] mephissto:
I found this thread about radios days ago, where you can find all existing radios, if you want to try others.

http://xdaforums.com/showthread.php?t=1405345
[Samsung Galaxy Nexus] nicholasbgr:
Found your thread on google code. This is what I posted there:

I have a similar issue. My phone doesn't lose signal for good, it just drops and comes back on 5 seconds later and this loop keeps repeating with random times between drops(1 minute intervals most of the time). It started right after updating to 4.0.4. I installed an app to help track when signal drops, I attached and screen of the app. I also tested with AOKP build 28 based on 4.0.3 and the problem was still there. I will test a 4.0.2 build soon.
[Samsung Galaxy Nexus] neotekz:
does it only happen in a weak 3g area? i noticed my phone having signal problems after updating to 4.0.4 too. In the secret menu, *#*#4636*#*# the preferred network type is set and stuck to wcdma preferred and if you are like me and are in a weak 3g area the phone will still prefer a weak 3g to a strong 2g signal. it prefers 3g so much that it will still hold on to it for hours even when the signal is too weak to make or receive calls. With 4.0.2 it was set to gsm/cdma prl which prefers a strong 2g but will switch when there is a strong 3g signal. unfortunately you cannot change this setting in 4.0.4.

i tried ugkl1, ugla4,, xxla2 and now using uglc1. they all had similar signal strength and will hang on to a weak 3g, so i dont think the radio is at fault here. an option for those running aokp is to go into the power saver settings and you can set your phone to go to 2g when the screen is off.
[Samsung Galaxy Nexus] quietriot84:
I have been having this issue since 4.0.3 on my GSM Nexus. I have tried multiple radio's and multiple kernels. I was having to change the min cpu to 700mhz. I tried FuGuMod's Kernel and it seems to have fixed my signal issues. I am able to keep the min cpu at 350mhz. If you search the thread he explains what he thought was causing the issue. Once he disabled that feature in the kernel my signal issues went away.

http://xdaforums.com/showthread.php?t=1438417

I think its a mix between software and hardware issues. There is some software setting that the hardware doesnt like. But since this doesnt happen to everyone running a certain kernel and only some people there must have been a bad batch of hardware from samsung.

I think I am going to try a warranty exchange with Samsung.
[Samsung Galaxy Nexus] memoreks:
For me at least, it is occurring in both 2G and 3G areas. I have tested it in both, and also in strong and weak reception areas.

Memoreks
[Samsung Galaxy Nexus] efrant:
But what I find strange is that some of us who have updated to IMM76D do not have the issue. I am using a stock yakju IMM76D ROM, which I updated from ICL53F. No issues whatsoever. I have not used any "fix" or "patch". For me, IMM76D is running just fine, with zero additional issues over and above what existed in ICL53F.
[Samsung Galaxy Nexus] @rbiter:
Some people don't have it but have touch input issues. Go figure. Could be different hw or poorly written drivers. Btw, I have hw 9 version of phone from Korea. Anybody have hw 10 from china?

bow chicka wow wow.
[Samsung Galaxy Nexus] cmstlist:
I'm not experiencing it but I am getting data stalls/drops on WIND and T-Mobile. HSPA will appear to still be connected but data just won't flow. Toggling data on/off or airplane on/off brings it back.
[Samsung Galaxy Nexus] Rodrigo Ark:
Do you updated via OTA? How you did it? I have stock 2.0.2 YAJKU and I'm still wating for the update
[Samsung Galaxy Nexus] efrant:
I updated with the update URL found in the update post in my signature.
[Samsung Galaxy Nexus] vro25:
There has to be a hardware difference - I haven't seen the issue reported on Bell phones yet, only Rogers/Telus.

Also, I swapped the battery from a working Bell model (made in Korea) with mine and I still had the issue.

Funny thing though, the issue didn't show up on first boot - I waited 5 minutes. 2nd boot it showed up right away.
[Samsung Galaxy Nexus] @rbiter:
I don't know if it mentioned in this thread or not. There is a hw 9 and hw 10 version of nexus. Korean and china respectively. Are there any more hw versions? Fastboot made tells you which version.

bow chicka wow wow.
[Samsung Galaxy Nexus] urbo83:
Is there any way to get back to 4.0.2 without rooting? I read something about ODIN, but I dont know if it can be done without root.
[Samsung Galaxy Nexus] @rbiter:
Fastboot mode.

bow chicka wow wow.
[Samsung Galaxy Nexus] vro25:
You need to be bootloader unlocked.
[Samsung Galaxy Nexus] urbo83:
Ok, I think that I will go to Samsung Service tomorrow... two weeks is to much for me :(
[Samsung Galaxy Nexus] benrees21:
Sorry I actually meant I have and still have no signal at my home as the phone mast that is about half a mile away from my home has a serious fault and Vodafone have engineers working on it, apparently. So think yourself lucky lol. :p

Sent from my Galaxy Nexus, running Slim ICS and the ever so mighty Trinity kernel.
[Samsung Galaxy Nexus] cmstlist:
HW version 9 here, no screen-sleep issues.
[Samsung Galaxy Nexus] Rodrigo Ark:
Thank you, I'll try with number 2 after google says something about that problem of lossing signal
[Samsung Galaxy Nexus] urbo83:
hw 9 with the signal lose issue
[Samsung Galaxy Nexus] @rbiter:
Any updates?

bow chicka wow wow.
[Samsung Galaxy Nexus] bobbysixkiller:
whats the best way i can get back to 402? i cant stand this any longer
[Samsung Galaxy Nexus] efrant:
http://xdaforums.com/showpost.php?p=24901578&postcount=841
[Samsung Galaxy Nexus] bobbysixkiller:
and is there anyway i can back up my apps if i have not already rooted?
[Samsung Galaxy Nexus] efrant:
You can try this: http://xdaforums.com/showpost.php?p=20868527&postcount=1
[Samsung Galaxy Nexus] rootusr:
Believe me guys, All I can say now is that Google is working on it.
[Samsung Galaxy Nexus] andQlimax:
are u a google employee? :D
[Samsung Galaxy Nexus] case0:
Missed a call for a job yesterday, really really annoying :(

I've upped the min processor speed to 700 now so hopefully that remedies the problem, but I hope it doesn't effect the battery life too much.
[Samsung Galaxy Nexus] rootusr:
That would be great but no, I'm not.

Please if you are experiencing the issue report it here http://code.google.com/p/android/issues/detail?id=28133 and star the issue. There is a procedure there to send a bugreport.
[Samsung Galaxy Nexus] @rbiter:
It will be noticeable but not too bad. Since you're waiting on phone calls for a job I would recommend using the phone less if you're a heavy user just to be sure. But you should be able to make 2h screen in a day easy if signal is not horrendous.

bow chicka wow wow.