yashsingh1/xdaforums huggingface dataset:
[LG Optimus 3D] feralcat:
Anyone know if any devs plan on possibly releasing a 4.3 rom for the Optimus 3d?
[LG Optimus 3D] krija:
berni work on it ;)
[LG Optimus 3D] feralcat:
Cool. Thanks for the input
[LG Optimus 3D] Edufex:
With the 3D functions working ? Huummmm

Send from LG P920 in deep Space .
[LG Optimus 3D] krija:
I think not :(
[LG Optimus 3D] berni987654321:
No way I think cm10 with a little piece of 3d is the maximum which could work in theory but the little time I have free I'm using to work on cm10.2
[LG Optimus 3D] michalsk11:
your CM10.1 is best !! but can you make overclock kernel with working BT ?? wee need more kernels.. .;p THANKS FOR YOUR WORK !!!
[LG Optimus 3D] SedyBenoitPeace:
Well this is great! A great developer! :D can you tell us something about your progress? Are there bugs? Or you're in an early stage of the porting?
[LG Optimus 3D] bstoinski23:
Android 4.3 LG Optimus 3D Port (Newbie to Porting)

I'm attempting a port for the Optimus 3D and I get as far as to flashing it in Clockworkmod Recovery and just getting an error. I think I'm getting close or something after tinkering for a few hours with it. I get as follows in CWM.

-- Installing: /sdcard/Download/base.zip

Finding update package...

Opening update package...

Installing update...

set_perm: some changes failed

E:Error in /sdcard/Download/base.zip

(Status 7)

Installation aborted.

If anyone wants to tinker with it or check things out let me know and I'll send the link or I can paste coding back and forth for you guys to mess with
[LG Optimus 3D] p-vlad:
remove

assert(getprop("ro.product.device") == "p920" || getprop("ro.build.product") == "p920");

from the updater script
[LG Optimus 3D] drastic00:
Good luck!
[LG Optimus 3D] p-vlad:
put every 5 lines such a string

ui_print("#1#");

....

ui_print("#3#");

....

....

ui_print("#3#");

etc.this will print a line with the number. so you can see on which state it brake.

also skip these lines

--------

mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/system");

package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");

package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");

set_perm(0, 0, 0777, "/tmp/backuptool.sh");

set_perm(0, 0, 0644, "/tmp/backuptool.functions");

run_program("/tmp/backuptool.sh", "backup");

unmount("/system");

show_progress(0.500000, 0);

--------
[LG Optimus 3D] bstoinski23:
Thanks... I'll try that now... Been trying for a while now to get this crap to work... 4.3 would be awesome... Lol

---------- Post added at 09:29 PM ---------- Previous post was at 08:42 PM ----------

I have it somewhat booting. I'm waiting to see if it fully boots. I modified the updater script and it installed. It's booting a cyanogenmod screen with a blue face and an arrow circling around it. I'm gonna see how it goes from here and see. Idk. Maybe there's something I missed. It didn't get no errors when flashing. It might just take a bit to boot. That's what I'm hoping.
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
ORIGINAL POST

:

As you all may already know that I am working on a custom ROM based on Samsung's JB firmware and you all might also be thinking why I still didn't release it, well its because my ROM is having a very weird problem...

The problem is that if I flash my ROM, then after the Samsung logo my phone's screen goes completely blank (or black).. Even though my phone's Menu and Back buttons lit up, it just doesn't output or show anything on the screen... But there's one more thing.. If I rotate my phone to Landscape mode, then only a QUARTER of my screen on the right is shown (see the attached pictures below).... In that small display, I can clearly see the Setup Wizard running with no Force Close messages or with any sort of errors that could have caused this....

(sorry for the lack of Quality of the picture above :eek:)

(even when I take a Screenshot, it comes like this)​

[MENTION=2805784]mr.harsh[/MENTION] has been helping me solve this issue for more than a week now but due to the huge time differences between our countries, its hard to keep up the communication on XDA, so in order to stop filling up his inbox with my messages I decided to create this thread so that anyone can help me resolve this issue.....

Anyways take a look at my Logcat to find out why this is happening... and a couple of more logs and other relevant info has been attached in Post #21 :good:

And Thanks in Advance.... :o

NOTE: All those logs, files, etc. are no longer available - I had to remove them as they can be easily misused

UPDATED & SUMMARIZED POST

:

The Problem

: My phone loses its ability to "Display" anything on its screen after flashing my ROM!

The Culprit

:: After a lot of trial-n-error and experimentation, I found out that my ROM's bootanimation file in the bin folder is somehow causing this problem!

The Solution

:: All I had to do is remove the faulty bootanimation file with the one which works perfectly... :victory:

Anyways, I'd like to thank each and every users who participated in this thread to help me fix my problem; but all I need is someone who can tell me why or how my boot animation is causing this issue and how it can be permanently solved! :D

You can checkout my website to get more information about Sami OS for Android! :good:

UPDATE: I've finally fixed all the problems with my ROM.. Thank GOD! Here's the link to its XDA thread... :good:
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Toni5830:
2 things I think I understood:

- this..:

I/BootTime( 2215): Fail Safe scanning for:/system/app/SecSetupWizard.apk
I/PackageManager( 2215): /system/app/SecSetupWizard.apk changed; collecting certs

W/PackageManager( 2215): Unknown permission android.permission.READ_OWNER_DATA in package com.google.android.setupwizard
W/PackageManager( 2215): Unknown permission android.permission.WRITE_OWNER_DATA in package com.google.android.setupwizard

..is not good

2- many errors similar to that for different apps are not good :p

Try fixing permissions from recovery

Sent from my N73 using Tapa
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] BOOTMGR:
What happens when you change LCD Density via build.prop?

Also attach ls -l /system/app>/sdcard/apps.txt (i just want to see which apps you've included) and ps>/sdcard/ps.txt (which processes are going on) and dmesg log after reboot.
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] ADDICT.ANK:
Its because the pixels and screen density is not correct. Thats y its not showing the screen on full scale ratio.

And about the log cat u have to set the permissions manually..

So try changin density to a higher value.

And post.
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
- But I never changed the Screen's density.. its set to 240 by default... even on build.prop its: "ro.sf.lcd_density=240"

- And how will I set the permissions manually? Isn't that done automatically by the updater-script.. because I have already included all the permissions in it...
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] ADDICT.ANK:
U didnt change it but it needs to be changed to a compatible level. To use the screen fully.

Which device are u using for testing..

As u need to set the density as per the device..

Like a 4.3 inch will use 320. So edit that in build.prop to reach the correct value. But again need to know the device u r using.

And once u r done with that.

U said there are no fcs. So if any app gives u fc. Then fix its permissions.

But firstly lets focus on scaling the density..

Tell me abt the devices which are compatible acc. To the rom u r building and the base sources u r using.

Let me know i'll do as. Much as i can.

:thumbup:
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
No, mate you might have misunderstood something... I am not porting a ROM... I own a Galaxy S Advance and I am making a ROM for Galaxy S Advance using Samsung's Jellybean firmware... This phone's LCD screen density is set to 240 by default and I didn't change it... And also I did not include any other system apps from some other device that could have caused this screen issue...

My guess is that the files responsible for my phone's display is probably corrupted, missing or is mis-calibrated... But I am still not sure about it...
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] ADDICT.ANK:
Its just that it needs a little tweaking. For adjustments.

Try a slight increase in density I.e. 240 to 250. And see.

And also which kernel are u using for it..

As if the files are corrupted u wont be able to use it. So its just a little value tweak

And Mate I know that u r building a rom not porting it. I wanted to know the device u are using.

So take a look at the device's config and os config.

Mean that compare the original build prop of jb with ur build prop.

U will find an answer.

And wat calibration did u used for display.. Try calibrating it again.

And as u said u can see it in landscape mode only.

So u have to go through ur potrait config and see whats missing.

Can u post the framework of it.

Or try editing the layout

As i think its just mis calibration.

And the values for ui.

Can u tell me what values u used for build prop.
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Stryke_the_Orc:
Ok, I guess first things first, Have you ruled out hardware failure? Next are you sure your updater script is correct? I would assume it is as you get some picture in landscape, but just to be safe, double check your mount points. As much as I don't think its a dpi issue ( I get what you're saying when you say you didn't change anything and why) just for giggles, try changing it in increments of 10 up or down...

Other than that I've found a few errors to be concerned about in your logs.

D/dalvikvm( 2162): Note: class Landroid/opengl/GLWrapperBase; has 250 unimplemented (abstract) methods
W/Zygote ( 1810): Class not found for preloading: android.content.res.Resources$1
E/PowerManagerService-JNI( 2215): Couldn't load power module (No such file or directory)
Pretty much anything that starts with W/PackageManager( 2215): Unknown permission
Pretty much anything that states that ResourceNotFound

I have never heard of this issue before, so I honestly don't know what help to give, but I'm willing to answer any questions you may have, and look at your logs, etc... So don't be afraid to shoot me a pm or whatever.

Good Luck:good:
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] ADDICT.ANK:
.The resources are not their or configured.

2. Use dependency to make resources set up and get configured as needed.

So decompile using dependencies and u have to edit layout , screen orientation in both landscape and potrait to set scaling.

As i said compare the build prop both original and the one u are using.. U'll see the difference.

As it overwrites by itself sometime..

CODE]D/dalvikvm( 2162): Note: class Landroid/opengl/GLWrapperBase; has 250 unimplemented (abstract) methods

Its unimplemented means its not used.

Thats the basic reason for screen not getting properly displayed.

Put Updated opengl drivers. Or try putting the original file in ur rom just to see that the problem is still there or not.

So either its corrupted. Or set the permissions to rwx-r-r.

And set this permission to the package manager and other permission related errors.
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] androiddoctor:
Hey

I don't know much about this but have you try changing kernal, you should try different kernal , that might solve this issue. Best luck dear. i am waiting for this ROM

---------- Post added at 07:21 PM ---------- Previous post was at 07:12 PM ----------

As per my experience it don't look like pixel or density problem, it looks like rom not interacting with hardware properly and its sending display signal to half panel only and only half panel is working , try stock kernal and if its not working try cocore different version and discuss it withsome hardcore kernal developer,

Hit tahnks if i helped
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
No mate I don't think its a kernel issue... I tried with CoCore E 7.0, stock kernel and also with HarshJelly's custom kernel... All gives the same result :(

But you are right about one thing though, some driver issue or software issue is causing this :rolleyes:

Anyways tonight I will try flashing it again and post all my results and log here again...
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] ADDICT.ANK:
That's what i am saying...Try a stock kernel....and compare the issues..

1 thing just use a galaxy s running jb the base version...and compare the build props....

all things regarding diplay and gpu rendering and init.d script..

Can u tell me that u how you dcompiled the rom.. ????

If you feel any of the things..give it a shot..it's worthy of efforts.

And can u use the phone in portrait at all , it boots up or not properly..

And try accessing the download mode and see whether it shows on full screen or not.
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
- I did try with stock kernel, it showed the same problem :(

- Ok, I will try with stock (un-edited) build.prop :o

- My ROM was built using DSIXDA's kitchen (the latest version)

- Only my ROM has this weird display problem... Download Mode and Recovery Mode both works with full screen
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] ADDICT.ANK:
Ok thats wat i need to knw that recovery and download mode in full screen.

And compare both build prop. Using notepad and u,ll find the diff.

Can u post the kernel??

Its ok if u want to keep it private..

Just try and edit a copy of kernel and in rom. Fix all permissions via recovery or pc.

And dnt feel down.

We'll get it up and working.

I'll take another look at logcat.
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] androiddoctor:
You should try CM10.1 kernal , And Before flashing your rom you should first install Stock Rom in your device and wipe all data and dalvik cache before flashing everytime. And you should use ODIN to flash your stock rom. Many times if you flash custom rom over other custom rom they conflict and creat problem.
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
- Mate I can't use CM 10.1 kernel BECAUSE this ROM is based on Samsung's 4.1.2 firmware :)

- Yep, I have always flashed my ROM over stock firmware only.. :)

- Yep, I always wipe EVERYTHING before flashing my ROM ;)

Anyways thanks for your concern and help anyway :good:
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] shut_down:
CM kernel + stock based ROM = bootloop. And he do not need to install stock ROM, he can just wipe system and do factory reset. :)

Послато са GT-I9070 користећи Тапаталк 4
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] androiddoctor:
I thought you are using JB 4.2.2

Hey friend, i visited your site and saw some screen shots and according to them your android version is 4.2.2 , thats y i said you should try cm10.1 kernal. I hope you will find solution very soon. Best luck dear.
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
Oh yeah, that's just a build.prop edit mate.. I like the number sequence "4.2.2" than "4.1.2" - that's why I used it.. I know its misleading but I used that to show off in front of my friends :p

And thanks again for your help :D
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
All the logs are attached below...

Sorry for the delay guys, I was busy with other things this week, but anyways this is all I was able to get from my ROM and yes it still has the problems... :eek:

1. This is my updater-script

2. This is my logcat (after flashing my ROM)

3. This is a list of all the apks in app folder

4. This is a list of all the jar and apk files in framework folder

- I'm sorry I can't get the list of processes running atm because the command "ps>/sdcard/ps.txt" isn't working for me... so I can't provide ps.txt for now

- I'm sorry I can't get dmesg log also because no matter what command I use it keeps telling me "the system cannot find the path specified" for both dmesg log and ps.txt

- If you guys want something else like a log or something then please tell me and also tell me how to get that particular log... I want to fix this issue asap but I need your help first :highfive:

==========================

Please take a look at it [MENTION=2805784]mr.harsh[/MENTION] [MENTION=5354640]ADDICT.ANK[/MENTION] and [MENTION=3053298]Stryke_the_Orc[/MENTION]
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] ADDICT.ANK:
Ok bro don't be sorry..

do you got any progress for the screen issue..

as i said check the dpi's.

thanks for updating...

I am pointing out a few log errors check and correct me if i am wrong somwhere...

Basically display related errors..

1. W/SurfaceFlinger( 1811): Wrong current context/surface, display hw rotation disabled. Multiple instances of DisplayHardware? Has surface flinger started using non-DisplayHardware contexts?

W/SurfaceFlinger( 1811): Wrong current context/surface, display hw rotation disabled. Multiple instances of DisplayHardware

1. Hw rotation based error.. enable rotation

2.Basically edit the build prop and add tweak the dpi from higher to lower...

3. Check the display related drivers and file...are they all there..Names used in rom should be same..

4. permissions for recovery give it appropriate permissions like rwx -rw-r or use 777 for permissions while using cmd ...

5.. check that there is no audio problems..there should be not.

6. are you facing any connectivity issues in the rom.. ??

One thing i will say that try putting exact stock files in your rom and see whether it changes or not and post the log...

Ur using the default permissions from the jb right ???

So it's 2 things

Screen and display related file if the files are ok try changing the permissions.

And post.

I'll update u thoroughly
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] BOOTMGR:
use busybox ps > /sdcard/ps.txt

btw, i can see that too many apks are there.I think our /system partition won't handle it.When /system will run out of space CWM won't show error during installation but aborts it (i've experienced it).So check all directories in /system after installation and check that all files from your zip are extracted correctly (just compare number of file available).I also doubt that it is rotation issue.Take android.policy.jar from deodexed (not modified,just deodexed) firmware (same as your ROM's base) and push it to /system/framework and check what happens.I suppose that there not init.d scripts there at the moment.

And the screenshot you've posted shows only landscape mode.What happens in portrait mode?
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
Okay.. I will do that tonight and inform you asap..... but I didn't add too many apks in /system/app directory :confused: and I only added the folders which are required... One more thing, I didn't edit or modify android.policy.jar yet so how did that make all this problems? And I also didn't add any init.d scripts too... Because I wanted to make a Base for my ROM first, then use it to make my ROM.. (that's why it doesn't have too many modification...)

about the screenshot- that is my problem dude.. my phone's display DOESN'T work when its on portrait mode.... only in landscape mode only "half" of it will work - as seen on the screenshot :eek:
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] ADDICT.ANK:
It actually will not matter that u modified it or not..

as they have the permissions to write and execute...so they'll make the changes like that to work in any way they find.

And with the display pls post your rom's and the original build prop of original samsung jb rom

I'll take a look at that....

As it's permissions and density and display files,rotation settings( the settings as we use for landscape, adding data to the potrait profile display) problems and the correct aspect ratio which are not coordinating with kernel as they should..

Just for try changing the density slightly one by one from to another to achieve a better working aspect ratio..
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
Okay I will try changing the LCD's density and see if that works... Anyways the both buld.props are attached below...
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
[MENTION=5354640]ADDICT.ANK[/MENTION], so mate did you take a look at my buld.prop? :o

and yes I just tried setting the LCD's density value from 240 to 243 and again from 243 to 245.. its stll showing the same problem :mad:

I don't think it has anything to do with LCD's density.. but I could be wrong.... :rolleyes:
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] ADDICT.ANK:
Well i did took a look at that. And the props good..

And do 1 thng that change the rotation to landscape only and see that it does show results or not.

And disable a few hw pimp my rom tweaks from the prop...just hw tweaks..

And the. Cpu rendering,debugging....

And well its a permission issue and thats specific to the kernel and device

As its giving error in hw and package manager.

Thats a bit fine but also use the drivers of gpu from the stable version.

See the sources of aosp and specificaly look for the orientation codes.. It will be helpful. If i got anything asap i'll post.

And do as i mentioned and post.

Are u using a stock kernel. ?
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
- I tried using both Custom kernel (CoCore E 7.2) and stock kernel; both showed the same issue on my ROM

- Okay I will remove some of the tweaks from my build.prop as you mentioned and inform you...

- I don't get it. I am not building this ROM from source or anything - I am using Samsung's (fully working) 4.1.2 firmware to build this, so why is it having GPU driver issues then? :confused: and will AOSP drivers work on TouchWiz ROM? And where is the location of these drivers so that I can take a look?

- And did you take a look at my updater-script, as you said it might be permission error so are all the permissions I wrote in my updater-script correct?
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] ADDICT.ANK:
I AM NOT SAYING THAT YOU ARE BUILDING AN AOSP ROM..

I MEAN TAKE A LOOK AT THE AOSP 4.1 ROM IN GITHUB TO THE DISPLAY SECTION AS A REFRENCE AND SEE THAT IS THERE SOMETHING LEFT UNDONE IN CASE...

I AM ALSO LOOKING CAUSE ITS BUGGING ME AND WHAT I THINK IT'S SOMETHING SIMPLE WHICH IS NOT GETTING SEEN...

and do disable a few pimp tweaks in prop especially a hw, gpu rendering..

You can use the rom at aroun 25 % of the screen..

and tell me is there any kind of stretch or it's showing exactly like stock....
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] ADDICT.ANK:
Also take a look at the framework.

Post it if u can.

Its most probably caused by that.
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
Okay I will upload my ROM's framework-res.apk here in a couple of hours... but I personally used and tested all my modifications and themes ONE by ONE on my phone first before adding any of them to my ROM - and none of the .apks force closed or caused any problems so how come they are showing problem after flashing my ROM? :confused:

and one more thing, did you check the permissions I wrote in my updater-script? perhaps I gave some wrong permissions or missed out on some...
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] ADDICT.ANK:
Post the framework in pm. If u want to let it stay personal or private.

And use a stock framework in ur rom just to test the display bug. And see and post.
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
Nah dude its alright, you can get my framework-res.apk here (its zipped to save a few MBs :p)
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Sami Kabir:
I've been very busy with my classwork and homework for the couple of days so I couldn't do what you've asked me to do - I will give it a shot this weekend and inform you... And no I didn't add any init.d scripts - if that's what you asked.... Anyways did you take a look at my framework-res.apk and my updater-script? :fingers-crossed: