Hi, I have a p920 working fine, and I recently bought another p920 to my sister.. but that phone got a problem, the 3d feature doesn´t work well, the 2 images get overlaped, getting a double image mixed in the screen, this is happening with any 3d feature in the phone (games, camera, images, videos, etc). It is like a 3d tv without glasses, all blurry
I don´t know what can cause that, I tried a hard reset, and nothing happened.
I can´t find any kind of 3d setup inside the phone either.
Any clue??
Thank you
For first what system is there?
In build.prop you have to check:
ICS - ro.lge.capp_real3d=true
GB - user.feature.real3d=true
If is false change to true. Must be root.
Maybe will help.
bether said:
For first what system is there?
In build.prop you have to check:
ICS - ro.lge.capp_real3d=true
GB - user.feature.real3d=true
If is false change to true. Must be root.
Maybe will help.
Click to expand...
Click to collapse
thank you, where do i find build.prop ? i´m really noob sorry
it is GB, and its not rooted yet but i can do it
thanks in advance
build.prop is is system/ of device.
You can look first that what you have in user.feature.real3d=true or false (you can use some filebrowser)
If is true that you problem is in hardware that device
If is false you must do root and edit build.prop changing to true.
Related
Hey guys i would like to ask your help for this problem, i have been trying to allocate my app2sd lately and finally i got success following this post http://forum.xda-developers.com/showthread.php?t=512762 but after all i realized that app2sd its not for me it made me phone don't work sometimes, probably cause mSD is not class 6, maybe thats the reason, anyway when i was trying this new thing i realized i lose auto rotation in my phone, i supposed that flash my phone with the normal jf1.5 will fix the problem but it didn't, so i don't know why i don't have auto rotation. My phone has JF1.5 aero1.3 theme
, baseband version 2.22.19 26I and build number dream_devphone-userdebug 1.5 CRB21 147201 test-keys, if someone can give me a hand with this i will really appreciate.
Thanks
joadchob said:
Hey guys i would like to ask your help for this problem, i have been trying to allocate my app2sd lately and finally i got success following this post http://forum.xda-developers.com/showthread.php?t=512762 but after all i realized that app2sd its not for me it made me phone don't work sometimes, probably cause mSD is not class 6, maybe thats the reason, anyway when i was trying this new thing i realized i lose auto rotation in my phone, i supposed that flash my phone with the normal jf1.5 will fix the problem but it didn't, so i don't know why i don't have auto rotation. My phone has JF1.5 aero1.3 theme
, baseband version 2.22.19 26I and build number dream_devphone-userdebug 1.5 CRB21 147201 test-keys, if someone can give me a hand with this i will really appreciate.
Thanks
Click to expand...
Click to collapse
You have to enable it, JF1.5 has it disabled by default. Go at home screen press menu -> settings -> sound and display and check the checkbox for orientation.
jeje OMG was so obvius sorry for that question.
I will delete this threat thanks dude !!!
Hi all, there's a simple mod enable the call-record feature on i9000:
http://forum.xda-developers.com/showthread.php?t=967297
and here is another approach:
http://forum.xda-developers.com/showthread.php?t=863074
I want to know if any of these also works on Nexus S?
FYI - I've tried the patch and although it says it backs up the Phone.apk and injects the "modded" Phone.apk - neither of these seem to occur.
I do however end up with the .rec template.
The APK app works fine.
When I dial, its as though nothing has happened to the phone.apk - no errors, no display indicating failure - nothing.
I do have SU/Root access on Android 2.3.3
g33k84 said:
FYI - I've tried the patch and although it says it backs up the Phone.apk and injects the "modded" Phone.apk - neither of these seem to occur.
I do however end up with the .rec template.
The APK app works fine.
When I dial, its as though nothing has happened to the phone.apk - no errors, no display indicating failure - nothing.
I do have SU/Root access on Android 2.3.3
Click to expand...
Click to collapse
So, are you saying that you have the call record feature worked, although the patch didn't inject the "modded" Phone.apk?
How did it happen? You made an recovery image by yourself and flash it?
Thank you~
Hi mate,
No, im saying that the patch SAYS it worked, but it doesn't in fact patch anything.
I suspect it will only work with that particular Samsung model due to the firmware.
Looks like you'll have to wait for someone to investigate further.
A great need for this feature！
Well, it does seem we didn't have to wait that long.
I have just tested the 8500 froyo pre-release on the 8300 and everything works except for the gyro. This means that the screen is always displayed in portrait.
I know, thats not good on a phone designed to display in landscape. But hopefully someone will port the gyro drivers from the 2.6.29 kernel and we'll have a real improvement on our hands! Or someone will find a solution that forces landscape, which is almost as good.
You'll find the instructions on installing froyo here:
http://forum.xda-developers.com/showthread.php?t=942971
And rooting here:
http://forum.xda-developers.com/showthread.php?t=966624
This is surely a treat!
And if someone has any working solution for the "landscape" problems please let me know on this thread. I'll keep looking for a solution.
/Peter
Edit:
Oh, yeah, forgot one thing. The initial splash screen looks terrible (green background with a blue and red square), so if someone has any idea on how to change that for a nice xda logo or something. I would be most greatful!
Doesn't seem like gps is working either...
/Edit
Well, i can't do any programming. But some things i can acutally improve.
It seems that the keyboard layout that came with the 8500 doesn't match the layout on the 8300.
So here's an updated keyboard layout. Just replace the file named:
qwerty.kcm.bin
located in:
/system/usr/keychars/
With the one attached to this post. Root explorer will (apparently) do that for you. I haven't tried doing it with root exporer (did it with adb). But i have tested the keyboard layout and it works just fine.
Hope that helps anyone!
Please let me know if you have any problems installing replacing the file!
/Peter
Oh yeah, almost forgot, adw launcher lets you set the layout (portrait) of your desktop screens. Thats at least a little help.
edit
Forgot again... The source for 8500 is available on the huawei download site.
http://www.huaweidevice.com/worldwi...d=list&flay=software&directoryId=20&treeId=0#
/edit
I flashed this rom, had alot of trouble with phone connection and such
did a nand backup using recovery-RA-pulsemini-v1.6.2.img reflashed my Boost stock updata.app then restored the nand backup, everything is working great and i have the Boost mobile splash instead of the odd one, didn't fix the gyro though
edit: GPS seems to be working fine, so fixing the gyro or a locked landscape mode is the only bug left.
I'll be following this thread very closely, with any results I get I'll be sharing them here.
I can't seem to get USB debug to work, it's either a CD emulator with the Huawei device programs or mounting the SD card. Anyone else having this issue, or is there a workaround?
OK, some progress; I've just rooted using z4root (sideload) and it appears to be working - Just backed up apps and settings with Titanium Backup.
I just downloaded the stock U8300 so now I've got something to fall back on in case of emergency. It's not listed on the Huawei website though.
So now forwards, to Froyo!
Current progress:
Downloaded U8500 Froyo ROM and installed as per instructions above, twice.
Rooted with Z4Root installed from my SD card.
Had trouble trying to get the keyboard settings over; I tried using Ghost Commander to copy it into place with root access without success. Any other options, lugiber?
I'm not really interested in using Android Dev programs, nor buying apps... is it possible to use terminal commands to copy it into place instead?
Still got the sideways screen issue as expected. GPS works, Wifi works, gyro and compass work somewhat (even the original U8300 caused some issues with North to the 'right' of the phone ie 90degrees off).
google root explorer apk download it to your sd card, install it and just remember to mount the file system as rw, theres a button at the top in root explorer then copy it over
Hmmm, no dice.
Clicked 'mount R/W' but still said /system/usr/keychrs directory didn't have permissions, tried editing manually which didn't apply either.
Are there any other similar ROMs (eg CM6 or the like) that may also be closely compatible? i can put up with the keyboard until I get the screen rotate working, and I read somewhere that some has done so... I'll get back if it works.
I just received and email from Huawei saying they have now released the source code for the U8300 on their website!! It's the eclair kernel, I presume; I haven't downloaded it to check yet.
They also have the 'Normal' (presumably generic) Froyo source code there too, if that is useful to anyone.
ginger rom here if u want to try -> http://forum.xda-developers.com/showthread.php?t=1091159
hi
anyone have fix the portrait problem ?
cuz this is really annoying for me...
Thanks
TuoNonno said:
ginger rom here if u want to try -> http://forum.xda-developers.com/showthread.php?t=1091159
Click to expand...
Click to collapse
Hi
is this rom in landscape mode?
Ty
Speed?
Hello,
I am interested too in landscape mode.
But I am more interested in speed: is it faster than stock firmware?
Thanks in advance!
Mario
ICS - Android 4 - Ice Cream Sandwich on U8300
Anyone know if ICS - Android 4 - Ice Cream Sandwich is going to work on our U8300?
Will the trick of using the U8500 rom work, IF it gets the new rom?
does someone stil use this rom?
i want to try it but links don't work...can someone help me?
Ok so i have been reading forum after forum after forum on how to make the data speed on the inspire 4g......well actually like 4g speeds.....i have found a working method that is working here in spokane, washington...where i do not have 4g but rather 3g....i have been playing and have found a consistent way to get better download/upload speeds that rival t-mobile 4g.....the first thing is you back up your build.prop ( just in case you need it) i use android commander to manage my files, then you delete the old one and replace it with the one i have posted, then you also go to system/lib and you backup the libhtc_lib.so and replace it with the one i posted...then reboot and then test......if you get good results post and let me know (and thank me if you want), if you don't post and let me know so i can play around a little more....i have posted screenshots for the people who are skeptical for you they display the speeds that im getting ant the speeds i was getting...good luck to you all.....
EDIT: This is the build prop from inspire saga 1.1.....DO NOT JUST COPY OVER AS I SAID....I WAS WRONG...OPEN THE BUILD.PROP IN WORDPAD AND THEN COPY OVER THE LINES THAT ARE MISSING FROM YOUR BUILD.PROP....SORRY FOR NOT KNOWING THIS TELL NOW......THANKS FOR THE HEADS UP GUYS.......
What ROM is this from?
Has anyone tried this? What are your results?
the rom is inspire saga 1.1...and i am hoping someone else tries this as well....but no one really looks in the general section anymore.....
itzsnookums said:
the rom is inspire saga 1.1...and i am hoping someone else tries this as well....but no one really looks in the general section anymore.....
Click to expand...
Click to collapse
I just flashed the ROM thats in my sig. Gonna see if this update fixes my crappy data speeds.
If I was still on saga 1.1, I would've definitely tried this. My speeds are really terrible lately and I don't know if its my area or some settings within the ROM.
ok that works...but you should open up the build prop i posted and there are a couple lines that are added and you should add them to yours as well...i have seen a difference from doing so....good luck let me know how it goes.......
itzsnookums said:
ok that works...but you should open up the build prop i posted and there are a couple lines that are added and you should add them to yours as well...i have seen a difference from doing so....good luck let me know how it goes.......
Click to expand...
Click to collapse
Not near my phone right now. Which lines are you referring to? Is it the one with the MTU setting? Or your build.prop doesnt have that.
WARNING - PLEASE READ
OP, I know you've got good intentions but threads like this are a can of worms waiting to be opened. You need to put a warning in your first post that states this build.prop is only for Inspire Saga 1.1. You can't move this file between different ROMs without risk. If you've got the wrong .prop file for your ROM it might cause your phone to go into a continuous reboot loop, or other problems. There are several settings in this file that are specific to the ROM it came from. This build.prop comes from a Sense/Gingerbread ROM, and may not work in a Froyo or non-Sense ROM.
Also, this file changes other things that many users might not appreciate. For example:
persist.sys.shutdown.mode = hibernate
This will cause your phone to never shutdown all the way when selecting shutdown, it will only hibernate. This can interfere with one method of getting into recovery mode, since the phone has to be all the way off when you press the power button & volume minus button at the same time.
henrybravo said:
WARNING - PLEASE READ
OP, I know you've got good intentions but threads like this are a can of worms waiting to be opened. You need to put a warning in your first post that states this build.prop is only for Inspire Saga 1.1. You can't move this file between different ROMs without risk. If you've got the wrong .prop file for your ROM it might cause your phone to go into a continuous reboot loop, or other problems. There are several settings in this file that are specific to the ROM it came from.
For example, let's look at this line is in your build.prop:
ro.build.fingerprint=cingular_us/htc_ace/ace/ace:2.2.1/FRG83D/318736:user/release-keys
The part I highlighted in red is the version of Froyo. Now what do you think will happen if this .prop file is applied to a Gingerbread ROM (version 2.3.3)
Also, this file changes other things that many users might not appreciate. For example:
persist.sys.shutdown.mode = hibernate
This will cause your phone to never shutdown all the way when selecting shutdown, it will only hibernate. This interferes with easily getting into recovery mode since the phone has to be all the way off when you press the power button & volume minus button at the same time.
Last but not least, your build.prop file is from a Sense/Froyo ROM, and there are my non-Sense/Gingerbread ROMs out there.
Click to expand...
Click to collapse
I agree, ROM version and more details on what changes are done, would be very helpful.
I had to "dissect" the build.prop using my mac to see what ROM this is from. I'm also sure the OP had good intensions.
EDIT: Once you open the build.prop up in textedit or notepad, you can see what ROM this is from.. ro.product.version=Inspired Saga v1.1.1
your right and im sorry.....didn't mean any harm...and actually didn't know that it was rom specific.....you always learn new things everyday...thanks guys....
itzsnookums said:
your right and im sorry.....didn't mean any harm...and actually didn't know that it was rom specific.....you always learn new things everyday...thanks guys....
Click to expand...
Click to collapse
No worries...thanks for updating the OP.
hey henry...im not running froyo on my phone...i have ginger sense??????
I hit those speeds already and am on cm7. It depends entirely on where I am located. A difference just two miles means a drop from over 4 down to 1.5 down. Upload stays above 1. This is in the booming metro of Athens, GA.
itzsnookums said:
hey henry...im not running froyo on my phone...i have ginger sense??????
Click to expand...
Click to collapse
Sorry I thought Saga was a Froyo ROM. Yes you've got a Gingerbread/Sense ROM. I've updated my previous post. Same warning still applies though.
Hi all.
I'm on KingDroid V5 based on latests LRG stock rom.
I would want to change the touch sound of the capacitive buttons. On previous versions was as easy as changing the original file (TW_touch.ogg) for the adecuate one. And I have done it but on this version that only change the screen tap sound but not the capacitive buttons.
Someone knows what file to modify??
Thanks in advance.
straycat said:
Hi all.
I'm on KingDroid V5 based on latests LRG stock rom.
I would want to change the touch sound of the capacitive buttons. On previous versions was as easy as changing the original file (TW_touch.ogg) for the adecuate one. And I have done it but on this version that only change the screen tap sound but not the capacitive buttons.
Someone knows what file to modify??
Thanks in advance.
Click to expand...
Click to collapse
TW_Touch.ogg and TW_SIP.ogg
Find them from a rom that you like the sound and replace them in system/media/audio/ui.
Keep in mind the version.
I m not sure and dont remember but i think that you need the same tw version....but not sure.
sotmax said:
TW_Touch.ogg and TW_SIP.ogg
Find them from a rom that you like the sound and replace them in system/media/audio/ui.
Keep in mind the version.
I m not sure and dont remember but i think that you need the same tw version....but not sure.
Click to expand...
Click to collapse
Thanks!
TW_Touch.ogg works as expected.
For the capacitive buttons I had to change the S_HW_Touch.ogg on /system/media/audio/ui.
The really weird thing is that when I "previsualice" with any player the original files both sound like I want but finally in the real world they don't...
straycat said:
Thanks!
TW_Touch.ogg works as expected.
For the capacitive buttons I had to change the S_HW_Touch.ogg on /system/media/audio/ui.
The really weird thing is that when I "previsualice" with any player the original files both sound like I want but finally in the real world they don't...
Click to expand...
Click to collapse
Maybe there is some kind of confliction there...
I see that many times and to avoid it you have to put the files in system and make a wipe data factory reset but it is obvious that none of us want to start over just for a sound...
) ) ) over the air on Galaxy Note ( ( (
sotmax said:
Maybe there is some kind of confliction there...
I see that many times and to avoid it you have to put the files in system and make a wipe data factory reset but it is obvious that none of us want to start over just for a sound...
) ) ) over the air on Galaxy Note ( ( (
Click to expand...
Click to collapse
There is some conflict, that's for sure.
Next time I will put the correct files on the correct path of the flashable zip to avoid the annoying issue.
Regards.