yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] albinoman887:
yeah sounds like we hare running out of pmem space in memory... had the same problem with pyramid. its a PITA to fix lol
[HTC Vivid, Raider, Velocity] haydnlj:
Yes definitely getting a couple a day, almost always seems to happen directly after an attempt to unlock the phone for me - backlights are on but unresponsive (without haptic), with screen not illuminating and no response to volume/power. Unfortunately haven't caught a log of this yet.

Also posted in discussion thread - new Maps 7.0 is creating a tonne of screen jitters/artifiacts, and soft reboot seem to happen more frequently since upgrading. Have cleared data/uninstalled/reinstalled and still the same (OnDemand Gov as per fresh install).

Looks like this..

[YOUTUBE]6cSB3d_7iGo[/YOUTUBE]
[HTC Vivid, Raider, Velocity] rignfool:
I corrected MOST of that with that new check box the egl one... Made most of it go away... But it doesn't survive reboot
[HTC Vivid, Raider, Velocity] pitpit24:
Could you look at the torch.apk and make it keep the phone awake, its frustrating to have the light closing after whatever duration is set for auto screen off.
[HTC Vivid, Raider, Velocity] xxthe:
I'm getting hung.. Says finishing boot, but sits for a few seconds and reboots to the ani and just hangs.
[HTC Vivid, Raider, Velocity] pitpit24:
Did you do a full wipe, then flash ROM, then gapps?

Full wipe is clear data/cache, clear dalvik cache, format /system.
[HTC Vivid, Raider, Velocity] haydnlj:
thanks.. had a little luck with GPU rendering and disabling HW overlays.. but no magic bullet.

By "new check box the egl one" - do you mean the "Force 4x MSAA" OpenGL option in developer options?
[HTC Vivid, Raider, Velocity] rignfool:
Yeah... That one
[HTC Vivid, Raider, Velocity] pitpit24:
Simply clear Maps data in app info settings and the bug is fixed...
[HTC Vivid, Raider, Velocity] yosoywilson78:
I too am having soft reboots, usually 2-3 a day & usually while the phone is locked in my pocket,I know theyre happening because I will get my voicemail alert at reboot & I keep them cleared. I also get a black screen atleast once a day, I cannot get the screen to display & have to do a battery pull, this happens almost always while Im listening to music & I unlock the phone to skip a song & when I relock the phone the music stops & the phone becomes unresponsive.
[HTC Vivid, Raider, Velocity] albinoman887:
lol thats an easy fix..

the torch thing i have fixed in source.... it will be in the next build
[HTC Vivid, Raider, Velocity] pitpit24:
Nice, is the next build ready soon?

---------- Post added at 10:26 PM ---------- Previous post was at 10:14 PM ----------

The maps bug is back after going to another app in multitasking and then going back to maps it bugs... Maybe a memory issue?
[HTC Vivid, Raider, Velocity] sdotkdot:
Just flashed this last night after trying Slimbean for a while and I don't have ANY of the listed bugs yet. Badass gov even scales properly for me :confused: . I haven't installed maps yet so i can't comment on that but so far this rom is flawless. Great job so far!

AT&T Vivid (white)

Chicago LTE market

Baddass gov min 384 max 1188

Undervolted -12 across the board
[HTC Vivid, Raider, Velocity] Mr_Random:
I didn't have problems with maps until I installed google earth... wiped data and cache for the app and now it's fine.

It JUST did the backlight but with black unresponsive screen/buttons after testing maps... I'd rather have a reboot than one of those... lol

I can confirm the wired headset mic problem too.

Also, I went into system/etc/init.d and messed with the kernel to try to make it 1350 at boot, but even though the script is saved like that, it still bypasses and goes to 1566 or whatever.

[MENTION=2464761]156[/MENTION]6 I get 22-24 hours of battery life, [MENTION=1466104]135[/MENTION]0 I get 24-28... either way pretty sweet, but I see no performance difference so I'd prefer the extra couple hours.
[HTC Vivid, Raider, Velocity] Jaxellis:
Your battery drops when it goes from 1.3 to 1.5 o.o I went from 1.2 to 1.5 to 1.782 and I never noticed a battery drop.. then again I could never get 24hr on AOSP.. only on a specific sense 4.1 rom

Go into performance and set it to 1350 and do set on boot that will work
[HTC Vivid, Raider, Velocity] Mr_Random:
Yeah I wish the performance thing would stick... it seems like at first everything is solid, but after a while it just reverts, despite being set at boot and all.

I use:

Greenify

lagfix

crossbreeder

xprivacy

and I messed around with how and what speeds badass scales to.

I think the biggest boost to battery is the combo of Greenify (let it hibernate everything) and not allowing apps to start at boot using xprivacy.

I use kernel tuner to make a data swap too...

How much RAM do you guys have available (no apps open)? Using CPU-Z to check, I have 375, which means right under 400 with CPU-Z closed.
[HTC Vivid, Raider, Velocity] Gene Poole:
I skimmed through the thread and didn't see anything related.

I'm having a horrible battery drain problem, but I think it might not be real. I went from 100% to 7% in about 2 hours with it sitting on my desk (very little use at all). When it squawked at me I plugged it in and it charged fully in about 20 minutes. That's why I think it was a phantom drain. Is there something I missed about battery stats or something?

Other than that, pretty solid except for bluetooth phone. It dropped out quite a bit during my 1 hour commute to work; and on the return trip, even needed a re-pairing at one point (BMW iDrive bluetooth phone). I didn't test BT audio.
[HTC Vivid, Raider, Velocity] albinoman887:
the permissions probably got set as 644 when you saved. thats the default umask. set the permissions to 777 or 775 a.k.a. executable on the 99kernel file
[HTC Vivid, Raider, Velocity] Jaxellis:
For anyone wanting PIE controls in this rom (Not supported) you can try this guide

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

I tested it and it worked. Pie settings are there and it works. But again.. its not supported so please dont fill this thread with questions about it.

You can edit the PIE buttons using the nav bar buttons and layout. Set it up how you want it then when you use Pie your changed settings will be there
[HTC Vivid, Raider, Velocity] lelouch68:
Same thing here
[HTC Vivid, Raider, Velocity] camo_flage:
I have never gotten any soft reboots. Only a rare black screen thing
[HTC Vivid, Raider, Velocity] plasticbiker:
For me, it seems to be related to what application is running when the phone falls asleep. For me, my solitare game usually seems to trigger the phone to reboot if I don't hit the home button before putting the phone to sleep.

I am also seeing graphics issues (Heavy flickering on screen refreshes) with trapster. It's the only app so far that I've seen this issue.
[HTC Vivid, Raider, Velocity] agentfusion:
I had a few. Mostly during deep sleep if I tried to wake it for a message (indicator light flashing to alert me of sms,mms, Facebook, etc) it would soft reboot instead of wake.

Aside from that, it was pretty solid. I just use my vivid as an actual phone too much to not have call volume control and good battery life, so I went back to good ol virtuous inquisition. Best battery life of any senseless rom I've seen. I'm considering jumping ship to the optimus G since its a penny at Wal-Mart, or the HTC One for $99 at Costco
[HTC Vivid, Raider, Velocity] albinoman887:
i gt it guys lol, i know what the issue is.. its just the matter of fixing it withut the device is hard. applications use pmem,, (well new devices use ION and thats what is suppose to be used in 4.2 but we dont have support) you have to set pmem memory heaps in the kernel. these are like reserved parts in memory for different things. framebuffer mdp pmem sf (which is what i'm talking about etc) applicatins use pmem. this is why it depends on the app. right now the heap is 32 mb. it needs to be bumped to 60. but when i do that it crashes into other parts of memory and causes black screen/artifiacts. so it takes a lot of trial and error. i can get it t work by using the shooters memory mapping but you lose like 250 mb of ram from userspace

So i so i know the bug is there, as soon as i fix it i'll let you know but dont expect it in the next build or anything its a pita
[HTC Vivid, Raider, Velocity] theslam08:
I might be talking about a different thing here but,

What about using Kernel Tuner and experimenting with the OOM settings? There are a bunch of presets, and sliders for each section of memory. I think thats what you're talking about? Foreground Application was at 32mb default when I opened it. But any preset sets it to 8mb, so I moved everything else way up (I put it on 1000 aggressive preset, seems anything else is wasting the avail. ram because they all were very low like 128mb max except for 1000 aggressive sets a few over 200mb like empty app, content provider secondary server and hidden apps).

Also, I noticed under MP-Decision, it says Idle Frequency and Screen-Off frequency are both at 192mhz. Its grayed out. Personally because I don't use my phone as much as others (maybe), I would like to bump that up so I have less chance of screen delays. Can that be unblocked?
[HTC Vivid, Raider, Velocity] albinoman887:
lol no. thats all for userspace... not for kernel space memory... but on that note...never talk in absolutes i guess.... :laugh:

https://github.com/Team-Hydra/andro...mmit/8ee576a09ba2ecb4e1643ec4241f7a0959e7702f
[HTC Vivid, Raider, Velocity] calikevin:
I noticed in a logcat from slimbean that ion was being referenced a few times, this is probably going to be an issue with all 4.2.2 ROMs we try to dish out it seems. Here is the logcat from sultans source built slimbean, though we have quite a few more bugs with slim right now than CM, maybe this will help in some way
[HTC Vivid, Raider, Velocity] Jaxellis:
We already have it fixed and a logcat wouldn't help hah. Thanks though

As you can see below
[HTC Vivid, Raider, Velocity] calikevin:
Ah excellent, still getting used to github and reading the commits.

Any way you might be able to take a quick look at my logcat and tell me if any of those errors are easily fixable? I would greatly appreciate your input
[HTC Vivid, Raider, Velocity] albinoman887:
its got nothing to do with ion or anything i was doing. frameworks is crashing... why i dont know why.. thast why EVERYTHING crashes.... i told android this already maybe he didnt relay the message. theres probably a patch in cm you need that goes in frameworks av or base or natiive, one of those 3
[HTC Vivid, Raider, Velocity] Mr_Random:
so do I replace every instance of 644 with 777 or 775? Just to be clear...

Also tried the pie thing... if it were more configurable I'd like it, but LMT seems to work just fine and is VERY configurable...
[HTC Vivid, Raider, Velocity] albinoman887:
no no no.... the 99kernel file. download es file explorer or something and find the file and long press. a menu should come up. look for permissions or properties or something. set it to executable. then reboot
[HTC Vivid, Raider, Velocity] Mr_Random:
Hmm, wow that was buried under like 4 sub menus... I like ES, been using it for a while... rebooting... yeah it sticks!
[HTC Vivid, Raider, Velocity] Maqical:
No updates /: Really was hoping for MPDecsion to be disabled for better battery life or the soft reboots fixed.
[HTC Vivid, Raider, Velocity] Jaxellis:
If you go back one page... SOFT REBOOTS HAS BEEN FIXED! wait for the update. I corrupted my data partition due to TESTING for the devs to try to make it work.. Aka ITS BEEN A POS but they fixed it... Just wait for the next release... probably would have been tonight if i wasnt busy and was available for testing
[HTC Vivid, Raider, Velocity] agentfusion:
This is a silly question, but while I was messing around with stock kernel source from HTC I noticed an option for ion. Has anyone checked to see if it's actually there, or just a placeholder? I'm not home right now to check menuconfig to see if it really can be enabled natively or as a module, but if it CAN be, I can't imagine the android kernel being so drastically different from the linux kernel that I couldn't just step through all the relevant code and make an ion patch that can be applied to the kernel source you're using now to enable ion.

I'll check when I get home to see if the code is actually there for ion, or if it was just a placeholder.
[HTC Vivid, Raider, Velocity] Jaxellis:
New build coming soonish... Depending on when albino is ready to release

Here is what you have to look forward too :)

(No not all your devices will be running like this... I have changed my performance settings to my preferences and your preferences may give you different results.. maybe better maybe worse)
[HTC Vivid, Raider, Velocity] JimiGEE:
Idk what i did wrong, but all seems well except for calls. I know the OP said that sweep2wake caused proximity sensor issues, but it also said credit was given to someone who fixed this bug. I however, have proximity issues when on a call. Any ideas?
[HTC Vivid, Raider, Velocity] switchy85:
I also have issues with s2w, to the point I just disabled it. I do hope it gets fixed soon, tho. I also notice that if you sweep to sleep it reboots the phone. I'll reserve comments until the next build, tho.
[HTC Vivid, Raider, Velocity] Jaxellis:
S2W is not going to be fixed in the next build most likely and probably wont be fixed for a while. We still aren't quite sure what the issue is but once we do you know albino will fix it ;) Dont you worry. I personally love s2w and cant wait for it to be fixed as well but as far as right now all i can say is please wait :)
[HTC Vivid, Raider, Velocity] switchy85:
Lol, no worries. I really like s2w, but like having a working cm10 better. :)
[HTC Vivid, Raider, Velocity] albinoman887:
new build, check op for changelog
[HTC Vivid, Raider, Velocity] albinoman887:
yeah its fixed now. and mpdecision is going to stay enabled. this is how i do it in my msm8660 kernel. and its how pretty much every kernel out there does it. if you dont want it. use a different kernel. but you will be hard pressed to find one without it... i think you can disable it via the sysfs or some apps
[HTC Vivid, Raider, Velocity] theslam08:
Just want to say,

At first boot, all seems good. Data, no 'Sim Error', wifi works, seems very smooth. Will report back some more.

Thank you for update. Hugely appreciated :)
[HTC Vivid, Raider, Velocity] haydnlj:
Was that an install over the top, or full wipe?
[HTC Vivid, Raider, Velocity] Jaxellis:
I would do a full wipe... Personally.

Full wipes = 0 problems most of the time

Dirty flashes = most likely going to have problems in the future
[HTC Vivid, Raider, Velocity] albinoman887:
eh full wipes arent always reguired if you are updating like every update.
[HTC Vivid, Raider, Velocity] theslam08:
Well, I always full wipe, just to be sure I am getting no remanence from the previous build. Make sure I have the best potential for having the best experience. I dont see why not to full wipe. Just have a good backup program. There are a good amount of them now, they do wonders for us flashers.
[HTC Vivid, Raider, Velocity] Ldbrown01:
On fresh install everything seems to be working except for in call speakerphone.
[HTC Vivid, Raider, Velocity] bsaman:
So far so good for me. In the past I needed to do the enter-then-exit airplane mode every time I rebooted to get cellular signal to work, but this build seems to have addressed that.

Speaker phone works for me though the volume is very low. Handset volume is adequate.

---------- Post added at 09:40 AM ---------- Previous post was at 09:28 AM ----------

I guess I should add that I did a flash through Goo manager, only wiping cache and dalvik.
[HTC Vivid, Raider, Velocity] switchy85:
I flashed dirty and just cleared caches last night. Seems to be working very well so far. No sim card issue and no reboots so far. Woot! I'll keep testing and update with any new issues. Thanks guys, you're doing an excellent job!

Edit:

Ok, so I just rebooted my phone after installing the Xposed framework to play with and got the message that I need to reboot to access the mobile network. Hit back button and it went away and everything seems to be working fine. Not sure if it is because of my dirty flash or maybe the Xposed installer, though. Since that was never that big of a deal for me I wont worry about it.

Also, The new Maps has always been jittery as hell for me, even after clearing data and checking all three of those boxes in Dev Settings. Anyone else have any tips to fix that?
[HTC Vivid, Raider, Velocity] rignfool:
Best I've come up with is to exit and re-enter
[HTC Vivid, Raider, Velocity] lelouch68:
Wi-Fi is broken for me! Clean flash.
[HTC Vivid, Raider, Velocity] htcvividnoob:
I haven't had a chance to flash the latest build yet, but on the 7/2 build the new Google Maps update has been jittery randomly for me too, but I never had this issue with the previous versions of Google Maps, so I think it's application based not rom based.
[HTC Vivid, Raider, Velocity] Jaxellis:
Yes it's an application issue ... Maps just recently got this update and it the next update will probably to make it smoother. No one else needs to report it :)
[HTC Vivid, Raider, Velocity] ZeroCool11:
My Wifi also broke....
[HTC Vivid, Raider, Velocity] theslam08:
Wifi, Data, Calls, Mic, Stable. All here for me.

Try a new CLEAN flash. I have had no problems with newest build, 7-15.
[HTC Vivid, Raider, Velocity] Jaxellis:
Try flashing the the rom and boot.img as if you were s-on
[HTC Vivid, Raider, Velocity] lelouch68:
I am s-on and that didn't work.. And I did clean flash..I went back to last build.
[HTC Vivid, Raider, Velocity] cancha:
sim card message, battery life

hello, people turned to flash the rom in the latest version July 15 and message sim card appears whenever restart the computer, in the previous version battery consumption was very fast, I have a 3500 mah extended battery , I come from the rom holics, the battery was carrying in holics night and 100% at 8 am beginning my work until 10pm the battery reached about 30% or a little less, with the previous jb version of this rom, did the same and I get the battery to about 10% (and a small recharge during the day a load of 30 min), now with this version is not the same thing happen to have mojores results with the battery change gov values ​​to badass in the script, another query for the battery issue would have to do a wipe of statistics, for that I have to charge the battery to 100% and then do the wipe from recovery, then let it discharge all at 0% correct? eh not yet tried this, have if I orient

or someone who has a configuration optimal for battery performance if I help please
[HTC Vivid, Raider, Velocity] theslam08:
The S-On is the problem.

You need to do fastboot flash boot boot.img I believe. Look up some guides in this forum, they will explain more. But that is most likely the cause for your WiFi broken. And while you're at it, look up how to S-OFF. Makes your life much easier (no need to do the above command everytime you flash a new ROM that has a new boot.img, which 7-15 does from the last build (which is why last build still works, this one has the new boot.img that didnt flash))

If you flash fastboot boot.img, and wifi still dont work, IDK, its just you. Sorry.
[HTC Vivid, Raider, Velocity] lelouch68:
I'll pass on that.. Thanks tho.. I'm not gonna go through that again it's quite more difficult on a mac.. but I never heard of a boot.img causing broken Wi-Fi but you may be correct. Everything else worked but the Wi-Fi.
[HTC Vivid, Raider, Velocity] Jaxellis:
The boot.img is the kernel

If you are s-on you HAVE to flash the boot.img through fastboot "fastboot flash boot boot.img" Or else the rom shouldnt even boot.

Albino is sleeping I think so don't worry.. I already messaged him telling him this and he will look it over
[HTC Vivid, Raider, Velocity] lelouch68:
I can't fastboot on Mac.. I'll have to do it at work.. But it does boot up and everything works but Wi-Fi so I'll try it out tomorrow morning.

---------- Post added at 01:35 AM ---------- Previous post was at 01:31 AM ----------

Would you happen to know if fish image GUI app will work with fishing the boot.img?
[HTC Vivid, Raider, Velocity] Jaxellis:
You can try.. I know some users on the vivid have used it and had it work. But I have not used it so I cant really say anything about it
[HTC Vivid, Raider, Velocity] lelouch68:
I just tried it and it worked!! Thanks!! I would have never knew it was the boot.img if it wasn't for ya.. I appreciate it.
[HTC Vivid, Raider, Velocity] Jaxellis:
Have you flashed the boot.img? Try doing that "fastboot flash boot boot.img" The boot.img is inside the ROM.zip This should fix wifi

@ Audio yes we are trying our best to make the audio/ in call volume as loud as possible.. Audio works for me perfectly its just the incall volume and speaker phone. I gave albino a file that boots the speaker phone loudness a little so hopefully that helps. Blame HTC for these problems...

@ Warm rebooting? You mean soft reboots? That was fixed. As long as you don't use sweep2wake

@ Camera... All the options are there for me? All low res and all HD... Maybe reflash?

@ CM-file explorer... Yes its complete crap xD There is a button @ bottom right .. its a bookmarks tab sorta. click it to switch between them all

To get root explorer on it go into the settings in it then hit general then hit "safe" and change it to "root" (Don't have it installed so cant tell you right now)

@ Speed dial... Maybe.. But probably not depending on if albino really wants to go through all that

@ Auto Brightness... Settings>system>Notification Drawer>power widget... Old CM10 power widget... Its there...

@ Google apps. Google apps are from gapps that you flash. Google asked cyanogenmod not to have them included in their roms. Therefore no. It wont be updated because its not part of the rom itself and google keyboard? There should be no updates to that.. Google doesnt even release updates for their keyboard? Not sure how this could happen...

You can always try Borked sense 4.1 rom. Its quite nice with some hiccups if you still want sense
[HTC Vivid, Raider, Velocity] pitpit24:
The camera is missing the wide screen resolutions... Pictures should fill the screen, but now its a more 4:3 resolution we have. It should be 16:9.
[HTC Vivid, Raider, Velocity] albinoman887:
Umm the guy is 100% right. Your kernel is in there and the modules for WiFi in /system/etc//lib if the modules get updated but not the kernel they won't match and it won't load the WiFi module. So ya. Not flashing a boot.IMG will break wifi

This is false. The camera doesn't take 16:9 pictures the preview is just 16:9 its like this for the s4 as well
[HTC Vivid, Raider, Velocity] pitpit24:
In CM 10 i had the option it was something like wcd written beside the resolution, like on ICS...

Don't tell me I don't know my phone... I have it since 2 years, this phone makes wide screen pictures.
[HTC Vivid, Raider, Velocity] eliaslear:
for me not flashing roms without their kernel ALWAYS breaks wifi. in fact i can recall that in most threads (very beginning) you'll see that wifi is broken because people did not correctly flash the kernel.

ALSO i have the old PC version of the s-off batch files if anyone needs them. just pm me.
[HTC Vivid, Raider, Velocity] camo_flage:
Thanks to albino man and android 1-7 for making this happen :) even though they didn't have the device they still worked on it which is more effort than most devs will do.
[HTC Vivid, Raider, Velocity] sdotkdot:
I don't know anything about developing roms, but I imagine it's not the easiest thing in the world especially if you don't even have the device to test with. Many people said we would never see 4.2. Major thanks for keeping this phone fun for us to use! And thanks to those who helped test as well :D:D:D

Edit: Sorry for adding a non-development related post. It was just really cool following the evolution of how this all came together and I'm excited to try the rom out later.