Beta test feeds in preware

Dilandu · 10/04/2011, 07:12 PM

Hello I have gained command access using Xecutah and I have entered the two commands that are listed on the wiki page following the directions as listed but I they dont do anything after I reinstall preware. Infact when I enter the commands they dont trigger any type of installation or script that I would normally see when entering commands. Anyone have some insight on what im doing wrong?

Rattor · 10/04/2011, 07:39 PM

Quote:

Originally Posted by Dilandu

Hello I have gained command access using Xecutah and I have entered the two commands that are listed on the wiki page following the directions as listed but I they dont do anything after I reinstall preware. Infact when I enter the commands they dont trigger any type of installation or script that I would normally see when entering commands. Anyone have some insight on what im doing wrong?

Was preware uninstalled when you ran the commands? If so, make sure you're doing number 4 under "Enabling the Beta Testing Feeds" at testing.preware.org. Those commands simply enable the beta feeds once you reinstall preware. You still have to activate the feeds in the manage feeds section, then refresh the feeds, and they new kernels should show up in the kernels section of preware. You then have to install them from that area.

Dilandu · 10/04/2011, 07:51 PM

yes I have followed the procedure step by step uninstall , command line , run the two commands , reinstalled , but there's no "testing feeds" in my manage feeds section it's just "regular" preware.

when you run the two commands do you get some kind of notification it's been ran. Cause when I run the first it just goes to the root command then when I run the second it just goes back to root command....nothing runs or shows me anything different.
thanks

dna550 · 10/04/2011, 08:10 PM

I think the documentation on how to install the beta Kernals needs to be re-written, since a lot has changed and now all of the step-by-step YouTube Videos are now obsolete as well as most of the existing documentation.

Initially, I thought maybe this was because my TouchPad came with webOS 3.02, but likely this would affect anyone now.

For Example:

This is where you start now:

WebOS Quick Install v4.3.1 - PreCentral Forums http://bit.ly/qK7C7h

and this is where you can get lost:

Testing Feeds - WebOS Internals Testing Feeds - WebOS Internals

Maybe this was the intent of the developers?

Dilandu · 10/04/2011, 08:31 PM

Doesn't need to be rewritten, I can understand the texting feed site fine. Just nothing works after I follow the steps it list.

dna550 · 10/04/2011, 11:18 PM

I know i would like this to be fixed, since I was looking forward to using the F4 Phantom Kernel @ 1.8GHz

http://forums.precentral.net/webos-d...omparison.html

Testing Feeds Q&A

Q: Who should use the Alpha testing feeds?

A: If you're asking that question, then you should not be using the Alpha testing feeds. Very very very very very few people should ever enable the Alpha testing feeds. Unless you have a git repository cloned and are editing code, you should not enable the Alpha testing feeds.

Q: Who should use the Beta testing feeds?

A: Anyone is welcome to use the Beta testing feeds, as long as they comply fully with the rules and know exactly why they are using a Beta testing feed (i.e. they are not just blindly following some instructions in some article or forum post somewhere).

Q: Why does enabling the feeds require connecting my device to a computer?

A: When you are enabling testing feeds for the first time, we want to ensure that you are able to connect to your device from a computer to assist in debugging the things you are testing, or to be able to recover your device if something goes wrong.

Q: Why does enabling the feeds require reinstalling Preware?

A: The feeds are actually created when Preware is installed, so you need to reinstall Preware for the feeds to be created on your device.

Q: Why does enabling the feeds require the use of the Linux command line?

A: To be an effective tester, you need to be able to access your device on the Linux command line to provide debugging information. We ensure that you can do that before you are able to access the feeds.

Q: Why can't I just enter in the feed URLs directly?

A: Too many people got the feed names or feed URLs wrong, so we took those things out of the equation.

Q: Why can't I publish the instructions on my blog or website or forum post?

A: Too many people were publishing the URLs without the corresponding rules and warnings.

This is now strictly forbidden.

Q: What are the alpha-patches and beta-patches feeds going to be used for?

A: The alpha-patches feed will be used for testing new AUPT scripts which will be able to handle patching files in /media/cryptofs/apps/ (files not inside /md5sums).

Once that is working, we'll use the beta-patches feed to do a complete upgrade of all patches to use the new AUPT scripts and then beta test those.

alex80386 · 10/07/2011, 11:45 PM

Quote:

Originally Posted by Dilandu

when you run the two commands do you get some kind of notification it's been ran. Cause when I run the first it just goes to the root command then when I run the second it just goes back to root command....nothing runs or shows me anything different.

That is the way the Unix/Linux command line works. If you don't get an error message, that means that it did what you asked it. It almost never asks "are you sure" or tells you "command executed successfully!" or anything like that... it just does what you tell it.

However, if you are running commands like 'mkdir' and 'rm' and you're not sure what those commands do, you should check the manual pages.
mkdir(1): make directories - Linux man page
rm(1): remove files/directories - Linux man page

goodfella420 · 10/17/2011, 11:05 PM

i got beta s up and running ... but nothing comes up under the beta-patches and beta-optware sections.... is this normal????

jdmfish · 10/18/2011, 03:08 PM

So you can no longer just enter in the feeds? I've updated to 3.0.4.77, and of course the F4 Phantom feed I was using is gone. And I'm trying to reinstall it, but it seems things have changed. I cannot use webOS with 1.18 or 1.5. It seems the machine only seems to really operate like I'd hoped at 1.8+.

I just don't know how to enter the Linux commands to re-access the feeds I need.

Unclevanya · 10/18/2011, 03:36 PM

Quote:

Originally Posted by jdmfish

So you can no longer just enter in the feeds? I've updated to 3.0.4.77, and of course the F4 Phantom feed I was using is gone. And I'm trying to reinstall it, but it seems things have changed. I cannot use webOS with 1.18 or 1.5. It seems the machine only seems to really operate like I'd hoped at 1.8+.

I just don't know how to enter the Linux commands to re-access the feeds I need.

I'm going to try to say this without seeming like a jerk...

Testing feeds are intended for those who have a reasonable technical knowledge of Linux and are willing to have to wipe their device at a moments notice.

If you don't feel comfortable with the testing feed requirements - wait for the stable feed options to show up.

I used to run testing feeds on my Pre Plus but I have gotten away from that after being uncomfortable with the requirements to wipe the device and recreate problems before getting help in some circumstances. The point I am trying to make is... pick what your comfort level can handle.

If you need help with the commands I'm sure someone can assist - but be aware that if you have problems later they are going to expect you to be willing to doctor the device and start over.

jdmfish · 10/18/2011, 04:20 PM

Quote:

Originally Posted by Unclevanya

I'm going to try to say this without seeming like a jerk...

Testing feeds are intended for those who have a reasonable technical knowledge of Linux and are willing to have to wipe their device at a moments notice.

If you don't feel comfortable with the testing feed requirements - wait for the stable feed options to show up.

I used to run testing feeds on my Pre Plus but I have gotten away from that after being uncomfortable with the requirements to wipe the device and recreate problems before getting help in some circumstances. The point I am trying to make is... pick what your comfort level can handle.

If you need help with the commands I'm sure someone can assist - but be aware that if you have problems later they are going to expect you to be willing to doctor the device and start over.

I understand that, and I was ready to wipe my device and doctor it back, should I run across problems.

The F4 kernel made this tablet usable, and its just rather sluggish stuck at 1.18. Even the 1.5 kernel is down or not available in preware right now. And I was planning on staying put here because the OS was so snappy.

Unclevanya · 10/18/2011, 04:30 PM

Quote:

Originally Posted by jdmfish

I understand that, and I was ready to wipe my device and doctor it back, should I run across problems.

The F4 kernel made this tablet usable, and its just rather sluggish stuck at 1.18. Even the 1.5 kernel is down or not available in preware right now. And I was planning on staying put here because the OS was so snappy.

Sounds like you are well informed and aware of the issues then. I haven't used this device with those feeds or I would be happy to help you in PM's.

qualitymove13 · 10/25/2011, 12:37 AM

Quote:

Originally Posted by jdmfish

I understand that, and I was ready to wipe my device and doctor it back, should I run across problems.

The F4 kernel made this tablet usable, and its just rather sluggish stuck at 1.18. Even the 1.5 kernel is down or not available in preware right now. And I was planning on staying put here because the OS was so snappy.

How did you make out with this in the end? I seem to be having the same problem as you. Thanks in advance!

twack · 10/25/2011, 12:55 AM

dna550,

My suggestion is to perform the following commands at a linux command line:

cd /media/internal
ls -R /var/preferences/ > ./beta.txt

Then post that beta.txt file here so the gurus can pick at it. I just installed the beta feeds and no problem. But then that would mean something if every TP was exactly the same. LOL

akwalter1 · 12/12/2011, 09:58 AM

To: jdmfish and Dilandu - I had this same problem and I'd like to share how to solve it - the problem is it's not in an obvious place to be able to enable the beta, alpha feeds. What you do is you need to go into preferences in the upper left "Preware " menu with an arrow - where it says "manage feeds" and TURN ON the buttons with the new beta feeds. Thereafter, update the feeds and you'll see all the cool kernels listed. HTH!

10/04/2011, 07:12 PM	#1 (permalink)
Dilandu Member Join Date: Jun 2009 Posts: 46 Likes Received: 2 Thanks: 8 Thanked 3 Times in 3 Posts	Beta test feeds in preware Hello I have gained command access using Xecutah and I have entered the two commands that are listed on the wiki page following the directions as listed but I they dont do anything after I reinstall preware. Infact when I enter the commands they dont trigger any type of installation or script that I would normally see when entering commands. Anyone have some insight on what im doing wrong?
	Liked by

10/04/2011, 07:51 PM	#3 (permalink)
Dilandu Member Join Date: Jun 2009 Posts: 46 Likes Received: 2 Thanks: 8 Thanked 3 Times in 3 Posts	yes I have followed the procedure step by step uninstall , command line , run the two commands , reinstalled , but there's no "testing feeds" in my manage feeds section it's just "regular" preware. when you run the two commands do you get some kind of notification it's been ran. Cause when I run the first it just goes to the root command then when I run the second it just goes back to root command....nothing runs or shows me anything different. thanks
	Liked by

10/04/2011, 08:10 PM	#4 (permalink)
dna550 Member Join Date: Aug 2011 Posts: 135 Likes Received: 10 Thanks: 0 Thanked 19 Times in 14 Posts	I think the documentation on how to install the beta Kernals needs to be re-written, since a lot has changed and now all of the step-by-step YouTube Videos are now obsolete as well as most of the existing documentation. Initially, I thought maybe this was because my TouchPad came with webOS 3.02, but likely this would affect anyone now. For Example: This is where you start now: WebOS Quick Install v4.3.1 - PreCentral Forums http://bit.ly/qK7C7h and this is where you can get lost: Testing Feeds - WebOS Internals Testing Feeds - WebOS Internals Maybe this was the intent of the developers?
	Liked by

10/04/2011, 08:31 PM	#5 (permalink)
Dilandu Member Join Date: Jun 2009 Posts: 46 Likes Received: 2 Thanks: 8 Thanked 3 Times in 3 Posts	Doesn't need to be rewritten, I can understand the texting feed site fine. Just nothing works after I follow the steps it list.
	Liked by

10/04/2011, 11:18 PM	#6 (permalink)
dna550 Member Join Date: Aug 2011 Posts: 135 Likes Received: 10 Thanks: 0 Thanked 19 Times in 14 Posts	I know i would like this to be fixed, since I was looking forward to using the F4 Phantom Kernel @ 1.8GHz http://forums.precentral.net/webos-d...omparison.html Testing Feeds Q&A Q: Who should use the Alpha testing feeds? A: If you're asking that question, then you should not be using the Alpha testing feeds. Very very very very very few people should ever enable the Alpha testing feeds. Unless you have a git repository cloned and are editing code, you should not enable the Alpha testing feeds. Q: Who should use the Beta testing feeds? A: Anyone is welcome to use the Beta testing feeds, as long as they comply fully with the rules and know exactly why they are using a Beta testing feed (i.e. they are not just blindly following some instructions in some article or forum post somewhere). Q: Why does enabling the feeds require connecting my device to a computer? A: When you are enabling testing feeds for the first time, we want to ensure that you are able to connect to your device from a computer to assist in debugging the things you are testing, or to be able to recover your device if something goes wrong. Q: Why does enabling the feeds require reinstalling Preware? A: The feeds are actually created when Preware is installed, so you need to reinstall Preware for the feeds to be created on your device. Q: Why does enabling the feeds require the use of the Linux command line? A: To be an effective tester, you need to be able to access your device on the Linux command line to provide debugging information. We ensure that you can do that before you are able to access the feeds. Q: Why can't I just enter in the feed URLs directly? A: Too many people got the feed names or feed URLs wrong, so we took those things out of the equation. Q: Why can't I publish the instructions on my blog or website or forum post? A: Too many people were publishing the URLs without the corresponding rules and warnings. This is now strictly forbidden. Q: What are the alpha-patches and beta-patches feeds going to be used for? A: The alpha-patches feed will be used for testing new AUPT scripts which will be able to handle patching files in /media/cryptofs/apps/ (files not inside /md5sums). Once that is working, we'll use the beta-patches feed to do a complete upgrade of all patches to use the new AUPT scripts and then beta test those.
	Liked by

10/17/2011, 11:05 PM	#8 (permalink)
goodfella420 Member Join Date: Aug 2011 Posts: 1 Likes Received: 0 Thanks: 0 Thanked 0 Times in 0 Posts	i got beta s up and running ... but nothing comes up under the beta-patches and beta-optware sections.... is this normal????
	Liked by

10/18/2011, 03:08 PM	#9 (permalink)
jdmfish Member Join Date: Aug 2011 Location: FL Posts: 41 Likes Received: 1 Thanks: 5 Thanked 0 Times in 0 Posts	So you can no longer just enter in the feeds? I've updated to 3.0.4.77, and of course the F4 Phantom feed I was using is gone. And I'm trying to reinstall it, but it seems things have changed. I cannot use webOS with 1.18 or 1.5. It seems the machine only seems to really operate like I'd hoped at 1.8+. I just don't know how to enter the Linux commands to re-access the feeds I need.
	Liked by

10/25/2011, 12:55 AM	#14 (permalink)
twack Member Join Date: Sep 2011 Location: The WackLands Posts: 610 Likes Received: 109 Thanks: 18 Thanked 181 Times in 73 Posts	dna550, My suggestion is to perform the following commands at a linux command line: cd /media/internal ls -R /var/preferences/ > ./beta.txt Then post that beta.txt file here so the gurus can pick at it. I just installed the beta feeds and no problem. But then that would mean something if every TP was exactly the same. LOL __________________ TWack On my 4G TouchPad, Pre3 or Panda-Veer. If you like our patches, please consider donating to the cause. \|wackware\|google+\|facebook\|twitter\|shortcut\|mylo\|multiapp\|flashfile\|donate\|
	Liked by

12/12/2011, 09:58 AM	#15 (permalink)
akwalter1 Member Join Date: Dec 2011 Posts: 1 Likes Received: 0 Thanks: 0 Thanked 0 Times in 0 Posts	problem solved To: jdmfish and Dilandu - I had this same problem and I'd like to share how to solve it - the problem is it's not in an obvious place to be able to enable the beta, alpha feeds. What you do is you need to go into preferences in the upper left "Preware " menu with an arrow - where it says "manage feeds" and TURN ON the buttons with the new beta feeds. Thereafter, update the feeds and you'll see all the cool kernels listed. HTH!
	Liked by

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode