Related
Looks like the folks over in the I9000 forums got tired of it before we did!
aditya_t90 wrote a simple little program available through the market that allows you to toggle the media scanner on and off!
Your phone will start up and it will still prepare media but it doesn't bother scanning it. The cons to this, is that your phone won't detect new music added to it (at least through the default media player), but you can rectify this by simply running the program and invoking a media scan. No more scanning after yanking out your USB cable or extra sluggish phone startups!
Just hit the market and search for: Rescan Media ROOT (Not the regular Rescan Media).
Zilch25 said:
Looks like the folks over in the I9000 forums got tired of it before we did!
aditya_t90 wrote a simple little program available through the market that allows you to toggle the media scanner on and off!
Your phone will start up and it will still prepare media but it doesn't bother scanning it. The cons to this, is that your phone won't detect new music added to it (at least through the default media player), but you can rectify this by simply running the program and invoking a media scan. No more scanning after yanking out your USB cable or extra sluggish phone startups!
Just hit the market and search for: Rescan Media ROOT (Not the regular Rescan Media).
Click to expand...
Click to collapse
Cool. Also the new leaked Captivate ROM is supposed to have a way better media scanner implementation.
Since I never really change anything on my SD card, I'm going to check this out.
I can confirm the new ROM is better... it's about as fast as it is in in the I9000 ROMS, which is to say: tolerable. But this makes it much better on any ROM
Zilch, thank you for this post! I was looking for something having to do with the media scanner as soon as I realized the media player doesn't find new music until I rebooted the phone.
have any of you had an issue with this app just hanging at the:
Doing Stuff
Hardcore background Kung-fu
screen?
Even when I type in the terminal command it hangs. My phone is fully rooted, and haven't had any issues.
I didn't have this problem, but one guy in the I9000 forums did, I'll link you to the comment from the author:
http://forum.xda-developers.com/showpost.php?p=7630532&postcount=16
Just enter that little code snippet into adb, apparently you only have to do it once and the program should run without any issues after that.
krakerx said:
have any of you had an issue with this app just hanging at the:
Doing Stuff
Hardcore background Kung-fu
screen?
Even when I type in the terminal command it hangs. My phone is fully rooted, and haven't had any issues.
Click to expand...
Click to collapse
I don't know much about the Captivate but you could help me out by opening my app while running adb logcat.
Then post the data you get from logcat.
Also are you running a stock rom or are you running a modified ROM?
Also does the Startup Manager work or does that hang too?
I'll try to fix it if I can. You are the first device I have seen with such a unique issue.
You know what's odd, is that I just reflashed to JM5 on my Captivate and went to reinstall it and I was having the same issue.
What makes even less sense is that after turning on debug mode the program ran flawlessly without me even having to terminate the task
Confirmed: I just turned debug mode off, ran it again and its hanging again. Toggled debug back on and it works again. Weird eh?
Let me sleep over it and I'll try and find a soln.
aditya_t90 said:
Let me sleep over it and I'll try and find a soln.
Click to expand...
Click to collapse
Thanks for the support! Hope this turns out to be an easy one
Turning on USB debugging was the key to getting this working on my Captivate running JH2.
Hello,
I just got my third really fast reboot if I can even call it a reboot.
The fastreboots (I'll call it FRB from now on.) always happened when the CPU was really busy
The phone were getting laggy and didn't respond anymore and the screen shut off but the 4 softbuttons still lit up.
The bootanimation was starting and stopped like 7 seconds later and the display showed the lockmenu.
the first time this happened I just thought "wow, what was a freaking fast reboot"
the second time I just said wtf and accidentally checked the uptime.. 2 days! the phone just rebooted but is still showing 2 days?
and now the 3rd FRB, checked the uptime -> almost 4 days
What the hell? Is someone else experiencing this?
All active apps are stopped and everything is just like a normal reboot
ROM: CyanogenMod 6 08172010 Nightly
Kernel: 2.6.35-925mV-1113MHz-BFS-SVS-AIX-720p-Monks-081610 (max clock: 1036; min: 245; interactive)
And I think I also noticed a FRB before using this kernel and a previous CM6 nightly
I've had this happen too. The only thing I noticed is it happened after my phone had been idle for a long period of times. Its happened roughly 3-5 times for me. As a windows user I admit it didn't concern me much lol
It's not a reboot, it's Android restarting. The back-end Linux stuff stays up. Pretty obvious when it's the boot animation you see, not the solid X.. And as you say, it's pretty fast.
And yes I suspect there's a watchdog.. If the whole system is stalled for > N seconds, restart it. Waze does this to me once or twice a week.
Yeah, this has been happening to me a lot more lately, especially when I start installing apps from the market after a wipe and restore, it messes up the market. It also messes up on Titanium backup. Getting very annoying.
Has happened on Enoms, and LeoFroyo ROMs.
khaytsus said:
Pretty obvious when it's the boot animation you see, not the solid X..
And yes I suspect there's a watchdog.. If the whole system is stalled for > N seconds, restart it.
Click to expand...
Click to collapse
Yes, makes sense
I've been calling it a random/soft reboot and it has been happening with eclair as well.
Happens for me too, got this stuff twice, both at car's dock with GPS and navigation on.
Isn't this kind of reboot a documented thing? How comes?
EDIT: not OC/UV, enom's 2.11.3.
because it seems its only mainly happening on custom roms lol
I don't think it's the custom rom. At least not enom's one, because of his conservative kernel policy. Looks more like something with overheating (both times it happened for me I've used a car dock with 3g,bt,gps on and charging)...
disgustip8ted said:
because it seems its only mainly happening on custom roms lol
Click to expand...
Click to collapse
Nope, I see this 1-2 times a week since I got my N1 2 months ago and only switched to a custom this last weekend.
tltester said:
I don't think it's the custom rom. At least not enom's one, because of his conservative kernel policy. Looks more like something with overheating (both times it happened for me I've used a car dock with 3g,bt,gps on and charging)...
Click to expand...
Click to collapse
Not overheating for me.. It's anything that bogs the system, as previously explained. But of course there could be many paths to this issue.
It's not the roms....I'm totally stock running FRF91 with absolutely no root access enabled and this happened to me yesterday. It caught me off guard too because like others said my phone went into a state of sluggish responsiveness and then all of a sudden it jumped right to my boot animation, no big X. about 5-8 seconds later I was back at the homescreen watching my Widgets load up like they do when the phone first boots up.
Is it possible to create an app that forces this kind of reboot? I think not
xPatriicK said:
Is it possible to create an app that forces this kind of reboot? I think not
Click to expand...
Click to collapse
I think so.
Try from adb:
Code:
adb shell stop
adb shell start
Is the observed behaviour the same?
djmcnz said:
Is the observed behaviour the same?
Click to expand...
Click to collapse
Yes
/10chars.
ptrrrrrck said:
Is it possible to create an app that forces this kind of reboot? I think not
Click to expand...
Click to collapse
djmcnz said:
I think so.
Try from adb:
Code:
adb shell stop
adb shell start
Click to expand...
Click to collapse
Quite an old thread here, never the less: any chance of reproducing this without ADB acces but on the device itself? Quite handy when playing around with the new T-Mobile Theme Changer and instead of a lenghty reboot reloading the shell would suffice. Eh...?
Sense ROMs have the feature ("Hot restart"), so it's reproducible.
schaggo said:
Quite an old thread here, never the less: any chance of reproducing this without ADB acces but on the device itself? Quite handy when playing around with the new T-Mobile Theme Changer and instead of a lenghty reboot reloading the shell would suffice. Eh...?
Click to expand...
Click to collapse
Well, you can stop the shell via terminal on the phone but then you'd have no way to start it again...
A week ago I used a CM Nightly and noticed the 'Suspend' mode in the powerbutton menu (when you hold the powerbutton). I pressed it and it kinda rebooted like this. Not sure if it's what I meant in post 1 .. and it's not in the nightlies anymore
schaggo said:
Quite an old thread here, never the less: any chance of reproducing this without ADB acces but on the device itself? Quite handy when playing around with the new T-Mobile Theme Changer and instead of a lenghty reboot reloading the shell would suffice. Eh...?
Click to expand...
Click to collapse
There are a few apps on the market that can do this, it's called hot booting (Search for hot boot). The only one I can see that is free is root toolbox but I couldn't get it to work on my S2. Quickboot plus has the option and it works just fine.
** Work-In-Progress: Ubuntu Touch Preview is just that.. a PREVIEW. Do not complain about missing features, etc. The OS isn't nearly ready for primetime. **
Curious as to how the Ubuntu Touch Preview looks? Why not load it on your Droid 3 and see for yourself.
Instructions:
1. Make a Titanium Backup and/or backup in recovery of your current Android (or just keep it on a different slot). This preview is fun to play with but not a replacement for something as developed as CM 10.1
2. Download the Droid 3 Mini-Android base for Ubuntu Touch and place it on your device:
[03/01] http://goo.im/devs/Hashcode/solana/ubuntu-phablet/ (use the newest one)
3. Download the latest Ubuntu Touch Preview Filesystem .zip from Ubuntu:
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/quantal-preinstalled-phablet-armhf.zip
If the above link is broken, use this link for a full listing of the current build files (download the quantal-preinstalled-phablet-armhf.zip .. soon to be raring-preinstalled-phablet-armhf.zip):
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
4. Reboot into Safestrap. Create a NEW 2GB ROM in the #4 slot.
IMPORTANT:
4a. Install the quantal-preinstalled-phablet-armhf.zip FIRST, and then the phablet-2013xxxx.zip SECOND.
5. Reboot and Enjoy
FIRST BOOT TAKES A LONG TIME. AND THERE'S NO BOOT ANIMATION. BE PATIENT (MAYBE 3-4 MINUTES).
WHAT WORKS:
Display
Touch screen
Wifi
Audio
WHAT DOESN'T WORK:
There's so much that is still being implemented into the Touch version of Ubuntu, that this list could get pretty long.
Due to memory issues, the device gets VERY laggy after just a little while of use. This means the swap mem is full. I hope they work on the amount of memory used and how it's freed over time.
Barely any sensors other than touchscreen work. IE: no rotation, etc. Ubuntu WIP issue.
No HD codecs (still being worked on) Ubuntu WIP issue.
No screen timeout / auto blank -- becareful when walking away from the device. Need to press the power button to turn the screen off. Ubuntu WIP issue.
RELATED UBUNTU TOUCH LINKS:
(Some of these describe how to install it on devices -- you can ignore those instructions and follow the above)
Ubuntu Touch Wiki: https://wiki.ubuntu.com/Touch/
Release Notes: https://wiki.ubuntu.com/Touch/ReleaseNotes
IRC Channel on freenode.net: #ubuntu-touch
Re: [ROM] Ubuntu Touch Preview [02/28: Alpha Update #1]
Neat. I had to battery pull to get it to boot, bootlooped until I did. It feels like unity, for my phone. It'll be interesting to see how it performs on our device when it's complete
Sent from my XT860 using xda premium
Fine!, downloading and booting in moments! i was wondering about this in the forums, some days ago! Hash, you're the best!
Glad to see an alternative for our devices...who knows...maybe this could lead to a fully functional rom...
EDIT: Sadly, it doesn't boot at all...same issues as latest CM10.1, but after a while of black lit screen, the phone turns off...trying later something else
Re: [ROM] Ubuntu Touch Preview [02/28: Alpha Update #1]
FrankieDedo said:
Fine!, downloading and booting in moments! i was wondering about this in the forums, some days ago! Hash, you're the best!
Glad to see an alternative for our devices...who knows...maybe this could lead to a fully functional rom...
EDIT: Sadly, it doesn't boot at all...same issues as latest CM10.1, but after a while of black lit screen, the phone turns off...trying later something else
Click to expand...
Click to collapse
I had the same until I battery pulled
Sent from my DROID3 using xda premium
Looks pretty cool. I think I could get used to that interface pretty quickly. I did have a little trouble getting back into SafeStrap to boot into the stock ROM (or CM10.1 in slot1).
I used both the power button and battery pull to restart, I got the SafeStrap menu, chose boot to recovery, and in a few minutes I get the Ubuntu screen back. I finally got into SafeStrap by holding VolUp & VolDown while powering on and choosing BP Tools (bottom option).
I'll have to go back through the flash process and test a few things. Sorry that it's messing w/ some of your devices.
3/1/13 Build worked fine for me but I do have one of the older CPU's since all the kexec builds have worked for me, first boot time was only like 20 seconds and it still worked pretty quickly (but I only used it for about 10 minutes), seeing something different was refreshing and it took me about a minute to realize there was no lockscreen, most definitely a developer preview but it looks promising.Thanks Hashcode for the preview build and all the work you do, I'll keep testing them when they come out.
oh yeah the safestrap problem persisted for me as well had to hold the volume buttons to get back to Rom selection. No biggie
Hi
I tried phablet-20130301-cm_solana.zip and it worked better than I expected, I could even make calls.
The experience is quite nice and it seems Ubuntu Phone OS is very promising!
Thanks
taksan said:
Hi
I tried phablet-20130301-cm_solana.zip and it worked better than I expected, I could even make calls.
The experience is quite nice and it seems Ubuntu Phone OS is very promising!
Thanks
Click to expand...
Click to collapse
Are you on GSM?
Sent from my DROID RAZR HD using Tapatalk 2
I didn't even try calling. I didn't expect it to work
Sent from my XT860 using xda premium
Right now phone function is only implemented for GSM. The GSM RAZR has working voice calls. I didnt think D3 would work either but in theory it could.
(I occasionally activate a 3g SIM for testing, but didnt for the preview.)
Sent from my DROID RAZR HD using Tapatalk 2
taksan said:
Hi
I tried phablet-20130301-cm_solana.zip and it worked better than I expected, I could even make calls.
The experience is quite nice and it seems Ubuntu Phone OS is very promising!
Thanks
Click to expand...
Click to collapse
I tried dialing one call to one of our office lines while I was booted into Ubuntu . It dialed and rang ok but I couldn't hear the receptionist when she answered and she couldn't hear me.
Sent from my Nexus 7 using Tapatalk HD
Yes, I'm on GSM. I didn't expect it to work either, but I just thought I'd try.
The problem is that it usually doesn't boot and keeps "boot looping". The first time I pulled the battery and it worked, but now it is not working anymore.
I'm trying a reinstallation.
Even though it is quite crude, it worked better than CM10 (the droid 3 version), because the CM10 phone service crashed on start and I couldn't make
calls and neither connect to WiFi
I got it working once again, but after a while it froze. I tried rebooting the phone and it isn't booting anymore.
Ok, booted and tried, it works really well for an early alpha, who knows...this could be the base for a fully functional rom? i'm a dreamer...
Anyway i'm on GSM and calls are lagging of 1-2 rings, and voice seems to be broken, anyway, good work! as usual
Very nice! Works great for being so new. Could not do much as it would not connect to my work WiFi but expected with such an early build. Looking forward to future updates.
Being based on the CM kernel is it safe to assume we will not see any camera function for this unless it first gets worked out in the CM 10 builds?
thanks yet again Hash !
Installed as per the first post.
First boot - no longer than one min I reckon.
Wifi works, got on to FB with browser and even posted
Today showing work mate, dialled his number (without any hint of cell network / settings) and to my amazement not only did it dial, upon answering we could hear each other fine, maybe a tad lagged half a second or so but honestly worked fine!!
May have imagined things but it also appeared to get faster again after 5-10mins of being powered on, reboots no issue.
Just no idea how to power off correctly lol, seems like holding power button puts it in sleep (saw today image very dark but certainly there), then could not wake (happened yesterday also the can not wake part), so I just battery pull, again reboots no issue
Cheers
Ok man im trying to install this on my droid 3 to see how it works and then i was going to try and port ubuntu to the k1 tablet but on part 3 when installing it it will get almost done and by then my phone is very hot as well and any way it will get almost done installing and the phone will go black and i will have to pull the battery to even get the phone to do any thing so im asking what am i not doing right? I will like to get this booted on the droid 3 to get a fill of how this works befor i port to the k1 tablet.
Sent from my K1 using xda app-developers app
---------- Post added at 08:10 PM ---------- Previous post was at 07:16 PM ----------
leerpsp said:
Ok man im trying to install this on my droid 3 to see how it works and then i was going to try and port ubuntu to the k1 tablet but on part 3 when installing it it will get almost done and by then my phone is very hot as well and any way it will get almost done installing and the phone will go black and i will have to pull the battery to even get the phone to do any thing so im asking what am i not doing right? I will like to get this booted on the droid 3 to get a fill of how this works befor i port to the k1 tablet.
Sent from my K1 using xda app-developers app
Click to expand...
Click to collapse
I got it installed i had to install in slot 2 not 4 to get it all the way installed i dont know y this matters but o will any way i tested it in the other slots and it will not work in them ony 2
Sent from my K1 using xda app-developers app
Just got it from Ubuntu:
Known Issues
Power Consumption
Currently the devices can not be shutdown from within the UI or by pressing the power button. Even if you use the power button long press your battery will be drained.
To shutdown a device completely there are two options:
Remove the battery and replace it. (Not an option if battery is not removable)
Stop it from the adb shell by executing the following commands:
adb root
adb shell reboot -p
Memory Usage
Memory usage has not yet been optimized for the devices. It is possible to experience application crashes due to having too many applications open at the same time. A workaround is to close apps that are not being used.
Timezone
The timezone needs to be manually set from the command line. Valid values for timezones can be found in the /usr/share/zoneinfo/zone.tab file. Run the following commands ( specifying your own time zone choice ) with root permission to set your timezone:
Access your device through SSH
Then on the terminal connected to your device run:
echo "America/New_York" | sudo tee -a /etc/timezone
sudo dpkg-reconfigure --frontend noninteractive tzdata
Networking
The Developer Preview has support for Wi-Fi networking via the new network indicator, which supports basic Wi-Fi connections (Open, WEP and WPA Personal). It is possible to configure more advanced settings, however at this time this requires working directly with Network Manager system connection files.
The following network features are not yet included in the Developer Preview:
Airplane Mode/Wi-Fi Power Control
Advanced Settings (e.g. Hidden SSIDs, Manual IP, VPN…)
Bluetooth
Hot Spot/Tethering
Telephony
The Developer Preview currently only supports limited voice and SMS over GSM.
The following Radio technologies are not yet included in the Developer Preview:
CDMA
LTE
Airplane Mode
Settings ( eg. APN choice, 2G only, … )
Mobile data is not supported, data is available via Wi-Fi only.
These Call features are not yet supported:
Emergency Call Support ( ie. ability to dial emergency numbers without a valid SIM card ).
PIN/PUK support for locked SIMs
No SIM filesystem support
Speakerphone
These SMS features are not yet implemented:
MMS
Send error handling
Delivery Reports
leerpsp said:
Ok man im trying to install this on my droid 3 to see how it works and then i was going to try and port ubuntu to the k1 tablet but on part 3 when installing it it will get almost done and by then my phone is very hot as well and any way it will get almost done installing and the phone will go black and i will have to pull the battery to even get the phone to do any thing so im asking what am i not doing right? I will like to get this booted on the droid 3 to get a fill of how this works befor i port to the k1 tablet.
Sent from my K1 using xda app-developers app
---------- Post added at 08:10 PM ---------- Previous post was at 07:16 PM ----------
I got it installed i had to install in slot 2 not 4 to get it all the way installed i dont know y this matters but o will any way i tested it in the other slots and it will not work in them ony 2
Sent from my K1 using xda app-developers app
Click to expand...
Click to collapse
Got it working it tuck 20 m of living the phone on lmao
Sent from my K1 using xda app-developers app
Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/
iamatechnoob said:
Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/
Click to expand...
Click to collapse
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.
chicle_11 said:
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.
Click to expand...
Click to collapse
Wow, you are right, webos has the same problem. I guess I was just in denial that it was a hardware issue and didn't think of checking it in webos. Damn, I don't think HP would want this back right
Sigh guess I should look into the chinapads my friend was recommending just this morning
Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..
iamatechnoob said:
Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..
Click to expand...
Click to collapse
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.
chicle_11 said:
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.
Click to expand...
Click to collapse
Thanks for the help! Will try this after backing up my stuff via Helium.
I have the impression that 10.1 isn't that stable, but I am likely wrong. Dont seem to see any cm10.1 with low deep sleep drain + working camera & mic + most other functions, or I could be looking at the wrong places.
I use milaq's nightlies, and for my needs, it's more than adequate.
I was given an 8gb Fire 7 5th gen I guess from the Black Fridays deals for xmas. What I would like to do is run it mostly as a digital calender, so keep it plugged in, running and having it display the calender most of the time only. Is this something I could do with it, easily?
Ideally I'd like to be able to touch the screen to wake it up, or have the calender events running on a screen saver somehow. I haven't even taken it out the box yet, but would pay to remove ads on the lock screen if I can get something set up so it can work that way for me.
Essentially I rely heavily on calenders over all my devices, as well as reminders, so it has to be linked with a google account.
Lifeformz said:
I was given an 8gb Fire 7 5th gen I guess from the Black Fridays deals for xmas. What I would like to do is run it mostly as a digital calender, so keep it plugged in, running and having it display the calender most of the time only. Is this something I could do with it, easily?
Ideally I'd like to be able to touch the screen to wake it up, or have the calender events running on a screen saver somehow. I haven't even taken it out the box yet, but would pay to remove ads on the lock screen if I can get something set up so it can work that way for me.
Essentially I rely heavily on calenders over all my devices, as well as reminders, so it has to be linked with a google account.
Click to expand...
Click to collapse
This device could be configured to perform such a role but it would take some time to set-up (including a few 'hacks') and come with several caveats. Touch wake is not an option on this device (lacks hardware support) so the display would need to be on 7x24. There's also no ambient light sensor which could be an issue depending on your environment. Reliable Google integration requires rooting and a custom ROM...more work. Really depends how much of a project you want to make of it and the level of personal satisfaction after the last 'T' is crossed.
Davey126 said:
This device could be configured to perform such a role but it would take some time to set-up (including a few 'hacks') and come with several caveats. Touch wake is not an option on this device (lacks hardware support) so the display would need to be on 7x24. There's also no ambient light sensor which could be an issue depending on your environment. Reliable Google integration requires rooting and a custom ROM...more work. Really depends how much of a project you want to make of it and the level of personal satisfaction after the last 'T' is crossed.
Click to expand...
Click to collapse
Thank you for replying. I had a think about it yesterday, and just having a read around, I decided to root it to stop OTA updates as I was on 5.0.1 I think, so I did that, then the guide went on to say about flashing a rom, so I figured why not and did that too :$
After a few problems, first being that I couldn't get the flashfire to work from the rootjunky site, I found the one included with the super tool and installed that through the computer. Flashing appeared to be fine, and it loaded into SlimLP fine. But it seems google play etc didn't get installed. After a lot of head scratching and trying to install apk's etc, I figured to reflash it and see what happened. This was a little problematic as now I couldn't connect via usb to do flashfire, so I eventually copied it over via sd card, and installed the apk that way, just reflashed the OS again and a google one, and this time play is there, working.
So I now have a fire running SlimLP saying its model number: KFFOWI, Android 5.1.1. And it's lovely. I have another fire 7 that I do use as a tablet now, and I wish I could do the same to that one, cept it OTA updated on it to fire os 5.3.2.1, and I guess I can't from reading around. It's stuttery compared to the newly flashed one. Oh well. I guess now I need to investigate calender apps, or lock screen widgets to give me what I want.
Thank you for reply, I read it, then though crikey that does sound complicated, however once I looked at locking down the OTA updates to at least allow me to do it later If I wanted, it kind just followed on.
Lifeformz said:
Thank you for replying. I had a think about it yesterday, and just having a read around, I decided to root it to stop OTA updates as I was on 5.0.1 I think, so I did that, then the guide went on to say about flashing a rom, so I figured why not and did that too :$
After a few problems, first being that I couldn't get the flashfire to work from the rootjunky site, I found the one included with the super tool and installed that through the computer. Flashing appeared to be fine, and it loaded into SlimLP fine. But it seems google play etc didn't get installed. After a lot of head scratching and trying to install apk's etc, I figured to reflash it and see what happened. This was a little problematic as now I couldn't connect via usb to do flashfire, so I eventually copied it over via sd card, and installed the apk that way, just reflashed the OS again and a google one, and this time play is there, working.
So I now have a fire running SlimLP saying its model number: KFFOWI, Android 5.1.1. And it's lovely. I have another fire 7 that I do use as a tablet now, and I wish I could do the same to that one, cept it OTA updated on it to fire os 5.3.2.1, and I guess I can't from reading around. It's stuttery compared to the newly flashed one. Oh well. I guess now I need to investigate calender apps, or lock screen widgets to give me what I want.
Thank you for reply, I read it, then though crikey that does sound complicated, however once I looked at locking down the OTA updates to at least allow me to do it later If I wanted, it kind just followed on.
Click to expand...
Click to collapse
Great! A couple footnotes:
- being one of the lucky few with a 5.0.1 bootloader you can boot a custom/full recovery like TWRP as a alternative to FlashFire (from fastboot ready: 'fastboot boot <image_name>')
- the build of SlimLP for this device has not seen much love since originally posted; you may want to consider a ROM that sees more frequent updates
Post back if you need/want further info on either topic.
Davey126 said:
Great! A couple footnotes:
- being one of the lucky few with a 5.0.1 bootloader you can boot a custom/full recovery like TWRP as a alternative to FlashFire (from fastboot ready: 'fastboot boot <image_name>')
- the build of SlimLP for this device has not seen much love since originally posted; you may want to consider a ROM that sees more frequent updates
Post back if you need/want further info on either topic.
Click to expand...
Click to collapse
Can I do a bootloader after using flashfire? Also I considered a CM rom, vaguely recall using one for an Orange san fran years ago, but wasn't sure on latest, or best and it seems that I can't connect things like supertool through usb now, so could I do a CM rom on top of what I have already using flashfire, or would I need to do something else? I seem to remember having to do an XP machine to do the San Francisco phone way back as it wouldn't connect any other way
Lifeformz said:
Can I do a bootloader after using flashfire? Also I considered a CM rom, vaguely recall using one for an Orange san fran years ago, but wasn't sure on latest, or best and it seems that I can't connect things like supertool through usb now, so could I do a CM rom on top of what I have already using flashfire, or would I need to do something else? I seem to remember having to do an XP machine to do the San Francisco phone way back as it wouldn't connect any other way
Click to expand...
Click to collapse
The CM 12.1 adaptation for this device is excellent; no worries there. I strongly recommend using (booting) TWRP for all future ROM updates. FlashFire is a great tool for those that do not have another option. You do! FlashFire will also work if you can not establish a USB connection.
If you opt to switch ROMs be sure to wipe the system and data (aka app/user) partitions before flashing the new image.
I re-did it all and now have CM 12.1 on it, however I've stalled beyond this as it's a far nicer tablet to use over my non-fiddled with Fire 7. So I'm now using the new one as my main tablet, and will stick the other one, wifi off, in the drawer and sit and wait to see if a roll back is available, or new method to root and flash comes along.