Related
So I thought id share some of the things i have learned about my Ouya that makes life a little easier:
1: Double Tap Ouya button = Home
2: To get an Xbox360 dongle to work with multiple controllers follow these steps:
2A - Power on Ouya WITHOUT xbox dongle attached
2B - Boot into Ouya and have the light lit on your Ouya Controller
2C - Plug Xbox360 controller dongle in and pair your xbox controllers.
2D - Activate within app (N64 emu it is in settings/input and then hit the on switch for each. Then go ahead and set it to the xbox360 controller profile and when you play the game hit multiplayer setup and follow the instructions. Each emulator is different.
3: To turn off your Ouya completely hold the power button on the Ouya until the standard Android popup appears and then use the controller to hit Yes
4: Root Explorer (Paid) can mount Dropbox as a partition within the app saving you the step of having to use the official Dropbox app which sucks.. BUT you can only open Root Explorer through Nova or another launcher. Fails through Ouya Launcher. You can also mount a SMB partition as well. Just makes sharing that much easier.
5: Never leave your Xbox dongle plugged in on boot. It screws with things. For instance I cannot start certain games because it is seeing my Ouya controller incorrectly and wont accept button inputs
Hope these tips help some people
6) Pressing 'Y' and then "powering off OUYA" doesnt really power it off. A large portion of the android framework is still running, including pretty much every service in init. Dalvik, zygote, adb, internet, etc are all still there, and still doing whatever they want to do. Apparently the only part of it that does power down is the video output.
7) Certain triggers make the ouya "power back on" (even though it never really powered off). One of these is getting a signal over HDMI cable. some TVs send this when you select an input, some of them send it when they power on.
8) OUYA has the option enabled to kill apps when they're no longer in focus. This is good since there's no "recent apps" button where you could normally kill running apps that you no longer wanted to be running. This is bad in that it makes some apps act wonky. For example, if you find a video in TVPortal and select it to watch, you will see the video in your video app like mxplayer. When you are done watching it and go back to TV portal, it will start all over from the beginning of the app.
gianptune said:
8) OUYA has the option enabled to kill apps when they're no longer in focus. This is good since there's no "recent apps" button where you could normally kill running apps that you no longer wanted to be running. This is bad in that it makes some apps act wonky. For example, if you find a video in TVPortal and select it to watch, you will see the video in your video app like mxplayer. When you are done watching it and go back to TV portal, it will start all over from the beginning of the app.
Click to expand...
Click to collapse
Nova's recent apps shortcut doesn't even work.
Sent from my SCH-I535 using Tapatalk 2
gianptune said:
8) OUYA has the option enabled to kill apps when they're no longer in focus. This is good since there's no "recent apps" button where you could normally kill running apps that you no longer wanted to be running. This is bad in that it makes some apps act wonky. For example, if you find a video in TVPortal and select it to watch, you will see the video in your video app like mxplayer. When you are done watching it and go back to TV portal, it will start all over from the beginning of the app.
Click to expand...
Click to collapse
You can change this in Developer options and deselecting the Dont Keep Activities option on the bottom. Netflix requires this in fact
altimax98 said:
You can change this in Developer options and deselecting the Dont Keep Activities option on the bottom. Netflix requires this in fact
Click to expand...
Click to collapse
Netflix requires you have that unchecked? I haven't run into any problems with it and I keep it checked.
The main reason it's checked is because if you let Android do it's thing like a phone, it'll take up too much RAM and slow down the bigger games, such as shadowrun. Leaving this checked is the best way to run it as a video game console.
The powering off by the Y button puts it to sleep much in the same way your phone goes to sleep when you hit the power button to turn off the screen. It puts it in a low power state mode and Wifi does go to sleep, but it does still stay connected at a very low level. For all purposes (since this is an android device) this should not affect the longevity of the product.
One thing to add is the difference between holding down the button on the OUYA until the shut down dialog pops up vs holding it down until the system goes off is that using the dialog makes sure everything is saved while holding it down is, essentially, like a battery pull. It shouldn't hurt the phone, but there's a small chance some data could be lost.
Hi,
How do you turn off the Nexus player? I can't find an option for it, I had to just switch off the power instead.
Any ideas?
Thanks.
kaznad said:
Hi,
How do you turn off the Nexus player? I can't find an option for it, I had to just switch off the power instead.
Any ideas?
Thanks.
Click to expand...
Click to collapse
There is no "off" on the Nexus Player, just like the Chromecast. It goes into a low powered standby mode after a few minutes, waiting for any Google Cast connections to wake it up and start playing (with HDMI-CEC enabled on TV or receiver, it'll automatically turn on, switch inputs, etc to start playing your cast immediately).
kaznad said:
Hi,
How do you turn off the Nexus player? I can't find an option for it, I had to just switch off the power instead.
Any ideas?
Thanks.
Click to expand...
Click to collapse
Like @Elrondolio already mentioned, there is no "Power Off" feature (which I HATE!!!). However, you could look for some kind of switch that you could attach to the power adapter cord so that you don't have to unplug every time that you want to turn the device off...something like this: http://www.adafruit.com/products/1125 (though, I have no idea whether or not that specific cord actually will work...I'm just presenting the concept). I've done this with my raspberry pi and it's awesome!
Another option would be to plug the player into an outlet that is controlled by a light switch (which would be much nicer than the cord IMO).
bsara said:
Like @Elrondolio already mentioned, there is no "Power Off" feature (which I HATE!!!).
Click to expand...
Click to collapse
I'm truly not trying to be confrontational here, simply curious: why do you hate that it's always on (in low power mode) so much?
To me, I see it no different than another phone or tablet in my home as it has nearly the exact same innards... all of my family's phones and tablets are on 24/7 as well, either on battery or charging on the mains. Having to boot up the box for a quick cast to show a quick video/trailer/etc to the family or start playing some music would be an inconvenience, I'd think, as having to wait for a receiver to boot its OS every time would be.
Again, simply curious as to your reasoning is all. Thanks!
Thanks everyone for your explanation.
I also have a Chromecast installed on my TV and I don't have any problem with it being always on WHEN my TV is turned on. However for the nexus player it will be truly always on unless you switch off the main.
I just got my nexus player yesterday so I dunno if it will be warm/hot if it's always on even when not in use. Anyway if it's not warm/hot if not in use then I've got no problem with it.
Thanks again everyone!
I've had my lean back launcher crash a few times, losing recommendations. It would be nice to have reboot
volwrath said:
I've had my lean back launcher crash a few times, losing recommendations. It would be nice to have reboot
Click to expand...
Click to collapse
agreed, a reboot option would be nice. a 3rd party app can achieve this with root. such as: power menu
Elrondolio said:
I'm truly not trying to be confrontational here, simply curious: why do you hate that it's always on (in low power mode) so much?
To me, I see it no different than another phone or tablet in my home as it has nearly the exact same innards... all of my family's phones and tablets are on 24/7 as well, either on battery or charging on the mains. Having to boot up the box for a quick cast to show a quick video/trailer/etc to the family or start playing some music would be an inconvenience, I'd think, as having to wait for a receiver to boot its OS every time would be.
Again, simply curious as to your reasoning is all. Thanks!
Click to expand...
Click to collapse
No worries about being confrontational, everybody has there own likes/dislikes...nothing wrong with that. Part of it is the made desire for efficiency that I have...why have something consuming power and bandwidth when it's not being used? Also, the amount of time that I and my family are using it is far less than the time that we aren't using it, if I was using it all day, I might not mind so much. Also, it's nice to do a reboot without unplugging the device, especially since I want to put it in a cabinet that is somewhat of a tight space. But, probably one of the biggest things that comes to my mind is connection to the internet on a 24/7 basis really bugs me. I know that my phone and my wife's phone is always connected...but it needs to be to notify me of things, my TV isn't notifying me of anything, I just want to use it when I want some good old couch potato entertainment, so why take up my bandwidth (I assume that it does some kind of check) and use any amount of power (which I do pay for, no matter how little the power usage is) when it isn't needed?
Personally, I believe that the following principle (highly advocated by Google) should have been followed: "Decide for me but let me have the final say" (http://developer.android.com/design/get-started/principles.html#decide-for-me). In other words, give the option to leave it on all the time for those that want it...but allow for powering off for those who don't. That way, everybody is happy.
I know this isn't an on-device fix, but if you're seriously concerned about your TV accessories only being on when the TV is on, there are many power strips out there that have a "master" outlet that toggles power to the rest of the outlets based on when the master device is on. So turning your TV on and off will switch power to the rest of your devices.
A reboot option would be nice. As for turning the NP off, I am using a TRIPP LITE TLP76MSG Eco Green Switched 7 Outlet Conserve Energy Surge Protector from Amazon.
Just an update, I found that when not in use the player is cool to the touch. As such I believe it goes into a low power/power saving mode. I have no issues with it being always on now. Way to go, google/asus. :good:
Confirmation of sleep mode
My nexus player's light is always on. Does anyone know if this means the unit is on or in sleep mode after the 30 minutes of inactivity? I have set it to 30 minutes and daydream does come on. Based on the manual, when the light is on the unit is on.
Thanks
https://support.google.com/androidtv/answer/6123074?hl=en&ref_topic=6121506
I think the light just means it has power, so it can be in sleep mode even when the light is on.
This was my main concern yesterday.
(I had since a week ago the Nexus Player but due my Internet provider's laziness, it was not until last night I could FINALLY setup my account and the device).
I noticed the DayDream options but I agree that the same OS needs an reboot option.
Mine doesn't switch back on when the TV is turned on again. Just a black screen and doesn't respond to pressing buttons on the remote.
wotandsdwys said:
Mine doesn't switch back on when the TV is turned on again. Just a black screen and doesn't respond to pressing buttons on the remote.
Click to expand...
Click to collapse
I recently brought a Nexus Player, I am having the same problem like you. Is this a problem with the software?
Understand that you can't power off the Nexus Player, but will it damage the internal components of the player (flash drive, etc) in the long run if you just simply cut off the power supply, which is apparently the only way to off the device?
Blank screen
xblues said:
I recently brought a Nexus Player, I am having the same problem like you. Is this a problem with the software?
Click to expand...
Click to collapse
Me too.. Screen is blank and will not come back to the launcher when a remote button is pressed. Does anyone know why? is it a hardware fault? Thanks in advance
shabba007 said:
Me too.. Screen is blank and will not come back to the launcher when a remote button is pressed. Does anyone know why? is it a hardware fault? Thanks in advance
Click to expand...
Click to collapse
I actually got it exchanged at the store. The problem disappeared with the new one (also using 5.1.1). So get a replacement!
kaznad said:
Hi,
How do you turn off the Nexus player? I can't find an option for it, I had to just switch off the power instead.
Any ideas?
Thanks.
Click to expand...
Click to collapse
yeah i can't find it too. i switch off instead power off
what about hdd version console - is anyone knows about sshd goes idle mode in some stage with full android on board installed or it's keep constant spinning like on native firmware even sleep mode?
And cec hdmi future works?
Sent from my Nokia 3310 using free xda app
So many comments and downloads about full android 2.2 and no one's can help with question. Gracias everyone.
Sent from my Nokia 3310 using free xda app
Not a user of the 2.2 full android.
Would have thought spin down would be controlled by the storage controller on the chip. I doubt Android has any built in mechanism to control this.
skymera said:
Not a user of the 2.2 full android.
Would have thought spin down would be controlled by the storage controller on the chip. I doubt Android has any built in mechanism to control this.
Click to expand...
Click to collapse
Ok! But why constant spinning on native firmware even sleep mode even can hear of spinning sound and small bit kind of vibrating?! Don't think this is main job controlled by controller (chip on hdd) there should be some OS or most likely and probably kernel command (deep sleep) when nothing goes through cpu. Take example: if you watching move from hdd - ok goes fine - when you press pause - last point has been stored in ram - and cpu stay idle and same time giving after certain time hdd goes in idle rest mode (something similar when you watching move from external hdd on pc - pressing play and move goes bit with kind of delay letting hdd fireing up first - sometimes you can even hear start point of spinning)
Maybe I'm wrong but this is my theory how should be
Sent from my Nokia 3310 using free xda app
Hello all,
I just wanted to let all who are interested know that the MyGica A681 USB stick works 100%. I have it hooked up to one of those flat window mount antennas and it receives full HD signal that I view through the PadTV app found on Play Store. The PadTV app lacks in a lot of ways, it would be cool if someone around here was able to come up with something better. A few of the channels have a major A/V delay but it may be due to reception and not the tuner stick or app. Overall, it was a very worthwhile purchase for me, if anyone has any questions let me know.
Hopefully this is useful information for a cord-cutter somewhere. I'm not in any way affiliated with MyGica, just a fellow MOJO owner who couldn't find any info on a TV Tuner stick that would work with our boxes so I took the dive on my own.
Thanks buddy, this is a great discovery!
AndroidSupaFan said:
Thanks buddy, this is a great discovery!
Click to expand...
Click to collapse
No problem. I've pretty much been doing a lot of my own discovering what works since there's not much documentation for our devices. Like I said in my first post, it would be awesome if someone around here was able to come up with something better for a channel surfing app. PadTV gets the job done, but it's certainly not the prettiest. I forgot to mention that it also does DVR, but one of my issues is that it will only save to internal storage and not something like an external drive or an SD card. The channel info/current episode descriptions are several hours behind. If theres a button on my remote for Channel +/-, I haven't found it. You have to use your mouse to bring up and scroll through channels. Again, it gets the job done, I can watch 39 or so OTA channels, and quite a few of which are HD. It's just not the most MOJO friendly UI, since it was intended for phones.
Some other things I use daily that work 100%: Ouya controller (as 2nd controller), Plugables brand 7x USB 3.0 hub, & a Rii Mini i8 keyboard. Obviously stuff like my Logitech Bluetooth receiver that I run to my stereo also works to receive audio from MOJO. My USB wired Logitech PC game controller works great as well.
Just trying to help fellow XDA'ers and Googlers not worry about compatibility before they order something like I did. That said, most if not all of my worries were completely unfounded because everything I've thrown at the MOJO so far works like a charm!
Would a wired XBox 360 controller work?
psxfa said:
Would a wired XBox 360 controller work?
Click to expand...
Click to collapse
I don't have one to test but I'm 99% sure it would.
I'd just like to clarify a point: it may sound like nitpicking, but it's not the PadTV app that works; it's the PadTV-HD app. The standard PadTV just says it can't find a device.
That being said, the little MyGica is a little giant. I live in a fringe reception area, for decent reception I need a huge rooftop antenna, but this little thumb-drive-sized receiver still picks up a round dozen stations on the 10-cm piece of coat hanger wire it comes with. Yes, the weaker stations have audio lag problems; I hope a better antenna fixes that. It also costs about half what other similar units do, and most of them work on windows only.
I tried a few of the other TV apps on Play Store but the PadTV-HD was the only one that recognized the A681. I didn't find it all that bad an interface, except that the sidebars won't stay in place longer than a couple seconds, and I couldn't find a setting for that. It also lacks a volume control, as the MOJO itself does, so you must hope you have some control somewhere else. And there is no info in the EPG (electronic program guide) even though it appears to have that function. But I was able to find and watch several different channels without any real problems; except, of course, that TV programming in general sucks. Unless you're a sports fan.
So thanks, @tideee88, for the heads-up here!
kevinthefixer said:
I'd just like to clarify a point: it may sound like nitpicking, but it's not the PadTV app that works; it's the PadTV-HD app. The standard PadTV just says it can't find a device.
That being said, the little MyGica is a little giant. I live in a fringe reception area, for decent reception I need a huge rooftop antenna, but this little thumb-drive-sized receiver still picks up a round dozen stations on the 10-cm piece of coat hanger wire it comes with. Yes, the weaker stations have audio lag problems; I hope a better antenna fixes that. It also costs about half what other similar units do, and most of them work on windows only.
I tried a few of the other TV apps on Play Store but the PadTV-HD was the only one that recognized the A681. I didn't find it all that bad an interface, except that the sidebars won't stay in place longer than a couple seconds, and I couldn't find a setting for that. It also lacks a volume control, as the MOJO itself does, so you must hope you have some control somewhere else. And there is no info in the EPG (electronic program guide) even though it appears to have that function. But I was able to find and watch several different channels without any real problems; except, of course, that TV programming in general sucks. Unless you're a sports fan.
So thanks, @tideee88, for the heads-up here!
Click to expand...
Click to collapse
Yes, thank you for mentioning that it is in fact the PadTV HD app. Hope I didn't cause anyone any confusion. I also had no luck trying other tuner apps and I tried literally every one available on Play Store (including non-ATSC ones) and even tried sideloading a few because I dislike PadTV HD so much.
I agree that the MyGica stick is a great little device. I'm really impressed with it when it's able to do it's thing properly. I never tried the dinky little antenna it came with, I ordered a 25-mile distance flat window-mount antenna and it gets me about 39 channels here in Pittsburgh, PA. Lots of them are HD, and look and sound great. However, many of the Play Store reviews for PadTV HD seem to indicate that the slow motion, lag, and stuttering are a result of the app not taking advantage of hardware acceleration and thus is trying to encode 1080p on the fly via software rendering or something to that effect. Other than the mild inconveniences of things like not having a dedicated button for CH +/- and as you noted, the channel info being totally useless, it's a real bummer that I can't even get the channels I could be getting if it weren't for a poorly written app that is unfortunately our only option at the moment. I feel as though this is a real hole that could be filled with the rate at which Android set top boxes are becoming popular.
I mostly purchased this because the only time I ever need to watch broadcast TV is when my Steelers are on and hence have no use to pay for cable. I'm really hoping we have a new app sorted out before football season because FOX is one of the channels that currently comes in very laggy and out of sync for me at the moment.
Your MOJO doesn't have volume control, though? It certainly should. Do the hardkeys not work on your C.T.R.L.R.? Android system volume works perfect for me in all apps. Failing that, I've found you can change the volume in Pad TV HD by clicking somewhere in the video frame and dragging your mouse up or down, like a swipe if it were touch. Hopefully that helps!
tideee88 said:
Yes, thank you for mentioning that it is in fact the PadTV HD app. Hope I didn't cause anyone any confusion. I also had no luck trying other tuner apps and I tried literally every one available on Play Store (including non-ATSC ones) and even tried sideloading a few because I dislike PadTV HD so much.
I agree that the MyGica stick is a great little device. I'm really impressed with it when it's able to do it's thing properly. I never tried the dinky little antenna it came with, I ordered a 25-mile distance flat window-mount antenna and it gets me about 39 channels here in Pittsburgh, PA. Lots of them are HD, and look and sound great. However, many of the Play Store reviews for PadTV HD seem to indicate that the slow motion, lag, and stuttering are a result of the app not taking advantage of hardware acceleration and thus is trying to encode 1080p on the fly via software rendering or something to that effect. Other than the mild inconveniences of things like not having a dedicated button for CH +/- and as you noted, the channel info being totally useless, it's a real bummer that I can't even get the channels I could be getting if it weren't for a poorly written app that is unfortunately our only option at the moment. I feel as though this is a real hole that could be filled with the rate at which Android set top boxes are becoming popular.
I mostly purchased this because the only time I ever need to watch broadcast TV is when my Steelers are on and hence have no use to pay for cable. I'm really hoping we have a new app sorted out before football season because FOX is one of the channels that currently comes in very laggy and out of sync for me at the moment.
Your MOJO doesn't have volume control, though? It certainly should. Do the hardkeys not work on your C.T.R.L.R.? Android system volume works perfect for me in all apps. Failing that, I've found you can change the volume in Pad TV HD by clicking somewhere in the video frame and dragging your mouse up or down, like a swipe if it were touch. Hopefully that helps!
Click to expand...
Click to collapse
I'll try the volume control thing. I'm using CM12.1 and maybe it has a volume control somewhere but I haven't found it yet, I'm used to hardware switches. I'm not using the CTRLR either, just a keyboard & mouse. I'm still working on display resolution problems, as I don't really have the right display hardware for the MOJO, and it's picky that way. I'm about to give up entirely on the powered HDMI-2-VGA adapter to the 1280x1024 computer monitor, too unreliable even just in Android. Neither it nor the HDMI-2-DVI cable to the old Dell monitor will display at all in recovery, for that I have to commandeer the living room and the only true HDMI display in the house, which is a projector--not the best setup for tweaking a device. Still doing my homework on tweaking TWRP to 720P which I hope will solve that problem.
kevinthefixer said:
I'll try the volume control thing. I'm using CM12.1 and maybe it has a volume control somewhere but I haven't found it yet, I'm used to hardware switches. I'm not using the CTRLR either, just a keyboard & mouse. I'm still working on display resolution problems, as I don't really have the right display hardware for the MOJO, and it's picky that way. I'm about to give up entirely on the powered HDMI-2-VGA adapter to the 1280x1024 computer monitor, too unreliable even just in Android. Neither it nor the HDMI-2-DVI cable to the old Dell monitor will display at all in recovery, for that I have to commandeer the living room and the only true HDMI display in the house, which is a projector--not the best setup for tweaking a device. Still doing my homework on tweaking TWRP to 720P which I hope will solve that problem.
Click to expand...
Click to collapse
I'm running a rooted stock rom via HDMI so I'm not sure about your display issues as I haven't had any. But I use a bluetooth keyboard/mouse most of the time and the volume hardkeys work on that as well. If your keyboard has volume hardkeys and they don't work, it may be some sort of issue with your rom. AFAIK, my keyboard's drivers are just generic Windows ones.
tideee88 said:
I'm running a rooted stock rom via HDMI so I'm not sure about your display issues as I haven't had any. But I use a bluetooth keyboard/mouse most of the time and the volume hardkeys work on that as well. If your keyboard has volume hardkeys and they don't work, it may be some sort of issue with your rom. AFAIK, my keyboard's drivers are just generic Windows ones.
Click to expand...
Click to collapse
Same display issues regardless of ROM. AFAIK there are only four, and I tried them all. (This is a very rare instance of me following my own advice: try all the different flavors before deciding on a favorite.) Several people have reported similar issues while in system but I think I'm unique in the recovery problem. Changing the resolution by editing the build.prop improved my display in system but did nothing in recovery; I will just have to carry the MOJO into the living room whenever I need to use recovery, which shouldn't be that often. The bright side is that I learned to unpack and repack recovery images.
My keyboard is a wired mini with no extra room for media keys, but it does have a third control key (FN) to emulate them. But I can't see the blue-on-black icons to use them unless the room is brightly lit! Volume control is not a biggie for me though, I run the audio through a seventies-vintage amp and speakers. I pity those who grew up with "modern" surround sound, satellite speakers and a single subwoofer. My setups often fool both myself and the dogs, we can't tell if the noise is outside the open door or inside the TV.
BTW Windows keyboard drivers won't work on Android, but it's such a low-level thing they are just included in the kernel. Somewhere in the ROM is a keyboard map that can be edited (with root of course), but I misremember where. I never had to remap a keyboard.
PadTV HD app no longer works for me as of the latest update. For anyone considering purchasing a tuner, I recommend against it. Flushed $40 down the toilet.
If you'd like I'll send you the old version, I'll just need to save it then upload it. You'd just have to uninstall the newer version then sideload the old one and not allow it to update. Just PM me.
kevinthefixer said:
If you'd like I'll send you the old version, I'll just need to save it then upload it. You'd just have to uninstall the newer version then sideload the old one and not allow it to update. Just PM me.
Click to expand...
Click to collapse
Can you please send me the version that works?
first and foremost, special thanks to alecbl for his initial device tree and kernel source. this build would not be possible without his kernel work.
This is LineageOS 13.0 for the Alcatel Idol 3 4.7" variants
as always, full device, vendor, and kernel trees available at github:
https://github.com/stayboogy/stayboogy_lineage13_idol347
all changes in detail: https://github.com/stayboogy/stayboogy_lineage13_idol347/commits/master
This build is not the same as alecbl's, mine has some various changes to make it a more proper build for this specific device.
Updates will be coming as time progresses and new features are added.
FEATURES:
tap2wake & tap2sleep
double press power button opens camera
triple press power gives brightness boost
call recording available
lineage.yahoo.weather provider now installed by default
notepad included by default
typical apps and functionality of CM / Lineage roms
SPECIAL NOTES
1) wrist/tilt sensor (accelerometer) is used for the missing motion sensor for doze settings
2) speech to text / voice typing requires the Google app and for microphone permissions to be activated in settings/apps/Google/permissions then it will work correctly
3) smart lock settings work and persist over reboots--you must have the play store updated, play store services updated, the Google app installed, and Maps installed for all settings to work in smart lock settings.
4) flip cover has not been activated in the device tree yet--if people want it, post and if enough want it i'll add it back
5) battery light pulse option is no longer available, battery light itself when plugged in is active; notification light pulses by default, it's speed can no longer be edited because it doesn't work correctly--this was an executive decision because i don't like options that don't work correctly, these will not be added back, versions 1.1 and higher are incompatible with 1.0 framework so don't try to replace.
6) selinux is enforcing
RELEASE 1.1
click here
RELEASE 1.0
click here
Hi stayboogy - looking forward to trying this out
Great to see a new dev picking up this device, looking forward to test your work!
sorry last build had an error, new link will be up later tonight
link is live now.
post anything i might have missed. so far i think it is fairly polished
@stayboogy - I'm Testing it now - No root access for apps ? only adb option.
k500zm said:
@stayboogy - I'm Testing it now - No root access for apps ? only adb option.
Click to expand...
Click to collapse
not missing, that's how modern security works and should be.
install superuser from recovery, that's standard mode of operation for everything after kk.
@stayboogy , Will you build lineage os 14.1??
A few issues I found on my day using this rom, I will provide logs on monday if you need, I'm out for the weekend and don't have a pc right now.
-Sometimes the power button instead of locking the device it boosts the screen brightness to max for a few seconds.
-I still find the smartlock issue with bluetooth devices, I do have google app and maps installed
-WiFi speed seems lower than on other devices connected to the same network, but since I'm not on my own house it might be a network issue, will confirm this when I get back home.
Phantom410 said:
A few issues I found on my day using this rom, I will provide logs on monday if you need, I'm out for the weekend and don't have a pc right now.
-Sometimes the power button instead of locking the device it boosts the screen brightness to max for a few seconds.
-I still find the smartlock issue with bluetooth devices, I do have google app and maps installed
-WiFi speed seems lower than on other devices connected to the same network, but since I'm not on my own house it might be a network issue, will confirm this when I get back home.
Click to expand...
Click to collapse
1) you're double pressing the power button then, and you have the "double tap power to open camera" option off in settings/buttons/
--either stop double pressing the power button which is what boosts brightness
--or turn on double press for camera option to turn off brightness boost
--or stop double pressing your power button
--pressing once will NEVER EVER produce brightness boost--i've been using the rom since before it was released so i'm sure of this
--your power button may be worn and more susceptible to register a double press when it wasn't
2) smart lock works for me in every option--make sure you're not using some crappy third-party lockscreen app or lockscreen security app that could be interfering with this.
--also there is a slight bug where bluetooth devices that are paired are not remembered upon a power cycle--i'm working on this as i type
3) this must be where you are--i have no issues whatsoever regarding wifi or networks period. of course i have 1GB/min speeds on bad days, and 2GB/min speeds on good days so idk
Thanks for Sharing, and this is the correct way for people to voice their finds and opinions, so thank you for that
alecbl said:
It does not have it by default but retains the option to enable it. I have enabled it. The day cyanogen/lineage starts needing to be rooted is the day I start building some other rom.
Click to expand...
Click to collapse
A message from alecbl from his build....
k500zm said:
A message from alecbl from his build....
Click to expand...
Click to collapse
you're arguing about nothing--engineering builds (ie. lineage_idol347-eng) are the only build that will have su enabled for apps and adb by default
userdebug builds and user builds do not have this enabled by default--only adb root access is made available standard by the system in developer settings.
again, the freaking su is NOT MISSING. I chose to leave the system as it is, because that's how it's supposed to be, and your problems are just stupid childish whining because you don't how current android works.
if you want root, use superuser from recovery which again is standard operating procedure for everything after KitKat. why you can't get this through your thick ****ing skull is beyond me. you obviously are not a developer and have no business making any claims as to what is standard or what is the right way for a rom to work when you aren't building any and have no experience or even basic knowledge of how the build system works or the hundreds of security revisions that have been introduced since kk that make non-systemless rooting a vulnerability...
stayboogy said:
1) you're double pressing the power button then, and you have the "double tap power to open camera" option off in settings/buttons/
--either stop double pressing the power button which is what boosts brightness
--or turn on double press for camera option to turn off brightness boost
--or stop double pressing your power button
--pressing once will NEVER EVER produce brightness boost--i've been using the rom since before it was released so i'm sure of this
--your power button may be worn and more susceptible to register a double press when it wasn't
Click to expand...
Click to collapse
Yeah, it's most likely my button being worn out, because I had disabled the double press to open camera since it was randomly opening when I pressed the button, I just didn't know double press for brightness was a feature (it's a useful one actually)
2) smart lock works for me in every option--make sure you're not using some crappy third-party lockscreen app or lockscreen security app that could be interfering with this.
--also there is a slight bug where bluetooth devices that are paired are not remembered upon a power cycle--i'm working on this as i type
Click to expand...
Click to collapse
After every power cycle I get the notification to pair it and confirm that the codes match and on the bluetooth device itself I get a new 6039A device on the paired devices list after it happens, so it might be that issue you mentioned. (I attached a pic of how the devices list looks on the bluetooth device)
Thanks for Sharing, and this is the correct way for people to voice their finds and opinions, so thank you for that
Click to expand...
Click to collapse
Well, I know and appreciate the free time from your daily life you take to develop and share your work. Hopefully certain type of entitled idiots who think they deserve everything their way and for free don't discourage you to keep up with your amazing work!
Versions 1.1 release
download link the OP
hopefully bluetooth paired devices retention is working now
stayboogy said:
Versions 1.1 release
download link the OP
hopefully bluetooth paired devices retention is working now
Click to expand...
Click to collapse
Is now camera included?
I think there is some confusion among users a camera is included just not the stock one
stayboogy said:
I think there is some confusion among users a camera is included just not the stock one
Click to expand...
Click to collapse
I was talking about stock camera, sorry for the omission
USB bug
After installing I cant transfer files from my device to pc.
In developer options you cant change the USB option from just charge to MTP, PTP or any other it stays in just charge
UPDATE: At the USB Configuration select MTP and keep touching the option to change it
NOTE: Enable Developer options before connecting the device for the first time to the pc
BlackDantex said:
After installing I cant transfer files from my device to pc.
In developer options you cant change the USB option from just charge to MTP, PTP or any other it stays in just charge
UPDATE: At the USB Configuration select MTP and keep touching the option to change it
NOTE: Enable Developer options before connecting the device for the first time to the pc
Click to expand...
Click to collapse
yes, i'm aware you can't change in developer options while it is not attached to pc,
and it bugs out sometimes when it's attached to pc
--this is a problem in the lineage source, not the device tree and therefore out of my control
--use the notification in the status bar to choose how you want the device to connect PTP, MTP, Charge only--this works perfectly and as expected
Somewhere along the way, CM/Lineage has messed with the Bluetooth stack in the source code, and there seems to be possibly some missing component service that needs to be running in order for fine location access to be given to bluetooth in order for it to work correctly, and this is also related to smart lock.
at this time, upon every reboot of your device, you will have to re-pair any bluetooth device you have used previously. auto-connect is broken in the bluetooth service stack somehow. also, your device is created anew each time it is rebooted due to a security measure enacted by google a while back that randomizes your bluetooth mac address so that your device location can't be sniffed by third-party apps. there's a whole long bulletin about it somewhere, but i guarantee this is why bluetooth auto-reconnect is broken after a power cycle.
i have discontinued all use of lineage 13 personally because of this reason alone.
i'll still be work on this rom though.
just don't expect a fix for bluetooth from me because it will have to come from upstream aosp and then made known to everyone.