Hi Everyone,
I am in need to know how to change the default homepage of litening rom as it gos to the very first page when i push the home button.
I would like to go to the middle page when i push it which requires i edit a line somewhere and put the number 3 in it.
Could anyone help me and the many others who dont know.
Thank you.
rom of Cognition provide this function base on official launcher, but i prefer 3rd party launchers such as adw launcher, zeam launcher and etc. all of which are configable.
Me too
Hey guys,
I wan't another screen to be default, so brought if I press the home button, too. I managed to change it on stock Samsung ROM with this method
http://forum.xda-developers.com/showthread.php?t=1096521
however there is no default.prop in system directory in Litening ROM! (I use 1.5).
So i wrote this ro.csc.homescreen.defaultscreen=4 into the "build.prop" file of the system folder -> does not work :'(
Then I have written it to the "default.prop" file in the / folder (so nothing ) -> does not work either : Seems to be that the Litening ROM overwrites this file every restart!
Please someone help me
I am in the exact same boat as you now. It does get annoying always going to the first page.
So not 1 person knows how to change it?
Easy way is to use Launcherpro, you an choose the amount of screens and which to use as default.
Put the below string in default.prop file. Replace 3 with whichever
screen as default.
ro.csc.homescreen.defaultscreen=3
This will set the homescreen at start up, but not working on pressing home screen button.
Sent from my GT-I9100 using XDA Premium App
kirdroid said:
Put the below string in default.prop file. Replace 3 with whichever
screen as default.
ro.csc.homescreen.defaultscreen=3
This will set the homescreen at start up, but not working on pressing home screen button.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
I dont get why it doesnt work when you press the homescreen button? LiteRom definately needs the feature to allow you to change it.
WhiteXR said:
I dont get why it doesnt work when you press the homescreen button? LiteRom definately needs the feature to allow you to change it.
Click to expand...
Click to collapse
This feature does not depend of LiteRom(only if he finds a way to modify the rom somehow)
This file witch we were modifying up to now is missing in the latest rom's so another way must be found.
Maybe somebody with more skills can help us of corse the suggestions of changing the launcher are not solving our problem.
we need solutions for touchwiz.
this makes me sad
I am very new to android and rooting and roms, etc. I finally figured out how to flash a rom so i decided to go with lightening 6.1. Its really frustrating when small things like these don't work.
I really hope someone can come up with a fix. I've also noticed that adfree android app also doesn't work with this rom and thats such a bummer. I dont want to go back to my stock rom...
chmsalman said:
I am very new to android and rooting and roms, etc. I finally figured out how to flash a rom so i decided to go with lightening 6.1. Its really frustrating when small things like these don't work.
I really hope someone can come up with a fix. I've also noticed that adfree android app also doesn't work with this rom and thats such a bummer. I dont want to go back to my stock rom...
Click to expand...
Click to collapse
and just what is it that doesnt work for you?
i tried litening 6 then cyanogen and returned running to litening 6.1 i should had never left it lol
Everything works ok for me.
This is my first android plugin for the sony ericsson Liveview
It has some Rooted-Phone-Only features that are watch-sided User-Interface only, its features are
-Reboot System (or a normal reboot basicly)
-Reboot Recovery
-Reboot Bootloader (if phone compatible, otherwise it will most likely reboot into system)
-Power Off
This app uses on-screen words when you move the left and right border touchpad area(s) to switch between the options then hit select to reboot/power off to the option on the screen, nothing more, nothing less
**note** after the phone is rebooted u WILL need to re-sync your liveview (as a reboot stops the bluetooth connection of course, not to mention a power off)
Download:
Google Play Download Link
Thank you for that. can you add 'shutdown' too?
Gesendet von meinem LT18i mit Tapatalk 2
kixaze71 said:
Thank you for that. can you add 'shutdown' too?
Gesendet von meinem LT18i mit Tapatalk 2
Click to expand...
Click to collapse
its under "power off", sorry for the confusion
Hmmmm not working for me. I hit the reboot icon, the liveview screen goes off for a second, then turns back on with the reboot icon (plugin), as if nothing happens. No change to liveview or phone.
devinpatterson said:
Hmmmm not working for me. I hit the reboot icon, the liveview screen goes off for a second, then turns back on with the reboot icon (plugin), as if nothing happens. No change to liveview or phone.
Click to expand...
Click to collapse
This bug is also on my second device (Arc S). I think i know what is wrong. Reboot a phone needs root acess. But my phone does not ask me, wheter I want to give the plug-in root acess. Has your phone ask you, wheter you want to give the acess (superuser/superSU)
@jkok: is it possible to add a Action-button, in the Plug-in-Preferences on Phone, which enables the rootacess without the liveview? Also there could be a Test Button, which shutdowns the phone for testing.
kixaze71 said:
This bug is also on my second device (Arc S). I think i know what is wrong. Reboot a phone needs root acess. But my phone does not ask me, wheter I want to give the plug-in root acess. Has your phone ask you, wheter you want to give the acess (superuser/superSU)
Click to expand...
Click to collapse
Nope, never asked me for root either. Samsung S3, rooted
devinpatterson said:
Nope, never asked me for root either. Samsung S3, rooted
Click to expand...
Click to collapse
So jkok has to do something
kixaze71 said:
So jkok has to do something
Click to expand...
Click to collapse
sorry ive been busy doing some things in the family lately ill look into these problems, and if i can ill add a check superuser button, so be patient ok?
The strange thing is, that it works on my Arc s, (SU question after clicking reboot on Liveview), but it does work on Xperia Play (no SU question). Both on ICS. But it works well on arc. Great work!
Send from my LT18i using Tapatalk 2
ok new version is uploaded, i couldn't add a setting to check, but i have it now to check (and send request if not granted/denied) every time the app opens, and/or onCreate()'d. hopefully this will help better then when the function is initiated (e.g hit select after reboot option is visible)
jkok said:
ok new version is uploaded, i couldn't add a setting to check, but i have it now to check (and send request if not granted/denied) every time the app opens, and/or onCreate()'d. hopefully this will help better then when the function is initiated (e.g hit select after reboot option is visible)
Click to expand...
Click to collapse
I will try it!
Send from my LT18i using Tapatalk 2
jkok said:
This is my first android plugin for the sony ericsson Liveview
It has some Rooted-Phone-Only features that are watch-sided only, its features are
-Reboot System
-Reboot Recovery
-Reboot Bootloader (if phone compatible)
-Power Off
This app uses on-screen words when you move the left and right border touchpads to switch between the options then hit select to reboot/power off to the option on the screen, nothing more, nothing less
Download:
Reusable Download Link
Click to expand...
Click to collapse
Thanks! Will use it on my new Xperia Z1 when it comes in
damitch300 said:
Thanks! Will use it on my new Xperia Z1 when it comes in
Click to expand...
Click to collapse
Thanks! glad to have helped, its one of the simpleist apps ive done tbh it just runs in android's shell (with root permissions, or else it would have to be a system app to reboot, only with different code then i used) so the way i did it you dont need it to be a system app, but requires rooted phone.
P.S. Thanks for bumping this the overall downloads went from 23 all the way to 98 since u posted 0.0... lol
edit: nvm i didnt see it on the front page of the portal lol
jkok said:
Thanks! glad to have helped, its one of the simpleist apps ive done tbh it just runs in android's shell (with root permissions, or else it would have to be a system app to reboot, only with different code then i used) so the way i did it you dont need it to be a system app, but requires rooted phone.
P.S. Thanks for bumping this the overall downloads went from 23 all the way to 98 since u posted 0.0... lol
edit: nvm i didnt see it on the front page of the portal lol
Click to expand...
Click to collapse
Well the homepage of xda shows your app but the link to your topic was broken.
And np on helping aswell haha.
Congratulations on the portal post!!
ClearD said:
Congratulations on the portal post!!
Click to expand...
Click to collapse
Thanks its my 3rd one (2nd app tho) lol, this one i didnt even mention and it got posted =) i guess im really getting better as a contributer lol
here you go liveviewers i posted this app also on Google Play, the Version is Considered FINAL as its fully working as intended without any bugs as long as u have a good connection, and ARE ROOTED+ALLOW SUPERUSER AT LEAST ONCE
but heres the link, the OP's Link has been updated too, if you need an alternitive download incase u are play-store blocked or cant download it feel free to reply here and ill post the old link in addition to the playstore link =)
https://play.google.com/store/apps/details?id=com.KittleApps.plugins.liveview.RebootPlugin
It really annoys me, when i enable golve mode, for extra responding, and when i gentelly touch the screen, a respond circle start to appear on the screen, so i figured it out, and i found where these things are.
You must be rooted, and install any file explorer (with root rights) and navigate to /system/somc/touch/images/
And you will find two pictures.
The way you can do it is to delete those two (It won't harm anything).
The way that i done it is to change the rights for both of them so they cannot be readable from system to try to show them.
And then rebooted and I am happy now that I could touch so soft, and nothing could appear.
HIT THANKS IF HELPED!!
Sent by me from my Z2.
Jhon998 said:
It really annoys me, when i enable golve mode, for extra responding, and when i gentelly touch the screen, a pind circle start to appear on the screen, so i figured it out, and i found where these things are.
You must be rooted, and install any file explorer (with root rights) and navigate to /system/somc/touch/images/
And you will find to pictures.
The way that i done it is to change the rights for both of them, it hows (rw r r) (or 644).
I changed both of them to just (r) or (i don't actually know).
And then rebooted and Iam happy now that I could touch so soft, and nothing would appear.
HIT THANKS IF HELPED!!
Sent by me from my Z2.
Click to expand...
Click to collapse
You could delete pngs instead of changing permissions.
Even...this isn't bad at all...you can revert to stock in a sec without restoring your backup.
You have my tnx
funky0308 said:
You could delete pngs instead of changing permissions.
Even...this isn't bad at all...you can revert to stock in a sec without restoring your backup.
You have my tnx
Click to expand...
Click to collapse
Yes you could, but if something went wrong, if not deleted then just revert the permissions.
Sent by me from my Z2.
My nook touch (unrooted) runs 1.2.2, but it has bugs now ( the home button doesn't work most of time, screensaver goes on in several seconds during reading, etc. ). I think a reinstallation of the firmware may most likely resolve the issues. ( already tried erase and deregoster, doesn't change anything, as expected ). But the problem is after putting the update zip file into nook's root directory, nook just erases it without doing anything. So my question: any tool can be used to force nook reinstall the update zip without checking version number? Thx in advance for any help.
smjohn1 said:
My nook touch (unrooted) runs 1.2.2, but it has bugs now ( the home button doesn't work most of time, screensaver goes on in several seconds during reading, etc. ). I think a reinstallation of the firmware may most likely resolve the issues. ( already tried erase and deregoster, doesn't change anything, as expected ). But the problem is after putting the update zip file into nook's root directory, nook just erases it without doing anything. So my question: any tool can be used to force nook reinstall the update zip without checking version number? Thx in advance for any help.
Click to expand...
Click to collapse
You need to do a factory re-image so that the onboard OS version will be older than 1.2.2.
Power down. Then restart, and as soon as the "Read Forever" screen appears, press and hold the two lower hardware buttons. Wait for the prompt. Once the Nook is re-imaged it will accept the update again.
Thank you, but by two lower hardware buttons, you mean the page turning buttons?
nmyshkin said:
You need to do a factory re-image so that the onboard OS version will be older than 1.2.2.
Power down. Then restart, and as soon as the "Read Forever" screen appears, press and hold the two lower hardware buttons. Wait for the prompt. Once the Nook is re-imaged it will accept the update again.
Click to expand...
Click to collapse
Ha, I tried, but problem is the Home button doesn't work. Any other suggestions? Thanks.
smjohn1 said:
Ha, I tried, but problem is the Home button doesn't work. Any other suggestions? Thanks.
Click to expand...
Click to collapse
Yes the two lower "page turning" buttons. Is the "n" button used during that sequence? I didn't remember that. I guess that's in the prompts. Well, I dunno. NookManager can be used to trigger the factory image, but if you say that requires the not-working button, then you are SOL. Even CWM is going to need that button to select options.
nmyshkin said:
Yes the two lower "page turning" buttons. Is the "n" button used during that sequence? I didn't remember that. I guess that's in the prompts. Well, I dunno. NookManager can be used to trigger the factory image, but if you say that requires the not-working button, then you are SOL. Even CWM is going to need that button to select options.
Click to expand...
Click to collapse
Any tools that can be used to peek into Nook's file system through PC ( Linux ) to delete something and add something to trigger re/installation? The whole reason I am trying to reinstall is that the Home button doesn't work most of time, and I checked it is not a hardware problem.
smjohn1 said:
Any tools that can be used to peek into Nook's file system through PC ( Linux ) to delete something and add something to trigger re/installation? The whole reason I am trying to reinstall is that the Home button doesn't work most of time, and I checked it is not a hardware problem.
Click to expand...
Click to collapse
AFAIK what you want to do (if you knew exactly what) requires root access--which you don't have. There is an app that has an option which makes the NST very angry and triggers a no-escape factory reset (I've fallen victim to it once), but to install it you would need--you guessed it--root.
I honestly don't remember whether the factory reset option of NookManager is promptless or just the usual. Seems to me it just takes off once you remove the card and the device reboots, but I could be misremembering. I have another day of work on something and then I will be doing a reset on one of my devices, so I could tell you then.
nmyshkin said:
AFAIK what you want to do (if you knew exactly what) requires root access--which you don't have. There is an app that has an option which makes the NST very angry and triggers a no-escape factory reset (I've fallen victim to it once), but to install it you would need--you guessed it--root.
I honestly don't remember whether the factory reset option of NookManager is promptless or just the usual. Seems to me it just takes off once you remove the card and the device reboots, but I could be misremembering. I have another day of work on something and then I will be doing a reset on one of my devices, so I could tell you then.
Click to expand...
Click to collapse
Thank you very much. Waiting for your experiment results.
1) I can do root. But I couldn't find the package any more. Any pointers?
2) What do you by removing the card? Which card? I was planning to open the back cover and remove the battery, but then I found out you would need a T5 Torx screwdriver, which I don't have. So I gave up.
smjohn1 said:
Thank you very much. Waiting for your experiment results.
Click to expand...
Click to collapse
So this is your lucky day. Mark it on the calendar and remember it sometime when it seems to be raining excrement on you.
NookManager invokes the factory re-image without user input. All you have to do is make a NookManager card. If you're not interested in rooting, etc., you don't need to do any of the updates. The original NookManager thread is here and the files are available. You just need an SD card which you can recover later if you don't want to root, etc. If you want to play around with rooting, NookManager needs to be updated for 1.2.2. The directions are in this post. Frankly, if I were you I'd just want to get my device working properly right now and possibly think about other stuff after all the dust has settled.
To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no (I hope your side buttons are working..........). Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update.
Two things: tell me you are not outside the US. That could change everything. And, download a fresh copy of the 1.2.2 update zip. It's possible your original is corrupted.
I hope you are right and that this is not a hardware issue.
Good luck.
nmyshkin said:
So this is your lucky day. Mark it on the calendar and remember it sometime when it seems to be raining excrement on you.
NookManager invokes the factory re-image without user input. All you have to do is make a NookManager card. If you're not interested in rooting, etc., you don't need to do any of the updates. The original NookManager thread is here and the files are available. You just need an SD card which you can recover later if you don't want to root, etc. If you want to play around with rooting, NookManager needs to be updated for 1.2.2. The directions are in this post. Frankly, if I were you I'd just want to get my device working properly right now and possibly think about other stuff after all the dust has settled.
To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no (I hope your side buttons are working..........). Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update.
Two things: tell me you are not outside the US. That could change everything. And, download a fresh copy of the 1.2.2 update zip. It's possible your original is corrupted.
I hope you are right and that this is not a hardware issue.
Good luck.
Click to expand...
Click to collapse
Thanks a lot and I am in US!
Everything you said was correct with only one minor thing: NookManager doesn't have to be updated to 1.2.2. As is, it will boot. But after factory re-image, 1.2.2 has to be applied, otherwise Nook cannot register due to Nook server's TLS issue even NST says network connection problem.
Thanks again for this wonderful guide. Hope this is useful to other (unlucky) people.
As for my NST, after reinstallation, the Home button still doesn't work. So I have to believe it seems to be hardware problem and the cover has to be opened.
nmyshkin said:
So this is your lucky day. Mark it on the calendar and remember it sometime when it seems to be raining excrement on you.
NookManager invokes the factory re-image without user input. All you have to do is make a NookManager card. If you're not interested in rooting, etc., you don't need to do any of the updates. The original NookManager thread is here and the files are available. You just need an SD card which you can recover later if you don't want to root, etc. If you want to play around with rooting, NookManager needs to be updated for 1.2.2. The directions are in this post. Frankly, if I were you I'd just want to get my device working properly right now and possibly think about other stuff after all the dust has settled.
To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no (I hope your side buttons are working..........). Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update.
Two things: tell me you are not outside the US. That could change everything. And, download a fresh copy of the 1.2.2 update zip. It's possible your original is corrupted.
I hope you are right and that this is not a hardware issue.
Good luck.
Click to expand...
Click to collapse
See the previous one.
smjohn1 said:
Thanks a lot and I am in US!
Everything you said was correct with only one minor thing: NookManager doesn't have to be updated to 1.2.2. As is, it will boot. But after factory re-image, 1.2.2 has to be applied, otherwise Nook cannot register due to Nook server's TLS issue even NST says network connection problem.
Thanks again for this wonderful guide. Hope this is useful to other (unlucky) people.
Click to expand...
Click to collapse
Yes the only reason to update NookManager is to root 1.2.2
I'm sorry about the apparent hardware issue. I don't know where to go with that, but just to throw this out: rooting with NM installs NookTouchMod which would allow you to reassign the "n" button function to another hardware button. Awkward and less than ideal but perhaps a way to salvage the device if all else fails.
nmyshkin said:
Yes the only reason to update NookManager is to root 1.2.2
I'm sorry about the apparent hardware issue. I don't know where to go with that, but just to throw this out: rooting with NM installs NookTouchMod which would allow you to reassign the "n" button function to another hardware button. Awkward and less than ideal but perhaps a way to salvage the device if all else fails.
Click to expand...
Click to collapse
Wonderful and thx again!
Already rooted, and after reboot, saw "Home" and "ReLauncher", chose "ReLauncher", and then the setting icon at upper right. Lots of functions, but didn't see NookTouchMod or where can set up buttons functions. Only saw "Screen buttons behavior" in the Advanced Settings, but these are not to set hardware buttons.
The only I need is in a book reading mode, press a button to return to the library, so that can switch to another book easily. But I guess I am closer now
smjohn1 said:
Wonderful and thx again!
Already rooted, and after reboot, saw "Home" and "ReLauncher", chose "ReLauncher", and then the setting icon at upper right. Lots of functions, but didn't see NookTouchMod or where can set up buttons functions. Only saw "Screen buttons behavior" in the Advanced Settings, but these are not to set hardware buttons.
The only I need is in a book reading mode, press a button to return to the library, so that can switch to another book easily. But I guess I am closer now
Click to expand...
Click to collapse
Mmm....Relaunch. Not my favorite, but many people like it for its "simplicity". There is a way in Relaunch to get to an "app drawer" type screen which shows all the installed apps. That's where you'll find NTM and everything else. The sad truth is, I can't tell you how to get there. For me, Relaunch is counter-intuitive and strange, but I do know that thereis an app drawer as I have seen it myself back in the day when all this was new to me. I've done a cursory forum search but come up empty. That's the other thing that always riled me up about Relaunch. It's like its operations are a secret. There must be documentation somewhere, but I don't know where. I have a vague recollection that at the center bottom of some screen or another there is an actual app drawer symbol, but getting to that magic screen is the issue.
I'll keep looking, but right now I'm coming up empty.
Edit: in the long run, once you find NTM and reassign the "n" button, you might be better served by having the standard B&N home screen as your default launcher. This would provide you with your accustomed functions, easy access to the Library via the quick-nav buttons, etc. You could assign along press of the same button to bring up Relaunch for the few times you'll want it.
nmyshkin said:
Mmm....Relaunch. Not my favorite, but many people like it for its "simplicity". There is a way in Relaunch to get to an "app drawer" type screen which shows all the installed apps. That's where you'll find NTM and everything else. The sad truth is, I can't tell you how to get there. For me, Relaunch is counter-intuitive and strange, but I do know that thereis an app drawer as I have seen it myself back in the day when all this was new to me. I've done a cursory forum search but come up empty. That's the other thing that always riled me up about Relaunch. It's like its operations are a secret. There must be documentation somewhere, but I don't know where. I have a vague recollection that at the center bottom of some screen or another there is an actual app drawer symbol, but getting to that magic screen is the issue.
I'll keep looking, but right now I'm coming up empty.
Click to expand...
Click to collapse
You are right again. I do see "app drawer" at the bottom. Inside there are things like "library", "setting", "app (amazon)", "Kconnect", etc., just couldn't find NTM.
I could reboot to Home too, but I didn't find NTM either. Anyhow, I will dig and search too, and report back here.
Thx again.
smjohn1 said:
You are right again. I do see "app drawer" at the bottom. Inside there are things like "library", "setting", "app (amazon)", "Kconnect", etc., just couldn't find NTM.
I could reboot to Home too, but I didn't find NTM either. Anyhow, I will dig and search too, and report back here.
Thx again.
Click to expand...
Click to collapse
You're fast.
Info on basic ReLaunch functions here: https://github.com/yiselieren/ReLaunch. NTMM icon looks like big bold "n" with a bold little broken circle in it. Gotta be there.
Edit: ...unless....something went awry during the rooting process. You can root "again" with no harm/no foul and watch carefully this time the list of "dones" to make sure it did not throw an error for NTMM.
nmyshkin said:
You're fast.
Info on basic ReLaunch functions here: https://github.com/yiselieren/ReLaunch. NTMM icon looks like big bold "n" with a bold little broken circle in it. Gotta be there.
Edit: ...unless....something went awry during the rooting process. You can root "agai n" with no harm/no foul and watch carefully this time the list of "dones" to make sure it did not throw an error for NTMM.
Click to expand...
Click to collapse
OK, I think I need to go back to basics:
1. here is the NM used: http://download.doozan.com/nook/NookManager-0.5.0.zip
2. Here are some screen shots from relaunch:
1) relauncher
2) all apps installed ( from the middle icon at the bottom ): no NTMM there
3) and 4) settings ( from right icon at the top )
3. I don't see a way to install other Android apps, except from Amazon stores ( which I didn't try ) but not from Google App store. Did I install a "wrong" version of NM?
4. One more thing: I "rooted" again, finished quickly, and no changes after boot ( My guess is NM sees the same root package to decide not to do anything ).
Any advice?
----------------------------------------------------------------------------------------------------
After posting above, I installed NTMM-0.4.0.apk successfully, but it says it needs modified jars. From https://forum.xda-developers.com/showthread.php?t=1991048 and https://github.com/doozan/NookTouchPatches.
So NTMM wasn't installed during root.
Now my questions:
how to install these patches? I am using Linux with no adb ( I don't want to use adb anyway ), any apk file that can be written to sdcard for quick and easy installation?
and does this patch work for 1.2.2?
smjohn1 said:
OK, I think I need to go back to basics.
Click to expand...
Click to collapse
Yes, I think you missed some important points from what I wrote previously. Here is the only sequence that is going to give you the desired result:
1. Factory re-image
2. Install 1.22 update
3. Register
4. Prepare NookManager card from here.
5. Update NookManager card following the directions here. You MUST do at least the update for 1.2.2 or root will not be successful and your device will be messed up. Other updates are optional, but know that some apps like Amazon App Store are dead. Other updates deal with these issues.
6. Boot with the NookManager card inserted.
*Optional* 7. Make a back-up of your registered device running 1.2.2. This can save you extra steps if you need to go back for any reason or suffer some catastrophe that seriously messes with your system.
8. Root using NookManager. Watch the screen for check for any failures.
9. Reboot, choosing ReLaunch as a launcher (but do not set as default yet).
10. Use NTMM to assign "n" button function ("Home") to some other hardware button. This is how you will get to QuickNav buttons.
11. Use NTTM to assign long-press of your reassigned "n" button to ReLaunch.
12. Reboot.
13. Select "Home" as default launcher (i.e., check the little box before choosing "Home". This choice can be changed later if you want.
Now you're back to a functioning system. Additional apps are installed by moving the apk file from your PC to a folder on your NST ("Download"?) and tapping the app icon in ReLaunch. Apps are uninstalled by long-pressing the app icon (I think).
The Amazon App Store is useless as you can read in the directions for updating NookManager.
Don't skip any steps.
nmyshkin said:
Yes, I think you missed some important points from what I wrote previously. Here is the only sequence that is going to give you the desired result:
1. Factory re-image
2. Install 1.22 update
3. Register
4. Prepare NookManager card from here.
5. Update NookManager card following the directions here. You MUST do at least the update for 1.2.2 or root will not be successful and your device will be messed up. Other updates are optional, but know that some apps like Amazon App Store are dead. Other updates deal with these issues.
6. Boot with the NookManager card inserted.
*Optional* 7. Make a back-up of your registered device running 1.2.2. This can save you extra steps if you need to go back for any reason or suffer some catastrophe that seriously messes with your system.
8. Root using NookManager. Watch the screen for check for any failures.
9. Reboot, choosing ReLaunch as a launcher (but do not set as default yet).
10. Use NTMM to assign "n" button function ("Home") to some other hardware button. This is how you will get to QuickNav buttons.
11. Use NTTM to assign long-press of your reassigned "n" button to ReLaunch.
12. Reboot.
13. Select "Home" as default launcher (i.e., check the little box before choosing "Home". This choice can be changed later if you want.
Now you're back to a functioning system. Additional apps are installed by moving the apk file from your PC to a folder on your NST ("Download"?) and tapping the app icon in ReLaunch. Apps are uninstalled by long-pressing the app icon (I think).
The Amazon App Store is useless as you can read in the directions for updating NookManager.
Don't skip any steps.
Click to expand...
Click to collapse
Ha, the step missed was 5, as it was difficult to change the files. But I remade an NM card ( there must be something wrong with the old one ), afterwards it was to update NM to 1.2.2.
Now buttons are reassigned and this reader is usable again ( I don't plan to make it a full android pad, as there are already too many tablets in house ). So this e-reader owes its life to you. Big thanks!
One last thing: how to reset Default back to Home instead of Relaunch? ( The re-root was quick, as it probably installed NTMM. But reboot doesn't give chance to reset default back to Home, it still goes straight to Relaunch. Of course I can live with it, but it would be nicer to configure as you suggested. )
smjohn1 said:
One last thing: how to reset Default back to Home instead of Relaunch? ( The re-root was quick, as it probably installed NTMM. But reboot doesn't give chance to reset default back to Home, it still goes straight to Relaunch. Of course I can live with it, but it would be nicer to configure as you suggested. )
Click to expand...
Click to collapse
If there is a way to access the App Manager through ReLaunch, you can run down the list until you get to ReLaunch and there remove any default actions associated with it.
If that is not obvious then the next easiest thing is to install yet another launcher! So you could transfer a copy of ADW Launcher from the NookManager update page to your NST and install it. If you then reboot it will trigger the App Picker dialog again because now there is a new choice. Before you select "Home", be sure to tick the little check box.
Then you can uninstall ADW Launcher. It's possible that may trigger another App Picker with the remaining two choices but I don't think so.
Once that's sorted you can finish your button reassignments. I think ReLaunch actually hijacks some of the QuickNav buttons so you might have to use NTTM to return them to default or pick completely new assignments, as you like.
I'm glad you were able to get the device back in a usable state. I love my NST for reading. After all these years I think it's still a great little piece of technology.