yashsingh1/xdaforums huggingface dataset:
[Xperia Z General] alex3305:
You probably did not flash userdata, which is required to install this rom.
[Xperia Z General] heubergen:
Come any update in the next days?

I will reflash the rom include the userdata because it's lagg.
[Xperia Z General] diopskill:
OK. Duh .....I forgot that. Will try later today. Thanks

---------- Post added at 05:40 PM ---------- Previous post was at 05:37 PM ----------

Just outta curiosity, how smooth is this ROM anyway? Does the app drawer stutter or lag? What about app drawer redraw?
[Xperia Z General] imna357:
Mine is as smooth as the flowing OIL, try it and you'll find out. and volume is also louder even my bluetooth in ear headphones, used to have Viper4mod, but with this one its freaking ok
[Xperia Z General] diopskill:
YES!!! very smooth!!! but.... having trouble flashing GAPPS from the op. can i use any 4.3 gapps and flash thru cwm? rom is smooth!!! thank you for all the help!!! and please keep up the great work!!!

*EDIT* NVM, I got it flashed. great work!!!!!
[Xperia Z General] alex3305:
'official' GApps will always work :).
[Xperia Z General] diopskill:
Very smooth ROM. Actually the smoothest 4.3 ROM I have flashed yet. Absolutely NO LAG AT ALL!
[Xperia Z General] imna357:
Correction... VIPER4MOD is currently supporting 4.3 already... YESSSS:cool:. This ROM + VIPER4... AWESOME
[Xperia Z General] Alhaddad:
which driver should i install?

i can't get it to work in this rom! can you help?

thanks
[Xperia Z General] diopskill:
+1

---------- Post added at 01:05 PM ---------- Previous post was at 01:00 PM ----------

My H+ signal does not show. In fact, the only icon that shows is 3g, but that goes blank BUT I still have a data connection. Weird... Anyone else having this problem? I miss the the h+ icon. I'm running c6602 on T-Mobile. Thanks
[Xperia Z General] alex3305:
Same here, I also kinda miss the connection type status icon in the status bar. Although it's not 100% AOSP, I think it's better than the AOSP way.
[Xperia Z General] diopskill:
Is there a fix?
[Xperia Z General] imna357:
Cortex with A8neon?

---------- Post added at 12:42 PM ---------- Previous post was at 12:41 PM ----------

Its been like that since the start, but in att my set up is using lte, it's just the logo 3g that doesn't change.:)

---------- Post added at 12:50 PM ---------- Previous post was at 12:42 PM ----------

BTW, download the file, extract using root explorer, get the app put it on system/app...reboot. Then open app, it'll prompt you the driver use the cortex with a8 neon, then reboot again. I only installed viper4FX then grab some irs files you can find it in the forum and adjust to your liking.

Don't get fooled on my signature, I'm using Sony xperia Z not galaxy nexus, tweak my build.prop to use my Google wallet:)

---------- Post added at 01:00 PM ---------- Previous post was at 12:50 PM ----------

Correction, CortexA8 with neon the driver that you need to install, but be sure to update busybox before installing everything, then don't forget to use superuser 1.51, install using recovery.
[Xperia Z General] pabx:
Version 2.4, based on JSS15Q is now up.

I will have a look at the H-Icon issue, but this is a very low-prio task (would be glad if someone sent me a patch)
[Xperia Z General] Thraxzzz:
Nice! Anyway to implement the battery percentage into the battery itself? :confused:
[Xperia Z General] shoey63:
Doesn't worry me, I got 4G icon :)
[Xperia Z General] diopskill:
Thank you very much!
[Xperia Z General] koziakauzu:
you can use custom sig within the xda app :p
[Xperia Z General] XeKToReX:
I actually barely get an icon at all, definitely no data indicators too.

Is this something that you are aware of PABX? Appears to be about the only bug I've found!
[Xperia Z General] pabx:
So your phone radio is in HSDPA (+) mode, that's exactly the 'bug' we are talking about.

Looks like qcom-ril is to blame for this: It seems to report a networking-mode constant that AOSP doesn't know about.

Could you post a 'adb logcat -b radio' to pastebin while your phone is in this network mode?
[Xperia Z General] pabx:
Still needs some outdoor testing, but looks fine so far:

Commit:

https://github.com/adrian-bl-yuga/a...mmit/8104bb9b2fb6fccc05c1b90deb3a3ac07b837429
[Xperia Z General] alex3305:
It switched a couple of times between 3G and HSPA. Maybe a large logcat, but it should be complete :P.

Edit: lol, you already fixed it. pabx I think you are one of best devs currently on XDA regarding speed, stability and communication to users. Thanks for all the effort!

Edit 2: Maybe this will also fix the never vanishing network selection bug?
[Xperia Z General] pabx:
Ok, thanks: that's what i wanted to see:

D/PHONE ( 1165): [ServiceState] setDataRadioTechnology=18

No: The network selection 'hang' is another issue.

The 'H-Icon-Bug' was/is caused by qualcomms rild: It seems to report hspa(+?) as constant 18 while android expects 15.

My patch in libril simply fixes this up before the value is passed to the android framework.
[Xperia Z General] alex3305:
With the new 2.4 release I couldn't get a connection to the Google servers, i.e. the icons weren't turning blue.. Anyway, I have fixed it by flashing your new GApps. Maybe this can also help others that are upgrading.
[Xperia Z General] pabx:
You always need to re-flash gapps after a 'fastboot flash system system.img'.

You can do this either via CWM or by keeping my gapps file in /sdcard/. (= this will automatically (re-)install gapps if they are missing and is very handy :) )
[Xperia Z General] alex3305:
Lol. I didn't flash GApps since 2.0 and it still worked like a charm. Thanks for the tip though, haha.
[Xperia Z General] XeKToReX:
derp.. good to know.

I actually have no data at all right now, restarted and disabled/enabled mobile data but can't get a connection. Swapped SIM's with a different operator and still didn't work on my device, my SIM worked in the other device.

I attached a logcat of disabling and re-enabling Mobile Data if it helps.

EDIT: Appears to be an LTE issue only, switched back to GSM/CDMA auto in the Phone Info area and data connected. Switching back to LTE/GSM/CDMA or just LTE/GSM Auto leaves the device in a "GPRS Service: Disconnected" state.

EDIT2: Attached radio logcat for further info.
[Xperia Z General] pabx:
But you probably had my gapps zip stored in /sdcard, so the initscript would reflash gapps automatically after each upgrade.

But build 2.4 expects the new gapps zip (see OP), so the automatic flash-after-upgrade didn't happen during the installation of build 2.4

This looks like a provider issue to me. Are you sure that you are 'supposed' to have LTE? Some mobile providers only offer LTE to customers that 'paid' for it. Also check your APN settings: Android fails to establish the data connection because either your provider simply doesn't respond or your APN settings are invalid:

From your log:

D/DC-1 ( 1128): DcInactiveState: enter notifyConnectCompleted +ALL failCause=MISSING_UNKNOWN_APN
[Xperia Z General] XeKToReX:
Had LTE on stock ROM, actually did have to pay for it.

Very weird, maybe I'll check over my APN setup, appears fine though.

Edit: I wonder if there's something different about the device identification that they've blocked from the network.
[Xperia Z General] Alhaddad:
pabx

the auto brightness is very dim! is this normal? any workaround it?

thanks
[Xperia Z General] Bairei:
I have the same problem, screen brightness sets very contrast, too bright or too dark (or bit more bright, but very rare).

In addition, my battery level during checking internet (tapatalk, etc.) is decreasing incredibly fast (because of that, probably). In 2 hours from ~70% fell down to ~40%, thru night it fell by about 2%. I attach screenies from battery graph.
[Xperia Z General] pabx:
No: There is even a settings option for it:

Settings -> Xperia Z Settings -> Display brightness scale

What do you expect from a phone with a 5 inch screen and 2330 mAh battery?!

Losing 30% capacity with 2 hours screen-on time is actually pretty amazing: This would sum up to 6 hours screen-on time.
[Xperia Z General] XeKToReX:
FYI pabx, my LTE refuses to connect on CM10.2 also, guess its back to stock for me.
[Xperia Z General] pabx:
Thanks for the info - but that's very strange: Could you check if the APN settings are *really* exactly the same on stock + post a logcat -b radio while you are connected to LTE?

Maybe LTE-on-stock is just a fake, there are some nasty options in android to fool people. Example:

<!-- When true, show 1/2G networks as 3G. -->

<bool name="config_showMin3G">false</bool>
[Xperia Z General] XeKToReX:
Yeah its definitely LTE, definitely no 70mbps over dchspa+

I'll check it out when I can and let you know. Cheers for the help!

Could it be something to do with baseband?

Edit: Fixed! It was APN settings, appears the APN I have always used is only 3g. This is also the default in aosp/cm apparently
[Xperia Z General] pabx:
Cool! And it makes sense that it also didn't work on CM as we are probably using the same apn-list.

Could you have a look at

https://android.googlesource.com/device/sample/+/android-4.3_r2.2/etc/apns-full-conf.xml

? Is the APN config in this file correct or wrong for your provider?
[Xperia Z General] XeKToReX:
Mine picked up vodafone internet (vfinternet.au) when it should be:

APN: live.Vodafone.com

MCC:505

MNC:03

Type: default

Can also have the MMS settings in there but I have a separate APN for that.

Thanks for the help, great work on the ROM, I'll flash back to aosp from cm when 2.5 is released!
[Xperia Z General] pabx:
Ok, so the entry from the 4.3 AOSP apn-list is correct.

I upgraded the list in my git tree, so v2.5 should work out-of-the-box for you.
[Xperia Z General] CodeRookie:
I don't know how you did it, but you totally DID it.

The One and only 4.3 ROM I've encountered so far with working bluetooth mouse and keyboard.

THANK YOU, and have a :beer:
[Xperia Z General] pabx:
Thanks for the donation! Getting mouse + keyboard working is just a matter of enabling UHID in the kernel :)

Oh, and i have linux 3.4.59 running :)
[Xperia Z General] Mr. Droid:
Anyway we can get Ethernet USB support? :)
[Xperia Z General] gm007:
Is it newer than 3.4.9?

Or what is the changes?
[Xperia Z General] pabx:
59 > 9

3.4.59 is the most recent LTS release of the 3.4 kernel series.
[Xperia Z General] CodeRookie:
[MENTION=3911109]pabx[/MENTION]

I've read about this fix, but found no ROM so far implementing this kernel configuration, so I assumed just including the config wouldn't do much good.

Any chance of downloading the latest kernel of yours?

I also do have an annoying issue regarding mounted external sdcard (ext4 fs) and usb connected, but I will try to solve on my own, because I don't know whether it is ROM specific or not.

Have a nice day.
[Xperia Z General] pabx:
The latest kernel is at https://github.com/adrian-bl-yuga/kernel_a806/tree/v3_4_LTS

I also noticed the USB issues but never really bothered to look into it. I don't think its a kernel issue as 'nexus media importer' works just fine.
[Xperia Z General] CodeRookie:
I thought more of a binary way, but when I get the time, I will prepare my laptop to compile the kernel.

If someone is experiencing the same USB issue like me, it seems somehow lock-related.

Short explanation: I connect my phone to USB, open my favorite player (Neutron MP), and bummer, library is empty, card however mounted in storage.

Disconnecting cable, starting to play, then connecting to usb, everything is fine.

I can just speculate, my best guess is that knowing the file names, the mediaserver process serves the contents of the files regardless whether in MTP mode or not, but somehow scanning the filesystem for file names seems to fail when connected in MTP mode.

Regards
[Xperia Z General] pabx:
Ah sorry: i misread your post: I assumed you were talking about OTG-USB-Storage.

Mounting the phone via MTP should have no effect on the apps running on the phone (that's one of the reasons why google is pushing for MTP) and i can confirm that usb-plugged-in + playing music on the phone works just fine for me.

Does this only happen with Neutron Music Player? Do you see the same using the stock player?
[Xperia Z General] CodeRookie:
Hi,

Nothing to be concerned about. Stock music player is no option for me being audiophile and having half my library in alac format...

Any chance for me to test this new kernel of yours posted somewhere in binary form?
[Xperia Z General] pabx:
I was asking about the stock player because it would allow you to test if it is a Neutron MP issue or not.

...anyway: I just installed the eval version of Neutron (wow - i really HATE the UI of this app) and playing music while the phone is mounted via MTP works just fine for me.
[Xperia Z General] OCmylife:
This rom rocks! ABsolutely stable(no screen-flickering as in other 4.3 roms) and so far absolutely stable. The only thing I miss from CM is the battery percentage. It would be nice to implement this one under Xperia Settings. :highfive:
[Xperia Z General] fareeed:
One thing I've noticed with this ROM is that the gamma levels are different from Cyanogenmod, the colours don't appear as dark. Is this intentional ? :)
[Xperia Z General] Mr. Droid:
Just installed this ROM,

Seems like the 3G Icon disappears shortly after using and comes back

No Root?
[Xperia Z General] motoridersd:
Are the build instructions still current? I get this error after a make:

build/core/base_rules.mk:130: *** vendor/sony/dash: MODULE.TARGET.SHARED_LIBRARIES.sensors.default already defined by hardware/akm/AK8975_FS/libsensors. Stop.
[Xperia Z General] XeKToReX:
Read the last few pages, will be fixed in the next build.

Flash superuser for 4.3 in recovery.
[Xperia Z General] pabx:
The only undocumented step is that you need to remove the lights-core part from vendor/sony/lagan/proprietary/Android.mk, but you would get a different error.

How did you setup your build dir? (repo init, etc) Did you extract the SW-Binaries v3 zip?
[Xperia Z General] motoridersd:
Interesting. Why does lights-core need to be removed? Are you building your own version of this library?

I am trying to build a version of your AOSP for Odin, and I just wanted to get a base and go from there. It's interesting that you take out lights-core since what I am eventually trying to do is fix the brightness adjustment on CM for Odin, it's broken, but it works well on the bare SonyXperiaProject AOSP and on stock of course.

Now that I am thinking about it, I copied the Odin repo into a new Yuga folder, updated the local manifest using the info in your readme, and synced. But I probably have some leftover Odin parts. I know that the Odin manifest specifically removed the akm project. I did extract the SW-Binaries zip file.

I'll do a clean sync and try again.
[Xperia Z General] pabx:
I remove lights-core because i don't want sonys liblights-core.so blob in my build: It conflicted with some other stuff (don't remember what exactly) and is only used for the illumination-api and is therefore of little use on the Z.

The display brightness is handled by https://github.com/adrian-bl-yuga/device-sony-lagan/tree/jb43/liblights

The brightness sensor is handled by DASH's lm3533 module.
[Xperia Z General] motoridersd:
Thanks for the info. I did find liblights.c on my Odin CM 10.2 build and I've made some changes that have helped, but it seems like the driver for the screen is missing something.

In liblights.h we define the LCD_FILE and setting values in this file controls the brightness. What is reading this file to adjust the brightness? Is it an lm3533 module, driver, or what is it?

This file is adjusted by the set_light_backlight function, and there's a "dirty" fix to make sure the screen will completely turn off when it is turned off. In this yuga AOSP, just like in cm for yuga, LCD2_FILE is sent to /dev/null, but if I do this in Odin, I don't get a fully dark screen when off.

Sorry I'm hijacking this thread but I haven't found much information. Would you happen to have documentation you can point me to where I can learn how the screen is controlled? (interface, drivers, etc)

Thanks!
[Xperia Z General] pabx:
Android will never read from the file: It 'knows' the display brightness value either because the user set it or because the value was calculated by using the measurements of the light-sensor.

Turning the display off (or on) is *not* done via sysfs: This is done by surfaceflinger by calling hwcomposer->blank(...);

qcom's hwcomposer will then probably do some ioctl() magic on a fb device (would have to check the kernel source on how it's done exactly)

But what problem are you trying to fix? Turning the display on/off? Display brightness? ..or the light sensor?
[Xperia Z General] motoridersd:
How does it know this? Is this the kernel that knows? In CM, if I do 'echo 255 > /sys/class/leds/lm3533-lcd-bl-1/brightness' (this is the LCD_BACKLIGHT_FILE2 defined in sony_lights.h) from the shell, the brightness changes. This is the same file that lights.c updates in the set_light_backlight function, so in CM's case something is reading this file and converting it into the actual brightness.

I see the display being turned off somewhere else (in dmesg), but if I don't write a 0 to LCD_BACKLIGHT_FILE(or in the original CM lights.c a '15' defined as LCD_BRIGHTNESS_MIN) the display will be off, but it will have a glow because the backlight will still be on. That's why there's a dirty fix to make sure this doesn't happen on CM. And this is what makes me believe something is wrong with the CM implementation of the backlight for fusion3 devices.

Initially I wanted to fix the auto brightness. In CM, auto brightness does not do a very good job, so I started using Lux which did a much better job, but then discovered the slider was broken. The full range of brightness was only available at the top end, so I fixed that by removing a function that CM uses called brightness_apply_gamma which was setting the minimum brightness to 180. I noticed in stock, the minimum brightness is 155, but in my fix I allow a 0 which gives me a huge range for the LCD brightness (and better battery life).

Once I did that, I noticed that at every brightness level, there is light bleeding at the top of the panel. It's like the backlight is not really being turned on full force or the driver is doing something wrong with Odin's panel. Here's a pic of what it looks like:

Notice the black/grey blobs at the top of the screen. This does not happen with stock nor AOSP, so that's why I'm trying to figure out what the differences in backlight/screen implementation are between CM and AOSP to fix CM.

I want brightness adjustment to work properly on CyanogenMod. Turning the display on/off works, with the dirty fixes. Light sensor works fine. I think fixing the independent problems (brightness, display on/off) is the wrong approach and should look into fixing the way the screen behaves.
[Xperia Z General] pabx:
No: You are mixing things up:

There are 3 parts: The Android Framework, the Android HAL (lights.c is part of it) and the Kernel.

If you change the brightness (or boot your device), the Framework tells HAL to change/set the brightness and HAL therefore writes into sysfs, telling the kernel to send the required commands to the hardware.

Of course: You can write your own value into /sys/class/..../brightness, but this change won't last as the framework/hal simply overwrites this value during a brightness change: The file in sysfs is never read by Android.

No: NOTHING reads this file in userspace. The file is provided by the display in-kernel driver and simply can be used to set the brightness of the LCD panel. The calculation of light-sensor-value <-> brightness happens in the android framework.

You are mixing kernel<->userland up again: Of course the kernel will tell the *hardware* to turn itself off, but the display-off event is initiated by the android framework (Framework -> hwcomposer -> kernel)

I doubt that the display *power* is controlled by the lcd-brightness on Odin.

You can verify this with a quick test: Just make 'set_light_backlight' a noop: Does the display still turn on/off if you hit the power button?

On Yuga, the kernel uses two sysfs values to actually calculate the real brightness value of the panel:

The 'brightness' file (0-255) and a file called 'fsc' (0-18 if i remember correctly). The 'fsc' file controlls the 'display brightness scale'. Changing the fsc value may solve your issue.

You can not fix 'how the screen behaves' without fixing the other two issues: You have to split up your problem.

First: DISABLE auto brightness and make sure that the manual brightness works to your satisfaction (= the lowest + highest values are OK). After this is fixed, you can start to work on the automatic brightness calculation.
[Xperia Z General] pabx:
Build 2.5 is up with kernel 3.4.59 and the h-icon fix (i assume that the mode reported by RIL is H+)
[Xperia Z General] iKillCypher:
is this from the sony official development team as in the sony c6603 ? which was made by sony team ?

seems like this is plain AOSP with no cyanogenmod stuff in it :3 pretty cool if you ask me..
[Xperia Z General] alex3305:
Thanks, gonna flash it in a bit :).

This is made by pabx and he uses sources from Google (Android), Linux, Qualcomm, Sony and his own to make this awesome rom.
[Xperia Z General] Thraxzzz:
Gonna try dual booting this :D

Edit : Forget that this is not a .zip file,able to make it to a zip file pabx?

Sent from voldemort's nose
[Xperia Z General] motoridersd:
Thanks for the detailed answer Adrian. I really appreciate you taking the time to explain.

I did this test. I made set_light_backlight do nothing, by reducing it to

static int set_light_backlight (struct light_device_t *dev, struct light_state_t const *state) {
int err = 0;
return err;
}

And the screen does not power off properly. The backlight is still on. The CM lights.c file has this dirty fix I mentioned:

//dirty fix for black display
if (brightness != 0 && brightness < 180)
brightness = 180;
err |= write_int (LCD_BACKLIGHT2_FILE, brightness);

Where can I find where the FSC value is being set? It must be used in Odin too, since I believe they use very similar panels, if not the same ones (the panel model number changes by one digit)

I have fixed the range of the brightness slider in CM by changing the lights.c file. To fix the auto brightness I would have to adjust the table that ties sensor to brightness values. I haven't tried doing that because I want to fix the screen first. The backlight bleeding I posted is not present in AOSP, so I want to fix that first. It's possible the FSC you mention is what is causing it, due to the scale being off.

Thanks again!
[Xperia Z General] iKillCypher:
which means this is pure AOSP without any cm patches in it?
[Xperia Z General] pabx:
That's strange: I had a quick look at the kernel source and can't see how this wouls really power off the panel.

AFAIK, the panel-poweroff is sent to the display using a DSI command (see mipi_dsi_panel_driver)

On yuga i think it's only used by the stamina mode.

The systfs file is located at /sys/devices/i2c-0/0-0036/leds/lm3533-lcd-bl/fsc
[Xperia Z General] Thraxzzz:
Hey Pabx,can you make a .zip file? I wanna try dual booting this ROM ;)
[Xperia Z General] pabx:
Sorry, but no - this will never happen.
[Xperia Z General] alex3305:
Just a quick question, has anyone experienced some kind of jumping regarding scrolling? For instance, when I'm browsing and I'm scrolling from like 50% oft he page to 60% of the page, it sometimes just jumps back to 50%. However when I continue to scroll, it starts again at 60%.

I most frequently experience it in the stock browser, but sometimes in the system settings as well. I hope I've made myself clear, because it's quite an hard issue to explain.
[Xperia Z General] Carceri:
Yes I have the same issue. It's been present for me in all 4.3 builds, but didn't occur in the builds based on 4.2.
[Xperia Z General] OCmylife:
I wanted to build your rom from source and got the following error:

Checking build tools versions...
build/core/base_rules.mk:130: *** vendor/sony/lagan/proprietary: MODULE.TARGET.SHARED_LIBRARIES.liblights-core already defined by device/sony/lagan/liblights-core. Schluss.

How could I fix this error?