Database Info

Let's all try to fix the charging issue..

... since this problem is bugging us with aku3.x and crossbow roms.
Especially with the crossbow rom, this seems to be the only problem. The other issues are already fixed, or are easy to get fixed (since they have already been fixed in earlier roms).
In addition to this, I think that if we work together we have greater chances of solving this frustrating issue.
So this is what I have tried (with no success):
1) replace the battdrv.dll with one from a prophet
I get the common result where the device will charge only when you softreset with the cable inserted. You also get a square in the "Model No" in device information (Module address conflict?) Someone solved the square issue in an aku 3.x rom. I would like to know how it was fixed.
2) replace the battdrv.dll with one from an HTC artemis
No charging/status indication. Model No is reported as "WIZA200"
3) I unloaded camera and keyboard driver to see if there are any conflicts with them - no difference

andrew_sh said:
... since this problem is bugging us with aku3.x and crossbow roms.
Click to expand...
Click to collapse
A possible way is to write a wrapper for the batterydriver, which logs information and try finding the differences in pnp, etc.. between a working rom and a non working rom with the prophet-driver.
You could try following too:
- don't touch the batterydriver in original aku3-rom
- do following while device finished boot and os is running:
- copy battdrvr.dll from prophet and rename it to \windows\battdrvr_New.dll (into the new rom)
- change the registry-value HKLM\Drivers\BuiltIn\Battery\Dll = battdrvr_New.dll
- wait some minutes and do a softreset
-->it will not survive a hard-reset, but i guess this could solve module-overlapps..
hope this helps,
ikarus

ikarus said:
A possible way is to write a wrapper for the batterydriver, which logs information and try finding the differences in pnp, etc.. between a working rom and a non working rom with the prophet-driver.
You could try following too:
- don't touch the batterydriver in original aku3-rom
- do following while device finished boot and os is running:
- copy battdrvr.dll from prophet and rename it to \windows\battdrvr_New.dll (into the new rom)
- change the registry-value HKLM\Drivers\BuiltIn\Battery\Dll = battdrvr_New.dll
- wait some minutes and do a softreset
-->it will not survive a hard-reset, but i guess this could solve module-overlapps..
hope this helps,
ikarus
Click to expand...
Click to collapse
Thanks for the info.
I just tried it.
Result:
I get the square in the device info.
No charging/no battery status.
Strange isn't it? I wonder why the model no gets f**d up.

To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...

MusicMike said:
To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...
Click to expand...
Click to collapse
I tried replacing this file. The result is that activesync stops working completely.

MusicMike said:
To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...
Click to expand...
Click to collapse
i do agree.. don't know which dll's, but maybe there are more dll's used for battery..
There is a tool called depends or similar, which can figure this out..
depends is part of free eVC++ (\Program Files\Microsoft eMbedded C++ 4.0\Common\Tools\depends.exe)
ikarus

ikarus said:
i do agree.. don't know which dll's, but maybe there are more dll's used for battery..
There is a tool called depends or similar, which can figure this out..
depends is part of free eVC++ (\Program Files\Microsoft eMbedded C++ 4.0\Common\Tools\depends.exe)
ikarus
Click to expand...
Click to collapse
ahh, thats a handy tool, thanks for the tip !

attached is a cab which could fix this issue.
my contribution to the great work of our rom-cooker
ikarus

ikarus said:
attached is a cab which could fix this issue.
my contribution to the great work of our rom-cooker
ikarus
Click to expand...
Click to collapse
Thanks ikarus, i'll try tomorrow.
So have you tried this? Did you find out what was causing the problem?

andrew_sh said:
So have you tried this?
Click to expand...
Click to collapse
MusicMike tested it, but it needs more testing hehe
andrew_sh said:
Did you find out what was causing the problem?
Click to expand...
Click to collapse
not yet... in part yes, but i don't want to write explanations which could turn out to be wrong...

I'm back, testing it now

Jesterz said:
I'm back, testing it now
Click to expand...
Click to collapse
Welcome back! hehe damn it's been a long time

HELP
okay i have the japnease wm6 rc7 both files its all in jap appantly the battrey issue is fixed and all the other problems can someone help me to convert the language into english and then i can test on my prophet we may have a fully working wm6 rom here guys please need help for final stages.

WM6 100% working on prophet
Hi i just installed wm6 rc7 and i can confirm usb charging and sound all works on prophet flawlesly i need a hero to covert the language into english please can someone help

c3l5o said:
so I was just wondering what does the app change in my phone to make it work... I didn't eve have to soft reset it once...
Click to expand...
Click to collapse
jutley said:
Hi i just installed wm6 rc7 and i can confirm usb charging and sound all works on prophet flawlesly...
Click to expand...
Click to collapse
great. i have some thoughts about the cause, but i don't have an verified explanation for the cause.
Actually i don't have enough time to do more investigation for... So i can explain what the cab is doing.
It's a very slight solution.
The cab creates a notification for the "Notification Broker", which in turn starts XDADev_BatFix.exe each time usb gets connected.
(That is there is no extra thread running, there is no dll loaded, there is no system service running and no extra resource needed. It is almost like before.)
XDADev_BatFix.exe does only set a PowerEvent and exits afterwards.
that's it.
Best regards,
ikarus

anyone sucess pls post...
i'll try tomorrow

ikarus said:
great. i have some thoughts about the cause, but i don't have an verified explanation for the cause.
Actually i don't have enough time to do more investigation for... So i can explain what the cab is doing.
It's a very slight solution.
The cab creates a notification for the "Notification Broker", which in turn starts XDADev_BatFix.exe each time usb gets connected.
(That is there is no extra thread running, there is no dll loaded, there is no system service running and no extra resource needed. It is almost like before.)
XDADev_BatFix.exe does only set a PowerEvent and exits afterwards.
that's it.
Best regards,
ikarus
Click to expand...
Click to collapse
Ok thanks ikarus! Really is a smart and slight solution
guitarz said:
anyone sucess pls post...
i'll try tomorrow
Click to expand...
Click to collapse
It IS working indeed

This fix tested and working on Qtek S200! Its one of the 2,2 clean roms from a few months ago. The battery problem has been my biggest annoyance! Thanks!

I also tried XDADev_BatFix on my 818Pro with AKU3.3-Jester-b1 ROM.
Looks like it really solve the battery charge problem.
Thanks ikarus!

Worked
It Worked on I-mate JamIn, Thanks.
some times the device do not wake up after it sleeps

Quick GPS doesn´t update

I have a problem with Quick GPS: It doesn´t update (I tried activesync, Wifi, 3G,...): "Connection error. Try again later"
any solution?
Thanks

Carolan said:
I have a problem with Quick GPS: It doesn´t update (I tried activesync, Wifi, 3G,...): "Connection error. Try again later"
any solution?
Thanks
Click to expand...
Click to collapse
The same for me!!!! (since a few days)
I'm waiting for a solution too....
THX

Solution that worked for me
You can load and run again the original cab attached here.
You can do it from your sd but remember to install it on the device. Soft reset and ...done!

milpap said:
You can load and run again the original cab attached here.
You can do it from your sd but remember to install it on the device. Soft reset and ...done!
Click to expand...
Click to collapse
Thanks for the tips. Unfortunately I can't install this Cab on my Polaris because the system inform me that this application isn't signed.
Any tips to bypass this problem ?
Thanks in advance

Try to install it when Polaris is not connected with pc.

milpap said:
Try to install it when Polaris is not connected with pc.
Click to expand...
Click to collapse
It is exactly what I've do (before reading your answer ;-) ).
It run perfectly (after a restart of the Polaris).
Thanks for the tip!

Unbelievable milpap!!!
It's work for me too...!!!
I have killed the process just before installing the cab, soft reset, and it's working now!
But where was the problem???

From Spain, thank you very much !!!, milpap
Works for me too

Fix using Registry
[HKEY_LOCAL_MACHINE\Software\HTC\QuickGPS]
"RemindTime"="02151010034724"
"Bias"=dword:fffffed4
"ExpiredTime"=dword:00002760
"folder"="\Windows\"
"region"="GB"
"INIDate"="20060531"
"remind"=dword:00000001
"actSync"=dword:00000001
"auto"=dword:00000000
"NotifyID"=dword:00001960
"INIFile"=""
"path"=""
"EEFile"="xtra.bin"
"curRegion"=dword:00000000
"curIP"=dword:00000000
"pwd"="1"
"authname"="1"
These registry settings will also correct the issue...

thanks
It worked, thank you very much!!!!!

Now workin`
Hey Guys!
After i read the post and updatetd my xda the QuickGPS Update runs like never before!
The O2 Germany Support was unable to fix my prob, so thanks to the Forum!!

Quick GPS
Same problem here, it works again, thanks!

Am i special?
Hey Guys...
I updateted the htc_quickgps.cab and restartet my device.
After one day the update ended with the old errormessage.
I dont know the reason, does anybody else?
best regards
Frank
btw:
I cant see any difference in the reg.-settings so i dont change anything

Quick GPS
Thanks a lot! I had the same problem and this solved it.

Hi,
I also had major problems with my QuickGPS (using a Polaris, which seems to be a little special in this concern).
After many days of research and finally a lucky hit at htc customer support I can tell you this:
You have to install some sort of navigation software, install a map, activate and soft reset before using quick gps the first time. if you dont, you screw up the registry and will always have problems with qgps!!
maybe some hints are helpful (they werren't for me), but I would not want to reinstall or change registry settings all the time.
Reason: The navigation software sets up qgps for its needs. qgps seems to be by far more than a simple download manager for ephemeris data. if you dont have a working navigation software, quick gps will start going wild
In case you will have problems later on: try uninstalling tomtom - soft reset - installl - soft reset and press thumbs
maybe a regular backup can help as well, we will see.
Wish you best of luck...

Thanks for cab, it works for me too !!
Mulb

Only Bepe 0.67 fixed it for me
Hey Guys!
I flashed my Device with Bepes 0.67 and now the update is running witout any problems.
Once again thxs to bepe!
Frank

There's a very easy fix which works for me. I see this problem from time to time on my device too. I am still unable to trace the "bad" software which replaces this registry key!
Just import the attached registry file every time you see the problem is back

Dmitry N said:
There's a very easy fix which works for me. I see this problem from time to time on my device too. I am still unable to trace the "bad" software which replaces this registry key!
Just import the attached registry file every time you see the problem is back
Click to expand...
Click to collapse
Thank you so much for this registery file...My problem was its update was only good for 1 day & 21 hours...It seemed strange to me & believe me I've tried everything & still didn't work right...Now with this registery file, update is good for 6 days....

at me this mistake. he managed to repair it. I say thank you for it

strange messages after upgrade to WM6.1 3.2 thingonaspring.5.2.1933.18533.REALVGA

Hi,
I've just upgraded my mda pro to wm6.1, specifically 3.2 thingonaspring.5.2.1933.18533.REALVGA
On start up or reboot, I get two pop up box errors.
ssdamon.exe
"THE FILE "SDDAEMON" CANNOT BE OPENED. eITHER IT IS NOT SIGNED WITH A TRUSTED CERTIFICATE, OR ONE OF ITS COMPONENTS CANNOT BE FOUND.IF THE PROBLEM PERSISTS, TRY REINSTALLING OR RESTORING THIS FILE"
elatepushservice.exe
The file elatepushservice.exe can not be opened .....
I've tried reflashing and cold reboots, but its still the same. The other functions work fine as far as I can tell.
Also I think the mda pro has retained some of my old settings, i.e. it has remembered the outgoing call duration, even after the rom upgrade ! Is there a way of clearing this info ??
Can any one help ?
Thanks
fs

Try finding the cab "sdkcerts.cab" to disable certificate checks and try it else reflash the rom once again and try.
fyi, the rom you're flashing is a WM6.0 build and NOT wm6.1

Fix?
Had the same issue, but it was related to a file that was removed from the windows directory search the ROM thread I think the file was something like olce?.dll to confirm its the same issue try installing isilo and see if the same error happens.

Hi guys where is Thingonaprings 6.1 ROM I didn't relise he'd released on?

No, he’s just confused between WM 6.0 and WM 6.1 it did take me a while to realize I am not superman too.
WizP said:
Hi guys where is Thingonaprings 6.1 ROM I didn't relise he'd released on?
Click to expand...
Click to collapse

firestormer said:
Hi,
I've just upgraded my mda pro to wm6.1, specifically 3.2 thingonaspring.5.2.1933.18533.REALVGA
On start up or reboot, I get two pop up box errors.
ssdamon.exe
"THE FILE "SDDAEMON" CANNOT BE OPENED. eITHER IT IS NOT SIGNED WITH A TRUSTED CERTIFICATE, OR ONE OF ITS COMPONENTS CANNOT BE FOUND.IF THE PROBLEM PERSISTS, TRY REINSTALLING OR RESTORING THIS FILE"
elatepushservice.exe
The file elatepushservice.exe can not be opened .....
I've tried reflashing and cold reboots, but its still the same. The other functions work fine as far as I can tell.
Also I think the mda pro has retained some of my old settings, i.e. it has remembered the outgoing call duration, even after the rom upgrade ! Is there a way of clearing this info ??
Can any one help ?
Thanks
fs
Click to expand...
Click to collapse
Hi,
Just remove sddaemon.lnk from windows/startup folder.
(when in doubt, just paste this file elsewhere)
greetings,
Wout

I am getting the same thing. None of these "fixes" has any effect whatever. I thought this was a thread full of knowledgeable persons. Why all the stab-in-the-dark answers? Doesn't anybody know what REALLY causes this trouble?

iGO 8 for Android

Anyone knows about android iGo for polaris (QVGA)?

it looks like that it's working...
but haven't really tested so far

Sorry but
Hi,
Not yet for us. It's only usable in 320*480 !
See here
Cheers.
douceka said:
Anyone knows about android iGo for polaris (QVGA)?
Click to expand...
Click to collapse

manu33xtro said:
Hi,
Not yet for us. It's only usable in 320*480 !
See here
Cheers.
Click to expand...
Click to collapse
there's a "fix" to change the resolution down to 240x320 (data.gro)
i've tried it and it works so far, just the maps wont work with the wm igo8 version
have to look now for some new maps!

Hi,
Data.gro ?? Where is this file ? I can't find it in android folders...
Can you share it ? And explain to us how to use it : I've android with haret solution
Thanks in advance.
Cheers.
scripttec said:
there's a "fix" to change the resolution down to 240x320 (data.gro)
i've tried it and it works so far, just the maps wont work with the wm igo8 version
have to look now for some new maps!
Click to expand...
Click to collapse

hi,
attached you can find the modified "data.gro" file.
as your pola should already be rooted , there should be no problem by changing the file.
just copy the file with adb to the device.
afair the path on the device was something like "/app/app/com.navngo.igo.javaclient/ ... "
currently working under wm again, so can't tell you the exact path
have fun with igo on android
so far i've experienced the best usage with "lcd.density=100" in the default.txt
ooh and btw.: maps of igo8 version r3 are working!!

can't see the file in my phone...
Ok. Thanks. I saw it in Warez forum...
But I can't see anything maybe because I use with Haret ?!? I've a data path but nothing in
I don't know why...
scripttec said:
hi,
attached you can find the modified "data.gro" file.
as your pola should already be rooted , there should be no problem by changing the file.
just copy the file with adb to the device.
afair the path on the device was something like "/app/app/com.navngo.igo.javaclient/ ... "
currently working under wm again, so can't tell you the exact path
have fun with igo on android
so far i've experienced the best usage with "lcd.density=100" in the default.txt
ooh and btw.: maps of igo8 version r3 are working!!
Click to expand...
Click to collapse

scripttec said:
hi,
attached you can find the modified "data.gro" file.
as your pola should already be rooted , there should be no problem by changing the file.
just copy the file with adb to the device.
afair the path on the device was something like "/app/app/com.navngo.igo.javaclient/ ... "
currently working under wm again, so can't tell you the exact path
have fun with igo on android
so far i've experienced the best usage with "lcd.density=100" in the default.txt
ooh and btw.: maps of igo8 version r3 are working!!
Click to expand...
Click to collapse
Thx for help.
I've found the file, replaced it, igo seems to start correct resolution. However it terminates for unknown reason after license agreement screen

I tried igo my way for android
and data.gro is supposed to go in
data/data/com.navngo.igo.javaclient/data.gro
but I don´t even have com.navngo.igo.javaclient directory

SUCCESS!!!!!!
have to use root explorer in order to copy data.gro

iseeka said:
SUCCESS!!!!!!
have to use root explorer in order to copy data.gro
Click to expand...
Click to collapse
What version of igo do you have?

douceka said:
What version of igo do you have?
Click to expand...
Click to collapse
IGO myway 8.4.2.124036
i have to say that i said success at home without gps
tried this morning outside 1min no fix
i´ll try this afternoon and will let it more time to see if i get a fix or not

I tried again and i got a quick fix
tried also to plan a route and ok
later i´ll try if it warms speedcams

Hi,
Success for me too.
Just a little problem because I can't see all of the informations in down of the screen (speed for example) If I tap the screen in place of the speed information (I see just the up) I have the popup with speed but not the all ...
Is the same effect for you ??
Cheers.
iseeka said:
SUCCESS!!!!!!
have to use root explorer in order to copy data.gro
Click to expand...
Click to collapse

manu33xtro said:
Hi,
Success for me too.
Just a little problem because I can't see all of the informations in down of the screen (speed for example) If I tap the screen in place of the speed information (I see just the up) I have the popup with speed but not the all ...
Is the same effect for you ??
Cheers.
Click to expand...
Click to collapse
yes.. i guess data.gro has to be improved...
some ppl make a mod in order to hide and use the space of the top bar... maybe is possible to do it in our polaris and fix it...haven´t tried

If I've time I take a look...
Thanks for the answer
iseeka said:
yes.. i guess data.gro has to be improved...
some ppl make a mod in order to hide and use the space of the top bar... maybe is possible to do it in our polaris and fix it...haven´t tried
Click to expand...
Click to collapse

Success finally!!
The problem was somewhere in Win Mobile Content. Now I'm using only few maps, no pois etc. And it works great...

any success in running it on 240 x 320?
I'm using the attached data.gro file, but the language selection is all messed up...

Offtopic:
IGO is design for higher resolution that we have.
Replace data.gro - is the right way to get it running, but at the end result not good. Icons are messed up a little bit.
The other thing - stability. IGO hanged after about 1/2 hour of usage. Phone hangs, only reboot helped. Maybe it was issue of the relise I used. Can anyone post a comment on usage stability?
Right now using Sygic - for me seems much better solution for the moment. Only issue - positioning can take up to 5 minutes.

Hello, I have the HTC Wildfire, downloaded Igo but were exactly I need to place the data.gro file? Tried in to data in the phone not on the SD and it won"t let me copy it, can some one HELP, I really need Igo for my trip. Thanks a lot

[WORKING!] Android on XDA Orbit 2

Since I posted a thread: http://forum.xda-developers.com/showthread.php?t=675311 and nobody could help me. I spent the past 5 days trying to get it to work and did it successfully (through haret).
Here's how to did it:
1. Download this .RAR I put together that includes:
-Eclair
-haret
-default.txt
2. Edit the "mddi.width=320 mddi.height=480" part of the "default.txt" to your needs. (either 320/480 or 240/320)
3. Put the content of the folder "android-orbit2-eclair" to the root of your SD card so it should be something like this:
Code:
-(D:) SD Card [COLOR="Red"](root)[/COLOR]
--conf
--media
--default.txt
--haret.exe
--initrd.gz
--rootfs.img
--system.sqsh
--zImage
4. Navigate to the SD Card (start>programs>file explorer>storage card) and click on the "haret.exe"
5. Once that has loaded up click "run" (about 3 lines down on right side)
6. Just wait, Give it chance to do its thing and simple... Android running on your XDA orbit 2.
any problems, reply to this thread and I will try to fix.
Thanks, James

it dosent work on my htc touch cruise.
I click on Run, and the screen becomes gradually black, and that finished as that… nothing any more occurs.
The screen is lit, but is black, and nothing occurs.

New problem now: I have the same message than you :
Code:
sh:2: unknown operand
losetup: /dev/block/loop 1: No such file or directory
Failed
Failed to reach system.img on SD card.
Whats the problem ?

nico85 said:
it dosent work on my htc touch cruise.
Click to expand...
Click to collapse
If you read the title it says for XDA orbit 2 not touch cruise.

Have you managed to get gprs/3g working with this? I can't seem to get mobile web working on my XDA Orbit II

I dont know whart u are doing here.
But i can use myns donut and eclair totally easy without modding something.
I just have to use the right "default.txt"...
Most packages you find here habe a "default-polaris.txt" in it or you use the one form myn ... It works great for the orbit 2 too
.....
But maby i dont get what you are doing here.. some special build or something?
BUt running android on orbit 2 is net a problem at all just use right conf.
-----------------------
@moondemon
Wifi works with myns eclair and donut. There are fixes (androidupdate.tar) you have to use (nomorootfs)

could u tell me which version have u installed? 1.6?
I succeeded installing the 1.6 version. but when I was trying installing the latest version, I was stucked at the screen which requires me to long-push the dpad center button. I did it but didnt work. I've even tried every keys, still didnt work.
could u give me a hand on it?

I have tried myn's and default-polaris does not work on my xda orbit 2. Also when I do get haret to run I have had trouble actually getting android to boot due to a continual "power wakeup" message. The default-polaris results in a flashing white screen for me. This config is the only config that actually works on my orbit 2.

Hello, i am just a newbie on Android for Polaris, so plz forgive me dump postings At the moment i am a bit spacy what i have to put together to work Android on my XDA2.
android-orbit2-eclair works on my XDA2 after installing but:
phone can't do outgoing calls:
3G can`t connect,
Cam/Gallery crashes
Wifi works.
Touchscreen works and all the rest.
before i installed the recent builds of froyo and eclair
System shows 10-15 min nice boot flash, then it works, but touch screen doesn`t work.
Anyway all the developers doing a great job here!
rgds Matthias

Im not using sd haret anymore. If you try with nand flash (http://forum.xda-developers.com/showthread.php?t=636024) everything works like a charm.
But as i used haret on my Orbit2 i was good with the package myn offered in her donut(or eclair im not sure).
In the package were a default.txt and a one for polaris/Orbit. I changed the polaris one to default (renaming) and it worked.
I think it was the donut package and it worked with zimages for eclair too.
Try this package if it works its worth a attemp to look into the default txt for other builds.
But atm i would suggest to give android at flash a try. Its almost perfekt for daily use if you not to much with some special programms on winmo.
As far as i read there are problems with haret atm gernerally that programms close even if install is fine.

Seems that flashing is the solution to all my problems, but
can you try to explain what makes the difference between haret and a NAND flash install relatet to the runing system?
Unfortunaley my XDA Obit2 is the carrier of my beloved navigation software. The other Wimo apps are junk compared with android. If there is a offline solution for Car Navigation on android, i could kick Wimo into the trash bin. Also i am a Linux user as well on my PC

Camera and astro application not working
Camera and astro application not working .. please help ...

xda orbit 2
I stuck these sections of

I've tried it and it seems it works, but I have a few questions and one major problem:
1. I installed the systems without the SIM card. When I started it again with SIM card, system says that the PIN I type is wrong altough I know that it's correct. How to solve it? Maybe it is so because I'm not O2 customer?
2. Is it possible to boot Android automatically without flashing NAND?
3. Can I theoretically Install Donut or Froyo using this method simply by putting different Zimage in the folder?
4. Do I have to perform another installation in case of buying a battery of more capacity? I saw that default.txt contains information about the battery.
5. May it work well If I change default.txt to the one prepared by atools?
Thanks for advance and greetings.

Double post, sorry.

running on my pola 200 / orbit2 but very slow i think my sd slow too

cingibi said:
running on my pola 200 / orbit2 but very slow i think my sd slow too
Click to expand...
Click to collapse
Can try rom from Scoot_CyanogenMod_6.1_RLS5.5_All_Language
I modified it for haret to O2_Orbit_2 (POLA200)_panel_3
All work perfectly except CAMERA
O2_orbit_2_panel_3_HARET_based_on_Scoot_CyanogenMod_6.1_RLS5.5_All_Languaget.rar
link bellow
http://www.4shared.com/file/01Vco3iR/O2_orbit_2_panel_3_HARET_based.html
Click to expand...
Click to collapse

denis__at said:
Can try rom from Scoot_CyanogenMod_6.1_RLS5.5_All_Language
I modified it for haret to O2_Orbit_2 (POLA200)_panel_3
All work perfectly except CAMERA
O2_orbit_2_panel_3_HARET_based_on_Scoot_CyanogenMod_6.1_RLS5.5_All_Languaget.rar
link bellow
Click to expand...
Click to collapse
Doesnt work for me ive left it about 20 mins and its still just a black screen. The first 1 worked but was slow.

hello, which rom is the best for o2 xda orbit 2 pola 200?