Never mind some bugs but then it would be boring with getting any
Super work Technomancer and many thanks!
I was trying to be funny there. I cannot fix any upstream issues (issues related to how CyanogenMod works). So any browser lagginess, ui issues or usability not caused by galaxy tab or our screen resolution are beyond scope of what i am doing here which is porting CM7 to galaxy tab, not working on improving CM7 in general. I am not part of CM team and i cannot change anything in main cm tree. Porting CM7 is my hobby so I am working on it when I have free time. I am reading all the posts here and replying if i have anything relevant to say. If I dont reply to some post it is not because I dont like someone. It may be redundant or I may just have no time to reply.
Now about Bluetooth SCO (headset profile). It annoys me as much as anybody else in there and I will fix it when I will know how. Logcats are mildly helpful because I can easily replicate the problem here. it would be interesting if someone with galaxy s calss device running cm7 could verify bt sco works for them and compare logcats and dmesg from their device and the tab. bt sco should work the same for us and them.
Sent from my GT-P1000 using XDA App while sitting on the beach in Half Moon Bay trying to have "a life".
# ADDITIONAL_BUILD_PROPERTIES # ro.sf.lcd_density=200
somethinh happened today. suddenly my tab rebooted and the screen density has been reverted to original value, which i had previously set to 240 using the lcd density app.
so i use tha app to change the ld density value again, but it wont boot up properly and i have to shut it down (by press and hold the power button) and the next time restart the tab the screen density remains unchange.
Sent from my GT-P1000 using XDA Premium App
Could anyone running stock (or stockish) GB ROM dump the SDP records?
start adb shell
and please post the result here, one should be enough
Like this http://pastie.org/2060098
|Thread Tools||Search this Thread|