CWM USB Audio Enabler - Nook Touch General

Flash the zip in CWM to enable USB Audio.
It works its just a bit tricky to get enabled. You may have to reboot the device to get it working.
Also if you have under 50% battery life the USB sound dongle will cut out. So make sure you have plenty of battery life.
MX Player works better playing videos then QQPlayer, but the sound with MKV files cuts out. On the QQPlayer the sound works fine.
The version of MX Player I tested was 1.7.40 for Froyo/Eclair.
Mediaserver doesn't work on the NST so any MP3s you add won't show up in Music players. To get around this use ES File Explorer built in music player to play local MP3s.

pinguy1982 said:
Flash the zip in CWM to enable USB Audio.
It works its just a bit tricky to get enabled. You may have to reboot the device a few times to get it working. Even when it is working I found that the sound in MX Player cuts out for a sec every 10 seconds.
Click to expand...
Click to collapse
What's going on under the hood here?
I'd like to get USB audio working on my system without using someone else's kernel, so if you could tell me what to change in mine, I'd thank you.
What other files, apps and such are necessary (so that I can add them by hand instead of flashing)?

ИΘΘK¡€ said:
What's going on under the hood here?
I'd like to get USB audio working on my system without using someone else's kernel, so if you could tell me what to change in mine, I'd thank you.
What other files, apps and such are necessary (so that I can add them by hand instead of flashing)?
Click to expand...
Click to collapse
Just unzip the package and have a look. The only thing that may not be obvious is you need to remove /system/lib/hw/alsa.zoom2.so
Apart from that you can see the files and apps that get added just by looking inside the zip.
The main files needed are:
/system/lib/hw/alsa.default.so
/system/etc/asound.conf
/system/app/UsbMode.apk this is the app that enables host mode. Needs SU to be able to run.
Plus the kernel.

pinguy1982 said:
Just unzip the package and have a look. The only thing that may not be obvious is you need to remove /system/lib/hw/alsa.zoom2.so
Apart from that you can see the files and apps that get added just by looking inside the zip.
Click to expand...
Click to collapse
Yes, thanks, I did that already.
I guess what I'm really asking is this: what do I need to add to my uImage and/or uRamdisk to allow USB audio? I'd prefer to just modify my kernel instead of overwrite it with a whole different one.

ИΘΘK¡€ said:
Yes, thanks, I did that already.
I guess what I'm really asking is this: what do I need to add to my uImage and/or uRamdisk to allow USB audio? I'd prefer to just modify my kernel instead of overwrite it with a whole different one.
Click to expand...
Click to collapse
Not sure where to get the audio sources for the kernel from. I just grabbed this: http://forum.xda-developers.com/showpost.php?p=43212551&postcount=164
It has everything I need.
FastScreen
MultiTouch
UsbHost
UsbToCom
UsbSound

@pinguy1982, here's the kernel I'm using: http://forum.xda-developers.com/noo...ultitouch-usbhost-files-t2846867/post54803848
The specific uRamdisk I have I also modded to mount /boot as read-write during the boot sequence, in case that matters.
The ideal thing for me to do would just be to add UsbSound to that kernel, if I can, and then release it for the Nook Touch Glow. I don't think I've seen an NTG UsbSound kernel yet, so that should be useful.
@Renate NST, can you help?

Just tested it with the your uRamdisk. It works fine. Haven't tested this with the Nook Touch Glow yet. So unsure if it works with it or not.

@ИΘΘK¡€ Here you go: http://forum.xda-developers.com/showpost.php?p=43860186&postcount=175
All the info is posted there.

Some apps didn't work with the sound so I have updated the USB-Sound package with a new sound engine.

pinguy1982 said:
Some apps didn't work with the sound so I have updated the USB-Sound package with a new sound engine.
Click to expand...
Click to collapse
Would you give me a quick run-down of the hardware required for USB sound and how to use it?

ИΘΘK¡€ said:
Would you give me a quick run-down of the hardware required for USB sound and how to use it?
Click to expand...
Click to collapse
Sure.
Hardware you need:
USB OTG cable. I have one of these so I can charge the device while I am using it.
USB Headset or a USB Audio Adapter (I own both and can confirm they work with the Nook).
Thats it.

pinguy1982 said:
Sure.
Hardware you need:
USB OTG cable.
USB Headset or a USB Audio Adapter.
Thats it.
Click to expand...
Click to collapse
Sweet, thanks! Now, all I need is to either find or make a Nook Touch Glow 1.2.1 kernel that has UsbSound included.
Can you help me with that?

ИΘΘK¡€ said:
Sweet, thanks! Now, all I need is to either find or make a Nook Touch Glow 1.2.1 kernel that has UsbSound included.
Can you help me with that?
Click to expand...
Click to collapse
@latuk is going to be the best person to speak to about that. But its gotta be easier getting his Kernel working with the Glow light then trying to build a kernel from scratch. His kernel has everything enabled already.

pinguy1982 said:
@latuk is going to be the best person to speak to about that. But its gotta be easier getting his Kernel working with the Glow light then trying to build a kernel from scratch. His kernel has everything enabled already.
Click to expand...
Click to collapse
Sounds like a good idea in theory, but @latuk has not been online at XDA in over a year. How would I get ahold of him?

@pinguy1982, okay, so I just tried the kernel from your .zip (just the uImage, not uRamdisk), and it appears to not have hosed by GlowLight after all! One thing I do ask, though - is this a 1.1.5 kernel? It appears to have removed proper functionality for NoRefresh, and since I have the 1.2.x test version, I thought perhaps the kernel downgraded me.

ИΘΘK¡€ said:
@pinguy1982, okay, so I just tried the kernel from your .zip (just the uImage, not uRamdisk), and it appears to not have hosed by GlowLight after all! One thing I do ask, though - is this a 1.1.5 kernel? It appears to have removed proper functionality for NoRefresh, and since I have the 1.2.x test version, I thought perhaps the kernel downgraded me.
Click to expand...
Click to collapse
Its based on 1.2.1

pinguy1982 said:
Its based on 1.2.1
Click to expand...
Click to collapse
Ah, I figured it out. It's FastScreen's fault.
I'm running the kernel as we speak, wih FastMode2 installed. I like it, but there don't seem to be any contrast settings. Got any tips?

ИΘΘK¡€ said:
Ah, I figured it out. It's FastScreen's fault.
I'm running the kernel as we speak, wih FastMode2 installed. I like it, but there don't seem to be any contrast settings. Got any tips?
Click to expand...
Click to collapse
FastMode2 doesn't have any contrast settings, but it shouldn't need it. The biggest issue with fastmode is with ghosting, but contrast wise it is far better then NoRefresh.

pinguy1982 said:
FastMode2 doesn't have any contrast settings, but it shouldn't need it. The biggest issue with fastmode is with ghosting, but contrast wise it is far better then NoRefresh.
Click to expand...
Click to collapse
Yeah, I've been noticing both items. Thankfully, ghosting hasn't been too terrible, but the contrast is, as you said, much better than NoRefresh.
Thanks for all your help - once I get my Sabrent External Sound Box USB-SBCV off Amazon (recommended by Renate, I believe), I should be in business for audio playback (and audio recording? is that also in this kernel?).

ИΘΘK¡€ said:
Yeah, I've been noticing both items. Thankfully, ghosting hasn't been too terrible, but the contrast is, as you said, much better than NoRefresh.
Thanks for all your help - once I get my Sabrent External Sound Box USB-SBCV off Amazon (recommended by Renate, I believe), I should be in business for audio playback (and audio recording? is that also in this kernel?).
Click to expand...
Click to collapse
Doubt it. I think the feature is kinda pointless on the NST. But if you want to enable audio recording the details are here: http://forum.xda-developers.com/showpost.php?p=43281985&postcount=374
But audio recording may work as is. I haven't tested it but as it has a new sound engine it might work (I ported part of it from the the NOOK Color v1.1.0)
I haven't modified the framework.jar though and I am pretty sure its not going to work until AudioRecord.smali has been modified.
By the way updated the USB-Audio package. It sounds really good now.

Related

it seems pocket player 4.1 is the only palyer that has no stuttering

Hey guys
I experienced audio stuttering with every player, but when I installed pocket player 4.1 all the stuttering disapeared.
any comments on this note
I would have to agree with you on that one. Although I'm having issues with adding my own podcasts from valid addresses not updating at all. And, I don't know how to delete the podcast entry and start over. Perplexing indeed!
got core player and its terrible for it. Real let down, bougth this phone for one of the big plusses of being able to plug head phones in. Is rediculas tbh.
8igdave said:
got core player and its terrible for it. Real let down, bougth this phone for one of the big plusses of being able to plug head phones in. Is rediculas tbh.
Click to expand...
Click to collapse
Might be because the built in equaliser is enabled. If I disable it and use something like Audio Booster instead Core Player is better than perfect.
custardo01 said:
Might be because the built in equaliser is enabled. If I disable it and use something like Audio Booster instead Core Player is better than perfect.
Click to expand...
Click to collapse
Its not enabled it really screws up the sound i find. are you runing version 1.3? im on 1.2
8igdave said:
Its not enabled it really screws up the sound i find. are you runing version 1.3? im on 1.2
Click to expand...
Click to collapse
I have the latest 1.3.2 but have also found success with earlier versions. What about preferences/audio/audio output=Wave Output or preferences/buffering/Preload for audio =64kb. Problem is there are so many options. I am sure it must be something in the preferences not set right. I don't use scan library at startt up option but prefer to select files direct from storage card or from a playlist file. My experience with WMP and HTC Audio manager is that library sorting always causes problems like pauses and skipping. Hope this may be of some help anyway.
custardo01 said:
I have the latest 1.3.2 but have also found success with earlier versions. What about preferences/audio/audio output=Wave Output or preferences/buffering/Preload for audio =64kb. Problem is there are so many options. I am sure it must be something in the preferences not set right. I don't use scan library at startt up option but prefer to select files direct from storage card or from a playlist file. My experience with WMP and HTC Audio manager is that library sorting always causes problems like pauses and skipping. Hope this may be of some help anyway.
Click to expand...
Click to collapse
I already have those options set thanks though, yaeh i suspect it hs something to do with library scan as when im looking through my songs, by scrolling thro them it causes music to skip like made. So i suspect there is a connection there.
Sadly it appears i am not alone at all:
Hi, this is a known issue with the hand set not coreplayer. See XDA Dev for details. This has not yet been fully solved but there are some improvments that can be made updating your ROM, drivers and Coreplayer to latest version.
Click to expand...
Click to collapse
From a post i did on core palyers forums to try get some answers:
http://forum.corecodec.com/viewtopic.php?f=4&t=2614
Someone had a fix for it somewehre i saw a logn tiemn ago, i dont know where it was. Might have been a differnt rom.
:EDIT:
Im going to see if douberling the buffer size to 128kb makes any difference.
increasign the buffer size does appear to have made some difference. Not sure its completely gone tho. I increased it further to 256kb, that smoothed it out a bit more. I may try 512kb
8igdave said:
increasign the buffer size does appear to have made some difference. Not sure its completely gone tho. I increased it further to 256kb, that smoothed it out a bit more. I may try 512kb
Click to expand...
Click to collapse
Sounds good. Will be interested to hear how that goes. I found it really bad at first and it did take a while to settle down. Pretty sure it helped putting the equaliser off. Now it is brilliant and would not be without it. Would using Audio Booster help at all? Not sure why it would help but just another thing I use without problems.

[FIX] Tnt mod based orientation fix for games

Weeds2000 fixed the orientation on our Folio100 to work with games like Asphalt5 and now its possible to play, although graphics are still kinda messed up. but other games like the 3d tilt works nearly perfect now too.
you might find it useful, and VEGAn mod might be able to include this as my FolioTntMod is based of the TNT framework...
Find the download patch i made for our folio in this thread.
it also include a full 360 rotation fix, if you need it
As we all share the same Tegra2 platform and can nearly swap experience here, im posting this to share the fixes weeds2000 made for us...
Hope you find it useful..
Note:
The patch i made might actually work fine as update.zip on your tablet as well, or might need minor adjust to install, but let g tablet modders fix this if needed.
at least now you know its available.
Thank you! One question - do you know what file(s) were altered for the 360 rotation fix? Was it a lib file, for example?
EDIT: Also, to any other modders looking at this, the system.img is a ext2 filesystem image, NOT a yaffs2 image.
roebeet said:
Thank you! One question - do you know what file(s) were altered for the 360 rotation fix? Was it a lib file, for example?
EDIT: Also, to any other modders looking at this, the system.img is a ext2 filesystem image, NOT a yaffs2 image.
Click to expand...
Click to collapse
Roeby wan Kanobi, is this something that could work and be added to TnT Lite? My Clockwork back up just completed
Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.
roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.
Click to expand...
Click to collapse
This could be another watershed update Also- with the accelerometer corrected, folks will be getting exercise by holding up the G while playing games
added:
Perhaps the one extra update that would be nice is a DSP manager so dB level or gain increases can be made. Modders released a DSP manager on the Incredible that allows increases to 3.5mm and speaker output. Hardware based EQ too.
Perhaps being too picky, but louder speakers would be nice.
Did you see.. they provided the SOURCE!!!!! This is what we need!
roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.
Click to expand...
Click to collapse
What does the patch change? Would is break things when the application developer fixes the orientation code in their game.
We saw this problem fixed in the application in the Gallery 3D application by google, not in framework. http://android-developers.blogspot.com/2010/09/one-screen-turn-deserves-another.html
roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Click to expand...
Click to collapse
okay here are some details.
the framework.jar modified comes from this file: update-smb_a1002-3338-user.zip
the library should be generic, but is required for the gsensor/rotation/orientation fix as part of the new framework.jar changes.
the 2 primary folders in the framework.jar changed are /android/hardware /android/view
you should be able to easily spot the differences in filesizes..
do note: there is another change android\os\Environment.smali as i modified it to work with /mnt/sdcard and /mnt/sdcard/sdcard-disk0 and /mnt/usbdisk-disk0 for compatibility with folio mount functionality.
here is the "vold" also different but works fine with the tap'n'tap framework.
remember that /etc/vold.fstab needs changed to support the more new mount devices if you wish to use that one too.
360 rotation fix is in android\view\WindowOrientationListener$SensorEventListenerImpl.smali
orientation fix is
android\hardware\SensorManager*.smali
but again, the framework.jar is Tap'n'Tap based, so works directly on top of r3338 edition.. and i made a patch in my section with just framework + lib files included.
rothnic said:
We saw this problem fixed in the application in the Gallery 3D application by google, not in framework. http://android-developers.blogspot.com/2010/09/one-screen-turn-deserves-another.html
Click to expand...
Click to collapse
No, as far as i understand, weeds2000 only made the hardware swap sensor reading, so now it acts like a portrait mobile phone, where our Tegra2 has the chip rotated once 90degree.
Dexter_nlb said:
No, as far as i understand, weeds2000 only made the hardware swap sensor reading, so now it acts like a portrait mobile phone, where our Tegra2 has the chip rotated once 90degree.
Click to expand...
Click to collapse
Hmm, so it does a 90 degree rotation. And the device is still a default landscape device. We definitely need to make sure there are no negative effects on games that utilize the acceleromether and worked fine before.
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.
Thanks for the explanation - this is something I suspected would fix it, but it's good to see that someone had pushed the idea all the way through to an actual fix.
So, I suspect that when the device boots up, it should be in portrait mode initially (until the sensor kicks in).
roebeet said:
So, I suspect that when the device boots up, it should be in portrait mode initially (until the sensor kicks in).
Click to expand...
Click to collapse
That makes more sense to me if that is true.
I read through the code ... Prior to the code change they were performing the rotation either for Acceleration minus Gy on the y-axis
or Acceleration minus Gz on the z-axis and NOT Acceleration minus Gx on the x-axis. Now the axis swap is always occurring... under all 3 conditions irregardless of sensor.
Dont know why there was an exclusion in the first place for Acceleration minus Gx on the x-axis...
When I get back I will look through the code some more...
rothnic said:
Hmm, so it does a 90 degree rotation. And the device is still a default landscape device. We definitely need to make sure there are no negative effects on games that utilize the acceleromether and worked fine before.
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.
Click to expand...
Click to collapse
rothnic said:
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.
Click to expand...
Click to collapse
if Google didn't "invent" the different way of reading sensors, there would only be one way of doing it, so developers would not be able to see it, so an update to like 2.2 or higher is now an requirement, right? but if older games do not check, it would work with them, so this fix solves it as i see it.
putting back androidos orientation handling to its original state, as many developers should be reading it.
I have ported the fix for both TnT stock and lite. As well as Vegan beta 4.
http://forum.xda-developers.com/showthread.php?t=892345
gojimi said:
I have ported the fix for both TnT stock and lite. As well as Vegan beta 4.
http://forum.xda-developers.com/showthread.php?t=892345
Click to expand...
Click to collapse
remember its all done by weeds2000 , i cannot/will not take credits for his effort here, i am just sharing the good work done on this fix.
I have released a new version of the fix, this should clean up all the remaining issues with the accelerometer/compass. Code is also much cleaner now. Some weird hacks you may have seen were caused by the legacy API which was used by my test game.
Only known issue up to now is that the mouse coordinates are also rotated.
The source can be found in the zip file attached to the original post, I hope that all changes are prefixed with // XXX:
The source files are based on the nvidia-froyo tree.
Link:
http://forum.xda-developers.com/showpost.php?p=10209624&postcount=38
Doodle jump doesn't work. Game loads upside-down with home buttons on top. If you tilt left you go right...Any fix for this?
Does this work for the VegaN Ginger Edition, or is that fix built into the ROM, I think I am having issues with some games on that ROM.
bmw4aaron said:
Doodle jump doesn't work. Game loads upside-down with home buttons on top. If you tilt left you go right...Any fix for this?
Click to expand...
Click to collapse
I think you can write the developer and tell , that the games is not working normally.. all other games work fine, so why would one game stand out, only reason, bad programming, or misunderstanding of androidOS and orientation. maybe developer thought he should fix the "orientation" in his game on tablet, and forgot other trying to make it reverse.. so: bad programming and choice of developer..he should follow guidelines and not his ideas.

Could Clockwork Mod 3.0.0.5 work on archos

i was wondering if we could do something like this on the archos?
http://forum.xda-developers.com/showthread.php?t=897612
And you are sure you have looked into the dev forum for gen8?
If we can compile an initramfs and a zimage from clockworkmod source, I don't see why not.
[email protected] said:
If we can compile an initramfs and a zimage from clockworkmod source, I don't see why not.
Click to expand...
Click to collapse
But we have the Sde already and we have a Multi Boot Menu
txtmikhail said:
i was wondering if we could do something like this on the archos?
http://forum.xda-developers.com/showthread.php?t=897612
Click to expand...
Click to collapse
Yes and no. $auron already has replicated some of the functions in his install script. The real question is why do we need CWM? You can backup/restore data directly on the device, or through ADB. You can install update zips by putting them in the UrukUpdate directory. Basically everything CWM does is already taken care of.
I use CWM on my HD2, so I do like it, but it's pointless on Archos, since they already give us the ability to dual-boot through their own Recovery menu.
Why all the people dont want to use SDE?
F*** the warrenty just be brave
I dont heard about anybody who soft bricked his Archos..
Okay, you're not understanding. The Archos AOS firmware and the Archos Bootloader are both encrypted. Even if you can decrypt them, you cannot change them, because they are signed, and the checksum is hardware-coded. Flashing the SDE adds a 3rd decrypted/unsigned boot image that can be flashed through the SDE menu.
Until someone cracks the boot signing and encryption, there can be NOTHING done to the Archos boot system without first flashing the SDE.
And trust me, there are MANY people working on that already, for almost a year.
P.S. How is your A70 useless because of Archos? Since the 2 latest firmware versions, it's been incredibly stable, and it does what's advertised. It even comes with Market now.
The boot loader was cracked see here But I don't think it's a very good option to use.
wdl1908 said:
The boot loader was cracked see here But I don't think it's a very good option to use.
Click to expand...
Click to collapse
Yeah, I know, I was following that thread, but I don't like it either. First off, someone needs to find a way to make that change with a reliable script, because you can't ask people to dd and hex edit the recovery block, or there will be bricks-a-plenty.
Second, I have yet to see someone compile a working AOS-format firmware file that works on Gen8. I stopped paying attention, but all the aos-tools only seemed to work with Gen7. Did someone find the AOS decryption code for Gen8?
msticninja said:
Second, I have yet to see someone compile a working AOS-format firmware file that works on Gen8.
Click to expand...
Click to collapse
This Is not very possible. You will need the private encryption key of archos.
msticninja said:
I stopped paying attention, but all the aos-tools only seemed to work with Gen7. Did someone find the AOS decryption code for Gen8?
Click to expand...
Click to collapse
I think the only thing that is missing to decrypt the aos file is the public keys that are used to verify the image files. They are stored in the flash somewhere we only need to find them.
wdl1908 said:
This Is not very possible. You will need the private encryption key of archos.
I think the only thing that is missing to decrypt the aos file is the public keys that are used to verify the image files. They are stored in the flash somewhere we only need to find them.
Click to expand...
Click to collapse
Then that's the next step to avoid the need for SDE, i suppose. Not like I don't already have the SDE watermark, but it would be nice to flash images through AOS instead of using the Developer menu.
Arobase40 said:
May be things are different with the 10" Tab, but with my 70IT it's far from being stable, whatever version I used : The Tab is laggy, the touchscreen is mostly jerky and "sticky" (Just scrolling the applications panel is a pain, as when I try to scroll to the bottom of the screen, I got unwanted apps launching), Most of the time I can't have wireless connexion, all bluetooth devices I have can't connect while they do instantly with the SGT, HDMI scrolling is also jerky and in blind mode, most USB storage devices don't work, ...
So I can't do Internet uses, nor Multimedia, except MP3 or Video playbacks IN LOCAL Mode after files transfer from a computer using the USB cable, and when the touchscreen allow me to select the correct files !!!
With the latest firmware I cant even not download any apps most of the time even if by any chance I got a connexion whether from Market or Applibs, for not reason... ^^ System is trying to download but got just stuck (not even a single byte), while I can browse (slowly but still)... ^^
So I have to find the apk from my laptop or with my SGT.
Click to expand...
Click to collapse
That certainly doesn't sound normal. Have you done a full system reformat and done a fresh install? Not saying it will fix it, but I have had times where it helped with hard-to-determine instability. Things like the wifi connection not working, bad touchscreen response, etc shouldn't be happening.
I believe you, I just know that most people with the A70 don't have those issues. I've even set up a few A70s and found it to be better than my A101, probably due to the lower screen resolution. In your case, it could even be bad hardware. If the SDcard controller fries and becomes unstable, the system can use 100% of the CPU cycles trying to keep up with the errors it will throw. Even the CPU can throttle itself if it's damaged, limiting your frequency, thus giving bad performance.
I hope you can get it figured out, or get it replaced/refunded, because I really do think the Gen8 devices were worth their price. I've had mine for 8 months and I've never regretted it. The Tab is probably a better tablet, but they weren't even close to market when I was deciding to get a tablet.
Arobase40 said:
Yeah, I did fresh reinstall twice and jus got the same issues.
Just for the touchscreen, it was responding more or less fine depending on the firmware version. So I guessed this is a OS issue. For the rest wifi, BT, HDMI or USB Host, it was the same whatever the version !!!
That's the reason, I wanted to do a dump backup and to restore older versions version just to figure out if this is a hardware issue or OS issue... ^^
And that's also the reason, I won't buy newer Tab when they are close to the market but will wait after some weeks or months before to decide. And test deeply them by myself, and not just at reading at web sites or blog tests !!!
I'm really attempted about the Asus Transformer or Slider, but I will wait again for a while... ^^
Click to expand...
Click to collapse
I would try to get it replaced if it was me. This forum would be very different if everybody had these problems. I know this is a stupid question, but is it actually an A70HT rebadged to say IT?
Arobase40 said:
Who knows ???
I was really too busy with my work, my other projects, private affairs, and testing my lovely new SGT with different firmwares...
But I'll get in touch with Archos, because this is really too much ass***
I can really certify you I'm not the sole persons having so much troubles, whether in France, in Canada, or UK, for what I have already noticed.
Click to expand...
Click to collapse
No, certainly not the only person with alot of troubles, but I truly feel that those people are louder, so you tend to think there's more of them.
Archos rushed to market, like they have for the past 15 years, and I think they started having component shortages, so some of the revisions ended up having unstable mixes of hardware. They probably even know that, and that may be why they've started replacing people's unstable ones as the demand dies.

franco.kernel ksatta changes pre-release

I will release my changes to the franco.kernel in this thread before franco includes them in his kernel for the upcoming releases. So this is a "pre-release" thread for franco.kernel, for the changes I'm making.
v2 (included in [16 SEP] franco.Kernel)
- Speakerphone echo fixed. Works with normal calls, not with Skype (or other voip apps probably). Skype still works like before, echo with speakerphone mode.
The fix can be disabled with
Code:
echo 0 > /sys/module/snd_soc_msm7kv2/parameters/speakerphone_echo_fix
You can post in this thread how it works. It always uses speaker_mono_tx instead of speaker dual mic broadside dev.
- Removed some logging from msm7x30.c (left there by Huawei. They must have a logging fetish or something )
mod_v1 (Included in [11 SEP] franco.Kernel)
- "Use phone's mic with headset"-feature is now user configurable.
By default uses phone's mic with headset/headphones/line-out. So if you want that, no configuration is needed.
To use headset's mic create a file called "10headsetswitch" in "/system/etc/init.d/" and paste the following to it:
"echo 0 > /sys/module/snd_soc_msm7kv2/parameters/headset_mic_switch"
Future plans
- Fix speakerphone echo in Skype. Investigate the volume problems (max. volume is too high, etc..).
Flashing instructions
- Boot to recovery
- install from zip
- choose francokernel_X_ksatta_vX.zip.
Notes for devs
The latest franco.kernel has logcat disabled by default, to enable it put this in .config:
Code:
CONFIG_ANDROID_LOGGER=y
To enable kernel debug messages (can be seen with dmesg):
Code:
git checkout 0c1adc36ed u8800-kernel/kernel/printk.c
NOTE: disable logging again before releasing anything, probably slows down the phone quite a bit when logging is on.
Credits
ksatta - use phone's mic with headset
stockwell - user config for headset mic setting
franciscofranco - the franco.kernel
Thanks
wmi543
genokolar
And everyone else if I forgot to mention someone.
Files
franco.kernel-sep11+ksatta_v2.zip - Zip file to flash phone.
franco.kernel-sep11+ksatta_v2-src.zip - V2 source for devs. msm7x30.c file is from u8800-kernel/sound/soc/msm. Also includes compiling instructions.
To make it set to using the phone mic at boot, save the following script into /system/etc/init.d/. Call it whatever you like just with a two digit number at the start (ie. 10headsetswitch)
Code:
echo 0 > /sys/module/snd_soc_msm7kv2/parameters/headset_mic_switch
As mentioned this is already configurable in Miui using x5 settings so you don't need to worry about making the script yourself but the voice quality might not be very good (will be fixed for the next version) unless you use the kernel attached from ksatta.
Please could explain how to install this kernel? Because I read the file that you have attache and in the end I finish like in the begginign without knowing how to do it.
Is only need to do by the recovery with the zip file ans what about the secund zip file the smaller one?
Sorry but Ian sure that I am not the only o w that is asking this.
Sent from my u8800 using XDA App
vlc_marcos said:
Please could explain how to install this kernel? Because I read the file that you have attache and in the end I finish like in the begginign without knowing how to do it.
Is only need to do by the recovery with the zip file ans what about the secund zip file the smaller one?
Sorry but Ian sure that I am not the only o w that is asking this.
Sent from my u8800 using XDA App
Click to expand...
Click to collapse
Yeah I was a bit unclear, sorry. To flash boot to recovery, install from zip and choose my zip.
edit: Updated first post, flashing instructions
ksatta said:
Yeah I was a bit unclear, sorry. To flash boot to recovery, install from zip and choose my zip.
Click to expand...
Click to collapse
Ok thanks. And for what is the small zip file?
So I will use in this last miui without any problems correct.
Will I get battery problems?
Sent from my u8800 using XDA App
vlc_marcos said:
Ok thanks. And for what is the small zip file?
So I will use in this last miui without any problems correct.
Will I get battery problems?
Sent from my u8800 using XDA App
Click to expand...
Click to collapse
Sigh man, I'm growing tired of your questions everywhere in every thread you can find. This is just my kernel compiled with a different file to make this "Use phone's mic with headset"-feature is now user configurable." avaliable.
No it won't take coffees for you, no it won't explode your device, no it won't turn it into an airplane and fly in circles above your head, and no it won't make you rich beyond imagining.
Sorry for the smallish OT ksatta, it ****s me reading stupid questions everywhere.
Very nice job like I told you before
franciscofranco said:
Sigh man, I'm growing tired of your questions everywhere in every thread you can find. This is just my kernel compiled with a different file to make this "Use phone's mic with headset"-feature is now user configurable." avaliable.
No it won't take coffees for you, no it won't explode your device, no it won't turn it into an airplane and fly in circles above your head, and no it won't make you rich beyond imagining.
Sorry for the smallish OT ksatta, it ****s me reading stupid questions everywhere.
Very nice job like I told you before
Click to expand...
Click to collapse
First of all Ian not from your family so stupidity is not in my genes. Secund if you are tired go to sleep.
I didn't ask to you, so you don't need to react like this. Don't be a small kid.
When I don't know I ask.
So Franco don't give me your ****y opinions when I don't ask for then.
Thanks
Sent from my u8800 using XDA App
franciscofranco said:
No it won't take coffees for you, no it won't explode your device, no it won't turn it into an airplane and fly in circles above your head, and no it won't make you rich beyond imagining.
Click to expand...
Click to collapse
I think it's a fair question, I was wondering why my phone wasn't making me coffee
vlc_marcos said:
Ok thanks. And for what is the small zip file?
So I will use in this last miui without any problems correct.
Will I get battery problems?
Click to expand...
Click to collapse
You can already do this in Miui, have been able to for a while. Flashing this version should make the voice quality better though.
Yeah, like franco said, the v1 is just user-configurability for the headset mic thing.
For anyone else wondering, I will report any changes I make in the first post. So the zips here won't have any other changes compared to franco.kernel, except the ones I report in the first post.
vlc_marcos said:
Ok thanks. And for what is the small zip file?
Click to expand...
Click to collapse
I updated the first post to be less confusing. the smaller file is only the source file, only needed by devs.
franciscofranco said:
Sigh man, I'm growing tired of your questions everywhere in every thread you can find. This is just my kernel compiled with a different file to make this "Use phone's mic with headset"-feature is now user configurable." avaliable.
No it won't take coffees for you, no it won't explode your device, no it won't turn it into an airplane and fly in circles above your head, and no it won't make you rich beyond imagining.
Sorry for the smallish OT ksatta, it ****s me reading stupid questions everywhere.
Very nice job like I told you before
Click to expand...
Click to collapse
Mate, you seriously need to get a grip and settle down. Maybe lay off the espresso a bit. I know you are doing good things with your kernel and everyone appreciates that and is grateful. However, almost every post you make is aggressive and condescending. Ok so you have it all figured out, that's great. But the majority of us are just struggling and muddling along enjoying Android and trying to learn and contribute as we go. When you attack and belittle most posters it just make you look like a wanker.
May I suggest: if you don't wish to assist then simply don't respond. Someone else will or maybe no one will in which case the post will recede into the past and the poster will look elsewhere.
Maybe you, or anybody here can write me pm with very short info how to compile kernel [what parrameters should pass to it] and make zip package to be installable to phone? Once i tried to compile but image was 2x times bigger than original realese so i was afraid to test it
GolfCranK said:
Mate, you seriously need to get a grip and settle down. Maybe lay off the espresso a bit....
Click to expand...
Click to collapse
it's PASSION man! Who wants to read nice post i want to read **** words man!
Tommixoft said:
Maybe you, or anybody here can write me pm with very short info how to compile kernel [what parrameters should pass to it] and make zip package to be installable to phone? Once i tried to compile but image was 2x times bigger than original realese so i was afraid to test it
Click to expand...
Click to collapse
Maybe you were looking at the uncompressed Image file? zImage is the correct file. But anyway the -src.zip contains compiling instructions, I created them today with a fresh install of Ubuntu 11.04. If you test my instructions and have any problems, inform me and I'll update the instructions.
Before you edited you asked about what v1 does, there's a whole lot of text in the first post, but yes, it only makes the headset mic switch user-configurable Future releases might have more changes
Actually my version uses phone's mic by default. I made it default because franco.kernel has been using phone's mic by default. So, to avoid confusion:
If you want to use headset's mic use "echo 0 > /sys/module/snd_soc_msm7kv2/parameters/headset_mic_switch" in the script.
If you want to use phone's mic, don't do anything
edit: This applies to the v1 kernel in this thread, miui uses headset's mic by default. Reason above.
Man, this kernel fixed the only issue I had with Oxygen, and call quality is even great! Now I won't change ROMS ever in the next months (unless Huawei releases official Gingerbread). I'm not gay but this is true, I LOVE YOU!!!!
ksatta said:
Maybe you were looking at the uncompressed Image file? zImage is the correct file. But anyway the -src.zip contains compiling instructions, I created them today with a fresh install of Ubuntu 11.04. If you test my instructions and have any problems, inform me and I'll update the instructions.
Before you edited you asked about what v1 does, there's a whole lot of text in the first post, but yes, it only makes the headset mic switch user-configurable Future releases might have more changes
Click to expand...
Click to collapse
MAN! Thanks! finally someone wrote how to properly compile. THANKS!! You're awesome
ksatta said:
Actually my version uses phone's mic by default. I made it default because franco.kernel has been using phone's mic by default. So, to avoid confusion:
If you want to use headset's mic use "echo 0 > /sys/module/snd_soc_msm7kv2/parameters/headset_mic_switch" in the script.
If you want to use phone's mic, don't do anything
edit: This applies to the v1 kernel in this thread, miui uses headset's mic by default. Reason above.
Click to expand...
Click to collapse
lol sorry I edited it now.
My theory about the speakerphone echo is that the audiolibs in 2.3 roms use the wrong routing. They're probably now using the same microphone dev. id. as normal mode, when they should be using the "speakerphone mic" dev.id.
I wasn't able to confirm this yet, didn't get my debug messages out of the kernel yet Normal logcat works, but the kernel debug messages don't show up in it. Also I couldn't find a syslog file.
But I'll continue another day.
Ksatta i see you good with freaking linux stuff and sound So can you make that recording audio and video - audio quality to be good not some arm ****?
I found that codec is here arch/arm/mach-msm/qdsp5v2/audio_amrnb.c How to make that system uses different codec or this but with better sample rate ant bit rate, i can change this in file but i can't find the specification of this codec so maybe it's not supporting 44.1Khz sample rate or even 16Khz.
Thanks ksatta for this ! Was exactly what needed. Btw instead of setting that init script couldn't just change the value from 1 to 0 or it is restored after every reboot?

[GUIDE] [ROOT] Get the best sound out of your Idol 3!

Hi y'all fellow Idol 3 users! And welcome to my guide which aims to help you make your phone sound exactly how you want it to.
Okay, so if you bought this phone, chances are you wanted a great media consumption experience, since this is the Alcatel Idol 3's strength. When I got the phone and first plugged my headphones in to test out all that JBL stuff they were advertising, I couldn't help it but feel let down. Yep. I found it sounded muddy, disorted and clicky. But since we are talking about android, I knew I could probably do something about that. Plus I KNEW the audio chip in this phone was great. So I started tweaking and I finally can say that my Idol 3 sounds like a beast.
Here are the steps, then!
1. Disable the JBL setting. First and foremost, please, pleeease... go to settings > sound and notifications and disable "JBL". Honestly, it just doesn't sound good. It introduces a LOT of disortion in exchange for a little bit of bass. They are much better ways to get bassier sound without hardly disorting it, trust me. I don't know what they were thinking... this setting just assassinates the music IMO. However you are free to do as you want, of course.
* For step 2, root is needed.
2. Install Viper4Android. The following steps will guide you through the installation of this godly piece of software. For you guys which don't know what Viper4Android is, it's one of the best sound engines (in my opinion the best) available for android. It originated in China where it became really popular. Installing Viper4Android will not alter the sound signature in any way, it will just unlock the true potential of your sound-related hardware, getting rid of bottlenecks that worsen audio quality. Just installing it WILL get you a better sound. However, it also provides lots of settings and tweaks to change the sound signature if you want to, and they work really well, unlike this JBL setting we were given. In order to install it, you can either follow my own instructions or head to the official V4A thread and follow the steps there.
2.1 Install Busybox. Download one of the many installers in the Play Store, open the app and click install. Reboot if it asks you to. You can safely delete the app afterwards.
2.2 Download the Viper4Android apk from the official site. Be sure to download ViPER4Android FX 2.3.4.0 which is the one that works with Lollipop.
2.3 Extract the zip and then pick the apk called "ViPER4Android_FX_A4.x.apk" and put it in your phone's storage, then install it.
2.4 Install the V4A driver. Open the app and it should prompt you to install the driver. Select "Audiophile quality" for the best sound quality. Even though it warns you about high cpu usage, I did not notice lags or battery drain. However if this worries you a lot you can always choose "high quality" instead, though I wouldn't recommend it. It will ask you to reboot your phone, do it.
2.5 Make it run along enforcing selinux. This mod normally wont work with enforcing selinux, so you can either change selinux to permissive mode or just flash this zip (by XDA member maximumentropy) through custom recovery, wich will make it work with enforcing selinux. I recommend the second method.
2.6 OPTIONAL STEP: In ViPER4Android's thread the instructions say you have to edit the next lines in the "build.prop" file, which is located in /system. Lines to edit:
Ipa.decode=true to lpa.decode=false
tunnel.decode=true to tunnel.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
I found that the second line was already set to false in my device. If you are not in stock rom you might not find this lines, if that's the case just ignore this step.
This step is optional because I used ViPER4Android for a few days without doing it and everything seemed to work. So if you prefer not to mess with the build.prop you can try without doing this.
2.7 Enable ViPER4Android. Open the app and you will find there are several tabs: "Headphones", "Speaker", "Bluetooth"... just activate the first checkbox in every tab if you want ViPER4Android working globally.
2.8 Turn off conflicting settings in some music players. Most player should work fine out of the box, but in some cases there are settings that conflict with V4A.
2.8.1 Poweramp: turn off EQ, tone and limiter. Go to settings > sound engine > advanced customization, and untick the first checkbox. The other settings didn't seem to conflict for me, but you can try disabling them too if you are having trouble to make it work (I have them all disabled).
This section needs expansion! Tell me how you made your favourite music player work with V4A.
2.9 Test it out! Play some music and open V4A. Click the dropdown menu and choose "Driver status". It should say:
NEON Enabled: Yes
Enabled: Yes
Status: Normal
Audio Format: Supported
Processing: Yes
If that's what you see, then contrats! Everything is set.
3. Grab a nice sounding music player. The consensus is that the one with the best quality is "Neutron Music Player". I do agree with this, however, the UI is really crappy and I just cannot cope with that scroll. That is why I use Poweramp, which also sounds nice, and has the addition of a nice little "punch" in the lower frequencies. If you know some other great sounding players be sure to comment below and tell so I can expand the guide!
4. Get a nice pair of headphones. The included ones by JBL do pretty well for the price they are valued at ($40) but that doesn't mean there aren't better choices out there! Also they didn't seem to fit comfortably in my ears with any of the sizes inlcuded. If you want something with a similar price and an even better sound, I recomend the Sony MH1C, a pair of IEMs you can get for $30 but sound like some good $100+ IEMs. If you want traditionally shaped headphones then my recommendaiton is the KOSS PortaPro (or the KSC75 wich are essentially the same but with a different form factor). They are also dirt cheap and have a very decent sound. For more recommendations you can ask me (though I am no expert) or just head to the Head-Fi forums. You won't get better advice anywhere else when concerning headphones! These guys really know their stuff.
Lastly, I hope this guide is of use to some of you and allows you to enjoy the Alcatel Idol 3 to the fullest. I wanted to contribute to this great device's community since I felt it diserves way more attention than it is getting. And by the way, english is not my first language, so please excuse any error I might have made!
FURTHER TWEAKING:
You will see that ViPER4Andoid has a lot of settings, especially if you select the "Expert" UI setting from the dropdown menu. If you want ideas and advice on using them, head over the the official V4A thread.
Thanks!!!
I use n7player. It produce nice sound with v4a combo plus convolver set on studer +1db updated. Also tried shuttle+ but n7 has nicer interface.
sent from Hell
Under cm12.1 do you need to disable "audiofx" before using v4a?
Attached is a flashable zip which should add the 3 lines mentioned in post #1 to the build.prop and remove any duplicates. The zip can be used to add ANY lines to the build.prop. You just add the lines to the tweaks.txt file inside the zip. I did not create the zip. I just modified it to put the 3 lines mentioned in there.
Code:
lpa.decode=false
tunnel.decode=false
lpa.use-stagefright=false
famewolf said:
Under cm12.1 do you need to disable "audiofx" before using v4a?
Click to expand...
Click to collapse
Flash the removable script from cm 12.1 thread. It's on first page. Then supersu, and then v4a.. That's how I managed to make it work.
sent from Hell
Nikola Jovanovic said:
Flash the removable script from cm 12.1 thread. It's on first page. Then supersu, and then v4a.. That's how I managed to make it work.
sent from Hell
Click to expand...
Click to collapse
You must mean a different "cm 12.1 thread" that unjustified dev's cause I don't see a "removable script".
Yes, I'm sorry. Here is the DL link https://www.androidfilehost.com/?fid=95916177934545546 and the thread is one for gapps in the first post of cm12.1 .
sent from Hell
famewolf said:
Under cm12.1 do you need to disable "audiofx" before using v4a?
Click to expand...
Click to collapse
Yes, you do have to disable Audio FX unless you want to try and use both with V4A in compatible mode. I wouldn't recommend it though.
Langsuir said:
Yes, you do have to disable Audio FX unless you want to try and use both with V4A in compatible mode. I wouldn't recommend it though.
Click to expand...
Click to collapse
Thanks for the guide..installed v4a tonight....seems to be working fine with spotify and bluetooth. I didn't use @Nikola Jovanovic's "cleaner" because it seemed to remove alot than just a few music apps...I used titanium backup to uninstall audiofx and I have n7player full installed (was free on amazon appstore)...haven't used it yet though.
It does, but really I don't see the reason to not apply it. Google cam is better than cm's, viper + n7 is better than apolo + audio fx.. So on, and so for..
sent from Hell
Nikola Jovanovic said:
It does, but really I don't see the reason to not apply it. Google cam is better than cm's, viper + n7 is better than apolo + audio fx.. So on, and so for..
sent from Hell
Click to expand...
Click to collapse
It seemed to be doing something with vending.apk which is the google play store...I didn't want to chance that getting deleted. I use google calendar and it looked like it might delete it as well...will have to research when I have time and maybe modify.
It may also be the cause of apps crashing, but haven't experienced any reboots as the other users.
GPS stays on your phone, it deletes aosp cal but I installed Google calendar for that purpose.
It would be awesome if you could modify it in that way so the bloatware is cleaned but all other core apps are intacted.
sent from Hell
What do you think about Phonograph? Is it a valid music player, speaking of audio quality?
I just finished installing. All works fine so far. Testing some settings but think it's an improvement over "stock"sound. I really like the jetAudio music player. Been using it for a long time and think it's one of the best out there.
Thanks !
Thanks!!
Thank you! Works amazing with PowerAmp and Sennheiser Momentum On-Ear. Thought that sound was amazing already but now It's 200% better!
Or if you don't want to root simply use DFX player.... ?
Envoyé de mon 6045Y en utilisant Tapatalk
Anyone still gets stuttering, even with this installed? This is problem that happens to me with every player I tried. The one that gives less stutters and skips remains jetAudio... Is it a Lollipop problem?
Can't flash selinux patch, help please?

Categories

Resources