yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] zacgoesrawr:
will s-off help in any way? i know some devices need s-off for CM. or is it just so it works on any carrier?
[HTC Vivid, Raider, Velocity] kozmikkick:
S-off means absolutely nothing. No device actually needs s-off to build cm or asop. That is a fallacy.
[HTC Vivid, Raider, Velocity] Leigh Kennedy:
I laugh every time someone says S-OFF is needed...
[HTC Vivid, Raider, Velocity] KCutrer1:
Go easy on the guy, he didn't know.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
i don't think they meant it bad towards me lol

i was just reading the pages on CM's wiki lmao.
[HTC Vivid, Raider, Velocity] Leigh Kennedy:
Of course not mate. It's all good :-)

We all have to start off somewhere.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
hey i think im doing pretty damn good for being on android for 2 months now lol. anyways, i've seen alot of great progress on github, ;)

EDIT:

logcat for 4.3 coming

backing up then flashing!

EDIT 2: logcat keeps repeating (with some more text as well):

I/ServiceManager( 234): Waiting for service media.audio_policy...

I/ServiceManager( 117): service 'media.camera' died

I/ServiceManager( 117): service 'media.audio_flinger' died

I/ServiceManager( 117): service 'media.player' died

W/AudioSystem( 234): AudioPolicyService not published, waiting...

I/ServiceManager( 234): Waiting for service media.audio_policy...

I/ServiceManager( 234): Waiting for service media.audio_policy...

I/ServiceManager( 234): Waiting for service media.audio_policy...
[HTC Vivid, Raider, Velocity] 78cortina:
Flashed 4.3 did not boot only got black screen. Velocity 4g. Sorry can't log cat don't know how.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
it's what mine did except i had logcat running

and to use log cat, plug in your phone and open terminal or command prompt:

/path/to/adb logcat

for a specific part:

/path/to/adb logcat -b radio(or other)
[HTC Vivid, Raider, Velocity] 78cortina:
Thanks bud ill give it a crack next time I get a chance to test.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
flashed 4.4

setup wizard has some problems

welcome screen comes up and after setting time goes to "just a sec" and goes black.

EDIT:sound works! at least on the emergency dialer LOL

EDIT2: i flashed again and managed to get through setup. System UI kept crashing though 2nd logcat is from that
[HTC Vivid, Raider, Velocity] synergye:
I'm on my way home and can test more then. Sound and wifi should work. Regarding the setup wizard, doesn't look like you fully wiped before flashing, otherwise you can skip setup wizard my pushing either home or holding back button (don't remember).
[HTC Vivid, Raider, Velocity] zacgoesrawr:
my second install i wiped everything again to make sure. then i got to the systemUI problem.

the wifi turned on but i couldn't scan or anything.

audio is a huge leap though! lookin' good :D
[HTC Vivid, Raider, Velocity] synergye:
Thanks again! Think I got to the bottom of the out of pmem errors in the new kernel.

Rebased of KozmikKernel, and just increased pmem sizes back up to what we were running in 2.6* kernel in his kernel (for initial, he only had 16mb set, I updated to 64mb, and changed doubled smi base, plus added +16mb to fb pmem). Now will be adding fast charge to the kernel, and also setup a sysfs interface for sweep2wake and settings checkbox (if there isn't already a sysfs interface for sweep2wake, haven't really looked yet). We're getting closer and closer to data functioning also. At least after this calls can be made/wifi can be used :D
[HTC Vivid, Raider, Velocity] zacgoesrawr:
i hope my logcats are helping since i cant do anything on the dev side haha
[HTC Vivid, Raider, Velocity] :
Tested 4.5 crashed at the setup screen. Tried multiple button combos but was unable to bypass the setup. I was able to see the logcat, on windows, but I was unable to get it to save.
[HTC Vivid, Raider, Velocity] Marshmellow92:
where do i open a command window to get a logcat?

just a regular one? or under a pecific folder
[HTC Vivid, Raider, Velocity] :
Regular cmd but change dir to the location of your adb. Example my adb is in an android folder c:\android
[HTC Vivid, Raider, Velocity] zacgoesrawr:
you can also get technical with it and put it in your bin. then you can simply run it by typing 'adb' i dropped both that and fastboot in there.

Also I'll get the logcat for 4.5 once i get home, 2 my time, so like 4 hours :)

I'd do it here except I don't have my usb to flash the kernel.
[HTC Vivid, Raider, Velocity] synergye:
Thank you, but not needed. You'll get graphics corruption from a kernel attempt to allocate a negative size.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
should i try the .6 or would that one not work?
[HTC Vivid, Raider, Velocity] contactwajeeh:
.6 is the new build. Nobody has tested as of now I believe? Please go ahead and post the logs...
[HTC Vivid, Raider, Velocity] zacgoesrawr:
logcat for 4.6

the screen stays black but buttons respond.
[HTC Vivid, Raider, Velocity] :
Had the same experience. On windows the driver now shows as a HTC device. Also i can tell that setup is working b/c when I was randomly tapping on the screen I heard the sound of the keyboard.

______

Logcat pulls now but it only saved the first couple of seconds of info....
[HTC Vivid, Raider, Velocity] Leigh Kennedy:
Looks like we're up to getting gfx and pmem sorted...
[HTC Vivid, Raider, Velocity] Marshmellow92:
i opened a command window where my adb file is and i type the logcat code you put and i get : the system cannot find the path specified.

edit -

wow im retarded haha

nvm i got it i was typing out path/....

i didnt know i just had to put adb logcat haha

anyways i formatted in recovery flashed rom then flashed the boot.img and no boot :( i dont know if im doing everything right

here is the logcat for 4.7
[HTC Vivid, Raider, Velocity] zacgoesrawr:
black screen but responsive buttons here,

marshmellow92 did you completely wipe everything including dalvik cache? it looks like something didn't wipe from looking at your logcat,
[HTC Vivid, Raider, Velocity] Marshmellow92:
yup everything.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
if you got a logcat at all it must have booted. logcat can't run unless it's booting.
[HTC Vivid, Raider, Velocity] Marshmellow92:
But it was blackscreen for like 10 minutes
[HTC Vivid, Raider, Velocity] zacgoesrawr:
it's all that's going to happen until what synergy mentioned before is fixed
[HTC Vivid, Raider, Velocity] zacgoesrawr:
should I flash 4.8 when i get home for the logcat?
[HTC Vivid, Raider, Velocity] Marshmellow92:
You don't think its work for me?
[HTC Vivid, Raider, Velocity] :
Flashed 4.8 and was unable to pull a logcat in windows b/c phone was never recognized. I was able to get though setup and I was able to search for mobile networks and it did locate AT&T. When I attempted to register if failed but when I called my self I was able to accept a call. When I called out I the call was made but couldn't hear myself, a no sim or sim error was displayed on the call screen. Attempted a screen shot but received the message couldn't capture screen shot. When I attempted to scan for a wifi network the phone crashed and rebooted.

After all this I flashed the kozmik kernal RC 1 it was dectected in ADB, but everything crashed.
[HTC Vivid, Raider, Velocity] synergye:
It's a sense kernel, this is Aosp. The screenshot issue is do to SD. Don't yet know what's going on with call audio, but seems wifi needs more work still. Pulled a true all-nighter working on kernel.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
When I tried to sign into my google account in setup it got mad and bootlooped. but here's the logcat, i'll do another after wiping and reflashing and NOT saying sign in lol
[HTC Vivid, Raider, Velocity] Kraizk:
This is slightly off topic but thank you for being one of the last reasonable developers in the Holiday thread.

<3 Bromance
[HTC Vivid, Raider, Velocity] MisterSchnapps:
Really syn. Thanks!
[HTC Vivid, Raider, Velocity] zacgoesrawr:
did anyone else have the problem of the phone crashing then bootlooping when trying to access wifi settings? it happened both times i flashed.
[HTC Vivid, Raider, Velocity] :
On 4.8? Yes I had the same issue.
[HTC Vivid, Raider, Velocity] jenkem110:
flashed 4.8 and got boot looped when trying to set up wifi, but if skipped you can get to the home screen and it worked pretty smooth. maps kept crashing and microphone doesnt work but both speakers work. doesnt show that i have any bars unless i make a phone call. making good progress. keep up the work man. sorry i cant provide logcat.
[HTC Vivid, Raider, Velocity] :
I second this even tho i got rid of my vivid because this was really the only rom i was interested in. And the fact that there's only like 5 or 6 developers here still. Epic post btw :) http://xdaforums.com/showpost.php?p=25447753&postcount=42
[HTC Vivid, Raider, Velocity] Leigh Kennedy:
Yeah, we're all pretty upset about the tantrums that go on in this forum alone.

This is why most of us tend to leave. Last thing we want is to be on the firing line and accused of "stealing" someone's work despite the fact it was never really their code to begin with.

I'm also wanting to jump ship to One X to do my developing as the Vivid forum is getting more ridiculous tirades than my 15-week-old son having his milk with-held from him.

People need to grow up fast before the Vivid forums loses all of us for good.
[HTC Vivid, Raider, Velocity] Jirv311:
I'm anxiously awaiting the S3 release so I can bid by Vivid farewell. Not sure what it is about HTC forums but they seem to be filled more with drama than any sort of community development. The Samsung forums are rarely this way. You post something, you expect people to use it. That's how its always been. It's the primary reason I posted my base ROM. In hopes there might be a bit more "dev" happening but I think everyone is too spooked to do anything now. It's just sad.

On that note, thanks to those helping to bring AOSP to the community here. :D

Sent from my HTC Vivid
[HTC Vivid, Raider, Velocity] :
They basically just defended there stupidity. With more stupidity but anyways on to bigger an better things.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
as much as it sucks there are selfish ignorant people on here. Synergy, the cubed and everyone else who;s helped with the ASOP development have been more than amazing by working on this! i hope a couple of sob's don't stop you from developing.
[HTC Vivid, Raider, Velocity] synergye:
Totally different game as far as we're concerned. Was just ridiculous to have some very talented developers who have been helping others out the whole time be accused of stealing something which isn't even owned by another developer. Trust me, we're not stopping development, just have hit kind of a big turning point and have been pushing through. Cayniarb's also been a huge help, and working on adding holiday support to his 3.0 kernel via totally new board files separate from htc's board-holiday.

A quick note. There are quite a few very talented developers helping each other out non-stop on the holiday. Once we get RIL totally out of the way, you will start seeing more ports, etc from many talented developers. Quite a few are just waiting for full RIL. It's easier to get going in source than decompiled java frameworks, and they're really waiting on that to occur. So I don't want anyone to think Vivid development is dead since there's just a small hump we are working on getting over. Really fully working AOSP RIL is propbably going to happen first, then other devs who have been holding back will start releasing their awesome work.

Now as much as I agree with what has been said, I really want this thread to go back on topic. Thank you.

Edit: thus far the amount of community cooperation out of Holiday devs has been superb and mostly behind the scenes so far. Far better than any other community I've been apart of.
[HTC Vivid, Raider, Velocity] kevsthabest:
thing is most people dont see the cooperation going on since alot of it is offsite from XDA. I'm glad we have the dev's we do. and once we get this RIL issue behind us, this phone will be great! (not that it isnt yet!)
[HTC Vivid, Raider, Velocity] come at me bro:
Exactly no one sees the irc team
[HTC Vivid, Raider, Velocity] Aus_Azn:
So maybe we should just move everything offsite. :rolleyes:
[HTC Vivid, Raider, Velocity] come at me bro:
Got the vBulletin license :)
[HTC Vivid, Raider, Velocity] :
By doing that your just doing what everyone one else did the xda community is all that some people know.
[HTC Vivid, Raider, Velocity] Aus_Azn:
It's all I knew, having come from the Captivate.

The advantage of XDA is the large network. Looking at other sites like Rootzwiki, private sites and the like, there's a noticeable lack of activity. As a positive, you could get the notion that "only those who care would dare" to actually switch to another forum.

I don't really understand why this became such a ridiculously hostile environment with the Holiday. Sure, there's the matter of this licence adherence or whatever, and the notion of crediting others, but I really fail to see why this descended into a mud-slinging battle. The Captivate and GT-i9k forums were never like this. It was what sold me on XDA being a pleasant environment for devs and end-users alike.

If you want to waste some time, feel free to look at my post history. You'll probably quickly notice when I began to get frustrated at the incompetence here and why.
[HTC Vivid, Raider, Velocity] thecubed:
No matter what happens, we will continue working on this project. It's not fair to let a few bad apples spoil the bunch.

I would like to thank developers like Cayniarb, pirateghost, Leigh Kennedy, and contactwajeeh (sorry if I used IRC-only names, I'm going off the top of my head) for keeping the community alive and well, as well as putting in so much work into this device. Without developers, a community fails and breaks down into anarchy.

So far, the biggest problem I've seen is the fracture between us IRC-mostly devs, and XDA-only devs. When the lines of communication are strained, it makes it very hard to stay 'on the same page' as everyone else. What may have started as a simple miscommunication now is ballooning into a issue with personal feelings attached to it.

As for me, I will continue developing oblivious to what is going on XDA. I urge other developers to do the same. Keep doing what you're great at, and let the idiots squabble away.

With that said, I do not mean we should simply withdraw totally from XDA and other forums alike, I merely mean we should not feed the trolls.

I would like to thank all of the people following this that have refrained from falling into the madness, let's continue to make this community great and prosperous.

I have one last sentiment to express: if someone offends you, in real life or online, try to work it out with them first privately. If they continue, arrange a second meeting with them in a semi-public way. Try to come to a reasonable agreement. We don't need drama :)

Thanks all!
[HTC Vivid, Raider, Velocity] zacgoesrawr:
amen thecubed couldn't say it better myself,

now back to business :cool:

I can sense RIL working soon ;)
[HTC Vivid, Raider, Velocity] Leigh Kennedy:
Amen! You couldn't have said it better broseph
[HTC Vivid, Raider, Velocity] :
Back to business... Flashed 4.9 skipped through the setup attempted to activate wifi and the phone crashed; bootlooped actually. AT&T was recognized as the carrier and I was able to make and receive calls, but audio only worked on my phone, person on the other phone could not hear me. I was able to attempt to setup an apn but it would not save. Windows drivers still didn't install so no logcat... Sorry
[HTC Vivid, Raider, Velocity] zacgoesrawr:
Is this where I come in? lol.

After i backup i'll flash..
[HTC Vivid, Raider, Velocity] come at me bro:
Isn't it ironic that a apple computer is helping build google software lol
[HTC Vivid, Raider, Velocity] zacgoesrawr:
Well OS X is built off of NetBSD so it's a form of linux and so is android.:p

Also synergy have you considered about making the boot.img flashable in the .zip? it'd make logcat-ing much faster ;)

logcat below. i sent a text to myself to see show send and receive (may not help anything but i figured the more the better)
[HTC Vivid, Raider, Velocity] synergye:
If you're s-off it will flash in the zip. You don't even need to download the boot.img. I'm not s-off, and know a few others who aren't, so have been uploading the boot.img separately also with no additional work required from me. The boot.img is the same as the one in the zip, and the updater-script will flash.

Also, thanks for getting the logcat. I actually uploaded for someone whose build was taking a bit, and ended up forgetting I uploaded it. Quite a bit changed, but nothing as far as usability goes in this build.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
oh i never knew that!

and regardless if I notice a change in the usability it doesn't matter, if it helps us move forward i'm more than happy to take a few minutes to get a log :)

and if you need me to compile a build I have my iMac downstairs. It says i5 in my sig but it's i7. I have MacPorts on it and I can run my macbook in disk mode and boot to ubuntu. (uses the computer like a bootable disk, and uses the hardware of the computer booting it)
[HTC Vivid, Raider, Velocity] kxhawkins:
Wow, sorry for OT, but OS X is NOT a form of Linux. At all. Ever.
[HTC Vivid, Raider, Velocity] cruzin_cruzing:
Mac OS X takes core components from Darwin, a Unix variant. Linux is actually another variant of Unix. They are related but no, Mac OS X is not actually based off of Linux.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
it's core is unix so i think linux my ignorance w/e w/e w/e :rolleyes:

where i got confused was Darwin, Apple's kernel, it's core is heavily based off of FreeBSD, Also it's framework has bits here and there as well. the trustedBSD MAC framework is in it's security features. FreeBSD is Unix-like BSD, i thought it was actually Linux.

MA BAD

now back to sweet ASOP~
[HTC Vivid, Raider, Velocity] zacgoesrawr:
Should I logcat the pmem test or wait for another beta?
[HTC Vivid, Raider, Velocity] synergye:
Nah, don't worry. Was just from when I was at work, and no logcat is possible.

Thank you though!
[HTC Vivid, Raider, Velocity] come at me bro:
Synergye, fell asleep my bad
[HTC Vivid, Raider, Velocity] :
Do we need to test any of the pmem test?
[HTC Vivid, Raider, Velocity] synergye:
Nope. Thank you though. Quick update for all of you:

Working on kernel trying to redo the horribly lazy way HTC setup pmem (basically the improper for 3.0 way). Basically going for more of a 2.6 CAF pmem layout. Then also on the kernel side of things, Cayniarb is working his ass off on a totally new CAF 3.0 kernel without using our board files. This is very promising and exciting, however we've been getting an error that Cayniarb hasn't yet figured out, nor myself and anyone else who's gone through source.j

You're probably wondering why we're not just using the old 2.6 kernel we had been using. This is because the kernel had quite a few issues that just aren't worthwhile to debug and work on (if you saw a kmsg from that 2.6 kernel, you know what I mean). Also, it would appear that the mic problem is actually related to kernel. So basically we're at the point of needing to work on this to continue. That said, there are still members of our team such as TheCubed who are working tirelessly on RIL, and we already have a pretty good understanding of what's going on there, and even partially diagnosed one of the no sim issues from the awesome RIL Class work rmcc's been doing.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
Hey synergy i've been creepin' through the github regularly, what are the ION fixes? When I think ION i think Nvidia ION boards lol
[HTC Vivid, Raider, Velocity] aaki_rocker:
which is the latest versions !!

i am confused as there are lot of files in the download link ! :p

and can i flash it on s-on ?

thanks.. :)
[HTC Vivid, Raider, Velocity] synergye:
Those aren't functional, sorry. Added ion support to rom and kernel with lots of CAF parts, but trying to find sizes that work with frame buffer. Thank you though. Very close. Oh, s-off isn't needed.
[HTC Vivid, Raider, Velocity] aaki_rocker:
ok i flashed the ion rom and the kernel through fastboot !!

after the green htc logo, it bootlooped everytime !

i even extracted the boot.img from the zip file and flashed through fastboot, still no luck ! :(

any workaround for it ?

also can other kernels like faux, kozmik's etc be used with this rom ?

thanks a lot :)
[HTC Vivid, Raider, Velocity] :
Sense kernels, faux, kozmik's etc will not work with this rom. Some rom test may not boot we are still testing this is not a fully functional rom at this point.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
let me know when you need a logcat :p
[HTC Vivid, Raider, Velocity] synergye:
As I said, not yet functional. Been doing a lot of work with kernel. Look at kozmikkernel repo on git if you'd like to see what's been done.

ION is a memory allocation system to work as a pmem replacement. It *should* actually help sense4 devs porting from 8960 also.
[HTC Vivid, Raider, Velocity] bigballa:
You guys are working tirelessly on this. Sure hope you know its appreciated.

I just bought a one x yesterday and I'm thinking of returning it because I think att will allow a bootloader unlock after they announce the next Gen HTC phone. Cuz they did the same thing with the vivid to the one x :-(
[HTC Vivid, Raider, Velocity] aaki_rocker:
i tried beta 4.9 started camera and it says "can't connect to camera" !

in settings, i get fc on storage and apps ?

rest of the rom is pretty good !

any fixes to the issues i mentioned above !

thanks.. :)
[HTC Vivid, Raider, Velocity] zacgoesrawr:
This is still very deep in the betas... if you read the very first post it says somethings may not be functional in the builds...
[HTC Vivid, Raider, Velocity] Aus_Azn:
The sole reason why I don't actively participate in testing (or by proxy, complaining) about this ROM is because I have no logcat to give.
[HTC Vivid, Raider, Velocity] aaki_rocker:
ok so which is the most preferable and better build out of all the builds in the download link ?

thanks.. :)
[HTC Vivid, Raider, Velocity] :
Testing has reached beta 4.9. We are waiting on synergye to hear what the next build is that needs testing. This is not a rom that has a better build this is all testing and re-testing. Since this is a "dev chat area" lets keep the comments to the builds and results of testing.
[HTC Vivid, Raider, Velocity] synergye:
Currently none due to no mic. I suppose you tested the most end user friendly at this point. Once I fix the frame buffer issue in ion kernel, we'll have mic and wifi. I will let you know when that happens with an RC0 on thread title. Getting no ion errors in kmsg, but only HDMI frame buffer is being initialized at this point. Have a few things to try with it.
[HTC Vivid, Raider, Velocity] aaki_rocker:
thanks a lot !!

will be waiting for an update ! :)
[HTC Vivid, Raider, Velocity] come at me bro:
Damn good shiit! Anything breaking with the radio etc
[HTC Vivid, Raider, Velocity] synergye:
Yes. Intervigil's done awesome RIL work on the ville (one s), and once we get the facking kernel working, it will all be good to just use his modified HTCQualcommRIL class (new class off ours)...

It's like HTC hired motorola to do the holiday kernel development.
[HTC Vivid, Raider, Velocity] zacgoesrawr:
we are so close i can almost taste it:p
[HTC Vivid, Raider, Velocity] zacgoesrawr:
Hey synergy, since the ION break through are we going to get into the "Gamma" builds ;)

i definitely had to look up what letter came up after beta.
[HTC Vivid, Raider, Velocity] Aus_Azn:
Will the handbuilt RIL that you mention here actually benefit the Sense 4 port too? Or is that a whole different framework that needs to be rewritten again?
[HTC Vivid, Raider, Velocity] zacgoesrawr:
flashing Beta 5 for logcat now ~~ :cool: