yashsingh1/xdaforums huggingface dataset:
[Xperia SP Android Development] MrSteve555:
I messed something up... I'll upload a fixed package in a few minutes. Thanks for pointing out my mistake.:good:
[Xperia SP Android Development] Oblox:
No problem. Glad I understood what it was doing! :p
[Xperia SP Android Development] MrSteve555:
Okay, fixed that mistake, now it should flash fine and work fine :)
[Xperia SP Android Development] Oblox:
Great thanks, looking forward to the new build whenever it arrives.
[Xperia SP Android Development] mrhnet:
Some installer feedback..

I'm on UBL.

*Dirty flashed build #3 via TWRP v.2.7.0.0 (found in DoomKernel)--> no baseband (expected).

*Dirty flashed same via TWRP v.2.6.3.0 (in Williams kernel)--> baseband/wifi/hotspot working!

I never had baseband missing issues with TWRP 2.6.3.0.

Noticed that the following value defaults to 136.. (touch response not that slick.. subjective though).

/sys/devices/i2c-3/3-0024/main_ttsp_core.cyttsp4_i2c_adapter/signal_disparity

Changing it to 0 (default in cm11-lbl) gives me better touch response. I think it's something to do with glove mode..

To appreciate the raw speed, change the animation speed to x.75.. true for me at least :P
[Xperia SP Android Development] neXus PRIME:
Thanks for touch optimization. I have also edited clearpad.idc values for better touch response. Next Build will have it.
[MENTION=5579865]MrSteve555[/MENTION]

Everything is finally merged. Check it before i build # 4.

EXPECTED CHANGELOG:
[Xperia SP Android Development] MrSteve555:
[MENTION=4350492]neXus PRIME[/MENTION]

Everything looks fine and should work fine :good:

And for everyone - these are the commands with stock glove mode values:

echo "280" > /sys/devices/i2c-3/3-0024/main_ttsp_core.cyttsp4_i2c_adapter/finger_threshold
echo "136" > /sys/devices/i2c-3/3-0024/main_ttsp_core.cyttsp4_i2c_adapter/signal_disparity

And they are set as default in CM, so using the commands won't change anything. Weird. Touch sensitivity with these values was a lot better on stock, just like Xperia Sola's floating touch.
[Xperia SP Android Development] mrhnet:
Setting signal disparity to 0 and finger threshold to 20 (the lowest value it accepts, it seems) gives me super touch response!! Maybe too sensitive for some..
[Xperia SP Android Development] MrSteve555:
Just tried that, and yeah, it also gives me really good touch response, maybe it's not as responsive as stock, but still works great. Thanks for finding these values! :)
[Xperia SP Android Development] neXus PRIME:
expecting pull request :p:p

We also need to fix LED color for charging. But maybe its a PA bug, if yes, we cant do anything about it,
[Xperia SP Android Development] MrSteve555:
No pull request this time.

But sooner or later the pull request will arrive, unexpected and deadly :p

I think it's PA bug, in CM there aren't any problems with it, and CM and PA are based off the same sources.
[Xperia SP Android Development] neXus PRIME:
I was talking about touch sensitive values
[Xperia SP Android Development] MrSteve555:
I know, I think you misunderstood me.

First part of my post was supposed to be funny. As always, I didn't succed in that :p

Btw, the settings in PA are using the old CM layout, so we can use the old bagyusz patch for switching the glove mode. I can add it back to the settings and ramdisk.

EDIT: Adding it to settings isn't a good idea. AOSPA-legacy team will update the settings sooner or later. And without a working switch it's annoying because the screen is oversensitive. So for now I would't add it. Touch is working fine even without these values and your new patch will make it better, so no need for that.
[Xperia SP Android Development] orangpelupa:
hello, after a day i use this rom i can say that i am:

Super paranoid happy :D :D :D

thanks [MENTION=4350492]neXus PRIME[/MENTION] for this awesome rom, thanks [MENTION=5579865]MrSteve555[/MENTION] and the developers for together working this rom better

btw,

Those that got Baseband Unknown (no cellphone network)

Reboot to recovery that look ugly (repeadly tap VOL DOWN after turn on phone), then flash the .zip again.

also those that want Glove Mode working,

you need to download Xperia Glove https://play.google.com/store/apps/details?id=t.gimbot.glove then select ENABLE, DISABLE, and ENABLE again. Now glove mode works.

if you got unstable performance (random stutter),

go to the setting, about, tap build number many times until DEVELOPER option appear. Now you can see Performance option, change governor to Wheatley and IO to cfq.

if you failed to restore your backup due to not enough space:

go to internal SD and delete a few GB of data. (yes its weird, the restoring of Data partition is affected by internal SD free space)
[Xperia SP Android Development] lvints:
[MENTION=4350492]neXus PRIME[/MENTION]

I'm a little confused, which build should I download the available [MENTION=5579865]MrSteve555[/MENTION] or should I wait for your build? Have you started working with Resurection Remix (please do not consider how ETA)?
[Xperia SP Android Development] Rycon33:
[MENTION=4350492]neXus PRIME[/MENTION] , a little OT here, I'm a bit desperate to self-build my own PA ROM, can you help me in making the local_manifest.xml. I"ve already done the repo init for the AOSP legacy. The issue is I am confused where to get those device tree, kernel tree, hardware source tree, & vendor proprietaries tree . It's my first attempt in building. TIA and apologies for the OT
[Xperia SP Android Development] neXus PRIME:
You should check out bagyusz cm11 thread for permission and instruction as I also did the same
[Xperia SP Android Development] ngoralph:
all the tress are in github, for UBL go to cm's github just fork everything and edit some stuffs and you're good to go

but gor LBL i think you can fork nexus prime's source and it would work
[Xperia SP Android Development] filipcar:
I flashed this rom and I just found out that I don't have gsm signal. Is there a way to fix it?
[Xperia SP Android Development] J0kker:
You should edit your post and take 5 minutes to read the last pages, unless you want to be burned alive on the public place ;)
[Xperia SP Android Development] neXus PRIME:
Flash again using cwm recovery
[Xperia SP Android Development] ParaSense.:
i have this problem to... allready reflashed with cwm but nothing works

Edit: it worked after 1 min :D nice rom ty

---------- Post added at 08:00 AM ---------- Previous post was at 07:56 AM ----------

btw is there any way to install stock keyboard?? cause im typing with T9 like on old phones... each number have 4 letters if you understand me ..
[Xperia SP Android Development] Oblox:
Stock keyboard as in sony or google? Google AOSP keyboard come with it, you can get the sony keyboard from Dipesh's Ultimate Pure thread http://xdaforums.com/showthread.php?t=2658043.
[Xperia SP Android Development] ParaSense.:
you mean install this? Q.Xperia Keybaord Fc

A.Install As Normal Apk http://d-h.st/61W

tried but cant install this
[Xperia SP Android Development] Oblox:
Recovery update flashed fine, god its nice to have TWRP back!

Waiting (im)patiently for build 4!
[Xperia SP Android Development] MrSteve555:
[MENTION=4423970]lvints[/MENTION]

I think you should wait for neXus' build #4. And I haven't posted any build, only recoveries for current users of #3 to update the ROM smoothly.
[Xperia SP Android Development] neXus PRIME:
Installing build #4 right now. if successful, upload in a few hours.
[Xperia SP Android Development] neXus PRIME:
It failed [MENTION=5579865]MrSteve555[/MENTION]. You should look into it why your new hijack.tar is failing.

I tried installing through Philz. The hijack.tar is not working. I think Set_metadata failed during philz and the file didnt become executable hence it could not start ramdisk and Now my phone in bootloop and have to repair via flashtool.

Bad experiment.
[Xperia SP Android Development] MrSteve555:
[MENTION=4350492]neXus PRIME[/MENTION]

I'm using my hijack.tar right now and it doesn't give me any issues.

Check if these lines are present in the updater-script:

set_metadata("/system/bin/hijack.tar", "uid", 0, "gid", 0, "mode", 0777, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata("/system/bin/wipedata", "uid", 0, "gid", 0, "mode", 0777, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
[Xperia SP Android Development] neXus PRIME:
its not about using it....

when you replace file, it takes on permissions of previous file so that means nothing.

but when zip gets installed. i think hijack.tar failed to get permissions.
[Xperia SP Android Development] MrSteve555:
I flashed my modified #3(updated hijack.tar and updater-script from build #2)with system formatted, not just replaced it with a file manager. As I told you, check these lines. If they aren't there, it's a permission issue and something in releasetools failed.

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

@neXus PRIME

Try your build #4 with this updater-script:

https://mega.co.nz/#!eU5DgRwD!zMK6y4gUIxIe7HxLcO92Io-tykitsOg3gyX46-Gm3p0

This sets everything properly on any recovery.
[Xperia SP Android Development] MrSteve555:
Oh, and [MENTION=4350492]neXus PRIME[/MENTION] could you upload #4 anyway? Just for testing purposes. Maybe someone will find it useful.
[Xperia SP Android Development] neXus PRIME:
i have bootlooped and destroyed my installation 4 times now. Still havent figured out why it doesnt boot.

The PA boot animation comes, so definitely system got flashed. But there was no KNIGHT RIDER LED before that. Meaning hijack.tar didnt get initialized.

Which is surprising, because that should not be the case.

Baseband issues apart, there is no reason it should not work. I did a build on clean ccache and make clean clobber.

Frustrated.
[Xperia SP Android Development] MrSteve555:
If you are using dssmex recoveries there's theoretically and practically no reason for it to not boot.

I've checked the github, cloned it locally and compared the md5 of my hijack.tar and github hijack.tar - the md5s are the same.

Have you tried installing in that way:

1. Flash ROM, gapps etc. with PhilZ

2. Mount /system

3. Flash aroma filemanager zip

4. Navigate to /system/bin and chmod 777 the wipedata and hijack.tar files.

Of course you could just use TWRP's inbuilt file manager or even adb shell, but I don't know if adb is even present on SP recoveries, so I'm giving the universal solution.

Other than permissions issue there is no other reason for not booting...
[Xperia SP Android Development] neXus PRIME:
done all this. no luck.

I am gonna revert to pre-hijack and raamdisk change.. clean rebuild and try flashing that. WITH bagyusz patch.

Closing thread till I get out of this build # 4 mess. Thread closed till then. PM me if needed.
[Xperia SP Android Development] neXus PRIME:
[MENTION=5579865]MrSteve555[/MENTION]

i have started uploading build #4 to dev host same folder.

Will be finished in some hours. Let me know if you find its bootloop issue.
[Xperia SP Android Development] neXus PRIME:
Warning. Normal Users. DO NOT FLASH.

Only test build for [MENTION=5579865]MrSteve555[/MENTION] and any willing tester on Unlocked BL.

http://d-h.st/BJx

Unlocked bootloader guys can recover easily from boot loop if using custom kernel, so they are best targets to test this for us.

[MENTION=5579865]MrSteve555[/MENTION]

I am definitely sure that hijack.tar is NOT getting initialized because i NEVER get the RED LED SEQUENCE in this build. But i dont know why.

Even if all libraries are corrupted, even if updater-script is faulty, i tried aroma to change permission of hijack AFTER INSTALL. NO use.

Please, help me find root cause. I am back to stock FTF just due to this mess.
[Xperia SP Android Development] Dammer Martins:
I can test to you.Later i post the result in this post.

EDIT: I having the status 7 erro. I edited the updater-script but still have the erro.

EDIT²: I delete the kernel of the zip and the erro is gone,but ROM is not booting up.And yes,no KNIGHT RIDER LED when bootlog appears.I can't enter in recovery too.
[Xperia SP Android Development] neXus PRIME:
Tell me which boot animation appears??? Paranoid?
[Xperia SP Android Development] neXus PRIME:
And Mr Steve uploaded an update script few posts below. Can you please check by pushing that into zip before install.
[Xperia SP Android Development] neXus PRIME:
[MENTION=5579865]MrSteve555[/MENTION]

I see that 26 and 30 build have NO DIFFERENCE in updater script other than set_metadata. Then why is it not booting. At the very least, hijack.tar SHOULD be initialized and KNIGHT RIDER LED Sequence should work. No reason why it should not work.
[Xperia SP Android Development] neXus PRIME:
Please do one more test.

Pull hijack.tar from 26 build # 3 and put in 30 Build #4 in system/bin and then try.

I think the ramdisk is messed up.
[Xperia SP Android Development] MrSteve555:
Maybe something bad happened in the compiling process and hijack.tar is just corrupted?

I have a few ideas, but I don't know if any of these will work.

Btw, downloading right now.

EDIT:

Permissions are set, the hijack isn't corrupted, also wipedata is clean of issues.

The only thing that might fail in that situation is busybox.

If the busybox isn't installed/is corrupted, then wipedata and hijack.sh can't execute the scripts properly.

I'm now reflashing stock ftf(thanks god I wiped /data/ without /data/media, so I don't have to clean my internal storage and thanks god for towelroot).

After that, I'll check my other ideas.
[Xperia SP Android Development] air001:
We very appreciate your hard work to make an amazing rom for us. Thank you very much guys!
[Xperia SP Android Development] MrSteve555:
[MENTION=4350492]neXus PRIME[/MENTION]

Fixed.

The busybox in the ROM was screwed up(maybe a recent update made it incompatible with bagyuszs scripts).

Now everything works fine(baseband,etc. :D), so I think our little "mission" to make the ROM more stable to flash is finally done.

I'm uploading the fixed version to MEGA. Will edit this post with proper DL link after it's done.

EDIT:https://mega.co.nz/#!2NoDFJoZ!5YCtmZ_UbTvQec5zY5GEBtA83NjG89q879XcPkc5W-w
[Xperia SP Android Development] Oblox:
Nice work Mr Steve and Nexus, downloading now!

---------- Post added at 10:21 AM ---------- Previous post was at 10:16 AM ----------

Whats the boot.img in this zip? Just the 205 Kernel?
[Xperia SP Android Development] MrSteve555:
It's CM kernel( I think), but it's not being flashed anyway(chceck the updater-script if you don't believe me).
[Xperia SP Android Development] Oblox:
I believe you dont worry, flashing in a second (just backing up).
[Xperia SP Android Development] neXus PRIME:
[MENTION=5579865]MrSteve555[/MENTION]

Great job. I know i can count on you for troubleshooting. What about hotspot and stuff?

@ ALL

OP Updated with change-log and download link. Uploading my own dev-host mirror in an hour or so.
[Xperia SP Android Development] deathviper:
so the rom is complete? means no bug!

btw can i instal it on UBL?
[Xperia SP Android Development] Oblox:
Tried flashing (typically after wiping /system) in TWRP from MrSteves recoverys and it failed to flash this new or the old version ROM with symlink errors.

Flashtool time for me and 205 install!!

Will try in TWRP from stock install.
[Xperia SP Android Development] neXus PRIME:
Try Philz.
[Xperia SP Android Development] MrSteve555:
Hotspot, baseband and all other things work fine when flashed with PhilZ, so the other recoveries should also work fine, but I haven't tested them with latest build.

---------- Post added at 11:58 AM ---------- Previous post was at 11:56 AM ----------

@Oblox

When using TWRP, don't wipe /system, TWRP has some problems when flashing newer ROMs with /system wipe.
[Xperia SP Android Development] Oblox:
Will do ta.

Thank god for Towelroot and 205 not being laggy, makes re-flashing a lot less of a pain.

---------- Post added at 10:59 AM ---------- Previous post was at 10:58 AM ----------

Ahh I see ill use Philz now then just to be sure.

---------- Post added at 11:35 AM ---------- Previous post was at 10:59 AM ----------

Just booting latest version now. Upgrading apps for ART, all looking good.

By the way if anyone wants a nice Android L theme for PA

http://xdaforums.com/nexus-4/themes-apps/theme-herathon-t2800921

This one is great (make sure its V2 you download), love the new icons and boot animation.
[Xperia SP Android Development] MetalOllie:
Is a full wipe needed coming from build 3?
[Xperia SP Android Development] Oblox:
No.
[Xperia SP Android Development] air001:
Just cache, dalvik cache and system.

Data wipe / factory reset is not necessary.
[Xperia SP Android Development] neXus PRIME:
I know you think LBL UBL in title means both are supported. But UBL needs williams or doom kernel. Some people said Stock kernel does not work. So try it out.
[Xperia SP Android Development] deathviper:
thanks
[Xperia SP Android Development] MixoMaxoViper:
[MENTION=4350492]neXus PRIME[/MENTION]

How big is risk to overheat or fry motherboard or electric circruit?
[Xperia SP Android Development] air001:
Does anybody experienced that in the appdrawer the first position is empty?
[Xperia SP Android Development] ngoralph:
thats a launcher thing not rom, download another launcher
[Xperia SP Android Development] air001:
This is Nova which I use since I installed the rom, and 2-3 days before it worked right.

I'm using build #2, should I update to build #4?
[Xperia SP Android Development] mrjraider:
Rooting, downloading, flashing and testing :) I am very curious about this work!
[Xperia SP Android Development] neXus PRIME:
Press an hold the empty spot. Place it on home screen. Then go to system/apps and kill launcher. It will be ok from then onwards.

Something fishy.
[Xperia SP Android Development] neXus PRIME:
Where did i write to put phone in oven?

There is as much chance of frying motherboard as of you being stupid.

it's actually not an offence. ;)

If you stupid, phone fry fry, BURN:silly::silly:.

You smart, phone rox with 4.4.4 PA awesomeness !!! :victory::victory:
[Xperia SP Android Development] neXus PRIME:
Hop on.:good: You won't be disappointed. I am planning to take this project to the limits.:fingers-crossed:
[Xperia SP Android Development] air001:
Sorry, I don't understand how to kill the launcher in system/app. Should I delete the apk from the system/app folder (I don't think so) or I have to kill the running process?
[Xperia SP Android Development] mrjraider:
I always loved PA on my Samsung Galaxy S+ ;) But well that device is pretty old and we never got a stable build..
[Xperia SP Android Development] neXus PRIME:
Yes kill the process . Dont delete any apk. And try Apex. I dont know exactly what i did, but something made that empty icon correct.
[Xperia SP Android Development] mrjraider:
@ OP:

Next build can you please remove the getprop lines because after a system wipe i get status error 7. Now I have to start all over :silly:
[Xperia SP Android Development] orangpelupa:
Guys, where I can find the settings for:

PIE control

Status bar

I have used gravity box but now it's messed up due to I have PIE from immersive mode and PIE from gravity box. 1st time activating immersive mode I got the choice to disable PIE, but now I never get that pop up. And I can't find any PIE setting in settings menu.

Thanks
[Xperia SP Android Development] neXus PRIME:
Dear, I am uploading that build with assert removed. You must be using MrSteve555 mega.com upload. I'll ask him to re-upload Build # 4 with those lines and boot.img removed.
[Xperia SP Android Development] neXus PRIME:
There is no PIE Settings.

Paranoid Android is almost like CM11 with very little obvious settings menus. Everything is hidden in relevant areas.

There is a page somewhere where you can RESET PA customizations. Then it will ask again about immersive mode and pie and all the stuff it asked you first time.

Dont remember where that reset page was.
[Xperia SP Android Development] mrjraider:
Okay but I still need to start all over xD So lets do so... :angel:
[Xperia SP Android Development] MixoMaxoViper:
[MENTION=4350492]neXus PRIME[/MENTION]

Great work!

Smootht,Fast,Stable and the best stock UI
[Xperia SP Android Development] MrSteve555:
[MENTION=4350492]neXus PRIME[/MENTION]

I think it isn't a good idea to remove getprop lines from the updater-script. There actually are people who will flash this ROM to (for example) Galaxy S4 mini. The getprop lines will prevent them from doing that. And AFAIK, the status 7 getprop problem is only on old CWM; PhilZ, TWRP and CWM Touch handle them without issues. So clearly someone didn't read the OP in that case :p.

Boot.img isn't doing any harm, but I can reupload the ROM without it, if you want to.
[Xperia SP Android Development] neXus PRIME:
For now, lets assume no stupid from other phones wanders here. pa-HUASHAN-xyz in Xperia SP Android Dev in Xperia SP page should serve the purpose. And this also causes issues for TWRP as mentioned by someone earlier.

So dont worry. We have upgraded recoveries and i am thinking of another little trick.
[Xperia SP Android Development] neXus PRIME:
Guys,

Mirror is up for Build # 4.

http://d-h.st/KlH

Added to OP.
[Xperia SP Android Development] lvints:
You wipe something?
[Xperia SP Android Development] neXus PRIME:
And some good guy, make 4 or 5 screenshots for me. Thanks.
[Xperia SP Android Development] Dammer Martins:
How to install in locked bootloader:

1-Download ROM,Gapps,ParanoidPreferences.apk and any kernel based on stock(doom kernel per example)

2-Open ROM zip and past ParanoidPreferences.apk in system/app

3-Put ROM zip and Gapps on your device

4-Turn your device off and flash the kernel with flashtools

5-Boot in recovery and make all wipes(data,cache and dalvik cache)

6-Flash ROM and Gapps and reboot

Screenshots: http://imgur.com/QukWF4b,yxbfeLJ,T59HYmP,vTLbt0J,66ZKASs,5CYBq1J,PYry0AH

For me,mobile network is not working.
[Xperia SP Android Development] neXus PRIME:
I think if you use CWM, the baseband will also work. Please try flashing again from CWM.

As treoboeth said:

EDIT: and screenshots in English please. Cant understand a word :p
[Xperia SP Android Development] Valaran:
doom kernel, no good for lbl, just flash stock 205 kernel only with flashtool.
[Xperia SP Android Development] Sajat.:
I had the same problem (I had no signal), but you are right, using CWM solves the problem.

Bluetooth is OK

Lightbulb is NOK (it is not switch led on, but led in camera works)
[Xperia SP Android Development] Shywim:
Since I hate this host so bad, (~50kB/s on a 100Mbit/s server), I give to others a mirror : http://shywim.fr/pa_huashan-4.4-RC2-20140619.zip (will remove if you don't like it, neXus :o )

The file is untouched ;)

What I did :

- Factory Reset

- Format /system

- Install ROM

- Install Gapps (Full Stock Package from http://xdaforums.com/showthread.php?t=2397942 )

- adb push ParanoidPreference.apk /system/app ; chmod 644

- Shutdown

- Flash .205 kernel (was on .201)

- Reboot

What it does :

- The "Welcome..." and "Just a sec..." screen stays for a very long time... (and ParanoidPreferences force close one time while "Welcome")

- Aaannd... Unknown Baseband (flashed with Philz recovery, never had a problem before even with CM versions that had this problem...)

- Also, the bootanimation is stock (AOSP) Android logo... Is that normal ?

Will try with CWM...

Edit: Baseband working with CWM :D

Edit2: So everything seems to work fine, except ParanoidPreferences who force close at every boot... will try to catch the logcat next time...

Edit3: Crash log :
[Xperia SP Android Development] Dammer Martins:
[MENTION=4350492]neXus PRIME[/MENTION] here is the screenshot. http://imgur.com/3Fc6HQ1,JxDR8xG,Vw...oDcpT,jhEtInc,CfySkMo,qyrnsJ6,uUVHUtV,1u0IMQU

And dude,for me the baseband is not working.I tried to flash with cm kernel(CWM) and after flash the doom kernel,but don't worked.I tried to use the stock kernel too,but still not working. :(

[MENTION=4018956]Sajat.[/MENTION] your bootloader is locked or unlocked?