yashsingh1/xdaforums huggingface dataset:
[HTC 7 Pro] IM0001:
Yep, the only thing I need in a custom Arrive rom is Unlock and Tethering, I believe anything else is just fluff that may in a way break the rom in one way or another. I can do any of the Reg Tweeks I want myself. (BT Audio for Video and max quality mainly).

Unlike roms of the old Windows Mobile days, the stock OS works great out of the box, so messing with things outside of the device (especially one as unique as the CDMA devices now) is not a good idea IMO until things become more standard and tested. Sadly with such little interest in CDMA devices as of yet, we don't have a lot of experience to go off of yet.

(The WiFi issue with the DFT rom is annoying but bypassable. WiFi On, Cellular Data off, Reverse when needed.)
[HTC 7 Pro] dandrayan:
Thanks for all of your hard work in creating this ROM! I was able to use it as a base for my first attempt at cooking my own WP7 ROMs. I got Internet Sharing and full unlock enabled, but the Sprint Zone app and the Marketplace both give me errors about not being able to connect and that apps cannot be installed for my carrier. Have you had any better luck adding features to yours?
[HTC 7 Pro] dwellman:
I agree.

Tethering is the mot important thing. This HTS T7575/Arrive is the first phone I've owned in 12 years (since I've started owning phones) that could not tether. It's sad. Sprint blames HTC. HTC blames Sprint. I''s actually Sprint, but c'mon. . . I digress.

My favorite ROM of the Windows Mobile days was this on http://forum.ppcgeeks.com/cdma-tp-d...om-6-5-x-23563-23138-21914-kitchen-clean.html
[HTC Sensation] stewalker:
As title is says is anyone still having the problems with sense restarting a lot. Happens mainly after exiting browser market or games. I'm using the official ics release flashed with s-off.

On a side note the browser does my head in opening the last page all the time. Is there any fix for this?
[HTC Sensation] shammanCZ:
Clearing sense cache helped by me
[HTC Sensation] Jonny:
If the phone is running low on memory (RAM) then it will kill HTC Sense process to give more memory to the game/browser that is why you have sense restarts.

On custom ROM's there us a way to always force launcher into memory therefore no sense restarts
[HTC Sensation] sshede:
Yeah, unfortunately nothing can be done about this on XDA. We can't touch stock roms unless they're rooted. You can try manually force closing smaller applications to keep the ram free, but that's about it.
[HTC Sensation] cr1960:
Make sure all apps are installed on phone instead of sd card.

You can check by going to setting>apps and selecting the sd tab.

Remove any ticks (if there are any).
[HTC Sensation] manpreetsj:
Keeping Apps on phone memory will help?? :o
[HTC Sensation] realsis:
I had this same issue when I was stock. After rooting s off and custom Rom, it never happened Again. I'm absolutely convinced that custom roms are much more stable than stock roms!
[HTC Sensation] Ojive:
I can't remember the name of the ROM i used, but it was one of the early ROMs for HTC Sensation and my phone was more unstable than stock. I used one of the first custom ROMs available for Sensation. Perhaps that's the case: too "young" rom :p
[HTC Sensation] alireza_simkesh:
how does this help?
[HTC Sensation] Jonny:
Not in the slightest

---------- Post added at 11:45 PM ---------- Previous post was at 11:43 PM ----------

It wont. If an app is loaded it is in RAM regardless of whether it is on phone memory or sd card memory, whoever said putting apps on phone memory helps is talking crap
[HTC Sensation] alireza_simkesh:
thats what i thought too.
[HTC Sensation] shetc:
This issue is the main reason I rooted my Sensation. I have been using Revolution and haven't the problem since.
[Samsung Galaxy Nexus] roriii:
Hello I just received an update to 4.0.4 on yakjuux.radio is i9250uglc1 and build number is imm48uglc1
[Samsung Galaxy Nexus] NexusDro:
Did you log the url??? That is the Canadian version, right?
[Samsung Galaxy Nexus] got_milk:
Build number looks fake. Doesn't match the standard formatting.
[Samsung Galaxy Nexus] adrynalyne:
No, it was IMM30B.
[Samsung Galaxy Nexus] got_milk:
Oh, my apologies then. I'll strike that out. :)

Just checked in as well and nothing so far.
[Samsung Galaxy Nexus] adrynalyne:
I have my doubts as well, of course. That sounds like a leak, at least.
[Samsung Galaxy Nexus] got_milk:
I agree. I'll keep an eye out as 4.0.4 would be great but I'm actually quite happy on 4.0.1 so far.
[Samsung Galaxy Nexus] roriii:
4.0.4 on yakjuux

All i did revert from yakju with nandroid 4.0.1 and then reflash original radio for yakjuux relock boot loader i got an ota saying full ota and if you want i could send a picture of my screen.
[Samsung Galaxy Nexus] adrynalyne:
Please do.

Screenshot it.
[Samsung Galaxy Nexus] iGoogleNexus:
Kinda taking forever eh? Lol

-Google Galaxy Nexus
[Samsung Galaxy Nexus] roriii:
4.0.4 yakjuux screenshot

If you need a screen shot send me ur email i will forward it to u . I don't know how to upload it from my phone thanks
[Samsung Galaxy Nexus] roriii:
4.0.4 yakjuux screenshot

If you want a screen shot send me ur email i am away from my desktop i am not sure how to post a screenshot but i could email it to you
[Samsung Galaxy Nexus] got_milk:
Yeah. I won't buy it until I see a screenshot.
[Samsung Galaxy Nexus] virtualcertainty:
Always assume good faith. :)

I recall a while back a guy here reported an OTA, apparently a limited test run of some non-yakju build. There was nearly a lynch mob calling for his head because no one could back up his claim. Until days later when it arrived for everyone else exactly as he described.
[Samsung Galaxy Nexus] got_milk:
Send it to f148617@rppkn.com - it's a 10minutemail address. I'll post it for everyone on your behalf.
[Samsung Galaxy Nexus] dipdeol:
I'm not calling OP a liar, but I would suggest people be a little extra sceptical for the next day and a bit with April 1st just a couple of hours away. I've already seen at least one obvious hoax online today.
[Samsung Galaxy Nexus] got_milk:
I agree. But if OP has a screenshot he's willing to share I'm listening, for now.

---------- Post added at 08:48 PM ---------- Previous post was at 08:04 PM ----------

OP hasn't emailed a screenshot to that email address so I'll let it expire in 10 minutes or so, giving it a full hour. If OP still wants to share the screenshot, I suggest grabbing the imgur for Android app and uploading it via that, then sharing the link.

---------- Post added at 08:52 PM ---------- Previous post was at 08:48 PM ----------

Okay, OP attempted to email screenshots but both emails contained no attachments or screenshots...I emailed him back suggesting he use the imgur for Android app like I suggested above. I'll keep the address open a little while longer just in case he emails me the link(s) instead, in which case I'll pass them along.

---------- Post added at 08:54 PM ---------- Previous post was at 08:52 PM ----------

OP just let me know that he will be uploading the screenshots via his PC in a few minutes.

---------- Post added at 09:16 PM ---------- Previous post was at 08:54 PM ----------

OP just sent me the screenshots:

Looks very legitimate to me.
[Samsung Galaxy Nexus] anton2009:
That does look very legitimate. :)
[Samsung Galaxy Nexus] roriii:
4.0.4 yakjuux ota

guys if you need anything from me to upload i will do it even if you want a nandroid backup i could unlock my boot and do a nandroid back as well let me know thanks .
[Samsung Galaxy Nexus] got_milk:
Just curious, is the option for NFC back in the settings? With the 4.0.2 OTA it was reported the option had disappeared.

Also, is the market/Play Store working correctly?
[Samsung Galaxy Nexus] Scottatron:
Strange that the build number is older than the Yakju release.

Can't wait to try the different radio though :) as I found the UG version to work very nicely.
[Samsung Galaxy Nexus] roriii:
Still no NFC in the setting menu
[Samsung Galaxy Nexus] adrynalyne:
The build.prop please.

adb pull system/build.prop and then upload it somewhere.
[Samsung Galaxy Nexus] jonnyg1097:
hmm if this is legit then perhaps its time for me to flash back to stock yakjuux and let it update to 4.0.4 that way...

although im on stock 4.0.4 yakju now (via factory image) and its working quite well so I guess its not needed....

decisions...decisions...
[Samsung Galaxy Nexus] roriii:
sorry to ask you i am using tool kit , can i get the adb build using tool kit .

thanks let me know .
[Samsung Galaxy Nexus] Hwaiting:
Does one still get OTA updates with a custom recovery like cwm flashed or does everything have to be stock?
[Samsung Galaxy Nexus] roriii:
all i know you have to be stock including the right Radio to be able to install update via ota .if not you will get failed when trying to install the update .
[Samsung Galaxy Nexus] ArmanUV:
OP needs to upload the radio. uglc2 is very new.
[Samsung Galaxy Nexus] roriii:
is there a Radio uglc2 .i have uglc1 .
[Samsung Galaxy Nexus] matthewr87:
I can confirm that 4.0.2 is missing the NFC and android beam options from the menu. I just saw my cousin's phone today. He randomly received a 4.0.2 OTA notification two weeks ago on Telus in Toronto.

Seems weird that 4.0.4 is still missing NFC. Is the yakju build missing NFC as well?
[Samsung Galaxy Nexus] dipdeol:
There was a problem with the 4.0.2 OTA for yakjuux. Doing a factory reset restored the NFC options. This was well documented at the time of the OTA, and I can confirm that a factory reset fixed NFC as well as the market problems at the time.
[Samsung Galaxy Nexus] roriii:
yakju the NFC is available in the setting on the 4.0.4 but not on the yakjuux 4.0.4
[Samsung Galaxy Nexus] roriii:
i did trimmed the new Radio uglc1

hello how i could upload the new radio from yakjuux uglc1 .

let me know and i will upload it .

thanks
[Samsung Galaxy Nexus] roriii:
build prop as you request yakjuux 4.0.4

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=IMM48

ro.build.display.id=IMM48.I9250UGLC1

ro.build.version.incremental=I9250UGLC1

ro.build.version.sdk=15

ro.build.version.codename=REL

ro.build.version.release=4.0.4

ro.build.date=Wed Mar 7 20:04:22 KST 2012

ro.build.date.utc=1331118262

ro.build.type=user

ro.build.user=se.infra

ro.build.host=SEI-29

ro.build.tags=release-keys

ro.product.model=Galaxy Nexus

ro.product.brand=samsung

ro.product.name=yakjuux

ro.product.device=maguro

ro.product.board=tuna

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.manufacturer=samsung

ro.product.locale.language=en

ro.product.locale.region=US

ro.wifi.channels=

ro.board.platform=omap4

# ro.build.product is obsolete; use ro.product.device

ro.build.product=maguro

# Do not try to parse ro.build.description or .fingerprint

ro.build.description=yakjuux-user 4.0.4 IMM48 I9250UGLC1 release-keys

ro.build.fingerprint=samsung/yakjuux/maguro:4.0.4/IMM48/I9250UGLC1:user/release-keys

ro.build.characteristics=nosdcard

# end build properties

#

# system.prop for maguro

#

rild.libpath=/vendor/lib/libsec-ril.so

rild.libargs=-d /dev/ttys0

telephony.lteOnCdmaDevice=0

# Ril sends only one RIL_UNSOL_CALL_RING, so set call_ring.multiple to false

ro.telephony.call_ring.multiple=0

#

# ADDITIONAL_BUILD_PROPERTIES

#

ro.com.android.dateformat=MM-dd-yyyy

ro.com.android.dataroaming=false

ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html

ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html

ro.com.google.clientidbase=android-google

ro.error.receiver.system.apps=com.google.android.feedback

ro.error.receiver.default=com.samsung.receiver.error

ro.setupwizard.mode=ENABLED

ro.setupwizard.enterprise_mode=1

ro.config.ringtone=Girtab.ogg

ro.config.notification_sound=Proxima.ogg

ro.config.alarm_alert=Cesium.ogg

keyguard.no_require_sim=true

drm.service.enabled=true

wifi.interface=wlan0

wifi.supplicant_scan_interval=15

ro.opengles.version=131072

ro.sf.lcd_density=320

dalvik.vm.heapstartsize=8m

dalvik.vm.heapgrowthlimit=64m

dalvik.vm.heapsize=256m

ro.com.google.gmsversion=4.0_r1

dalvik.vm.dexopt-flags=m=y

net.bt.name=Android

dalvik.vm.stack-trace-file=/data/anr/traces.txt
[Samsung Galaxy Nexus] adrynalyne:
Its old enough that the kernel isn't even the latest version. Last commit to the kernel was March 13th.
[Samsung Galaxy Nexus] roriii:
i was getting this update almost 2 weeks ago but failed to install till i did reflash my nandroid back up and reflash the ugkl1 and relock the bootloader and today took the update it was a big update and on the ota was message ( full ota ) my phone was 4.0.1 on yakjuux i was thinking the 4.0.2 but i was surprise when i saw the 4.0.4 with new radio uglc1 . this was never released why only me no one did mention anything about this build .
[Samsung Galaxy Nexus] roriii:
i tried the yakjuux 4.0.4 build it is still laggy but the yakju 4.0.4 way better than the yakjuux .so i will go back to yakju 4.0.4 with the Radio ugla2 for know i wasn't impress with the radio uglc1
[Samsung Galaxy Nexus] Mwinggg:
April fool joke??
[Samsung Galaxy Nexus] zolah:
Awwww u beat me!!!! I was just about to point that out!
[Samsung Galaxy Nexus] efrant:
You need to have root.

Plug into a computer and open a command prompt:

adb shell

su

did bs=256 count=49153 if=/dev/platform/omap/omap_hsmmc.0/by-name/radio of=/sdcard/radio-uglc1.img

exit

exit

adb pull /sdcard/radio-uglc1.img
[Samsung Galaxy Nexus] efrant:
Can you also try looking in this file and see if the OTA download link is there: /data/data/com.google.android.gsf/shared_prefs/update.xml
[Samsung Galaxy Nexus] dendirk:
I wonder why everyone is telling that the yakju versions get the update first.

This one is a yakjuux version, i guess all versions getting the update from Google and not Samsung.
[Samsung Galaxy Nexus] geemaan:
The yakju?? variants have additional localization files added by samsung that's why they are pushed later by google.
[Samsung Galaxy Nexus] dendirk:
i did not asked for localized versions.. besides there are also yaku only versions in Belgium.
[Samsung Galaxy Nexus] virtualcertainty:
Don't know about that. Assuming this is real, and if the the kernel is older than in the yakju release, it might just be that this was an accidental release/leak. The build date is one week after yakjuux broke a bunch of phones. So the decision might have been made, since this was so close to another major release, to skip 4.0.2 and let Samsung bug fix with a 4.0.4 pre-release. This is all wild speculation on my part. Either way I'm doubtful this yakjuux OTA is in the pipe for a wider population just yet.
[Samsung Galaxy Nexus] Smallsmx3:
Can u post the radio since its newer than ugla4
[Samsung Galaxy Nexus] efrant:
Yakju does get updated first. (This does not mean all devices running yakju will be updated before the first non-yakju device receives an OTA.) The yakju build update was available before yesterday.
[Samsung Galaxy Nexus] efrant:
All non-yajku builds are localized: yakjuux is north America, etc
[Samsung Galaxy Nexus] roriii:
Radio for uglc1 from yakjuux

i did trimmed the Radio from my galaxy nexus yakjuux 4.0.4

here is the link . did not had great success with this radio but maybe for other could be helpful.

http://www.mediafire.com/?v10pmeyfe6pmz5j

thanks
[Samsung Galaxy Nexus] efrant:
Thanks.

Did you get a chance to look in this file to see if the link for the OTA update is available: /data/data/com.google.android.gsf/shared_prefs/update.xml
[Samsung Galaxy Nexus] Smallsmx3:
Is this via cwm or fastboot
[Samsung Galaxy Nexus] efrant:
Fastboot. I've packed it for CWM and posted it here.
[Samsung Galaxy Nexus] Wolfglance:
Hi All,

anyone tried the UGLC1 radio yet ?

Thank you,
[Samsung Galaxy Nexus] cmstlist:
I've tried it on yakju 4.0.4

WIND Mobile: As good/bad as it ever is. I'll see if I get any signal dropouts, can't comment yet.

Bell (via PC Mobile SIM): 7037 kbps down, 2977 kbps up. Pretty decent.
[Samsung Galaxy Nexus] roriii:
more screenshot about update for yakjuux 4.0.4

http://roriii.imgur.com/all

i have a question how i can pull out the ota update link from my phone .
[Samsung Galaxy Nexus] cmstlist:
If you already did the update you probably can't get the link anymore.
[Samsung Galaxy Nexus] efrant:
Try this and see if you can find it. Otherwise, the only way to get it is to restore a pre-4.0.4 nandroid backup, and then follow the instructions here.
[Samsung Galaxy Nexus] efrant:
Here it is. Thanks a lot.

http://android.clients.google.com/p...yakjuux/0ce2bc924e74.update_yakjuux_IMM48.zip

P.S. This looks like a full update, so it should update ITL41D, ITL41F and ICL53F to IMM48.
[Samsung Galaxy Nexus] roriii:
the weird issue i only get this update on 4.0.1 yakjuux nandroid if i do wipe i will never get this notification .
[Samsung Galaxy Nexus] Hwaiting:
Thanks to the OP and Efrant for the link.

Whether this is a full update or not, I take it the steps to update are the same as in your OTA thread?
[Samsung Galaxy Nexus] roriii:
thanks for your help efrant
[Samsung Galaxy Nexus] efrant:
Yes, use the same steps that are in the OTA thread. The difference (and I haven't had a chance to download it yet, but judging by the size I can get a pretty good idea) in this case is that you can use it if you are on 4.0.1 or 4.0.2, and it will upgrade you. The other updates I had posted are incremental updates, so they only work on one specific build version.
[Samsung Galaxy Nexus] Hwaiting:
Thanks, I downloaded it and it was 186MB. Will try updating now from 4.0.1...

Update: now on 4.0.4. After the update, no NFC as the OP mentioned. Tried a factory reset thinking NFC would come back like how people said on 4.0.2 but it's still not there.
[Samsung Galaxy Nexus] roriii:
Just keep in mind no NFC in this build
[Samsung Galaxy Nexus] guyb99:
ignorant noob question but do we know why NFC has gone AWOL?
[Samsung Galaxy Nexus] cmstlist:
Interesting to compare it to the yakju URL.

http://android.clients.google.com/p....signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip

Google Maguro, versus Samsung Proxima.

Proxima, perhaps because of its proximity to being a Google phone without actually being one? :-P
[Samsung Galaxy Nexus] adrynalyne:
When you lose the option to enable or disable it.
[Samsung Galaxy Nexus] adrynalyne:
Its a Samsung supplied update branch.
[Samsung Galaxy Nexus] cmstlist:
I snooped inside the update script. I don't see any conditions whatsoever that restrict which bootloader, radio etc you need to be running. It just formats the system partition and extracts, and then flashes bootloader and radio.
[Samsung Galaxy Nexus] efrant:
Yup, your right, there are no checks so, technically, anyone on any build can use it to "update" to yakjuux IMM48.

But you are mistaken though, there is NO bootloader included.
[Samsung Galaxy Nexus] guyb99:
So is it permanently ON in this new build or permanently disabled?
[Samsung Galaxy Nexus] adrynalyne:
I don't know. I just know how to diagnose it. Usually if its missing, its off.
[Samsung Galaxy Nexus] roriii:
i did not tested it because i don't have another nexus or a phone with NFC built in all i could say if someone could try it and report it could be helpful .

thanks
[Samsung Galaxy Nexus] cmstlist:
Oops I saw boot.img (kernel) but for some reason I remembered it as bootloader.

This also means that restoring for warranty purposes is easier than ever - wipe data, flash this zip in recovery, then flash stock recovery from bootloader and relock.

Interesting to note: no bootloader means that anyone who got the direct OTA from 4.0.1 to 4.0.4 still has bootloader PRIMEKK14. Anyone who got 4.0.2 first and then 4.0.4 - they have PRIMEKK15.
[Samsung Galaxy Nexus] mopardroid:
How do you install this update? Flash it... I am on yakjuux 4.0.2
[Samsung Galaxy Nexus] cmstlist:
Umm there was no leaked OTA 4.0.4 for the GSM Galaxy Nexus any earlier than last week. Only Verizon.

Original yakjuux units that shipped with 4.0.1 had bootloader

PRIMEKK14

.

The 4.0.2 yakjuux OTA upgrade included

PRIMEKK15

.

The 4.0.4 OTA zip contains no bootloader at all, so you keep whatever you had.
[Samsung Galaxy Nexus] elpatolucas:
True, the leaked OTA 4.0.4 was for the CDMA version and included bootloader PrimeLA03.

So no new version in this OTA?
[Samsung Galaxy Nexus] cmstlist:
Right. The only bootloaders you should see on unmodified yakjuux devices are KK14 and KK15.
[Samsung Galaxy Nexus] Hwaiting:
It looks like the no options for NFC means it's disabled. I tried doing android beam to my friends Galaxy Nexus on 4.0.2 (which also has no NFC options) and nothing happened.
[Samsung Galaxy Nexus] g8who:
I just flashed it yesterday afternoon so I've only had it a day so nothing is definitive. But so far I've tested it using speedtest and at my office I use to consistently get 5000-6000 kbps down and and 1200 up but not I only get 2000-3000 down and 600 up. As for the signal strength, there is this one spot in my parking garage where I usually get 1 bar but never loses signal. Now I have no signal at all. Will monitor a few more days but will probably reflash to the old radio.

Anyone else have the same experience?

---------- Post added at 03:00 PM ---------- Previous post was at 02:48 PM ----------

I'm pretty new to all this rooting and bootloader stuff so pardon my ignorance but are there a lot of differences between the bootloaders?
[Samsung Galaxy Nexus] vro25:
Radio problems on yakju 4.0.4

Just an fyi, I took my Telus Nexus (used on Rogers) from yakjuux to yakju by flashing the 4.0.2 stock image on android.com and then upgrading to 4.0.4 - it was a disaster. 4.0.2 worked great, but 4.0.4 loses it's cellular signal when the screen goes to sleep. Not only do you loss cell service, but the battery was draining at 6% an hour as the phone was constantly searching for signal. I tried multiple different radios but nothing worked. I ended up going back to 4.0.4.

Now I'm going to restore to a Wind yakjuux build and try to upgrade to this 4.0.4 without updating the radio - which is perfect atm - and see if that works...
[Samsung Galaxy Nexus] jdwright45:
I would disagree with the above post.

I have a Telus Nexus that I moved from Yakjuux to Yakju 4.0.1. Then got the OTA to 4.0.2. I upgraded to 4.0.4 this weekend by downloading the update.

Everything works. It is definitely an improvement from 4.0.2. Much smoother, white is now more white on the screen, faster camera loading, new power menu, etc.
[Samsung Galaxy Nexus] cmstlist:
Not sure what you are experiencing but it could be some kind of idiosyncratic fluke. I do know that after changing ROM or radio, my device seems to require some coaxing to first catch onto a signal, but I've never seen an issue where signal drops long-term when asleep.
[Samsung Galaxy Nexus] efrant:
http://xdaforums.com/showpost.php?p=23305473&postcount=195
[Samsung Galaxy Nexus] vro25:
So I upgraded to this version of 4.0.4 and I'm still experiencing the same issue...

It's great that everything is working for you. The main difference between Telus and Rogers is a 2G network. I wouldn't be surprised if the phone is trying to be smart and latch on to the 2G network when it's asleep and is somehow getting stuck. Also my upgrade path was a little different by I don't think that would be the issue. Aside from the radio issue everything is fast and stable - the camera is especially better - and no more long delay when activating the camera from the lock screen!

My phone doesn't have an issue when using any other ROMS or radios - only ones putting me on 4.0.4.

I saw that when I was debugging on Saturday and it didn't help. Tried again now with no luck. I've tried different radios, just tried xxkk6 and it don't help either.

Thanks anyway for the suggestions!

**Update**

Upon restoring my device back to 4.0.2 on yakju I was greeted with a system update notification. Not sure how it would be any different than a manual update, but we'll see how it goes!

**Update**

I md5'd the upgrade file and as efrant suggests below, it was the same as the one I tried to patch manually. It actually didn't work as I got a verification failure.