I flashed HC onto the Nook Color, from this thread http://forum.xda-developers.com/showthread.php?t=936995, and it seems to run very slowly, sometimes not registering my touches too well. Is it that way normally or should I flash back to Nookie Froyo? If so, how?
Thanks
Because the source of the rom is a modified SDK image, there were many work arounds that had to be made to the compiled code. As such, the rom can be very shaky, and really isn't suited to be a daily use ROM.
THis image is not representative of Honeycomb; once we get the source code, devs should be able to make a much more stable version and really make an amazing ROM.
Yeah that is normal. Honeycomb at this point is basically a demo. The only fully working non-stock ROM is Froyo.
poofyhairguy said:
Yeah that is normal. Honeycomb at this point is basically a demo. The only fully working non-stock ROM is Froyo.
Click to expand...
Click to collapse
How would I go about getting Froyo instead of HC?
Has anyone got webtop2sd to work with the 901 update?
Has anyone been able to get a full working linux distribution to run on the bionic?
There doesnt seem to be much information at all about webtop and the bionic. There is a ton out there in atrix land.
Thanks for you time. Its appreciated.
I haven't seen where anybody has gotten webtop2sd working on the 901 system. I think the updated webtop does run better. I haven't been getting low memory errors at least.
Sent from my DROID BIONIC using Tapatalk
I now have webtop2sd, webuntu, linux swap all working. Running Eclipse 2.1 rc1 .901
Don't know why it works on Eclipse and couldn't get it working on anything else.
Sent from my DROID BIONIC using Tapatalk
SaddleTramp said:
I now have webtop2sd, webuntu, linux swap all working. Running Eclipse 2.1 rc1 .901
Don't know why it works on Eclipse and couldn't get it working on anything else.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
I wasnt able to get webtop2sd to work on 5.5.893 or 5.9.901...i went back to 5.7 since the versions aren't too diff and webtop2sd works (and getting back is a cinch now)
I thought eclipse *system base* was based on 5.7 ( i know 2.0 is) ..the radios and webtop image don't matter...
You can use the 901 webtop, along with webtop2sd, with other system versions (eg kin3tx uses 5.8 and webtop2sd works) by first flashing to 5.9,then using a custom rom
Sent from my XT875 using XDA App
System shows 5.9.901 in about phone running Eclipse 2.1 rc1, that being said I don't know if that means it's really on .901 system i'm not that knowledgable on the inner workings on all of this. Most of my experience is simple trial and error (and learning from others errors) until I get things running the way I like it
Edit: it is based on ota 5.9.901, with some 5.7 according to nitro. And he would know.
Sent from my DROID BIONIC using Tapatalk
running imilkas aosp v07 and have noticed that when i tether to my mbp it downloads suuuuper slow, on stock it used to fly. anyone know how to fix this?
a detailed response would be awesome as im pretty new to the custom rom game.
proably because stoick was gingerbread with fully written driverts for the device and the ICS is a leak and has hacked drivers etc to make it work on the device, there is no guarantee its going to be the same until samsung release ics
thanks for the input mate but i doubt there's no way to rectify it without waiting for official ics. otherwise it would be listed as a bug...which its not.
I know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel
EDIT: i meant leaks, stupid typo
The kernel is based on GB because of the locked bootloader. At least that's how I am to understand it. In other words I think that the custom ROMs can be improved using the leaked ROMs but they'll still have to remain based on the GB kernel. Unless you update your stock system to ICS that is. I think the biggest thing devs should focus on right now is a way to safely upgrade to ICS where downgrading is possible in order to stay on Verizons official upgrade path.
As it stands, the OTA will look for GB 219 when upgrading so those early adopters won't be able to get future upgrades. Unless devs find a way to downgrade or trick the update that is.
Everything I've said could be wrong however this is how I have come to understand it.
Sent from my DROID4 using XDA
Given that we have the fastboot files can't we just wipe and flash that to downgrade?
Sent from my DROID4 using XDA
azrael293 said:
Given that we have the fastboot files can't we just wipe and flash that to downgrade?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
No, this results in a brick. Fastboot refuses to flash older partitions over new ones.
Sent from my XT894 using xda premium
flamefangahs said:
The kernel is based on GB because of the locked bootloader. At least that's how I am to understand it. In other words I think that the custom ROMs can be improved using the leaked ROMs but they'll still have to remain based on the GB kernel. Unless you update your stock system to ICS that is. I think the biggest thing devs should focus on right now is a way to safely upgrade to ICS where downgrading is possible in order to stay on Verizons official upgrade path.
Click to expand...
Click to collapse
This is why you need kexec - you can load the ICS kernel dynamically, without corrupting your GB install.
Sent from my DROID4 using Tapatalk
highlandsun said:
This is why you need kexec - you can load the ICS kernel dynamically, without corrupting your GB install.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Actually, upgrading to ICS leak is probably the way to go. We can now upgrade from leak 200 to 206, giving us the ability to stay on the upgrade path. Since the XDA forums are dead for the Droid 4, I suggest everyone keep up at droidforums.
Here are the instructions for upgrading from leak 200 to 206:
http://www.droidforums.net/forum/droid-4-roms/209619-get-unstuck-ics-leak-200-aka-upgrading-200-206-instructions.html
Also, I believe Hashcode is working on bringing Safestrap 2.0 to the new ICS leak based on the new kernel, and will be working on getting our ROMs on the new kernel as well.
rumgool said:
Since the XDA forums are dead for the Droid 4, I suggest everyone keep up at droidforums.
Click to expand...
Click to collapse
droidforums is about as dead for the Droid 4 as is XDA. I am really surprised how little interest people have in this phone. I guess I am one of the few that still loves physical keyboards. Only drawback on this phone is the non-removable battery. Otherwise it is rock solid. Had the original Tilt, then TP and TP2. Had the G2 on T-mobile, but reception on that phone was not good and T-mobile Network in the US sucks.
GermanGuy said:
droidforums is about as dead for the Droid 4 as is XDA.
Click to expand...
Click to collapse
This is true, I was just mentioning since most of the recent information regarding the ICS leak has been on droidforums so checking it out would fill everyone in on whats going on. Because basically development for the GB kernel is probably going to come to a halt and future development will be based on the new ICS kernel, including the existing AOSP ROMs.
wait, the 206 version keeps you on the upgrade path?
dewhashish said:
wait, the 206 version keeps you on the upgrade path?
Click to expand...
Click to collapse
No, but 206 was supposed to require 219 as 200 did and the official one will and people have found ways around it.
Sent from my XT894 using xda premium
I have Hashcode's stuff running on my kindle fire. We will all be in for a treat once he starts focusing on D4. He's done really really good work on the kindle.
dewhashish said:
I know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel
EDIT: i meant leaks, stupid typo
Click to expand...
Click to collapse
They won't be able to do so. What they will be able to do is make their builds work off/with the new kernel/radios flashed by the leak.
So Hashcode will have two builds.
1) - works on phones running the current stock GB kernel.
2) - works on phones running the leaked ICS kernel.
There is still a locked bootloader so you can't flash unsigned kernels/boot.img. For the leaked "system" files to help you need the ICS kernel. The only way to get the ICS kernel is to flash the leak.
So the leaks are great news for people wanting an AOKP or CM9 build running fully functional....on their leak installed phones. Not much help for those who do not want to flash the leak.
I'll definitely flash the leak once root has been released for 4.0.4 (in case OTA rootkeeper doesn't work) and hashcode releases safestrap 2.0 for the leak.
I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.
So far it's working great, face unlock and the camera is working perfectly and GSM/WDCMA performance is awesome, I don't seem to have the problem of under-reported GSM signal like in the stock MotoBlur leak.
(Note that I'm in Canada and using Bell Mobility, not in the US on Verizon so I can't say if LTE is functioning properly).
I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
Won't be long before Hashcode puts up an official release, but I definitely recommend trying it out if you're up for it. If Hashcode doesn't mind, I could share a .zip of the build I made if anyone out there is interested.
Sent from my XT894 using xda premium
Rick#2 said:
I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.
Click to expand...
Click to collapse
Do you think you create a guide or go into more detail how you did this? I'm not quite sure what their git is.
Sent from my XT894 using xda premium
Rick#2 said:
...
I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
...
Click to expand...
Click to collapse
This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.
Sent from my Amazon Kindle Fire using Tapatalk 2
Hashcode said:
This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire
Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?
podspi said:
If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire
Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?
Click to expand...
Click to collapse
Right now, I'm treating the front buttons like they are a special portion of the touch screen (basically any touch past 960 pixels down is considered the "button row", and then I divided the width up into 4 spots for button presses: menu, home, back and search respectively. (This is in the recovery itself as well as the splashscreen which triggers off of menu)
If that fails, Ill just use hard keys for D4's Safestrap temporarily.
Sent from my DROID4 using Tapatalk 2
..or maybe the volume buttons (I bet it requires less modification than implementing support for the digitizer)
I just put up an updated Droid4 2.00 Safestrap for use w/ the new MotoICS leaks:
http://forum.xda-developers.com/showthread.php?t=1688610
BE SURE TO MAKE AN INITIAL BACKUP OF NON-SAFE SYSTEM BEFORE YOU DO ANYTHING.
You will use the "System" backup to restore back to stock .206 to update later.
I have the D4 CM9 / AOKP builds for the MotoICS leaks almost ready and I'll post those soon.
Hi,
I am still running 2.3.6 because of I am enjoying webtop 2.0, however, I though upgrade to ICS is a must very soon, and I am looking for a "real" webtop.
webtop2sd cannot run on Droid 4, ubuntu using VNC... is there any options for Droid 4? I want a native ubuntu or other linux like webtop on my Droid 4.
I have google already but found it seem impossible? If anyone have any hints, please let me know.
Million thanks!
Kent
I run Ubuntu on mine from an IMG. It works just ducky for me. Does everything I want and then some.
zeroktal said:
I run Ubuntu on mine from an IMG. It works just ducky for me. Does everything I want and then some.
Click to expand...
Click to collapse
how about install in Droid4? I have lapdock moded for my Droid4, but ubuntu is more "flexible" although the performance may be ....
dinokent444 said:
Hi,
I am still running 2.3.6 because of I am enjoying webtop 2.0, however, I though upgrade to ICS is a must very soon, and I am looking for a "real" webtop.
webtop2sd cannot run on Droid 4, ubuntu using VNC... is there any options for Droid 4? I want a native ubuntu or other linux like webtop on my Droid 4.
I have google already but found it seem impossible? If anyone have any hints, please let me know.
Million thanks!
Kent
Click to expand...
Click to collapse
What's wrong with the tablet mode in ICS - seems to work fine for me. Some apps even display differently when in that mode.
Cheers,
Steve.