867 replies to this topic

[markymarkmark12345]

i know it's kind of gimmicky...but any chance of getting photosphere in this rom?

[newskate9]

So, I tethering is fixed, maybe a good time to try this one again!

 

Question - all of the 4.2.2 builds give about 1000 less Quad scores for me.  Is this normal?  Expected?  [ I know folks don't like comparing Quad scores, but 1000 is a big jump ]

 

Question - I tried so shutdown the nav bar (I think it was this rom) and use PIE, but he Nav bar would just blink and come back.  Any one else seeing this?

[pcarenza]

i know it's kind of gimmicky...but any chance of getting photosphere in this rom?

I wouldn't count on it for now.. it's Google proprietary, and like wallet, won't work on anything but what Google authorizes. You could try downloading one of the many flashable zips of the photosynth camera online and change your build.prop settings if you think it's worth it...

[pcarenza]

So, I tethering is fixed, maybe a good time to try this one again!

 

Question - all of the 4.2.2 builds give about 1000 less Quad scores for me.  Is this normal?  Expected?  [ I know folks don't like comparing Quad scores, but 1000 is a big jump ]

 

Question - I tried so shutdown the nav bar (I think it was this rom) and use PIE, but he Nav bar would just blink and come back.  Any one else seeing this?

The kernel is still in development; I think as we see more kernels for the Razr HD we'll see overclocking, new governors.. all those sorts of things. I don't know how significant a quad score really is though - this ROM has been nothing but blindingly fast for me without having to ask antutu or whatever.

 

Re. the Nav bar/PIE mode.. I'm looking into that, as I've got another report.

[newskate9]

The kernel is still in development; I think as we see more kernels for the Razr HD we'll see overclocking, new governors.. all those sorts of things. I don't know how significant a quad score really is though - this ROM has been nothing but blindingly fast for me without having to ask antutu or whatever.

 

Re. the Nav bar/PIE mode.. I'm looking into that, as I've got another report.

Thanks for the response.  I still find it amazing the stuff you guys can do! 

 

I do find it smooth and "fast", only because the score was so different, did I ask. 

 

Cool beans - ready to give another run!

[tk0827]

Sir, meet hugeness! Tethering fixed in 5/18 build!

 

SIR!  You are GREAT!  I can verify that all is working great!  

 

Status update:

Baked in Wifi Tether - fully functional!

FoxFi - fully functional!

Wifi Tether for Root Users - not so functional.  It could be because there's too many options and variables, but I haven't gotten this app to work yet.  Ah well... no biggie!

[polysaturate]

Ran teh update just now and I keep getting AOSP Keyboard that keeps failing, Seems, like contacts, etc hasn't synced. I did Wipe cache and Dalvik. Very weird...and of course, i didn't back up...lol

 

EDIT: I just went with a full restore, and install, seems like TRWP lost all my backups somehow anyway...

 

logcat seems to say it keeps looping through gravity and sensors:

 

 

D/Gravity (  652): gravity_compute_filter_alpha: alpha=0.033333, accel samples=8605, device state=1

D/Gravity (  652): gravity_compute_result: accel_x=0.497498, accel_y=0.340393, accel_z=-9.107300, timestamp=76869570

D/Gravity (  652): gravity_compute_result: quat_a=1.000000, quat_x=-0.000002, quat_y=0.000008, quat_z=0.000007, timestamp=76869591

D/Gravity (  652): gravity_compute_result: gravity_x=0.495416, gravity_y=0.325230, gravity_z=-9.204118

D/Gravity (  652): gravity_sam_update: gravity_x=0.526757, gravity_y=0.345805, gravity_z=-9.786386

D/Gravity (  652): gravity_sam_update: lin_accel_x=0.002081, lin_accel_y=0.015163, lin_accel_z=0.096818

D/Gravity (  652): gravity_sam_update: timestamp=76869591, accuracy=3

D/FMV     (  652): FMV_UPDATE_OUT , 76869591, -0.089752, 0.065982, 0.289290

D/Sensors (  652): UnCalibrated Mag Data: Magx: -20829, Magy: -20436, Magz: 2358

D/Sensors (  652): Calibrated Mag Data: Magx: -825, Magy: 3971, Magz: 21941

D/Sensors (  652): Calibration Offset: X: -19306.905000, Y: -23710.925000, Z: -19778.765000

D/Sensors (  652): Calibration Accuracy: 2

D/Gravity (  652): gravity_update_accel_buf: variance=0.004804, dev state=1

D/FMV     (  652): fmv_update_gyro_buf: variance=0.000020, sumSquare=0.000020, dev state=1

D/FMV     (  652): FMV_UPDATE_OUT , 76869591, -0.089752, 0.065982, 0.289290

D/Gravity (  652): gravity_compute_filter_alpha: alpha=0.033333, accel samples=8606, device state=1

D/Gravity (  652): gravity_compute_result: accel_x=0.468933, accel_y=0.329681, accel_z=-9.233459, timestamp=76870231

D/Gravity (  652): gravity_compute_result: quat_a=1.000000, quat_x=0.000009, quat_y=0.000021, quat_z=0.000004, timestamp=76870252

D/Gravity (  652): gravity_compute_result: gravity_x=0.494915, gravity_y=0.325223, gravity_z=-9.205081

D/Gravity (  652): gravity_sam_update: gravity_x=0.526171, gravity_y=0.345762, gravity_z=-9.786419

D/Gravity (  652): gravity_sam_update: lin_accel_x=-0.025982, lin_accel_y=0.004458, lin_accel_z=-0.028378

D/Gravity (  652): gravity_sam_update: timestamp=76870252, accuracy=3

D/FMV     (  652): FMV_UPDATE_OUT , 76870252, -0.089752, 0.065982, 0.289290

D/Sensors (  652): UnCalibrated Mag Data: Magx: -20436, Magy: -20043, Magz: 2751

D/Sensors (  652): Calibrated Mag Data: Magx: -865, Magy: 3971, Magz: 22059

D/Sensors (  652): Calibration Offset: X: -19306.905000, Y: -23710.925000, Z: -19778.765000

D/Sensors (  652): Calibration Accuracy: 2

[newskate9]

Re. the Nav bar/PIE mode.. I'm looking into that, as I've got another report.

  

 

Just FYI - on this install, getting rid of nav bar worked fine........... go figure.  I did the exact same process - wiping everything, etc.  All else seems to be working.

[drewrivera]

There are some things missing in the latest 518. I don't know if it's because if dirty flash but for example, when on Bluetooth there's no option to go into handset speaker mode and speaker mode. just one option, which is the speaker mode. Also i have to finagle with the Bluetooth for music to play. (Probably a4.2 issue anyway) and every time i touch something in the build prop it's hard for the phone to wake up. I should probably just wipe data and system as well and try them out huh? I'll see. Thanks

Sent from my Razr HD using Tapatalk 2

Edit. False alarm on my last posting. Ask is well now. Just a simple reboot but i don't why.

[newskate9]

HI guys,

 

All seems to be working as predicted but I've noticed something weird.  I use GO SMS.  I had PIE set up with no Nav bar.  Pie was on the right side.  It seemed that the screen in right area stopped working at times, became less sensitive.  I decided to nuke in the rom and use LMT instead.  I now have that running on both left and right.  The screen seems better, but still not as snappy on that side as other rom, Rage for example.

 

I may back this up and jump back to my Rage backup just to confirm.  I can't think of a reason this would happen that is software related - I wonder if I goofed my phone somehow?

[tk0827]

Would like to pass along a bug... I'm seeing an issue with Exchange contacts... They are not showing up.  All I see in my contacts are my Google Talk contacts probably coming over from Gmail... but there's nothing for my Exchange account.  Any ideas?

 

From XDA XenonHD Forum: 

Hmmm... just noticed. My Exchange contacts aren't synching. I've tried from 5 different Exchange accounts ranging from Exchange Server 2010, 2007, 2003 and live.edu (outlook.com). Can anyone duplicate? Started from scratch on this thing... same issue. Cleared cache/data, no dice.

[pcarenza]

 

Ran teh update just now and I keep getting AOSP Keyboard that keeps failing, Seems, like contacts, etc hasn't synced. I did Wipe cache and Dalvik. Very weird...and of course, i didn't back up...lol

 

EDIT: I just went with a full restore, and install, seems like TRWP lost all my backups somehow anyway...

 

logcat seems to say it keeps looping through gravity and sensors:

 

 

D/Gravity (  652): gravity_compute_filter_alpha: alpha=0.033333, accel samples=8605, device state=1

D/Gravity (  652): gravity_compute_result: accel_x=0.497498, accel_y=0.340393, accel_z=-9.107300, timestamp=76869570

D/Gravity (  652): gravity_compute_result: quat_a=1.000000, quat_x=-0.000002, quat_y=0.000008, quat_z=0.000007, timestamp=76869591

D/Gravity (  652): gravity_compute_result: gravity_x=0.495416, gravity_y=0.325230, gravity_z=-9.204118

D/Gravity (  652): gravity_sam_update: gravity_x=0.526757, gravity_y=0.345805, gravity_z=-9.786386

D/Gravity (  652): gravity_sam_update: lin_accel_x=0.002081, lin_accel_y=0.015163, lin_accel_z=0.096818

D/Gravity (  652): gravity_sam_update: timestamp=76869591, accuracy=3

D/FMV     (  652): FMV_UPDATE_OUT , 76869591, -0.089752, 0.065982, 0.289290

D/Sensors (  652): UnCalibrated Mag Data: Magx: -20829, Magy: -20436, Magz: 2358

D/Sensors (  652): Calibrated Mag Data: Magx: -825, Magy: 3971, Magz: 21941

D/Sensors (  652): Calibration Offset: X: -19306.905000, Y: -23710.925000, Z: -19778.765000

D/Sensors (  652): Calibration Accuracy: 2

D/Gravity (  652): gravity_update_accel_buf: variance=0.004804, dev state=1

D/FMV     (  652): fmv_update_gyro_buf: variance=0.000020, sumSquare=0.000020, dev state=1

D/FMV     (  652): FMV_UPDATE_OUT , 76869591, -0.089752, 0.065982, 0.289290

D/Gravity (  652): gravity_compute_filter_alpha: alpha=0.033333, accel samples=8606, device state=1

D/Gravity (  652): gravity_compute_result: accel_x=0.468933, accel_y=0.329681, accel_z=-9.233459, timestamp=76870231

D/Gravity (  652): gravity_compute_result: quat_a=1.000000, quat_x=0.000009, quat_y=0.000021, quat_z=0.000004, timestamp=76870252

D/Gravity (  652): gravity_compute_result: gravity_x=0.494915, gravity_y=0.325223, gravity_z=-9.205081

D/Gravity (  652): gravity_sam_update: gravity_x=0.526171, gravity_y=0.345762, gravity_z=-9.786419

D/Gravity (  652): gravity_sam_update: lin_accel_x=-0.025982, lin_accel_y=0.004458, lin_accel_z=-0.028378

D/Gravity (  652): gravity_sam_update: timestamp=76870252, accuracy=3

D/FMV     (  652): FMV_UPDATE_OUT , 76870252, -0.089752, 0.065982, 0.289290

D/Sensors (  652): UnCalibrated Mag Data: Magx: -20436, Magy: -20043, Magz: 2751

D/Sensors (  652): Calibrated Mag Data: Magx: -865, Magy: 3971, Magz: 22059

D/Sensors (  652): Calibration Offset: X: -19306.905000, Y: -23710.925000, Z: -19778.765000

D/Sensors (  652): Calibration Accuracy: 2

 

I'm not sure I follow you -- did you do a factory reset the first time you installed this ROM?

[pcarenza]

Would like to pass along a bug... I'm seeing an issue with Exchange contacts... They are not showing up.  All I see in my contacts are my Google Talk contacts probably coming over from Gmail... but there's nothing for my Exchange account.  Any ideas?

 

From XDA XenonHD Forum: 

Hmmm... just noticed. My Exchange contacts aren't synching. I've tried from 5 different Exchange accounts ranging from Exchange Server 2010, 2007, 2003 and live.edu (outlook.com). Can anyone duplicate? Started from scratch on this thing... same issue. Cleared cache/data, no dice.

I'm using Enhanced Email for my work Email which uses Exchange... works fine with my Contacts. Does your Exchange provider use Activesync?

[tk0827]

I'm using Enhanced Email for my work Email which uses Exchange... works fine with my Contacts. Does your Exchange provider use Activesync?

Yep we use activesync. Didn't have a problem on 4.1.2. I'm using the stock email app and people (contacts) app. Email and calendar are synching fine. My co-worker is also running this build of XENONHD on his xt926 and has identical issues.

[polysaturate]

I'm not sure I follow you -- did you do a factory reset the first time you installed this ROM?

Yes...loaded up the original Rom late last week, did factory wipe, and all the good stuff. Worked without an issue. Tried to upgrade the ROM, with the newest version, the day I made my previous post, by following your instructions a little higher in the thread of only needing to wipe the cache and dalvik, and then flashing the ROM, and at first I was getting install errors, ones you usually see if system is not mounted, but it was. rebooted, then it installed, and once it booted into the ROM, I pretty much lost my google account(sync, contacts, now, etc), and AOSP keyboard just kept popping up saying it had closed. Tried flashing the upgrade another two or three more times with the same result, and ran that logcat for the purpose of this thread. At any rate, I did a complete wipe, and fresh install and everything worked(why shouldn't it). Just figured i'd keep the information available if anything, for troubleshooting.

[pcarenza]

Yep we use activesync. Didn't have a problem on 4.1.2. I'm using the stock email app and people (contacts) app. Email and calendar are synching fine. My co-worker is also running this build of XENONHD on his xt926 and has identical issues.

OK I'll check it out... I may not have contacts sync and not know about it yet

[pcarenza]

Yes...loaded up the original Rom late last week, did factory wipe, and all the good stuff. Worked without an issue. Tried to upgrade the ROM, with the newest version, the day I made my previous post, by following your instructions a little higher in the thread of only needing to wipe the cache and dalvik, and then flashing the ROM, and at first I was getting install errors, ones you usually see if system is not mounted, but it was. rebooted, then it installed, and once it booted into the ROM, I pretty much lost my google account(sync, contacts, now, etc), and AOSP keyboard just kept popping up saying it had closed. Tried flashing the upgrade another two or three more times with the same result, and ran that logcat for the purpose of this thread. At any rate, I did a complete wipe, and fresh install and everything worked(why shouldn't it). Just figured i'd keep the information available if anything, for troubleshooting.

That's why I love having Titanium Backup handy... if stuff goes wrong after a flash I know I'll have my stuff secure because I need to do a factory reset... hope everything's working well now for you, I  may end up having my team mate adjust the install instructions. 

[jld]

Anyone else get a force close on gallery after taking a picture?

[jrdnsingh89]

Is there google wallet support for this rom?

[pcarenza]

Anyone else get a force close on gallery after taking a picture?

I've gotten the occasional (once every couple of weeks occasional) FC with normal use of the camera.... I don't expect it to be fully stable until the kernel is complete.

Having said that, the new builds of this ROM have made some major improvements to the camera.... too bad you'll have to wait til official release of the next version