First things first: Hey everyone. Some of you may know me from other devices or because of some Moderator related business. Anyways, I recently thought I needed a tablet upgrade and so decided to order a shield tablet. I have been going through some threads, and was actually kinda surprised that this nice piece of technology doesn't have more development going on, especially regarding kernels.
After a few days of getting to know the tablet I noticed one very useful feature missing: sweep2wake, or at least doubletap2wake.
Unfortunately, though, Nvidia did not yet release the kernel sources for their marshmallow kernel, so I can't add it myself that easily. Which is why I had to make a detour adding s2w to the kernel using a module. This, however, has the downside that I cannot prevent the touchscreen driver from suspending, nor get the information whether the screen is turned on or off. Therefore I need a dedicated background service to retrieve exactly this information and reenable the touchscreen driver.
Requirements
Android Marshmallow
Root
Both the kernel module and my app
Installation
Download the latest kernel module and app
Install the app
Push the kernel module to your internal storage (/sdcard/sweep2wake.ko)
Usage
Open the app and press "insmod"
--> this will load the module but also set selinux to permissive
--> S2W is now up and running, but can only be used to turn the screen off
Press "start" to start the background service
--> This will reenable the touchscreen driver when the screen got turned off and also tell S2W that the screen is turned off
--> S2w will now work perfectly fine as long as the tablet is plugged in or another app holds a wakelock. If this is not the case and the tablet is in deep sleep, you will not be able to wake the device and touch input might not work after turning the screen on manually. If this is the case, just turn the screen off and back on and it will work as usual again.
--> In order to wake the device at all times, start the service with the "enforcing" switch turned on. This will make the service hold a wakelock while the screen is off. However, your battery will drain rather rapidly as the tablet cannot go into deep sleep
To stop the service again, simply press "stop"
Keeping in mind that this is still in a rather early stage, I did not add a "enable on boot" option for the service.
I really hope that Nvidia releases the M sources soon, so I can add S2W and DT2W to the kernel properly.
This module should be compatible with all (current) Marshmallow firmwares, on both the old and new shield.
XDA:DevDB Information
Sweep2Wake Module, Kernel for the Nvidia Shield Tablet
Contributors
laufersteppenwolf
Source Code: https://github.com/laufersteppenwolf/android_kernel_nvidia_shieldtablet_modules
Kernel Special Features: Sweep2Wake
Version Information
Status: Beta
Created 2016-01-16
Last Updated 2016-01-22
They've got a new repository up, which is not yet listed on their web page. Haven't checked, but these should be the marshmellow sources.
repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r7-partner -m tlk/shieldtablet.xml
repo sync -j5
njhuiz said:
They've got a new repository up, which is not yet listed on their web page. Haven't checked, but these should be the marshmellow sources.
repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r7-partner -m tlk/shieldtablet.xml
repo sync -j5
Click to expand...
Click to collapse
Nope, it's not the MM kernel. these sources are actually what my module is based on
laufersteppenwolf said:
Nope, it's not the MM kernel. these sources are actually what my module is based on
Click to expand...
Click to collapse
First of all, thnx for your work and bring this expected feature.
About sources, we are using rel-24-sb-r1-partner branch from Nvidia for CM-13.0 and Bliss6. This seems to be latest code for latest K1 MM OTA. Have you explored it ?
Very nice, thanks for starting work on the tablet. I've got requests for adding this to my CM builds, but I don't have the kernel experience to add it myself. Once I've gotten both roth and shieldtablet stable on cm-13.0 and pushed to official, I will want to look into pulling this in for both. It should port to the M kernel pretty directly. Maybe a difference in the mach-tegra file, but that should be it. The touch failing to re-enable sounds very familiar... Custom ROMs had the issue for a while, caused by blobbing the powerhal. It was mitigated for a while, but after we started compiling the powerhal, we haven't seen it since. I'd be interested to know if this was compiled into the kernel (not as a module) for a custom ROM if the problem still occurs.
Did you upload the code for the apk somewhere? I'm kinda curious how you are triggering touch enable/disable. By writing to the sysfs file like the powerhal does?
Are there any other obvious features missing in the kernel? The one that bugs me a bit is volume/button controls on headphones. Seems that needs kernel support and Nvidia didn't write that in.
BitOBSessiOn said:
First of all, thnx for your work and bring this expected feature.
About sources, we are using rel-24-sb-r1-partner branch from Nvidia for CM-13.0 and Bliss6. This seems to be latest code for latest K1 MM OTA. Have you explored it ?
Click to expand...
Click to collapse
No, I did not. I will look into it, though, as I definitely need a better kernel than the stock one I am running ATM
If you need a hand some time, feel free to drop me a PM and I will see what I can do
Steel01 said:
Very nice, thanks for starting work on the tablet. I've got requests for adding this to my CM builds, but I don't have the kernel experience to add it myself. Once I've gotten both roth and shieldtablet stable on cm-13.0 and pushed to official, I will want to look into pulling this in for both. It should port to the M kernel pretty directly. Maybe a difference in the mach-tegra file, but that should be it. The touch failing to re-enable sounds very familiar... Custom ROMs had the issue for a while, caused by blobbing the powerhal. It was mitigated for a while, but after we started compiling the powerhal, we haven't seen it since. I'd be interested to know if this was compiled into the kernel (not as a module) for a custom ROM if the problem still occurs.
Did you upload the code for the apk somewhere? I'm kinda curious how you are triggering touch enable/disable. By writing to the sysfs file like the powerhal does?
Are there any other obvious features missing in the kernel? The one that bugs me a bit is volume/button controls on headphones. Seems that needs kernel support and Nvidia didn't write that in.
Click to expand...
Click to collapse
First off, no, you cannot just cherry-pick this patch into another kernel. This is made to be working as a kernel module only. It'll most likely cause the kernel not to boot anymore when cherry-picked.
It should be rather easy to implement this directly into a kernel, though.
No, I did not upload the app's sources yet, I can, though, if you want me to. And yes, I do enable the ts driver by writing to the sysfs node.
Well, TBH, there's a lot that can be done to the kernel, it just depends on what one thinks is really necessary
Volume control is not kernel related, though. The kernel only passes the information "vol up pressed" on to the Android system, everything else is handled by Android's framework.
laufersteppenwolf said:
First off, no, you cannot just cherry-pick this patch into another kernel. This is made to be working as a kernel module only. It'll most likely cause the kernel not to boot anymore when cherry-picked.
It should be rather easy to implement this directly into a kernel, though.
Click to expand...
Click to collapse
I just glanced through the commit, but nothing stood out to me as working only for 'm' vs. 'y'. What in particular would cause a problem?
laufersteppenwolf said:
Well, TBH, there's a lot that can be done to the kernel, it just depends on what one thinks is really necessary
Volume control is not kernel related, though. The kernel only passes the information "vol up pressed" on to the Android system, everything else is handled by Android's framework.
Click to expand...
Click to collapse
I looked into the volume control thing a little while back. The code to detect the inaudible tone used by the headset buttons wasn't implemented in the stock kernel at that time. I haven't looked at the M kernel yet, but I expect it's the same.
I'm not one for extravagant features in a kernel, especially for the official CM devices I maintain. But when there are features missing that people expect as standard these days, I'll make an exception. D2W is one (not that I'd use it personally, but enough people expect it), and headset volume is another.
Steel01 said:
I just glanced through the commit, but nothing stood out to me as working only for 'm' vs. 'y'. What in particular would cause a problem?
I looked into the volume control thing a little while back. The code to detect the inaudible tone used by the headset buttons wasn't implemented in the stock kernel at that time. I haven't looked at the M kernel yet, but I expect it's the same.
I'm not one for extravagant features in a kernel, especially for the official CM devices I maintain. But when there are features missing that people expect as standard these days, I'll make an exception. D2W is one (not that I'd use it personally, but enough people expect it), and headset volume is another.
Click to expand...
Click to collapse
well, the general implementation including the modification of some other files (makefile, scripts,..)
But good news is I got the 3.10.67 kernel booting, which means it's time for yet another werewolf kernel S2W and DT2W is already implemented, but not yet properly working. Needs some more work.
My bad, I thought you were referring to the device's volume buttons and the "keep pressed for skip" feature
Haven't looked into that either TBH.
Hey man! Thanks for this feature! I used your kernel on LG Optimus 4X HD hope you can give us more rom development. Best of luck!
Enviado do meu wx_na_wf através de Tapatalk
Related
Alright so Yesterday I installed the android os on my touch pro (raph 500)
i orginally have windows mobile 6.5 which is preety fast
but android is really slow!
i turned off all the settings which i would think it used alot of memory but still no help, so i started seeing videos on overclcking?
can someone explain to me on how to do this,
with links to the download
i really need to speed this up ,it would be amazing if it worked.
also if you give me a response that helps me , ill donate 10.00+ to you .
I do not require funds as I enjoy helping out!
From THIS thread and THIS post:
Overclocking
acpuclock.oc_freq_khz=XXXXXX ( suggested 600000-640000 )
but it is very unstable if you try to get higher than 650000-700000
Click to expand...
Click to collapse
Basically, you add that to the startup.txt file somewhere between the parentheses with an added space between the next command. Keeping in mind, with added OC, you may and may not notice a difference in stability. I honestly never use OC and I am using FroYo from THIS thread. Additionally you can try out Gingerbread Alpha from THIS thread. Please leave feedback in their respective threads, thanks!
n-Joie! (Enjoy)
thanks but this is my startup text :
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 acpuclock.force_turbo=1"
boot
Click to expand...
Click to collapse
so which am i supposed to edit, sorry im a noob lol
& u said that was the one you used,
is it fast?
Actually, I can't use that one because I have an at&t Fuze. If you have a RAPH500, you might want to use the following:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 pm.sleep_mode=1 acpuclock.oc_freq_khz=XXXXXX"
boot
Click to expand...
Click to collapse
Where XXXXXX is equal to a value between 600000-640000
Additional note: make sure you type something like 600000 or any value up to 640000
lol thanks im trying to see if theres a difference in speed.
but you used froyo?
is that running fast?
It's running fine with sync and a few other apps running in the background. I would be mindful of livewallpaper and HQ video at the moment as this project is currently still under development, at best. At least that is what I have noticed as far as performance is considered. I have also run a stripped Gingerbread alpha build (the one I linked you to earlier) and it is running faster/smoother than FroYo. To be expected without all the bells and whistles...
NOTE: Speed is relative to performance at the moment. Hence why I say it's still under development...
intresting ill test that out in about 15 mins
but does yours take a long time to come out of sleep mode?
Hmmm, that might be the notorious sleep of death SOD. I usually do something that most don't like but I sort of turn off the screen time out by first making the screen time out greater than 10 or 30 minutes. After that it should make things easier as far as disabling the auto back light/screen timeout feature. Keep in mind this is only a work around, I believe there is mention of actually fixing this issue. You'll need to download a free app called batterybooster (use the link if you want to read up on it a little). Once installed, run it and look for the far right icon and tap it. Set the timeout to Never and you'll notice a decent performance enhancement in the screen off and screen on.
NOTE: You will need to manually turn it off from here-on. You can try to play around with the setting but I find it somewhat problematic. Meaning that if you enable the timeout, it might and it might not work.
alright well i tried the gingerbread and that didnt work it lagged .
i tried froyo , it was amazing then i found out wifi didnt work
so now im back to the regular android one i had before ill be trying to see if theres a difference now that i "overclocked" it .
but thanks for all the help.
ill post back if i need something!
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
R^7Z said:
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
Click to expand...
Click to collapse
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
ndnmaster096 said:
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
Click to expand...
Click to collapse
NVM I got the wifi to work now .
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
R^7Z said:
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
Click to expand...
Click to collapse
well i set it to never timeout and i have a lock pattern
but since it never times out it wont lock .
also now im starting to notice froyo is rebooting for some weird reason automatically .
Calm down, that is kind of "usual behavior" . There are quire a few things going on and the OS is attempting to "handle it". Sometimes it can't and just quits instead of freezing up ( which would be the lesser of two evils ). To get it to lock, you will have to turn it off manually (power button). Unfortunately, I think if the keyboad slides out, it self unlocks (kind of a self defeating purpose, more or less). If you turn the screen off and wait like 10 seconds then turn the screen on (power key), you should see the lock. I can't say for sure but it does work for me. I don't really have much time for troubleshooting today, as I am at work currently but do look over the threads I linked you to earlier if at all possible.
okay so i turned it off using the power button and it booted to windows mobile (odd)
then i tried running haret.exe & got this message:
"The file HARET cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. IF the problem persists, try reinstalling or restoring the file."
im not sure what to do.
i tryed reformatting the card and installing fresh files, which didnt work so now im left questioned?
When you say you turned it off, did you hold the button or just press it once? If you pressed it once, then, that is definitly not "usual" behavior. I recall having that issue once upon a time but for the life of me, I don't recall what I did to recover from it. However, it sounds like you are attempting to run from a shortcut that references the program(haret) that is no longer there. To resolve this, I need you to confirm that you are running from the microSD and not a shortcut. Also, you aren't formatting under windows, right? If you are formatting from windows, that would be a "no-no"
Find something like the HP tool (can be googled) that everyone else talks of or even something like the free version of partition wizard should work.
i held the button and it gave me options
1) airplane mode
2)shutoff
3)vibrate
i did try to make a shortcut but i deleted it and now when i checked i was running it from the actual application.
lastly, i did format from windows but i downloaded hp format tool
and formated my device in quick format.
reinstalled the programs and it still gave me the same error message,
please help, i really miss android =(
Try deleting data.img and letting it recreate the file. To clarify about the screen off issue, when you press the power button once (not hold), what does it do? Also, which kernel package are you using and have you attempted to download a newer kernel package yet?
Also, try THIS kernel package; I got it from THIS site. It looks like that kernel package is specific to our devices.
we all owe a hell of a thanks to Isaacj87 for getting miui over to the triumph.
i take no credit for [email protected]#$%^&*() i am just posting this link so people who dont go to android forums can find this!
to flash this you will also need issacj87's CWM custom made for the triumph.
here you go guys and again be sure to thank isaacj87 for all his hard work!!!!!!!!!!!!!
DISCLAIMER: I am not responsible for any damages (bricking/phone ruining) occurred while flashing or using this ROM. By using this ROM, you understand that that I am not liable for any or all consequences of using this ROM. If you don't know what you're doing, DON'T TRY IT. Use at your own risk!
SPECIAL NOTE: These builds are not being built from source (only partially). This port is technically a port of a port of a port (DHD-CN --> DHD-EN --> MI410 --> Triumph). I can only account for the changes I made personally. There are no records on what was changed up to this point from elsewhere. This is something to consider.
Also, since I don't have the source for this ROM, it's being worked on with a take-it-or-leave-it attitude. If I can manage to fix something, it'll get fix. Since it was originally in Chinese, some of the language translations will be strange. I'm using code from CM7, building said code, and cramming it into MIUI. Since MIUI and CM7 share a lot of the same code, this has been working fine so far. But remember: I can't stress how much I don't want complaints and bug reports. I'm doing this for my own amusement and I'm just sharing what I've got.
I'd like to put up the the changes I've made to this ROM, but, basically, it would be useless. I used whatever tools I could find to decompile the various aspects and apply changes, but I wasn't able to save any of the decompiled stuff in any readable form. However, the changes to kernel I made will always be available. You can view those changes on my Github: http://github.com/ikarosdev
Overall, everything has been working quite well and I hope your happy with the results.
What works:
BOLD=NEW
RIL/3G/1xRTT
Audio/Call recording
WIFI
USB Tethering
Bluetooh
Keymapping
2D/3D/EGL/GPU
LED (dual-mode)
Capacitive button lights
Screen rotate/orientation
Touchscreen with multitouch/screen rotate capable
USB mounting
CRT screen off animation
Proximity sensor
Camera (front and rear) [see next section below]
GPS
HD 720P video recording/FFC video recording
MMS [see next section below]
Torch
Google Talk with video/voice chat
Wired headse
What partially works:
Camera (FFC output during video calling and snapshots is not mirrored.)
MMS (I can send, but not receive. Always comes back complaining about something.)
What doesn't work:
Ambient light sensors
WIFI hotspot (DON'T ASK, WON'T FIX)
720p video recording (Doesn't work in MIUI camera app. I've heard reports this works with a 3rd-party app)
HDMI out/mirroring (I don't have any way of testing this. Maybe it does work.
Known issues:
These builds, as mentioned, are not being built from source. As such, measures were taken to get everything working. Don't be surprised if you get a FC or eleven. Furthermore, these are development builds (a.k.a not stable). Some of you may be able to live with it, some won't.
Being similar to CM7 (at the core), the proximity sensor goes wonky during phone calls.
Recovery:
I also have my own CWM port for the Triumph. Since I got everything working, it's been running like a champ. I've themed it a bit to make it unique, but it's still Clockwork recovery at its core. I've currently put this up (minus the custom colors and graphics) for review to be included in ROM Manager. You can watch its progress here: http://github.com/koush/ROMManagerManifest/issues/311
The keymapping in my recovery is:
- Volume up/down to navigate
- Menu to select
- Back to go backwards
Downloads:
Recovery:
NOTE: tjstyle's recovery (4.0.0.9) will not work. You have to use a recovery for the Triumph.
NOTE: You must use a recovery with EXT4 capabilities. The one below should be just fine. If you're already using a recovery with such features, you don't have to change it.
ROM
NEWhttp://www.mediafire.com/?0m5rm6l5sl6samc
OLDhttp://www.mediafire.com/?u80w31lrkeoj05f
CWM
NEWhttp://www.mediafire.com/?y10vq724nr7al8p
OLDhttp://www.mediafire.com/?0h8uph17x1w30e8
**Instructions on how to install isaacj87's CWM**
1. download the recover img listed above
2. unzip the file using winrar or any other unzipping program
3.turn your triumph all the way off
4. unplug the usb cable for your triumph
5. hold the volume down+power button on your MT
6. the screen should come up as black with small white text in the top right hand corner. the text will keep repeating but dont worry this is normal.
7. plug the usb cable into your MT and computer and let the drivers install.
8. once they are finished installing, go to computer and you should see a new device called mobile. click on it then click on the image folder.
9. there you will see the recovery.img file. take this and make a back up of it on your desktop or in a safe place where you wont lose it.
10. next drag issacj87's recovery.img to the folder and copy and replace the current recovery.img. once this is finished you can eject your MT and the only way to get it out of bootloader mode is to do a battery pull.
11. after the phone is off hold both volume keys and also the power button and it will boot into isaacj87's cwm 4.0.1.5 recovery =)
12. from there do a full wipe of the system and D cache and user data and then you can flash MIUI!!!!!
Enjoy!!!!!!!
THANK YOU AGAIN ISACCJ87!!!!!!!!!!!!!!!!!!!!!
original thread at android forums
http://androidforums.com/triumph-al...1-10-7-triumph-10132011-1-gb-2-3-5-based.html
hmm no mms. i will wait. thanks for the heads up
Could you, I don't know.......post a link to the original thread? Whats working, whats not, features, change log, screenshots, ect. Elaborate a little.
there is that better?
platypuss94 said:
there is that better?
Click to expand...
Click to collapse
Yes sir Thank you. I went ahead and flashed a little while ago, and this is a nice miui build. Needs to be overclocked. But other then that, its nice.
Wait, this ROM requires a /data wipe? That's different.
crxmax said:
hmm no mms. i will wait. thanks for the heads up
Click to expand...
Click to collapse
MMS is my least favorite smartphone feature by far... try GO SMS (it comes with built-in uploading) or just use URLy to put files online. Since we all know how lousy Virgin Mobile's MMS system is already.
I kind of use it for work. Need to be able to send and receive. Its easiest to send to a phone number for some customers
Sent from my Triumph using XDA App
couldnt resist...seems like wifi locks up my screen tho =/
Data is horrible with this and cm7. Constantly having to toggle mobile data off then on to get it to work.
Sent from my MOTWX435KT using xda premium
Will Isaac's kernel that works on cm7 work on this?
Sent from my Triumph using MIUI
dimasp6 said:
Will Isaac's kernel that works on cm7 work on this?
Sent from my Triumph using MIUI
Click to expand...
Click to collapse
No. It'll only work on CM7.
isaacj87 said:
No. It'll only work on CM7.
Click to expand...
Click to collapse
Alright, thanks.
Sent from my Triumph using xda premium
rom has been updated. it would be nice if the original poster would keep up with the updates.
crxmax said:
rom has been updated. it would be nice if the original poster would keep up with the updates.
Click to expand...
Click to collapse
yeah. the link to the "original" thread on android forums doesnt work. i want update!
Here you go.
http://androidforums.com/triumph-al...1-10-7-triumph-10132011-1-gb-2-3-5-based.html
Anyone else have data problems with miui? Its super solid with the exception that my data drops constantly.
Sent from my Motorola Triumph using xda premium
i use juice defender. it cuts off data when the screen is off and restarts it when you turn the screen back on. thus resetting your 3g every time. not an actual "fix" but it makes the rom that much more usable
MMS has been fixed. I've been sending and receiving all day today. Clean pics, I might add.
I've also went ahead and bumped us up to 1.10.14. It will be released soon.
I've been investigating some fixes for the data drop issue. I think I may have found something that might work. I'm going to try it first in CM7 and if it works, it should be applicable to MIUI as well.
Happy MIUI-ing guys.
P.S. I would make an "official" thread here, but it seems most Triumph users frequent Android Forums. I'll make an effort to keep an eye out here as well.
crxmax said:
i use juice defender. it cuts off data when the screen is off and restarts it when you turn the screen back on. thus resetting your 3g every time. not an actual "fix" but it makes the rom that much more usable
Click to expand...
Click to collapse
I found something that might fix this problem (i.e. a real solution). Tickerguy also worked on a solution that seems to be working. He's going to test it for a couple days to confirm, but so far it looks good.
Once he shares his fix, I'll try and "code" (smali) it into MIUI.
i cant wait for this next update.
hello,
as far i know the battery life on raph is that bad because of the LCD-driver. since nobody knows how to switch the LCD off - and back on again - the LCD is just dimmed - but stays on.
... of course this consumes battery a lot ...
i'd like to help - if i can ?
- i am a developer (but never developed for (xd)android so far)...
- i have a raph
- i have basic (xd)android knowledge
can somebody tell me, where to start ?
what exactly do we need ? the correct hardware registers / arm-code to handle it ?
Wouldn't it make sense to try on WM first - developing arm-code - without win-api of course.
WM has one advantage: i can test faster - since i don't have to reboot to android all the time.
so i need:
- i need to know, what the xdandroid developers already know about this topic - as far i know, they have the code to switch off - but not to switch on.
- i need a quickstart guide how to setup a "xdandroid development environment".
thank you!
Some thoughts
Baal, good look with your try. I'm sure many people will pray for your success -I'm one of them.
I don't have enough time to try to do that, but I spent many hours thinking about the problem. What I'ld do is:
Try to capture all the operations that WM does diring a sleep-on/sleep-off process, specifically registry modifications, internal calls, etc. Also try to save the status before and after, in case they depend on some kind of previous initialization.
I'm not sure if developers didn't get that information or do have it but didn't know how to implement it. Ask in the XDandroid development list.
If you have to do that, maybe you can use some kind of emulator, but probably you'll need to get a system debugger on your phone.
Modify the android module to do the same operations.
Here, both XDandroid Development List or other android developers should help you a lot.
In this part, you'll have to reboot many times...
Good luck! And keep us informed, please.
Well, this is a kernel issue. Unfortunately there's no "how-to" on the kernel sources...
The Getting the Source page is about the system image unfortunately.
Here's the GIT repo for the kernel code.
As for the rest of it, I don't know how to help you. I don't know how they shut the panel down, and as you know, no one actually figured out how to shut the screen back down. Hopefully someone else chimes in about the other information you requested.
Please keep us updated...
Hi, Baal_zebuz
I know it's been a short time since your intentions were declared, but, do you still keep them and you're working on it, or you already abandoned the idea -no matter the reasons, time, difficulty, etc.? Just to keep the hope's flame lighting or switch it off.
Thanks in advance!
Uhm... I use xdandroid in Raph100 and if the chargher is disconnected, the backlight os turning off after few seconds. I've downloaded the last one from xdandroid.com
Maybe I am OT, in this case I apologize
TheXeno said:
Uhm... I use xdandroid in Raph100 and if the chargher is disconnected, the backlight os turning off after few seconds. I've downloaded the last one from xdandroid.com
Maybe I am OT, in this case I apologize
Click to expand...
Click to collapse
Brightness is set to 0 and the backlight is shut off. Unfortunately the panel itself is still drawing power, and sucking battery life. No one has sorted out the proper kernel code to deinit/reinit the panel.
Hey all, I'm trying to figure out how to get some brightness settings for the touch key brightness to stick. I've used LG 2x Notifications and O2x Touch Key Brightness, and they both work up until the point where i put the phone to sleep by tapping the power button. As soon as I wake it up, the brightness goes straight to zero unless i head back to the app and raise it up again. And if i uninstall the apps, the brightness on my keys stay off until i re-flash or reinstall the app again. Help!
My issue is a little different but similar. It worked fine for me on every basic gingerbread rom, but when I switched to a cm7 based rom the lights change with the brightness of the screen. I turned off all the light notifications but it did not help.
If anyone has any ideas, I'd love to hear them.
What rom?
Sent from my LG-P999 using XDA
redmonke255 said:
What rom?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
On SinghUI but it doesn't have built-in LED notifications, if that's what you're getting at.
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
xBIGREDDx said:
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
Click to expand...
Click to collapse
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
rrroach said:
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
Click to expand...
Click to collapse
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
xBIGREDDx said:
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
Click to expand...
Click to collapse
Thanks for the link. It turns out that the ROM does have led notifications. However, disabling them didn't help the problem. :/ the g2x has just been an awful experience for me! :/
On all custom Roms I've tried so far (and they've been a few), there's an ongoing problem while using Android Auto connected to the car's built-in display. Basically, if you plug in your phone and start using AA, after a while the bottom bar on the car's display will disappear, and although you can keep driving and AA will keep working, once you stop and unplug the phone from the car, the phone will lock you out and it's screen will start to flicker and go crazy, giving you no other option but to force reboot the phone.
This issue was present on MIUI Oreo roms as well, but since they updated to Pie last month, it was addressed and a fix was found (seems it was related to the devices default display drivers). For custom Roms, there's a temporary workaround, which is to disable hardware overlays in developer settings, but you need to do this every time you reboot your phone since these settings don't stick permanently.
I've posted and mentioned this issue on several different custom ROM threads, but as far as I know, none of the devs has acknowledged the issue nor has tried to find a solution. So, the question is; how many of you have the same problem?
Please provide your feedback, as it would be good to let the devs know this is not unimportant or isolated.
krilok said:
On all custom Roms I've tried so far (and they've been a few), there's an ongoing problem while using Android Auto connected to the car's built-in display. Basically, if you plug in your phone and start using AA, after a while the bottom bar on the car's display will disappear, and although you can keep driving and AA will keep working, once you stop and unplug the phone from the car, the phone will lock you out and it's screen will start to flicker and go crazy, giving you no other option but to force reboot the phone.
This issue was present on MIUI Oreo roms as well, but since they updated to Pie last month, it was addressed and a fix was found (seems it was related to the devices default display drivers). For custom Roms, there's a temporary workaround, which is to disable hardware overlays in developer settings, but you need to do this every time you reboot your phone since these settings don't stick permanently.
I've posted and mentioned this issue on several different custom ROM threads, but as far as I know, none of the devs has acknowledged the issue nor has tried to find a solution. So, the question is; how many of you have the same problem?
Please provide your feedback, as it would be good to let the devs know this is not unimportant or isolated.
Click to expand...
Click to collapse
On which MIUI Version are you having that problem?
Which car display with which software version are you using?
For me with MIUI 8.12.27 weekly EU version and Skoda Bolero display I'm not having the issue you describe.
MikelFuchs said:
On which MIUI Version are you having that problem?
Which car display with which software version are you using?
For me with MIUI 8.12.27 weekly EU version and Skoda Bolero display I'm not having the issue you describe.
Click to expand...
Click to collapse
Please read the title: on custom roms, not miui...
You wrote on Oreo stock ROM it was present to.
oiseau1201 said:
You wrote on Oreo stock ROM it was present to.
Click to expand...
Click to collapse
Yes, and it was (plenty of comments on MIUI forums and over the net, if you want to take a look...) They fixed it on Pie, and if you're still running Oreo and don't have issues, then I guess they fixed it there, too.
This poll, topic and thread is for the issues still affecting Aosp based custom roms, such as Crdroid, PE, Lineage, etc.
Even I would like to know the result of this poll. I am on the verge of trying out a custom ROM (since i am done with the bugs in MIUI). But if AA doesn't work on custom ROM, it is a showstopper for me.
Hi,
I have a different issue with Android Auto.
My problem is that when I connect to Android Auto, after a couple of minutes (1-2, 2-3 minutes) the screen on the car's display seems to be stuck, and from then on it doesn't follow my progress on the way. The screen itself is not frozen, because e.g. I can make a reroute but after it is done it goes back to the "original" state of my route when it stopped progressing. The screen remains responsive regarding the controls because I can even change to Google Maps on the car's AA display, and it works flawlessly.
Anyone else had this issue?
I'm using xiaomi.eu rom 9.1.17 beta
aghilvr said:
Even I would like to know the result of this poll. I am on the verge of trying out a custom ROM (since i am done with the bugs in MIUI). But if AA doesn't work on custom ROM, it is a showstopper for me.
Click to expand...
Click to collapse
I'm currently on Crdroid, and in my opinion it's the one that works best. As for the AA issue, it's present on all custom roms, but for the time being, I'm using the workaround I mentioned on OP and can use AA fully.
rn74 said:
Hi,
I have a different issue with Android Auto.
My problem is that when I connect to Android Auto, after a couple of minutes (1-2, 2-3 minutes) the screen on the car's display seems to be stuck, and from then on it doesn't follow my progress on the way. The screen itself is not frozen, because e.g. I can make a reroute but after it is done it goes back to the "original" state of my route when it stopped progressing. The screen remains responsive regarding the controls because I can even change to Google Maps on the car's AA display, and it works flawlessly.
Anyone else had this issue?
I'm using xiaomi.eu rom 9.1.17 beta
Click to expand...
Click to collapse
Strange, I tried an EU rom about a couple of weeks ago for a few days and AA worked out of the box. Didn't like the MIUI stuff, though, so reverted back to Crdroid.
I however remember I flashed the full MIUI rom completely, wiping everything and starting from scratch, so if you want to stick with MIUI, maybe you should do a fresh install...
krilok said:
Strange, I tried an EU rom about a couple of weeks ago for a few days and AA worked out of the box. Didn't like the MIUI stuff, though, so reverted back to Crdroid.
I however remember I flashed the full MIUI rom completely, wiping everything and starting from scratch, so if you want to stick with MIUI, maybe you should do a fresh install...
Click to expand...
Click to collapse
Edit: just noticed. Are you using Waze for navigation? If you are, there's an ongoing location issue with the app running on MIUI...
Having the same issue running PIxelExperience and it's driving me nuts.
krilok said:
, there's a temporary workaround, which is to disable hardware overlays in developer settings, but you need to do this every time you reboot your phone since these settings don't stick permanently.
Click to expand...
Click to collapse
I did not know that, thanks for the tip .
Update: you can automate disabling the hardware overlays using Tasker and the Secure Settings plugin
bob*nwk said:
Having the same issue running PIxelExperience and it's driving me nuts.
I did not know that, thanks for the tip .
Update: you can automate disabling the hardware overlays using Tasker and the Secure Settings plugin
Click to expand...
Click to collapse
Thanks, I had read you could use tasker for that, but it's a paid app and I wouldn't be using it for anything else at the moment. I'm fine with remembering to disable it manually. Still, I believe the issue has to be addressed at some point by the devs...
One General question:
The only thing keeping me away from custom roms is the AA issue. Nice to hear that at least we have a workaround.
At the moment i am on MIUI Android pie and using a VW in build AA Display. The issue i'm having is that WhatsApp notifications are not shown on the Display. I can send WhatsApp Messages via Ok Google but not able to hear received messages.
Do you guys have the same issue?
gella1992 said:
One General question:
The only thing keeping me away from custom roms is the AA issue. Nice to hear that at least we have a workaround.
At the moment i am on MIUI Android pie and using a VW in build AA Display. The issue i'm having is that WhatsApp notifications are not shown on the Display. I can send WhatsApp Messages via Ok Google but not able to hear received messages.
Do you guys have the same issue?
Click to expand...
Click to collapse
Wouldn't be able to confirm that, although I did read somewhere that if you're using any Dual apps on MIUI, AA won't work correctly. Are you using two WhatsApp accounts by any chance...?
I can tell you though that on the current rom I'm using (crdroid), they do work and appear on the cars screen, although most of the time there's no notification ringtone whenever they arrive. Since that was happening on my previous phones too, be it on nougat, oreo and pie, I guess that's a problem with AA itself...
Thanks for your quick reply.
Happy to hear that it is generally working.
Not using dual Apps. Will try to flash a custom Rom in the next days
krilok said:
Thanks, I had read you could use tasker for that, but it's a paid app and I wouldn't be using it for anything else at the moment. I'm fine with remembering to disable it manually. Still, I believe the issue has to be addressed at some point by the devs...
Click to expand...
Click to collapse
If you buy it, I guarantee you will be using it for a lot more than just that...
papete said:
If you buy it, I guarantee you will be using it for a lot more than just that...
Click to expand...
Click to collapse
I can confirm this. Best $5,- I spent on an app ever.
papete said:
If you buy it, I guarantee you will be using it for a lot more than just that...
Click to expand...
Click to collapse
I understand and appreciate the recommendation, but I've already got Macrodroid for other automation functions...
I don't get the menu on the bottom visible with disabling HW Overlay, tested Nitrogen,CRdroid, Liquid Remix,LOS
using: beryllium-9.1.24-9.0-vendor-firmware
mf76130 said:
I don't get the menu on the bottom visible with disabling HW Overlay, tested Nitrogen,CRdroid, Liquid Remix,LOS
using: beryllium-9.1.24-9.0-vendor-firmware
Click to expand...
Click to collapse
Works for me and others as well, although someone did mention on another thread he couldn't get this workaround to work either...
This is my setup:
USB debugging on and hardware overlays disabled.
In AA developer options, enable 720, 1080, unknown sources.
If it still won't work, then Im guessing it could maybe be due to different screen panels or something...