Related
I have been working on getting vanilla android to work on the Tattoo as I am not a big fan of all the modifications that HTC have done to their rom.
I am now launching the first usable version of the rom.
Phone calls and sms work, so does wifi, camera, gps and sensors.( thanks to fyodor)
Camera works only in android 1.6 I'll try it in 1.5 latter on today.
All aplications work.
Bluetooth and fm radio aren't working yet.
For the next release I'll be focusing on getting bluetooth to work.
The rom comes in two flavours :
ANDROID 1.5
ANDROID 1.6
lgstoian said:
I have been trying to get normal android 1.6 working on the tattoo.
I'm not a great fan of all the htc modifications.
So I have managed to build a rom that boots into vanilla 1.6 but I'm having trouble with the touch screen calibration. I may be doing the init.rc modifcation incorectly.
Code:
137
Click to expand...
Click to collapse
this should be 120 i guess... try it & let us know what is the result....
They are the same modifications to init.rc that worked for the 2.1 rom but have no effect what so ever for 1.6 .
I might be missing something. I extract the boot.img and I add that line to the end of the init.rc file. Should I be doing something else too?
I'll try with 120 once I'm sure I'm editing it corectly.
lgstoian...if you will port a normal donut on our tattoo without htc build i will love you forever!
lgstoian said:
I have been trying to get normal android 1.6 working on the tattoo.
I'm not a great fan of all the htc modifications.
So I have managed to build a rom that boots into vanilla 1.6 but I'm having trouble with the touch screen calibration. I may be doing the init.rc modifcation incorectly.
Code:
# write Calibration for Tattoo
write /sys/class/input/input1/calibration 8
write /sys/class/input/input1/calibration_points 55,850,173,855,515,493,851,132,166,137
Here is version 0.001. mirror
Test it at your own risk.
I'm open to any help and ideas.
Click to expand...
Click to collapse
That whould be great.
I'm have the same thoughs has you, concerning to the HTC stuff...
Whouldn't be more easy to reverse the offcial rom?
cheers
cat /sys/class/input/input1/calibration_points
824,855,206,865,509,502,826,139,201,142
Click to expand...
Click to collapse
You could start with the values from the stock HTC rom
Thanks mainfram3. Just got touchscreen to work.
I'm uploading now version 0.002.
So it seems that camera doesn't work, wifi, bluetooth and gps.
I suspect some would be fixed in the build.prop maybe someone else can check it out too. I'm calling it a night.
The rom feels very fast and finally a grey task bar.
Take it for a spin and see how it goes.
something new??
To fix WiFi you need to compile the proper driver against your kernel source or use HTCs kernel + their wlan.ko.
For bluetooth take a look at the files in /system/etc.
And gps is related to libgps.so
I am using the HTC kernel + their wlan.ko and I'm still not getting any results.
Call and sms works??
Yah they do work.
Keep the good work..
Cheers
great job!! Hope to have a full working ROM soon
where can we get information about including drivers into vanilla android ROM?
please help this man! we want a working vanilla rom for Tattoo!
I'm still stuck at getting wireless to work. I even got android 1.5 and 1.1 working on the tattoo just for fun.
lgstoian said:
I'm still stuck at getting wireless to work. I even got android 1.5 and 1.1 working on the tattoo just for fun.
Click to expand...
Click to collapse
Good...yeah..it's fun
Can you post the 1.5 rom??In that rom work everything??
Thank you
I just finished uploading the 1.5 rom. It has working wifi. I'm now working on getting wifi to work on 1.6 too and I'll upload that one later during the day.
Is 1.6 rom fully working?
Camera, gps, bluetooth and accelerometer aren't working yet.
Any help in getting them to work is highly wellcomed.
Hi I´m sure most of you are aware of this problem, the unstable fps after 2.1 update I installed the dexter froyo rom hoping i would finally be able to fix this issue but to my surprise the problem remains.
I´m aware that changing the governor on set cpu from on demand to performance it helps a bit but i still see the stuttering playing mostly emulators !
I´m running at 800 mhz and I still have drops from 60 to 40 fps constantly.
Is there a fix for this that i´m not aware of ?
Pls help !
Motorola is aware of the problem. I think, it's a kernel related thing, but i don't know exactly. The fact, that the framerate dropped, is known so far:
There's also a thread at motorola discussion boards:
http://community.developer.motorola...-Milestone-2-1BUG-major-2D-slowdown/td-p/5719
So, the thing is known. And it was promised to be fixed with froyo. but it seems not to be fixed i don't get any solution for now. i'm searching a few days also now.
yeah i was aware of that post and the being investigated situation by motorola ..... motorola europe does a lot of research but real work not really ...
the new update of 2.1 that is currently rolling out fixes this problem??????
kniffo80 said:
Motorola is aware of the problem. I think, it's a kernel related thing, but i don't know exactly. The fact, that the framerate dropped, is known so far:
There's also a thread at motorola discussion boards:
http://community.developer.motorola...-Milestone-2-1BUG-major-2D-slowdown/td-p/5719
So, the thing is known. And it was promised to be fixed with froyo. but it seems not to be fixed i don't get any solution for now. i'm searching a few days also now.
Click to expand...
Click to collapse
Thats because we can only use the 2.1 Kernel at the moment.
I´d rather use the 2.01 since i could play most emulators perfect ....
Is there any way to downgrade it using open recovery ?
mousiope said:
I´d rather use the 2.01 since i could play most emulators perfect ....
Is there any way to downgrade it using open recovery ?
Click to expand...
Click to collapse
you may downgrade your phone to 2.0.1 flashing a full sbf file from here (e.g.)
http://and-developers.com/sbf:milestone
remember to use a FULL sbf not a service sbf.
I tried it yesterday and my 2.0.1 milestone gives me at stock 60 FPS with fps2d!!! dexter's frenzy is not fixing this problem
kniffo80 said:
Motorola is aware of the problem. I think, it's a kernel related thing, but i don't know exactly. The fact, that the framerate dropped, is known so far:
There's also a thread at motorola discussion boards:
http://community.developer.motorola...-Milestone-2-1BUG-major-2D-slowdown/td-p/5719
So, the thing is known. And it was promised to be fixed with froyo. but it seems not to be fixed i don't get any solution for now. i'm searching a few days also now.
Click to expand...
Click to collapse
bad link? (10 chars)
The link is not broken, works fine for me
Another link to Google Code: http://code.google.com/p/android/issues/detail?id=7520 i've bumped the thread. perhaps, someone can tell us, what has been changed to fix the 30 FPS issue and i HOPE this is not a motorola kernel fix (some module changes) - cause 2.0.1 and 2.1 use both 2.6.29 kernel.
EDIT: @silico: no, it should not pend on the kernel. i just flashed my milestone with 2.0.1 and after flashing that fresh full sbf (with 2.0.1 kernel) i restored nandroid frenzy v 0.5 (which is not changing the kernel at all) and ran into the same problem: after restoring dexter's frenzy, the framerate dropped again to 30 FPS on stock clock!
here is a patch library which might work fine on regular stock firmwares too, but its not tested much..but results are 60fps+ now even on 550mhz
update-script fixed
kniffo80 said:
The link is not broken, works fine for me
Another link to Google Code: http://code.google.com/p/android/issues/detail?id=7520 i've bumped the thread. perhaps, someone can tell us, what has been changed to fix the 30 FPS issue and i HOPE this is not a motorola kernel fix (some module changes) - cause 2.0.1 and 2.1 use both 2.6.29 kernel.
They use the same kernel ? Where did you saw that?
I´m using the GOt´s modified sbf for uk and the problem remains !
If I downgrade the sbf to 2.01 i gain the stability for the 60 fps but what are the disavantages of using 2.01 ?
And you also say after using 2.01 sbf and recovering moto frenzy image you went back to 30 fps, so where is the problem in the kernel or in the image ?????
If you are using motofrenzy image now if you downgrade to 2.01 after the image is already in use the problem remains???
Thanks dexter for the reply ! Are u gonna include that on your image soon?
How do I apply it? to a stock image can anyone help me?
Click to expand...
Click to collapse
mousiope said:
Thanks dexter for the reply ! Are u gonna include that on your image soon?
How do I apply it? to a stock image can anyone help me?
Click to expand...
Click to collapse
just use "apply update" or you copy the lib yourself directly into the /system/lib/hw folder manually.. (gralloc.omap3.so is the name of the file)
the first update-nosign.zip was messed up, please make sure you have the last one i uploaded now..
Dexter_nlb said:
just use "apply update" or you copy the lib yourself directly into the /system/lib/hw folder manually.. (gralloc.omap3.so is the name of the file)
the first update-nosign.zip was messed up, please make sure you have the last one i uploaded now..
Click to expand...
Click to collapse
I´ve just applied it it didnt´t worked.
the problem persists and it messed up my graphics !
I´ve just loaded your image and applied this update it messed up my graphics exactly the same way !!!
Its like i´m seeing artifacts.
I copied it manually to my phone with 2.1u1 and it fixed the 2d slowdown problem but it does mess up the main GUI, the emulated games run perfect though, only emulator menus have the same problems the main GUI has, ingame they are perfect!
Super smooth like in 2.0.1 but able to overclock
okay. the lib from dexter is from droid 2 and it seems, there are some sync problems. this causes the glitches on the screen. yes, 60FPS are back, but which price?
so i started a thread in cyanogen forum, asking for the libs from CM 6 RC3 to be used to crack that 30 FPS cap.
I tried the libs from the CM6RC3 and that does not solve the issue
Anyway lets wait and see what happens.
We are a bit closer already, I can play my emulators at full speed
Renegade_Rulez said:
I tried the libs from the CM6RC3 and that does not solve the issue
Anyway lets wait and see what happens.
We are a bit closer already, I can play my emulators at full speed
Click to expand...
Click to collapse
which libs did you try? i already tried only changing gralloc.omap3.so, but same result, as yours. i wonder, how cyanogen fixed that cap ...
I tried gralloc.omap3.so and gralloc.default.so but that got me the low fp/s again...
Strange that they fixed it in another way then...
Would it be possible to use gralloc.omap3.so from a milestone 2.01 rom. The bug was also pressent in 2.0. But they fixed it in 2,01. Maybe they just accidently used the bad libs again in 2.1.
If i use the files from my 2.0.1 release it wont boot anymore...
Renegade_Rulez said:
If i use the files from my 2.0.1 release it wont boot anymore...
Click to expand...
Click to collapse
same here. also tried other libs together (from 2.0.1), as all under /system/libs/hw and
- libpixelflinger.so
- libpvrANDROID_WSEGL.so
- libskia.so
- libskiagl.so
- libsurfaceflinger.so
and from egl:
- libGLES_android.so
same: stuck at motorola bootlogo
done for today ... too much nandroid restores
so before any of us have to answer this question again please read this thread
so with dzo's port of the newest kernel he started including a wlan.ko compatible with the newer 2.6.32.nbh's into his builds. this left small fragmentation issue with people still using the older kernel
so when you use android on any of the phones in our project your nbh/ zImage is where your kernel is
so you have 2 options for your .nbh/zImage their are
2.6.25 (older kernel)
2.6.32 (newest kernel)
the older 2.6.25 kernels are available on dzo's site (should be a link to it in the first post of this thread) the last one he made was 26-07-2010 (what i use on my touch)
the newest kernels 2.6.32 are avalible for download from the kaiser kernel thread
if using a 2.6.25 kernel you need an update for the wifi this is attached to this post
now those instructions are assuming you have a kaiser if you have a polaris you need the wifi update for it reguardless the one for the 2.6.32 kernel that is also attached
for older polaris kernels i am not sure where the wifi update is for it but a forum search should find it easily if you know what your looking for
and lastly if your on a vogue, wifi will never ever work ever so stop asking
i think that should cover it if i missed anything everybody feel free to chime in (also if this could get stickied that be great)
Good stuff, glad to get that off your chest?
Haha does it show?
Sent from my HERO200 using XDA App
perfectly working
This should be stickied tbh. This question is one that pops up the most followed by questions about .nbh's. Such as how do I edit them, how do I use a vogue rom on my kaiser, etc.
Mind awfully if I link this in my mini-faq, since it's definitly a frequently asked question
Sent from my HTC Dream using Tapatalk
zenity said:
Mind awfully if I link this in my mini-faq, since it's definitly a frequently asked question
Sent from my HTC Dream using Tapatalk
Click to expand...
Click to collapse
please do, i wrote this for the intent of not having to answer it again so if people use the FAQ like they should to start it will make for way less hassles
well it's sitting at near 7000 views, so it's getting looked at
Just thought it would help keep it from getting buried
Help my WIFI doesn't work!
Just kidding
Thank you for organizing all of the answers in one place.
Sorry for bothering you but i can't install this update.
I just get "failed to extract" message after each attempt.
Hope someone can help me to solve this problem.
I've got kaiser with .25 kernel installed on it, system stored on nand and data on ext2.
Did you open the zip you downloaded or try to. flash it as is, if you flashed it as is that's your problem
Sent from my HERO200 using XDA App
Hi,
I am having problems getting any Android ROM to have working Wifi.
I have tried several different ROMs along with the corresponding Kaisimg.nbh generated using the NBH Editor and have tried applying the Wifi update after testing the 'virgin' install. Still no success.
I have an UK O2 Stellar. Could someone tell me a combination of NBH and ROM that has working Wifi (with or without the fix).
edit : just fixed by using the NBH from DZO's site instead of the Editor default.
thoughtlesskyle said:
Haha does it show?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
What's an nbh? Just kidding
sorry for stupid question , but how can i instal this fix?
robgie said:
sorry for stupid question , but how can i instal this fix?
Click to expand...
Click to collapse
Extract wifi update zip file.
Copy androidupdate.tgz to Andboot Folder on your SD Card
Enter Android install menu
Select Install Update
Select Fix Permissions
Quit the menu and check wifi connectivity
Sorry for pushing this thread...
I had Fat Free Rom running for some months and now wanted to switch to an newer one. But I can't get WiFi working.
I tried:
Scoot Cyanogenmod RLS6
Thoughtlesskyle's Not So Super Froyo RLS18
New KAISER ROM Valentine 1.0.2
Krazy-Killa's Kernel Release - RLS5.9.1.2 Alpha
I also updated the Radio to
1.70.19.09 and now 1.71.09.01
and suggested or newest Kernels.
Furthermore I tried ALL fixes for WiFi I could find in this forum like:
http://forum.xda-developers.com/showthread.php?t=848921
http://www.ziddu.com/downloadlink/13294643/androidupdate-unpack-me.rar (from valentine)
and of course the updated linked here.
What's wrong with my Kaiser? WiFi never worked at first offence in Android and even with FatFree I needed to fix it (forgot how I did ^^, guess with new Kernel)
did you use the update with the Krazy-Killa kernel before posting?
What do you mean? ^^
I downloaded this http://forum.xda-developers.com/showthread.php?t=980551 and used atools to get "RLS 5.9.1.2 NBH.7z" and "HAReT Kernel Files.tar" into 1 file. Afterwards I flashed it.
im on the cache kernel 2.6.32 and im having problems with wifi. everytime i try to turn it on it says error
wifi worked fine in the super froyo, but it doesnt now that im on the dzo rom. i tryed to install the update from the cache kernel rar file and it failed to exract. its a androidupdate.tar file
Installed everthing as per instructions on my SE X1 : http://forum.xda-developers.com/showthread.php?t=1156421
First time starts smooth - after doing CWM recovery of Honeycomb..v3
Wifi works.. browsing works.. etc.
I powerd off using the power off option..to reboot and installed gapps.
Now on its keeps rebooting anywhere during booting process.. sometimes it would come to the honeycom moving screen and then reboot.
I reformatted and tried everything again - 4 times now.
It is stable when gapps is not installed??
Any other way to install gapps? other than by CWM recovery method??
Or am I doing something wrong here..
I am very new to android installation.. please help
you should ask this in the rom-thread, not here. if someone comes to "question & answers" about x1, he doesn't expect questions about a half-ported OS, right?! (it's a winmo-phone...)
but yeah, you're doing something wrong. never had this problem when using honeycomb v3. which gapps-zip are you using? the one needoo uploaded?
anyway, better head over to neopeek and get neofroyo v0.1, it's much better. looks like needoo has a new version coming too, based on neofroyo.
Thank you for your reply..
Newbee to XDA so no permission to post in those threads...
However evrything is working now...wifi, apps.. maps.. etc.
hopefully once I am used to getting around these things will take ur advice and try neoFroyo V0.1.. Sure
oh, i always thought that 10-posts-limit only affects the "real" dev-forums. sorry.
I was checking out Live Wall papers from the Market.. Nothing seems to be compatible with HoneyComb Froyo V.3
Does anyone know any that may be compatible..
Ofc it does drain your battery..
simply put best android for x1
neofroyo has wifi issue and not even close to as sexy as honeycomb v.3 is
maybe your installing wrong gapps i never had that issue either
what kernel are you using as well
i found that the only kernel the worked perfect was ygge's turbo
No wifi-error on neofroyo with ygge-kernel. Midnight's kernel works too, but battery-charge isn't shown yet. But it's fast...
Neofroyo is faster than honeycomb, but let's see what needo comes up with next.
caliban2 said:
No wifi-error on neofroyo with ygge-kernel. Midnight's kernel works too, but battery-charge isn't shown yet. But it's fast...
Neofroyo is faster than honeycomb, but let's see what needo comes up with next.
Click to expand...
Click to collapse
No wifi-error on neofroyo with ygge-kernel？ I have tried many times. But wifi never works. Can you share your kernel to me?
http://db.tt/V7TKnyV
don't use the wifi-fix provided on neopeek. (i never did and it still worked fine; that's my old setup, i switched to midnight's kernel since then)
Thank you.
Is there anything that can make the battery last longer on Android??
While x1 on Windows can last for three days Android last only one day?
Hi Guys !
I have an Optimus Black (P970H).
Recently I installed the Stable version of Cyanogen Mod 10 (10.0.0-p970)
My problem is, using the LG Stock ROM, my GPS works fine.
The version that I'm using is the Brazilian version of the Gingerbread ROM (V20A)
When I installed CM 10, the GPS stoped working.
It doesn't fix do any sattelite and using softwares like GPS Test, shows no sattelites at all.
Tomtom doesn't work at all and Google Maps keeps "Waiting for Position"
I wish to know if there's any fix that I can try.
I know that on the folder /etc resides the configuration files for the GPS (gps.conf and gps_brcm_conf.xml).
Can I use the stock files to make the GPS on CM 10 work ?
If you guys know something that can help me I will be glad.
I'm on Brazil, South America.
Thanks to everyone!
Help!!
I have the same problem! I kinda really need GPS. And I don't wanna reveert back to ICS. Can anybody please help me please!!!
If you used the search, you would find several threads about that...
http://forum.xda-developers.com/showthread.php?t=2205560
On CM10 it doesn't work properly, and it won't work later, as there are no new nightlies of CM10. So nobody is developing this rom (its core).
dcop7 made some files that can help a bit, but it's still far from the performance you get on LG's ICS or CM10.1-based roms.
On CM10.1 though, it's working fine now, as the issues with gps were fixed a few months ago.
You can get some info about the issue here:
http://forum.xda-developers.com/showthread.php?t=2230395
I would suggest you to try CM10.1-based roms, as they improved a lot lately.
Sent from my LG-P970 using Tapatalk 2