Develop Bugs

[ROM] [GPL] Team Villain Presents... FroydVillain 1.7.2 (Based on CM6.1 Final)

Please read post 3 before reporting bugs/issues
FroydVillain 1.7.0
This bit's the introduction. If you're not interested in who we are, or how we got here, or are of the TL;DR mentality, then skip this entire section.
Well folks... It's currently snowy here in Scotland. Got an email to say not to try and commute in this morning, as everything was off, so I set about thinking about things to do I did some work, and then decided it was time to get something out based on CyanogenMod 6.1 (pretty much final) for the hero. Based on the last nightly, here we go...
I applied the usual tweaks to it, as this seems to be a pretty good ROM. And the best bit, no wipe required (though it's still a good idea if you can be bothered) if you are coming from FroydVillain 1.6.x. If you are coming from ANYTHING ELSE, it is required. Maybe some other ROM will work with it, but I have no idea, and don't really want to know So if you have trouble and didn't wipe, please wipe before asking for help. Let me say it again...
If you have problems with the ROM or apps or anything else for that matter, go do a wipe before asking for help. It's the first thing you'll be asked to do anyway, so save yourself the time and get a faster answer
This is based on CM6.1's nightly, which I think is meant to be the stable release for the Hero. It's certainly stable enough for my liking
As for what's new/fixed, look at the CM6.1 changelog.
Overscrolling works, apps that whined about the version string should work now, and there's a new call screen from CM that means you don't put people on hold with your ear, when on a call. Plus everything else from Cyanogenmod that got fixed or improved
Before I go onto the ROM, I would like to thank a fair load of people. First of all, all the Cyanogenmod developers. Without them, this ROM would not exist. Big props out to them for their excellent work. Next, the VillainROM developers, including Ninpo for his ARM optimisations in CM6.1, Kendon for his usual behind the scenes scripts and time in setting things up, DMzda for his dedication in helping me test this ROM in the latter stages, MikeBeecham for his artwork and designs used throughout the ROM, HomerSp for his help taking Mike's bootscreen to life, and everyone else who has been there helping... Particular thanks must go to Shen for helping me get this build out to you while I have been so busy recently. Also, big thanks as usual to Lenny, NPRussell, Mike, RaiderX, RichardTrip, Acolwill, Alankila and sorry if I forgot anyone. Their contributions have been too numerous to mention. But this ain't an Oscar speech, so I must stop now.
Finally big props go to Erasmux, whose FlyKernel 11c has been tweaked slightly for performance. Details of the tweaks below...
So here we go...
FroydVillain 1.7.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTES:
Nothing much, but let's proclaim the glory of CyanogenMod again Thanks guys.
INSTRUCTIONS:
1. Boot into recovery
2. Nandroid backup
3. Wipe of data, dalvik and cache (optional, but if you need help, you're gonna need to do this first before asking!)
4. Flash the ROM
5. Reboot. At setup screen, give it time to complete optimisation after boot... Should settle down in about 5 minutes, more if you didn't wipe EXT.
Your download link:
http://www.villainrom.co.uk/forum/showthread.php?3698-FroydVillain-1.7.0-Released!
e989a86d44bea67e0a56499cab009bdd FroydVillain1.7.0-signed.zip
A kitchen is available at http://www.villainrom.co.uk/forum/showthread.php?3698-FroydVillain-1.7.0-Released!
Addon Zips
Some optional things you might want to try installing:
Ubuntu Fonts (flashable zip) - Screenshot 1 - Screenshot 2 (thanks DMzda)
Finally...
Join us on irc for banter (chat.freenode.net : 6667 - #villainrom) for support!
We hope you enjoy the ROM!
Finally, kernel tweaks are exact same as last time, in 1.6.0, so see that thread for info.
Base kernel (cheers, Erasmux, and big props) https://github.com/erasmux/hero-2.6.29-flykernel/tree/flykernel-11c

Optional FroydVillain Update to Re-Enable Trackball LED
Re-enables trackball LED for incoming calls and SMS messages. This is an optional zip for those who want this feature back. Future updates will not depend on this, it is not a required update.
http://www.villainrom.co.uk/forum/s...-Update-Released&p=35279&viewfull=1#post35279
FroydVillain 1.7.2 Update
Fixes voice search and speech support. Flash over 1.7.1. You MUST install 1.7.1 first, or you won't get those fixes. This goes in ADDITION to 1.7.1
http://www.villainrom.co.uk/forum/s...-Update-Released&p=35279&viewfull=1#post35279
FroydVillain 1.7.1 Update
Fixes twitter, HTC IME, a few other apps that are missing from market. Flash over 1.7.0. Then use manage applications to clear market data
http://www.villainrom.co.uk/forum/s...-1.7.0-Released!&p=35118&viewfull=1#post35118

Before Reporting Bugs/Errors/Problems/FCs/etc...
In order to help people sooner, and reduce the number of repeat reports, please observe the following before reporting a bug along the lines of "GPS is broken, HTC_IME mod FCs, it won't boot, it's slow, it's got poor battery, this breaks..."
1) Look in post 2 for any updates. Flash any with a version number, there's no need to flash optional ones unless you want to.
2) Search this thread for a keyword. eg. if gps isn't working, search thread for "GPS". If apps are missing from market, search "market". See if it is fixed, or already reported.
3) If there is no patch or fix, turn off the phone, remove your SD card, and boot the phone with no SD card. Does issue persist? If you need a memory card to test the bug, use a blank, freshly formatted spare, with just one partition.
4) If this cures the problem, you need to clear out your SD card. Back up your apps, and wipe apps2sd partition if you use it (Wipe EXT from recovery). See if problem is cured (with SD card inserted in phone). If it is, stop here, and enjoy the ROM.
5) If issue persists after removing SD, turn off phone, insert SD, boot to recovery, nandroid, wipe Data, cache, Dalvik cache. Reflash ROM and all patches. Turn off phone. Remove SD card. Boot.
6) If issue is solved, try with sd inserted now. Looks like you just needed a wipe. If not, please report the bug using the usual procedures. Mention you got to "step 6" with no resolution.
This will alleviate about 80% of bugs, I would estimate, allowing me to work on the remaining 20% not cured by this.

Sweet thanks Pulser another great realese from Team Villain

Awesome!
Sent from my HTC Hero using XDA App

Running it now sweet thanks a lot : )
Sent from my HTC Hero using Tapatalk

wow... that was quick! Thank god for snow hehe..
You say no wipe is required if coming from FV1.6.x, so i wont need to back up call log, sms, app data, backup widget positions etc etc? Just put zip file on SD card and flash?

amazing flashing now!

That's what I did no wipe just flashed and all's good : )
Calico5 said:
wow... that was quick! Thank god for snow hehe..
You say no wipe is required if coming from FV1.6.x, so i wont need to back up call log, sms, app data, backup widget positions etc etc? Just put zip file on SD card and flash?
Click to expand...
Click to collapse
Sent from my HTC Hero using Tapatalk

Many thanks, I will give it a go as soon as possible. Can someone please report about performance, batterylife etc.? I really appreciate your work.
Sent from my HTC Hero using XDA App

Many Thanks pulser_g2, appreciate your diligence!
rustynuts34 said:
That's what I did no wipe just flashed and all's good : )
Click to expand...
Click to collapse
Thanks for the info!

harlequix said:
Many thanks, I will give it a go as soon as possible. Can someone please report about performance, batterylife etc.? I really appreciate your work.
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Performance no worse than 1.6.
No idea about battery, it's a bit soon yet for people to be able to tell. I see no reason it won't be good though

Thanks for this! I'd been flirting with Floyo after being a FV diehard for a few months, but I've just flashed this ROM and it's looking good so far.

ROM runs fine, but Twitter and Tweetdeck 'gone'. Posted a bug report on VR.

UbuntuBhoy said:
ROM runs fine, but Twitter and Tweetdeck 'gone'. Posted a bug report on VR.
Click to expand...
Click to collapse
This one is weird... I will look tomorrow to see, but toiteur is fine here.

Yeah, Seesmic also works fine, just the two I mentioned.

Sorted it.
Download this file
http://db.tt/MUiuogS
And put in /system/etc/permissions
Chmod the file 644, and reboot and twitter will return
Will release as zip tomorrow if nobody else has done so by then

pulser_g2 said:
And put inside it
Code:
Click to expand...
Click to collapse
haha, I don't think that's going to do much my friend.
forgot to paste the code maybe?
and congrats on the new release!

Cheers Pulser, will check in the morning. Far too tired right now.
Sent from my HTC Hero using XDA App

UbuntuBhoy said:
ROM runs fine, but Twitter and Tweetdeck 'gone'. Posted a bug report on VR.
Click to expand...
Click to collapse
pulser_g2 said:
Sorted it.
Download this file
http://db.tt/MUiuogS
And put in /system/etc/permissions
Chmod the file 644, and reboot and twitter will return
Will release as zip tomorrow if nobody else has done so by then
Click to expand...
Click to collapse
thank you, I've got the same issue here.
missing tweetdeck, twicca and twitter for android.

[Q] Why is my Desire Z so DANG SLOW?

I have had my Desire Z since October 2011. It has been great. I love the phone, and the swing-out keyboard with the number keys missing hasn't bothered me at all.
What does bother me is HOW DANG SLOW my phone is now. I installed Cyanogen 7, the last build available for Desire Z. I seem to remember the phone being responsive when I installed. However, now, the phone is almost becoming unusable. Starting applications like Google Maps frequently results in the "Wait / Force Close" dialog. It can take 10 seconds to realign the screen when I move the keyboard. I've tried CPU monitoring but don't find anything in the background eating the CPU.
What's going on? Lately I've thought about buying a new phone, but I love my Desire Z! (and I've already paid for it and I should get 2 years out of a phone)

Mine is snappy as ever, try a different kernel, a different ROM, partition to ext4, supercharge it, add swap, compcache or zram, pimpmyrom, remove bloat and bad apps, overclock, etc. there are so many things you can do to change how your phone performs, try some things find what works for you.
Then again your idea of slow may differ than mine, I will say that I can hardly remember what a force closed looks like as its been so long...
Sent from my Nexus 7 using xda premium

How do I find out what's slow? And how to make it faster?

My G2 is slow because I've had it for over two years now, it's single-core and is pretty slow even compared to the first dual-core Android phones, I've flashed numerous ROMs on it, etc. In spite of all of that, it has been my most reliable Android phone and is always the one I grab when I brick any other device of mine.
By the way, flash one of Flinny's CM10.1 ROMs and thank me later.

Hi.
Try to stay free ROM more than 500Mb.

AW: [Q] Why is my Desire Z so DANG SLOW?
I would recommend to flash the latest official CyanogenMod 7.2 for DesireZ. It's the fastest in daily use for me.
I also tested Flinnys CM10.1 but flashed CM7.2 again after a couple of days, because it does not run as smooth as CM7.2 and the new features do not wight it.

demkantor said:
Mine is snappy as ever, try a different kernel, a different ROM, partition to ext4, supercharge it, add swap, compcache or zram, pimpmyrom, remove bloat and bad apps, overclock, etc. there are so many things you can do to change how your phone performs, try some things find what works for you.
Then again your idea of slow may differ than mine, I will say that I can hardly remember what a force closed looks like as its been so long...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
seriously, mine is fast too. If I compare it with a s2, my dz isn't that bad at all!
viperZ is very impressive, I dont know what they did on this rom, but it's fast.
-no swap
-no ext4
-no supercharge
- zram off
-seeder entropy ON
- animation off
- 2d force gpu
- smartassv2 governor
- 1.4 ghz

mobil_z said:
I would recommend to flash the latest official CyanogenMod 7.2 for DesireZ. It's the fastest in daily use for me.
I also tested Flinnys CM10.1 but flashed CM7.2 again after a couple of days, because it does not run as smooth as CM7.2 and the new features do not wight it.
Click to expand...
Click to collapse
Cyanogen 7.2 is exactly what I'm running! It's the latest version of Cyanogen ever released for Desire Z. I just can't understand why other peoples' phones are OK while mine drags. It's the same hardware and software!

its your apps that are installed or your not partitioned to ext 4 or many other things.
personally i havent liked 7.2 for the vision and dont use it as i found it a bit buggy. like i said try a few roms and try some various mods and settings, find what works for you

I noticed this too. Supercharging it helped a bit
---------- Post added at 09:41 PM ---------- Previous post was at 09:41 PM ----------
Another recommendation is to clean your sdcard. Some apps leave crap and crap all over the SD card and you install/uninstall some and its still there. Might help.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What does this tell anyone?
I don't think it's stuff on the SDcard. That's data, it just sits there and doesn't interfere with the operation of the system.

gromky said:
What does this tell anyone?
I don't think it's stuff on the SDcard. That's data, it just sits there and doesn't interfere with the operation of the system.
Click to expand...
Click to collapse
Could Overclock a little, like others said have you tried supercharge or if you dont like messing with scripts there is always
https://play.google.com/store/apps/...sImNvbS5qcnVtbXkuYXBwcy5tZW1vcnkubWFuYWdlciJd
Also check a task manager see what background programs are running sometimes apps on the sdcard don't just sit there I like android assistant made by Aaron. mainly for its 4x1 widget. Also I have found if things sync alot then my phone seems slower along with short battery.
Hope that helps a little

gromky said:
[I don't think it's stuff on the SDcard. That's data, it just sits there and doesn't interfere with the operation of the system.
Click to expand...
Click to collapse
And that data does what? Just sit there? No, it is constanly being (more) read and (less) written to. That has a overhead.
Check your apps and delete any innceesary ones.

gromky said:
What does this tell anyone?
I don't think it's stuff on the SDcard. That's data, it just sits there and doesn't interfere with the operation of the system.
Click to expand...
Click to collapse
Get SD Main from the Play store and run corpse finder a system cleaner. See if anything's clogging your sd card and / or /data/ partition up, and clean it.
Also use swap enabler to move apps to sd-ext (I wouldn't recommend memory swap though) this noticeably and immediately speeds my G2 up.

AW: [Q] Why is my Desire Z so DANG SLOW?
HTCDreamOn said:
I wouldn't recommend memory swap though
Click to expand...
Click to collapse
Right, unfortunately CM does not support a swap partition as far as I know.
Somebody knows a kernel, what can be flashed in CM7.2 to support swap?

mobil_z said:
Right, unfortunately CM does not support a swap partition as far as I know.
Somebody knows a kernel, what can be flashed in CM7.2 to support swap?
Click to expand...
Click to collapse
Of course it does. Check if you have an sd-ext partition, if you don't know then you probably don't have one, in which case backup your SD card onto your computer, reboot to recovery and select partition SD card, wherever that may be. You don't need a swap partition, and if you have room I would suggest having a 1.5GB SD ext, although 512MB is fine for me.
Now put all the data back onto your SD card which you backed up to your computer earlier, if you get errors then don't copy over .android_secure, Android, and data folders (along with any other .folders / hidden folders).
Now reboot to recovery and flash swap enabler select skip data swap and SD swap but enable sd-ext, it should give you happy messages about it working and then you can reboot. You'll notice you'll have an init.d script and your apps will have moved to SD ext. If you don't like it, just flags swap enabler again and remove it, it will move your apps back for you.
This relies simply on an init.d script as I said, which literally just moves and binds /data/app to sd-ext, don't worry about kernels or anything.
By the way, I would upgrade from Gingerbread if I were you.
Also, if you're only getting 3500ish in An tutu, there is a problem because I get over 3700 at 768MHz in Andromadus CM10.1

I just used SDmaid's "corpsefind" function. After deleting files, my Chinese dictionary didn't work, ADWlauncher crashed and wouldn't come back up, and when I reboot the system was screwed up and needed to be restored. It's a bit too agressive in "cleaning" the system. It deleted files that were still in use by installed applications.

gromky said:
I just used SDmaid's "corpsefind" function. After deleting files, my Chinese dictionary didn't work, ADWlauncher crashed and wouldn't come back up, and when I reboot the system was screwed up and needed to be restored. It's a bit too agressive in "cleaning" the system. It deleted files that were still in use by installed applications.
Click to expand...
Click to collapse
It shouldn't, it usually just gets rid of databases left behind by uninstalled apps. If you're getting these sorts of problems you really should do a full clean install, maybe try some different ROMs.

[August 3rd]SailfishOS for Galaxy Nexus (Alpha)

SailfishOS for Galaxy Nexus (GSM)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a community port of Jolla's SailfishOS for the Galaxy Nexus.
It features a gesture-based user interface with a unique design and ease-of-use in mind.
For more information about SailfishOS please head over to sailfishos.org.
This is not an Android ROM, this is a different operating system.
It only uses parts of Android for hardware enablement (drivers).
Special Thanks to vakkov, sledges, mugna91, the Mer Project, the Nemo Project and all the fine people over at #sailfishos-porters
Release Notes:
This release is based on SailfishOS 1.0.8.19 (Tahkalampi).
The Galaxy Nexus port is considered to be of alpha quality.
Though depending on your usage it might be stabile enough for daily use.
Bug reports:
Please issue bugreports at the Nemo Project Bugzilla.
Known issues:
Due to an issue with ofono, reading from SIM does not work. You'll need to remove your PIN lock before flashing.
Setting an ambiance (color theme & wallpaper) causes hangs. Either needs the battery to be pulled, or you can SSH into the device and run:
systemctl --user restart lipstick
The startup wizard is getting skipped for now, due to the issue above.
The Jolla Store currently does not work. As an alternative you can try Warehouse for OpenRepos.
The camera does not work.
Due to redistribution issues the codec for MP3 can't shipped. To enable the codec run the following command:
devel-su zypper in gst-av
Instructions & Download:
Make a backup
Factory Reset (Wipe /data & /cache)
Wipe /system
Install CyanogenMod 10.1.3
Install SailfishOS on top:
Mirrors:
beidl.eu
Reboot
Old versions:
Alpha1:
XDA
beidl.eu
XDA:DevDB Information
SailfishOS for Galaxy Nexus, ROM for the Samsung Galaxy Nexus
Contributors
beidl, vakkov, sledges
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2014-08-03
Last Updated 2014-08-24

Reserved
Changes:
August 24th, 2014:
Notification LED working
Bluetooth activation/deactivation fixed
Changes for Video playback (work in progress)
August 3rd, 2014:
Initial release

Nice & interesting..

Awesome! I'd love to check this out, as I've been following the progress in the other thread! (And because I'd actually like to check sailfish out, I never experienced Maemo and Meego so this will be an entirely new experience). However the XDA download link is unbelievably slow (Topping out at like 30 KB/s maximum on a decent internet connection). Does anyone have a download link from a service such as Google Drive/Mega/AFH? I'd be extremely thankful if someone did have a mirror, and would return the favour by uploading it. (If the OP allows for mirrors).

Justice™ said:
Awesome! I'd love to check this out, as I've been following the progress in the other thread! (And because I'd actually like to check sailfish out, I never experienced Maemo and Meego so this will be an entirely new experience). However the XDA download link is unbelievably slow (Topping out at like 30 KB/s maximum on a decent internet connection). Does anyone have a download link from a service such as Google Drive/Mega/AFH? I'd be extremely thankful if someone did have a mirror, and would return the favour by uploading it. (If the OP allows for mirrors).
Click to expand...
Click to collapse
Mirror to my private server added.

Ubuntu 14.04 recognizes the device as a ethernet cable connection..
I've played around the USB settings and all the others are charging-only.

freshgiammi said:
Ubuntu 14.04 recognizes the device as a ethernet cable connection..
I've played around the USB settings and all the others are charging-only.
Click to expand...
Click to collapse
Alright, definitely something nobody has tested, for whatever reason. As you are using Ubuntu, a quick sshfs mount to [email protected] might do it for now.

beidl said:
Alright, definitely something nobody has tested, for whatever reason. As you are using Ubuntu, a quick sshfs mount to [email protected] might do it for now.
Click to expand...
Click to collapse
Also, powering down the device while connected via USB to the PC, reboots it instead of shutting it down.
Can't try sshfs since i've just restored my Android backup bc Gnex is my daily driver, I'm sorry.

i couldnt select allow untrusted software to install warehouse. it does nothing when i select accept to allow it o settings.

freshgiammi said:
Also, powering down the device while connected via USB to the PC, reboots it instead of shutting it down.
Can't try sshfs since i've just restored my Android backup bc Gnex is my daily driver, I'm sorry.
Click to expand...
Click to collapse
As mentioned, the "Alpha" tag is pretty much justified. Thank you for testing.
Also, the "untrusted software" switch is pretty useless and installing 3rd party applications
is supposed to be done through the command line for now.

beidl said:
As mentioned, the "Alpha" tag is pretty much justified. Thank you for testing.
Also, the "untrusted software" switch is pretty useless and installing 3rd party applications
is supposed to be done through the command line for now.
Click to expand...
Click to collapse
so i have to install cm10.1.3 maguro and install the sailfish os alpha..?
cause it been 15minute it's stuck on google boot screen.
EDIT:
does it have to be EXT4..?
edit:
ah yeah it does ext4..

z3n0x1 said:
so i have to install cm10.1.3 maguro and install the sailfish os alpha..?
cause it been 15minute it's stuck on google boot screen.
EDIT:
does it have to be EXT4..?
Click to expand...
Click to collapse
Yes, I would assume it needs to be EXT4

Justice™ said:
Yes, I would assume it needs to be EXT4
Click to expand...
Click to collapse
yup correct just installed it now..
and now need to install the alternative jolla store.. the warehouse.. but i don't know how..
allow untrusted software are not working..
what i have to go.. even get the warehouse.rpm.. it still can't be installed..

z3n0x1 said:
yup correct just installed it now..
and now need to install the alternative jolla store.. the warehouse.. but i don't know how..
allow untrusted software are not working..
what i have to go.. even get the warehouse.rpm.. it still can't be installed..
Click to expand...
Click to collapse
You need to install it through the terminal, I'm not sure what the command is to install rpms of the top of my head, so googling it would probably get you an answer.

Justice™ said:
You need to install it through the terminal, I'm not sure what the command is to install rpms of the top of my head, so googling it would probably get you an answer.
Click to expand...
Click to collapse
well i got this...
after download the warehouse.rpm
goto setting > develoment > set password > save
type into terminal: devel-su -c harbour-warehouse
and type the password.. but nothing comes up
do i have to restart after save password or maybe restart after type pass word?? :silly:
EDIT:
open terminal
type cd ~/Downloads
type pkcon install-local ./downloaded-package.rpm
got "fatal error:nothing provides libsailfishapp.so.1 needed by harbour-warehouse-0.3-20.armv7h"
need the libsailfishapp.so.1.. lookfor it now..
the alpha looks smooth untill now been few hours test.. message working.. wifi.. haven't check the rest..
im still curious about how to install .rpm

z3n0x1 said:
well i got this...
after download the warehouse.rpm
goto setting > develoment > set password > save
type into terminal: devel-su -c harbour-warehouse
and type the password.. but nothing comes up
do i have to restart after save password or maybe restart after type pass word?? :silly:
the alpha looks smooth untill now been few hours test.. message working.. wifi.. haven't check the rest..
im still curious about how to install .rpm
Click to expand...
Click to collapse
I assume you'd need to elevate to root using devel-su, and then use one of the commands I've quoted below to install the warehouse rpm.
From terminal, root
Install a package
rpm –ivh packagename
upgrade a package
rpm –Uvh packagename
you can find out what the switches mean by doing a rpm --help from the command line.
Click to expand...
Click to collapse
I think -ivh would indicate installation and -uvh being the uninstall process

Justice™ said:
I assume you'd need to elevate to root using devel-su, and then use one of the commands I've quoted below to install the warehouse rpm.
I think -ivh would indicate installation and -uvh being the uninstall process
Click to expand...
Click to collapse
yes it's seems so..
i'll try you code now..
or maybe the -uvh are the upgrade..?? since it's upgrade on the code you are quote..
EDIT:
error: failed dependdencies:
libsailfishapp.so.1 is needed by harbour-warehouse-0.3-20.armv7h
so i perssume it the libsailfishapp.so.1 the problem..
http://forum.xda-developers.com/showpost.php?p=53171554&postcount=90
he's said that just copy it from /usr/lib/ . but how come even we don't have filemanager..
i'll try the pkcon install jolla-fileman (the native file manager from jolla) apprently the rpm are not there..
just maybe.. even we have the native file manager.. the missing libsailfishapp.so.1 still occur..

z3n0x1 said:
yes it's seems so..
i'll try you code now..
or maybe the -uvh are the upgrade..?? since it's upgrade on the code you are quote..
Click to expand...
Click to collapse
I must've misread it as uninstall then, yeah.

Justice™ said:
I must've misread it as uninstall then, yeah.
Click to expand...
Click to collapse
oh my im deprresed Lol
oh my now what should i do..
is there anyway that we can reach the root via computer..?

z3n0x1 said:
oh my im deprresed Lol
oh my now what should i do..
is there anyway that we can reach the root via computer..?
Click to expand...
Click to collapse
You could try and SSH in and run the commands, which may be easier, I'm trying to get the warehouse installed now

Pixel XL - System UI Has Stopped Working

Hello all,
I usually don't join forums and jump in to make one post pertaining to my issue but rather conduct extensive research to figure out my problem, so many apologies beforehand. However, this issue seems to be unique to me and I would to know if anyone can help me out!
After unlocking the bootloader yesterday, I rooted my Pixel XL using chainfire's systemless root method and I was ecstatic as ever! I followed the directions to the T to make sure I didn't make any mistakes, but using ADB program is familiar territory to me - everything went as expected and I successfully rooted my phone. However, I made the mistake of downloading apps that were not compatible with the systemless root, which I read could have some complications. This is where I was stumbling upon new ground, because I am not entirely familiar with "systemless root" and what the key differences are, nor what the repercussions would be for downloading apps that would look for root access in the /system partition. The two apps that I downloaded were "Magisk Manager" and "Game Guardian." On the Magisk Manager, the install data was downloaded to my phone, nothing was actually installed to the phone. As for Game Guardian, I don't think that app had compatibility with systemless root yet.
This issue where my UI would crash would persist, even after restarting my phone. I would boot the phone up to bootloader and recovery mode - just to cycle through and restart the phone regularly (since you can't wipe the cache partition), that didn't work. I tried deleting those apps and clearing their data from my phone, and that didn't work.
I made a revelation when I plugged the phone in and the persistent UI crashing stopped. I had thought that I fixed the issue, but then it continued throughout the day - up until before I posted this post. That was when I noticed that the crashing is tied with the battery status;
When I had low battery and my phone wasn't charging, my System UI would immediately crash.
When I had low battery and my phone was charging, my System UI would not crash.
When I have a decent charge (anything above what is "low battery" - 15%?), my System UI would not crash.
I did a little experiment when I was at low battery and I noticed that RIGHT BEFORE the System UI would crash, the battery icon would stay with the lightning bolt, instead of switching over to a red battery with low charge. I was unable to get a screenshot before it crashed, though. Provided, are screenshots of what my screen looked when the System UI would crash (minus the consistent pop-up) and when it was charging:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My concern right now, with my ignorance on systemless rooting and how incompatible apps could affect the phone, is that maybe the stock battery icon for when the phone is at a low charge is missing from the system file images and that is what might be causing the crashing.
Can anyone give any insight on the matter? I'll provide any information required, if need be!
Thank you in advance.
EDIT 1:
This issue is being tracked; http://forum.xda-developers.com/pixe...3490156/page11

this has been well documented in other threads. read around...

nbhadusia said:
this has been well documented in other threads. read around...
Click to expand...
Click to collapse
I understand that this a well-documented issue on other threads. However, those particular issues on those particular devices offered no remedy to the issue on my phone.

Callyvan said:
I understand that this a well-documented issue on other threads. However, those particular issues on those particular devices offered no remedy to the issue on my phone.
Click to expand...
Click to collapse
....thats because 'those' devices are the same devices as yours and theres currently no 'remedy' though CF is workin on one.... read around... its well documented for the device youre using....
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156/page11

Change your battery saver to 15%.
See pic below.

nbhadusia said:
....thats because 'those' devices are the same devices as yours and theres currently no 'remedy' though CF is workin on one.... read around... its well documented for the device youre using....
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156/page11
Click to expand...
Click to collapse
My apologies, I had thought that "read around" meant that other threads were posted, not that it was discussed in a previous thread.
Thank you for a point in the right direction.

Callyvan said:
My apologies, I had thought that "read around" meant that other threads were posted, not that it was discussed in a previous thread.
Thank you for a point in the right direction.
Click to expand...
Click to collapse
I have not experienced this problem. And some that have were using outdated ADB / SDK drivers.
One person fixed it by simply updating ADB and drivers then re-rooted and he was all set. I will try to find the link...
Correction: Chainfire did identify the issue: http://forum.xda-developers.com/showpost.php?p=69405488&postcount=143

Scott said:
I have not experienced this problem. And some that have were using outdated ADB / SDK drivers.
One person fixed it by simply updating ADB and drivers then re-rooted and he was all set. I will try to find the link...
Correction: Chainfire did identify the issue: http://forum.xda-developers.com/showpost.php?p=69405488&postcount=143
Click to expand...
Click to collapse
Thank you for that, Scott. I'll be following that main thread now.
At least it is indeed that it only happens when the battery level is low.

Callyvan said:
I understand that this a well-documented issue on other threads. However, those particular issues on those particular devices offered no remedy to the issue on my phone.
Click to expand...
Click to collapse
The current fix is to flash the stock boot.img or custom kernel and don't flash root. Im hopeful it will be fixed in next Supersu update.

Wtf
nbhadusia said:
this has been well documented in other threads. read around...
Click to expand...
Click to collapse
Who the heck are you helping even posting this stupid sentence? Not everyone is sitting at a desktop. Your post is just a big waste of time for you and everyone who reads it. Why not try to be helpful for once. I see over 200 people have viewed this post but all you can do is post how it's documented . Thanks a whole lot buddy..

ko0ky said:
Who the heck are you helping even posting this stupid sentence? Not everyone is sitting at a desktop. Your post is just a big waste of time for you and everyone who reads it. Why not try to be helpful for once. I see over 200 people have viewed this post but all you can do is post how it's documented . Thanks a whole lot buddy..
Click to expand...
Click to collapse
You're welcome. So hows that anger management course coming along 'buddy'?

nbhadusia said:
You're welcome. So hows that anger management course coming along 'buddy'?
Click to expand...
Click to collapse
Useless reply.

Question App isn't available every now and then?

Greetings,
Has anyone seen some apps getting greyed out and when you try to open it, you get a:
App isn't available. App isn;'t available at the moment.
This is managed by root.
Tried to search for this everywhere but wasn't able to find anything.

emontes said:
Greetings,
Has anyone seen some apps getting greyed out and when you try to open it, you get a:
App isn't available. App isn;'t available at the moment.
This is managed by root.
Tried to search for this everywhere but wasn't able to find anything.
Click to expand...
Click to collapse
What app?

toolhas4degrees said:
What app?
Click to expand...
Click to collapse
It's random, it's happening to a few at the moment: Wifi Analyzer, WireGuard, Wirex, Wise, etc.
As it happened to WhatsApp, I uninstalled, reinstalled and it worked but it's very odd.

emontes said:
It's random, it's happening to a few at the moment: Wifi Analyzer, WireGuard, Wirex, Wise, etc.
As it happened to WhatsApp, I uninstalled, reinstalled and it worked but it's very odd.
Click to expand...
Click to collapse
Maybe custom kernel issue, is it only on boot before everything initializes? Should have to wait 2 to 4 min after boot

toolhas4degrees said:
Maybe custom kernel issue, is it only on boot before everything initializes? Should have to wait 2 to 4 min after boot
Click to expand...
Click to collapse
I don't have a custom kernel, it's straight on latest Oxygen and it stays indefinitely, funny enough. Was also happening with the XDA app, removing and reinstalling did the trick.

emontes said:
I don't have a custom kernel, it's straight on latest Oxygen and it stays indefinitely, funny enough. Was also happening with the XDA app, removing and reinstalling did the tri
Click to expand...
Click to collapse
emontes said:
I don't have a custom kernel, it's straight on latest Oxygen and it stays indefinitely, funny enough. Was also happening with the XDA app, removing and reinstalling did the trick.
Click to expand...
Click to collapse
Try turning off modules one by one till you find the culprit. No issues here

toolhas4degrees said:
Try turning off modules one by one till you find the culprit. No issues here
Click to expand...
Click to collapse
Cheers, will give it a go!

emontes said:
Cheers, will give it a go!
Click to expand...
Click to collapse
Did you find what was causing your issue?

toolhas4degrees said:
Did you find what was causing your issue?
Click to expand...
Click to collapse
Not yet, I ended up reinstalling those apps but will disable modules next.time it happens (and it will), I will update here when I do. Thanks for.the help!

I think I had similar with Sesame shortcuts. I'm not entirely sure what happened, but it went away eventually

This is crazy. It just happened again, I disabled every module and rebooted but it is still there, same error message and the app is greyed out. Both on nova and oneplus launcher . Have no idea what's causing that here .
Attached is the error on the screen.
Just ran a logcat and this message is what I get when I click one of the greyed out apps:
Package root not found
android.content.pm.PackageManager$NameNotFoundException: root
at android.app.ApplicationPackageManager.getApplicationInfoAsUser(ApplicationPackageManager.java:428)
at com.android.internal.app.SuspendedAppActivity.getAppLabel(SuspendedAppActivity.java:73)
at com.android.internal.app.SuspendedAppActivity.resolveDialogMessage(SuspendedAppActivity.java:138)
at com.android.internal.app.SuspendedAppActivity.onCreate(SuspendedAppActivity.java:208)
at android.app.Activity.performCreate(Activity.java:8006)
at android.app.Activity.performCreate(Activity.java:7990)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1329)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3589)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3780)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:85)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2251)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:233)
at android.app.ActivityThread.main(ActivityThread.java:8035)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:631)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:978)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Did you block root permission for all apps?

Facing the same issue here. Did anybody find any solution?

I found the answer! The apps are being suspended by alpha backup for backup. The bugger ended up suspending itself while backing itself up. Guess what happens when you suspend your own self?....
A simple :
Code:
pm unsuspend com.ruet_cse_1503050.ragib.appbackup.pro
from adb shell with root did the magic

devsk said:
I found the answer! The apps are being suspended by alpha backup for backup. The bugger ended up suspending itself while backing itself up. Guess what happens when you suspend your own self?....
A simple :
Code:
pm unsuspend com.ruet_cse_1503050.ragib.appbackup.pro
from adb shell with root did the magic
Click to expand...
Click to collapse
Oh wow,that's cool, @devsk, thanks for coming back for an update!
My apologies @matze19999 , I haven't seen your update on the thread (didn't get a notification!)
It just happened with me again, though, and alpha backup blocked the settings and UI wizard apps ,bizarre to say the least. Just thinking how I will get out of this situation as ADB shell doesn't work , magisk (which I renamed and is called settings) is also locked and if I boot via bootloader with a magisk_rooted boot image, I can't install magisk as well. Looks like it's start from scratch for me.

emontes said:
It's random, it's happening to a few at the moment: Wifi Analyzer, WireGuard, Wirex, Wise, etc.
As it happened to WhatsApp, I uninstalled, reinstalled and it worked but it's very odd.
Click to expand...
Click to collapse
Good to know you found a solution. I was going to say avoid apps starting with W.

devsk said:
I found the answer! The apps are being suspended by alpha backup for backup. The bugger ended up suspending itself while backing itself up. Guess what happens when you suspend your own self?....
A simple :
Code:
pm unsuspend com.ruet_cse_1503050.ragib.appbackup.pro
from adb shell with root did the magic
Click to expand...
Click to collapse
Many thanks Sir!
You've saved my life
Exactly the same happened to me when trying out Alpha Backup Pro and naively check the "Suspend apps before backup/restore" not realizing it might not unsuspend them *after* backing them up :/
Quite a bugger if you'd ask me - I had to unsuspend about 200 apps ... what a tedious job
On another note: what do you think about Alpha Backup Pro? Is it worth keeping? I'm not switching/updating ROMs a lot nowadays because our device has some problems with TWRP so I can't test it "in real life scenarios"

Apart from this glitch with suspend, I have found this app to be the most complete and most reliable backup solution (I loved TiBu before it got abandoned).

devsk said:
Apart from this glitch with suspend, I have found this app to be the most complete and most reliable backup solution (I loved TiBu before it got abandoned).
Click to expand...
Click to collapse
Thanks for coming back to my question!
I'm still undecided between Alpha Backup Pro and OandBackupX ...
Right now I'm quite puzzled that Alpha Backup Pro seems to have executed the nightly schedule to backup the complete data well - at least the backup folder is filled with files *but* inside the app the backed up data tab is empty

I played with OandBackupX for quite a while because I was looking for replacing TiBu with an open source solution. My advice: stay away from it. It won't restore properly. As much as I like open source, this app is not there yet. I hope it is complete and reliable at some point.
With Alpha Backup, make sure you do a complete local backup! Ignore everything else.