yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] Mr_Random:
6/29 on new kernel running great, I am confused about whether 6/30 booted with the new kernel or not, so I haven't downloaded it. Can anyone confirm whether the new kernel works with it so I can download?

I had the SIM thing for a couple reboots, but it seems to have settled down now... It would say it needed to restart, but if you just hit the back button and touch the signal tile a few times on quick settings panel, it usually works from then on.

Using Apex Launcher and LMT Pie, in Tablet mode and with the swipe up gesture to access app drawer makes for a very clean Android. I have one Home screen and one Glass Widget multi-panel thing covering the whole screen, with quick access to everything. I also like to map the menu hardware button to pull up recents screen with one tap, long press for normal settings. It makes multitasking a little quicker...

I'll get back on with battery life stats... on PACrom with sultan's r2b3bt I was getting an average of 20 hours battery life, I hope to see similar with the new kernel :)
[HTC Vivid, Raider, Velocity] albinoman887:
hey guys. the one on GOO is the same in the op. dont use it without all the extra zips. just wait. i'm doing a build now. i fell asleep earlier haha
[HTC Vivid, Raider, Velocity] albinoman887:
can someone test this kernel befroe i do a full rom build?

http://d-h.st/qL5
[HTC Vivid, Raider, Velocity] calikevin:
Downloaded, backing up with twrp and I'll let you know what happens
[HTC Vivid, Raider, Velocity] frankieGom:
Flashed yesterday's ROM then this kernel.

Interesting... the screen flashes all the time, through the CM boot animation (with a stroboscopic effect, much like that in a dance club!) and all the way into the OS...

Fun, but not very useful... ;)
[HTC Vivid, Raider, Velocity] calikevin:
Boots but screen is flickering... Otherwise seems great
[HTC Vivid, Raider, Velocity] frankieGom:
Just the boot screen? Mine flickers until I power it off...
[HTC Vivid, Raider, Velocity] calikevin:
Yes same here.
[HTC Vivid, Raider, Velocity] drpigman:
Same here.

Mine seems to show only the bottom part of the screen, then flickers the whole screen, then off again.
[HTC Vivid, Raider, Velocity] calikevin:
Just reflash this kernel from earlier and your screen will return to normal, no need to restore or even wipe caches.

I also found out why SMS Backup+ wouldnt restore my texts, it's the new feature Privacy Guard in 4.2.2 which I really like actually, but I had to go into App Info for SMS Backup+ and uncheck Privacy Guard. Hopefully this fixes it for other programs if they have problems too.
[HTC Vivid, Raider, Velocity] camo_flage:
Great benchmarks :D
[HTC Vivid, Raider, Velocity] phrotac:
Thank you :)

Sent from my Samsung Galaxy S4
[HTC Vivid, Raider, Velocity] Jaxellis:
I feel like with newer releases this will be better ;)
[HTC Vivid, Raider, Velocity] albinoman887:
New build in a couple hours all the issues from yesterday are sorted
[HTC Vivid, Raider, Velocity] NWinfuse:
Thanks for all the hard work!
[HTC Vivid, Raider, Velocity] frankieGom:
I ran Antutu on mine for fun and get results anywhere between 5900 & 7200. Most scores are roughly similar to yours (better or worse dependingp except one, CPU-float, which is stuck at 217! Even with the phone set to performance mode and min cpu clock set to max (1836)!!

Anybody heard of such discrepancies before? I'm curious now...
[HTC Vivid, Raider, Velocity] albinoman887:
Billibox is running a newer kernel version is why
[HTC Vivid, Raider, Velocity] frankieGom:
Aaaaaah. I can hardly wait, now! :laugh:
[HTC Vivid, Raider, Velocity] pitpit24:
I'm like a child waiting his Christmas gifts!
[HTC Vivid, Raider, Velocity] Jaxellis:
I was actually running the 6/29 kernel ;) hehehe I use 1728max and ondemand gov. with CFQ I/O scheduler On stock gpu speeds as well... raising the gpu speed seemed to lower my benchmark scores.

This was from a "Ultimate" kernel ;) Lawl best bench I could get
[HTC Vivid, Raider, Velocity] camo_flage:
But how is the battery life at 1700 mhz....
[HTC Vivid, Raider, Velocity] Jaxellis:
on this performance one not very good xD On stock 29 build kernel I got 12h+ days...

1728MAX isn't bad at all... Wildchild roms were doing that :P I've been doing it ever since and always saw no decline in battery
[HTC Vivid, Raider, Velocity] camo_flage:
It doesn't go down??
[HTC Vivid, Raider, Velocity] Jaxellis:
Lol 1.7ghz goes down the same way 1.2ghz goes down :P I've actually had better battery on 1.7 than i did @1.2ghz and 1.5ghz

i just meant the battery doesnt go down any faster hahahaha

Also new build coming this way.. Fixes as well ;)
[HTC Vivid, Raider, Velocity] drumm3rb0y:
does this have the same volume issues that the rest of the jellybean builds have?? Searched through the forum and the question wasn't answered.
[HTC Vivid, Raider, Velocity] pitpit24:
Look at the OP,

Changelog

June-30

* Fixed Low volume, etc.
[HTC Vivid, Raider, Velocity] drumm3rb0y:
saw that but i was really just asking from user experience
[HTC Vivid, Raider, Velocity] Jaxellis:
From what I've been testing I would say it still need a bit of work.. its still low and you cant really hear in the car. Probably though if you use bluetooth or headphones its fine!
[HTC Vivid, Raider, Velocity] drumm3rb0y:
thank you. thats the answer i was looking for
[HTC Vivid, Raider, Velocity] pitpit24:
It always been hard to hear in the car...
[HTC Vivid, Raider, Velocity] Jaxellis:
are you talking about JB roms or in general on stock rom?
[HTC Vivid, Raider, Velocity] pitpit24:
Stock ROM had good sound but it could be louder in car. Jb has really low sound.
[HTC Vivid, Raider, Velocity] Jaxellis:
Had no problem with stock.. lol was loud enough in the car for me :P But! remember! The vivid's are all different...
[HTC Vivid, Raider, Velocity] albinoman887:
i havent forgot about you guys. i'm getting this build nice and fine tuned before release. its really getting close to being bug free.
[HTC Vivid, Raider, Velocity] rignfool:
I disagree...

I took a phone call yesterday while my coworker was hammer drilling and I heard then other caller as good as can be expected...
[HTC Vivid, Raider, Velocity] phrotac:
The AT&T models are the ones affected my low in call volume which is why I offered mine up for testing :good:

Sent from my Samsung Galaxy S4 :D
[HTC Vivid, Raider, Velocity] albinoman887:
it should be a little better with the latest build
[HTC Vivid, Raider, Velocity] phrotac:
I'll check it out then :)

Sent from my new GS4 from T-Mobile.
[HTC Vivid, Raider, Velocity] albinoman887:
new build posted. also added some more info about the kernel to the OP
[HTC Vivid, Raider, Velocity] bruce7373:
Thanks a lot. A small wrinkle... when I booted up after flashing, there was a popup saying "SIM card added, reboot to access mobile network." But in the background I could see that the mobile network was on. Rebooted anyway. This time, no popup, but no mobile access. I toggled airplane mode and it turned on (AT&T).

I just noticed yesterday on the 0628 build this was happening, (not the popup but having to toggle airplane mode). Since I'm usually at home on WiFi and make few calls, I honestly don't know when this started and if it is ROM related. Any ideas?
[HTC Vivid, Raider, Velocity] l0000l:
Thanks albinoman

The great rom

Can you add usb otg and ntfs support to next version of kernel :rolleyes:

I think it will be usefull ;)
[HTC Vivid, Raider, Velocity] albinoman887:
this is on 0702?
[HTC Vivid, Raider, Velocity] albinoman887:
i specifically fixed that bug. maybe a clean install?
[HTC Vivid, Raider, Velocity] bodrick:
I had a similar thing, the popup with the sim card added, please reboot your phone, which I would do and it would be fine then.
[HTC Vivid, Raider, Velocity] albinoman887:
on the latest build?
[HTC Vivid, Raider, Velocity] bodrick:
Yup, tried the latest build, started from scratch, full system wipe etc.
[HTC Vivid, Raider, Velocity] babymatteo:
Hey guys, so to flash this with S-On i would have to extract the boot.img and flash that first before i flash the rom correct? Would it possible to flash the boot.img with the Flash GUI app since i'm away from my PC and can't do it through fastboot?
[HTC Vivid, Raider, Velocity] erics:
7/2 build is running very smooth:

No SIM issue for me

Video recording works fine

In call volume does seem higher (ATT Vivid)

Only issue i have noticed is that the rocker buttons no longer seem to effect in call volume. In call volume seems to be static.

I will admit i did an over the top flash from 6/29 only clearing cache and Dalvik, maybe related to In call volume being static?

Thanks for all your hard work! Never thought I would be running 4.2.2 as a daily :laugh:
[HTC Vivid, Raider, Velocity] bruce7373:
Yes, I'm sorry, 0702. Something else which has happened a couple of times -- when I do a simple reboot, the phone shuts off instead of rebooting.

I did a dirty flash over 0628. I'll do a clean install and report back.
[HTC Vivid, Raider, Velocity] babymatteo:
[MENTION=4196197]Albinoman[/MENTION] maybe you can answer this question? Thanks in advanced
[HTC Vivid, Raider, Velocity] camo_flage:
I've flashed this through flash img gui. It works fine
[HTC Vivid, Raider, Velocity] babymatteo:
Awesome thanks Camo
[HTC Vivid, Raider, Velocity] NWinfuse:
This worked fine for me

On a different note, I'm having an odd issue where I can't get widgets to stick... message pops up saying "not enough room on this page" I have removed all app shortcuts leaving plenty of room but still won't work. Anyone else see this? Clean install from 6/29 build
[HTC Vivid, Raider, Velocity] rignfool:
The volume rocker in call bug is known and accepted in all CM and CM based builds...
[HTC Vivid, Raider, Velocity] babymatteo:
Flashing boot.img thru Flash GUI worked flawlessly. Thanks guys.

Quick notes about the ROM:

It's super smooth! Coming from CM10 weekly build, this build is definitely smoother. Great job [MENTION=4196197]Albinoman[/MENTION]
[HTC Vivid, Raider, Velocity] bruce7373:
After a clean flash all issues seem to be resolved, except for sometimes having to initialize data access by toggling airplane mode after rebooting. As I said, I don't know if ROM related or my phone just being flaky.
[HTC Vivid, Raider, Velocity] albinoman887:
seems to depend on carrier variant
[HTC Vivid, Raider, Velocity] :
First call no mic still a problem for anyone else on the 7/2 build ?

Coming from 6/29 complete wipe still an issues as well as the new SIM reboot message after a reboot.
[HTC Vivid, Raider, Velocity] jtsurfs:
I got the same thing with the "New SIM Restart". After I restarted it hasn't come up again.
[HTC Vivid, Raider, Velocity] Mr_Random:
Latest Build is very fast and smooth, everything working great, I'll update with battery life once I've used it more... Seems better than last build so far.
[HTC Vivid, Raider, Velocity] theslam08:
ROM 7/02-

I also get Sim Card error at boot, first boot completely clean install, wiped dalvik, data and system. But, when you get the error just hit the back button and everything is fine.

Also seems if I boot up with WiFi on, I have no cell reception (no signal bars at all, its the blank triangle). If I turn off WiFi, it takes about 5 min for data/cell reception to kick on. EDIT: Trying to make a call, it says "To place a call, first turn off Airplane Mode.", which its obviously not in, just WiFi is on but cell should still work. EDIT AGAIN: Seems no APN's are there in 7/02 ROM, not sure why, they were there in the previous builds. Ok...cannot even save the APNs. Hit save and it doesnt save. HAve to go back to previous build :(

Other than that seems very good and smooth.
[HTC Vivid, Raider, Velocity] ziolko:
I keep waiting for the bomb to drop, however this far I don't have a low in call volume problem I have had on other roms :D

I had to make two calls to get the in call mic working but other than that this rom is amazing
[HTC Vivid, Raider, Velocity] Wolfhawke:
Kudos to the Devs...

Just tried the latest build on ATT Vivid and I have to say compared to the original CM10 first run, much better, no perceived issues with the AT&T mic problem, call volume much better, have not tried speakerphone yet or using the USB mass storage feature yet...Battery life with both processors running Badass governor (default settings) doesn't seem to yield any different battery life than using intellidemand in kernel tuner. did note a brief wake-up issue, but it's not severe enough to steer me away from daily use.

Did not have any issues with messaging that I noticed.

Kudos to both Albinoman887 and Android1234567! Wish I could afford to trib the cigs Albinoman, but perhaps later after I get traction on the job front!:D
[HTC Vivid, Raider, Velocity] ProtheusIRC:
The only thing I have to report is horrible battery life. And intermittent signal issues.
[HTC Vivid, Raider, Velocity] plasticbiker:
7/02 ROM:

I'm still seeing a SIM/Mobile Network prompt after an initial reboot, but everything else seems to be ok. This is with a dirty install w/ both Dalvik and Cache partitions wiped.

I did have to install the ROM twice in order to get the 7/2 kernel to show up as well, but that might be due to the recovery kernel I have installed on the device.

Update:

I'm seeing about a 10% per hour battery drain while the phone is idle. Phone Idle takes about 16% of the battery life.
[HTC Vivid, Raider, Velocity] bruce7373:
What carrier are you with? I'm with ATT and I have "WAP Cingular" selected. It should be on "ATT pta" for LTE. I wonder if this is the reason for the changed SIM card message.

I got the airplane mode prompt, too, yesterday when I was still on 0628. Also no speakerphone function at all.

Edit: I guess speakerphone works, but incredibly low volume.
[HTC Vivid, Raider, Velocity] pitpit24:
I don't hear a big difference in the volume, it could get louder. By the way I'm on bell mobility, in the case it is carrier related.
[HTC Vivid, Raider, Velocity] l0000l:
I Record a video in 1080p full hd but when I try play it from gallery it doesn't shown. I see only tiled screen
[HTC Vivid, Raider, Velocity] Maqical:
Clean install since 629 build.

Call volume on ATT got louder, could be better, but A LOT better.

Video works

After pressing the power button, phone sometimes reboots ( Not that big of a deal to me, still usable)

Everything else seems to be good, doing good on battery life, Data & Wifi ALWAYS on, texting nonstop (Teenager)

Great job :D
[HTC Vivid, Raider, Velocity] pitpit24:
Set the min freq to 384 MHz if you get reboots on wake up, but this should be repaired in the build from 7/02, try installing this new one.
[HTC Vivid, Raider, Velocity] Maqical:
Is set at that speed, 7-02 kernel too, all stock didn't touch it.

Only happened twice so far though.
[HTC Vivid, Raider, Velocity] pitpit24:
By kernel you meant to say ROM I believe. If you really only installed the kernel, you must download the new ROM build.

http://goo.im/devs/Albinoman887/holiday
[HTC Vivid, Raider, Velocity] Maqical:
Installed the new rom and the boot.img from in the .zip through fastboot & I'm also s-off'd

Kernel has a new date of 7-02 as well.

and it's already at 384 default
[HTC Vivid, Raider, Velocity] NWinfuse:
You don't need to flash using fastboot if you are s-off, that's the whole point of doing it.
[HTC Vivid, Raider, Velocity] pitpit24:
Its weird i have the 192 freq and zram is their too and it shouldn't I think...
[HTC Sensation] shdw03:
Not sure what to do. Happened about 2 weeks ago and getting progressively worse. Sometimes screen unresponsive, sometimes ok, and other times registers a touch in a completely wrong place. Is my digitizer going out? Will flashing different rom or kernel work? Currently have an xe s-off with elegencia rom
[HTC Sensation] rzr86:
you can try different roms or kernels and see how it goes

also check this it out

http://xdaforums.com/showthread.php?t=1239238
[HTC Sensation] 0911:
For me the cause of this was certain apps running in the background, Any.do and the new Skype update with it's new UI, seems there's a problem with custom roms and some apps UI, just like watsapp sometimes causes typing issues on custom roms, stopping or uninstalling solved my problems.

Haven't reported it with to CM team tho, when I get to ten post count.
[HTC Sensation] shdw03:
thanks for the ideas guys, but I think that my digitizer is shot. turned on touch overlay and pointer location. seems like the screen is warped. if I put moderate pressure in the middle of the screen, it will register 5-8 differet touch points across the center section of the screen. sometimes if you drag your finger, it will skip or not register certain areas(mainly the center of the screen) I'll try get a screen shot later.
[HTC Sensation] OllieArmageddon:
Take the back cover off your phone. Along one edge of your phone there will be a little metal square with a nipple. Add small folded tin foil to the nipple loosely then put the cover back on. Your screen can now ground probably. This problem is more noticeable when charging.
[HTC Sensation] shdw03:
Already done that... still have trouble with touchscreen in the center. Cuts off, doesnt register or registers multiple touches
[HTC Sensation] AndroidSupporter318:
Did you try leaving the phone in your freezer overnight?

Sent from my Ouya
[HTC Sensation] jmcclue:
Hi i bought a sensation and it had the wifi problem and digitizer problem (going crazy) and i searched for 2 days and got nothing, i also read that putting tinfoil over the silver nipple thing would fix it but if anything it made it worse. tried bout 7 different roms, everything was still the same but now i have perfect wifi and digitizer, fixed it last night and not 1 problem so far. So.. what i did was got an old digital camera card, cut off 4 of those metal pins (look at pic) put 2 next to each other using strong double sided tape and stuck them to both connector pins on the back battery cover, now i got perfect wifi. The connectors on the battery cover r just conductive paint and wears through to the plastic over time (i also tried condutive paint but didnt work). And the digitizer i cut a piece of plastic/rubber off an old usb cable (see pic) round the wire and fitted it over the silver nipple ground pin thing and now my digitizer works perfect, not one problem so far. Give it a try, assuming ur digitizer isnt actually broke.
[HTC Sensation] 0911:
My problems also started reoccurring and it doesn't seem to be software related, cause even when it's completely stock people reported freezing and lock ups on this and other HTC models, I hate this phone and will never purchase another HTC product.
[HTC Sensation] dub2012:
I recently took mine apart to clean dust from under screen and refit the old digitiser. It was unresponsive and some parts of the screen didnt work at all so I flashed a calibration file which improved it but still working 100%. Took apart the phone several times to check connections, reinstalled several roms, calibrated screen and cleaned contact on the back cover etc...nothing worked.

I use the trace keyboard a lot but couldnt with this problem. I was sure I had damaged the digitiser and was losing hope until I upgraded to firmware 3.33.401.106, hboot 1.29.0000 and radio 11.76C.3504.00P_11.29A.3504.18_M. hboot from 1.27.1000 and screen is now working as normal.

I ran CM 10.1 JB and Viper 1.63 before removing the digitiser and after refitting it flashed CM JB, Inspiration, ARHD and currently on viper 3.1.

I have seen a high number of posts recently about screen responsiveness so could it be an issue with 1.27.1000 on the latest roms?

I cant understand how this happened straight after removing the digitiser and was fixed by flashing newer firmware.
[HTC Sensation] 0911:
Thanks, flashed it last night and seems ok so far, will give it another day of two
[HTC Sensation] 0911:
Sadly my problems are still persistent, tired every possible solution including the grounding pin fix from another post which spans over 50 pages long, also trolled the Internet only to find this is not an isolated problem, other people who own the HTC sensation have been having the same telltale issues and quite frankly I've come to the conclusion that this is just another half broken HTC device HTC decided to release to cut corners on just to save on overall production cost.
[HTC Sensation] dub2012:
try this

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

just flash the file without replacing digitiser
[Samsung Galaxy W I8150] geniusboy93:
Hi there Malaysian. Welcome yo this community:)

You can try spirit fm. Try search it on google. It is work fine to me:D
[Samsung Galaxy W I8150] Jason Tan:
I am using Spirit UL now, but I still can't hear any channel of the Radio.

Beside Spirit FM Unlocked do have other Application?
[Samsung Galaxy W I8150] geniusboy93:
Oh, really? You sure you plug your ear phone:p

I think this is the best apps. I think you should open app > settings > band > change to 200Hz. Tell me the result:D
[Samsung Galaxy W I8150] Jason Tan:
Ya~! I plug in the earphone.

But I can't find the app > settings > band > change to 200Hz.

It only have app > setting > Regional Band or Audio or user interface or Ul Elements or Alternate Frequency or Debug

May I know the setting of Audio > Method > should be CyanogenMod 7 or qsd8250 or qdsp5v2.
[Samsung Galaxy W I8150] geniusboy93:
Really? What version did you use? I use version 2013_05_08. And i think, what is the same as band i talking abouy is regional band. Try to change it to world 200KHz. And the audio, mine is automatic. Just fine for me to hear fly fm, or hitz fm, or any channel.:D
[Samsung Galaxy W I8150] thearif:
Under settings choose regional band. In there you will find the frequency step settings.

Never mind, poster above already said this.
[HTC One X] Tepes4:
Hello all,

I have the One X for a year now and tried many roms both in JB and ICS with no problem at all. Two weeks ago, after having flashed the latest Viper rom, I realised that while on speakerphone people cannot hear me. This happens while on the phone, on Skype,viber, tango etc. I have searched the forums and found out that there are two microphones on the One X. The one on the bottom of the phone, used while on headset mode and another on the top of the phone, by the 3.5 mm (handsfree-speakers) hole that is used when on speakerphone mode. Tried different roms (on Orio now) and kernels (XM 305 at the moment) but had no luck.

So I ask

1) Anyone else experiencing this?

2) Is there anyone who has disassembled his phone that can confirm that there is a microphone on the upper side of the One X and if it is attached to the motherboard? In other words, is there a microphone over there and can it be changed with a spare one?

3) Is there any way (app for example) to test the speakerphone microphone and see if it is a hardware or software (base or rom) issue? (tried the *#*#3434#*#* method)

Thanks in advance

Tepes4
[HTC One X] fridaycider:
The lower main microphone is part if the volume button flex cable and is separate from the main board . Costs about 10 pounds off eBay .

The noise cancellation microphone is part of the power button flex and is separate also at the top of the phone .

I usually test by using the voice memo app .

But sounds like you need the first one .
[HTC One X] Tepes4:
Thanks for your input fridaycider. The microphone that you use for non speakerphone calls is the one in the lower end of the phone. So, I would probably need the second that you mention. The one that is part of the power button flex. Is that correct?

Tepes4
[HTC One X] fridaycider:
You would need the first one I mentioned which is part of the volume button flex . That is the main microphone , the upper one is just for noise cancellation.

http://www.ebay.co.uk/itm/Genuine-H...986&pid=100015&prg=1006&rk=1&sd=171064782479&
[HTC One X] Tepes4:
But when using the phone as normal (place it on my ear and talk) people can hear me no problem at all. It's only when on speakerphone mode that this annoyance is happening. How do you explain that mate? Thanks for your help fridaycider!

BTW tried evernote recording and it had no problem recording my note. My voice sound clear. It seems to only happen on communication apps (such as skype, viber, phone etc)...

Tepes4