yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Incredible 2] TB13:
I don't think he can figure out what is wrong. I posted up a recovery log like he asked, I hope it helps.
[Verizon Droid Incredible 2] renzo.olivares:
ok my upload speeds are being horrible ive attached a meta-inf folder to this post delete the one in the rom zip and replace it with this one and flash hopefully it works

credits to rms its his updater-script from his deodexed gingerbread stock rom
[Verizon Droid Incredible 2] REDSCARFACE1:
Tomorrow I will pull the file apart and try to fix it it seems like it will be pretty easy
[Verizon Droid Incredible 2] TB13:
Trying it right now.
[Verizon Droid Incredible 2] voxigenboy:
dang it all. i've attempted to dl this 2 times and cancelled both times once i found out it wasn't working.

/me crosses his fingers

/me hopes for the best this time and will just let the whole thing dl on my slow ass connection

wee

well at least in the meantime i'm having fun installing other ROMs and going "nah".

i'm sure i will like yours the most. õ_Ô
[Verizon Droid Incredible 2] punkasfreak:
Unzipped Meta-INF.zip then overwritten the files in Vivow_kingdom_port.zip then works like a charm. can't wait to try this ROM.

Thank you :)
[Verizon Droid Incredible 2] renzo.olivares:
so it flashed? now hopefully it boots :)
[Verizon Droid Incredible 2] punkasfreak:
yes it did flash, but now im stuck at White HTC screen now... nothing has happened for 5 minutes...
[Verizon Droid Incredible 2] renzo.olivares:
hmm.....can someone get me an adb logcat? or has anyone gotten farthe than the splash screen?
[Verizon Droid Incredible 2] voxigenboy:
i've had that happen with a few ROMs today. right when i was about to give up it then booted up. i hope this is the case here.
[Verizon Droid Incredible 2] truelefty:
<xgunther> can't...I get an error: protocol fault (no status)
[Verizon Droid Incredible 2] ruvort:
Any luck?

Sent from my Droid Incredible 2
[Verizon Droid Incredible 2] xgunther:
Same for me. Can't adb logcat, says "waiting for device"
[Verizon Droid Incredible 2] yoitsbry:
its flashing currently for me..... hopefully it boots
[Verizon Droid Incredible 2] punkasfreak:
same here adb logcat then "waiting for device"
[Verizon Droid Incredible 2] renzo.olivares:
ok this is an hboot issue same thing happened to the inc some people were on .72 and gsense only worked for .92 im not sure how it works on the inc2
[Verizon Droid Incredible 2] andybones:
alpharev people have 1.09 or something like that

and xtc clio ppl have .96.200 or .98.200

ill try it soon i xtc clipped
[Verizon Droid Incredible 2] :
maybe if you alter the kernel...

or are there any other hboots to flash with s-off?

EDIT: i have hboot 6.13.1002 ?????
[Verizon Droid Incredible 2] renzo.olivares:
yea if someone can get this to boot please tell me what hboot ill post something else up tommorow if no one can
[Verizon Droid Incredible 2] TB13:
I am about to try with .96
[Verizon Droid Incredible 2] xgunther:
Might help if you joined us on IRC. irc.andirc.net #inc2root
[Verizon Droid Incredible 2] TB13:
+1^

/10char
[Verizon Droid Incredible 2] xgunther:
I'm on hboot-1.09.1000
[Verizon Droid Incredible 2] yoitsbry:
gunther ask your buddies on irc see if they have any idea of what could be up.
[Verizon Droid Incredible 2] andybones:
.96.200 hboot, never left white slpash screen.. waited ten min.
[Verizon Droid Incredible 2] TB13:
Same here...
[Verizon Droid Incredible 2] :
am i the only one with something crazy 6.13.1002

flickr.com/photos/65086713@N05/?saved=1
[Verizon Droid Incredible 2] andybones:
that doesn't seem right, i would flash the .98.200.. same method as after xtc clip
[Verizon Droid Incredible 2] dogshmog:
Nope, I have the same HBOOT. I used AlphaRevX beta 2 Linux, I assume you did the same.....
[Verizon Droid Incredible 2] jesand83:
I've got the same thing, used the Alpharev method for S-Off
[Verizon Droid Incredible 2] punkasfreak:
same. AlphaRevX Linux was used and same version
[Verizon Droid Incredible 2] dogshmog:
And how would I go about doing that? What is the benefit, if any, to different versions of HBOOT?
[Verizon Droid Incredible 2] :
maybe if its 6.13.1002 then any OTA update wont over-write it since its so high it wont flash one with a lower version
[Verizon Droid Incredible 2] mpoly112:
I have the same one, did the s-off through linux, everything is working great, only having the same issues with loading this ROM as everyone else with other H-Boot versions.

Had this ROM on my INC1, these guys are geniuses, well worth the wait for them to get this all straightened out. Thanks for all your hard work and massive cerebral capacity!
[Verizon Droid Incredible 2] yoitsbry:
seems like joel might of anticipated this issue as it is in his disclaimer at the start of the thread...... sucks.
[Verizon Droid Incredible 2] voxigenboy:
right now i'm settling for having this installed:

RMK Gingerbread Sense r1 :: 2.18.605.3 (Rooted/Deodexed/Debloated)

it's fast like CM7 but very stable.

once Joel gets this KINgDoM REwInD 3D straightened out, i'm switching right over though.
[Verizon Droid Incredible 2] mpoly112:
+1 although I'm on PlainJane
[Verizon Droid Incredible 2] BCXtreme:
Same here, as far as my phone and I are concerned, it's just a matter of which comes out first, KINgDoM REwInD 3D or Virtuous Unity.
[Verizon Droid Incredible 2] pwelyn:
Thank you!

assert failed：write_raw_image("/tmp/boot.img", "boot")?
[Verizon Droid Incredible 2] zozor:
Wipe all, also cache partition .will be ok
[Verizon Droid Incredible 2] ozzynyc:
Not very helpful, what hboot version are you on? How did you get it to install? Thanks.
[Verizon Droid Incredible 2] TB13:
As of right now it will not install. Some of the paths are messed up.
[Verizon Droid Incredible 2] Mr. Clown:
Thread closed by OP request while he releases a version.
[Verizon Droid Incredible 2] renzo.olivares:
back in business guys :)
[Verizon Droid Incredible 2] andybones:
Your teasin us man! J/K awesome job bro thanks for all the work! hope the link is up soon:cool:
[Verizon Droid Incredible 2] HeroOfTime:
Link

I'm guessing that means that the link at the beginning of the thread will be good to go soon? I am way psyched to try this one out. I've heard great things.
[Verizon Droid Incredible 2] renzo.olivares:
ok there link fixed now you can download lol
[Verizon Droid Incredible 2] voxigenboy:
holy crap it's back!!!!

thank you OP and friends for all the work.

i can't wait to try it out!
[Verizon Droid Incredible 2] InkedRoughNeck:
Downloading now! This might take a while. Lol. Ill let ya know whats up with it thanks! U da man!
[Verizon Droid Incredible 2] truelefty:
how long did it takes joel?? a few hours ? working hard to get these guys the 3.0 rom ;)
[Verizon Droid Incredible 2] TB13:
I am glad we finally got this semi-functional. Awesome rom.
[Verizon Droid Incredible 2] Lokean13:
Just dl'd and flashed. It booted within a couple minutes.

Thanks for this ROM, I've been waiting for it.
[Verizon Droid Incredible 2] SoCalSpecialist:
ok..lets see how this one goes.

the other 3.0 ROM i just downloaded was still kind of buggy.
[Verizon Droid Incredible 2] Bobby Buggs:
Any user comments yet
[Verizon Droid Incredible 2] jrizk07:
I'm in the same boat as you are. MMS still isn't working on that other ROM and it needs a bit of tweaking.

As far as this ROM goes, even in Alpha it was flying for me. Gonna test some different work arounds to see if we can get the camera working along with the soft keys to light up.

I have no idea where to even begin with GPS but i'd like to try a few things out.
[Verizon Droid Incredible 2] Lokean13:
The only bug that I have seen so far is the home/menu/etc buttons don't light up. other than that everything incl. WiFi are working for me. I did have 1 phone proc fc but it started right back up without a problem.
[Verizon Droid Incredible 2] andybones:
I'd be able to use this as a daiily if we could figure out the keys.
[Verizon Droid Incredible 2] Bobby Buggs:
Am I unrealistic to want all the functions to work, I need the camera
[Verizon Droid Incredible 2] jrizk07:
Bobby,

This ROM is still in Alpha stage. It's hard for Joel to get everything working since he doesn't own the actual phone to test on.

It's a miracle he's been able to get as far as he did without the phone. For that i'm sure we're all thankful but we're currently working to get everything fixed and running 100% stable on this ROM.

Be patient and i'm sure things will start getting fixed.
[Verizon Droid Incredible 2] jrizk07:
Have you tried the camera yet??
[Xperia Play General] FrAsErTaG:
Hi guys

Im selling my Play

Used, but in perfect condition

Hard cover that fits perfectly and was $40

Three batteries in total (one official one) and a wall charger

original box, 16gb memory card, headphones.

Unlocked bootloader.

800i version.

$400AUD + Postage

Item is listed on Ebay so please act quickly
[Xperia Play General] TheBassman369:
You should try posting this in the Market. You would get more interest there. I'm considering selling/trading mine also...lol.

adb shove iPad2post.apk to /forum/thread
[Xperia Play General] FrAsErTaG:
Sold
[Nook Color Q&A, Help & Troubleshooting] darkamikaze:
Hi my gf just got a new nook color and I was planning on adding CM7 (don't plan on doing nightlies) on it.

I've been trying to read as much as I can but there's a lot of information going around..

Are there SOD issues with RC1?

Also if I flash a completely different ROM..

can anyone tell me the difference the stock experience gives as the ereader (since technically that's partially why she bought it) compared to running just the nook app as the ereader on CM7? would it be worse?

Thanks in advanced
[Nook Color Q&A, Help & Troubleshooting] Phatdawg:
Okay, my first reaction is that you need to read the thread about workarounds for the rooted stock nook. That gives you a good idea what is annoying.

SOD occurs but most people get it about once a day or less. PBD does occur as well, but I've never had it myself.

Personally, the issues that are put forth in the workaround section is enough that the stock ereaded rooted is more or less gimped compared to cm7 or cm7 based rom.
[Nook Color Q&A, Help & Troubleshooting] A3 Biker:
Sounds like you should go with CM7 from SD card and dual boot. Doesn't touch the stock experience so you can use both options and see what works best for you with no real mod to the machine.
[Nook Color Q&A, Help & Troubleshooting] painter_:
Way to misrepresent! SOD was squashed a few weeks ago, I do not remember what biuld. PBD was also squashed thanks to fattire.

There are very few reports of ether.

Up until last night I was running N121 and 6/30 kernel with out rebooting all week. I also was able to go 3+ days without charging with moderate use.
[Nook Color Q&A, Help & Troubleshooting] darkamikaze:
that's great news.

can you tell me the exact details of what you're running ?

such as CM7 build xx and what kernel?
[Nook Color Q&A, Help & Troubleshooting] painter_:
darkamikaze, Read the last sentence of what you quoted in your last post and the answer will reveal its self.
[Nook Color Q&A, Help & Troubleshooting] Phatdawg:
"Way to misrepresent"?

Nice.

Let's analyze your awesome post.

1) It's been squashed.

2) They are very few reports of ether.

Hence it hasn't been squashed. They both still occur. And are still issues. And for me it's a daily SOD issue.

There is no "misrepresent". If someone wants to challenge me on these things, that's fine. I've been extremely active in the forums both here and cm7 over the last 2-3 weeks (since I just bought my nook color). I am posting from recent experience.
[Nook Color Q&A, Help & Troubleshooting] ace7196:
C'mon guys, it's all good :)

So OP guy (too lazy to scroll up :P).

Go here: http://download.cyanogenmod.com/?type=nightly&device=encore

Get the top link.

Go here: http://coachz.inetpro.org/~dalingrin/nook/kernels/

Click the latest date, then the correct kernel (if you're running off SD or eMMC)

Install both, wipe cache/dalvik, enjoy!

SOD has been fixed for me as well in the more recent stuff. PBD I used to care about, but since going back to 1.2 and then CM7 again it is down to 4%, which is fine for me :)
[Nook Color Q&A, Help & Troubleshooting] darkamikaze:
mm one of the recent nightly if i'm reading right causes some black screen issue?
[Nook Color Q&A, Help & Troubleshooting] Phatdawg:
That is probably the SOD, there's a post every couple days about it on the cm7 forums.

I don't see PBD posts often. Maybe once or twice over the last few weeks.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
http://forum.ppcgeeks.com/android-tp2/145568-3-5mm-headset-test-kernel.html

you're welcome :D
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Hey ACL,

Did you build this test kernel off Kernel 1336 (the latest FRX07 test kernel) or is it from a prior kernel that doesn't incorporate the changes? Will this be in FRX07?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Wait, what? There's no "FRX07 test kernel"... This is based off of 1333 - if you look at the autobuild service, there's a new kernel now 1337 - this has the 3.5mm code in it.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Sorry Arrrghhh, I misspoke, I meant that 1336 added some things for the upcoming FRX07 release. I was just wondering what kernel ACl built the patches off of so I could figure out what was included and not included in his testing kernel, but I had not had the chance to check the site to see there was a new kernel available that included his patches. So I will just use 1337.

Sorry for the confusion.
[Touch Pro2, Tilt 2 Android Development] emanuelrv:
yes

god listen to me and put to work 3.5 mm beacuse i use the big audio jack o the usb headphone finaly i use 3.5 mm jack
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Pretty sure god had nothing to do with it. Unless you're putting ACL on that high of a pedestal... don't let him get too big of a head now :p

Enjoy.
[Touch Pro2, Tilt 2 Android Development] vnes1984:
Dev of the day

Works great, I've been using the auto build kernal all day and I'm very happy that I no longer get any system panic issues after unplugging like I did when using the extusb. Good job! Thanks ACL
[Touch Pro2, Tilt 2 Android Development] emanuelrv:
when using the extusb reboot the phone sometime
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Do you have an issue with just the 3.5mm jack? I haven't had a single reboot yet. Please tell us what build, phone, etc...
[Touch Pro2, Tilt 2 Android Development] Starfox:
Apparently the code to check for headset button isn't there. From a quick look at dmesg it thinks that the TRRS headset is a plain headphone, and pressing the call/answer button doesn't seem to do anything.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Correct, I guess ACL or I should've mentioned this is only the jack that is functional and the audio that routes out of it - there are no advanced features that work (yet).

Give 'em an inch and they'll take a mile - fix it then! :p
[Touch Pro2, Tilt 2 Android Development] fortunz:
Alarms don't seem to play over either the jack or the speaker when the 3.5mm jack is plugged in.

I tend to keep my TP2 in a cradle overnight, with a speaker. It plays white noise at night over the cradle speakers, charges, and then, in winmo, plays the morning alarms over the device speaker (can't remember if that routing is optional or automatic, but it's comforting since my cradle doesn't have battery backup).

Not trying to take a mile, just thought the mention might be helpful ;)
[Touch Pro2, Tilt 2 Android Development] [ACL]:
hehe.. :p

Well i dont have a headset with any advance features so i can't continue at this point until i get my hands on one. And i'm not sure of what the rhod can do even on winmo since i've never used those features.

I guess if we have an outlined goal as to what needs to be added then we can start. Right now its just plain audio
[Touch Pro2, Tilt 2 Android Development] AkumaX:
what's an "advanced" feature anyway? are they referring to button-event handling? (as in, during music playback, 1 button press on the headphone is pause, double press is skip to next song, etc...)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes. I believe you can also mute calls, answer calls, etc if you have a fancy headset/mic. Some have volume controls as well. All sorts of in-line goodness.
[Touch Pro2, Tilt 2 Android Development] steveoski111:
Hey ACL this is really great work on the 3.5 jack. thank you so much for getting that working i have been using it the past few days and it is great!

I will point out one thing i know there is no advanced features as of yet but i will point out that when you get a phone call and the jack is plugged in you can answer thru the phone but the mic is not active. Like my wife uses her phone in her car thru the 3.5 jack and that is how she talks hands-free but the mic does not activate when the headset is plugged in when you receive a phone call. if you unplug it the other party can hear you but as soon as you plug it in they cant. I don't think that is really an advanced feature but just thought i would point it out!

Thanks again this stuff is really awesome!

oh and we are both on rhods400 and rhod500 she being the rhod 500 but its the same on mine cuz i tried it.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Is this the same for extUSB? I guess I could try it, but I would assume "yes".
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Yeah the mic should not work. What we did was actually trick the system to route sound to the headset based on a trigger. We aren't detecting the type of headset which has to be done later along with the advanced functions.
[Touch Pro2, Tilt 2 Android Development] Gilliland:
Is there any way to make it work - maybe an option to force it? The ability to use the headphone jack to drive the car audio (while leaving the mic active) is crucial to many of us. I don't care whether or not the phone detects the type of headset - I'd just like to be able to have it default to having the mic turned on rather than off.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
course there is a way. write the code.. lol ..

i dont know about any workarounds .. to be honest i dont care about any workarounds. I'll leave that up to you guys to find out. :D
[Touch Pro2, Tilt 2 Android Development] steveoski111:
LoL thx ACL you the man, appreciate everything that you do!
[Touch Pro2, Tilt 2 Android Development] Gilliland:
No, the mic generally worked when audio was taken via USB. It's just the 3.5 that disables it.

And I discovered today that the 3.5 jack support is "works once", just like the USB one was. I plugged the phone into the car stereo and listened to music while I was driving to the store - everything sounded great. Unplugged the phone at the store and went shopping. When I came back to the car, I reconnected the 3.5 plug to the car stereo, but sound came only from the phone itself - the external connection was completely ignored. I plugged and unplugged it several times, but no sound was routed through the jack.

Yet it is clear that the phone knows that a plug has been inserted. When I unplug it, the music player automatically pauses - even though no audio was being routed through it at the time. Weird.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This certainly is NOT the experience I had. I've been able to unplug and replug 3.5mm many times without rebooting and it always routed audio correctly.
[Touch Pro2, Tilt 2 Android Development] fortunz:
I've also been able to unplug and replug on many occasions, and still receive sound over the jack.
[Touch Pro2, Tilt 2 Android Development] Gilliland:
Thanks, it's very useful to know that it works in some/most cases. It seems to me that it's worked correctly for me in the past, but I can't say that with certainty. I'm just not sure that I've cycled through plugging/unplugging before yesterday.

Any thoughts on why it failed in my case yesterday? There must be some difference between our configs, or perhaps there's some instability in the code. I'm running FRX07 as packaged, but with the newer rootfs and 1342 kernel.

(Damn, just reached for my phone and found that it had booted back to Windows. It was on Android just an hour ago, and had been for more than a day.)

If logs will help, please point me to a tutorial on how to collect the right one for this situation. It's about time I learned that anyway. :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I keep trying to recreate this and just _can't_. I'm on the newest kernel & rootfs as well. All works fine here...

I guess you can pull some dmesg logs after recreating the issue. Since no one else can recreate, I'm not sure what good they will do...
[Touch Pro2, Tilt 2 Android Development] Gilliland:
Thanks for trying to recreate it. I haven't had the chance to try it again myself, but I'll try to do so this weekend. I'm hoping to have your experience. :)

Still, if it happened once, it seems likely it will eventually happen again.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
I have had this happen to me exactly one time since using the new kernel. I just thought it was a fluke and never pulled logcats on it, but here is exactly what happened to me to make it happen.

I was listening to my music streaming through the Google Music Beta App (I am not sure it matters what app you are using to listen to music), I got a text message, and the phone never really played the sound for my text message, but the sound got a little garbled and then continued to stay garbled from then on. I took out the headphone plug from the 3.5mm jack and it was playing garbled over the phone's speaker, I then tried to re-insert and take out the plug several times and could never get the music to go back to playing over the external speakers I was using. It did indeed see I was unplugging and plugging it in, because the music would pause.

I found a fix for it. I went to the running applications and stopped my app and also the Android music player app (which always runs for me when any streaming music app is running). Once I did that I re-started the app I wanted to use and plugged in the cord the 3.5mm jack and it worked just fine again.

I am not sure this was even the same exact issue the other guy is having, but I just took it as a weird fluky thing. The funny thing is I had similar things happen to me when using WM 6.5 back in the day too, so it may not necessarily be anything fixable.
[Touch Pro2, Tilt 2 Android Development] Gilliland:
OK, I tried it again today. Recreated it consistently.

If I play music through the 3.5 jack, then pause the music and unplug the 3.5, then plug the 3.5 back in and restart the music, it does NOT play from the 3.5 jack. It doesn't even play from the TP2 loudspeaker. It actually plays from the earpiece. I have to hold the phone to my ear in order to hear it - even though the 3.5 plug is inserted.

However, if I play music through the 3.5 jack, then pause the music and unplug the 3.5, then restart the music and plug the 3.5 back in, it works fine. Music comes right back through the external speakers (connected via the 3.5).

So that seems to be the difference. If I restart the music (by pressing "play") before I plug in the 3.5, it works correctly. But if I plug in the 3.5 first, and then start the music, it fails.

That is consistent - happens every time. And, btw, if I do start the music first, it plays correctly through the TP2 loudspeaker up until the time that I plug in the 3.5.

Note: I've only tested it with the 3.5 wire that connects into my car stereo. I haven't tried headphones or other 3.5-type connection.