yashsingh1/xdaforums huggingface dataset:
[Droid Incredible General] rgps:
What is the correct number to replace with?

Previous post says

"yep" to using 264040

but slightly older post from yesterday by cmlusco says to

"Change it to: verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys"

So is it 264040 or 389630.15 ?
[Droid Incredible General] veroson:
Thanks sonic!
[Droid Incredible General] soniclude:
The only way to know for sure is to look in the \cache folder and see what the update file is called. You'll see one of these two numbers there and that's the one to use.
[Droid Incredible General] veroson:
thanks again sonic.

I just checked the /cache folder and mine is called 264040.zip.

after I edit that line, reboot , and if the update notif goes away, can I then delete that 264040.zip file?

eta: the fix worked like a charm!
[Droid Incredible General] cmlusco:
389630.15 is the correct one, im running stock 4.08.605.15 and thats what my build.prop says. However changing it to either should stop it from updating.
[Droid Incredible General] rgps:
My zip file in /cache was named 264040 so I tried that but it didn't work.

So I tried 389630.15 and that did the trick. So it looks like 389630.15 is the right number to use at least it was for me.
[Droid Incredible General] veroson:
hmm...

was your build.prop 4.08.605.15 like cmlusco's? My build.prop was 4.08.605.2. I used 264040, rebooted and the update notif was gone. I went to system updates, and it said my system was up to date. I didn't try 389630.15 though so maybe they both work?

thanks again for all the help
[Droid Incredible General] ezegm:
Hey I have 4086052 prop and changed the number 38963015. Do I restart after?
[Droid Incredible General] cmlusco:
Yes restart and clear cache
[Droid Incredible General] ezegm:
Clear which cache in recovery?
[Droid Incredible General] cmlusco:
Yes the cache partition in recovery. That will wipe out the ota file and nag files if there on the phone.
[Droid Incredible General] ezegm:
So far so good.
[Droid Incredible General] cubsfanaz:
Thanks for this info. Going to a search to see if I can figure this out, but any info you have is appreciated.

---------- Post added at 10:13 PM ---------- Previous post was at 09:36 PM ----------

I think I got it. Used a program called Android Commander. Booted into recovery and mounted the system. Pulled the file with Android Commander, edited it on my computer, then pushed it back. Cleared the cache in recovery. When I rebooted the phone, the update nag did not appear. Also, when I look at the build.prop file in root explorer, my change has been saved.

Thanks much for posting how to do this without having "s-off."
[Droid Incredible General] JermsMalibu:
The "389630.15" worked for me, thanks guys. :thumbup:
[Droid Incredible General] wrigbone:
Cautionary Tale

Hey folks – there were so many bad reports of this (June 2012) OTA floating around and didn’t want my phone booting at 2am so I decided to just update the radio and use the directions here to remove the nag.

There is good news and bad news to this story so bad news first – I kinda bricked my phone messing with the build.prop. I think the culprit was, of course my stupidity, and ES File Explorer. I am rooted with s-off and had all the settings in ES to allow read/write – root privilege – etc… but when I edited the build.prop and then re-opened it the file seemed to be blank. ES also automatically created a “build.prop.bak”. I tried to move a copy out of system/ edit and copy back in but the same thing happened. Here is where “stupid is as stupid does” I chanced it that the file was saving just fine and I just needed to reboot. If there was a problem I could just ADB into the system folder and pull/push the build.prop backup. So whatever ES File Explorer did/does when saving the file was not good. All I can think of is it is a permissions thing or it adds some formatting (like MS Word) to a .prop file. Okay phone will not boot now - no biggie - bring up ADB - pull the back up – rename – push it baaaack aaaahhh wait a minute “could not push file no space left on disk”. Without knowing much about Linux I Googled and tried to troubleshoot to no avail. Ef it! the phone is going up for sale as soon as my Galaxy SIII arrives so I might as well just put this latest ROM on here and see how it goes.

Good news – cmlusco’s “UPDATED” stock rooted OTA 4.08.605.15 Deodexed version and the new radio 2.15.10.12.20 are up and running fine for me. No bootloop in the middle of the night and no freezes. Had to start fresh but was planning on doing that next week anyway. With all the crap I had added and removed over the past year the phone is running much smoother and faster now. I cannot report, as some have, of dramatic network improvement from the radio update however. Signal strength has gone from avg -90 dBm to -88 dBm but I also don’t have the case on it right now so don’t get your hopes up people.

So the moral of the story is “be careful if you are using ES File Explorer”. I’m sure someone will point out that I did something wrong. And don’t be afraid of the new ROM. I think the folks that are having problems are OTA update issues. I’ve read that even those folks will get past it if they leave their phone on and not pull the battery overnight but that is debatable. Anyone interested in a rooted Droid Incredible next week? ;)
[Droid Incredible General] ironside2011:
strangeness

Ok,I gotta a question for you guys. Before I was able to flash the rooted new OTA , I used the RUU to flash back to 4.06 Gb and got the 92.000 hboot locked. But when I flashed the rooted 4.08.605.15 OTA and flashed the new hboot to go with it I'm unlocked now. Can someone explain this?
[Droid Incredible General] bill_starr:
My problem is very similar to "Cautionary tale" above.

I'm new to doing things with a rooted phone and am not sure the best place to post this, but it seems related to this thread.

Sunday this week (12 Aug 2012), I successfully rooted my phone using Steps 1 to 9 of the following page.

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

I have Droid Incredible with Gingerbread 2.3.4 and it keeps trying to push me the "4.08.605.15" OTA update I don't want to install. Rather than hitting the "Later" button every time it pops up a reminder, I wanted to get it to stop reminding me.

So with Root Explorer, I mounted "/system" to R/W and opened "build.prop" with the text editor function of Root Explorer and changed the "ro.build.fingerprint" entry from "185897.2" to "264040" as described here.

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

When I selected Save and Exit from the text editor menu, "build.prop" seems to have disappeared from "/system" and there is a zero-length "backup" copy named "build.prop.bak" created by the editor.

So far, the phone seems to be working okay, but I am afraid to restart it now.

I have a copy of the pre-edit "build.prop" saved on my SD card and have it copied to my laptop as well.

Trying to copy it back to "/system" via Root Explorer does not seem to work. I don't get any error, but the file does not appear either.

Anyone have a suggestion for the simplest way to get "droid.prop" restored to the "/system" folder?

Or maybe it's really there and I just can't see it.

Is there anything that will get me into trouble with a missing "build.prop" file other than restarting the phone?

Thanks, Bill

Wed, 15 Aug 2012, 4:33 pm EDT

---------- Post added at 05:16 PM ---------- Previous post was at 04:33 PM ----------

Just after posting, I remembered that I had done a Nandroid backup with CWM two days ago, so I did a restore and got my original "build.prop" back in the "/system" folder that way, at the minor expense of losing a couple of days of call and text history and needing to reinstall a couple of apps.

I guess pressing "Install Later" every once in awhile isn't so bad after all.

I'll do more research before trying to edit "build.prop" again.

Thanks, Bill

Wed, 15 Aug 2012, 5:16 pm EDT
[Droid Incredible General] cmlusco:
Arr you s-off? If not it will not work. At reboot the file will be regenerated from the ramdisk. To edit any system file, you need to be s-off. It will look like you edited it, but apon reboot will be unchanged.
[Droid Incredible General] MKEbrew:
So, for this new 4.08.605.19 OTA, I extracted the zip and found AAInfo.txt file showing "Customization Id: 351442". Is that what I would change my build.prop to in order to get rid of the update notification? Currently I have 4.08.605.2 389630.15. do I change 389630.15 to 351442? I'm not sure where to find the number, so this is a guess.
[Droid Incredible General] cmlusco:
No you want to look in /system/build.prop of the update file for ro.build.fingerprint=. What ever it says change your phones build.prop to that.

I still have not recieved an update notification yet. Is there any way you could upload the update zip file somewhere and post a link?
[Droid Incredible General] MKEbrew:
That was what I was hoping, but its a build.prop.p. How do I view a build.prop.p file? I've tried notepad already.
[Droid Incredible General] cmlusco:
Not sure really, googling says there isnt a way.
[Droid Incredible General] Hand76:
Yea would love to know what to edit to stop these new notifications.
[Droid Incredible General] MKEbrew:
Sorry cmlusco, I missed this yesterday. Here is the zip: http://markpiontek.com/misc/fd0d8be3759e.OTA_Incredible_C_Gingerbread_S_VERIZON_WWE_4.08.605.19-4.08.605.15_release_305224.zip
[Droid Incredible General] nitrodev:
Root Browser (I'd post a link, but I'm too new) has a text editor that will allow you to view and edit the file. Just need to find out what needs to be edited in the ro.build.fingerprint line.
[Droid Incredible General] MKEbrew:
Yep. I've done this before, juts don't know what to change it to. Hoping that posting the zip will help out with that.
[Droid Incredible General] nitrodev:
I changed ro.build.fingerprint to verizon_wwe/inc/inc:2.3.4/GRJ22/539174.19:user/release-keys

rebooted into recovery, cleared cache, cleared the update notification once more and haven't received an update notification since.

Thanks for posting the .zip MKEbrew!
[Droid Incredible General] cmlusco:
That is the correct build number, i just installed 4.08.605.19.

Edit /system/build.prop. Look for "ro.build.fingerprint=", change the whole line to read this:

ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/539174.19:user/release-keys

Save the file, reboot to recovery, wipe cache and dalvik-cache, reboot.
[Droid Incredible General] MKEbrew:
That seems to have done it. Much appreciated!

I just wiped both cache manually & then rebooted.
[Desire HD Android Development] RaiderX303:
This is a Fully Functioning port of CyanogenMod for the Desire HD, everything works hardware wise except proximity sensor doesnt turn screen off in calls.

ALL ROMS ARE FLASHED AT YOUR OWN RISK, I AM NOT RESPONSIBLE FOR ANY ISSUES THAT MAY BE CAUSED FROM FLASHING A CUSTOM ROM

MAKE SURE YOU PERFORM A WIPE/FACTORY RESET BEFORE FLASHING THE ROM

Change Log;

v0.4 - Beta

-New Base - Based on CyanogenMod-vision-RC3

-New Kernel by Apache14

-- CFS

-- BFQ

-- Group Scheduler

-- EXT4 support

-- CIFS (Module)

-- utf8 (Module -- Non latin file names)

-- tun.ko for OpenVPN

-- LZMA Compressed

-- SmartAss Governor (Very Battery Friendly)

-- Default Governor OnDemand

-- Stock Frequency and voltage

-- Buzz Kernel 1.0.2 based

-Camera 720p should work now (Set encoder to H264 not MPEG4)

v0.3 - Beta

-Back to v0.1 base, Still has v0.2 fixes

-Fixed bluetooth

-Fixed FC in settings

-Another attempt at camera fix

-Added Wifi Tether for Root users (Will FC on first run, just reopen)

v0.2 - Beta

-New boot.img with fixes

-Working DSP Manager

-New updater to fix camera issues (hopefully)

-Auto Backlight should work

-Cleanups

v0.1 - Beta

-Initial Release

-All hardware working (Except Prox Sensor)

-Camera works at 8MP including HD recording

-All features of CyanMod 6 including settings controls in notifications bar

-All latest GApps included

-Removed Rom Manager as this doesnt yet work correctly with the Desire HD

-Full Vanilla ROM, no HTC Sense bits AT ALL

- DOWNLOAD -

Known Issues;

-None

FLASH WITH CLOCKWORK MOD

Credits go to Cyanogen, Modaco, VillainROM Team, and anyone else i have missed who has contributed to android development.
[Desire HD Android Development] dr.m0x:
This is it! The Desire HD has come of age!

Rejoice!

Thanks so much ... personally I'm gonna stick with Leedroid until prox issue is resolved because it ****s me off when my face starts pushing buttons mid call ... but this is really the news I have been waiting for since I got this phone.
[Desire HD Android Development] flando:
Flashed and working smoothly.

Will begin noob test.

work at 8.30 not looking fun...
[Desire HD Android Development] Thyrus:
Thanks soooo much!!

what a difference :)

something I noted - DSP manager is not working, means settings have no effect
[Desire HD Android Development] Eddie1506:
So, is the sound volume any better with this ROM? I guess it could show us if the low sound volume is a hardware or software issue.
[Desire HD Android Development] yvon1029:
i flash this rom and then find the cinema not working

when start the cinema,it is crashed and only to restart the phone
[Desire HD Android Development] Thyrus:
if one would know what you mean by cinema....
[Desire HD Android Development] liorra3:
yep, it was my favorite in the old days that i playd with the google nexus one, but now - dono, i have some weird feeling to stay with the new "sense" for now.
[Desire HD Android Development] yvon1029:
sorry，i means the camera does not work
[Desire HD Android Development] Thyrus:
just ported the minimal theme to it, and by porting it, i seem to have corrected the proximity issue....
[Desire HD Android Development] AndyCr15:
How did you 'port' or apply the theme then?
[Desire HD Android Development] Thyrus:
ported, made some modifications, updated to buzz kernel v07, created update.zip, applied zip, finished :)
[Desire HD Android Development] AndyCr15:
So from that, what can you give us that will fix the proximity sensor issue?

(Just about to take a look at the ROM myself :) )
[Desire HD Android Development] Thyrus:
honestly, i have no idea .... i must say though, i didnt check for the error when i flashed the CM port from raider (didnt make any calls). Just updated to CM6.1 then went straight to porting MinimalTheme (as I cannot stand the stock android look anymore)

So I went straight to porting - either the error/bug was not there in the stock CM port in the first place, or is only an issue on raiders device, or when theme-porting it solved the issue. hard to say to be honest....

but the port included the phone.apk -> which means, this may very well be the root cause....
[Desire HD Android Development] palexr:
I used to be CM'ed to the latest release on my Magic/Sapphire, religiously. But since I've had my DHD I've kind of lost the plot on the benefits of CM over Sense as it is now. It seems to be working very smoothly as is.

Can someone spell out what the benefits are.

Also, mainly because I haven't investigated flashing on the DHD, I take it there is a way flashing back to the original via nandroid or some such?
[Desire HD Android Development] RD1945:
The proximity sensor is picking up light and returning values.

I tested it with the "Light Sensor" app.

Also, on my phone the screen does turn off when making a phone call (didn't change anything on the system, it worked out of the box).

Things I found not working so far:

- Auto Brightness (someone else can confirm this?)
[Desire HD Android Development] RaiderX303:
The proximity issue is related to the phone.apk, what device did you port the theme from?
[Desire HD Android Development] alain57:
does the htc sense service work with this rom ?

i love custom rom, but i also love the htc sense service (disabling phone, erase phone and locate phone from the htc sense website)
[Desire HD Android Development] Thyrus:
raider, i used the nexus one port :)

http://xdaforums.com/showthread.php?t=787232
[Desire HD Android Development] garok89:
:D:D:D:D:D

BEEN WAITING FOR THIS FOR WEEKS....

let us hope the nightlies start coming soon (im an update junkie)
[Desire HD Android Development] ghostofcain:
logcollector
[Desire HD Android Development] HTF:
Any chance you can upload a version with stock android launcher, some people prefer it to 3rd party ones.

TBH if I was you I would keep the stock launcher in the rom along with ADW so users of the rom can choose.

Edit: My bad cyanogen uses ADW launcher by default.
[Desire HD Android Development] FernandoMiguel:
Since CyanogenMOD comes with ADW I see no reason to change this ROM more then needed!
[Desire HD Android Development] FernandoMiguel:
i rather like alogcat

http://www.appbrain.com/app/alogcat-logcat-application/org.jtb.alogcat?install
[Desire HD Android Development] timstanley1985:
Upgraded to v.03 and still no Bluetooth OPP and FTP. I am also having the 2 second 720p force close too.

Settings force close is fixed

Keep up the good work

Sent fron my CyanogenMod Desire HD
[Desire HD Android Development] wonderwout:
This is great, thanks a LOT for this port. Coming from the N1 I really really enjoy having CM on my phone again. Flashed v0.1 on Friday and now on v0.3.

I have the 720 camera issue as well, it hangs after 9 seconds for me. Also I do have some occasional lags when desktop scrolling (ADW) and some battery drain which I think is related. I haven't looked into it much but the Android system process seems to use more battery and CPU resources then expected. Still battery gets me through the day and I'm sticking with this port while awaiting official CM support. Thanks Raider!
[Desire HD Android Development] arielext:
Something is straining the battery but no real clue on what it is atm. Since this rom also gives me some problems with my wifi I'm reflashing a different rom but will surely look into this topic; The base of this rom is just awesome!
[Desire HD Android Development] forelli:
Twidroyd+nexus 1 live wallpaper was draining my battery very fast. Now I just look at the tweets and then exit the application and I changed the wallpaper for a static one and now I can listen to 3 hours of music, having some phone calls (30 min) and I'm left with 81% battery: this was my yesterday routine. This is not a benchmark or whatever but I share it with you FWIW.

f.
[Desire HD Android Development] ghostofcain:
Android System seems to be culprit here as well, although I must confess battery is not the issue I feared on this ROM
[Desire HD Android Development] arielext:
Very much appreciated, but (there is always a but) i checked this *beta* cyanogenmod against the stock desire hd rom and the rooted rom with a diff. kernel / advanced cpu profiling / 3g throtteling with the exact same apps installed and the exact same'ish usage. this rom lasts ~ 20 hours vs. 30+ hours on desire stock; the rooted rom with advanced features last over 48 hours. Bare in mind that I've used the exact same settings for kernel and 3g throtteling in both this rom and the rooted stock.

I surely believe this rom will outlast all others once the tweaking of it is done.
[Desire HD Android Development] ghostofcain:
Look Ma! we made the CyanogenMod Wiki
[Desire HD Android Development] Walker Street:
OpenVPN works a charm on CyanogenMod, combined with Buzz's kernel

Hi, see my thread. I got OpenVPN working a charm using the CyanogenMod Rom 0.3. Interestingly I'm not using the CyanogenMod kernel tun.ko, but am using Buzz's kernel (and his new tun.ko). I am however using the openvpn binary that came in the cyanogenmod /system/xbin.

Thanks RaiderX303 for your wonderful rom!

I just bought you a drink or two (beer or cider your choice) :D

6PB4043083727203H
[Desire HD Android Development] Walker Street:
Our problem on the LeeDroid Rom with openvpn might have been related to problems with busybox and ifconfig. These might be more cleanly installed on cyanogenmod.
[Desire HD Android Development] wonderwout:
I found out what was draining my CPU and battery using OSmonitor. It was not an app but the 'android.process.media'. It was constantly trying and failing to make thumbnails from some sdcard directory containing png files with file names which where to long. Directory was from Pulse reader app which I had already uninstalled long ago.

Deleted those png files and all seems fine now, happy!
[Desire HD Android Development] timstanley1985:
Still having wifi tether problems. If you tick the portable hotspot button in settings it just comes up with error. Wireless tether from the market FC's everytime you try to open it.

Barnacle loads without any errors but I haven't got a way of testing the connection until this evening. Will update then.

Sent from my CyanogenMod Desire HD
[Desire HD Android Development] darrenjdoc:
Is bluetooth working yet on the rom ? I couldnt get it working and had to switch back to LeeDroid as i need it for my van.
[Desire HD Android Development] Walker Street:
Same here. Bluetooth is not working yet. Ah well. CyanogenMod for Openvpn. LeeDroid for Bluetooth. I must admit: I can live without the Sense stuff and kinda like the idea of getting a truer version of Froyo (now that I think of it).
[Desire HD Android Development] flando:
LeeDroid Bluetooth is sense based though :(
[Desire HD Android Development] FernandoMiguel:
i didnt see any post regarding this, but GPS is NOT working in 0.3
[Desire HD Android Development] RD1945:
Same here. GPS is dead.
[Desire HD Android Development] timstanley1985:
GPS is working for me. Try turning GPS on and off in settings. That fixed the GPS problem for me in the first build

Sent from my CyanogenMod Desire HD
[Desire HD Android Development] ghostofcain:
doesn't appear to be working for me either
[Desire HD Android Development] RD1945:
I even tried the trick: disable gps, reboot, enable gps, reboot.

Did not work.
[Desire HD Android Development] Doktaphex:
GPS working fine here on v0.3 with BUZZ 1.51 OC kernel v1.0.0
[Desire HD Android Development] liljom:
hey guys,

if I copy the power widget to a Sense ROM, will that work?

And which file is that? :D

I looked around in /system/app/ but I can not see which one :/
[Desire HD Android Development] RaiderX303:
new rom to be released tonight or tomorrow based on my own compiled cyanogen build with custom kernel by Apache14 (no overclock), kernel details below.

-- CFS

-- BFQ

-- Group Scheduler

-- EXT4 support

-- CIFS (Module)

-- utf8 (Module -- Non latin file names)

-- tun.ko for OpenVPN

-- LZMA Compressed

-- SmartAss Governor (Very Battery Friendly)

-- Default Governor OnDemand

-- Stock Frequency and voltage

-- Buzz Kernel 1.0.2 based

this should help with performance and battery life aswell as add some features. big thanks to Apache14 :)
[Desire HD Android Development] dr.m0x:
FM Radio coming?
[Desire HD Android Development] jjrroberts:
I installed this mod yesterday, works brilliantly. Excuse my newness but i couldn't see any posts detailing how to upgrade?

Do we simply download the rom to the sd card, reboot to recovery and then flash? Is a wipe required each time?

Thanks again, i'm enjoying this mod significantly more than the default sense.
[Desire HD Android Development] RaiderX303:
wipe is not required for each flash, FM radio is not yet working on CM, i will work in radio when i have compiled sources
[Desire HD Android Development] timstanley1985:
I really love the the pure android experience and prefer ADW by a country mile to sense but there are a couple of elements from sense that I do miss:

1. The keyboard had trackball replacement buttons at the bottom which I really miss when trying to navigate text input

2. The sense copy and paste implementation was a great leap from my stock hero. Are there anyways a similar innovation can be implemented in the build.

Sent from my CyanogenMod Desire HD
[Desire HD Android Development] RaiderX303:
the next version is going to be delayed a bit due to issues compiling the source for the DHD, good news is camera seems to be working better, new version supports OpenVPN fully by default and better battery life
[Desire HD Android Development] forelli:
Many thanks for your efforts. Will be patiently waiting.

Sent from the Galactic Empire using the Dark Side of the Force