yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] synergye:
No clue. That said, we were all able to get the radio to read baseband (no longer says "no service"). Now it's just a matter of getting RIL to work right. bcmdhd.ko (wifi kernel module) was causing a kernel panic, so we needed to scrap that for now, haha.
[HTC Vivid, Raider, Velocity] Marshmellow92:
so i put the folder zip in my sd card. went to recovery and installed it then i rebooted to bootloader/fastboot usb/ fastboot flash boot boot.img

then i rebooted. did i do everything right?

all i see is a black screen
[HTC Vivid, Raider, Velocity] :
There is no boot animation for this build. Just give it some time and it will load
[HTC Vivid, Raider, Velocity] Marshmellow92:
i waited like 15 minutes
[HTC Vivid, Raider, Velocity] synergye:
If you're on old hboot, THERE IS NO POSSIBLE WAY the new builds will boot. that said, been working on getting RIL working right. Toastcfh gave us a few things to try. If you don't give a log/kmsg/dmsg, there's no way I can help you get it booting though, sorry about that. Priorities lie in getting RIL working right above helping people flash testing builds currently.

After first boot, rebooting seriously takes about 15 seconds though (I know a few guys were watching the webcam linked to in IRC thanks to deamonfish).
[HTC Vivid, Raider, Velocity] Marshmellow92:
I flashed it right I put whatI did.

IM on 1.85
[HTC Vivid, Raider, Velocity] doktor buknasty:
Is it 1.85.0025? If not, you don't have the latest hboot.
[HTC Vivid, Raider, Velocity] synergye:
Try the boot.img in the testboot.img folder on mediafire. Otherwise, I would need to see a log/kmsg/dmsg to actually know what is going wrong. You might also need to open an adb shell and rm bcmdhd.ko from /system/lib/modules (or delete from zip prior).

That said, my recommendation is to just wait. A day ago we didn't have radio firmware loading, or the phone charging. Now we have the phone charging and radio firmware loading. SIM is even recognized.
[HTC Vivid, Raider, Velocity] come at me bro:
Radios functions or no because the ril?

That's a big break through
[HTC Vivid, Raider, Velocity] synergye:
Not yet functional (RIL) but working on it and extraordinarily close :D

Calling it a night. Did a ton however, and know how to setup RIL now for our setup.
[HTC Vivid, Raider, Velocity] :
Flashed 3.7 Great news! ^_^ Phone is charging. But no wifi, storage, radio etc..

Trying alternative libril file now....

Nogo on the alternative libril.so
[HTC Vivid, Raider, Velocity] synergye:
Yeah. Frameworks thing for building libril with it. Think we figured out the issue with the old setup that was showing baseband but not loading RILJ. Look here: https://github.com/IceCreamSpaTreat...mmit/3723a7cb5061c5f911e3d360af2ef3d3754f8b61
[HTC Vivid, Raider, Velocity] :
So the interface layer is working? ^_^
[HTC Vivid, Raider, Velocity] noobsquared:
I am not sure but if I remember correctly, log nitro cm9 uses stock radio and something else stock as well. I am not an expert but in about me it showed a couple of things same as stock. Can't we use stock HTC radio in cm9 here?

Again, I don't know anything about all this stuff but I'd like to help for sure :)
[HTC Vivid, Raider, Velocity] synergye:
They also use prebuilt but have a different setup than us. We are using prebuilt though. As far as IOMonster and I can tell, we're the only ones with this configuration who haven't given up.

Edit: before anyone mentions skyrocket, we're already a bit further along than them, and they seem to have also given up on RIL.
[HTC Vivid, Raider, Velocity] :
Whats the nobody download build? Will it insta brick?lol
[HTC Vivid, Raider, Velocity] chachin:
If you download and install it on your phone... It will open the gates to hell and suck you inside your phone.. aka hell
[HTC Vivid, Raider, Velocity] htcvividnoob:
Sounds like it's a huge pain, but I really hope you guys don't give up. There's plenty of us rooting for you. Keep it up and good luck and thanks
[HTC Vivid, Raider, Velocity] :
I bit the bullet and flashed the "brick Build" needless to say i didnt get bricked. Looks like the same exact build as 3.7 even with including the new modules.
[HTC Vivid, Raider, Velocity] Brand New:
You're brave bro holy cow.
[HTC Vivid, Raider, Velocity] cannothas:
For this I am very thankful!

Sent from my HTC PH39100
[HTC Vivid, Raider, Velocity] synergye:
Hah, I thought someone might bite the bullet. Yeah, switched some flags around in that build for testing RIL.
[HTC Vivid, Raider, Velocity] come at me bro:
I have a feeling a working build is coming soon :)

Last time I had that feeling we got ics that day
[HTC Vivid, Raider, Velocity] meatwad0222:
u better be right or ill cry a long time
[HTC Vivid, Raider, Velocity] :
New RIL Tester build flashed, it cannot find my sim card apparently? lol other then that everything else is still hosed. Also reflashed and same issue with sim card but it appears that the radio is apparently starting to load which is great news!
[HTC Vivid, Raider, Velocity] bigballa:
does anyone want to point me to the right direction of what IOmonster is?

google (amazingly) didnt find anything on it...
[HTC Vivid, Raider, Velocity] randong:
That's the name of "the cubed" on irc he uses that name on there ;)
[HTC Vivid, Raider, Velocity] zacgoesrawr:
Newest build works, still no radio but a few things i noticed (maybe already pointed out) but no proximity sensor, the screenshot doesn't work, and it thinks the last time my phone looked for an update was 12/31/1969 :p

other than that seems kick ass and i cannot wait till i can leave my house with this on my phone :D
[HTC Vivid, Raider, Velocity] :
Did you get a message saying that your Sim card could not be found
[HTC Vivid, Raider, Velocity] come at me bro:
logcat pls

also if you can, a radio log

adb logcat -b radio > radiolog.txt
[HTC Vivid, Raider, Velocity] :
I'm not using a Linux box at this time unless there's a way to get it working with windows? :(
[HTC Vivid, Raider, Velocity] zacgoesrawr:
i actually did not!

and i'd give a logcat except I switched back to Dark Raider.
[HTC Vivid, Raider, Velocity] :
Interesting, I think that happened because i didnt flash the boot img that syn had provided. I just had the kozmi kernel. hmmm? anyways beta 3.8 seems exactly the same no wifi no radio things like that.
[HTC Vivid, Raider, Velocity] come at me bro:
I'm thinking since its not an HTC rom its not a HTC phone per say

In other words I'm thinking we need something other then the HTC drivers to logcat even though we can still fast boot and get the CPU to connect to the device

Most likely wrong but its a idea

I know i was able to connect on the very first builds
[HTC Vivid, Raider, Velocity] zacgoesrawr:
logcat worked for me?

i was using adb for mac

adb isn't HTC only, it's actually all android
[HTC Vivid, Raider, Velocity] come at me bro:
I'm saying maybe we need a aosp driver or something to dump log cats on windows idk

Edit

Like we do not have the correct driver

I think everyone knows the command to dump a log cat christx
[HTC Vivid, Raider, Velocity] christx:
you can issue the logcat command within adb...

https://sites.google.com/site/androidhowto/how-to-1/save-logcat-to-a-text-file

To save LogCat to a text file open up a terminal window and type:

adb logcat -d > logcat.txt
[HTC Vivid, Raider, Velocity] :
Anybody else flashed the 3.8 build?
[HTC Vivid, Raider, Velocity] :
Tried it with the same results as 3.7
[HTC Vivid, Raider, Velocity] Crimson Ghoul:
yup.. no boot here either. flashed boot.img before and after flashing. it didn't boot at all
[HTC Vivid, Raider, Velocity] synergye:
Yep. I know what the problem is. Thank you. I will start building more and upload a working beta when I get home.
[HTC Vivid, Raider, Velocity] Crimson Ghoul:
awesome.. and sorry I couldn't get you the logcat.. it would just freeze :/
[HTC Vivid, Raider, Velocity] come at me bro:
I put my logcat in my last post
[HTC Vivid, Raider, Velocity] synergye:
Thank you for it also. I'm home and am now starting to work on fixing the issue (feel kind of stupid for overlooking it), and I'll upload the update as test5 as soon as it's done. Really I'm just working on making this less hacky, and practically needed to start over to do it. I've moved the old build that worked fine into a different folder on my laptop awhile ago just in case at the end of my compile day it comes down to uploading that and settling for it (no proper gpu accel with new libs in it or speaker audio). Also with less than half an hour build times, testing over and over again on my own can get kind of overwhelming.
[HTC Vivid, Raider, Velocity] jmone:
beta 5 just boot loops for me - I'll try to grab a log

---------- Post added at 06:30 PM ---------- Previous post was at 06:17 PM ----------

I did not get anything in the logcat during the boot loop (it would do the HTC Logo 1 --> HTC Logo 2 --> Telstra Logo --> reboot).

I did get this from logcat in one of the modes if it is any help:

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

/sbin/sh: exec: line 1: logcat: not found
[HTC Vivid, Raider, Velocity] synergye:
Yes it does. Damn. I think I refixed USB debugging, and will test once this new build's done.

Edit: USB debugging works for me in that test. I'm assuming your partition layout must differ. Well, moving on.
[HTC Vivid, Raider, Velocity] jmone:
No harm done, just reinstalling the boot.img and ROM from WCX.
[HTC Vivid, Raider, Velocity] synergye:
OK. Check my edit above. Strange it didn't work for you. I'm guessing it didn't format as ext4? Well, I got what I needed and am moving on now.
[HTC Vivid, Raider, Velocity] contactwajeeh:
Mine is stuck at the htc screen. Not even booting up... :(
[HTC Vivid, Raider, Velocity] synergye:
OK. Next test build almost done, and I'll test. Will work on this for the next few hours.
[HTC Vivid, Raider, Velocity] 78cortina:
Is this working in the velocity 4g telstra phone. I am more than happy to test.
[HTC Vivid, Raider, Velocity] synergye:
Please let me know! I'm about to test the build uploaded as "test6" on a vivid.
[HTC Vivid, Raider, Velocity] doktor buknasty:
Is there any particular reason why the rom gets flashed first then the boot.img?
[HTC Vivid, Raider, Velocity] meatwad0222:
It probably doesn't matter all that much...ill try it and post results
[HTC Vivid, Raider, Velocity] synergye:
No. If it's easier to do it the other way I don't think it should affect it. I guess with an app it might be easier switched.

Edit:Meatwad, I would wait until 5 or 6. I have personally tested 5.
[HTC Vivid, Raider, Velocity] contactwajeeh:
how was the tests with test6.... mate...?
[HTC Vivid, Raider, Velocity] synergye:
I guess I wasn't paying attention on counting. I meant to say 6. So wait for 7 or 8.
[HTC Vivid, Raider, Velocity] come at me bro:
Booting up yet? I wanna test but I won't

Be near a CPU for like 12 hrs , my only way to flash a bootimg is the GUI app
[HTC Vivid, Raider, Velocity] synergye:
Then I recommend waiting until I get to the beta, or upload the old build.
[HTC Vivid, Raider, Velocity] :
Yep thats what i figured. No message about a missing sim card?
[HTC Vivid, Raider, Velocity] :
Nope.. still receiving an error when attempting to locate carriers of course
[HTC Vivid, Raider, Velocity] :
I think it was because i was using the stock kernel like i didnt flash syns kernel. I might try to reproduce it but first im flashing the new build that was just uploaded.
[HTC Vivid, Raider, Velocity] synergye:
New build *should* have working adb for windows users. That's what I'm testing. Currently need a log for bootup. Also, baseband should also still be showing up (difference between 3.7 onward).
[HTC Vivid, Raider, Velocity] :
Log cat is still waiting for device. Device is no longer charging. Stuffs getting worse were going backwards 8U lol
[HTC Vivid, Raider, Velocity] synergye:
Haha, okay. then stock init.usb.rc is a nogo.
[HTC Vivid, Raider, Velocity] :
New Ril tester appears to have same issues but charging via usb has been restored flashing nitro test now. Nitro also the same issues nothing appears to have changed.
[HTC Vivid, Raider, Velocity] synergye:
Both have had changes, just none that the end-user can recognize. They both need a logcat and radio logcat to proceed, and I even added a log app so users may get logs and copy them to storage, then grab them from recovery while on windows.
[HTC Vivid, Raider, Velocity] :
It doesn't allow access to storage on my phone. It says cant find directory when I try to pull it
[HTC Vivid, Raider, Velocity] 1987dram:
Hi,synergye

A quick question I just picked up a spare laptop and was wonder what OS you would you suggest for testing?
[HTC Vivid, Raider, Velocity] iStatiK:
Most use Ubuntu
[HTC Vivid, Raider, Velocity] :
Any one tested the Nitrolib test ? I was unable to get it to boot.

--------------------------

Also no logcat b/c drivers will not install on windows.
[HTC Vivid, Raider, Velocity] :
I did it booted but i couldnt get log cat.
[HTC Vivid, Raider, Velocity] :
@Imftmf Which boot.img did you use? I used the one in the folder and kozmikkick's but neither booted.
[HTC Vivid, Raider, Velocity] :
The one in the folder. Did you flash twice?
[HTC Vivid, Raider, Velocity] :
Didn't never had to... hummm.
[HTC Vivid, Raider, Velocity] :
I created a batch file to flash it twice I always read that it was good to flash it twice. Maybe not?
[HTC Vivid, Raider, Velocity] :
Flashed 4.0 appears to be the same to end user. When i try to use the GetLogs app it says data.txt: open failed: Enoent (No such file or directory)
[HTC Vivid, Raider, Velocity] Aus_Azn:
Just out of curiosity, once we get working CM9, how hard is it to compile a working build straight from AOSP source? Would the CM9 implementation be "hacked to hell" meaning that there are actual software-side tweaks, or would it give a strong-enough framework that you'd be able to flash an Android version straight from source?
[HTC Vivid, Raider, Velocity] synergye:
If you mean a straight AOSP build over CM9, AOKP, or Evervolv, quite easily.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
I'm just wondering, but is it actually easier or would it be the same to port ASOP instead of CM?

also since the build being used (at least so i thought) is nexus, why not use the Sensation's CM build and modify that, they're so similar that it'd seem like little would have to be done?

i am obviously uneducated with the whole ASOP roms but it just seems logical to my ignorant self lol
[HTC Vivid, Raider, Velocity] htcvividnoob:
I'm pretty sure you can't just take a port and drop it onto our phone. Device specific files such as drivers and the RIL (radio interface layer) and lots of other things need to be modified to work with our phone. The biggest thing seems to be getting RIL working, and that will make it a lot easier to port over AOSP/MUIU/etc, it seems like it's not any easier to get AOSP on there else that's probably the route they would have taken. It's a complicated process which people are working hard at.

Out of curiosity, does anyone know if getting CM9 working will make it easier to get Sense4 or are the RILs completely different?

I'm no expert so feel free to correct me if I'm wrong.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
reading about why Sense4 hasn't been ported yet is because of it so deeply "tying" with the drivers, that it's just as hard as "removing" sense
[HTC Vivid, Raider, Velocity] synergye:
We have a better understanding of what is needed for RIL, which is also helping the sense guys. You can take a few commits and our device repos to build straight AOSP, AOKP, Evervolv, or whatever your favourite source variety is. We're doing source building though, not precompiled copy and pasting, so it's quite a bit different.
[HTC Vivid, Raider, Velocity] synergye:
Edit: Zacgoesrawr, we're not using a nexus build, but using source. You can check the manifest on the github page to see where the repositories are being taken from. At this point most are from CM, or CM based (the playground).

Edit: this was a failure. Meant to edit the previous post, not quote.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
oh gotcha i thought i saw before it was from the nexus i probably was skimming something and made that up lol sorry
[HTC Vivid, Raider, Velocity] :
Flashed build 4.1 still no radio,wifi,usb with windows,sound,storage. Something to note which i've posted before. Flashing the kozmi kernal causes a no service message on the lock screen. Where flashing the attached boot.img doesn't initialize the radio. Unfortunately the kozmi kernal causes force closes all over the place so its impossible to see whats really going on.
[HTC Vivid, Raider, Velocity] synergye:
The fcs might be why. RIL is still a WIP and needs some framework changes now.
[HTC Vivid, Raider, Velocity] kozmikkick:
To be exact. Sense 4 port has not been release because of ril not working yet. Everything else works just as well as on our sensation sister. And no working ril on asop or cm9 will not really make a difference. The framework is different.
[HTC Vivid, Raider, Velocity] Brand New:
So porting from the Sensation/Evo 3D is harder than it looks?
[HTC Vivid, Raider, Velocity] kozmikkick:
Porting is very easy. Ril is not though it takes a lot of smali coding to get it working.

But let's keep on topic. This thread is about ASOP not sense 4 :cool:
[HTC Vivid, Raider, Velocity] zacgoesrawr:
Logcat for 4.1

Radio Logcat too

Edit: I flashed Kozmick's Kernel and noticed that the notification led is orange instead of green since my phone is actually charging. without it, it was green but in the settings it said it was charging still.
[HTC Vivid, Raider, Velocity] randong:
I kno I don't say much in here but...did yall guys give up on cm9 and are just goin for the asop build ...either way I'm glad to see so much effort into this ...good luck guys
[HTC Vivid, Raider, Velocity] cruzin_cruzing:
They chose AOSP because the source is cleaner. Once they get AOSP working, CM9 will be super easy to compile.
[HTC Vivid, Raider, Velocity] kevsthabest:
The joys of multiband radios with LTE :/ hopefully the new route your taking is going to push us a bit more forward.

I have to say the ril is a real pain in the butt. Once we get this hurdle passed it should be alot easier then. And with the new source maybe the WiFi will work without too much hacking!
[HTC Vivid, Raider, Velocity] Aus_Azn:
OHH SNAP.

This is exactly what I've been waiting for. Unfortunately, courtesy of no s-off and my work laptop lacking HTC Sync drivers, I don't really think I can beta test, as much as I want to....
[HTC Vivid, Raider, Velocity] synergye:
That route was too big of a pain in the ass. It was like building ICS when the source first dropped. So now going the other route of fixing up source for the other radio states. I think I know what needs to be done for wifi both kernel and source wise regarding changing the wpa supplicant in use and symlinking, but focusing on one thing at a time.

Edit: changed it to AOSP because the source we're using is varied, and FWB/Settings is mostly from ThePlayground, which isn't vanilla CM.

Edit2: Happy Holiday to anyone who partakes.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
seems like Mac's adb finds drivers a little more reliably than windows (no drivers needed, kexts > drivers ;;;) (i don't know about linux, im sure it's the same as mac) if logcats are needed and not accessible let me know and I'll run em'
[HTC Vivid, Raider, Velocity] homeslice976:
Happy Holidaze. I've been watching this closely - progress looks great. Excited to see the completed project - I loved your ICS build on the Inspire/DHD
[HTC Vivid, Raider, Velocity] davezaff:
Happy holiday.:)
[HTC Vivid, Raider, Velocity] 1987dram:
Beta4.20

Holy crap!! Very Cool!! Thank you for the hard work! looking good!!
[HTC Vivid, Raider, Velocity] zacgoesrawr:
4.20 has some sort of RIL working!!!!

no screenshot function yet

EDIT: TEXTING WORKS!

EDIT 2: No mobile data, bluetooth, or wifi

Good job devs i'm really impressed!!
[HTC Vivid, Raider, Velocity] DeamonFish:
Try adding an APN for data.

Also, DDMS can take screenshots.
[HTC Vivid, Raider, Velocity] come at me bro:
anyone tried the apn
[HTC Vivid, Raider, Velocity] Leigh Kennedy:
Trying as soon as 4.20 finishes downloading.

RIL is definitely working if you can SMS.

SMS requires no APN to work while Data and MMS does.

Anyway, we shall see.

---------- Post added 22nd April 2012 at 12:32 AM ---------- Previous post was 21st April 2012 at 11:36 PM ----------

UPDATE:

APNs will not save. APN is a no-go.

Wi-Fi obviously not working seeing it does not see a MAC Address when I look at advanced WiFi settings lol
[HTC Vivid, Raider, Velocity] come at me bro:
Ahhh inching away at perfection
[HTC Vivid, Raider, Velocity] jenkem110:
holy crap. props to the devs on getting ril working enough. now i feel like we are just around the corner from a daily user build. seems like changing to aosp instead of cm9 was a great idea. will def be using this when wifi and apns work.
[HTC Vivid, Raider, Velocity] thecubed:
Here's a quick video update!

http://www.youtube.com/watch?v=IqEV71BqVjM

Stuff is happening often, we're very close to having audio fixed and RIL figured out.
[HTC Vivid, Raider, Velocity] joshua54:
New video looks great! I can't wait till this is up and running, thanks for all the hard work guys!
[HTC Vivid, Raider, Velocity] cannothas:
Good to see you again, excited for awesome progress to go with an awesome phone!

Sent from my HTC PH39100
[HTC Vivid, Raider, Velocity] kozmikkick:
Looking at the video I see you're using a 2.x kernel. I think you need a 3.x kernel build for WiFi to work at least without hacking it.
[HTC Vivid, Raider, Velocity] kozmikkick:
I don't really have a lot of time to build an asop kernel right now but I believe tiamat said he'd provide a none oc asop kernel if asked. Might be useful.
[HTC Vivid, Raider, Velocity] come at me bro:
Let's try to get him on irc later if its cool with everyone
[HTC Vivid, Raider, Velocity] thecubed:
We actually have tried a few things so far in regards to wifi, and using the bcmdhd.ko module that replaces bcm4330.ko gives us CRC errors in dmesg upon loading the module, shortly after that the bus crashes and the module goes offline.

If you have any experience with this, I would greatly appreciate your input or help. Stop by #htc-holiday on irc.freenode.net if you get a chance. Just ask for IOMonster (me) or Synergye.

Thanks much!
[HTC Vivid, Raider, Velocity] synergye:
About to try a new 3.0 kernel setup/wifi device setup to load the fw. I believe we were having kernel issues with the wpa supplicant we were using, but it could have been a lot more. It's my understanding that people have even been able to load 4330 firmware through the 4329 module (trying to use the unified bcmdhd layout now however).

Anyone who might feel they're able to help, or provide info is always welcome on IRC. One of us is usually on.
[HTC Vivid, Raider, Velocity] kozmikkick:
Should work using the same 3.0 setup for WiFi as our sense kernel along with the same WiFi firmware
[HTC Vivid, Raider, Velocity] synergye:
We use a rev.1 bcm4330 chip though, correct? The stock init.holiday.rc from ICS has "-puse_p2p_group_interface=1" in it, which I thought was reserved for rev.2 firmware, since only rev.2 firmware has the p2p firmware. The ICS OTA/RUU includes both sets of firmware.
[HTC Vivid, Raider, Velocity] kozmikkick:
Yes I'm pretty sure its rev 1 not positive though. Not at home so I can't check to be certain.
[HTC Vivid, Raider, Velocity] come at me bro:
I heard we have the same chip as the rezound

Check it out
[HTC Vivid, Raider, Velocity] synergye:
yeah. Thinking HTC's build.prop and specsheet is wrong because of that line they use. Also according to the spec sheet, we have rev1, they have rev2 so they are different chips since there are calls which are rev2 specific.
[HTC Vivid, Raider, Velocity] chachin:
derp
[HTC Vivid, Raider, Velocity] come at me bro:
I remember saying that we should grab stuff from the skyrocket and rrzound but it got shot down I forget what but they listed something wrong on the vivid and it was correct for us on the skyrocket

Ugh brain fart lol

Edit- mighta been something with LTE