Develop Bugs

[Q] The TyTN II on Android...

First of all, I'd like to thank all the super-talented people on this board that have persevered and have managed to create and tweak these Android ports for our devices. You peeps truly are amazing! Never would I have imagined running Android on my nearly-ancient TyTN II, but now I can.
Now that the praise is out of the way...
Are there any (or are there any coming soon) Android ports that would allow for full functionality on my TyTN II and actually be stable? For example, USB connectivity doesn't appear to work. As soon as I connect it to my PC, it starts and stops continuously. The Bluetooth functionality seems to be present, but whenever I attempt to connect a headset to the device, it only recognizes it for music playing, not for calls or as a hands-free device. In addition, it doesn't matter whether I overclock or not, I'm still hounded by constant application crashes and it seems to get worse the longer the device is on. These things (at the least) are constants no matter which port I install.
Any ideas or suggestions?
In the end, I'm still very thankful for all the talent here at XDA and am amazed at all you've accomplished.
Thanx again.

I have had my old Tytn2 running Android fast and stable for weeks now - details in my sig. Edit the nbh for Kaiser and your panel then you just need to do two extra things:
1. Run the wifi fix
2. Get hold of an app called SD Dual Mount for USB mass storage.
Not sure about BT. I don't use it on mine.
Like you I am in total awe of these guys getting Android working so well on our ancient devices.

u can run it but its not going to be as stable as a native android phone i dont think...

Eventually it will be.

So, nothing right now to stabilize and utilize the full functionality of a BlueTooth headset? Thanx again.

Question... is the 2.6.25 supposed to be better than the 2.6.32 ??

daedric said:
Question... is the 2.6.25 supposed to be better than the 2.6.32 ??
Click to expand...
Click to collapse
Nope, they are the same as linux kernels just ported to our phones. .25 is almost two years old lol. It is stable though as it is more developed for our kaiser.

aceoyame said:
Nope, they are the same as linux kernels just ported to our phones. .25 is almost two years old lol. It is stable though as it is more developed for our kaiser.
Click to expand...
Click to collapse
What will i miss on using the .25 ? and what will i gain?
I've seen things like "2.6.25 users get the wifi patch here"
So we need a patch for wifi ?

daedric said:
What will i miss on using the .25 ? and what will i gain?
I've seen things like "2.6.25 users get the wifi patch here"
So we need a patch for wifi ?
Click to expand...
Click to collapse
yup there's a patch 4 wifi... but yaffs arent implemented over .25 right? couldnt that be intetesting????
Sent from my Full Android on Vogue using XDA App

Personally I'd go with .32 at this point. .25 isn't any more stable on my phone as far as crashes and lockups are concerned. And data loss issues with .32 seem to be mostly ironed out (I would still keep a /data backup in case tho).
Plus the performance increase from .25 to .32 is well worth it.

albertorodast2007 said:
yup there's a patch 4 wifi... but yaffs arent implemented over .25 right? couldnt that be intetesting????
Sent from my Full Android on Vogue using XDA App
Click to expand...
Click to collapse
Yaffs is implemented in the latest .25 kernel.

stmasi said:
So, nothing right now to stabilize and utilize the full functionality of a BlueTooth headset? Thanx again.
Click to expand...
Click to collapse
Bluetooth headset and stereo both work for me with Fresh Froyo, ever since Kallt-kaffe posted a fix for the permissions of one of the files.
daedric said:
Question... is the 2.6.25 supposed to be better than the 2.6.32 ??
Click to expand...
Click to collapse
32 is probably better at this point. For quite a while, 2.6.25 would survive crashes better, but I think they're pretty much equal now in that regard. The 25 branch doesn't get attention of developers anymore.

Not to mention the .25 kernel is right about 2 years old now.

aceoyame said:
Not to mention the .25 kernel is right about 2 years old now.
Click to expand...
Click to collapse
Don't be like that! My girl is perhaps 24 yo (i really don't know) and its still good to go

daedric said:
Don't be like that! My girl is perhaps 24 yo (i really don't know) and its still good to go
Click to expand...
Click to collapse
LOL, but kernels (and software generally) ARE NOT like wine and cheese daedric.... if that would be the case... all of us we would be windows 3.0

albertorodast2007 said:
LOL, but kernels (and software generally) ARE NOT like wine and cheese daedric.... if that would be the case... all of us we would be windows 3.0
Click to expand...
Click to collapse
Ok, i'll agree with you. Yet... i rather have a .25 working good, than a .32 faulty.
Yet... as mentioned before, they're more or less on the same quality as of this posting...

kernel update
sorry for dummies question, but...
I have tytn ii as all of you, and have same bug with all 3 versions of Android setuped on it.
The microphone not working at least, so when i call somebody, i hear him, but he isn't hear me.
All other, include wifi, internet working good.
I found that it's well-known bug, and kernel version change could help.
But how to change it?
All versions i downloaded, based on 2.6.25, it's 2.6.25-01106-g50cf5f2-dirty on my device.
I found zImage file 2.6.32 but when i change zImage in andboot and restart - it's don't help.
i found NBH file for tytn ii ( kaisimg-panel2-240x320-2.6.32-tilt-froyo-09-09-10_21.nbh) , but how to install it?
Pls help!

Try one of these:
http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel-release.git;a=tree
If ur having problems look for a guy named l1qu1d, look at his signature it says something bout "atools" click on it and follow the guide....
Sent from my Kaiser.

I have already found zImage and nbh-file as well on that link, but the question is - how to install it?
as i understood atools working under Mac only, but i have Win7 on my PC.

krava1209 said:
I have already found zImage and nbh-file as well on that link, but the question is - how to install it?
as i understood atools working under Mac only, but i have Win7 on my PC.
Click to expand...
Click to collapse
its written in python. works with all os's as long as you have python installed.

[FIXED] Compass not working in GingerBread rom's

Hello,
I have been trying out some GB roms lately and during the testing i saw that the compass was not showing north anymore.
If i turn the phone a little, the compass is swaying somewhere between NE and NW, but it never points north.
So i went back to FroYo roms, but now i have it there also.
I have been reading several messages fro different GB roms that people are having the same problem.
I also used the recommended radio's for the GB roms.
Since my AuraxTSense (FroYo) rom now also has this problem, it looks like a radio problem.
Can someone confirm this problem and tell me the solution or tell me the radio that is working?
Eric
Edit: See my post on page 2. There is a snq kernel fix for this problem.

Well, i have been testing some further.
Radios (old or new) make no difference.
Froyo rom (Aurax 8.4) and recalibrating the compass the old way, did make it work again.
Installing a new rom (GingerBread that is) and everything was wrong again. The radio version did not make any difference.
So i'm going back to Aurax and hope that i can recalibrate it again to let it work.
For other's with this problem:
Try the old way of calibrating the compass.
Make at least 2 figures 8, but do it slowly. It should take at least 2 seconds for every 8 you make.
Then turn the phone around 360 degrees along the length axe of the phone, also at least 2 times and 2 seconds per turn
Then turn 360 degrees along the sides axe (width), also at least 2 times and 2 seconds per turn.
If this did not work, repeat the last 2 ways of turning (length and width axe) but do it faster and about 6 to 8 times per direction.
This worked for me (and i hope it will work again in a few minutes).
Eric

Looks like North is up and South is down. The compass is now a "bubble" app.

MrXimi said:
Looks like North is up and South is down. The compass is now a "bubble" app.
Click to expand...
Click to collapse
I read a few days back that some Chinese Rom's had fixed it (HiAPK or something like that), but i just read that they also still have this problem.
So i will have to wait untill this is really fixed, because i need the compass for finding directions etc.

it seems to be a general gingerbread problem, other devices are affected too:
http://www.youtube.com/watch?v=l-9lehX8u2U
http://www.google.pn/support/forum/p/Google Mobile/thread?tid=07d4eaf9686b664e&hl=en

It is a general Ginger problem..we can nothing do about it but...waiting for fix

I opened a bug report on android's bug tracker, I encourage everyone who has this issue to confirm it so it will be fixed.
http://code.google.com/p/android/issues/detail?id=16741

I added my comments also.
Sent from my HTC Desire using XDA App

supposedly this fixes the problem on GbB as well but I havent tried it yet and don't feel much like flashing a GB rom and having to go back again to froyo if ot doesnt work:
http://forum.xda-developers.com/attachment.php?attachmentid=425776&d=1287930092

godutch said:
supposedly this fixes the problem on GbB as well but I havent tried it yet and don't feel much like flashing a GB rom and having to go back again to froyo if ot doesnt work:
http://forum.xda-developers.com/attachment.php?attachmentid=425776&d=1287930092
Click to expand...
Click to collapse
In the RCmix S thread there was somebody who had tried it.
In GB most of the files are not found.
The fix is for Froyo and not GB.
The guy (i think) reported that it did not work at all.
We will have to wait for some other solution.

godutch said:
I opened a bug report on android's bug tracker, I encourage everyone who has this issue to confirm it so it will be fixed.
http://code.google.com/p/android/issues/detail?id=16741
Click to expand...
Click to collapse
Confirmed

godutch said:
i opened a bug report on android's bug tracker, i encourage everyone who has this issue to confirm it so it will be fixed.
confirmed... Thnx
Click to expand...
Click to collapse

Compass fixed with new kernel
Since yesterday there is a fix for the Compass problem in the GB rom's
It is a new kernel from snq and works for (at least) most GB rom's and probably all GB rom's.
I have not had time to try it, but in most rom threads there are people who have tried it and it works!!!!!
The fix can be found here:
http://forum.xda-developers.com/showthread.php?t=1039004
If you want the flashable version, you can find it on the line with this text (on the previous page link):
download: zImage-v05 (flashable v04-to-v05 kernel image update package here)
Click to expand...
Click to collapse
or click on the link below:
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1039004&v=1&libid=1306265553578&out=http%3A%2F%2Fdl.dropbox.com%2Fu%2F13432479%2Fmsm-2.6.35-bravo-GB%2Fg308ba26%2Fv04_to_v05-img-upd-flash.zip&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D628%26order%3Ddesc%26page%3D2&title=%5BKERNEL%5D%5BGB%2FSENSE%5D%202.6.35.10%20%5Bv05%5D%20%7C%20OC1152%20%7C%20LZMA%20%7C%20COMPASS%20%7C%20fixes%20%2Baddtl%20modules%20-%20xda-developers&txt=here
Have fun with it. I will when i have time to flash it

Confirmed working btw, got it in my ROM and it's fine

Yeah, works for me too. Using latest leedroid.

sorry. wrong post.
~renzs

Working on Nexus S
Hello,
is this fix working on Nexus S, too?

So, is this fix going to be incorporated into the official Acer releases (prob not)?
I guess we have to root and flash after market roms to fix their fubars...

2.3.4 MMS Question for AOSP Roms

No rush but was curious if any developer's were getting close to fix with the pic download mms for the 2.3.4 roms ?

Its getting close with nightly 72...hopefully in the next nightly.

mrjaydee82 said:
No rush but was curious if any developer's were getting close to fix with the pic download mms for the 2.3.4 roms ?
Click to expand...
Click to collapse
asking for ETA's is a major no no ... but i agree im waiting on a fix myself

mrjaydee82 said:
No rush but was curious if any developer's were getting close to fix with the pic download mms for the 2.3.4 roms ?
Click to expand...
Click to collapse
simple answer is that you'll see a bunch of posts when it's fixed, it's being actively worked on but it's not a simple fix

In very much layman's terms, can anyone explain how something like this gets broken? Why does it work in one version and then not in the next? Thanks!

Different phones use different settings and different servers. Different networks use totally different ways of handling messages.

thanamesjames said:
In very much layman's terms, can anyone explain how something like this gets broken? Why does it work in one version and then not in the next? Thanks!
Click to expand...
Click to collapse
dabbill said:
Different phones use different settings and different servers. Different networks use totally different ways of handling messages.
Click to expand...
Click to collapse
that, and that code gets re-written, updated, etc.
something gets updated or fixed, and some other thing could break because of it... what I do know is that CM is a community project, with amazing devs, and they are dealing with cutting edge software. we gotta remember that 2.3.4 is only (officially) on two phones right now, the Nexus One and Nexus S, both Google phones.

Someone posted a fix on the nightlies thread: MMS Fix Here

[Q] After 10.1-20130226 - Nightly Hercules phone call problems.

Hey Guys,
I've been reading of a forum to this problem I've been having with any Cyannogenmod after 10.1-20130226. There seems to be this problem where when I make or receive a call, I can't hear anything but the other party can hear me talking. I've kept updating to newer and newer versions only to figure out all of them have this problem, and that the last working one is the 10.1-20130226 version. Is there something the devs messed up on?
This is of course for the SGH II T989.
And here's the link with other people with the same problem:
This is on the forum for cyannogen mod. copy and paste it into the forums.
topic/69560-101-20130302-nightly-phone-calling-is-broken/
If anyone knows a solution to this, that will be great, otherwise I have to stick with this version till the newest update fixes that problem.

mikloish said:
Hey Guys,
I've been reading of a forum to this problem I've been having with any Cyannogenmod after 10.1-20130226. There seems to be this problem where when I make or receive a call, I can't hear anything but the other party can hear me talking. I've kept updating to newer and newer versions only to figure out all of them have this problem, and that the last working one is the 10.1-20130226 version. Is there something the devs messed up on?
This is of course for the SGH II T989.
And here's the link with other people with the same problem:
This is on the forum for cyannogen mod. copy and paste it into the forums.
topic/69560-101-20130302-nightly-phone-calling-is-broken/
If anyone knows a solution to this, that will be great, otherwise I have to stick with this version till the newest update fixes that problem.
Click to expand...
Click to collapse
There's also about 10 threads here too. Same fix for everyone. Flash a different kernel, or a different ROM. Cerux kernel fixed it for me. It's in the development forum.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Could someone please tell me the most stable 4.1.2 rom?

Need to know for a little experiment I wanna try.
Sent from my SGH-I927 using xda premium

Pacman or cm10 both by dman who is in fact da man !
Sent from my SGH-I927 using xda app-developers app

They seem like there's too many problems with them.
Sent from my SGH-I927 using xda premium

There's a thread reporting current bugs.
Those bugs are still important but I can say that these ROMs already work very good.
Thanks to dman for original work and, lately, to spyke555 and kick who are really doing an excellent job (development was almost dead before they committed and i'm very thankful to them for what they are doing).

I've seen the current bug thread but it's for 4.2.2 I need 4.1.2
Sent from my SGH-I927 using xda premium

spitfire2425 said:
I've seen the current bug thread but it's for 4.2.2 I need 4.1.2
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
He already answered your question, the 4.1.2 weren't ever completed, they were abandoned... hence why the issues in those roms are still present.
Install PACRom 18.2 and then apply the fixes for keyboard etc. I think the fixes are in the litekernel thread. Put on the latest litekernel for 4.1 keyboard fix, lights fix and you'll have the best working 4.1.2.
Note - skype and bluetooth headset still won't work, pretty sure the camera issue with rotation is still present. I ran pacrom 18.2 for MONTHS without any issue except those listed and the wake lag.

I was trying to port something, not use it as a rom.
Sent from my SGH-I927 using xda premium

GPS and other features
Uhm is any STABLE release with:
GPS Working (most important)
MUSIC Working
Skype Working
Camera Working
Google Now Working (this seems to be an issue from all custom Roms)
Since I've seen most these features working but none on the same ROM all together

myxoh said:
Uhm is any STABLE release with:
GPS Working (most important)
MUSIC Working
Skype Working
Camera Working
Google Now Working (this seems to be an issue from all custom Roms)
Since I've seen most these features working but none on the same ROM all together
Click to expand...
Click to collapse
Not for version 4.1.2 (jellybean)
Only ICS 4.0.xxx ...
****, somebody needs to make a sticky for the most current stable rom .. this question keeps coming up over and over and over in every forum and many threads.

myxoh said:
GPS Working (most important)
Click to expand...
Click to collapse
GPS has always worked. Some of the technical data returned is invalid/bogus but Google Maps/Navigation is completely unaffected.
MUSIC Working
Click to expand...
Click to collapse
Again, it's always worked, so long as you don't have an app trying to record audio at the same time.
Skype Working
Click to expand...
Click to collapse
Skype works for text messages, but received audio in calls is corrupt. The core of the issue is audio playback breaks when an app opens the microphone. (Ironically, the microphone itself actually works fine, i.e. voice recognition has messed up audio cues but it does process what you say correctly.) Current hypothesis is it's a driver issue. Research is ongoing. This is a longstanding issue going all the way back to our very first JB kernels.
Camera Working
Click to expand...
Click to collapse
Current CM10.1 and derivatives have a fully working camera.
Google Now Working (this seems to be an issue from all custom Roms)
Click to expand...
Click to collapse
This is actually a known problem with Google Now itself, it depends on an instruction set the Tegra 2 doesn't have. The Galaxy R and the Galaxy Note 10.1 have the same problem, on ALL Jellybean ROMs, even official. Bug Google, not us.
There is a workaround: downgrade GNow to a working version (possibly by flashing old gapps), then disable "Hotword detection" in settings. Once that is turned off you can upgrade to the latest and it will still work.

Thanks for the reply
roothorick said:
GPS has always worked. Some of the technical data returned is invalid/bogus but Google Maps/Navigation is completely unaffected.
Again, it's always worked, so long as you don't have an app trying to record audio at the same time.
Skype works for text messages, but received audio in calls is corrupt. The core of the issue is audio playback breaks when an app opens the microphone. (Ironically, the microphone itself actually works fine, i.e. voice recognition has messed up audio cues but it does process what you say correctly.) Current hypothesis is it's a driver issue. Research is ongoing. This is a longstanding issue going all the way back to our very first JB kernels.
Current CM10.1 and derivatives have a fully working camera.
This is actually a known problem with Google Now itself, it depends on an instruction set the Tegra 2 doesn't have. The Galaxy R and the Galaxy Note 10.1 have the same problem, on ALL Jellybean ROMs, even official. Bug Google, not us.
There is a workaround: downgrade GNow to a working version (possibly by flashing old gapps), then disable "Hotword detection" in settings. Once that is turned off you can upgrade to the latest and it will still work.
Click to expand...
Click to collapse
Thanks for the reply but:
1) GPS was not locking for me until I changed the gps.conf file in MOST of the ROMs I've tested.
2) Music didn't work on one rom I tested (now and then the music player started lagging and it automatically stopped every few seconds for a few milliseconds)
3)Thanks for the Skype reply; I was hoping there was some version with this fixed but evidentely not.
4)Camera flips orientation in all the roms I've tested. HDR just worked in 1 of them. Camera actually crashed from time to time in one of them.
5)Oh, sad about the Google Now fact. It's actually one of the main reasons I wanted JB
The skype thing Can't be a hardware issue since I've used skype several times before rooting my device. The issue you are talking about happens on google voice sometimes; therefore I'm guessing you're right on thinking that the problem is on the driver.
I'm very interested in ROM building since I'm an app developer for android and a C++ programmer; yet I've been too lazy to check how it worked. Are the drivers we are using open source? or are we just messing with the conf files trying to get things fixed?

myxoh said:
Thanks for the reply but:
1) GPS was not locking for me until I changed the gps.conf file in MOST of the ROMs I've tested.
2) Music didn't work on one rom I tested (now and then the music player started lagging and it automatically stopped every few seconds for a few milliseconds)
3)Thanks for the Skype reply; I was hoping there was some version with this fixed but evidentely not.
4)Camera flips orientation in all the roms I've tested. HDR just worked in 1 of them. Camera actually crashed from time to time in one of them.
5)Oh, sad about the Google Now fact. It's actually one of the main reasons I wanted JB
The skype thing Can't be a hardware issue since I've used skype several times before rooting my device. The issue you are talking about happens on google voice sometimes; therefore I'm guessing you're right on thinking that the problem is on the driver.
I'm very interested in ROM building since I'm an app developer for android and a C++ programmer; yet I've been too lazy to check how it worked. Are the drivers we are using open source? or are we just messing with the conf files trying to get things fixed?
Click to expand...
Click to collapse
hi,
thread how to compile from source:
http://forum.xda-developers.com/showthread.php?t=2071542
AFAIK drivers are not open source if they were there wouldn't be so much problems with them. They are ported from other devices similar hw but with code for them.

any news about JB and bluetooth headset issue?
this is the only thing that's been holding me back so far

myxoh said:
Uhm is any STABLE release with:
(...)
Click to expand...
Click to collapse
Where to find this "Uhm"? It was not listed here: http://forum.xda-developers.com/showthread.php?t=1621350