230 replies to this topic

[dts2]

So after 10+ flashes, 3 downloads each of DU & Slim GApps, I finally got to the screen to enter my email & password. Previous to this, all I got was unable to connect to Google servers. Also in the setup process, I had several soft reboots, as well as times where i would go back to the start of setup (language choice). Even right before I successfully entered my email, I had entered the email & hit next, to only get the can't connect error, then went back to language selection. 

 

I tried other roms in the middle of the DU flash attempts to make sure they flashed fine, and they did.

 

I chose to setup as a new device, as I was getting download errors of programs during this process. So I went to PlayStore immediately after reaching the home screen, and tried a random app, and got an "could not be downloaded due to an error (960)." 

 

No idea what is wrong, or if it is just me, but I can't get things to jive on this rom.

 

update: I finally got 1 app to install (hangouts dialer), but nothing else. I thought installing 1 by 1 might help, but all it allowed me to see was the downloads are restarting. I got up to 79%, then it went back to 0%, and then back up to 79% before the "960 error."  I cleared PlayStore data, but same thing. 

[spainter]

Looking through the google forums they are saying back up your pics and personal data to your computer and do a factory data reset. You may have to reflash your gapps as well. I would also wait for Jl90 to comment on this before doing it. He will know what havoc this might cause.

[jl90]

So after 10+ flashes, 3 downloads each of DU & Slim GApps, I finally got to the screen to enter my email & password. Previous to this, all I got was unable to connect to Google servers. Also in the setup process, I had several soft reboots, as well as times where i would go back to the start of setup (language choice). Even right before I successfully entered my email, I had entered the email & hit next, to only get the can't connect error, then went back to language selection.

I tried other roms in the middle of the DU flash attempts to make sure they flashed fine, and they did.

I chose to setup as a new device, as I was getting download errors of programs during this process. So I went to PlayStore immediately after reaching the home screen, and tried a random app, and got an "could not be downloaded due to an error (960)."

No idea what is wrong, or if it is just me, but I can't get things to jive on this rom.

update: I finally got 1 app to install (hangouts dialer), but nothing else. I thought installing 1 by 1 might help, but all it allowed me to see was the downloads are restarting. I got up to 79%, then it went back to 0%, and then back up to 79% before the "960 error." I cleared PlayStore data, but same thing.

I'm going to run a build for you without the OC'ing. IF that clears it up it may just be that your phone doesn't like the higher frequencies... back when I was working on the xt912 some users could get higher frequencies without issue, others could not OC at all, or only slightly (all phones ARE slightly different). If you want to try the suggestion spainter made feel free, it can't hurt to try if you back up important stuff first. I will send you a pm when the build is ready. Sorry it's giving you such a hard time.

[motoxt926]

So after 10+ flashes, 3 downloads each of DU & Slim GApps, I finally got to the screen to enter my email & password. Previous to this, all I got was unable to connect to Google servers. Also in the setup process, I had several soft reboots, as well as times where i would go back to the start of setup (language choice). Even right before I successfully entered my email, I had entered the email & hit next, to only get the can't connect error, then went back to language selection.

I tried other roms in the middle of the DU flash attempts to make sure they flashed fine, and they did.

I chose to setup as a new device, as I was getting download errors of programs during this process. So I went to PlayStore immediately after reaching the home screen, and tried a random app, and got an "could not be downloaded due to an error (960)."

No idea what is wrong, or if it is just me, but I can't get things to jive on this rom.

update: I finally got 1 app to install (hangouts dialer), but nothing else. I thought installing 1 by 1 might help, but all it allowed me to see was the downloads are restarting. I got up to 79%, then it went back to 0%, and then back up to 79% before the "960 error." I cleared PlayStore data, but same thing.

I was having similar issues a week ago. I uninstalled busy box, wiped everything but external data 3 times and did a factory wipe which was probably over kill because I wiped internal data, flashed rom, flashed gapps. Also had to reboot 2 times right at beginning. One to get data working then once set up was done I had to reboot for my Google account to show up. I had to power down and power up one of them just the reboot button didn't fix it.

Sent from my DROID RAZR HD using Tapatalk

[dts2]

Every flash since November, I have done a full reset everytime. 3x (sometimes more) wipe of everything except microsd, and also format data twice. Never have come close a dirty flash. 

 

tried 3 different gApp packages (slim, banks, TK) and all seemed to have the same issues. So thinking it is my device and the rom. nice from what I did see.

[motoxt926]

Every flash since November, I have done a full reset everytime. 3x (sometimes more) wipe of everything except microsd, and also format data twice. Never have come close a dirty flash.

tried 3 different gApp packages (slim, banks, TK) and all seemed to have the same issues. So thinking it is my device and the rom. nice from what I did see.

Did u try not flashing gapps at all?

Sent from my DROID RAZR HD using Tapatalk

[motoxt926]

Did u try not flashing gapps at all?

Sent from my DROID RAZR HD using Tapatalk

Something else I did was fix permissions and repair files. I was desperate I really didn't want to go threw rsd or house of moto so I did everything I could threw twrp

Sent from my DROID RAZR HD using Tapatalk

[soocold]

I'm going to run a build for you without the OC'ing. IF that clears it up it may just be that your phone doesn't like the higher frequencies... back when I was working on the xt912 some users could get higher frequencies without issue, others could not OC at all, or only slightly (all phones ARE slightly different). If you want to try the suggestion spainter made feel free, it can't hurt to try if you back up important stuff first. I will send you a pm when the build is ready. Sorry it's giving you such a hard time.

OC fell off on the later production runs after they found out the chips they WERE using surpassed their minimums. So they went with cheaper chips that still meet stock frequency but that was all. MFGs do this all the time. Intel "k" cps, high end nvidia, ect. All get the very best chips and the lesser models are built from the rejected chips.

[jl90]

OC fell off on the later production runs after they found out the chips they WERE using surpassed their minimums. So they went with cheaper chips that still meet stock frequency but that was all. MFGs do this all the time. Intel "k" cps, high end nvidia, ect. All get the very best chips and the lesser models are built from the rejected chips.

That's very interesting stuff, thanks for the info man.

[Ziltoid]

I've been running the Test-v9.4 (7/12) build with the OC and when I went autocrossing last week in the heat I think it might have caused problems with too high temperatures. It was almost 100°F on the parking lot and I had the phone in my pocket out there for about 5 hours. I wasn't using it but when I tried to get directions home the phone was sooooo slow. I would tap on something and it wouldn't register until 30 seconds later. I told it to reboot and it took 5 minutes(maybe more, I wasn't timing) to shut down and start up again, and it was still slow. Later that day when it had cooled off it was better so I think it might be related to the OC. Edit: Or it could just be due to the heat and might have done the same thing on the stock clock settings.
 

Question 1) If I don't have any glitches or random reboots with the OS, is it safe to assume that my chip is capable of handling the OC fine? When it's not in the above extreme heat case (and at just room temperature) the phone isn't that fast in general, it's pretty normal for apps to hang for a couple seconds when doing really simple stuff on my phone. But it's not really slow either. It's about on par with Blisspop 5.1 from what I can remember.

 

Question 2) If I flash the OC version of 9.5, will dirty flashing the non-OC version of 9.5 over it be fine? And then back to the OC version again? I might try doing some benchmarks to see which one suits my phone better.

 

Regardless, thank you for this rom, it's easily the best one out for this phone right now.

[motoxt926]

OC fell off on the later production runs after they found out the chips they WERE using surpassed their minimums. So they went with cheaper chips that still meet stock frequency but that was all. MFGs do this all the time. Intel "k" cps, high end nvidia, ect. All get the very best chips and the lesser models are built from the rejected chips.

Anyone one know how to find the "date of birth" and when they stopped making the xt926?

[dedik46]

Hasbeen 4 days using this rom as my daily driver and i should say this rom is amazing i don't have any problem at all till now but there is one hasbeen annoying me that is low battery notification, how do i remove that so the notification doesn't show up anymore is there any setting to do that?

[soocold]

If you want more info I'll be glad to nerd out. I'm only a PM away

[soocold]

Anyone one know how to find the "date of birth" and when they stopped making the xt926?

That I'm not aware of. I just knew one of my three bionics had a different model chip than the others and I could successful nuke a battery running the CPU @1.4ghz and the GPU almost double the stock.

[Pow_2k]

I've been running the Test-v9.4 (7/12) build with the OC and when I went autocrossing last week in the heat I think it might have caused problems with too high temperatures. It was almost 100°F on the parking lot and I had the phone in my pocket out there for about 5 hours. I wasn't using it but when I tried to get directions home the phone was sooooo slow. I would tap on something and it wouldn't register until 30 seconds later. I told it to reboot and it took 5 minutes(maybe more, I wasn't timing) to shut down and start up again, and it was still slow. Later that day when it had cooled off it was better so I think it might be related to the OC. Edit: Or it could just be due to the heat and might have done the same thing on the stock clock settings.

Hmm... on my XT926 when running the latest stock Moto ROM one day I had received a heat warning.  Phone was in a cradle on my car dash, charging and also using the Waze app for navigation.  So between the radios and CPUs in use, the battery charging (and/or discharging, not sure my charger was putting out sufficient amps to keep up with power consumption), and the unit being in the sun I wasn't surprised.  But, was this a Moto warning or was it something in the OS itself?  Only saw it on that one trip and not sure when I may put the phone in similar conditions.

 

Separately, put DU on my phone yesterday, before that was running NoBe's build of AOSP.  Slim zero GApps were used.  Went pretty smooth and so far no troubles to speak of.  Been restoring backed up data as needed via TiBu.  Would be curious to know if anyone has tried the backup/restore functionality included with Android (LP only I think?) that uses the associated Google account.

[Pow_2k]

Ok, let me know if I'm missing something here.  I use a dock for charging, the phone makes a great bedside clock in that way.  But something that I've found which differs from the previous ROM (NoBe's [AOSP] AOD-CuStOm) I was using...  While in the dock the Daydream feature will display the time on the face, fading it in and out, moving it to different screen locations.  In the last ROM if I wanted to see screen notices that had popped up while I wasn't paying attention I would simply touch the screen and it would go to the normal lock screen where I could see what sort of alerts I had.  On this ROM (DU 9.5 official) a touch to the screen just blacks it out entirely.  As does any button press.  To see the screen I first need to touch something and then press the power button.  I'm not sure why this is?  Maybe there is a setting I need to change?

 

Otherwise, very pleased so far! Great work!

[jl90]

Ok, let me know if I'm missing something here. I use a dock for charging, the phone makes a great bedside clock in that way. But something that I've found which differs from the previous ROM (NoBe's [AOSP] AOD-CuStOm) I was using... While in the dock the Daydream feature will display the time on the face, fading it in and out, moving it to different screen locations. In the last ROM if I wanted to see screen notices that had popped up while I wasn't paying attention I would simply touch the screen and it would go to the normal lock screen where I could see what sort of alerts I had. On this ROM (DU 9.5 official) a touch to the screen just blacks it out entirely. As does any button press. To see the screen I first need to touch something and then press the power button. I'm not sure why this is? Maybe there is a setting I need to change?

Otherwise, very pleased so far! Great work!

Honestly I'm not sure, I've never used the phone that way. I will ask the other team members if they have tried doing that and get back to you. 😀

[jl90]

So I got my Nexus 6 today (64gb from el goog)!!! What an awesome phone! Anyways rest assured I will continue developing for the HD, I still have it and will keep it as a dev device/backup.

[soocold]

I haven't booted my N4 since I got the N6 iirc the N4 is still on KitKat. Welcome to the whale club.

[watson387]

So I got my Nexus 6 today (64gb from el goog)!!! What an awesome phone! Anyways rest assured I will continue developing for the HD, I still have it and will keep it as a dev device/backup.

Nice! You'll love this phone!

Sent from my Pure Nexus 6