Database Users

Vine for Android here! Bug on CM?

Hey guys,
I am the Android engineer responsible for the video playback and recording components on the Vine for Android app. We noticed that there is a bug on a rooted 4.2.2 ROM (mostly S2, prob CM related) that it did not implement one of the camera method (specifically, onPreviewFrame, the data returns null when using image buffering) that we are relying on to work properly. Just want to let you guys know what the problem is.
Best,
Edison Wang
Vine Labs (Twitter Inc.)

I'm on CM10.1 (4.2.2) on my Nexus S and I still have the "Initializing" problem after the update.

@op you do know about the open source camera s2 use ,you can look into that
Replicant guys made it
Sent from my GT-I9100 using xda app-developers app

Recording worked when I was on stock 4.1.2 rom, but it force closes upon recording when I'm on cm10.1. Is there an easy fix for this?

wzsddtc2 said:
Hey guys,
I am the Android engineer responsible for the video playback and recording components on the Vine for Android app. We noticed that there is a bug on a rooted 4.2.2 ROM (mostly S2, prob CM related) that it did not implement one of the camera method (specifically, onPreviewFrame, the data returns null when using image buffering) that we are relying on to work properly. Just want to let you guys know what the problem is.
Best,
Edison Wang
Vine Labs (Twitter Inc.)
Click to expand...
Click to collapse
Any news on this bug fix?

Vine crash
I'm on latest update of Vine.
It still crashes less than a second after recording. I keep on sending crash reports hoping they can fix it.
I am running X-treme JB rom v9 with Dorimanx kernal. Android 4.2.2.
Best ROM I've ever used. Everything else works great but I just want Vine to work!

wzsddtc2 said:
Hey guys,
I am the Android engineer responsible for the video playback and recording components on the Vine for Android app. We noticed that there is a bug on a rooted 4.2.2 ROM (mostly S2, prob CM related) that it did not implement one of the camera method (specifically, onPreviewFrame, the data returns null when using image buffering) that we are relying on to work properly. Just want to let you guys know what the problem is.
Best,
Edison Wang
Vine Labs (Twitter Inc.)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=43063033&postcount=24753
Cheers!
Enviado desde mi GT-I9100

new update
vine has updated.
they say its the biggest update yet for android and has new shooting options ansd camera options etc.
might be worth trying again with a 4.2.2 rom to see if it works.
i am sticking with neatrom for the min (4.1.2) as it works with instagram and vine. once both aps work with 4.2.2 aosp and aokp based roms i will go back. i miss halo and pie

hetster said:
vine has updated.
they say its the biggest update yet for android and has new shooting options ansd camera options etc.
might be worth trying again with a 4.2.2 rom to see if it works.
i am sticking with neatrom for the min (4.1.2) as it works with instagram and vine. once both aps work with 4.2.2 aosp and aokp based roms i will go back. i miss halo and pie
Click to expand...
Click to collapse
Thanks for the info. Just updated and it still crashes. Unlike last time it would be half a second, now it's instant.
However! Using the front facing camera works! Progress?

jkne said:
Thanks for the info. Just updated and it still crashes. Unlike last time it would be half a second, now it's instant.
However! Using the front facing camera works! Progress?
Click to expand...
Click to collapse
i think its going to be a long wait. most aosp roms are based on CM. the problem is CM use a hacked rear camera with higher resolution. aps are created using normal android firmware so dont take into account the new hacked camera. unfortunately i think the makers of vine will see modified firmware user base as quite small so not bother to change their app and CM is unlikely to undo a better camera for the sake of 2 aps (same bug is in instagram video for the very same reason as vine)
neatrom works with them all as they are based on original samsung firmware but i prefer aosp roms but till the bugs for these 2 aps are sorted i'll have to stick to neatrom as 80% of what i do on my phone is instagram or vine related. oh well
full explanation from dorimax here
http://forum.xda-developers.com/showpost.php?p=43063033&postcount=24753

WTFFF
wzsddtc2 said:
hey guys,
i am the android engineer responsible for the video playback and recording components on the vine for android app. We noticed that there is a bug on a rooted 4.2.2 rom (mostly s2, prob cm related) that it did not implement one of the camera method (specifically, onpreviewframe, the data returns null when using image buffering) that we are relying on to work properly. Just want to let you guys know what the problem is.
Best,
edison wang
vine labs (twitter inc.)
Click to expand...
Click to collapse
how can you not fix this? We are waiting!!!!!!!!!!!!!!

bombsofgold said:
how can you not fix this? We are waiting!!!!!!!!!!!!!!
Click to expand...
Click to collapse
I wish either Vine or CM and X-treme could come up with some kind of workaround.
I am missing a lot of moments that a standard photograph cannot capture and a video is too cumbersome.
I'm having to use my girlfriends iPhone when I have perfectly good Android hardware in my pocket!
By the time I have the iPhone in my hand and unlocked the precious 6 second moment is gone, FOR EVER.
Come on Vine! Can't you enable a compatibility mode or anything? :crying:

X-treme Rom v10 will be ready soon by the looks of things. Looking forward to it!
Does anyone know if this will fix the problem? (cannot currently write on all threads as I haven't enough posts)

@wzsddtc2
Nasty bug. Vine seems to be the only app on cm 10.2 that does not work..
with the latest update they outright claim your device is not supported. (It worked perfectly on Official 4.1.2 roms)
is this going to be fixed?

chuckiler said:
@wzsddtc2
Nasty bug. Vine seems to be the only app on cm 10.2 that does not work..
with the latest update they outright claim your device is not supported. (It worked perfectly on Official 4.1.2 roms)
is this going to be fixed?
Click to expand...
Click to collapse
That's be cause we are probably the only app that uses that special method that Samsung broke.
The same bug happens on S4's front facing camera driver, but Samsung has provided a workaround for that (we post-process the images).
On Cyangenmod, the problem is they don't even pass back a bad frame, it just passes back nothing, so we can't apply any workarounds there.

hetster said:
i think its going to be a long wait. most aosp roms are based on CM. the problem is CM use a hacked rear camera with higher resolution. aps are created using normal android firmware so dont take into account the new hacked camera. unfortunately i think the makers of vine will see modified firmware user base as quite small so not bother to change their app and CM is unlikely to undo a better camera for the sake of 2 aps (same bug is in instagram video for the very same reason as vine)
neatrom works with them all as they are based on original samsung firmware but i prefer aosp roms but till the bugs for these 2 aps are sorted i'll have to stick to neatrom as 80% of what i do on my phone is instagram or vine related. oh well
full explanation from dorimax here
http://forum.xda-developers.com/showpost.php?p=43063033&postcount=24753
Click to expand...
Click to collapse
That's not true. We saw the log from CM's bug tracker, it is entirely on their side and they just won't admit it.
Apps will request 640x480 preview size, but CM will report it succeeded but record at 720x480, which is a higher resolution.
We use onPreviewFrame() to get video frames and expect 640x480 frames, but CM will give frames at 720x480.
Because we give buffer frames at the smaller size, CM will treat them as invalid buffers and then just drop the frames.
Totally insane.

I'm using a t0ltetmo with the newest Carbon Nightly and Vine recording doesn't work.
Do you guys have a list of custom ROMs that is compatible with your app?
This is a bit annoying.

Hi there, Vine still doesn't work
Did you give up ?
(Sorry wrong thread)

orangeraf said:
Hi there, Vine still doesn't work
Did you give up ?
(Sorry wrong thread)
Click to expand...
Click to collapse
Yeah I gave up. I got an S4, running AOSB and everything is working well.
The S2 is a backup phone now.

ok so apparently no one fixed this issue.. i tried a bunch of cm based roms and different versions of android and ive found problems with video upload to instagram (upload bar just stuck at middle and wont go on), vine app wont work (it just tells me that im using custom rom and there's a problem with camera), upload videos to twitter also stuck.. so it seems to me that the problem is with CM kernel and video format.
still cant believe that no one addressed this issue over 2 years now, im stunned

Camera is really slow

Hi. Has anyone experienced really slow camera performance with S3 Neo? Like you pressing shutter button in camera app and image is actually being taken 3-8 seconds after that?
I got this issue on CM12 and CM12.1, didn't tried other ROMs yet. I've tried different camera apps, Google Camera, OpenCamera and CM stock one. Each of those apps seems to be affected the same way. It works a bit better after reboot and cleaning camera app cache but I can't do that often. If someone can help me with this, I'd really appreciate. Thanks.
PS: I've tried camera fix from this forum but probably it's for some other issue as my camera stopped worked completely after applying fix and I had to re-flash ROM.

Camera fix is for devices that have a different camera sensor (there are two). So that's indeed not the right file. As for the camera speed, I'm not really sure. Mine is also really slow (cm12,1). I've come to live with it because i rarely use my camera anyway. I've tested some touchwiz based roms, and the camera was faster on those :/
Sent from my GT-I9301I using XDA-Developers mobile app

stelio_kontos said:
As for the camera speed, I'm not really sure. Mine is also really slow (cm12,1). I've come to live with it because i rarely use my camera anyway. I've tested some touchwiz based roms, and the camera was faster on those :/
Click to expand...
Click to collapse
OK, it seems like we're getting somewhere. Could it be CM issue? Maybe some other CM users can write a word about their camera app speed? I really like CM though, stock ROMs are overloaded with tons of software that is never used.

Nikola's CM have some issues with camera timing, and Motion based roms have laggy camera performance
Better to go with stock, because it uses the camera at the maximum performance.

ziad311 said:
Nikola's CM have some issues with camera timing, and Motion based roms have laggy camera performance
Better to go with stock, because it uses the camera at the maximum performance.
Click to expand...
Click to collapse
Thanks! I'm currently testing CM based '[ROM][Stable][5.1.1][December 31]Resurrection Remix 5.5.9 - Final version' and it looks better. Need more testing though. Stock is too awful to use, I'd better live with slow camera, but maybe there's a solution.

Nope, Resurrection Remix is slow either, CM's curse. OK, I got it - fast camera OR fast ROM, no exceptions. Too bad, maybe CM13 will fix this?

Camera Quality is Poor
S3 original is better than this..
regards Junaid Shahid

I've found 'lite' version of original firmware made by guys from 4PDA (link to original thread, sorry it's in russian).
It's 500 MB in archive and almost all Samsung stuff has been removed, so it's as clean and fast as possible. Camera works fine. In case someone else may need it, here's direct link.
Please note that I'm not the author of this firmware, not related to him in any way and not responsible for your flashing experience.

NastyRose said:
I've found 'lite' version of original firmware made by guys from 4PDA (link to original thread, sorry it's in russian).
It's 500 MB in archive and almost all Samsung stuff has been removed, so it's as clean and fast as possible. Camera works fine. In case someone else may need it, here's direct link.
Please note that I'm not the author of this firmware, not related to him in any way and not responsible for your flashing experience.
Click to expand...
Click to collapse
Any bugs on this lite rom ?

kico94 said:
Any bugs on this lite rom ?
Click to expand...
Click to collapse
Haven't found any yet. 4.4 is not as good as 5.1, of course, but the camera is awesome

NastyRose said:
Haven't found any yet. 4.4 is not as good as 5.1, of course, but the camera is awesome
Click to expand...
Click to collapse
What about apps and interface? Except what is removed, everything else is all stock or anything replaced with 3rd party apps or other kind of mods? Because if so, it's not for me, I go for stock anytime.

kico94 said:
What about apps and interface? Except what is removed, everything else is all stock or anything replaced with 3rd party apps or other kind of mods? Because if so, it's not for me, I go for stock anytime.
Click to expand...
Click to collapse
Well, it looks like stock to me: http://pyaka.ga/litestock.png
Some Samsung apps and probably all settings are still there.
I've made some tweak using GravityBox, so clock, battery indicator does not look as they were initially.

NastyRose said:
Well, it looks like stock to me: http://pyaka.ga/litestock.png
Some Samsung apps and probably all settings are still there.
I've made some tweak using GravityBox, so clock, battery indicator does not look as they were initially.
Click to expand...
Click to collapse
Flashing it now. I hope it is good on what I expect, otherwise its the last rom i ever try.

Is it possible to go back to lollipop?

I'm sick of my Moto X Style not running smoothly on stock android 6.0.1. Some custom roms fixed that but had other problems like calling echoes, slow camera launching, not being able to playback videos on facebook etc... Will i brick my phone if i try to roll back, or can i actually do it?

At worst you will softbrick it... I doubt it would hardbrick, but most of the threads where people have tried to downgrade have not gone well but they eventually get it working. Moto's don't like to be downgraded, the big problem is the partition table changes from Lollipop to Marshmallow and it won't go back. Although I don't know about this device specifically, but several older Moto's would brick if you downgraded then took an OTA later due to the mismatch of bootload and gpt partition table versions.
I would try to find solutions to your problems with MM rather than downgrade... I don't have any issues with any of the problems you are stating with echo, camera launch (mine is ready to take pictures in less than 2 seconds from either lock screen or icon), and Facebook works fine. Guess I am a little puzzled, but then again I am on 6.0.0 on the Pure.

akeflo said:
I'm sick of my Moto X Style not running smoothly on stock android 6.0.1. Some custom roms fixed that but had other problems like calling echoes, slow camera launching, not being able to playback videos on facebook etc... Will i brick my phone if i try to roll back, or can i actually do it?
Click to expand...
Click to collapse
It is possible if you have a TWRP backup of lollipop. I have done it before and it does work.

!Iamdeath! said:
It is possible if you have a TWRP backup of lollipop. I have done it before and it does work.
Click to expand...
Click to collapse
It's possible even without a backup too.

Spasticdroid said:
It's possible even without a backup too.
Click to expand...
Click to collapse
It is possible, but as mentioned by @acejavelin, it could cause issues later. The better option is to try and work out the current issues. Since the OP obviously has TWRP installed, my recommendation for stock ROM is to possibly look at apps that may be the culprits. Other options can include custom kernels.

Thank you so much everyone! But then, how do i do it? Is there anyone who has done it before and could help me? I don't have a lollipop backup on my TWRP btw..

acejavelin said:
At worst you will softbrick it... I doubt it would hardbrick, but most of the threads where people have tried to downgrade have not gone well but they eventually get it working. Moto's don't like to be downgraded, the big problem is the partition table changes from Lollipop to Marshmallow and it won't go back. Although I don't know about this device specifically, but several older Moto's would brick if you downgraded then took an OTA later due to the mismatch of bootload and gpt partition table versions.
I would try to find solutions to your problems with MM rather than downgrade... I don't have any issues with any of the problems you are stating with echo, camera launch (mine is ready to take pictures in less than 2 seconds from either lock screen or icon), and Facebook works fine. Guess I am a little puzzled, but then again I am on 6.0.0 on the Pure.
Click to expand...
Click to collapse
On stock ROM everything works but lags, but for example on cm13 videos on facebook won't playback, switching to front facing camera takes maybe 10 seconds and the echo is there when speaking on the phone. What ROM are you using?

akeflo said:
On stock ROM everything works but lags, but for example on cm13 videos on facebook won't playback, switching to front facing camera takes maybe 10 seconds and the echo is there when speaking on the phone. What ROM are you using?
Click to expand...
Click to collapse
Stock, and I have no "lag" to speak of, but my point of references lately are the Moto G3, Nexus 4, and Lumia 640 LTE so by these standard the Pure is a Ferrari by comparison.
Sent from my Motorola XT1575 using XDA Labs

I'm using stock with no lag. I get the occasional stutter every now and then but that has been the case with every Android I have owned. Have you gone to developer options and changed the Windows animation scale and Transition animation scale to 0.5? This might help.

acejavelin said:
Stock, and I have no "lag" to speak of, but my point of references lately are the Moto G3, Nexus 4, and Lumia 640 LTE so by these standard the Pure is a Ferrari by comparison.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Haha i see! Well my comparison is with a Nexus 5x and an LG G2 and i hardly can't tell a difference between my moto and the LG G2 with a cyanogen based ROM. The Nexus is clearly the smoothest of all three.

aybarrap1 said:
I'm using stock with no lag. I get the occasional stutter every now and then but that has been the case with every Android I have owned. Have you gone to developer options and changed the Windows animation scale and Transition animation scale to 0.5? This might help.
Click to expand...
Click to collapse
Yes every android has some lag now and then but my Nexus 5X ran much smoother than the Moto X. It lags when i open the app drawer for instance which is the most simple task ever. It really pisses me off. I will try changing animation speed, thank you.

akeflo said:
I'm sick of my Moto X Style not running smoothly on stock android 6.0.1. Some custom roms fixed that but had other problems like calling echoes, slow camera launching, not being able to playback videos on facebook etc... Will i brick my phone if i try to roll back, or can i actually do it?
Click to expand...
Click to collapse
I flashed Android Lollipop many times but wifi doesn't work so I am not able to log in into Google account so I flash back marshmallow. I especially face serious lag when scrolling through YouTube in marshmallow.

[email protected] said:
I flashed Android Lollipop many times but wifi doesn't work so I am not able to log in into Google account so I flash back marshmallow. I especially face serious lag when scrolling through YouTube in marshmallow.
Click to expand...
Click to collapse
Are you clean flashing? I've flashed several different roms and none of them have lagged for me the slightest bit.
Sent from my XT1575 using Tapatalk

Z5p dual has the Mokee based on Nought

As the title said,the Z5p dual has the Mokee rom.......
When I flashed it on my E6853,I find that the camera can't take a picture and the other apps need to take picture,still not work.But it works well on E6883.So can do something change to it to fix the bug on E6853?It's a fantastic rom,hope it can works well on E6853:fingers-crossed::fingers-crossed::fingers-crossed:

nuanfengqingyu said:
As the title said,the Z5p dual has the Mokee rom.......
When I flashed it on my E6853,I find that the camera can't take a picture and the other apps need to take picture,still not work.But it works well on E6883.So can do something change to it to fix the bug on E6853?It's a fantastic rom,hope it can works well on E6853:fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
It's possible sharing link for this rom ? https://download.mokeedev.com/?device=satsuki not exist here link delete !
Thank you

It sitll exist yesterday.Maybe something happened.Wait for it come back.

It has reupdated at 2017-03-08 19:00:10.May someone could make a rom for z5p E6853~~~Thanks~

nuanfengqingyu said:
It has reupdated at 2017-03-08 19:00:10.May someone could make a rom for z5p E6853~~~Thanks~
Click to expand...
Click to collapse
me too !!! this rom is good !!! im wait for E6853 !!!
have you got test @nuanfengqingyu with boot.img aosp @Elfmirth thread here https://forum.xda-developers.com/z5-premium/orig-development/aosp-7-1-z5-premium-e6853-t3519216

xrenoix said:
me too !!! this rom is good !!! im wait for E6853 !!!
have you got test @nuanfengqingyu with boot.img aosp @Elfmirth thread here https://forum.xda-developers.com/z5-premium/orig-development/aosp-7-1-z5-premium-e6853-t3519216
Click to expand...
Click to collapse
Nope,Mokee can't take photos on E6853.And I think that aosp is not mokee so I'm afraid of destorying my phone and don't test that boot.img....

Has anybody tried this ROM on E6883 or E6833? Are there any functional problems found?

DarkSilentSC said:
Has anybody tried this ROM on E6883 or E6833? Are there any functional problems found?
Click to expand...
Click to collapse
It runs very good on E6883

Flashed the latest Mokee ROM (March 10th version). WOW does it work so well! Other than lack of fingerprint sensor (which I don't use), I've never seen such a stable AOSP ROM as this! Also it comes with working kernel and TWRP recovery! I've already placed SuperSU and Viper4Android and my phone is kicking real hard! Camera is basic but works beautifully, and it reads my 128GB MicroSD card as well.
Really impressed.
Since the new nightly came out, you might give it another try for E6853? It seems to accept single sim model as well, and hopefully that night build resolved not all but some issues?

DarkSilentSC said:
Flashed the latest Mokee ROM (March 10th version). WOW does it work so well! Other than lack of fingerprint sensor (which I don't use), I've never seen such a stable AOSP ROM as this! Also it comes with working kernel and TWRP recovery! I've already placed SuperSU and Viper4Android and my phone is kicking real hard! Camera is basic but works beautifully, and it reads my 128GB MicroSD card as well.
Really impressed.
Since the new nightly came out, you might give it another try for E6853? It seems to accept single sim model as well, and hopefully that night build resolved not all but some issues?
Click to expand...
Click to collapse
I've tried it and the camera can't take photos on E6853...Just want someone can fix this bug and publish a suitable rom for E6853

DarkSilentSC said:
Has anybody tried this ROM on E6883 or E6833? Are there any functional problems found?
Click to expand...
Click to collapse
I can't flash it on my E6833, says device is not compatible during the install , also errors about E: not mounted.

version I used is MK71.2-satsuki-201704211533-NIGHTLY Model : E6853
First link is the picture with the default app.
the other two are screenshots of the default app open
Video also works EDIT:2 (Bug using the Volume keys to Zoom freezes the picture while recording, the recorded video also has this frozen picture) zooming with finger is still ok and working.
https://photos.google.com/share/AF1...?key=T2oxU0EyQ2VmWUtEbDhULXJENU9iVlREdFJUMEV3
Over all this rom is solid. runs extremely fast in comparison to stock, Games load crazy fast, I don't even see the loading screen on one of them anymore.
Google apps are all working
Wifi and mobile data are working
fingerprint reader is working
all standard AOSP features look like they're working normally, I've not had any FCs or problems since last night when i flashed it.
it is missing some features or i'm not sure where to activate them, like the split screen feature of Android 7 .... maybe its not in the AOSP roms yet, or it was taken out as a useless feature.
But over all, very snappy rom. very stable, except for the aforementioned bug in the video recorder, this is my new daily driver i think. a bit more testing and observation but i think Mokee has a winner there.
................................................ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> .........................................................
Final Edit.
A few days later
stable. solid. quite simply one of the best open source roms ive used.
faster than stock in every way. has built in root, built in privacy controls, best battery management ive ever seen in a phone.
options for this i thought should have been standard in android already.
like reversing the volume keys in landscape mode.
per app. notification management
DPI setting
much much better app loading. still cant get over how fast my games load.
but ... there is always a but.
the camera after alot more testing, just ain't the same. its a fine camera app. and it works well. as solid as the rest of the rom. but the over all quality when compared​ to my older photos of things I took in the same light conditions, sony stock with post processing just kills it.
gonna go back to custom debloated stock once Xposed is updated for 7.
ill keep an eye on mokee roms though, except that camera. the rom is just amazing. once a top quality decent camera is made that works for this rom. it will easily be the best rom made for this phone.

Post 12 is positive, does anyone have any news about the full functioning of the Rom on the E6853?

Can any one post some screen shots!?

Why are we working on Oreo???

Why are we working on android Oreo? Should we try to perfect Nougat first. I see this so much with other devices, instead of having a few perfect roms you have a ton of half baked ones.

I'm running this device on Oreo and it works perfectly well for my needs. Its not my day to day tablet, but as a backup tablet, its there when I need it and does what I need it to. Why wouldn't they work on Oreo? There's no such thing as a perfect rom and nobody is ever going to make one due to limitations in hardware and open source drivers etc....
Personally, I'm happy that they have brought the latest incarnation of Android to this device and look forward to watching it improve with each new release.

lmulli said:
I'm running this device on Oreo and it works perfectly well for my needs. Its not my day to day tablet, but as a backup tablet, its there when I need it and does what I need it to. Why wouldn't they work on Oreo? There's no such thing as a perfect rom and nobody is ever going to make one due to limitations in hardware and open source drivers etc....
Personally, I'm happy that they have brought the latest incarnation of Android to this device and look forward to watching it improve with each new release.
Click to expand...
Click to collapse
>No such thing as a perfect rom
what are you talking about? Nougat on my RAZR M (just as old as the Nexus 10) runs flawlessly, and everything functions, so yes, there is such a thing as a perfect rom (or at least one with minimal bugs)
Most all roms have all functions on my ancient OG Nexus 7 (albeit a bit slow)
>Running oreo
HW video playback doesn't work, so no youtube app or netflix
Camera is still broken (some people need it for conference calls and hangouts chats)
--flash is broken too (you usually don't need it, but for those few situations you do, this is quite annoying)
Bluetooth wifi bug persists (turning on bluetooth and connecting a device makes wifi slow down and then disconnect)
My point is that we shouldn't just ditch/give up on fixing old bugs just to pursue a newer version of android. I'd rather run stable and fast Nougat than a half baked Oreo or Nougat build any day.
I know development is hard (my build set up errors out like no other) but that is just the reason we need to fix these things before wasting our time on something that will be harder to fix.

Galaxyninja66 said:
>No such thing as a perfect rom
what are you talking about? Nougat on my RAZR M (just as old as the Nexus 10) runs flawlessly, and everything functions, so yes, there is such a thing as a perfect rom (or at least one with minimal bugs)
Most all roms have all functions on my ancient OG Nexus 7 (albeit a bit slow)
>Running oreo
HW video playback doesn't work, so no youtube app or netflix
Camera is still broken (some people need it for conference calls and hangouts chats)
--flash is broken too (you usually don't need it, but for those few situations you do, this is quite annoying)
Bluetooth wifi bug persists (turning on bluetooth and connecting a device makes wifi slow down and then disconnect)
My point is that we shouldn't just ditch/give up on fixing old bugs just to pursue a newer version of android. I'd rather run stable and fast Nougat than a half baked Oreo or Nougat build any day.
I know development is hard (my build set up errors out like no other) but that is just the reason we need to fix these things before wasting our time on something that will be harder to fix.
Click to expand...
Click to collapse
If you know how to fix the issues on Nougat, nobody will stop you.
The Devs. which are still supporting the N10 said that they are not specialists for the open issues like camera, so they can't fix it. We should be happy that they try to make the best rom which they are capable and motivated for Nougat/Oreo etc.

tim-scrap said:
If you know how to fix the issues on Nougat, nobody will stop you.
The Devs. which are still supporting the N10 said that they are not specialists for the open issues like camera, so they can't fix it. We should be happy that they try to make the best rom which they are capable and motivated for Nougat/Oreo etc.
Click to expand...
Click to collapse
>making the best rom which they are capable
they aren't though, that's my point. They are slowly moving on to building oreo instead of trying to fix nougat which would both be easier and more beneficial to the community.
>If you know how to fix the issues on Nougat, nobody will stop you
I obviously don't (not that I'm not trying to), and part of my point is that the people who are the most competent (not competent, just the most competent, if you know what I mean) would get on the camera fix choo choo train, we could probably have a fix sooner rather than never.

Galaxyninja66 said:
>making the best rom which they are capable
they aren't though, that's my point. They are slowly moving on to building oreo instead of trying to fix nougat which would both be easier and more beneficial to the community.
>If you know how to fix the issues on Nougat, nobody will stop you
I obviously don't (not that I'm not trying to), and part of my point is that the people who are the most competent (not competent, just the most competent, if you know what I mean) would get on the camera fix choo choo train, we could probably have a fix sooner rather than never.
Click to expand...
Click to collapse
Got your point. Nevertheless if the developers are not willing or capable doesn't matter. It's their decision and they owe us nothing. If you read the different threads each dev. said why he didn't fix e.g. camera.

tim-scrap said:
Got your point. Nevertheless if the developers are not willing or capable doesn't matter. It's their decision and they owe us nothing. If you read the different threads each dev. said why he didn't fix e.g. camera.
Click to expand...
Click to collapse
link me, I have been looking for explanations on the camera for ages now. I didn't know if it was a problem with the Exynos framework for the camera or Nougat/Oreo themselves.

Galaxyninja66 said:
link me, I have been looking for explanations on the camera for ages now. I didn't know if it was a problem with the Exynos framework for the camera or Nougat/Oreo themselves.
Click to expand...
Click to collapse
Sorry my friend I will not read all posts of the last roms and why scanno, followmsi and the others are not fixing the open topics like camera, etc. That's your job. And if it is still not clear for you, you can ask the last active dev. (followmsi). he just pointed out today why he will not do so. Just read the posts around N10.

Galaxyninja66 said:
link me, I have been looking for explanations on the camera for ages now. I didn't know if it was a problem with the Exynos framework for the camera or Nougat/Oreo themselves.
Click to expand...
Click to collapse
Marshmallow is the last version of Android where everything works right on the Nexus 10. I don't have links but from everything I have seen/read, the devs can't do anything about the camera after Marshmallow. Google isn't giving the devs anything to work with anymore so stuff has to be ported or fixed by the devs alone. And I do beleive it has something to do with the hardware. But as it stands, Nougat is pretty flawless except for the camera. And Oreo is getting worked on to fix the HW Video Playback and other bugs which I'm sure they'll get fixed eventually. But most of the issues lie with the hardware. There's nothing much any dev can do about certain bugs. At this point, it's either live with the bugs or move on from the Nexus 10.

jsgraphicart said:
Marshmallow is the last version of Android where everything works right on the Nexus 10. I don't have links but from everything I have seen/read, the devs can't do anything about the camera after Marshmallow. Google isn't giving the devs anything to work with anymore so stuff has to be ported or fixed by the devs alone. And I do beleive it has something to do with the hardware. But as it stands, Nougat is pretty flawless except for the camera. And Oreo is getting worked on to fix the HW Video Playback and other bugs which I'm sure they'll get fixed eventually. But most of the issues lie with the hardware. There's nothing much any dev can do about certain bugs. At this point, it's either live with the bugs or move on from the Nexus 10.
Click to expand...
Click to collapse
I'll probably live with the bugs for a bit, I don't use the camera much, but when I do, its REALLY convenient. Marshmallow works great, and worst case I sell my N10 and grab a Nexus 9

Galaxyninja66 said:
I'll probably live with the bugs for a bit, I don't use the camera much, but when I do, its REALLY convenient. Marshmallow works great, and worst case I sell my N10 and grab a Nexus 9
Click to expand...
Click to collapse
Yeah, don't get a nexus 9. Oreo has the same problems (no h/w video decoding, no camera) on N9. I've pretty much given up on Android tablets (I own 4, Touchpad, N10, N9 and Amazon Fire w/ LineageOS), it looks like google has too.

funkybrunk said:
Yeah, don't get a nexus 9. Oreo has the same problems (no h/w video decoding, no camera) on N9. I've pretty much given up on Android tablets (I own 4, Touchpad, N10, N9 and Amazon Fire w/ LineageOS), it looks like google has too.
Click to expand...
Click to collapse
I can't, I love android tablets. They are a blast to use, and I use them much more often than my phone. To each their own, but frankly Google can suck it if they think people will stop using tablets.

The point is thet when android 8 wil works on nexus 10 all newer androids will work to thanks to project treble.
source.android.com/devices/architecture/treble

sagu55 said:
The point is thet when android 8 wil works on nexus 10 all newer androids will work to thanks to project treble.
source.android.com/devices/architecture/treble
Click to expand...
Click to collapse
iirc project treble was only for devices shipping with oreo out of the box, and was only a requirement, i.e. you must have a compatible AOSP factory image that is compatible with other treble devices (which doesn't count the N10 as it shipped with 4.2). I'll give that link a read but I as far as I currently know it doesn't support the N10

@Galaxyninja66 to fix the camera you need to port the old api1 camera to nougat/Oreo.
The api2 camera code was removed entirely from Android, that's why the camera stopped working.
The reason nobody is working on this is because it takes a lot of time to do that and none of the active devs even use the camera

tetsuo55 said:
@Galaxyninja66 to fix the camera you need to port the old api1 camera to nougat/Oreo.
The api2 camera code was removed entirely from Android, that's why the camera stopped working.
The reason nobody is working on this is because it takes a lot of time to do that and none of the active devs even use the camera
Click to expand...
Click to collapse
I also noticed while poking around in the camera HAL that a TON of values were just missing entirely. I would love a working camera but frankly it doesn't seem worth the work if it means either A: porting a deprecated API or B: rebuilding an entirely new one
*sigh* and the layer of dust on top of the Nexus 10 gets a little thicker.

Everyone else is doable tho

considering what an excellent tablet the Nexus was in its brief heyday, this is all very depressing! I really hate how valuable devices can be turned into landfill so gratuitously...