yashsingh1/xdaforums huggingface dataset:
[XDA Assist] RyanBernardo:
Hi XDA Peeps,

I owned my Samsung Galaxy S3 (Shv e210k) for almost 2 years and i would say that it is a wonderful device (variant). However, last week I had problems with the wifi connectivity. The Wifi range became shorter and it doesn't connect with my secured router and even public, "it says saved, secured wpa" i kept on pressing connect but it doesn't connect. Unless if im 1 meter from my router and I have to press the WPA button of my router for it to identify my phone, also with a public wifi it does connect but it drops on certain time and reconnects again, I tried most of the thread here at xda such as:

- *#0011# method which I have disabled the power saving mode

- Factory reset my device

- Reflashing stock firmware

- forget network wifi and logging in again

Am I missing something here? What do you think is the problem with my shv e210k? And would you suggest any solution to this?

Thanks!
[XDA Assist] jd1639:
Hi, thank you for using XDA Assist. I would try asking your question here, http://xdaforums.com/galaxy-s3/help/help-thread-galaxy-s3-question-t2690307 Although it's not specific to your device it does cover all of the S3 variants. Also see this, http://xdaforums.com/galaxy-s3
[General Questions and Answers] e6daniel:
Does anyone have knowledge on howto root the Huawei mediaq m330 maybe from experience of m310?

Second question is related to the possibility to install third party apps. I have enabled this in the menues but have no idea howto install and later expect where to launch them from in the GUI.

BR Daniel
[General Questions and Answers] e6daniel:
Apps successfully installed

I have successfully installed two apps from sdcard and I have recieved shortcuts to them. Unfortunately the scrren just flickers whem I launch them. Not full Android? I assume?? Any thoughts on this?
[General Questions and Answers] Ctyhunterz:
Hi do u know how to change the language in this mediapad?
[General Questions and Answers] nightmaker:
Hi daniel,

Did you successfully work on your mediaQ M330?
[General Questions and Answers] delphis.wang:
no, it doesn't work.
[General Questions and Answers] ultiga:
I've used Halauncher and it's working..

But you won't be able to Set the HAlauncher as default unless someone able too root it.

I also tested some apps like moviehd, cloud tv, iflix, terrarium tv, hypptv and some others with success
[Omni Features Development] jeekajoo:
Hi,

do you know if microg/android_packages_apps_GmsCore was finally integrated into omni?

this ticket says it was accepted but I have no access to omni's jira to verify by myself: https://github.com/microg/android_packages_apps_GmsCore/issues/2

this projects is a free/opensource reimplementation of google play services (gcm, location, store, ...)

Thanks

J.
[Omni Features Development] xuefer:
what do we get from it?
[Omni Features Development] jeekajoo:
http://xdaforums.com/showthread.php?t=1715375
[Galaxy Note 3 Themes and Apps] sherif-bakhoum:
Hi everybody I'm wandering if anyone of you know a way to have a shortcut to the weather main app so i can check in the drawer like a normal app instead of the widget?

Thanks in advance [emoji4]
[Omni Q&A] gigoo25:
Hello I am trying to port the beloved OmniRom to my device which is a KLTE (Samsung Galaxy S5) I have successfully built the ROM from source using kernel and device configs from CM and of course some fixes and cherry picking. The issue I have now is that the ROM will not boot.

I stays at my carrier logo (Samsung) so it does not even let me cat-log. I tried to install the ROM and then restored a backup of Cyanogenmods system directory. It boots to android but all apps forceclose. I did this to see if it was an issue with the boot image and since it can boot to a different system partition I don't believe its a boot.img issue or kernel issue for that matter. Or is it?

Any help getting this to boot would be appreciated. I can provide build logs and my device repo if needed.
[Omni Q&A] Entropy512:
MSM8974 is our first CAF chipset we're working on supporting.

I'd suggest looking at the Oppo find7/msm8974-common repos as nearly all initial CAF 8974 work is being done on the Find7.

you need android-5.1-caf branches for frameworks/av and frameworks/native for a CAF device until I finish the merge effort
[Omni Q&A] gigoo25:
Thank you! That explains a lot. Maybe you can help me again? I keep coming across building with legacy opposed to CAF and to change it in the configs... What configs are they talking about?
[Omni Q&A] Entropy512:
You mean AOSP HALs? It's pretty rare for a CAF device to work with vanilla AOSP HALs.

It's the various QCOM_blah_VARIANT flags - 8974s are caf-bfam
[Omni Q&A] gigoo25:
Updated my repo to 5.1 source but still getting errors. Here is the device configs that I am using. I am getting the same errors throughout.

First error was

frameworks/base/core/jni/android_view_Surface.cpp:206:14: error: 'class android::Surface' has no member named 'setDirtyRect'
surface->setDirtyRect(&rect);

Which I solved by cherry-picking THIS

Next I get an error that msmcal-hwdep.h is not found not sure how to fix this yet...

I recreated my devices config from scratch and uploaded it to git... Maybe you can take a look when you have some free time? It would mean alot! https://github.com/Gigoo25/android_device_samsung_klte
[Omni Q&A] Entropy512:
msmcal_hwdep - look at the stiff in your kernel source under include/ - all of that header-y stuff in some of the Kconfigs

You shouldn't be cherrypicking that, I'm not sure why Max even put that up. Until I finish the CAF av/native merge, anyone declaring QCOM_HARDWARE should be using the android-5.1-caf branches of av and native
[Omni Q&A] gigoo25:
Awesome! alright will look into that
[Omni Q&A] gigoo25:
Having issues compiling the camera I get the error

device/samsung/klte/camera/CameraWrapper.cpp: In function 'char* camera_fixup_setparams(int, const char*)':
device/samsung/klte/camera/CameraWrapper.cpp:161:20: error: 'KEY_DIS' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_DIS, android::CameraParameters::DIS_DISABLE);
^
device/samsung/klte/camera/CameraWrapper.cpp:161:56: error: 'DIS_DISABLE' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_DIS, android::CameraParameters::DIS_DISABLE);
^
device/samsung/klte/camera/CameraWrapper.cpp:162:20: error: 'KEY_ZSL' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_OFF);
^
device/samsung/klte/camera/CameraWrapper.cpp:162:56: error: 'ZSL_OFF' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_OFF);
^
device/samsung/klte/camera/CameraWrapper.cpp:164:20: error: 'KEY_ZSL' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_ON);
^
device/samsung/klte/camera/CameraWrapper.cpp:164:56: error: 'ZSL_ON' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_ON);
^
make: *** [/home/rob/android/omni51/out/target/product/klte/obj/SHARED_LIBRARIES/camera.msm8974_intermediates/CameraWrapper.o] Error 1
make: *** Waiting for unfinished jobs...

Is this a framework issue?
[Omni Q&A] Entropy512:
Looks like maybe some missing Samsung patches
[Omni Q&A] gigoo25:
I appreciate all the help you have been giving me in trying to port Omni to the KLTE! I could not have done it without you!

I ended up having a booting and working build when I removed the camera and RIL

RIL gives me an error of

frameworks/opt/telephony/../../../device/samsung/klte/ril/telephony/java/com/android/internal/telephony/KlteRIL.java:282: error: no suitable constructor found for SignalStrength(int,int,int,int,int,int,int,int,int,int,int,int,int,boolean)
return new SignalStrength(gsmSignalStrength, gsmBitErrorRate, cdmaDbm, cdmaEcio, evdoDbm,
^
constructor SignalStrength.SignalStrength(Parcel) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(SignalStrength) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(int,int,int,int,int,int,int,boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(int,int,int,int,int,int,int,int,int,int,int,int,boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength() is not applicable
(actual and formal argument lists differ in length)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error

It should be a frameworks/opt/telephony issue correct? Except it doesn't display the full file path?
[Omni Q&A] Entropy512:
It looks like the KLTE actually specifies its own RIL subclass (interesting trick, I've never seen that before) and that subclass is depending on something in frameworks/opt/tel that Omni doesn't have.

Either find the missing patch in f/opt/tel or figure out how to adapt KlteRIL.java
[Omni Q&A] gigoo25:
I seem to have gotten everything working fine besides the camera. The app and libraries compile fine but when the rom boots I cannot see it in the app drawer. When I try to launch it through the lockscreen it just force closes. Not sure what could be causing the problem? All the permissions seem to be checking out, and messing with the BoardConfiv and Device make files has not seemed to help. Any suggestions on how to fix this? Could it be a framework issue?
[Omni Q&A] Entropy512:
Look through the logcat for camera errors, especially any errors about missing libraries.

Not appearing in app drawer indicates that Android doesn't think there is a camera present. There are 2349734297320 different things that could cause this - missing camera HAL dependency, kernel/HAL mismatch, many other things.
[Omni Q&A] gigoo25:
Here is what I found in the logcat

--------- beginning of crash

[ 06-01 20:08:07.366 3437: 3437 E/AndroidRuntime ]

FATAL EXCEPTION: main

Process: com.android.camera2, PID: 3437

java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.camera2/com.android.camera.CameraActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.camera.util.PhotoSphereHelper$PanoramaViewHelper.onStart()' on a null object reference

at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2325)

at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2387)

at android.app.ActivityThread.access$800(ActivityThread.java:151)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1303)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:135)

at android.app.ActivityThread.main(ActivityThread.java:5254)

at java.lang.reflect.Method.invoke(Native Method)

at java.lang.reflect.Method.invoke(Method.java:372)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)

Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.camera.util.PhotoSphereHelper$PanoramaViewHelper.onStart()' on a null object reference

at com.android.camera.CameraActivity.onStartTasks(CameraActivity.java:1885)

at com.android.camera.util.QuickActivity.onStart(QuickActivity.java:111)

at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1236)

at android.app.Activity.performStart(Activity.java:6006)

at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2288)

... 10 more
[Omni Q&A] Entropy512:
Pretty much - if you can't figure out what is wrong from reading a logcat, most likely, you can't figure out what parts of the logcat are relevant and which are not.

That excerpt basically tells me nothing.

I assume that was from trying to forcefully start the camera with no camera actually present as far as Android was concerned. That's a symptom, not the root cause of the problem. Based on what you've described, the root cause of the problem will likely be visible even if no attempt is made to use the camera.
[Omni Q&A] gigoo25:
I've been messing around with the device configurations and logcats. I I think I have found the culprit for my camera not working. It shows that it loads the module but then fails to open it? Is this a CameraWrapper issue? Still trying to fix the camera so I can use this as a daily build but I have limited experience as a developer.

EDIT: Also the camera shows up on first boot but then disappears and says that the application is not installed. I'm trying to logcat it but not sure how to do that on the first boot without allowing my PC

EDIT2: From the looks of it searching the web it seems to be an issue with frameworks/av/camera/CameraParameters.cpp & frameworks/av/camera/include/CameraParameters.h

I/CameraService( 381): CameraService started (pid=381)
I/CameraService( 381): Loaded "MSM8974 Camera Wrapper" camera module
I/CameraWrapper( 381): camera_get_number_of_cameras
I/CameraWrapper( 381): check_vendor_module
I/PackageManager( 741): /system/priv-app/MmsService changed; collecting certs
I/PackageManager( 741): /system/priv-app/OmniSwitch changed; collecting certs
E/HAL ( 381): load: module=/system/lib/hw/camera.vendor.msm8974.so
E/HAL ( 381): dlopen failed: cannot locate symbol "_ZN7android16CameraParameters25KEY_DYNAMIC_RANGE_CONTROLE" referenced by "camera.vendor.msm8974.so"...
E/CameraWrapper( 381): failed to open vendor camera module
[Omni Q&A] Entropy512:
Looks like a patch for CameraParameters needed by your device is missing since no one has tried to bring that device up before, or hasn't tried bringing it up with 5.x

Since it's a Qualcomm-based device and likely using CAF repos, you'll probably have to patch frameworks/av-caf and not frameworks/av - see https://lists.omnirom.org/pipermail/maintainers/2015-June/000101.html for details (we need to add this info to the wiki...)
[Omni Q&A] gigoo25:
So I would have to split av into two folders then applying I believe THIS patch to av-caf in order to compile it properly?

Also does native-caf branch still have to be merged before compiling?
[Omni Q&A] Entropy512:
Well, the splitting of av is already done. Native is already merged with ifdefs (it didn't require nearly as much ifdefing as av, so we have a "unified" CAF+AOSP native). The only thing that is needed for device maintainers is adding av-caf to omni.dependencies - see the maintainers list post I linked to, or look at the Oppo find7 history.

So once you're pulling in av-caf via omni.dependencies, you should be able to apply that patch to av-caf and then submit it to Gerrit for review.

You might want to start idling in IRC, #omni is where most device maintainers are (in fact, all maintainers for supported devices idle their routinely, it's now a requirement for maintainers to routinely idle in IRC so they can see what's going on/people can ping them with questions.)
[Omni Q&A] gigoo25:
Turns out I might of fixed the problem. Instead of messing with frameworks/av I can just override it with a file inside include/camera? Looking back at the Cyanogenmod repo for my device THIS is present while in my source it is not.

Compiling now. Will post results after.
[Xperia Z2 General] pec0ra:
Thanks for the guide and the good explanations :)

I just think it would be interesting to give your sources since there is a lot of false information on this topic.
[Xperia Z2 General] ottomanhero:
OP updated with source ;)

EDIT : OP updated with detailed info, few tricks added
[Xperia Z2 General] Haldi4803:
Nice.

Now if we just had two Z2 one charged from 0-100 and another from 20-80 for over 2 years, then we could see the difference.

If we just had something like THIS not from 2010 but 2015 with 3200mAh Battery from Sony.
[Xperia Z2 General] OverTheEdge:
I believe in stressing the battery by charging it fully to 100%. I always charge at night until morning. The sweet spot for is 90. Sony created Li-ion batteries if I'm not mistaken and they know a lot about batteries. That's the reason why Sony phone's light indicator turns green when 90% charged already.
[Xperia Z2 General] HellsDemise:
thanks that was some really useful information
[Xperia Z2 General] ottomanhero:
No offense but you're just being a sony fanboy here.Battery tech is the slowliest proceeding tech out of every other components' and battery quality is averagely the same with the exception of some very low level products.Even so, in the article over there in battery university it says that those 1500 mAh batteries were made for smartphones and brand new.

Cropped from sony xperia z2 'environmental' (can be found on sony website) :

Quote from Wiki :

(LiPo = Lithium ion polymer)

P.S: Feel free to proceed with buying two xperia Z2's and charging them differently though, you may discover something new that every sciencist on the world couldn't. ;)
[Xperia Z2 General] Haldi4803:
I've had one of those 1500mAh Batteries in my X10

Compared to the Z2 battery the capacity has increased by 2.1 while I doubt that the volume has increased by 2.1x!

I believe that this "good usage" will increase battery life. Yet I'd love to know by how much exactly. 10%? 15% 20%?

Just "better" doesn't satisfy me :(

Sadly the cost for good testing equipment easily overwhelms the cost of 2 Xperia Z2 ^^

BTW, according to Kernel Adiutor:

5% is 3.6V

1% is 3.4V

You might want to check that.

View attachment 3279914View attachment 3279915View attachment 3279916View attachment 3279917

Edit:

Here we also have the Voltage when fully charged.

While plugged 4.3V

After unplugging, more like 4.2V
[Xperia Z2 General] ottomanhero:
Yes, 4.2 V is the safe highest voltage for use, however charging till 4.1 V is lot better for prolonging battery life.Also like you said, 4.3 V when charged but still plugged in.Which is why you should avoid charging over night.

Voltage status may differ between apps, for example cpu-z shows around 3.4 mV for me when it's 10%
[Xperia Z2 General] Haldi4803:
isn't it the other way around?

Android system gives a Voltage value read from the battery and is calculating the % Battery remaining from this?

So they % You have is depending on the ROM you're using but the Voltage reading of the battery will always be the same?
[Xperia Z2 General] ottomanhero:
Android system reads both the voltage and percentage seperately.This is one of the reasons why battery calibrations is required at times.If you haven't calibrated your battery for half a year or so, it may show 100% at 4.0 V or something lower compared to 100% at 4.2 V ~ which would give you less of your battery.

Voltage reading is not exact mostly, rather approximate.But yes, it is more reliable than percentage and shouldn't differ between ROMs.
[Xperia Z2 General] maddboss:
Thanks for this guide, I have just one question. Is it matters that in how many parts I charge it? For example I charge it from 40% to 80% in one part (I start charging and let it charge until it reach 80%) or charge it in more parts (like I charge it for half an hour and then play ten minutes and then again).
[Xperia Z2 General] ottomanhero:
Older tech batteries had a famous knowledge : "plug once in and charge till 100% without interruption or else battery dies fast"

However, li-ion batteries have no problem with how many times you plug it into charge.

For example you can plug-unplug your charger thrice to charge from 40% to 80%, but then you can also plug it in and charge from 40% to 80% without any interruptions, it will wear the battery just the same.

Only things that matter is that you must not discharge below 3.3 V and try to avoid above 4.1 V, maintain room temperatures while charging and do not use the phone while charging.
[Xperia Z2 General] Haldi4803:
Oh.... and i've made some nice graphs :)

THIS

is the reason why you shouldn't use your phone till it's death.

Under 10% the Voltage drops below 3.6V which is unhealthy.
[Xperia Z2 General] Lasantha:
From what I see new batteries can handle 4.35v unlike older 4.2v models

https://en.wikipedia.org/wiki/Lithium_polymer_battery

& something direct from sony

http://talk.sonymobile.com/t5/FAQ/Battery-time-and-enhancement-features/m-p/347874#U347874
[Xperia Z2 General] AK2H:
THANK YOU VERY MUCH FOR YOUR HUGE EFFORTS!

If I Helped, Leave A Thanks ?
[Xperia Z2 General] Knutselmaaster:
Why do you use mV to indicate the voltage?

The battery goes from ~3.2 volts to ~4,2 volts, not ~3,2 milivolts to ~4,2 milivolts ?

(I use ~ to indicate "approximately")

Other than that, you're quite right that it is preferred to maintain a maximum battery capacity over time to prevent total charge and total discharge.

But on the other hand, the last bit of charging is a lot slower as the battery is charged more carefully so the impact is not that big.

If you use the phone, and not let it charged 100% while the phone is turned off for a longer period, it isn't that bad. Maintaining a high voltage for a long time is bad but as we all use the phone permanently, the time it remains fully charged is quite short.

And we talk about a few percent worse after 1000 full charge cycles. Imagine one full cycle a day (from 0% to 100%) that is a few percent less capacity in three years. Personally I did not have a smartphone for over three years yet and I prefer taking profit of not having to recharge than knowing that I will have a few percent worse capacity when my phone is "old and slow" anyways in 2019.

Don't take my remark as a flame, I'm just giving my opinion ;)
[Xperia Z2 General] AK2H:
For me this guide can't be followed in the real life because it would be very stressful and I change my phone every year and a half so I shouldn't be worried about my battery life (especially SONY devices):D

However, I can't deny that you done a great job writing this thread

WELL DONE :thumbup:

If I Helped, Leave A Thanks ?
[Xperia Z2 General] ottomanhero:
Just an update on the topic, Sony has confirmed they will add "soft charge" which is basically the same thing as following this guide but automated.It is also gonna be in beta versions pretty soon as far as I've heard http://www.xperiablog.net/2016/06/2...soft-charging-landing-this-week-23-5-a-1-238/

*cough* guys, sony wouldn't add such feature if it did not infact prolong battery life.
[Xperia Z2 General] supercfc:
I have a Xperia Z2 D6502 2 years old.

My back cover had become curved due to swollen battery. I ordered a new duplicate battery from here

http://www.amazon.in/Battery-Xperia-D6502-3200mAh-Generic/dp/B01H5HJ79K?ie=UTF8&psc=1&redirect=true&ref_=oh_aui_detailpage_o01_s00

When I opened my back cover for replacing the battery, I realized that battery case had not swollen but there was Air trapped in the thin plastic covering of the battery.

I can easily feel the air. Its like the air trapped in a thin plastic bag.

My new duplicate battery gives me 3.5 hours of screen-on time while my old swollen battery still gives me 5 hours of screen-on time.

Can I remove the air by pricking a safety pin and continue to use the old battery?
[Xperia Z2 General] Lasantha:
big no no in my opinion

https://www.youtube.com/watch?v=w-fgXQUVt8g
[Xperia Z2 General] supercfc:
Haha.. Am not going to pierce the case..

Just the plastic cover..
[Xperia Z2 General] Lasantha:
As far as I know lithium reacts rapidly with moisture or oxygen. I'm not sure piercing would let those in or not :(
[Xperia Z2 General] supercfc:
Okay.. I guess i should stick with the new battery and discard the old :(