Hey everyone. Hope this is 'dev' enough.
I haven't seen anything anywhere about AT&T note3 chroots, other than AT&T N3 can not because of lack of boot loop. Anyway, I thought i'd mention that it works quite well with partition & Xsdl. I made a small post for the interested in the general forum.
To my question: has anyone tried the freedreno drivers? ~Github link~
I haven't been able to build it properly, it's missing some .o's. I have gcc working on my chroot.
I'm also having problems with pulse/alsa/gstreamer, I think it's a permission problem. The android audio user shows as aid_audio, but the dir /dev/socket/ shows as usr:Media/grp:audio and the socket is system/system. They're recognized as users in the chroot, but they're still unable to find get access to it. I couldn't get an alsa recording app on from playstore to connect to it either.
I'm kinda wondering if something funky with permissions after towelroot. I couldn't get su,chroot, etc to work properly until I got the system to recognize su as 'root' instead of uid:0. Once I got that everything for su started working? So, lost and confused. Ideas on what i'm doing wrong?
thanks!
I was able to build a kernel with DRM and KGSL DRM interface enabled, boot CM11 with it, open SSH in my Debian chroot, kill Android, and then attempt to run Xorg with the freedreno driver but I ended up getting a memory mapping error and a segfault.
The Note 3's panel is a command-mode DSI panel which means it will not automatically display what is written to /dev/graphics/fb0 like you would expect. Instead, you must call an ioctl (FBIOPAN_DISPLAY) to force a refresh of the display. The panel must be on for this to work. I'm not sure the exact sequence required to turn on the display but it involves opening /dev/graphics/fb0 and possibly mmap'ing it. If you use the fbdev Xorg driver it will turn on the panel, but you must then run a program to continuously send the FBIOPAN_DISPLAY ioctl to refresh it. This is non-accelerated and also seems to crash any GTK apps (only X11 basic apps like xterm worked, and even then the refreshing was glitchy).
I'm trying to tackle kexec-hardboot first because that will allow booting an entirely-Debian-focused kernel with the correct color mode and the DRM drivers and all. It will likely require some patches to the KGSL GPU code in the kernel, at least it did on my Note 1. Get on #freedreno on Freenode if you aren't already there, lots of knowledgeable people there to analyze logs and find patches. I got it working on my HP TouchPad and Note i717 with help from there.
Very nice, thanks!
I've only gotten fb to work on my nexus5.
Also thanks for the heads up on the freenode. Going to check it out.
Have you messed with sound at all?
Edit:
Wait, did you do this on a 900A? (I'm probably way behind times?)
N900T, so bootloader-unlocked. It will be doubly hard to do on the N900A since you'll have to compile as modules rather than just compile your own kernel, at least unless you guys get kexec (non-hardboot) working on the locked variants. You should be able to mess around with the framebuffer on the stock kernel just fine though, only the freedreno driver needs custom kernel changes.
I haven't messed around with sound at all. On my HP TouchPad I figured out how to use ALSA UCM files which set up the mixer controls. By default Android locks the sound devices so using them from a chroot while Android is running probably won't happen, but with Android out of the way you may be able to use them. I do know on the Note 1 and the HP TouchPad you have to load q6.xxx firmware files for the audio system to initialize during boot.
This file will be of interest when writing ALSA UCM files:
https://github.com/CyanogenMod/android_device_samsung_hlte-common/blob/cm-11.0/audio/mixer_paths.xml
I used the TouchPad's mixer_paths.xml file to write two UCM "verbs" - one to turn on internal speakers and one to turn on headphones. The UCM file basically sets the given switches to the given values and is basically just a reformatting of mixer_paths.xml. I was unable to find a mixer_paths.xml for the Note 1 and thus haven't messed with sound on it yet (it has to exist somewhere...).
CalcProgrammer1 said:
N900T, so bootloader-unlocked. It will be doubly hard to do on the N900A since you'll have to compile as modules rather than just compile your own kernel, at least unless you guys get kexec (non-hardboot) working on the locked variants. You should be able to mess around with the framebuffer on the stock kernel just fine though, only the freedreno driver needs custom kernel changes.
I haven't messed around with sound at all. On my HP TouchPad I figured out how to use ALSA UCM files which set up the mixer controls. By default Android locks the sound devices so using them from a chroot while Android is running probably won't happen, but with Android out of the way you may be able to use them. I do know on the Note 1 and the HP TouchPad you have to load q6.xxx firmware files for the audio system to initialize during boot.
This file will be of interest when writing ALSA UCM files:
https://github.com/CyanogenMod/android_device_samsung_hlte-common/blob/cm-11.0/audio/mixer_paths.xml
I used the TouchPad's mixer_paths.xml file to write two UCM "verbs" - one to turn on internal speakers and one to turn on headphones. The UCM file basically sets the given switches to the given values and is basically just a reformatting of mixer_paths.xml. I was unable to find a mixer_paths.xml for the Note 1 and thus haven't messed with sound on it yet (it has to exist somewhere...).
Click to expand...
Click to collapse
Great thanks! That explains a few things with the boot lock. FB has been a total no go for me. I read something about the type of display not working with it? I have no idea if that's true, and can't seem to find that information right now. (it worked great on the my note2). If someone has gotten success let me know! I'll check out the UCM once more. I did get ALSA working with debian on the note 1, so that's the first thing I tried. My Touchpad, I thought, worked right out of the box. (I miss that thing!)
I'll give it shot tonight and see what I get. thanks a lot to both of you.
The Note 3's panel is a command mode panel while the Note 1's panel is video mode. I'm not sure about the Note 2 as I don't have one but if it worked for you it was likely video mode as well. In video mode it works like you'd expect any display to work - the framebuffer memory is automatically drawn to the screen at a fixed refresh rate (60Hz). A command mode panel is different, the framebuffer is only drawn to the display when it is commanded to, and thus the software has control over the refresh rate of the display. I did a test where I found the section of code in the Note 3's kernel where it does the software refresh and stuck a printk in there. I had the kmsg printing out over SSH while I swiped the screen around in Android. Sure enough, the printout only happened when I moved my finger and caused the framebuffer to update, the screen completely stopped refreshing otherwise.
I'm still trying to find a good solution to this, especially in regards to running kexec-hardboot and the kexecboot bootloader GUI. I've been able to get kexecboot to display by sticking an FBIOPAN_DISPLAY ioctl into the framebuffer sync function that kexecboot calls after it updates the screen. This ioctl seems to force the display to refresh, but only if certain conditions are met (and I'm unsure what all these conditions are). I do know that the LCD (actually AMOLED but it's listed as LCD panel in the code) must be powered on, the framebuffer must be open (i.e. call the open() function to /dev/graphics/fb0 and get a file descriptor), and possibly memory-mapped as well (the code I was using as a software refresher had mmap, though it might not be necessary). This is another thing to go to #freedreno for, a user there (crondog) has been working on Freedreno on the 2013 Nexus 7 which also has a command mode panel and he's done some software refresher work.
Related
I wrote this program because I was unable to find a good app capable of recording the other side of the call properly.
Except for AirVoice, all such apps record the speaker rather than the line, and you barely hear the other side in the recordings.
The guy who wrote AirVoice knew the trick but seemed to be very annoyed by the negative feedback from Android Market, where the users of various devices (with the list of supported ones clearly stated!) tried to install that program. Because it wasn't open source, I had to disassemble it in order to write what I wanted exactly.
So the app uses an esoteric HTC driver, and NEEDS THE ROOT ACCESS just to open the device. If you do "adb shell chmod 666 '/dev/voc*' ", it'll never ask you for root access (but you have to be ROOT to execute that command).
It writes the calls in either WAV (recommended) or MP3 format (not tested much; needs some time to encode the file after the call, but the size is about 4 times smaller), stereo (left ear is your voice, right is that of the other party), to "/sdcard/voix" directory.
The kernel driver itself is kinda buggy. Actually, the auto-answer mode is non-functional for kendon's & ninpo's kernels (others not tested). Do NOT select it in Settings unless you've got such ROM and particularly need to reboot your phone on each incoming call . It'd be nice if somebody try to fix that.
If you select "Ask each time" for any incoming calls, be sure to wait half a mo until the confirmation dialog appears. The "Foreground service" (default) setting is also recommended because Android may otherwise kill it if memory is low.
Any comments are welcome. I'm not sure that I'll ever add something to this program because I'm too lazy for that, but any bugs will reasonably be fixed. The code is open source, PM me if you're a programmer and have any ideas how to improve it.
=======================
NOV 24 UPDATE
Numerous improvements/corrections/bugfixes (I'm not removing the previous version as this one haven't been much tested).
Enjoy!
Thanks dude. Great job
avs333 said:
I wrote this program because I was unable to find a good app capable of recording the other side of the call properly.
Except for AirVoice, all such apps record the speaker rather than the line, and you barely hear the other side in the recordings.
The guy who wrote AirVoice knew the trick but seemed to be very annoyed by the negative feedback from Android Market, where the users of various devices (with the list of supported ones clearly stated!) tried to install that program. Because it wasn't open source, I had to disassemble it in order to write what I wanted exactly.
So the app uses an esoteric HTC driver, and NEEDS THE ROOT ACCESS just to open the device. If you do "adb shell chmod 666 '/dev/voc*' ", it'll never ask you for root access (but you have to be ROOT to execute that command).
It writes the calls in either WAV (recommended) or MP3 format (not tested much; needs some time to encode the file after the call, but the size is about 4 times smaller), stereo (left ear is your voice, right is that of the other party), to "/sdcard/voix" directory.
The kernel driver itself is kinda buggy. Actually, the auto-answer mode is non-functional for kendon's & ninpo's kernels (others not tested). Do NOT select it in Settings unless you've got such ROM and particularly need to reboot your phone on each incoming call . It'd be nice if somebody try to fix that.
If you select "Ask each time" for any incoming calls, be sure to wait half a mo until the confirmation dialog appears. The "Foreground service" (default) setting is also recommended because Android may otherwise kill it if memory is low.
Any comments are welcome. I'm not sure that I'll ever add something to this program because I'm too lazy for that, but any bugs will reasonably be fixed. The code is open source, PM me if you're a programmer and have any ideas how to improve it.
Click to expand...
Click to collapse
thanks, good job
but recorded sound a lit low, any chance to make it loud
Aha Thats Great Now i can prove my prank calls
no auto start, please add (i mean after re-boot)
Hi-Fi said:
but recorded sound a lit low, any chance to make it loud
Click to expand...
Click to collapse
No problems with sound volume here, but I'll see if I can add some basic volume normalisation...
Hi-Fi said:
no auto start, please add (i mean after re-boot)
Click to expand...
Click to collapse
Added as an option in Settings. Also fixed a triffle UI bug (forgetting to set proper dialog attributes).
Just tried this, works great on my Hero (Vanilla Eclair 4.0). Thank you very much for this one!
Interesting software. Could you possibly add a new feature: The app saves all calls, but deletes them, if you don't move them to another folder/to your PC.
This because I could record all of my calls, without the risk of making a huge 1Gt folder to fill up my memory. So if the user could choose how many recent calls (2,5,10) the app saves before deleting them I'd be great!
What about battery draining?
This great app is also tiny enough not to reduce drastically battery duration?
TIA
I'd love to see this generalized to not require the HTC driver. Do you think that would be possible?
cool app. anyone know if it would be possible to play an audio file directly to the caller? would come in handy rickrolling damn telemarketers
Very good work. Handy app, for sure.
Can you enable recording mid call?
Works in all Androis Devices? I have a Milestone.
Awesome idea, I've been looking for exactly this sort of software.
I'm having a bug I hope someone can help me with. When I start the program I get a prompt that says "Device does not exist, or its permissions cannot be changed." When I click "OK" it takes me to the screen to uninstall the program.
I'm running an Evo, fully rooted, NAND unlocked, running Virus Airbourne ROM and King #11 kernel.
I never get the prompt from the SuperUser app to give the app root access.
I tried the adb command but it gave me the error:
Unable to chmod dev/voc*: No such file or directory
Having same issue on rooted G2.
Sent from my T-Mobile G2 using XDA App
MercuryTangent said:
Awesome idea, I've been looking for exactly this sort of software.
I'm having a bug I hope someone can help me with. When I start the program I get a prompt that says "Device does not exist, or its permissions cannot be changed." When I click "OK" it takes me to the screen to uninstall the program.
I'm running an Evo, fully rooted, NAND unlocked, running Virus Airbourne ROM and King #11 kernel.
I never get the prompt from the SuperUser app to give the app root access.
I tried the adb command but it gave me the error:
Unable to chmod dev/voc*: No such file or directory
Click to expand...
Click to collapse
I experience the same problems on my rooted DINC. ROM and kernel are in sig.
Am I right to assume that this is a HTC Hero exclusive?
bemymonkey said:
Am I right to assume that this is a HTC Hero exclusive?
Click to expand...
Click to collapse
Likely so, but I'm hoping the dev will extend it or I can find a way to make it work
This is amazing app. The only thing I would beg the author to consider a white status bar icon for normal running service as colored icons there usually break the aestetics of Android UI. The icon can change or become colored while recording, but when only running in the background it should remain white.
I have the same problem (link to uninstall) on my Nexus One. Everything works fine on Hero
I had some issues with the ADB commands for preparing my rooted Nook Color for on-device app install (primarily due to microcrap's 64-bit Vista) so I found a very easy method.
In the Market, there's an app called "Sqlite Editor" from the folks who make "Root Explorer" - it's about $3.07 US$ but I bought it anyway.
With this [AFTER A BACKUP!] I was able to directly edit the settings.db (sub category SECURE) and change the following:
'install_non_market_apps' from the default value of 0 to 1 and following a SAVE and REBOOT I can now install directly from my SD Card.
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Dare I do this???
I also posted this in Mobileread's excellent Nook Color Forum and I was thinking that may we should also acknowledge them as a great forum for our beloved Nooks!
docfreed said:
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Dare I do this???
Click to expand...
Click to collapse
LOL...If only it were this easy.
I had no issue with installing apps from the sd card after rooting/installing mkt and gapps.
Depends on How You Rooted..
I'm not certain but some rooting methods have market/gapps built-in, some don't. I used Autonooter (after upgrading to 1.01) and market & Gmail just appeared - I never had to install anything else.
If you used Autonooter then you wouldn't have to do anything to be able to install non market apps. Maybe just toggle the setting in Nook Tools if anything.
docfreed said:
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Click to expand...
Click to collapse
Its NOT that simple, its been turned on in the kernel & custom ones built for it with nothing.
If you see the "salting nook" posts so much as been done trying to get it to work, most expect something ground breaking to come from actually looking at the pins on the chip it self an connection through the MoBo.
Amd sold faulty quad cores as triples so it could be that the chip/Mobo cant do it. Could be a easy hardware mod but TBH so much deep thought an attempts have been seen in IRC i dont see a "virtual fix" anytime soon.
But that said im an idiot so could be 475% wrong
Yeah, I tried toggling Nook Color Tools per the instructions - never seemed to work for me. Anyway, it appears to be just a one-shot adjustment any way it's done (at least till we get FroYo) so I'm happy.
Merry XMAS everyone
docfreed
sqlite not working for me
Purchased Sqlite, when trying to install, exits without loading apps. Any suggestions? Rooted with older booker and then re-rooted with pre 1.01 autonooker. Thanks. -
I have a kernel and u-boot that enables the bluetooth portion of the module and sets up an rfkill device. hciattach will detect it as a TI Bluetooth module and will load one of the TI bluetooth firmware scripts, but then complains about a missing socket or something. It sounds like a software error more than anything that might be wrong with the hardware.
What this means is that the Bluetooth part of the WiFi module isn't just left disconnected and the link to the CPU is working. But we don't know if the antenna is set up to share between wifi and Bluetooth or if the hardware is otherwise missing something that would keep it from working.
If you have experience with getting TI WiLink Bluetooth working in Android or Linux, or know someone who does, PM me or join us on Freenode channel #nookie. We're really close!
Hi,
Before a few month the display of my note died. Now I need a device for controlling my quadrocopter via inet. My idea was to use my note for this task(The flightcontroller is Arduino based, so I should be able to control it via usb). The problem is, I need to drive it headless. Concrete, I need to use gps, the camera and to put software onto the device without using the display.
I think the best way would be to install a linux into a chroot environment but it's questionable if I'm able to access the camera and gps from inside the chroot env, so I'm open for better ideas.
Kind Regards
Ralph
can no longer see the display so needing tips on how to use android headless!
debian kit seems to work pretty well for using linux applications but I need to solve the problem of how to start that (or anything else) after a reboot without needing to use the Android gui.
a few days ago I had access to that gui but now my hdmi->vga box died
(hardware failure - not related to debiankit or any Android app )
so now I have an Android minipc with those nice debian extras on it that I can't risk shutting down for feat of not being able to use it at all!
- unless I can find what I need to edit to get it to at least start sshd after boot!
vnc/xrdp would be nice too but ssh would be the minimum -
.. after a week still hoping .. please someone please suggest *something*!
btw connectbot is on there (like debiankit it was installed while I could still see the display) and I have seen posts suggesting that you can add scripts in that to execute after boot, but how do I do that without using the gui?
I found an sqlite3 file that looks like it contains the connectbot settings .. can I add something in there directly using sqlite3 via the shell?
sooner or later that reboot will come - the question for me now is will this device still be usable at all after that!
headless Android (on real devices) info needed URGENTLY!
I've began to write up a guide for getting Arch usable on the Nexus 7. I just threw it up on google docs because I'm too lazy to try to do the wiki thing until it's more complete. Hopefully it is far enough along to get things rolling for people who are looking to experiment with arch.
Anyway, it's a work in progress, if anyone has suggestions, correction, completions, criticisms, etc then holler.
Linkies
Changelog
========
2013-07-20
--Added instructions for installing the platform tools on an arch host pc
--Added references to wicd and network manager as alternatives to netctl
2013-10-20
--Updated instructions to reflect new *-grouper.zip naming scheme for MultiROM files
--Added instructions for updating the kernel to include kexec
--Got bluetooth 90% working. Interface comes up and can find devices with scan. Can’t get it to pair yet though.
2013-10-24
--Got the bluetooth device to power up on boot by adding a udev rule. Unfortunately the bluetooth daemon seems to be failing as it starts.
2013-10-28
--My keyboard is pairing on boot now. Ugly ugly things to get it working, but it works.
2013-11-03
--Updated the guide to get X working.
2013-11-04
--Tweaked xorg.conf files to get kde and e17 working.
--Added instructions to get Touchégg working to provide more tablety experience
Todo/Bugs
Problems/Bugs/Todo
The following is a list of things that need to be addressed or that I want to address. These things will be tackled in no particular order but hopefully over time the number bugs and problems will go down relative to the number of features I want to add.
Feel free to comment with your own ideas or bug reports.
Fix slow shutdowns after enabling networking with netctl
Fix whatever extremely verbose crash shows up on shutdown after setting up bluetooth
Get bluetooth working without hacks and under bluez5
Get a graphical login working
On screen keyboard (especially at login screen)
Set up an aur and/or googlecode project to automate some of the scripting required to get things working
Automate the process with some kind of setup tool
Replace the google doc with a wiki page in a relevant place
Make a custom spin that works more out of the box
Sound
GPS
Accelerometer
Magnetometer
Hardware buttons
Any other sensors that I forgot or am unaware of
Auto screen rotation
For the section on setting up fastboot and adb...it's safe to assume someone installing arch on the nex7 probably has arch on their pc too. For arch, you need to set up access to the AUR, with a package manager that has access to it, i.e. yaourt. Then you can get android-sdk-platform-tools. The rest of the guide looks good. I personally like wicd for my network manager as it is easier to add and remove networks when you go to new locations, and I installed e17(enlightenment desktop).
joeG78 said:
For the section on setting up fastboot and adb...it's safe to assume someone installing arch on the nex7 probably has arch on their pc too. For arch, you need to set up access to the AUR, with a package manager that has access to it, i.e. yaourt. Then you can get android-sdk-platform-tools. The rest of the guide looks good. I personally like wicd for my network manager as it is easier to add and remove networks when you go to new locations, and I installed e17(enlightenment desktop).
Click to expand...
Click to collapse
Thanks for the feedback
I don't have arch on my pc at the moment, so it's not a given, but i think you are right that people are probably more likely to have arch if they are looking at this guide. I updated the guide with info on how to install the tools from AUR. Also added links to wicd and Network Manager in the arch wiki so people are aware of some options if they don't like netctl, and mentioned that e17 works.
Xorg with alarm on nexus 7
Okay, got ALarm installed on my nexus 7 8GB.
For Xorg, I used files from "plasma active" nexus 7 distribution.
Just take them from the plasma active and put them into your /etc/X11 and X should work.
(I can't post a link, must wait 10 posts, I'll link the files later or you can PM me)
My only problem now is to put a cross-compile toolchain on my computer to be able to compile e17 with illume modules. Tried to compile on my tablet but it's too slow and I've not enough disk free to finish. If anybody can help on this point…
What distribution are you using on your PC? Also you can pm me the link for the xorg configuration and I'll post it for you
OK so I have come as far as installing multirom and I installed the archlinux rom and got this error when I tried to boot it
"kexec-hardboot support required to boot this kernel"
How do I resolve this?
thecrimsonfukr said:
OK so I have come as far as installing multirom and I installed the archlinux rom and got this error when I tried to boot it
"kexec-hardboot support required to boot this kernel"
How do I resolve this?
Click to expand...
Click to collapse
Go back and reread the multirom thread, then install a kexec-hardboot patched kernel in your internal rom.
Sent from my SGH-T679 using xda premium
joeG78 said:
Go back and reread the multirom thread, then install a kexec-hardboot patched kernel in your internal rom.
Sent from my SGH-T679 using xda premium
Click to expand...
Click to collapse
Thank you! I didnt realize it was that simple... for some reason i find the original multirom post difficult to follow.
thecrimsonfukr said:
Thank you! I didnt realize it was that simple... for some reason i find the original multirom post difficult to follow.
Click to expand...
Click to collapse
Hello
i want install arch linux on nexus 7 , but i confuse about it . is arch linux on nexus 7 fast and stable ?
can i watch hd video in arch linux withot lag ? before days i install ubuntu desktop on N7 but when i open video HD ( not full) with vlc , it somtimes play withot sound and it have lag . unity is heavy for nexus 7 , i want install arch + lxde . is it fater ?
sorry for english .
For me Arch works without any problems but when I type startx xserver freezes after the first image of xfce or e17.
Has anybody a solution?
? How to install e17 ?
joeG78 said:
For the section on setting up fastboot and adb...it's safe to assume someone installing arch on the nex7 probably has arch on their pc too. For arch, you need to set up access to the AUR, with a package manager that has access to it, i.e. yaourt. Then you can get android-sdk-platform-tools. The rest of the guide looks good. I personally like wicd for my network manager as it is easier to add and remove networks when you go to new locations, and I installed e17(enlightenment desktop).
Click to expand...
Click to collapse
e17 is the fast
so , i want to installing to my nexus 7
thanks .
Why ? my bluetooth not work?
not find the device ????
ylixir said:
I've began to write up a guide for getting Arch usable on the Nexus 7. I just threw it up on google docs because I'm too lazy to try to do the wiki thing until it's more complete. Hopefully it is far enough along to get things rolling for people who are looking to experiment with arch.
Anyway, it's a work in progress, if anyone has suggestions, correction, completions, criticisms, etc then holler.
My bluetooth not working
cannot find the device ??
Nexus 7 32GB Wifi
Click to expand...
Click to collapse
bluetooth
I have bluetooth (almost) working. I've put instructions in the guide. They aren't really a final solution, but maybe people who are running gui's can tell me if they work. I know I have the hardware working because I can see my keyboard when I scan for it, but I can't figure out how to get bluez5 to pair from the command line. Hopefully someone has better luck with a gui?
bluetooth
I've got Bluetooth working. I even have it pairing automatically on boot with a keyboard. Its an ugly solution but it works. The guide has been updated. I'll tackle X next
My Arch Install
Hey just wanted to add my install experience to the thread hopefully to help others. First of all I want say thanks for all documentation from the previous posters. I tried to follow the instructions as close as possible for a kde install, but I ran into some trouble with lightdm, so I tried kdm instead. And I can happily report it has worked swimmingly. Instructions on how to setup kdm, navigate to /usr/share/config/kdm. First edit the kdmrc to turn off the themed greeter. Then add the xvkbd to the XSetup file as in the lightdm setup. Another thing I did was utilize the plasmaboard widget on my main kde panel for my on screen keyboard once I log in. It seems to work much better than xvkbd for me. I can also confirm flash is working great.
So this really close to totally replacing my linux laptop, especially when I am on the go, in fact I am writing this post on the device in arch. However one key piece is still missing for me is sound. I can't seem to coax any sound out the device with my arch install, and amarok crashes on startup, even though both these items were working perfectly in ubuntu. If any one has any ideas how to make audio and amarok work I would be immensely grateful. Also thanks again, I am so happy to be rid of the X11 touch race condition. I have added a screenshot of me editing this post for those interested as well.
Figured out sound!
I think i found a solution to all of my troubles from my previous post. Amarok started working after a pacman update. My general audio problems seem to be caused by the linux for tegra audio drivers lack of head phone jack detection, I found a workaround the ubuntu nexus 7 launchpad bug tracker: https://bugs.launchpad.net/ubuntu-nexus7/+bug/1068804/comments/24. For the tldr crowd basically you have to use alsamixer manually mute and unmute the int_spkr channel for speaker audio and the int_mic channel to enable headphones. Then you can use the output and and hp to channels adjust volume for speaker and headphones respectively. It also might help to do a suspend resume cycle i sound still isn't working. Thanks to everyone else, hopefully others will find this useful as well.
Many thanks for your work!!! I'm using it on a nexus 7 with glass and touch broken (unuseless) but now it lives!!! and is a very responsive lxde desktop with xrdp starting on boot which I use with amule or bittorrent all night long...
two questions:
1) for me it does not work shutdown -r now or reboot... it close immediately all network connections but I have to keep power button 10 sec to restart system...
2) using it with an hub usb I'm trying to connect a big hard disk: pcmanfm (lxde file manager) refuse to mount it saying than it is not authorized... (I've followed archlinux wiki: it work on my archlinux desktop but not in nexus 7).
(I am new and cannot post in dev forum, that's why I posted this here. Still hope someone will be able to help.)
Is there a way to get crash-dumps out of Windows Phone 8 during development time? I am after a file that is dumped similarly to when a normal Win32 app crashes. Or similar to what is saved on iOS devices at crash to be investigated at a later point.
My question is specifically about somehow retrieving this (or similar) file/info from the phone after a crash without me having to do anything in my code e.g. manually writing the stack trace to a file from an unhandled exception.
I am aware the option of getting "live" crash reports from a beta-submitted app but that is not what I am after.
Thanks!
Can Visual Studio's debugger generate crash dumps? I'd expect so (I know windbg can, but I haven't managed to attach windbg to a phone app) and that would be the obvious approach.
Not sure why you want a dump when you can do live debugging, though...
GoodDayToDie said:
Can Visual Studio's debugger generate crash dumps? I'd expect so (I know windbg can, but I haven't managed to attach windbg to a phone app) and that would be the obvious approach.
Not sure why you want a dump when you can do live debugging, though...
Click to expand...
Click to collapse
Hmmm, I never thought of using windbg because that never came up as a tool that is used with WP8.. Will give it a try and see if I get anywhere.
I need a crash dump because the crash does not happen when a debugger is attached.
I am trying other options to catch the issue: isolating the code the crash might happen, dump the stack trace into a log file, but a crash log would be the most obvious place to look at and I am shocked that it is not possible or at least this hard.
There's a way on the ATIV S to get crash dumps (without even crazy hacks, I mean; it's a hidden option in the Diagnosis application) but I think they're only for the OS, not for individual apps.
A crash that only happens without the debugger attached is a very irritating sort of crash!
GoodDayToDie said:
There's a way on the ATIV S to get crash dumps (without even crazy hacks, I mean; it's a hidden option in the Diagnosis application) but I think they're only for the OS, not for individual apps.
A crash that only happens without the debugger attached is a very irritating sort of crash!
Click to expand...
Click to collapse
Amazing, I have access to an Ativ S device so will give a try! Thanks!
I have got a confirmation directly from Windows Phone team: what I am asking for is not possible at the moment.
I have provided them feedback on what kind of situation this can put some developers, I hope they will consider it and look into doing something about it.
In the meantime your options are to manually dump the stack trace (along with any info you want) from an unhandled exception or to upload your app for beta testing and check the crashlogs on the dashboard of your developer account.
Yeah, sorry. I should have mentioned that my approach is to always implement a custom unhandled exception function (there's a stub for it in App.xaml.cs) and either present an error message or write an error file. It's not a true crash dump, but it's often enough to help you find the spot where the problem occurred.
Hmm... I wonder how hard it would be to write a native component that would generate a crash dump on demand. I mean, it *should* be possible to do it, since you have raw pointer access and file I/O. I've just never tried.