yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] synergye:
Well, I would need a log to know for sure, but I think the fcs with the second build are because of board flags that shouldn't play nicely without gpu accel. And the fcs in the first one are probably from incorrect graphics flags. But it could indeed be something as simple as init.rc since I had to manually get rid of some stuff in there for testing. Almost home, but not going to be able to do much testing do the GF, just going to upload another build assuming it completed.

Edit:

Thank you! This is to the gpu accel build, even though it says "B" in the filename, correct?

Edit: also, want to link me to your git? Or upload source? I would like to know what to put in the Max partitions flag.
[HTC Vivid, Raider, Velocity] ghostdogg:
I'm a git newb so I never got it uploaded and after a recent repo sync I cant get a build to compile correctly. Haven't had more than a spare hour concurrently so I apologize! I can get stuff together a little later this week, giving myself a mandatory day off.

Here is the log from build A.

http://pastebin.com/qBrdYQHf

You may find some interesting stuff in my pastebin as well. I think the proper max partitions is 37 and I'm almost positive its copied in my pastebin somewhere.
[HTC Vivid, Raider, Velocity] synergye:
Thanks! I'm uploading two builds again in 1.6. And now I'm pulling myself away from the computer for the night. Take it easy everyone.
[HTC Vivid, Raider, Velocity] enzyne:
Exact same problems as last build in Alpha 1.6 for me.
[HTC Vivid, Raider, Velocity] :
Same here Alpha1.6 has the force close loop and then the second only the setup wizard :/
[HTC Vivid, Raider, Velocity] ghostdogg:
Build 1.6 logcats thanks to DeamonFish.

http://pastebin.com/kQ92mn6M

PS. The purpose of this thread is to allow for development posts. It's extremely distracting and time consuming for many of the people involved in development to have to sift through the 5-10 "chat" posts that appear between visits. In all honesty there are only about 25 useful posts (without a LOGCAT output for a build anything else is relatively useless now that ADB has been confirmed to be working) in this entire thread for Synergy to read. Just for his sanity if we could all please just refrain ourselves I'm sure it would be appreciated.
[HTC Vivid, Raider, Velocity] cannothas:
I highly recommend reading this:

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

Synergye, thanks for your work! All I can contribute is thanks, so here they are!

THANKS. Super excited for when this is done!
[HTC Vivid, Raider, Velocity] MisterSchnapps:
GTFO! If you have nothing positive to contribute to this thread, your presence isn't welcome. Rome wasn't build in a day, and this **** ain't easy. I'm sure comments like this really motivate syn. to do this for us. Especially when he isn't asking for anything in return..

No wonder this forum has lost so many dev's.. if you think you can do better, step up to the plate.
[HTC Vivid, Raider, Velocity] :
Flashing 1.7 A now will get back with results. The A build has me stuck on the bootanimation. Build B same thing :/ One thing i've noticed is that when its not gonna boot, the animation usually moves slower then normal.
[HTC Vivid, Raider, Velocity] come at me bro:
What's the update in 1.7?
[HTC Vivid, Raider, Velocity] synergye:
Snagged a log at work and it's media profiles that's causing the issues. Come at me bro, check me git to see what's changing. We've gotten past the overlay commit failed errors with 1.6 regarding graphics.

Edit:also put in some missing proprietary libs regarding audio.
[HTC Vivid, Raider, Velocity] come at me bro:
Damn 2 already, I wish I didn't need my phone today would test
[HTC Vivid, Raider, Velocity] DeamonFish:
http://pastebin.com/ZSLvtRdX Logcat for CM9 Alpha 2.0

http://pastebin.com/6dv7duhV Logcat for CM9 Alpha 2.1

http://pastebin.com/0zygtdXn Logcat for CM9 Alpha 2.2

http://pastebin.com/cgBkXDkD Logcat for Alpha 2.2 without libbeatscorehtc.so
[HTC Vivid, Raider, Velocity] :
Alpha 2.3 SystemUI and setup wizard crash cycle.
[HTC Vivid, Raider, Velocity] :
Beta 1.1 same issue. :/ This is the graphics driver that's causing this?
[HTC Vivid, Raider, Velocity] synergye:
Wait...same issue! So it got past the white HTC Screen! Awesome. I'm at work right now...someone want too grab a log through boot?
[HTC Vivid, Raider, Velocity] :
Yep! and only linux users can grab the log cats right? Beta 1.0 stuck at hTC Screen but its interesting it installs as a google gadget cd drive thing during boot but thats it.
[HTC Vivid, Raider, Velocity] synergye:
A few windows users have been able to get logs also. You might need to run as administrator. And that's why I was glad 1.1 passed the boot animation
[HTC Vivid, Raider, Velocity] come at me bro:
I can't wait for this I'm so close to swapping this phone and 200 bucks for a fresh 4s
[HTC Vivid, Raider, Velocity] synergye:
Don't. If you've been following IRC, IOMonster pointed out that Adreno libs weren't copying. Now they are. The reason 1.0 didn't boot.
[HTC Vivid, Raider, Velocity] come at me bro:
I'll hop on later and try to contribute :)
[HTC Vivid, Raider, Velocity] come at me bro:
Wait so 1.1 is a working Rom?
[HTC Vivid, Raider, Velocity] synergye:
No. 1.1 wasn't synced to the git.
[HTC Vivid, Raider, Velocity] dagnus:
beta already??

holy ****.. we're in beta?
[HTC Vivid, Raider, Velocity] synergye:
The betas haven't been booting. Just due to sheer progress and number of builds.

Edit: take that back.
[HTC Vivid, Raider, Velocity] come at me bro:
Take wha back lol

---------- Post added 6th April 2012 at 12:29 AM ---------- Previous post was 5th April 2012 at 11:46 PM ----------

newest beta booted up to the welcome screen, digitizer/touch screen didnt work

no logcat :(
[HTC Vivid, Raider, Velocity] synergye:
No touch screen? What device? Also, 2.1 seems fine as far as touch screen goes.
[HTC Vivid, Raider, Velocity] come at me bro:
the 2.1 rom

htc att vivid

i guess HTC PH39100
[HTC Vivid, Raider, Velocity] synergye:
Yeah. 2.2 was my fault. It was actually freezing. But 2.1 should be ok (no radio/wifi currently, but gpu accel if you want to play around)
[HTC Vivid, Raider, Velocity] come at me bro:
so no cell service??

gonna check it out
[HTC Vivid, Raider, Velocity] synergye:
Or wifi...yet.
[HTC Vivid, Raider, Velocity] 1987dram:
2.1 Boots nice! Just playing around to see what works.

Very Very cool!! Looks Nice!!:D
[HTC Vivid, Raider, Velocity] come at me bro:
your on irc?
[HTC Vivid, Raider, Velocity] synergye:
Roger that.
[HTC Vivid, Raider, Velocity] come at me bro:
you left :(
[HTC Vivid, Raider, Velocity] :
Beta 2.2.1 No bootanimation black screen after htc logo but boots and then rebooted after device sat for 5 seconds. Very fast boot up after that and setup wizard crashes right after time zone setting. Looks like not selecting the set by network check box rectifies the problem. Dont have wifi to try with at this time.
[HTC Vivid, Raider, Velocity] lordshido:
Report for 2.2.1

https://gist.github.com/b7f6d7a62538d095cc5d

Wifi doesn't work. Near end of log is camera trying
[HTC Vivid, Raider, Velocity] kevsthabest:
Keep up the work guys! The work you guys are doing and the progress is amazing!
[HTC Vivid, Raider, Velocity] Brand New:
Ooooo now it gets interesting!! I can tell you guys are almost there! :)
[HTC Vivid, Raider, Velocity] synergye:
It sure is. Realized I was copying quite a few incorrect libs/binaries, and had changed wifi firmware location without changing it in the kernel, so definitely getting interesting! :)

Also, if it's ever a day without a new build uploaded, check the git and I'm sure you'll see that progress is being made.
[HTC Vivid, Raider, Velocity] MisterSchnapps:
Shoot, your git and mediafire are my homepages. on the lappy and mobile. haha i feel like a fiend. but can wait for this to get that daily drive status! soo close.

keep up the good work man.
[HTC Vivid, Raider, Velocity] come at me bro:
What I miss? Cell and text work? I wish I could test right now
[HTC Vivid, Raider, Velocity] :
Beta 2.4 boot loop after some time no boot animation. Beta 2.4 alternate freezes on black screen and doesnt do anything also no boot animation.

Doesn't look like it yet but were close to getting WiFi. The builds don't really like my phone it seems :/.
[HTC Vivid, Raider, Velocity] synergye:
Has nothing to do with your phone. That's how 2.4 is. if you just want to play around 2.3 is the one to do it with currently. Don't know if wifi or radio will happen first, but I can assure you we're hard at work.

Once it happens, you will know by this thread's activity and title.
[HTC Vivid, Raider, Velocity] :
majorultimatetestkang boots wifi not working and no cellular modem. What is the kernel module libbeatscore for? And is it going to be new practice to have no boot animation?
[HTC Vivid, Raider, Velocity] synergye:
Won't be new practice, just wasn't a priority to change the shell script and/or system.prop to enable the bootanimation (I will have it set as default on, but you can still disable it in settings).

libbeatscore was for testing what sound profiles were missing, and is an HTC proprietary lib.

That build was to test if the thermald binary had an impact on internal kernel errors, and is now down. Also wanted to test wpa_supplicant.conf in different form.

Possible good news however is that I seem to have forgotten about ueventd.rc (DUH, right?) and am missing lines for radio/wifi/other smd interfaces :O Also, I had the wrong smd interface listed for the radio in init.rc (was fixed earlier today however and proper in a few builds).

That said, I need to stop working on this and go to bed since I'm very sleep deprived. SO I wrote notes to myself, and will start adding onto ueventd.holiday.rc (copies as ueventd.rc) and testing when I wake up :)
[HTC Vivid, Raider, Velocity] :
Beta 2.5 boots, looks like sound settings do not crash anymore like they had on previous builds, but still no sound, storage, wifi, bluetooth, or cellular modem connectivity. Everything else seems to be working pretty well. Excellent progress is being made.
[HTC Vivid, Raider, Velocity] synergye:
Yep. As far as wifi goes, you'll notice this line in logcat: I/wpa_supplicant( 367): rfkill: Cannot open RFKILL control device

This commit fixes the issue: https://github.com/IceCreamSpaTreatment/android_device_htc_holiday/commit/c058d6ae17da58e8bb4d3bf159cf841c70648f18

Also, as far as audio goes, pyramid libs fix the issue (thanks rafyvitto for pointing out pyramid libs don't have libbeatscorehtc dependency). Check here for device repo commits that I've made today: https://github.com/IceCreamSpaTreatment/android_device_htc_holiday/commits/master
[HTC Vivid, Raider, Velocity] meatwad0222:
looks like we are about to get working radio...i love u...lol:)
[HTC Vivid, Raider, Velocity] :
Any idea why im unable to get logcat on my PC?
[HTC Vivid, Raider, Velocity] synergye:
No idea. Some people have issues with it. If you're on windows, you could try running as admin, or if you're on a nix system, run adb as root.
[HTC Vivid, Raider, Velocity] cannothas:
Very excited about your progress! Awesomeness is just around the corner! Thanks to you all for all your time, devotion, and expertise!

Sent from my HTC PH39100
[HTC Vivid, Raider, Velocity] meatwad0222:
about to try 2.6

no boot stuck on black screen
[HTC Vivid, Raider, Velocity] :
2.6 failed to get past black screen. waiting for 2.7 to upload.

---------- Post added at 03:57 AM ---------- Previous post was at 03:46 AM ----------

2.7 Bootloop.
[HTC Vivid, Raider, Velocity] synergye:
How did you guys get to it and flash it so fast?! Wow! yeah, I messed up git with audio files and did something different than when I pushed them.
[HTC Vivid, Raider, Velocity] :
The power of ultra super high speed broadband lol and constant F5 key usage.
[HTC Vivid, Raider, Velocity] meatwad0222:
bootloop for 2.7:(
[HTC Vivid, Raider, Velocity] synergye:
Done for the night. Cap blew on my laptop, so a little upset. Was rebooting due to being unable to load the modem firmware from bad positioning in the init.rc
[HTC Vivid, Raider, Velocity] come at me bro:
What's quick and dirty

Imma hop on irc later, last night was ahmazing :)
[HTC Vivid, Raider, Velocity] :
It sounds like the build with the working modem but it looks like syns computer took a crap on him last night so the upload didnt complete.
[HTC Vivid, Raider, Velocity] synergye:
Yeah. Only upsetting due to how long it will take to get a replacement. That build did not have working modem though. Was just a test for another user. The issue with the kernel panic from being unable to find q6.mdt was due to mounting one wrong partition.

The fried laptop isn't stopping my development however.
[HTC Vivid, Raider, Velocity] cannothas:
Well that is good news at least :-)

Sent from my HTC PH39100
[HTC Vivid, Raider, Velocity] synergye:
Quick note, you guys NEED the new hboot from now on out, otherwise kernel panics can occur.
[HTC Vivid, Raider, Velocity] come at me bro:
I miss so many builds being mobile

Starting to hate s-on
[HTC Vivid, Raider, Velocity] :
Beta 2.8 stuck on black screen.
[HTC Vivid, Raider, Velocity] pside15:
I'm sure we will see s-off soon.
[HTC Vivid, Raider, Velocity] :
Theres no point to have s-off. Other then to flash radios?
[HTC Vivid, Raider, Velocity] come at me bro:
No need to fastboot a boot img

Or need a booting Rom to flash GUI the boot IMG

Basically you don't need a CPU to change roms or fix softbricks
[HTC Vivid, Raider, Velocity] Brand New:
Is there any hboot differences between the .56 OTA and the .52 leak?
[HTC Vivid, Raider, Velocity] synergye:
Yeah, forgot to push the second audio commit for new libs. That was the issue. I'll have the fixed build up soonish. At work so not as quick as when I'm working on this with full attention.

That leaked hboot also has the new modem firmware, so no. Biggest difference is from the 1.85hboot.
[HTC Vivid, Raider, Velocity] :
I don't believe so. The RUU would tell you if you have both of them for the leak and official builds.
[HTC Vivid, Raider, Velocity] synergye:
Once we get to a better point in builds, I'll show you that you don't even need a PC to flash boot.img with a shell script :)
[HTC Vivid, Raider, Velocity] :
Does the recovery not flash them properly is that the issue? Because restoring from a nandroid requires fastboot flashing.
[HTC Vivid, Raider, Velocity] synergye:
Recovery can't flash them due to s-on. We can however use a different updater script that copies a shell script to reboot into fast boot and do the flashing itself and the boot.img so the flashing doesn't occur in recovery but fast boot.
[HTC Vivid, Raider, Velocity] :
Why is it that we can use the computer, but not the recovery? lol s-on should be s-on regardless or we should be able to flash radios?
[HTC Vivid, Raider, Velocity] synergye:
It's not so much the computer as it is using fastboot to flash. Recovery won't flash boot.img so long as we're s-on. Just as we can't flash radios.
[HTC Vivid, Raider, Velocity] :
Somebody said that you can flash a radio as long as its signed so wouldnt that eliminate that restricition or?
[HTC Vivid, Raider, Velocity] synergye:
Yes. That's what I meant. Currently we can flash radios so long as they're signed/matching (official). With s-off that doesn't matter, and users who haven't received the new hboot will be able to flash it.
[HTC Vivid, Raider, Velocity] :
With s-off we can also downgrade our hboot right?
[HTC Vivid, Raider, Velocity] cruzin_cruzing:
But why would you need to, if you're on Ics hboot you could flash a gb radio and if you're on gb hboot you could flash an ics radio.
[HTC Vivid, Raider, Velocity] :
I guess to return to complete stock like gingerbread stock with the gingerbread RUU i know you can flash the ph39img but the ruu feels more official lol.
[HTC Vivid, Raider, Velocity] cruzin_cruzing:
You would need s-off to flash different radioes with different hboot, but we now have an ICS Ruu so that would be now considered stock.
[HTC Vivid, Raider, Velocity] synergye:
Definitely. I know that because I have the new hboot, I'm not going to s-off since there currently isn't a reason for me.
[HTC Vivid, Raider, Velocity] :
Out of the box stock w/e lol
[HTC Vivid, Raider, Velocity] come at me bro:
Ctuzin the only lucky one :rolleyes:
[HTC Vivid, Raider, Velocity] synergye:
If you're out of the box stock with original hboot, the new builds won't boot for you.

Yes, but it's my understanding he still had to use the download pin (unless I missed something).
[HTC Vivid, Raider, Velocity] cruzin_cruzing:
Yeah true.

:P
[HTC Vivid, Raider, Velocity] :
Beta 2.9 stuck on black screen.
[HTC Vivid, Raider, Velocity] synergye:
You're on new hboot? At work so can't get a log/kmsg.
[HTC Vivid, Raider, Velocity] :
Yes I am ill try to get a log cat. My PC doesn't like to work tho.
[HTC Vivid, Raider, Velocity] synergye:
Ok. it wasn't booting because I ****ed up the rmt_storage line by using emmc@* references (saw it in IOMonster's git awhile ago when I first set it up, and now it was having an effect). Fixed on Git. Also using new adreno libs now (supposed to be ~15% improvement), proper CAF libs, dynamic compositioning, and coposition bypass :D
[HTC Vivid, Raider, Velocity] :
Can I compile roms from the git? I was confused.
[HTC Vivid, Raider, Velocity] synergye:
Well, about to build again. You can definitely build from github though. I would recommend the android repo, not the platform_manifest repo (labeled as AOKP). That manifest isn't ready.
[HTC Vivid, Raider, Velocity] :
Is there a tutorial for that? Or is it like partially easy for a Windows noob like my self to tackle.
[HTC Vivid, Raider, Velocity] come at me bro:
Get the linux install for windows its far easier then virtual box.. its a dual boot and you can uninstall it through control panel

Look up cmc compiler or read the cubes read me

It's frustrating at first and once you cook up you normally sit there figuring out the errors
[HTC Vivid, Raider, Velocity] synergye:
OK, I'm just going to stop this right here before the thread becomes all about setting up a nix system etc (no offense to anyone). You can check out the source.android.com site, or nicandris' script without repo syncing to get you started out.
[HTC Vivid, Raider, Velocity] come at me bro:
Haha I'm a noob too

Totally forgot about syncing because I never used to sync just to grab

Looking forward to testing in a bit
[HTC Vivid, Raider, Velocity] :
Im just gonna leave the building to the Devs lol it looks like its very time consuming.
[HTC Vivid, Raider, Velocity] meatwad0222:
gonna try 3.0 now
[HTC Vivid, Raider, Velocity] :
Beta 3.0 stuck on black screen. Verified that im running the ics boot as well. adb just says waiting for device. :/
[HTC Vivid, Raider, Velocity] synergye:
Yeah, did something kind of wonky with source for that one. Someone on new hboot should try 3.1 right now since I can't test it, and also try cam since both are now recognized.
[HTC Vivid, Raider, Velocity] Marshmellow92:
does not boot. stuck in black screen
[HTC Vivid, Raider, Velocity] synergye:
3.1 boots. I'd recommend you check that the boot.img was flashed properly.
[HTC Vivid, Raider, Velocity] come at me bro:
What one? I'm on what pirate pushed out
[HTC Vivid, Raider, Velocity] :
Thats why lol
[HTC Vivid, Raider, Velocity] 1987dram:
Hi synergye

3.1 boots nice and smooth but no go on the cam
[HTC Vivid, Raider, Velocity] bigballa:
3.1 boots

black bootscreen

cant add apns...so no test on calling

hw accel looks to be working

no camera (black screen)

adb not working (waiting for device) saying MTP driver and HTC driver not installed - if anyone wants to tell me the solution ill give logcats. (tried the naked drivers)

cant mount sdcard as MTP (reboots)

no sound

looks like progress is finally being made! cant wait!
[HTC Vivid, Raider, Velocity] come at me bro:
Link me to what I have to be on with instructions if possible

I'm on ics did I miss something
[HTC Vivid, Raider, Velocity] Marshmellow92:
what the heck. i flashed the zip in the recovery and then went to fastboot, and did the fastboot flash boot boot.img
[HTC Vivid, Raider, Velocity] synergye:
Currently all known issues (mtp/logcat problems seem to have been persistent on windows). I was missing more permissions, so more should hopefully be fixed. Now at least we don't have mediaserver fault.

Don't quite know what's going on here, but just so you know, this is NOT daily driver status unless you only play tetris on your vivid.
[HTC Vivid, Raider, Velocity] Marshmellow92:
so what did i do wrong?
[HTC Vivid, Raider, Velocity] come at me bro:
I read it as I needed a new hboot lol

I'm on the firmware/hboot from the ics leak
[HTC Vivid, Raider, Velocity] Jirv311:
This comes with Tetris??? I'm gonna flash this now! :D

On a serious note, thank you for the work you're putting into this.

Sent from my HTC Vivid
[HTC Vivid, Raider, Velocity] synergye:
I don't know. No way for me to tell you given the info (or lack thereof) I've been given. Seems to be a PEBKAC issue.
[HTC Vivid, Raider, Velocity] Marshmellow92:
oh then idk. i followed the instructions. flashed the zip in recovery then i fastboot flashed the boot image.
[HTC Vivid, Raider, Velocity] :
Yea it booted but no cam,no wifi yet. :/ Looking hope full still :) 3.1 btw

---------- Post added at 07:39 PM ---------- Previous post was at 07:21 PM ----------

3.2 Stuck on HTC logo.
[HTC Vivid, Raider, Velocity] 1987dram:
3.2 Same here
[HTC Vivid, Raider, Velocity] :
Starting entire reflash procedure to double check and still stuck on htc logo
[HTC Vivid, Raider, Velocity] doktor buknasty:
What hboot version do you have? It needs to be 1.85.0025 :p
[HTC Vivid, Raider, Velocity] come at me bro:
I have 1.85.0024?
[HTC Vivid, Raider, Velocity] :
That explains it lol
[HTC Vivid, Raider, Velocity] synergye:
It will still boot on old hboot, but without the new radio, no sound/modem.
[HTC Vivid, Raider, Velocity] CasualStarlord:
3.2, cannot get past white screen, green HTC, on a velocity with Telstra HBOOT
[HTC Vivid, Raider, Velocity] synergye:
I apologize, 3.2 had a bad boot.img. I'm uploading the next build now with a new wifi setup, tons of other commits, and a new kernel with 2d/3d core overclocked( same values as kozmikkick and the other msm8660 kernels).
[HTC Vivid, Raider, Velocity] 1987dram:
Testing 3.3 now

no Wi-Fi

no Camara

no sound

no call

Going to try to flash again just to double check
[HTC Vivid, Raider, Velocity] :
Just flashed 3.3 as well same here.
[HTC Vivid, Raider, Velocity] synergye:
Just letting you guys know from the end user perspective 3.4 is the same as 3.3. IOMonster(the cubed) and I think HTC got the wlan specs wrong and we actually use a rev2 bcm4330 chip, not rev 1 due to the bad clock source error. Really working on radio right now though.

edit: we do have rev1, was a different problem.

Edit2: and 3.5 is the same to end-users as previous
[HTC Vivid, Raider, Velocity] :
Seemed like wifi worked for a split second then device rebooted.

What are the test boot.imgs for exactly?
[HTC Vivid, Raider, Velocity] zacgoesrawr:
this **** is way too complicated for my knowledge of android (and i know alot about computers, but android is a whole new game) so i'm just going to say i appreciate all of your guys' work and looking forward to the first 99% working build!:p
[HTC Vivid, Raider, Velocity] doktor buknasty:
Just tested 3.5 and it boots up, couple of things:

1. black bootscreen

2. no wi-fi

3. no radio

4. no sound

5. gallery can't detect my sdcard which has photos on it

6. camera and camcorder don't work

7. torch gives a force close

8. adb doesn't detect the phone (probably cause the drivers are not installed)

Obviously you know most of the things I've listed. Just trying to help since no one posted about 3.5 and can't produce a logcat (using windows:()

Is there any way that I could get a logcat using a mac?
[HTC Vivid, Raider, Velocity] come at me bro:
yo I read something that there was a typo on the vivid radio frequencys etc I don't know if its revelrnt at all tho but maybe peep out the skyrocket radio
[HTC Vivid, Raider, Velocity] :
What would the skyrocket radio have to do with the vivid? The LTE?