yashsingh1/xdaforums huggingface dataset:
[Xperia SP Android Development] christiano88:
Yes!

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

For some reason, in build 3 the SDcard doesn't show up on the computer when you plug the USB cable (sometimes it does work, but most of the time it doesn't).
[Xperia SP Android Development] Guillemp97:
Ok, thank you all guys, I think is most valuable having xposed rather than ART :o
[Xperia SP Android Development] neXus PRIME:
[MENTION=5579865]MrSteve555[/MENTION]

Does this work

https://play.google.com/store/apps/details?id=in.championswimmer.twrpxperia&hl=en
[Xperia SP Android Development] MrSteve555:
[MENTION=4350492]neXus PRIME[/MENTION]

Probably it won't work, but I'm going to try that. If it doesn't work, I still have an idea.
[Xperia SP Android Development] neXus PRIME:
How did this guys flash and use a kernel from fotakernel on LOCKED BL?

http://xdaforums.com/xperia-u/u-development/dev-booting-custom-kernel-fota-t1969804
[Xperia SP Android Development] MrSteve555:
[MENTION=4350492]neXus PRIME[/MENTION]

Flashing things to FOTAKernel work. Altrough extract_elf_ramdisk tools won't work. So the only way to boot from that partition is to:

1. Flash the recovery.img.

2. Mount it on some mountpoint like /fota

3. Chroot to it during the boot process.

But to mount it I think there is a change required in fstab.qcom. I will try that soon.

Oh, I missed the part when they talk about kernel, not recovery. Nevermind that info up^. There is no way for booting from FOTAKernel other than kexec method.
[Xperia SP Android Development] paulux2:
nexus prime i think you should remove lbl only from op and name of 3d because it works Also con ubl (i didnt flash any custom kernel and works perfectly

Sony Xperia SP, PA 4.4 final
[Xperia SP Android Development] MrSteve555:
[MENTION=4350492]neXus PRIME[/MENTION]

So, I'm trying to mount /dev/block/platform/msm_sdcc.1/by-name/FOTAKernel on /fota/ and mount command gives me "No such device" error, even when I'm using commands like that:

mkdir /fota
chmod 777 /fota
mount -o defaults -t emmc /dev/block/platform/msm_sdcc.1/by-name/FOTAKernel /fota

Other arguments give me "Invalid arguments" error. What's wrong with it?

EDIT: Nevermind, I've just noticed my stupidity...
[Xperia SP Android Development] neXus PRIME:
Dear, the problem is, people are not as smart as you. They will have some issues installing it on UBL and spam the thread.

But ok, i am changing it to LBL UBL
[Xperia SP Android Development] neXus PRIME:
Any video will be good enough. But not by screen cast... FPS should be ok.
[Xperia SP Android Development] MrSteve555:
I tried many things, read many things and FOTAKernel recovery still isn't working. Extract_elf_ramdisk should be in the kernel image and we have locked bootloaders so it's not possible for us. Also "my" way for chrooting and mounting also wouldn't work.

But after reading and scrolling, reading and scrolling I noticed one thing - FOTAKernel is actually a second kernel.

Also, this kernel can be booted without kexec. The only thing is that no one knows how to boot from that partition, maybe tracing down the commands sent by Sony Update Center app(that thing can boot into that kernel) would help.

Theoretical instructions to make DoomKernel work on LBL:

1. Install .201 CE1 build,

2. Flash DoomKernel to FOTAKernel partition.

3. "Update" to .205 via OTA.(it's not actually updating, because there's now no fota-ua recovery, so it should boot DoomKernel rather than that recovery).

It looks easy. Too easy. Anyone wants to try it :p?
[Xperia SP Android Development] ldysc:
guys how do you find this rom? is it good? is there any random freezes? and is it worth to install after cm11?

sorry for my bad english.
[Xperia SP Android Development] neXus PRIME:
I think you should. Seems safe enough, but will be a great stride for LBL folk. Sooner or later, the reboot to FOTA will be solved.
[Xperia SP Android Development] neXus PRIME:
Try yourself. It will surprise you.:good:
[Xperia SP Android Development] MrSteve555:
If no one tries that till tomorrow, I'll be my own guinea pig. It is safe, indeed. In worst case scenario, Update Center will refuse to boot into modified FOTA.
[Xperia SP Android Development] paulux2:
best ROM for xsp, maybe vanirAOSP beat this. there isnt the freeze problem and the battery isn't too worse than stock, just a bit. in standby is really better when you use the phone it drains faster than stock.

Sony Xperia SP, PA 4.4 final
[Xperia SP Android Development] orangpelupa:
downloaded the ROM, will try tomorow to flash... after i deleted some things from SD Card to make full backup and app backup.

hopefully everything will be fine after app restore :D

btw does the glove mode work in this ROM?

i will try it tomorow with Glove Xperia app too, but it will be nice to hear the experience from other people. In case its only my phone that bugged.

EDIT:

wait a sec, i read on 1st page i need latest CWM. And after searching this topic i cant find the Download link.

where is the latest CWM? can i use this one? http://xdaforums.com/showthread.php?t=2649923 but thats for 4.3 and im on 4.4 :/

thanks
[Xperia SP Android Development] neXus PRIME:
Use it
[Xperia SP Android Development] MrSteve555:
[MENTION=4350492]neXus PRIME[/MENTION], [MENTION=5765508]bagyusz[/MENTION]

So, I tried booting from FOTAKernel. It doesn't work (yet).

Anyway, I've gathered some infos:

1. Actual FOTA recovery is in kernel. The whole OTA-update system boots into that mode by using commands written in cache. After that, it does some checks, and if everything's ok, it boots to FOTAKernel partition to update kernel.

2. The commands are logged, so I think I've found a method of booting into fota mode without any Sony apps. The sad thing is that gives us nothing.

3. I've copied some logs from /cache, I've also captured the .205 OTA(it's in .pkg format), and I've captured a logcat. It could be useful for you.

(I'll attach them to the post later, I need to investigate them by myself).

EDIT: Here are the logs and some misc stuff I've found:

https://mega.co.nz/#!acRF1Yia!fdavwo1WN_QftSlcOU17V70q3BOcALkRS2GtXycY3po

BTW, I've just discovered that we actually need to gather logs from complete update, not from one, that failed. In that way, we can get the command needed to boot into FOTAKernel partition. And I'm so smart that I've just restored PA nandroid backup :banghead:. I'll try that later.
[Xperia SP Android Development] neXus PRIME:
fotakernel or no fotakernel, where iz my V-D-O.

MUST HAV VDO Ree-V-oOZ
[Xperia SP Android Development] MrSteve555:
I've just reflashed .201 and got through the OTA process. It's split into four stages, and at the stage three, the FOTAkernel is booted. I still need help with getting into that boot process, because the logs after that are being overwritten by the stage 4. And I don't know how to get earlier logs, because during OTA there is no access to anything that would give us the sufficient data. I know we can get it to work but I need serious help...

Oh, [MENTION=4350492]neXus PRIME[/MENTION], I'm gonna record a V-D-O (:D) "review fo the ROM in a few minutes.
[Xperia SP Android Development] orangpelupa:
i wiped everything and flashed this ROM. But i cant get cellphone signal (im roaming out of country).

Then i change the network from LTE to 3G, or 2G. if i manually search for network, it stuck in "searching". Its not frozen, it just searching endlssly.

i also already tried backup and restore via CWM.

any idea whats wrong?

(previously i was on LBL Slim KitKat and kernel 205)

thank you

EDIT:

i reflashed 205 kernel and now waiting "serching" network. I will put it like that for 30 minutes and report here the result :)

EDIT: after about 10 minute, the "searching" stopped by itself and still no network.

EDIT:

i can remove my SIM card while the phone ON and it does not complain. Usually it will say that it need restart.
[Xperia SP Android Development] Pachanka:
Hey,

i had exactly same problem 30mn ago, with no sim card, no imei no baseband founds

i redone all the procedure and now that works......BUT now i can't activate WIFI, still witing on "activating WIFI"
[Xperia SP Android Development] MrSteve555:
[MENTION=4664949]orangpelupa[/MENTION]

Go into settings > info and check if the baseband version number is being shown. If it shows up correctly, you just don't have signal, it's not ROM's, but your operator's fault. [MENTION=4350492]neXus PRIME[/MENTION]

Brace yourself, the video is uploading.

Caution: quality is bad, voice quality is bad, my English skills + accent are just 1/10. I'm definitely not born to make YouTube videos...

Link will be here in a few minute.

http://youtu.be/DQDBe1_VE6o
[Xperia SP Android Development] orangpelupa:
[MENTION=5579865]MrSteve555[/MENTION]

it say baseband unknown

[MENTION=2466656]Pachanka[/MENTION]

okay, i will try flashing again :D

EDIT:

awesome, i flash it again and now basebad is ON and i can connect

thanks Pachanka :D

EDIT:

ugh this is my unlucky day. My application backup is corrupted, gotta restore back to SimBean and back to this rom again. Hopefully this time all good :D
[Xperia SP Android Development] air001:
Have anybody experienced that the soft back button doesn't work? I see the touch response but doesn't happen anything. I have to switch onto another running task to make it work again.
[Xperia SP Android Development] neXus PRIME:
Thanks a lot for the review. I am gonna switch to my rom v soon.

By the way, steve we have to find a way to make the ROM zip stable. The baseband issue needs to be fixed in next version. Many people are hesitating to switch to LBL aosp-based roms just because of these install issues.

We have to find root cause, and compile fixed versions of philz cwm twrp in a single package for them to use.
[Xperia SP Android Development] MrSteve555:
These baseband issues are also present in stock-based ROMs. Have a look at PureXSP thread: there is a baseband fix in the OP. It's just /system/etc/firmware folder made flashable, but it's still small step into fixing that issue.

Also, I think there is a way to include the fix suitable for PA in the ROM zip, it's not much to modify. I'll upload it when I'm done with updating hijack.sh to include [MENTION=1262249]dssmex[/MENTION] newest recoveries(these are the most stable ones I've tested).

Combined with my "fix", the installation should go smoothly on any recovery, and if an user flashes your ROM, he/she will get recoveries that will allow seamless updating.
[Xperia SP Android Development] neXus PRIME:
OK. Good. I am updating the "pa" branch with more fixes. Just fork and pull. Remember, i am placing my latest hijack.tar in huashan/rootdir/system/bin/hijack.tar

Only change this binary and pull request.
[Xperia SP Android Development] MrSteve555:
[MENTION=4350492]neXus PRIME[/MENTION]

I've just updated recoveries, cleaned up the hijack.tar, added TWRP, and opened a pull request.
[Xperia SP Android Development] neXus PRIME:
I was wondering, in hijack.sh, why cant we use the cwm_ramdisk portion for philz and twrp??? philz_ramdisk seems to be missing a lot of portion from cwm_ramdisk function. I think you should test using cwm_ramdisk function call for all three recoveries, that way we dont need 3 functions.

You have already done this.
[Xperia SP Android Development] nudelaug:
Please Help me

I had install and have no Baseband

and now i will retour to another Rom but i had no CWM and caanot inst.CWM
[Xperia SP Android Development] neXus PRIME:
Also, the hijack.tar u changed, have you tested it to be working on your phone???
[Xperia SP Android Development] neXus PRIME:
You have recoveries, dont worry. Just after the red led stops dancing and there is a short vibration, press volume up key and u will enter recovery.

But, if you want to fix baseband, just backup and restore a nandroid in CWM recovery. To enter that, press volume down during above sequence.
[Xperia SP Android Development] MetalOllie:
Little help, if someone would be so kind..! I seem to have stuffed up my system sounds, ringtones etc, in as much as none of them play. I extracted the ogg files from my Nandroid backup and put them in the appropriate folders (ringtones, alarms, notifications), however now none of them are playing.. The phone is silent. Speaker is ok, as I can play music just fine.

I suspect I've done something to permissions, although have read conflicting reports as to what the correct permissions should be.

Update.. They are all back.. Sort of. I cleared the Media storage in apps, so they all appear in the list again after a reboot, however when selecting a ringtone or sound, they all make the same sound.. A "ding". The files themselves are all different sizes, so there's no duplication.

Any idea please?
[Xperia SP Android Development] nudelaug:
Ah Volumen up thanks
[Xperia SP Android Development] MrSteve555:
[MENTION=4350492]neXus PRIME[/MENTION]

Your "Attempt Baseband fix" commit won't fix it, it will still be the same and it makes the dev tree unclean.

I think something like that:

package_extract_dir("system/etc/firmware", "/system/etc/firmware");

Added at the end of updater-script would fix the baseband. I'm not sure though.
[Xperia SP Android Development] neXus PRIME:
You didn't see this is huashan.mk, did you?

This will effectively do the same thing you are saying. So it should fix baseband. I will have to test myself though. Or I can upload a test build.
[Xperia SP Android Development] sarkar1990:
Can you link me to your git? Can't find it in the OP. Sorry if I missed it.
[Xperia SP Android Development] neXus PRIME:
https://github.com/neXusPRIME

Ask me before releasing anything here using the tree.:good:
[Xperia SP Android Development] sarkar1990:
Sure, I just wanted to try and build PA for SP. Just wanted to verify if the dependencies were correct. If I release anything, I will ask you. Thanks!
[Xperia SP Android Development] neXus PRIME:
Dont release PA. Use it for yourself if you want.

But yeah, you can change it for PAC/Omni/AOSB etc and release that.
[Xperia SP Android Development] MrSteve555:
[MENTION=4350492]neXus PRIME[/MENTION]

I tried fixing the baseband my way and PureXSP way and it doesn't work. The weirdest of all, even TWRP doesn't flash the baseband properly in the latest build.

We need to check every possible way, so maybe your method will work?

Also that updated recovery is a no-go until we fix basebands, because only bagyuszs CWM can "backup-restore fix" baseband, and I've deleted it and added CWM Touch...
[Xperia SP Android Development] Emma22288:
When i use cwm i dont have any problem with baseband. Its working perfect right after flashing
[Xperia SP Android Development] orangpelupa:
about baseband, it seems completely random to me.

currently i going back and forth between my backup of SlimBean and backup of this ROM. Sometime after restoring whichever backup, my baseband become unknown. its random when hapenend to me. weird.
[Xperia SP Android Development] MrSteve555:
Maybe we should use set_metadata instead of set_perm? All the recoveries in my updated package support it, so there won't be any problem with it.

Also set_perm is really old edify command, and set_metadata is fairly new. My theory is that selinux changes just won't allow us to use certain files without certain attributes(I didn't check it, it's just a shot in the dark). I've chcecked official CM nightlies - they use set_metadata and the baseband issues aren't present. So, maybe removing SKIP_SET_METADATA flag and patch and also using CM releasetools will fix it?
[Xperia SP Android Development] nudelaug:
Hello i come from Existenz

Paranoid is a cool Rom but how can i install 5 Button Navigation Bar

sorry for bad english
[Xperia SP Android Development] MrSteve555:
[MENTION=4350492]neXus PRIME[/MENTION]

I've finally found a connection: before that skipe metadata patch there were absolutely no problems with baseband/wifi hotspot. But after bagyusz introduced it in 05.28 build, the whole baseband madness started.

Also:

PhilZ doesn't support set_perm.

TWRP supports both.

CWM doesn't support set_metadata BUT CWM Touch has been updated to support it.

So now it's clear why baseband doesn't work - it's a permission issue.

I'll try to push a fix to my github in a few minutes.

EDIT: Build #2 has the fix inbuilt. I'll try it.
[Xperia SP Android Development] Oblox:
Keep up the great work you two!
[Xperia SP Android Development] ParaSense.:
any working fix for no baseband?
[Xperia SP Android Development] MrSteve555:
Tried updater-script from build #2(it's with set_metadata) and guess what? Everything is working now, with TWRP and PhilZ. Great :D.

EDIT: Spoke too soon, baseband works, but no WiFi hotspot...
[Xperia SP Android Development] Oblox:
Please read the thread or use the search tool, the fix has been posted numerous times and a longer term fix is being discussed here and now.

Flash in CWM, backup and then restore the backup.
[Xperia SP Android Development] Emma22288:
It's something good anyway :D
[Xperia SP Android Development] neXus PRIME:
Most LBL users use the LBL recoveries by dssmex, so we only need to find a way to support those.

Once my rom flashes ok with them, then it is ok.
[Xperia SP Android Development] MrSteve555:
We also have these recoveries integrated into ROM, so they are the priority.

Using set_metadata at least baseband is fixed on them.

With set_metadata WiFi hotspot doesn't turn on and shows an error.

I'll try to find a fix for that(I think it's my fault and it's finally fixed now for everyone, I screwed up something when flashing over and over, so it may not be an issue anymore).

EDIT:

Yep, I screwed up some files in /data/, that's why it doesn't work for me. We can count wifi hotspot as fixed. I've opened a pull request with required changes.

EDIT2:

I clean flashed my modified Build #3(I've added updated hijack.tar and updater-script from build #2) with PhilZ and TWRP:

WiFi hotspot and baseband are working as they should. So my commit included in pull request will work fine. :good: One thing worth mentioning - you removed bagyuszs set_metadata patch and few days after that you synced his changes and everything was reverted to its previous state.
[Xperia SP Android Development] neXus PRIME:
I am rejecting your commit. I have corrected the files in hijack.tar and the meta data changes before you. Plus, i am going to keep the firmware files i added, just for safety. No harm in few mb of files. Will commit changes after i flash rom myself.
[Xperia SP Android Development] Shywim:
Would this fix WiFi and GSM reception? I am still on build #2 and have 3 bars instead of 4 for WiFi while I am just next to it (It was full on stock and existenz) and also I still have half of the GSM reception I had on stock & existenz (as I said at the start of the thread).

I still haven't updated because I am using ART and rebuilding dex-cache is extremely longer that on dalvik and I need to keep my phone running for now...
[Xperia SP Android Development] Oblox:
Just out of interest did you check the actual strength of the signal in decibels or basing this solely on the bars? Im just curious as its not been unknown for people to rig the signal strength to different levels so it shows better than it is. Not sure if this is something manufacturers can change or if its android base settings.
[Xperia SP Android Development] MrSteve555:
So, you reverted to the older recoveries, didn't you? I think using newer recoveries is better, they have some fixes included but whatever, it's your ROM, your decisions. If you corrected metadata changes before me, it's good, we will have working ROM on every recovery. And for these files you added:

https://github.com/neXusPRIME/android_vendor_sony/tree/master/huashan/proprietary/etc/firmware

They are included here, so I don't see a reason for keeping them in two places simultaneusly.
[Xperia SP Android Development] neXus PRIME:
check again tell me where is	a225_pfp.fw

And i will use old hijack and then your new hijack if it works ok, then include your pull request. Have you tested your own hijack.tar?
[Xperia SP Android Development] MrSteve555:
There is no need for a225_pfp.fw. It's for adreno 225 GPU. With our current drivers, we only need a300_pfp.fw, which is located in /system/vendor/firmware:

https://github.com/neXusPRIME/android_vendor_sony/tree/master/qcom-common/proprietary

I know that file is included in stock ROM(and I don't even know for what reason it's there), but we have different drivers on CM.

I've just checked and your hijack.tar includes changes to ramdisk which I didn't include. In my hijack.tar I've just fixed a small typo in hijack.sh and I've made use of illumination bar in recoveries. Just a cleanup and it looks nicer now.

BTW, I've tested it and it works. I can update it with your changes and then you could include my pull request.
[Xperia SP Android Development] neXus PRIME:
ok sure. make a new pull request. i'll merge it asap.
[Xperia SP Android Development] MrSteve555:
Should I open a pull request with only the hijack.tar change or also with my other changes?
[Xperia SP Android Development] Shywim:
I actually have -100 dBm... I'm not sure but I think it was higher than -60 when at home...
[Xperia SP Android Development] neXus PRIME:
Hold on, im merging your commit. Will update ramdisk later.
[Xperia SP Android Development] neXus PRIME:
[MENTION=5579865]MrSteve555[/MENTION]

I have added all your changes and new hijack.tar. Credits in commit.

I have also reverted the Baseband fix commit as it made my build unstable. Had to reflash stock ftf n root n recovery. Nightmare.

Hopefully i'll do a fresh build tonight with this new stuff and we will have no more baseband issues if people use latest cwmtouch philz n twrp recoveries.
[Xperia SP Android Development] Vivaz90197:
4 me on DooMKerneL not work data/sim.
[Xperia SP Android Development] MrSteve555:
Read this^
[Xperia SP Android Development] neXus PRIME:
I'm finally on my OWN Rom.

Hover and peek are SO SO Cool.

Dual Tiles Very very useful.

And has anyone used the screen peek function??? Settings>Buttons>Screen Peek. Camera key half press toggles screen on off. :)

PA rox !
[Xperia SP Android Development] Emma22288:
I cant find the lockscreen seen throug option. First i dont liked PA but after a little use i actualy love it.
[Xperia SP Android Development] Oblox:
Is there an easier way to set the lockscreen image than going through the CM theme chooser?

I find it doesnt work (doesnt set the image position correctly) half the time and just doesnt set it the other half. When I set my background for my homescreen it doesnt set the lockscreen and im sure it used to.
[Xperia SP Android Development] MrSteve555:
[MENTION=4350492]neXus PRIME[/MENTION]

Congratulations! Let the PA be with you :p [MENTION=4720877]Emma22288[/MENTION]

I don't think that option is present on devices other that Nexus 7,10,4 and 5. [MENTION=4888117]Oblox[/MENTION]

There's no other way to set the lockscreen wallpaper. Yes, it's really annoying, but it actually set my wallpaper cut in a half, so it actually looks better :). You know, more "artistic" way :p

To all:

As the new #4 build will bring some changes to flashing process, you need to update the recoveries:

https://mega.co.nz/#!7UQCECjK!ySx2_BH-nHNO_SxTC7xJEV_7X4ICYf6vD6Rin3bfvbI

When #4 arrives, you will be able to flash it with PhilZ, TWRP or CWM Touch without any problem, when you flash this :good:

So, to prepare for ROM update:

1. Flash the package.

2. Done.

With this recovery pack press vol+ to access PhilZ, vol- to access TWRP, cam button to access CWM.

And [MENTION=4350492]neXus PRIME[/MENTION] I've updated the hijack.tar with your ramdisk aaaaand I've opened a pull request :p SO - MANY - PULLING

And I suggest you to add the update instructions to OP.
[Xperia SP Android Development] Oblox:
Not questioning you MrSteve I like trying to learn how all this scripting works, that recovery update doesn't seem to mention the /bin folder where the hijack used to live, has it moved or is there something i'm missing that tells it to put it there? Its not in a folder so it cant be that.