Quote:
Originally Posted by m4f1050
Touching screen while boot animation does nothing, I tried it many times. Will try the other suggestions though..
Noticed something weird now.... The xdandroid animation at the beginning was flashing (turning on and off very fast, like 4 to 6 times a second)
Pressing both MENU and END got my screen on, went to MENU, SETTINGS, DISPLAY and AUTOMATIC BRIGHTNESS was OFF, turned it on and it stayed on. When I tried turning it off the screen turned off! :O
AUTO BRIGHTNESS is back on...that seemed to fix it...
EDIT: Let it sleep and when tried to turn screen back on it didn't want to, not even with MENU and END.... :/
EDIT 2: Is there a way to reboot android propperly? reboot -f is just a soft reset sort-of... I want it to go through the init and not to leave partition "dirty"...
For now I installed VNC server and DYN IP update utility to connect to phone and be able to see what's on the screen... LOL
|
I take it you are using the reference build? Do you have the 3D drivers from Tiad's thread or my full package build in the root of your sdcard? I get that flickering without 3D files, but it works nice and smooth with the 3D files there.
As for screen on/off, it is still under development, and I'm sure ACL and Wistilt are working on figuring that part out. We just have to be patient and wait for them to get it ironed out
For the reboot, I thought they added proper shutdown and reboot, but I think something else is causing the partition to be dirty.
Quote:
Originally Posted by mpannen
that dll I attached is specifically for rhod400/rhod500 (maybe, I am trying to figure out the difference between 100/400/500 and all of those specific names)
OK I think I understand now, MightyROM is only for CDMA worldphones, and the rhod100 must be only a European GSM.
|
rhod100 is a GSM European version of the Touch Pro 2. The rhod400 and rhod500 are US CDMA. You cannot mix/match the ROMs on those devices.
Quote:
Originally Posted by mpannen
Can a rhod100 be called a touch pro 2? That dll .zip file came from OEM driver folder from MightyRom, and if I am not mistaken, his ROM will work on GSM phones as well. I guess I am not certain what phones are considered 'RHOD100'.
Nevermind I think I understand now. Will not work for RHOD100.
|
MightyRom is CDMA only. Also, I would not recommend grabbing drivers from a cook's kitchen as you never know where they pulled them from. Always disassemble a stock ROM from the manufacturer for that specific phone.
Quote:
Originally Posted by m4f1050
uhm... the TP2 is my daily phone, what build should I flash so I don't have to keep flashing between nand and wm rom?
|
I would not recommend using any of the NAND builds for your daily phone. It is not ready for full time use, and I really don't feel that Haret is ready yet either. In any case, Haret will be much better for constant daily use than NAND will be.
Quote:
Originally Posted by MassStash
not if one exists... but if so, like 11/29??? maaaaybe.
anyhow, had a funny thought today, which i only imagine, has had to have been thought of already by someone IF possible. Is it that we haven't quite figured out full nand? or don't want to do it for test purposes. If its been/being done by you, the panel is stills fussy i take it? I just thought maybe if its full nand, the panel would react better... idk, just a thought/Question
is it just me that cant get tinboot to work now??
|
Being on full NAND will not help with the panel stuff. The biggest fear is writing to the wrong parts of the NAND and bricking a device. Maurice says he has it working and has created 4 partitions. I'm also looking into it now that I only have a few months left on my contract before I can get a new phone. I don't mind bricking it as much at this point. Once I get some details from him, I'll start messing around with YANG to move everything to NAND, but I definitely want to do my research rather than ending up with an expensive paperweight
