yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam General] Markee:
As it's an Orange SPVM3100 and works fine with my Orange sim but not with a Vodafone SIM,I dont think warranty is going to be an option!

I am maybe thinking a hard reset might solve the problem as it does not appear to be a hardware problem, but was waiting for input from the resident techies first!

Mark
[8525, TyTN, MDA Vario II, JasJam General] dan1967:
change radio maybe?
[8525, TyTN, MDA Vario II, JasJam General] Markee:
Weird - just swapped the SIM cards around again (after numerous power cycles / soft resets / SIM swaps) and hey presto it's working again!

How weird!!!???
[8525, TyTN, MDA Vario II, JasJam General] Markee:
Not working again!!

Have now got signal bars, but making outgoing calls very slow, incoming calls going striaght to voicemail....
[8525, TyTN, MDA Vario II, JasJam General] Markee:
One thing I have noticed is that under

Settings | Phone | Network | Set Networks

Vodafone uk keeps is unticked, after ticking and moving to top it then becomes unticked again.

PS I Have also upgraded radio to 1.51

PPS Handset still works perfectly with Orange SIM

Any suggestions?
[Galaxy S6 Edge Q&A, Help & Troubleshooting] jakir01:
Hi,

Is their any mod or way to get sub menu with on off written on international version G925F?
[Huawei P8 Questions & Answers] JoeK025:
hello everyone,

is it possible to port samsung's keyboard to HW P8?

I've seen a tutorial to port galaxy s6 keyboard to s5 and s4, but am not sure if it would be possible, or if there's a way to port it to th eP8.

thanks in advance..
[Huawei P8 Questions & Answers] t0m4s_g1l:
U need to find in internet the apk of the galaxy s6 and install in system apps.. u can see if that works... no one has port that keyboard, or maby not here in xda...

normaly that may work but am not 100% sure.
[G2 Q&A, Help & Troubleshooting] Agus_Young:
This is what happened:

I wanted to flash to a stock rom. So I went to TWRP and wipe everything (system, data, cache, etc.). I did it before so I continued without any doubt.

The problem is that when I tried to flash the stock .kdz I download, Flash Tool 2014 just keeps on stopping on 2% and then it says "Retry" but it just followed to the same.

I tried some other methods, like Flash Tool but the 1.8v and the UpTestEx too, but they don't work.

I also reinstall drivers. But nothing

I wiped everything, so I don't have access yo Recovery, only to Dowload Mode.

This is the log info:

I hope you could help.

Thanks
[G2 Q&A, Help & Troubleshooting] anh676:
Did you change to COM41? If not working, You should try flash tot file first, then flash kdz. Good luck!!!
[One (M8) Q&A, Help & Troubleshooting] CrimsonToker:
Ive had my M8 for about five months now. I bought it online already rooted with s-off, running the "Android Revolution" os. Ive been trying to get Xposed to work ever since. I read the forums, googled my hardware and found the correct arm version blah blah blah. I install in recovery, it says installation successfully, but then when I go into modules it says "framework not installed". I've tried a few versions of the framework, only to get the exact same result. What am I doing wrong here?
[AT&T LG G3] tal32123:
Hi Everyone I'm new here I was wondering if there is an LG g3 d850 rom that has the quickcircle/quickwindow working and is preferably based on AOSP, but if not that is ok too. It should still be supported and that it will hopefully get marshmallow soon. Also all of the features should be working with no bugs. I couldn't find anything myself on Google unfortunately. I really appreciate your answers and thanks in advance.
[AT&T LG G3] TheMadScientist:
Cloudy g3 2.5 stock based. But stable smooth
[Samsung Galaxy Mega] ohdarr:
Hello XDA, I just got this phone a few days ago and decided as I do with every phone to install roms. But I have seen that there are very few to none for the Metro PCS version of this phone. I was wondering if there would be a demand for me to port some of the Galaxy S3 roms over to this device. For instance, probably the first one I would port would be CM 12 because that is my favorite and it is not on this phone. I have also seen people saying that they have gotten the I9205/I9200 version of CM 12 working on this device but I am not having any luck. It just wont boot. But I digress, I just wanted to gauge if people on here would be interested in some updated roms for this awesome phone.
[LG V10 Q&A, Help & Troubleshooting] jrock79:
Anyone willing to make a stock deodexed tmobile rom?
[LG V10 Q&A, Help & Troubleshooting] Rydah:
I made one yesterday at work. I'll see if I could upload it later today.

Sent From My LG V10
[LG V10 Q&A, Help & Troubleshooting] headcreepz:
Please do!!!
[LG V10 Q&A, Help & Troubleshooting] jrock79:
I second that. Please do.
[LG V10 Q&A, Help & Troubleshooting] Rydah:
Okay, finally at work. I have the system ready, just need to zip and upload. Hopefully I'll have free time soon to do it.

Sent From My LG V10
[LG V10 Q&A, Help & Troubleshooting] Rydah:
http://xdaforums.com/lg-v10/development/rom-h901-10c-stock-deodexed-t3252158

Let me know how she runs fellas, I'm unable to test as I am unrooted and such for a swap. Make sure to backup before in case of meltdown.
[T-Mobile LG G4] Mogster2K:
I use Lastpass as my password manager, and the main way to enter passwords in apps is to copy them to the clipboard. Unfortunately, Clip Tray is grabbing them and storing them (probably in plain text.) There's no app called "Clip Tray" on the phone that I can find. I found a reference to "com.lge.software.cliptray" under /system/etc/permissions, but there's no app by that name either. Anyone have a solution? I tried emailing LG support but their reply was no help. Thanks
[T-Mobile LG G4] vsanch24:
I also use LastPass on my phone. However, Clip Tray doesn't grab my passwords. The tray appears and a box gets added, but right away that new box is removed. I have gone back into clip tray after wards and looked at the history and none of my passwords are listed. This is with full T-mobile Stock ROM and the latest version of LastPass for Android. Also using the LG Keyboard.

From other posts elsewhere, the clip tray is part of the LG Keyboard. But disabling the keyboard doesn't turn off the Clip Tray.
[T-Mobile LG G4] ikenvape:
http://android.stackexchange.com/questions/81911/possible-to-disable-lg-cliptray

Since the device is rooted, here's a way of disabling Clip Tray:

Go into Clip Tray and delete all entries.

In the file /system/etc/permissions/com.lge.software.cliptray.xml, change this line

"com.lge.software.cliptray"/>

to

"com.lge.software.cliptray"/> -->

This will put the feature in comment, and will not grant permission for this feature.

Reboot the device.

Note: You might still see the option Paste, Cliptray in your stock LG keyboard, which will not work after this modification but cannot be hidden or removed. A way to work around that is to use an alternate keyboard, like Google Keyboard.
[Nexus 5 Q&A, Help & Troubleshooting] kaushikd:
I am using the phone since 2.5 years. Recently I have updated to 6.0 and the screen time I am getting is hardly 2.5 hours. Earlier I used to get atleast 3.5 hours. But the doze works perfectly fine, hardly 2-3% battery drain over 6-7 hours overnight. But when I start using the phone it starts draining rapidly. Does this means the battery is fine and replacement is not required. Some app might be causing the battery drain? :confused:
[Nexus 5 Q&A, Help & Troubleshooting] Primokorn:
If your battery is faulty then you note huge battery drain overnight and abnormal behaviours (e.g. from 80% to 20% in 10 minutes and back to 78% after a reboot).
[Nexus 5 Q&A, Help & Troubleshooting] kaushikd:
Thanks. That means my battery seems fine only. Will try a fresh install again.
[Samsung Galaxy Star] ItsAnilSingh:
For screenshots, click on Screenshots tab of the dev project.
[Samsung Galaxy Star] Qiangong2:
I sent you an email through GitHub about a month and a half ago... sorry to bug you, but would you be willing to answer it?
[Samsung Galaxy Star] ItsAnilSingh:
I replied to that email long ago. Check github or your email folders.
[Samsung Galaxy Star] Qiangong2:
Sorry, but I have no record of it
[Samsung Galaxy Star] ItsAnilSingh:
Can you link me to that query in github?
[Samsung Galaxy Star] Qiangong2:
It wasn't a GitHub query. I sent it from my personal email to yours
[Samsung Galaxy Star] Qiangong2:
Thanks for trying. After about ten attempts, I believe I finally made a test build :) I used your GitHub trees, just so you know. I hope that's fine
[Samsung Galaxy Star] ItsAnilSingh:
My Cyanogenmod 10.1 device tree? Its open source, you can use it as you like with a little credits when you release the stuff.

By the way, what device are you compiling for? How was the test build? I moved to CM 11.0, abandoned CM 10.1 because of RIL issues.
[Samsung Galaxy Star] Qiangong2:
Okay, some people just want their explicit permission before using it. Just checking is all.

I'm still building... I have 2gigs of RAM and no SSD. It will take a while. Also a dual core CPU. And no ccache. Yay. Will report tomorrow if it works. So far no build errors though. I'm building CyanogenMod 10.1 for the s7262. I plan on trying an Ubuntu touch port if this works.
[Samsung Galaxy Star] Qiangong2:
10.1 won't work. Now trying ishantvivek's cm-11 device tree
[Samsung Galaxy Star] Qiangong2:
Snip
[Samsung Galaxy Star] ItsAnilSingh:
Sorry for replying late but I was busy in personal works, hence couldn't login and reply.

10.1 has RIL and wifi issues, that is the reason I am not releasing the ROMs. Switched to CM11.0 for the same reason.

Use kernel source from this repo of mine. It has fixes https://github.com/ItsAnilSingh
[Samsung Galaxy Star] Qiangong2:
Sorry about that last post it was about 11pm and I was beat :(

Here's what the code boils down to:

external/e2fsprogs/e2fsck/problem.c:1201:4: warning: missing initializer [-Wmissing-field-initializers]

Also, kernel make error 2
[Samsung Galaxy Star] ItsAnilSingh:
Looks like you have outdated code for cm11.0

Delete external/e2fsprogs folder from cm source.

Download the android_external_e2fsprogs-cm-11.0.zip file from the following link and exact it in external directory of cm source.

https://github.com/CyanogenMod/android_external_e2fsprogs/archive/cm-11.0.zip

Rename android_external_e2fsprogs-cm-11.0 folder to e2fsprogs and compile again.
[Samsung Galaxy Star] Qiangong2:
Okay. Fixed that. Now I'm getting RIL errors under classes debug jar. They are all under the device framework. I've tried using your tree, FireLord1's tree, ishantvivek's tree, and even 123vipulj's tree. All using your kernel (which builds the recovery and boot image fine).

I've attached the errors
[Samsung Galaxy Star] ItsAnilSingh:
I did not update my device tree for CM-11.0 yet. The tree you are referring is for CM-10.1, all those people you mentioned use my tree atleast as a base. So, they will definitely generate error for RIL.

Instead, download the file from below link and then replace it with the existing one in device tree and compile again. No need to "make clean".

https://github.com/SamsungBCM-Cyano...android/internal/telephony/SamsungBCMRIL.java
[Samsung Galaxy Star] ItsAnilSingh:
Update: The file I uploaded was corrupt. Compiled again the recovery from source now and uploaded the working file. Please check the first post for updated link. Replaced the old link with newer one.
[Samsung Galaxy Star] Qiangong2:
Thanks, it's building now :) just trying to figure out some minzip errors and then it should be good to go.
[Samsung Galaxy Star] Qiangong2:
Everything is building, but I'm always getting minzip errors where the file is inflated to the wrong size. It won't install correctly. Any ideas? I've tried redoing everything from scratch. Deleting the source and redownloading it. Redownloading repo and creating a new local manifest. Even tried git clone the device and kernel source.

P.S. I'm also working on 6.0 aosp port just for fun :)

Qiangong2
[Samsung Galaxy Star] ItsAnilSingh:
Sorry, didn't get the error?? I think discussions regarding CM11 is allowed in this thread as it is in development sections. Am I right? Or the moderator will delete the posts??
[Samsung Galaxy Star] Qiangong2:
As long as you (The OP) are okay with it, it should be fine. You're right this is development :)

I've been building on xubuntu 12.04 so that may be the problem. I'm updating now to 14.04.
[Samsung Galaxy Star] Qiangong2:
Could the reason that it isn't working be because I'm using the ./extract-files.sh on stock firmware?

UPDATE: still getting the minzip error. I've found one post (on the miui forums) that addresses the file mismatch error, but it doesn't work. I've tried on twrp and cwm, but it still doesn't work. I used to get stuck at the logo, but then I tried changing the boot image from the one I built from source to the star kernel v2 you made, I get a white screen after logo. I believe it's a problem with the actual ROM, but I can't figure out what. Any ideas?
[Samsung Galaxy Star] ItsAnilSingh:
You need to have newer (not the latest) stock rom in order to use star kernel, else it will generate white screen. Baseband is changed in newest version of kernel source, hence the requirement.

As for the compilation, I have compiled another build of recovery just now. Will update the thread with new link soon. That being said, I compiled a test build using new tree. This is the proof that CM 11 is getting compiled without any errors. I have not uploaded the new device tree yet, but will do so after compiling a working build.
[Samsung Galaxy Star] ItsAnilSingh:
CWM Recovery v6.0.5.1 v2 is now available for download. Check 1st post for changelog.
[Samsung Galaxy Star] Qiangong2:
I'm missing something then. I'm having a problem with the system apps on compilation. The boot.img works and boots fine. The deskclock.APK is where it breaks, but when I remove it, it breaks upon trying to inflate the email and exchange APKs.
[Samsung Galaxy Star] ItsAnilSingh:
You mean you can get past the boot logo and can see Cyanogenmod boot animation of CM-11.0? That's a great step. I may help you. I don't have access to Ubuntu as of now but surely can help you get past the bootanimation.

Kindly visit my xda profile and then add me at facebook by following the facebook link. We can discuss this further if you want.
[Samsung Galaxy Star] Qiangong2:
Stuck at boot logo, log shows minzip errors. I have the red exclamation point in the corner. The total size is 241.30MB. Is that right? Or should it be more/less

If you have a wechat we can talk. If you have a QQ as well. You can always sign in to wechat using Facebook ID
[Samsung Galaxy Star] ItsAnilSingh:
Same in my case too. I thought it was because of the deodex entry, I removed that entry from device tree and compiled again.

This was the result even after that change. Looks like we both have got the same issue.
[Samsung Galaxy Star] Qiangong2:
Okay :) SNIP. It looks like the s5282 uses an SP8810 processor. Oops.

Another idea, could the filesystem be set to the wrong size? The userdata one specifically?

On a side note, when will you add the vendor repo to the ItsAnilSingh repo?
[Samsung Galaxy Star] ItsAnilSingh:
Its not at all related to system size. Its the inflated sizes that differs before and after making the zip file. Most probably related to our build system.

What's your system config?

Edit: Vendor repo will have to be cleaned first. It will be up once we succeed flashing the build on our mobile. :)
[Samsung Galaxy Star] ItsAnilSingh:
CWM Recovery v6.0.5.1 v3 is now available for download.

Changelog: v3

1) Now "Home" button will also act like "Select" button

2) Rainbow mode enabled, you can now see the rainbow changes effectively. Keep scrolling through the menu at least 5 times fully and experience the fun.

3) SELinux policies updated

4) Added "init.recovery.sc6820i.rc" for better compatibility

5) Now using default stock samsung kernel source (no changes for drivers etc) with fixes for compiling "Cyanogenmod" and selinux changes in defconfig

6) Other misc recovery changes

See post 1 for instructions.
[Samsung Galaxy Star] Qiangong2:
Snip.
[Samsung Galaxy Star] Qiangong2:
On my computer, I'm running Ubuntu 15.10 with a core i7, 8GB of RAM, single SSD. My builds go pretty fast, better than the old 2GB RAM 12.04 I was using when I first started working on the S7262 :)
[Samsung Galaxy Star] ItsAnilSingh:
Try this:

-> Unzip the cm zip archive in ubuntu to a folder

-> Monitor for any error that you may come across

-> DO NOT change anything in that extracted folder

-> Make a zip of the extracted files again of that folder and sign it, follow this guide

-> Try flashing again the new zip and see if the new zip will flash fine or not

Things to learn from this steps:

-> If the new zip gets flashed completely then there is something wrong with the scripts used in cm source or our system or something involved in making and signing the zip

-> If the new zip fails just like before then the minzip of cwm is to be blamed, we have to solve this at recovery level

-> I will suggest you one more possible way of checking whether is it cwm thats causing the problem after your next reply
[Samsung Galaxy Star] Qiangong2:
I got installation aborted... log says volume keeps changing from 3 (checking to 4 (mounted) then back again. It won't even get to minzip. I've tried with multiple sdcards as well. It doesn't do it with other ROMs though.

I lost my data in a blackout last night, so when I redownload the source again, I'll do another build to make sure.
[Samsung Galaxy Star] ItsAnilSingh:
You lost your mobile data by following the above steps? Sorry for that.

I am trying to skip that error by using another method.
[Samsung Galaxy Star] Qiangong2:
I've rebuilt and there are no inflation errors, but it stops after extracting system/xbin/zip.

It says:

script result was [/system]
I:Cannot load volume /misc
I:Can't partition non mmcblk device /devices/platform/sprd- sdhci.0/mmc_host/mmc1
[Samsung Galaxy Star] ItsAnilSingh:
What did you do to overcome that inflation error? Compiled again with same device, kernel and source and you got it working this time?

I would have helped you if there was any reference to device sources of your build.
[Samsung Galaxy Star] ItsAnilSingh:
[MENTION=6124463]Qiangong2[/MENTION] Your facebook profile link please? We can message there to notify each other about our posts here at xda. I visit facebook more than xda.
[Samsung Galaxy Star] Qiangong2:
[MENTION=6391897]anilsingh1605[/MENTION] I've been using Fire-Galaxy's device tree and your kernel source. I've attached a copy of the recovery log I always get when I flash. No minzip errors. (nothing important happens until line 215)

One thing that jumps out at me is that it says on lines 232 and 233:

Not backing up files from incompatible version: 11
run_program: child exited with status: 127

Also on line 248:

warning: wipe_block_device: wipe via secure discard suppressed due to bug in EMMC firmware

Any Ideas?

Update: it may be because we are using the generic SamsungBCMRIL.java instead of the SamsungSPRDRIL.java
[Samsung Galaxy Star] Qiangong2:
So, I've done more troubleshooting, and it builds and installs. Only problem is that it won't boot beyond the Galaxy Star Plus GT-S7262 screen. It stays stuck there. It may be a problem with the tree...
[Samsung Galaxy Star] ItsAnilSingh:
There were elections in my hometown, so didnt saw your replies so have not replied.

Took a small peak at the log you provided and it shows minzip errors? As for the other errors, will read the full log and reply again from ubuntu, currently replying through windows. Maybe changes in ramdisk is needed.

Looks like we both have the same problem, push your modified tree to github. Will try and see if any changes can be done to your tree as well. I will cross verify my tree with yours for the same.
[Samsung Galaxy Star] Qiangong2:
It's not minzip errors, it's just notifying you that it has successfully extracted the file. It would say minzip error if it was an actual error.

I use your kernel tree and Fire-Galaxy's device tree. Both are available on Github. I haven't made any changes to them.
[Samsung Galaxy Star] Qiangong2:
The problem is with the ROM not initializing. It isn't a radio problem, and it isn't a boot.img problem. Changing to cm recovery doesn't make it work either. I feel like we are missing a proprietary file.
[Samsung Galaxy Star] ItsAnilSingh:
Told you that I just had a peek at the log, not have fully gone through it. Now checking the log.

I suggest you to use CWM and TWRP one after the other made by Firelord for our device. Maybe you will get success.

He posted proof of CM11 getting past the bootanimation at facebook group. Try his recoveries and see.
[Samsung Galaxy Star] Qiangong2:
I've been trying on his recoveries, just installed his latest TWRP recovery. CWM doesn't work.

---------- Post added at 09:05 PM ---------- Previous post was at 08:55 PM ----------

UPDATE: TWRP doesn't work.
[Samsung Galaxy Star] ItsAnilSingh:
CWM and TWRP, both, doesn't work? I didn't get you. Those recoveries doesn't flash or those recoveries gives the same error as above.
[Samsung Galaxy Star] Qiangong2:
Same as before
[Samsung Galaxy Star] Qiangong2:
[MENTION=6391897]ItsAnilSingh[/MENTION] I found a new device tree on github for the logan2g. It's for 10.1, but we may be able to copy parts of it.

https://github.com/tailormoon/device_samsung_logan2g

Qiangong2
[Samsung Galaxy Star] ItsAnilSingh:
Forked from my tree. Saw commits, they are of no use.

I am really busy these days, but anyhow got sometime to check back xda. I will soon compile a build and test it with modified tree and a new twrp is in store to be released.
[Samsung Galaxy Star] nairitmukherjee0007:
just wanted to know if this recovery will work in my GT S5282..?
[Samsung Galaxy Star] ItsAnilSingh:
There is already a recovery available for your device in this very forum. Please check the Android Original Development section of this device forum.
[Samsung Galaxy Star] Qiangong2:
Github claims your tree has been updated, but doesn't show the commits. Also, I'm now getting sub-make errors related to the arm-eabi-4.6.
[Samsung Galaxy Star] ItsAnilSingh:
I havent pushed the new tree yet, probably will push to soon. The users might be updating the tree on their accounts after forking my tree. Hence the notification from github.

And as for the errors, I am not sure what tree you are using now. So, have no idea.
[Samsung Galaxy Star] Qiangong2:
Sorry, I'm using Fire-Galaxy's device and vendor trees and your kernel tree.
[Samsung Galaxy Star] rony raj:
thanks for cwm
[MDA III, XDA III, PDA2k, 9090 General] laura_kim:
:( :confused: HI,

I'VE UPGRADED MY BA WITH KitchenAKU3.5v2-XPLODE

tHEN I UPGRADED RADIO TO 1.15.

THE PROBLEM WITH MY BLUETOOTH (BT) HEADSET IS IT'S ABLE TO WORK WHILE USING IT WITH THE PHONE BUT WHEN I TRY TO LISTEN TO MUSIC USING WINDOWS MEDIA PLAYER OR TCPMC PLAYER IT ALLOWS ME TO HEAR JUST FEW SECONDS OF THE SONG AND THEN IT BECOME AS MUTE.

IF I CLOSE THE PLAYER APPLICATIONS (BOTH WMP OR TCPMC) IT STARTS AGIN WORKING ALLOWING ME TO HEAR ALSO THE "TAP" SOUNDS WHEN I HIT THE SCREEN WITH THE PENCIL.

I HAVE TRIED USING ALSO AN OTHER KIND OF BT HEADSET AND THE REACTIONS ARE THE SAME.

NOTE: WHEN I CONNECT TO THE HEADSET BY BT THE MANAGER SHOWS ME THE AVAIABLE SERVICES FOR IT WHICH ARE "HEADSET" AND "WIRELESS STEREO" (AND CONNECTING IT IS POSSIBLE TO HEAR ALSO THE CLASSIC CONNECTION SOUND BY THE HEADSET).

Please, how can i solve the problem? do i need to use an other flash rom ?

PS: SORRY FOR MY ENGLISH ; I'M ITALIAN
[MDA III, XDA III, PDA2k, 9090 General] janicic:
I am having the same problem with the Wireless Stereo BT

And having a big head ache out in the nowhere!

Could you find the answer?

My MSN:

janicic@yahoo.com

Greetings from China!