yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] zonyl:
Im pretty sure the Note has Samsung memory. Kinda of a relief because I was worried about the rainbow bubble guy.
[AT&T Samsung Galaxy Note I717] KillaHurtz:
Quite possibly the dumbest 4 minutes I have ever endured.
[AT&T Samsung Galaxy Note I717] cbass:
I see you've never watched a state of the union address...
[AT&T Samsung Galaxy Note I717] animeware:
Dumb commercial I don't see why this topic was posted on the Note Forum.

It has nothing to do with the Note......
[Android Q&A, Help & Troubleshooting] kkoolerter:
hei,guys,how to port CyanogenMod to FriendlyARM Tiny6410 board???:)
[Motorola Droid RAZR] marculous:
over the last few weeks I've noticed that when playing the next track the signal sometimes doesn't go through. If I pause then play it comes back on. using razr with dynex cable and logitech speaker. anyone else have this or a similar problem?

droid razr stock un- rooted .181 waiting for official ics...
[Motorola Droid RAZR] thunderknob:
G'day,

May not be related but my headphone jack got stuffed up with lint a couple of times and I had to dig it out gently with a pin.

does it happen without use of the headphones jack? cause if it's only with the use of the jack, it might just be the connection being unreliable.
[Motorola Droid RAZR] [x]:
Actually. I'm not sure if this relates, but I've had headphone jack issues. I'm on my second Maxx, and this one has same issues. Slight touches to the headphone jack while plugged in causes the music to stop playing (as if they were pulled out). It's not the headphones because I'm actually using hotspot to my Razr and listening to my music via the Charge.

Sent from my Droid Razr Maxx
[Motorola Droid RAZR] marculous:
thanks to both of you, I will investigate your tips

droid razr stock un- rooted .181 waiting for official ics...
[HTC Sensation] claudiuslu2011:
i have a sensation 4g from tmobile that has never been root, and it was update to ics recently thru OTA update. i follow this guide http://xdaforums.com/showthread.php?t=1632553 to root my phone.

currently phone status as follow

unlocked

pyramid pvt ship s-on rl

hboot-1.27.0000

then i download cyanogenmod 9 and flash it to my phone from my sd card through recovery, after restart the phone is stuck at cyanogen boot animation screen. did i miss some steps before i flash the custom rom?? please help.
[HTC Sensation] Nescar:
Do you flashed the ICs Firmware? You shold Do that if you missed it :-) maby it work :-)
[HTC Sensation] claudiuslu2011:
I did not do that, can u point me to a guide on how to do it
[HTC Sensation] realsis:
Here is the link to flashing 3.32 firm wear hope this guide helps! I searched and found this. I think it talks about other things too but the firm wear guide should also be included. I really hope this helps

Read first to make sure this is what your looking for.

http://xdaforums.com/showthread.php?p=26319379. sent from my HTC Sensation Z710e using xda premium
[HTC Sensation] elyts:
Flashing the correct firmware is not a big deal. Just download the correct file (you can find the version number somewhere in the thread of the rom) and flash it via 4ext recovery.
[HTC Sensation] yahhboy:
No its flashed via fw, make sure you use one with the correct cid :rolleyes:

Sent from my sensational sensation 4g
[HTC Sensation] MarlinFF:
Flashing the firmware is REQUIRED.. How is it not a big deal?
[HTC Sensation] valefour:
If he updated to ICS then unlocked wouldn't the firmware already be the 4.32? If not, then do that.

Did you use super wipe before installing? Correct me if I'm wrong but aokp and cm is not compatible with super wipe but needs to use recovery's wipe all data option before install?
[HTC Sensation] dwaynedman:
This should work perfectly fine on any ver. of ICS.

Make sure to wipe cache and super wipe / factory reset after installing Cyanogen.

You may get stuck on boot screen still.

Just power down into CWM and wipe cache and data again then reboot,

Works flawless for me on 4.03

Thanks please
[Motorola Droid RAZR] mattlgroff:
So... a lot of us are stuck on a certain firmware and need to get off of it. A solution to us all (hopefully), is a program called "bspatch" (usually comes with bsdiff). We have a boot.img file (compiled android img) and a boot.img.p (from an OTA update, zip, which we know 100% works and people have updated with the OTA zip).

We need bspatch to stop checking for corruption like it does now and to just force the patch to go. This would help save a lot of users stuck on firmware and we would all appreciate a point in the right direction.

We tried compiling the source of bspatch from many sites, but none seem to compile correctly or even run. We get them to run from binary pre-compiled versions, but those won't help us since it sees the patch as corrupt.

If we can get boot.img from the 6.12.181 fastboot files to patch with the boot.img.p from an ICS like the most current (6.16.206 as of 5/20/2012) we can make a fastboot files that is flashable onto someone stuck on 6.14.84 so they can upgrade to 206 with Moto Recovery.

Also if this magically can be done by the help of the XDA community, we can create a boot.img from 6.12.181 patched with a 4.0.3 boot.img.p (like from 84 or 85, since 79 and below aren't flashable on newer ICS), we can also have a root method for 4.0.4 like the GSM users have.

Best of luck to those who try to help with this!

http://www.daemonology.net/bsdiff/

https://launchpad.net/ubuntu/+source/bsdiff/4.3-10ubuntu1/+build/2960721

Files(s): http://rombot.droidhive.com/ROMs/spyder/BspatchProject.zip

alt link: http://www.filefactory.com/file/1xj6eh1mocz7/n/BspatchProject_zip

Note: My friend tried this already and we got Pre-flash validation errors when trying to fastboot it. Just throwing this idea out there.... best of luck.

EDIT: Added as an attachment.

Thanks to dhacker29 for trying this idea out first :D
[Motorola Droid RAZR] whirleyes:
Err.. Doesn't the /system/bin/applypatch can do this already??

I've always used it to patch OTA manualy..

example usage:

applypatch boot.img boot_new.img [B]X Y Z[/B]:boot.img.p

where

[B]X[/B] is the target(boot_new.img) sha1sum
[B]Y[/B] is the target(boot_new.img) new size
[B]Z[/B] is the source(boot.img) sha1sum

Obviously it will failed the cert test,

if the patch(boot.img.p) is not intended for the base(boot.img)

Information can be extracted from OTA update-script

example

X = 2997ddb421e1d44b026410339e343f60b3bb65bd

Y = 8388608

Z = 5fff8425560eb1002b467062de2b355b45090ad7

easily done via adb

adb.exe push boot.img /tmp/
adb.exe push boot.img.p /tmp/
adb.exe shell /system/bin/applypatch /tmp/boot.img /tmp/boot_new.img X Y Z:/tmp/boot.img.p
adb.exe pull /tmp/boot_new.img
[Motorola Droid RAZR] SilentViper:
I can confirm that applypatch does have at least some success in patching a boot.img once you can figure out the information required from updater-script found in the OTA you are trying to make fastboot images for. I patched the file obtained by

dd if=/dev/block/mmcblk1p14 of=/sdcard-ext/b/boot.bin

on a 6.12.181 successfully using the code

applypatch ./boot.bin ./boot.bin.2 dd9310794842a4908aff55979a9fe97f825e8748 8388608 8e21cfa5d9be4dd08427b079fbff9a80d6e04560:boot.img.p

the code i ripped apart from 6.16.206 is

assert(apply_patch("MTD:boot:8388608:8e21cfa5d9be4dd08427b079fbff9a80d6e04560:8388608:dd9310794842a4908aff55979a9fe97f825e8748",
"-", dd9310794842a4908aff55979a9fe97f825e8748, 8388608,
8e21cfa5d9be4dd08427b079fbff9a80d6e04560, package_extract_file("patch/boot.img.p")));

to figure out the apply patch code i looked at the info above and compared it to this

[qoute]adb shell applypatch

usage: applypatch <src-file> <tgt-file> <tgt-sha1> <tgt-size> [<src-sha1>:<patch> ...]

or applypatch -c <file> [<sha1> ...]

or applypatch -s <bytes>

or applypatch -l

Filenames may be of the form

MTD:<partition>:<len_1>:<sha1_1>:<len_2>:<sha1_2>:...

to specify reading from or writing to an MTD partition.[/quote] and with a little trial and error got it to work :D

EDIT

Let me be clear the patched boot.bin.2 does flash perfectly fine. no preflash validation failure.

Anyone on 6.16.206 want to do me a favor and do?

dd if=/dev/block/mmcblk1p15 of=/sdcard-ext/b/recovery.bin

and email/upload it to me? I'll hit the thanks button :) </bribe>
[Motorola Droid RAZR] mattlgroff:
I asked on the DroidRZR thread for 6.16.206 if anyone could do it, let's see :D

Edit: By the way which version boot.img is patched and flashable, and could we get a copy?
[Motorola Droid RAZR] dimitri407:
This is what a user at DroidRzr got when he tryed:

dd if=/dev/block/mmcblk1p15 of=/sdcard-ext/b/recovery.bin

[quote name='Fixter' timestamp='1337690349' post='46825']

Doing it right now Matt.

PS: Cannot Open for Read: Permission Denied

Also, I have root. Let me check now. I forgot to restore root.

Update 2: Cannot Open for Write: No such file or Directory. I copy pasted it, so I know it's right.

[/quote]
[Motorola Droid RAZR] SilentViper:
[/QUOTE]

He might need to do

mkdir /sdcard-ext/b
[Motorola Droid RAZR] mattlgroff:
He might need to do

mkdir /sdcard-ext/b

[/QUOTE]

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

Recovery.bin from DR user Fixter from 206.

Enjoy!
[Motorola Droid RAZR] xlightwaverx:
[/QUOTE]

Finally, some headway,

But I have a question is in regards to the DD command (kinda off topic but not really). How do you know that p15 is associated with recovery.bin, well at least for Droid Razr XT912-Verizon. I have some tools that show symlinks in an android file browser, but I am looking for a Linux command as well.

Been trying to find access to the devtree partition as well as cdrom, recovery, cdt.bin (p18=true), and now in this case, boot. I found all but devtree. Any ideas,

X
[Motorola Droid RAZR] cellzealot:
Open the recovery.img in a hex editor and the partitions are listed at the top.
[Motorola Droid RAZR] SilentViper:
AWESOME. I successfully flashed that to my secondary razr that i am playing with these updates on. I used this plus my custom patched boot.bin.2 to successfully boot into recovery. but im currently stuck there because no OTAs will flash from that, and my /system partition isn't the right version, nor anything else for that matter. now I need the rest of the /dev/block files from 206 :/

i'm going to have to figure something out quick
[Motorola Droid RAZR] TheLoonyRebel:
Couldn't you just extract the files from the .206 zip file that you need? Unless if I am missing something of course... just one thought I had on this.
[Motorola Droid RAZR] SilentViper:
No, those are patch files. To make a fastboot package I need the block dumps
[Motorola Droid RAZR] TheLoonyRebel:
Makes sense. Hopefully someone running .206 could provide that to you. Sadly I'm unable to as I'm on .203 on my RAZR. Bummer. :(
[Motorola Droid RAZR] mattlgroff:
Project Success.

http://www.droidrzr.com/index.php/t...m-icsbut-not-back-to-gb-6148485-616203204206/

Great job to everyone involved!
[Motorola Droid RAZR] SilentViper:
Awesome! mind posting just the fastboot commands? I tried interpreting the .bat but haven't had much experience with .BATs and am not entirely sure what you are doing
[Motorola Droid RAZR] jamminjon82:
Not anymore you're not!

Sent from the bottom of my fart
[Motorola Droid RAZR] [TSON]:
SEMI success. We wanna get us back on the path, not on a later ICS build. This might be okay if it works with the OTA, but...
[Motorola Droid RAZR] jamminjon82:
Why wouldn't they be able to use this strategy again and use img file from official ota?
[Motorola Droid RAZR] [TSON]:
Knowing Moto...
[Motorola Droid RAZR] jamminjon82:
I feel like update is pretty close . I would be impressed if they patched it that quickly
[Motorola Droid RAZR] mattlgroff:
"fastboot flash boot boot206.img" or "fastboot flash boot boot85.img"
[Motorola Droid RAZR] SilentViper:
Knowing the methods Matt used, and that updates use the same applypatch method update.zip uses. They would have to change pre existing releases to patch this method

Edit: thanks Matt!
[Motorola Droid RAZR] xlightwaverx:
So, now that all the stuck ones can go up, and eventually leave GB for good and be solely on ICS, are we done? I kinda feel the need to keep working on an ICS2GB method.

Essentially, whatever version your boot.img is, you can install (by force) whatever build that the boot.img is from. If you are on .84, and you want to go to .85, you would have to patch .181GB-boot.img with .85ICSboot.img.p, flash new boot.img, proceed with recovery (by force) of .85. .84 cannot go to .85 and vice versa unless you issue a new boot.img.p patch off of original .181GB-boot.img and then proceed with that ota version recovery install correct?

Now, if u wanted to go backwards, is this where the CDT.bin file would prevent you from doing that? Because if we fastboot a .181 boot.img, it seems to take fine correct? The only issues are cdt.bin, devtree, cdrom, and recovery.

So since we successfully bypassed the CDT.bin preflash validation by copying (DD) a .181GB mmcblk1p18 to (whatever version of ICS leak you're on), rebooting in to fastboot, and flashing old cdt.bin, no issue arrises.

Now, once at that stage when we (by force) fastboot .181 GB files on after replacing cdt.bin, we receive customer ID error on boots, but cdt.bin is flashed, so customer id error keeps popping up because of the other 3 partitions being mismatched (devtree, cdrom, recovery?) I'm thinking out loud...

So, we if DD .181 cdt.bin (p18) along with recovery, devtree, and cdrom, reboot into fastboot, would the .181 fastboot files then be able to pass preflash validation? At that stage, force OTA update of .181GB over passed validated partitions, and then we would have a full 181 OTA install?

I understand the concept of having a locked bootloader, but when we DD these images out of .181GB, wouldn't these images retain their signature? Phew, that's a lot of typing, and then again, thinking out loud.

X
[Motorola Droid RAZR] SilentViper:
Logically and theoretically what you are saying makes sense. I was going to try that first chance i get. Since i just realized that i have the fastboot screen burned in I'm more willing to screw with my second phone
[Motorola Droid RAZR] xlightwaverx:
Bump!
[Motorola Droid RAZR] Q9Nap:
So does the no corruption bspatch posted in the op make a flashable boot.img? i used it to patch the bionic 5.9.905 boot.img with boot.img.p from the latest 6.7.235 leak and it does create a file; however the new boot.img is different than the boot.img included in matt's DroidBionicUnstuck.zip utility. I know i can just use the image from this utility, but want to have the technique ironed out for future reference.

is the method from this post...

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

...still the only way to successfully patch boot.img?
[Motorola Droid RAZR] mattlgroff:
The stickied method thread by myself for patching boot.IMG is the only way I know of.
[Galaxy S II I9100G Android Development] projectrally:
I've done some searching on this, but so far nobody's problem seems to match up with mine. Any help would be much appreciated!

I bought my wife and I both international Galaxy phones to use on AT&T's network. I have a Galaxy Note, and my wife has a GS2-G. My phone is super stable, but my wife's phone will regularly drop all cellular connectivity with no warning. About once a day or so, it just drops everything. Wifi will still connect, but the phone can't text, make calls, or get data. The signal bars are replaced with a circle with a slash through it. This doesn't happen when we're moving from cell to cell. It often happens while she's at work (in the same building all day), and this weekend it happened twice at home. We have great reception at our house, too.

Her phone is setup using the APN settings for a "medianet" phone, found here: http://xdaforums.com/showthread.php?t=1196118.

Otherwise, it's running stock 2.3.6 baseband XXKL4.
[Galaxy S II I9100G Android Development] JROppenheimer:
i am experiencing similar problems.losing signal totally without any hint.

not once a day but sometimes it happens to me also.
[Galaxy S II I9100G Android Development] ad_ek:
i too have this problem. i too sit in the office the whole day. same spot. and this happens frequent enough to piss me off. i raised this issue several times in other discussions, and they keep saying its probably network issue or a faulty phone.

1. i use this same network on my previous phone (iphone), and its fine

2. i cant just send it for warranty cause they will keep the phone for a week or 2 to troubleshoot. so i dont want to be without the phone for that period of time without knowing for sure its a faulty phone.

since i see quite a few people going through and thanks to projectrally, i hope we can all narrow this problem down to what may be the cause, and take necessary action.

---------- Post added at 03:07 PM ---------- Previous post was at 03:05 PM ----------

i have tried flashing diff roms, modems, kernels. i have disabled fast dormancy, and problem still persist.
[Galaxy S II I9100G Android Development] Xialis:
Got this problem yesterday for the first time :( , I had to reboot.

When the problem occured, i tried to find network but the phone kept searching...
[Galaxy S II I9100G Android Development] ironman123:
...

Same problem here! I think all we can do is wait for the ics update.

That should fix it...

P.S: It usually happens when im running low on battery...
[Galaxy S II I9100G Android Development] ad_ek:
im still not sure if its a software or hardware issue
[Galaxy S II I9100G Android Development] tesh94:
yup i have the same prob to sometimes..after rebooting the phone it works jst fine.. but its quite annoying rebooting the phone when it happens :(

but it doesn't happen so often as u all described.. mayb once or most twice happens to me in a day ...
[Galaxy S II I9100G Android Development] Garrafone:
Maybe its a hardware problem, LG Optimus 3D has also this problem of "ghost calls" and have the same hardware (TI OMAP 4430)
[Galaxy S II I9100G Android Development] mmdixit:
After ICS update i am facing the same problem. Before i read this thread, i thought it is a software bug but now it seems to be a hardware problem.
[HD7 General] sirajgoku:
Go to this key: [HKEY_LOCAL_MACHINE\Software\OEM\KeyState]

Then add this value: "application_btn_vibrate3"=dword:1

to add the value, go to settings in registry editor in the described directory and choose "new value"

valuename: application_btn_vibrate3

value data: 1

value type: Dword

This will disable the vibration for the three touch keys ( back,home,search) and increase the battery life significantly.... If u want the vibration back then just change the value to 0

:D
[HD7 General] Magpir:
known long ago....
[HD7 General] luckydog98:
Thanks for the info!! I did not know long time ago!!! I'll have to give it a try and see if it helps me out.
[HD7 General] sirajgoku:
it definitely does....im testing this and a few other reg tweaks and seeing how long my battery will last...ill post the results with some screenshots soon :)
[HD7 General] jomuc:
Thanks vor this tweak. I'm glad to get ride of this anoying vibration. If this saves measurable power that would be perfect :-)

Sent from my HD7 T9292
[HD7 General] sirajgoku:
Im using custom Intrinsic ROM now....will post the battery life pics in some time.....

Searching for other tweaks too :)
[HD7 General] Ttblondey:
Using Intrinsic rom apply it. Switch off and on my Hd7 thought my understanding the 3 button deactivated but it still vibrate.

Edit: delete it and apply new ones(dword)string b4. And now it work.
[HD7 General] Magpir:
i have this tweak applied in my custom evolution 7 rom

u will see a battery life increase in standby time
[HD7 General] backlashsid:
Thanks...will try...

Is there a reg tweak to make the automatic brightness levels range from

0-10.

The HD7 is considerably bright even in a pitch dark room. But if you change the brightness from Auto to Low. Its significantly low.

Can anyone please look into this. Thanks.
[HD7 General] sirajgoku:
i guess the auto brightness doesn't work :/

Been searching for that tweak since so long.....even the SMS Led notification....so far no success.....i cant even find where the LED registry's are.....:confused:
[HD7 General] backlashsid:
well it sucks for the auto brightness to not work then..my old Hd2 with Windows Mobile 6.5 did a better job at it..there has to be a way !!
[HD7 General] Magpir:
the HD7 auto brightness needs a complete overhaul. it does get brighter dynamically but does not lower down the same way.

the samsung omnia 7 auto brightness works correctly
[HD7 General] backlashsid:
PLEASE!!!! someone find a way....to make it work !! Its a big battery life killer !
[HD7 General] Magpir:
basically the HD7 can up the brightness under direct sunlight. but when come into the shade , the brightness does not go down.

need to press and awake the phone for the sensor to adjust to the shade
[HD7 General] backlashsid:
wait !! how is that ??

how can it up the brightness but not lower it down..

the hd7 was almost build on the same hardware as the hd2...and hd2 could do it..i know the OS was different...but still...i assume it works well on other phones !!! and how is it smart..if its not auto...
[HD7 General] sirajgoku:
Yup that's the major defect!!

You can see the display when outdoors cuz the brightness automatically adjusts itself...but when u come back indoors the screen still remains bright....

I looked into the brightness registries and I didn't find anything to change to make it work properly :/

I guess that's it with brightness of hd7 :/
[HD7 General] Magpir:
IF HD2 can do it , why not HD7 which is newer?

Maybe someone can find something in the registry to modify auto brightness to work like HD2 ?

---------- Post added at 07:41 AM ---------- Previous post was at 07:39 AM ----------

yes, when it adjusts itself to the ourdoot brightness, it does it quite well too, like 2-3 step increment ( u can see the brightness going up 2 steps depending on the ambient sunlight). THis means the sensor is on and running all the time when u have the screen turned on

but go back to indoors, it doesnt adjust down.

still pondering how is that they make it this way? Does not make sense
[HD7 General] sirajgoku:
Ya even was searching for the LED for the SMS notification....no success!! :(
[HD7 General] backlashsid:
+1 !!!
[HD7 General] Cateye:
How can i access registry files of hd7
[General Questions and Answers] mon5trum:
No activity going on please delete
[Samsung Galaxy Nexus] Paleryder:
Any idea why the market is telling me that the modern combat games are not compatible with this device GNex?
[Samsung Galaxy Nexus] martonikaj:
Says compatible for me. Do you have a modded display density or anything like that?
[Samsung Galaxy Nexus] ellimistx99:
I will second this. Modern combat is also showing compatible for me. Perhaps there is something in your Rom that's causing this? Do you have multiple devices setup for your play account?
[Samsung Galaxy Nexus] ExtctnLvlEvnt:
Its telling me that its not compatible either and I'm stock unrooted ......

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] theking_13:
The games that show up for me are the second and third MC games. I have the third one installed as well, plays fine. Try clearing market cache maybe

Sent from my Galaxy Nexus running AOKP+Franco on Tapatalk 2
[Samsung Galaxy Nexus] ExtctnLvlEvnt:
Have done that and this is what I get, have even reset phone too........

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] theking_13:
Can you download it from the online Play Store?

Sent from my Galaxy Nexus running AOKP+Franco on Tapatalk 2
[Samsung Galaxy Nexus] ExtctnLvlEvnt:
Nope doesn't give me the option to do so

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] theking_13:
I mean go on your computer, and go to the Play Store there.

Sent from my Galaxy Nexus running AOKP+Franco on Tapatalk 2
[Samsung Galaxy Nexus] jimmyhook:
I don't know for sure, but after the last update I've had several problems trying to launch MC 3. It works, but takes multiple launch attempts. Perhaps they closed off purchasing until there's a fix, because they are aware of the issue.