yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] zimphishmonger:
Hey Everyone,

I was just wondering that if we have a build to which we have BOTH RamHack kernels and the non-ramhack kernel, would there be a way to write a quick app or script to switch between them.

I guess we could store both kernels on the /sdcard and use a .sh script to flash_image between them, and reboot. I dont believe we can "hot-swap" between kernels, but if anyone knows a method, please respond here :D

If anyone can think of a better or more efficient method of doing this, I believe the whole community would benefit. Lets see if we can get something like this going....
[G1 Android Development] adelco93:
is it really that hard to boot into recovery and flash an update.zip?
[G1 Android Development] sipvn:
I guess this is what you're looking for:

http://wootroot.com/blog/?page_id=1463

Ive seen it implemented on one other rom on xda, but can't remember which one ..
[G1 Android Development] zimphishmonger:
I am trying to make it easier and more efficient to switch between them. The uneek switch seems exactly what im looking for
[G1 Android Development] zimphishmonger:
I put together a version of uneeks script that can be flashed over SuperD or FastTest3.1.

ISSUE THOUGH, I cant get it to flash correctly, as I get the "update-script not found" error, even though I signed it and created the appropriate META-INF directories.

Here is the file, if anyone thinks they can fix it

Uneek Script (needs to be fixed\signed) : http://www.4shared.com/file/257220832/8b6c2940/uneek.html
[G1 Android Development] zimphishmonger:
Alpha release

Here is a very alpha release of a working port of uneek's RamHack/NonRamHack Toggle script ported to SuperD 1.10.2 by myself.

http://www.4shared.com/file/257253893/a61182a2/Uneek_Script.html

Instructions

extract zip file to /sdcard/uneek

Launch terminal

type 'su'

type 'sh /sdcard/uneek/install-uneek.sh' -should see no errors/messages

execute 'uneek' from /system/bin

Chose Ram option or JIT (not tested) options, all others prob dont work as I didnt modify them

reboot (you must do so to see effects take place, the kernel doesn't "hot-swap" :-( )

WiFi still works, CC & Swap work.

Issues

Switch breaks boot screen - not sure why as its stored in framework-res.apk, but still a bug

Leave me feedback\ improvements\whatever......
[G1 Android Development] Ace42:
You still have to boot into recovery so you might as well flash a zip containing a rhack or noram-hack kernel.
[G1 Android Development] Firerat:
I did some scripts based off Kings,

get gscript from the market ( donate if you like it )

and drop script into the gscript folder

with a little uname query you could have just one script, which switches based on the current running kernel

Edit: , actually if your kernel needs different kernel modules, then you will have to build in a copy ( which I suspect is where king got his rwsystem bit from , he copied from a script which updates the kernel modules )
[G1 Android Development] lbcoder:
If you have an engineering SPL installed, there isn't any need for the recovery partition, so might as well install your second kernel to the recovery partition. Boot normal = normal, boot recovery = ramhack.
[G1 Android Development] Firerat:
and then have a script switch wlan.ko if incompatible

might as well switch with script and keep recovery for the odd times when you just want to quickly flash some zips from a list and not at your pc.

yeap, I've downloaded and flashed a rom while 'out and about' before.
[G1 Android Development] lbcoder:
If the only difference is ramhack on one but not the other, then the wlan module will be fine -- there is NO REASON to be switching modules around with your kernel unless you use a kernel that is binary incompatible -- which means DIFFERENT VERSION.
[G1 Android Development] Firerat:
yeap, true but why not keep options open?

What if they decide they want to switch between binary incompatible kernels?

They would need to switch kernel modules anyway.

so get a script that works, and is simple to 'generate'.

I know you are trying to keep it simple, but you are actually needlessly setting up restrictions, which would then require a script to get around.

So why not use a script from the start, keeping the added convenience of a recovery image?
[G1 Android Development] lbcoder:
If the only objective is to be able to easily toggle between ramhack and noramhack, then the recovery solution is (1) more reliable, (2) doesn't require reflashing NAND, (3) just easier to activate. With the reflashing approach, you have to either go into recovery and flash something, or pause-and-wait-and-autoreboot.
[G1 Android Development] Firerat:
did you ever read anything?

the script is as easy as a couple of taps, maybe home button, swipe tap tap.

( the key app here is gscript )

the flash is over very quickly, it checks md5sum first, it reboots.

you have to reboot with the recovery method anyway

recovery method restricts to binary compatible kernels, or require a script to switch kernel modules.

It is a no brainer imo, keep it flexible and keep the convenience of a true recovery.img

ok, so nand only gets what, on average 10,000 writes, is it really going to reduce its life in practice?

I like your idea, it will work but it just isn't as flexible as a script.

It is however more suited to an mt3g, offering duel ROM

I'm thinking mtdblock3 for one ROM, block4 for the other

errm, data , yeah might need to section that up somehow

any reason why a loopback can't sit on yaffs?

oh, and the ramdisk will need tweaking, obviously.

Sorry back on topic

Guys,

Either will work, if you do have incompatible kernels, and are having problems with scripts just let me know, I can probably make a script to generate a script for you.
[G1 Android Development] IConrad01:
1) Booting into recovery to change out your kernel image is totally unnecessary. You can do it via CLI with the flash_image command -- most every modded ROM already includes it.

2) Removing the recovery image just to put up a second install also seems somewhat overkill for devices as heavily limited on storage as most Android phones -- especially the G1.

3) I don't know about loopback on yaffs2 -- but I don't see any reason why it couldn't work.

4) It really seems to me that what we need is some kernel hacker who's familiar with hotswapping patched files -- a la ksplice ( http://www.ksplice.com/ ) -- to hack together a genuine, non-rebooting, RAMhack switch.

5) In all seriousness; what makes gscript superior to ASE ( http://code.google.com/p/android-scripting )?
[G1 Android Development] Firerat:
Nothing, apart from its easy, it works and I haven't looked at ase yet

btw , you missed a p/ in that link

http://code.google.com/p/android-scripting/
[G1 Android Development] IConrad01:
>_<

Pesky perniciously persistently phantasmagoric P!!!

I just keep on seeing people referring to gScript when ASE is a vastly more robust offering. It can run its scripts as daemons, run in background, run in terminal, it offers the same desktop shortcut option -- and more importantly, it can run Python, Perl, JRuby, Lua, BeanShell, JavaScript, Tcl, and shell scripts. (It loads the interpreters onto your /sdcard.) I've asked this question more than once before and I've never gotten an answer. It really seems like people just aren't aware of ASE -- which is kinda sad, considering the fact that ASE is still seeing continuing development whereas development ended on gScript sometime at the end of last year.
[G1 Android Development] Firerat:
no, I am very interested in it,

I have been meaning to have a proper look at it for sometime

, I think I first saw it on @google

gscript is just handy,

unzip this, gscript from market,add, load, tick su, save , tap

But I promise , I will look at ASE :)
[G1 Android Development] zimphishmonger:
Glad this is getting your attention....My script was pretty dirty anyways.

Anyway you can package it up in signed-zip format for easy access and modification of boot.imgs. Im having some issues with the update-script portion during the signing process tos keeping me from getting mine to be "flashable"
[G1 Android Development] Firerat:
still having update-script issues?

if you post it, I'll be happy to take a look for you

Oh, I've started a kernel switch script

I'll do some testing when its done and post it here for you
[G1 Android Development] Firerat:
free sample

Kings threads are full of people posting as they can't get his scripts to run

FR-KS-Kaosp19.zip

unzip to sdcard

install either gscript or ase

( have to admit ase is growing on me )

done, no messing around, I have generated the scripts already :)

enjoy
[G1 Android Development] krohme:
bro which is for performance and which is the full 3D kernel?

dumb question I know - BTW thanks for all your contributions in XDA, how you figure out these little tricks n stuff is pure genius mate. Lol you related to Einstein?
[G1 Android Development] Firerat:
ones called

Perform-Kaosp19

and the other

Full3D-Kaosp19

;)

btw, gscript is probably easier , ase is just tap mad
[G1 Android Development] Clavs1:
So I followed all your instructions with gscript for perfom K but when I run the script and it gets to rebooting now, it says "stderr: not permited!" then I rebooted it myself and now it loops on the HTC quietly brilliant screen. =(
[G1 Android Development] xillius200:
Love your work FireRat :P But hasn't lazlo already done a ramhack on and off script with use with terminal emulator with 2 commands and he laso put it in a rom 0o
[G1 Android Development] Firerat:
hmmm

FR-KS-Kaosp19.zip is not for a Legend or Eris

its Kings aosp 1.9

unless I'm confused, and you generated a script for the Legend/eris

let me know which kings rom you are using and I'll check
[G1 Android Development] Firerat:
no idea,

but have you seen how many people can't use King's terminal emulator scripts?
[G1 Android Development] Clavs1:
Sorry, you're right. I was trying to run the script on the eris, not the aosp 1.9.

do you have a script for his performancekernel on eris 1.2 he just came out with yesertday? http://xdaforums.com/showthread.php?t=642643

that I may use instead? =) thanks!
[G1 Android Development] xillius200:
Yeah XD I see what you mean :)
[G1 Android Development] xillius200:
LOL feel like helping to fix a ramhack and jit in spareparts option if I can't get it fixed or my man Wes can't either he's taking a look for me :P lol got it all set up just doesn't execute the code the sh script looks perfect XD
[8125, K-JAM, P4300, MDA Vario General] vespaman2006:
Hi everyone new here and im really hoping to get some help here

I purchased this of ebay as i got the wife one hers being imate kjam

i managed to unlock and update rom to wma6 no probs with help from

this forum.

So i brought another but this had g4 chip so hardslp needed etc etc

all went well unlocked etc etc but lost sound out going and incoming so thought i would flash a different rom the t-mobile one RUU_Prodigy_1060204_105_11210_TMO_UK_Ship it wouldnt take it wrong update tool so exracted the nk.nbf and used RUU MUN update tool all went well flashed ok restarted but got stuck at start screen left it for 5 mins nothing so did hard reset same again stuck did it second time it wont come on at all now

Ha Ha ive bricked it

Can anyone help me restore it please
[XPERIA X1 General] 8SE8:
I've had this phone for just under a year now and my experience with it has been horrible.

+ Flashing is pretty much out of the question if you don't want SOD (Almost any rom that's WIN 6.5 = SOD, almost any use of Manila = SOD) even the more stable roms eventually start getting SOD after prolonged use.

+ Typing is probably the worst. After a few months of usage, the keyboard function is really crap, keys are not interpreted properly, several keypresses, some not registering - 'space' and '.' Only fix is to tear the whole thing open and wipe down the keys, something I'm not going to do. Similarly, the 3" screen is too small to credibly use the touch only/software keyboards that seem to take up over half the screen.

+ CRACKS.... I remember some guy raving about how the Xperia is made of metal. It has picked up just as many scuff marks and scratches as any other phone I've had, on top of all of this, it has the damn crack issue.

+ Reliability = 0. This is mainly because of the first point, an SOD can occur at any time, making this a uselss business device - don't know when calls will be missed, don't know when alarms will be missed.

+ The panels interface is mediocre at best, on top of which, I have seen it ported to all other WM phones, so hmmm....

Perhaps as an out-of-the-box-don't-touch-this type phone it will suffice, as (I'm guessing) no SODs will occur, but still cracks, and the damn keyboard (which is why I bought this phone in the first place) are issues of real concern.

What do you guys think?
[XPERIA X1 General] emuneee:
I completely and wholeheartedly agree. Theee most frustrating aspect of my X1 overtime was how crappy the keyboard was as it aged. So much so, that I sold my X1 and bought a Motorola Q9h (keyboard on this thing is fantastic).

The X1 can do a lot however, I liken it to a mini computer. That includes a whole lot of positive (web browsing, video, mp3s, etc.) but also alot of negatives (crashing, SOD, terrible build quality, etc.).
[XPERIA X1 General] republicano:
i gotta say the xperia is quite good - i like the design,hardware (black, non 3 week cracking case)

i only have received a sod once while leaving it on the charger all night, but then again i reset once a day.

i gotta say that i dislike the keyboard over a period of time

my space bar double space in the middle of it so i have to press it at the end so it wont apply a full stop double space, so its not the kind of keyboard you can leave in your pocket.

i think the panels are rubbish, i barley use the other ones, a waste of the x panel button

its a nice phone but the only reason why im keeping it is because of the possible android os, winmo is terrible in my opinion these cooked roms are better than the original ones in terms of reliability and efficiency
[XPERIA X1 General] anothadave:
lol i thought the reviews i read where always quite low. bear in mind that any reviewer probably judged the phone over a few weeks so wouldnt of encountered any of the major problems we found after 6 months proper use. and an official reviewer from a website or magazine wouldnt consider flashing it at all so that wouldnt get a mention.

also a professional reviewer would of tested many many phones and unfortunately the X1 isnt alone with its unreliability. so might of taken this into account when giving their score. they would of seen the flaws and crashes of all the other phones too. pretty much all modern phones, especially smart phones and pocketpcs, crash at some point or a laggy or have bugs. unhappy X1 users may hold other phones as perfect holy grails that function flawlessly and last decades unscathed. but in reality they also have bugs, crash and fall apart too...
[XPERIA X1 General] doministry:
On my side I'm absolutely surprised

by a huge X1 reliability.

I've never owned such a stable device, which is still as a rock

since Dec 2008.

So I think it was success and I understand high notes in reviews.

It all depends on how you use the device, really.

Not even what you install but also how you operate it.

I believe devices are generally very sensitive and not bullet proof.

I'm really surprised, but now, just a moment before I will switch to X2,

I can sum my time with X1 as almost perfect.

Of course, with all the problems any device on this planet

occasionally has..
[XPERIA X1 General] altae:
I for my part absolutely understand the good reviews the X1 got when it was released. Ok it has its flaws and it's not perfect. But like it has been said multiple times in various posts, every phone out there has its shortcomings so the X1 is no exception. Look at what we got:

-High quality video playback with WMP or the Media Xperience Panel (as long as we use a codec that is hardware accelerated, peferably mp4)

-An abolutely superb high resolution display (it could be bigger but that does not affect the quality of the screen itself)

-A useable keyboard (so far I don't have any problems) although it's not the best one on the market

-The device is very agreeable to hold in the hand thanks to the choice of material

-Great sound quality through headphones. Ok, the speaker isn't that good but who buys a smartphone because he intends to walk the streets listening to music through a phone speaker :-)

...

I'm still on WM 6.1 (stock rom R3AA, Switzerland, German) and I consider it absolutely stable. I don't know why everybody ist rushing for an unstable custom 6.5 rom since there is absolutely nothing that can be done with 6.5 that can't with 6.1. It's just the optics and for me that's not worth the loss of stability. My Xperia X1 very rarely crashes. If you perform a soft reset every couple of days the stock rom really is stable. This is by the way the same with every desktop computer. If one does not reboot his computer for several days it will eventually become unstable and crash. So why should this be different with pocketpcs?

All in all I think for a device that was released in late 2008 the X1 is still a very capable phone. And what's more I have not encountered so far one single problem like keyboard failure or cracks. Maybe I'm just lucky but that's my experience.
[XPERIA X1 General] Concentrate:
Those of you getting the SOD, try flashing to 826x Rom.

Most stable rom I've used so far.
[XPERIA X1 General] poetryrocksalot:
Well, it takes about a year for these faults to appear on the Xperia X1. Don't expect any late reviews on any phone 'cause once the phone is released, the public coverage and reviews will dwindle.
[XPERIA X1 General] flamingsamurai:
Had my phone since Feb 09, and bar a funky lcd repair, it hasn't missed a beat at all. I don't even know what SOD is. My phone stays on for weeks at a time.

Dom is right, it really is about how you use it, and as devices give more and more control to the user, they tend to be more and more sensitive.
[XPERIA X1 General] altae:
I totally agree. Nowadays smartphones are more computers than phones. They got sliding mechanisms, high quality screens and a lot of very sensitive electronics inside. And by the way they are very expensive (some devices almost reach the price of a decent laptop). So would you drop your laptop? Or more exactly would you drop it and complain afererwards because it did not withstand the fall? Of course not. Every child knows: If you drop your laptop it will almost certainly breake.

My opinion remains, the X1 is a good phone despite its shortcomings. It well deserved the good reviews it got in 2008.
[XPERIA X1 General] 8SE8:
Some problems, i.e. keyboard and cracks have nothing to do with flashing, it's just poor design quality. Perhaps it was only a specific batch that was affected.

You are right though, I bought the phone for a fair bit back in the day and I do expect a lot from it (I have 25 stocks as well as 6 different currencies attached to the stocks tab), countless appointments, contacts, switch timezones on an almost weekly basis etc. To me, it didn't deliver (even if I switch back to stock rom, it will always have cracks and keyboard failure).

PS. I have never dropped this phone, I take care of all my phone.
[XPERIA X1 General] Haioken:
My experience has been significantly better than yours has, as outlined below.

I'm using a custom ROM, as I was tbh dissatisfied with the stock rom available for the device. I'm using TouchX 10.9.1, (WinMo 6.1, w/Sense 2.1) which has had no SOD problems since flashing months ago.

In my experience, SOD only occurs when using WinMo 6.5 or above, which I avoid like the plague due to annoying memory & speed issues.

Yes, I have had issues with my own keyboard as well, only with double to quadruple spacing when hitting the spacebar. I've never disassembled the phone, and found the rubbing my thumb up and down the keyboard with a bit of pressure has alleviated the problem for extended periods of time on 3 seperate occasions now.

I also have had asthetic issues with my phone, but I refuse to complain about that, as I am not gentle with my phone. It has in face fallen off a landing, 10 feet onto wooden steps, then bounced down onto ceramic tiles, with no discernable functional issues, just some minor cracking in the corners.

I witness none of the SOD issues you rave about throughout this rant, and attribute your issues to an irrational draw to using WinMo 6.5.x. If you wanted 6.5, why not get a mobile that is built to handle it, or at least has a factory certified update to allow for it?

I've never had any use for panels at all, and don't use them. I don't see this to be a point of detriment however, as the simple answer is Don't use it.

I've software remapped my X-Panel button to kill tasks instead.

Honestly, I think you're being a bit harsh on this particular review. The issues you've raised are:

SOD - Resolved by not using WinMo 6.5.x, which is not designed for use in this application. I don't use it for the same reason I refuse to use 2-stroke or diesel in my car.

Keyboard - I can agree with this issue, but see your point as a little over-sensetive. Try my fix, see if it works for you.

Cracks - I have these in my case as well. Mistreatment does nothing to make the problem any worse, the case integrity is still intact (Well, mine's not losing pieces anyway), and functionality has not been compromized. Unless you purchased the phone to gaze upon during those long and lonely nights, I don't see what the big deal is. Even with these cracks & chips, the phone is still amazingly robust for what you get in it. My touch pro was not this robust, hence why I no longer have it.
[XPERIA X1 General] Hannigan174:
Don't blame the device if you flash your phone and can't deal with it.

It is a poor craftsman who blames his tools.

The xperia got mixed reviews, and given its highs and lows I am not surprised. It seems a little late (given the phone came out in 2008) to start whining about people's reviews.

I am saddened and disappointed that you bought a device that was wrong for YOU and are now trying to find company for your misery. If you are dissatisfied with the X1 perhaps next time you should look for a device that fits YOUR needs.
[XPERIA X1 General] poetryrocksalot:
I think people are going a bit harsh on the original poster. I think he looked at publicity reviews (loaners sent to bloggers) instead of consumer reviews (asset bought by forumers).

These publicity reviews do not address long term issues as SOD, Keyboard and Cracks.

As for the Panels interface, a lot of reviewers already said that it was flop and a gimmick.

As for SOD, the iPhone and Symbian Phones also have SOD.

Yeah sure, he's insulting the Xperia X1, but it is a fact that most people buy smart phones based on these reviews and not one of these reviewers mentioned these issues because they didn't have enough time to experience these issues.

By the way, the keyboard is very bad, and I can totally relate to why he's 'over-sensitive' about it. Think about it. You have to open up your phone just to replace or clean your keyboard. Is that really necessary? (by the way, you all know how much it is a pain in the butt just to re-attach the Xperia's ZIF cable right?).

Apparently, this phone did fit his needs. Of these needs, he addresses them. He wanted a reliable keyboard, no SOD, no cracks, etc. Most of these issues that he addressed are not addressed by the reviewers. So obviously, it is the reviewer's fault. Not his.
[XPERIA X1 General] ring-bearer:
The reviews I read for the X1 basically went: nice hardware, bad/antiquated software. That's a fair assessment.

I second the nomination of 826X roms as incredibly stable. (blogspot.826x.com) I've never even had a freeze let alone a screen of death. Definitely give that a try if you are unhappy with your rom.

I've also now started to notice a crack or two after 1.1 years. Had the keyboard problems and a screen problem, but overall I am happy with it.