Develop Bugs

updated viperone OTA from 1.3.0 to 1.40 and now NO ON SCREEN BUTTONS

since the update the 3 main on screen buttons have disappeared.
is there somewhere in the options to put them back ? since the update its been hell to use my phone.

htcuser3000 said:
since the update the 3 main on screen buttons have disappeared.
is there somewhere in the options to put them back ? since the update its been hell to use my phone.
Click to expand...
Click to collapse
go to venom tweaks then keyboard,buttons ,navigation bar

It worked thank you

htcuser3000 said:
It worked thank you
Click to expand...
Click to collapse
No worries

LCB43B - Huawei Watch update rolling out

Huawei Watch Receives Maintenance Release
Optimized the mic gain for improved "Ok Google" detection
Optimized the fitness tracking to improve step counting accuracy
Optimized the Bluetooth reconnect mechanism
Add a new app to display the battery level when charging
Add a new watch face that user can self-customize
Add fusion sensor of gravity/linear acceleration/rotation vector
Download link in post http://forum.xda-developers.com/showpost.php?p=64009566&postcount=14
you need to be full stock to flash it.

Nothing yet.
Sent from my Nexus 6P using Tapatalk

Can we still get a OTA update with a unlocked bootloader and a custom kernel?

stalls said:
Can we still get a OTA update with a unlocked bootloader and a custom kernel?
Click to expand...
Click to collapse
Nope. I flashed back to stock for it.

bmg1001 said:
Nope. I flashed back to stock for it.
Click to expand...
Click to collapse
dang ok

Changes according to this article are:
Optimized the mic gain for improved "Ok Google" detection
Optimized the fitness tracking to improve step counting accuracy
Optimized the Bluetooth reconnect mechanism
Add a new app to display the battery level when charging
Add a new watch face that user can self-customize
Add fusion sensor of gravity/linear acceleration/rotation vector
I have not received the OTA update yet. I thought the next update would bring speaker support which would have been awesome, but I of course appreciate other improvements as well.

..

MuF123 said:
so do I have to reflash:
-boot
-recovery
-system
and put oem lock back on?
And now - how can I now I am elligle to update? It won't update, however I don't know if it is because it was not rolled out for me yet OR if there is still problem with the watch that prevents it to be OTA updated.
Any ideas?
Click to expand...
Click to collapse
I think you'll need to wait until the OTA is available. I'm on stock and still don't have anything.

bmg1001 said:
Nope. I flashed back to stock for it.
Click to expand...
Click to collapse
how do i lock the bootloader again?

Hopefully I'll be able to use the always on mode without the watch locking up inside of 10 minutes.

earlymorninghours said:
Hopefully I'll be able to use the always on mode without the watch locking up inside of 10 minutes.
Click to expand...
Click to collapse
I'm hoping for that too. Mine isn't as bad if I use a stock face, but I like the ones I've picked out from the Play Store.
Sent from my LG-H810 using Tapatalk
---------- Post added at 10:29 AM ---------- Previous post was at 10:24 AM ----------
Motawa88 said:
how do i lock the bootloader again?
Click to expand...
Click to collapse
After you are back to 100% stock use commands
fastboot devices
fastboot oem lock
fastboot reboot
Sent from my LG-H810 using Tapatalk

Motawa88 said:
how do i lock the bootloader again?
Click to expand...
Click to collapse
Unlocked bootloaders are fine with OTAs

Anyway someone can just upload the new update so we can all flash it?

The update seems available here : : https://drive.google.com/file/d/0B4CYHidtQWQGWG1Pbjd6QUYxQzg/view?usp=sharing
source :https://www.reddit.com/r/hwatch/comments/3u9g3e/huawei_watch_lcb43b_update_updatezip_for/
Code:
go to command windows and type : adb reboot bootloader.
choose "reboot-recovery" by clicking fast to go to the right menu, then long press to select it.
the choose apply sideload ADB by swipe down then swipe left/right
and then type : adb sideload update.zip
wait, reboot, wait again and enjoy

imfloflo said:
The update seems available here : : https://drive.google.com/file/d/0B4CYHidtQWQGWG1Pbjd6QUYxQzg/view?usp=sharing
source :https://www.reddit.com/r/hwatch/comments/3u9g3e/huawei_watch_lcb43b_update_updatezip_for/
Code:
go to command windows and type : adb reboot bootloader.
choose "reboot-recovery" by clicking fast to go to the right menu, then long press to select it.
the choose apply sideload ADB by swipe down then swipe left/right
and then type : adb sideload update.zip
wait, reboot, wait again and enjoy
Click to expand...
Click to collapse
getting a error after loading 19%
E: ERROR executing updater binary in zip '/sideload/package.zip'

stalls said:
getting a error after loading 19%
E: ERROR executing updater binary in zip '/sideload/package.zip'
Click to expand...
Click to collapse
No error for me 100% a bit long but it all works.
Are you sure there is no problem with your usb ?
The new charging screen is nice, and the new custom watch face too.

imfloflo said:
No error for me 100% a bit long but it all works.
Are you sure there is no problem with your usb ?
The new charging screen is nice, and the new custom watch face too.
Click to expand...
Click to collapse
Do I have to be stock in any way? I have the boot loader unlocked, custom kernel, and twrp.

stalls said:
Do I have to be stock in any way? I have the boot loader unlocked, custom kernel, and twrp.
Click to expand...
Click to collapse
I believe you do have to be on stock, but the bootloader's state doesn't matter.

Do I need the watch to be connected to WiFi? How do I update the watch?

stalls said:
Do I have to be stock in any way? I have the boot loader unlocked, custom kernel, and twrp.
Click to expand...
Click to collapse
Yes you will need to roll back to stock. Bootloader can stay unlocked.
redeuxx said:
Do I need the watch to be connected to WiFi? How do I update the watch?
Click to expand...
Click to collapse
If you are waiting for the OTA, you will just have to wait until it gets pushed to your watch. You can checked by clicking the system update button in the about screen on the watch, but its rolling out in stages so there is no definitive time on when your watch will get it.

Bugs in 4.1.0 update

Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.

Taran3105 said:
Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.
Click to expand...
Click to collapse
Also the volume keys are not working.

no brothers both the capacitive buttons and volume rockers work flawlessly on 4.1.0

all is working for me :-/

Working fine for me.

Working fine for me. Seems like a temp issue or a wrong flash to me. You can try wiping system and flash full zip. If you are fully stock, i would advise to perform a factory reset.

Taran3105 said:
Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.
Click to expand...
Click to collapse
Sounds like a firmware issue. I suggest a full reflash.

I did a clean flash 4.0.3&4.1.0 OTA. Sometimes pulling down the notifications doesn't darken the background.

Clean flash ..stop making up bs posts

I cannot launch Google Assistant by voice with the screen off, whereas I could before the update

croques said:
I cannot launch Google Assistant by voice with the screen off, whereas I could before the update
Click to expand...
Click to collapse
As i have been saying repeatedly, the OTAs from OnePlus suck.
Clean flash the full ROM.

andrneumann said:
I did a clean flash 4.0.3&4.1.0 OTA. Sometimes pulling down the notifications doesn't darken the background.
Click to expand...
Click to collapse
Please PM me if you ever find a fix for this.. it forced me to use another ROM

Never call it Touch ID... This is not Apple.

works fine here clean flash

azaidi said:
Please PM me if you ever find a fix for this.. it forced me to use another ROM
Click to expand...
Click to collapse
Clean flashed again, now with OOS full zip 4.1.0, same thing. Pulling down notifications not always darken the rest of the screen. Still looking for a fix.

Factory reset solved the problem.

croques said:
I cannot launch Google Assistant by voice with the screen off, whereas I could before the update
Click to expand...
Click to collapse
I could never do that

andrneumann said:
Clean flashed again, now with OOS full zip 4.1.0, same thing. Pulling down notifications not always darken the rest of the screen. Still looking for a fix.
Click to expand...
Click to collapse
Did u find anything?
having the same issue
guess very few are having this issue (not many reported)

Anyone who's shortcut to for example a document on the home screen doesn't work anymore?
I already deleted the shortcut and made a new one, but still doesn't work

Ronak Chandak said:
Did u find anything?
having the same issue
guess very few are having this issue (not many reported)
Click to expand...
Click to collapse
I have the same issue...

Nougat 7.1.1 is rolling out!

Hey everyone, been a little while, but 7.1.1 N is rolling out to you guys.

Awesome! Is this the same 108 build that went out to beta testers?

Does it include the battery optimization that was mentioned some time ago?

***

New update appears to be uncertified and Android Pay doesn't work.... any way to fix this?

ipowyourface said:
New update appears to be uncertified and Android Pay doesn't work.... any way to fix this?
Click to expand...
Click to collapse
Is your bootloader unlocked?

Nextbit_Khang said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No, I relocked it after I flashed the image and turned off the oem unlocking option after. I was previously rooted though, but the script on the image should have taken care of that right?

ipowyourface said:
No, I relocked it after I flashed the image and turned off the oem unlocking option after. I was previously rooted though, but the script on the image should have taken care of that right?
Click to expand...
Click to collapse
Yeah that's kinda weird. It should work. I'll ask around.

Nextbit_Khang said:
Yeah that's kinda weird. It should work. I'll ask around.
Click to expand...
Click to collapse
Yeah, there was another person on the Razer forums who had the same problem as well.

Just got my Nextbit today updated few times before work on 7.0 present and update pending hopefully 7.1.1 , How's the update ? any issues fixed not had it long enough to find any
Sent from my Robin using Tapatalk

Nextbit_Khang said:
Yeah that's kinda weird. It should work. I'll ask around.
Click to expand...
Click to collapse
I figured it out, I had just came from Omni Rom. For some reason, I had to flash the 6.0 image then flash the 7.1.1 image and now everything passes, and AP works.

ipowyourface said:
I figured it out, I had just came from Omni Rom. For some reason, I had to flash the 6.0 image then flash the 7.1.1 image and now everything passes, and AP works.
Click to expand...
Click to collapse
You had to re-lock your bootloader also, correct?

Is anybody having issues with sending text messages (your standard text message) with WiFi on? Not over WiFi, but just with WiFi on. I tried the default messaging app and the Google one. They both work the same. For me to get a text message out, I have to turn off WiFi.

I flashed stock N88 and still have TWRP recovery installed I got a system update that updated now stock on nextbit logo on boot , is this coz I still have TWRP recovery or just bad update would factory reset in TWRP fix ? Thanks
Sent from my MotoG3 using Tapatalk

DoobyDroid said:
I flashed stock N88 and still have TWRP recovery installed I got a system update that updated now stock on nextbit logo on boot , is this coz I still have TWRP recovery or just bad update would factory reset in TWRP fix ? Thanks
Click to expand...
Click to collapse
Why don't you flash the latest factory image?
You can't flash an OTA update via custom recovery.

Loving this new update!
However, if you want to save resources and please your customers at the same time when doing the next update -
skip the nextbit bits.
Just make the next updates (if you plan on making any more of course) stock, for all intents and purposes, except perhaps for the backup/cloud feature.

revert back to 7.0 ?
since i updated to 7.1.1, my pebble 2 would constantly disconnect.
how to revert back to plan 7.0 ?
thanks!

Any word on android 8

Franzferdinan51 said:
Any word on android 8
Click to expand...
Click to collapse
Lmao very doubtful

hey there guys i'm having this weird trouble updating to 7.1.1, i'm currently on 7.0 (Robin_Nougat_88) and i have downloaded the 7.1.1 update (560 mb) and when i hit the "reboot and install" button it say restarting in 10 ... 9... 8 blah blah then rebooting now and never get to reboot... i can't install this update is there some solution? do i have to install the N108 image like new following the razer thread? thanks in advice guys have a good day!

Development Stock Rom

Link
https://drive.google.com/file/d/1BxZVXPubTA9U4PsJdCGrcisc15wmAUw8/view?usp=sharing

lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Moto Updates Tracker
An automated channel that tracks Motorola updates releases. By @vachounet and @yshalsager https://mirrors.lolinet.com/firmware/motorola More automated channels that you may like: @yshalsager_projects
t.me

sd_shadow said:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Moto Updates Tracker
An automated channel that tracks Motorola updates releases. By @vachounet and @yshalsager https://mirrors.lolinet.com/firmware/motorola More automated channels that you may like: @yshalsager_projects
t.me
Click to expand...
Click to collapse
Stock rom page not loading what to do ?

Sanuarul Islam said:
Link
https://drive.google.com/file/d/1BxZVXPubTA9U4PsJdCGrcisc15wmAUw8/view?usp=sharing
Click to expand...
Click to collapse
no failure

Surenmof1 said:
Stock rom page not loading what to do ?
Click to expand...
Click to collapse
Try again. Seems to be working now.

arsradu said:
Try again. Seems to be working now.
Click to expand...
Click to collapse
Would that be flashed thru Twrp, would that include Gapps, or there any other problem flashing that in a Unlocked bootloader. Now am using lineage 19 only issue is that ambient display & double tap to wake up doesn't. I don't wanna use power button often Or Aosp 13 any good to flash on ?

Surenmof1 said:
Would that be flashed thru Twrp, would that include Gapps, or there any other problem flashing that in a Unlocked bootloader. Now am using lineage 19 only issue is that ambient display & double tap to wake up doesn't. I don't wanna use power button often Or Aosp 13 any good to flash on ?
Click to expand...
Click to collapse
1. No, that would be flashed using the commands within the zip file (from flashfile.xml).
You can also use RSA/LMSA to get the stock ROM. If you've never done it via fastboot commands (from that flashfile.xml), my recommendation would be to do it from RSA. This should also give you the correct version for your region.
2. Yes, that includes GApps (same if you flash it from RSA).
3. No, there are no problems flashing that with an unlocked bootloader.
4. right now, since there is no support for any G40/G60 ROMs, my recommendation would be to stick with a ROM that works best for you. AOSP 13 still has some issues, and since there's no one to fix them, you'll be stuck with that ROM. You have more info on what works and doesn't work with that ROM on that specific thread.
So...if Lineage doesn't work as expected, my recommendation would be to go back to stock ROM, for now. And DON'T lock the bootloader. At least not right now. There's a risk of bricking your phone.

arsradu said:
1. No, that would be flashed using the commands within the zip file (from flashfile.xml).
You can also use RSA/LMSA to get the stock ROM. If you've never done it via fastboot commands (from that flashfile.xml), my recommendation would be to do it from RSA. This should also give you the correct version for your region.
2. Yes, that includes GApps (same if you flash it from RSA).
3. No, there are no problems flashing that with an unlocked bootloader.
4. right now, since there is no support for any G40/G60 ROMs, my recommendation would be to stick with a ROM that works best for you. AOSP 13 still has some issues, and since there's no one to fix them, you'll be stuck with that ROM. You have more info on what works and doesn't work with that ROM on that specific thread.
So...if Lineage doesn't work as expected, my recommendation would be to go back to stock ROM, for now. And DON'T lock the bootloader. At least not right now. There's a risk of bricking your phone.
Click to expand...
Click to collapse
Flashing stock rom seems risky so I stick with lineage 19 it has good battery backup only missing is the ambient display, double to wake up so can live with it, Hope there would be some new builds for this device.

Surenmof1 said:
Would that be flashed thru Twrp, would that include Gapps, or there any other problem flashing that in a Unlocked bootloader. Now am using lineage 19 only issue is that ambient display & double tap to wake up doesn't. I don't wanna use power button often Or Aosp 13 any good to flash on ?
Click to expand...
Click to collapse
aosp13 has nothing but gapps, it's ok to use it, it saves power

xindefenggan said:
aosp13 has nothing but gapps, it's ok to use it, it saves power
Click to expand...
Click to collapse
Ambient display works in that?

Surenmof1 said:
Ambient display works in that?
Click to expand...
Click to collapse
Ambient display?

xindefenggan said:
Ambient display?
Click to expand...
Click to collapse
when you pick up the phone it turns on the lock screen and when receiving notifications the display turns on

Surenmof1 said:
when you pick up the phone it turns on the lock screen and when receiving notifications the display turns on
Click to expand...
Click to collapse
No Pick up will not display Double tap will not wake up

arsradu said:
1. No, that would be flashed using the commands within the zip file (from flashfile.xml).
You can also use RSA/LMSA to get the stock ROM. If you've never done it via fastboot commands (from that flashfile.xml), my recommendation would be to do it from RSA. This should also give you the correct version for your region.
2. Yes, that includes GApps (same if you flash it from RSA).
3. No, there are no problems flashing that with an unlocked bootloader.
4. right now, since there is no support for any G40/G60 ROMs, my recommendation would be to stick with a ROM that works best for you. AOSP 13 still has some issues, and since there's no one to fix them, you'll be stuck with that ROM. You have more info on what works and doesn't work with that ROM on that specific thread.
So...if Lineage doesn't work as expected, my recommendation would be to go back to stock ROM, for now. And DON'T lock the bootloader. At least not right now. There's a risk of bricking your phone.
Click to expand...
Click to collapse
Thanks for the info RSA worked well mate moto has many features and eats up ram and slowing down but it's fine hoping for good android 13 builds to flash.