Speed Fix? - Captivate Android Development

Any chance of bringing this speed fix by mimocan to the Captivate?
Supposedly some international version Galaxy S'ers are sitting pretty with 1700's Quadrant scores because of this fix among other firmware flashes, etc.
Can we replicate this for the Captivate?
Here's a little inspiration:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

"I have made a custom kernel to mount an ext3 partition on the sdcard at the boot time."
Can't make a custom kernel without source... and there is no source out yet... or even a stock firmware.

designgears said:
"I have made a custom kernel to mount an ext3 partition on the sdcard at the boot time."
Can't make a custom kernel without source... and there is no source out yet... or even a stock firmware.
Click to expand...
Click to collapse
Isn't the stock firmware in this? http://forum.xda-developers.com/showthread.php?t=731989
I've compiled kernels for linux before on my own PCs, and from what I can tell, he's just added ext3/ext4 support and customized the init.rc to mount the partition at boot time. I should dig around and see what I can find.

MANG~
I will worship the ground you walk if you can get this to work on Captivate.
I bricked my phone many times trying to make this work. Apparently when mimocan's kernel installed, external sd card can not be detectect and g sense will be off 90 degrees. however, all buttons do what they are suppose to do.
Anyways, please please help with this MOD. Alot of us Captivate owners are looking for this fix.

You will be my new hero if you get this working on the captivate.

sl8125 said:
MANG~
I will worship the ground you walk if you can get this to work on Captivate.
I bricked my phone many times trying to make this work. Apparently when mimocan's kernel installed, external sd card can not be detectect and g sense will be off 90 degrees. however, all buttons do what they are suppose to do.
Anyways, please please help with this MOD. Alot of us Captivate owners are looking for this fix.
Click to expand...
Click to collapse
You ain't kidding either! That fix is the [email protected]! I've finally gotten my Captivate to run decently with LauncherPro but it's that nothing compared to what it could do with this fix. It's a shame really, we have KILLER hardware and the software implementation has seriously crippled it.

designgears already posted the stock firmware... no? Twenty bucks to anyone who can get my captivate up to these benchmark scores.
Koush posted up the stock kernel too.
Sent from my Samsung Captivate using XDA app

I'd donate $20 as well.

im in for 20$ for a fix, even using SetCPU to 1000mhz whenever the screen is on I still get little stutters that feel like memory read issues, buddy was just over with his froyo nexus 1 and it was amazingly fast.
20$ is cheaper than the 35$ return see

I am in. I love to see happen. $$s for your time and bro.

Holy CHIT!
Ck this vid out. Its running the Mimocan Fix.
I need a FIX now. Come on man gotta do this.
http://www.youtube.com/watch?v=_b363eq0dXY&feature=related
http://www.youtube.com/watch?v=AjJdT-tlHOY

Well..... I just drooled all over my keyboard..... Anyone out there want to take a stab??? PLEASE!!!!

Hopefully that won't take much get running for us
Sent from my SAMSUNG-SGH-I897 using XDA App

I'm not a baller like some of you, but I would give 10 dollars to whoever makes this work with the captivate and maybe makes a vid on how to do it.

Don't worry it will come around.
Sent from my Nexus One using XDA App

it appears ext2/3 are already supported...
On my stock Captivate kernel /proc/filesystems shows ext2 and ext3 are already supported. Only boot scripts should need to be changed to use them. Also interesting, cramfs and romfs are supported but unused.

I tried this fix with ext3 and ext4, it didn't work just a black screen. Check this reply i posted to see my steps
vietphunguyen said:
Yep Ext4 nor Ext3 works on Captivate, it just goes to Black screen, Here are my steps below:
1.) Rooted Captivate
2.) Installed Busybox
3.) Made GParted ISO, booted computer up with GParted, Made the FAT32 2.5GB and EXT3/4 1.5GB (no labels and I have a 4GB SD)
4.) Put phone into Download mode (cmd: adb reboot recovery)
6.) Selected the v3/v4 for PDA, successfully worked, phone rebooted up fine
5.) adb shell, su, ran "mount -o remount,rw rootfs /" to mount the ext3/4 file system as writeable
6.) Ran the busybox commands (listed on main post of this thread)
7.) rebooted and it went to the Samsung Galaxy i9000 screen, then the 3g/att animation, then the galaxy S loading screen, then it turned black, when i tried ext3 and ext4,
8.) Cries, hoping someone finds a fix for captivate
Click to expand...
Click to collapse

in that case, anyone care to try the i9000 bootscripts with our kernel?

Kagoshema said:
in that case, anyone care to try the i9000 bootscripts with our kernel?
Click to expand...
Click to collapse
how is this done? new to this. i'll give it a try.

Good luck with that. I hope it works for you. We really need this fix until Samsung can fix the "bottle neck" but that probably wont happen until froyo is ready.

Related

CMod 4.1.999 has slowed my phone to a halt

I was running a G1 with Cyanogen Mod 4.04, Cyanogen Recovery 1.2. I updated to Recovery 1.4, installed the 1.6 .img, installed Cyanogen Mod 4.1.999, ran the fix permissions command in console, and rebooted. It is SOOO slow. Takes between 15 seconds and 1 minute for any button press or screen touch to be recognized. It is completely unusable. I have found a few posts about this, but nothing offered a concrete solution.
I have since done a wipe in console, and reflashed Cyan 4.1.999. It didn't fix anything.
My SD card is properly formatted for apps2sd, as it worked fine in Cyan 4.04.
Any ideas?
try a task manager and see what is running in the background
try ending programs that may be chewing up memory
set up a swap
What do you mean by set up a swap? My SD card already has a main partition, an ext3 partition and a linux swap partition.
you made no mention of your sd partitions
something is most likely hanging up your memory which is why i said check with a task manager
you can always try flashing the adp again and then cyan
when i first went to cy's i had to do that
I'll try the task manager. Based on how slow it is, it may take me a few hours to get it installed.
i got a quick idea, try shutting off your phone, pull out your sd and try rebooting without it and see what happens without apps2sd going
update to ext3 if you are not already
delete your dalvik-cache if you are upgrading from a previous rom and didn't wipe
huh, did you not read his posts, he has ext3 and he has wiped
Don't know if it would make any difference, but maybe try to install HTC and 4.1.99 and then just flash .999 over the top of that.
hey knowfear, you are not too far from preme, right? do you guys know each other
gridlock32404 said:
hey knowfear, you are not too far from preme, right? do you guys know each other
Click to expand...
Click to collapse
Not personally but I have talked to him in PMs. He lives not too far away from me.
sweet, you might see me driving through your day in about 2, 3 weeks after preme gets me drunker than all hell
so just aplogizing before hand
The fact of the matter is that it simply is DEAD SLOW.
His development process is taken from the MS-developers-handbook.... just keep on shovelling on the bloat, and every once in a while release a new version and CLAIM that it is faster than the last, even when it is slower.
Then you get all the little kiddies, who update with every new version, each of which makes no appreciable difference, BUT because the release notes SAY it is faster, and the fact that they can't really tell, the placebo effect tells them that it IS faster. They keep doing this... several times, so the cumulative placebo effect tells them that it *must be WAY faster*, except that with every new version it actually becomes slightly SLOWER, so after MANY MANY "upgrades", what you turn out to have is something FAR FAR slower than the original.
Just to get a feeling for the differences, try out a stock cupcake build, then try FOUR CM cupcake builds that are evenly spaced out (in order), then again try the stock cupcake build. Then try the stock donut build.
If you want a fast donut that supports apps2sd, etc., and doesn't have the insane bloat, take a look at this one: http://forum.xda-developers.com/showthread.php?t=538456
This ROM is a simple rooted ADP1 donut base, with an "expansion pack" -- from which you can pick and choose the extra features you need/want so as to end up with a system that is optimized to YOUR needs, rather than just packing in everything including the kitchen sink and claiming it is the best thing ever.
zinite said:
I was running a G1 with Cyanogen Mod 4.04, Cyanogen Recovery 1.2. I updated to Recovery 1.4, installed the 1.6 .img, installed Cyanogen Mod 4.1.999, ran the fix permissions command in console, and rebooted. It is SOOO slow. Takes between 15 seconds and 1 minute for any button press or screen touch to be recognized. It is completely unusable. I have found a few posts about this, but nothing offered a concrete solution.
I have since done a wipe in console, and reflashed Cyan 4.1.999. It didn't fix anything.
My SD card is properly formatted for apps2sd, as it worked fine in Cyan 4.04.
Any ideas?
Click to expand...
Click to collapse
I had the same horrible lag when I went from 10.1 to .999, so I repartitioned my sd and tried again fresh and it worked perfectly...purrs like a kitten now...
kittens purring is a good thing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

			
				
Fixed it.
I wiped, deleted dalvik cache in console (I can't find the command I used though), reinstalled, fixed permissions in console.
Thanks guys

[Q] ryanza's one click lag fix, i need it

does anybody have ryanza's one click lag fix. i need a copy of it, and its not in the market.
Search the development section there are many posts related to it. There also is an app on the market just search for one click lag fix.
Is root needed?
Sent from my SGH-T959 using XDA App
the one downloaded from the market has rooting capabilities built in. check it out. i rooted mine beforehand so can't verify how well the market OCLF works.
One click lag fix from market is a must have app . It'll root, unroot, lag fix and unlag fix. Just the ****.
Really could not find this app by searching? Really?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
agree.!!!
Sent from my SGH-T959 using XDA App
if i used the ADB version of ryan's lagfix and install this app, will it still work to unlagfix, etc?
dont want to **** anything up ... thoughts?
just installed it and checked, looks like unless the app has done the fix, it cant undo it.
all i can do is:
install ext2 tools
check data/data free space
unroot device 2.1
change scheduler
turbosix said:
if i used the ADB version of ryan's lagfix and install this app, will it still work to unlagfix, etc?
dont want to **** anything up ... thoughts?
just installed it and checked, looks like unless the app has done the fix, it cant undo it.
all i can do is:
install ext2 tools
check data/data free space
unroot device 2.1
change scheduler
Click to expand...
Click to collapse
same with mine when i tried to install it.. you need to have 40% of battery or more in order to install the lag fix, at least that's what happened to mine..
charge it up then install it..
Did your first boot take like five minutes? Really thought I bricked my phone, but it finally booted.the reason I ask here is because another guy in the main thread had that same issue but was ignored. Boot takes at least 60 seconds of black screen before the boot animation loads..
Sent from my SGH-T959 using XDA App
I just DLed "one click lag fix" on Tuesday. Worked great for me. Does everything for you. However if it fails do a reboot between steps.
Sent from my SGH-T959 using XDA App
turbosix said:
if i used the ADB version of ryan's lagfix and install this app, will it still work to unlagfix, etc?
dont want to **** anything up ... thoughts?
just installed it and checked, looks like unless the app has done the fix, it cant undo it.
all i can do is:
install ext2 tools
check data/data free space
unroot device 2.1
change scheduler
Click to expand...
Click to collapse
Your next step is to install ext2 tools. then, the option to apply the lag fix will be enabled. two more steps and you're done.
When you install the OCLF app, you have to create a partition. When you undo the lag fix, does it undo the partition you made? Or, would you have to undo everything AND uninstall the whole app?
I think the partition created when installing this is causing a problem with titanium backup (it's backing up to my internal SD instead of the external SD card). I want to work backwards for a second and see if that indeed is the problem, but I don't know how to modify or even verify existing partitions.
Yeah I thought I was going to faint waiting fit my phone to boot up..
Sent from my SGH-T959 using XDA App
That scared the hell out of me too. First reboot took freakin forever. I was sweating bullets

Gingerbread BETA available for HD

Just posted on twitter by Kali:
2.3.1 AOSP for HD http://bit.ly/hETZtd completly unsupported, not working: usb mass storage, camera and camcorder, do not report bug
Anyone taken the plunge and flashed this? Does everything else work bar the aforementioned?
sent from my DHD
Done a full backup, wipe and then flashed. Boots OK.
I have installed the google apps add on package, but no market or google account sync. etc. Will try to get working, having a look at the G2 forums...
Rooted gapps for gingerbread available here: http://forum.xda-developers.com/showthread.php?t=872441
Downloading now. Just need to work out how to get onto my SD card now!
EDIT: That is a full rom, not just the gapps I think. Do not flash!
Had a quick flash of the 2.3 rom. It goes on fine and it whizzes around lovely. Could dial numbers and rings, but no data though, from wifi or mobile.
Was worth it just to play with the sleep animation.
sent from my DHD
just flashed it, boots fine but no mobile data or wifi for me
jambamkin said:
Had a quick flash of the 2.3 rom. It goes on fine and it whizzes around lovely. Could dial numbers and rings n buy No data though from wifi or mobile.
Was worth it just to play with the sleep animation.
sent from my DHD
Click to expand...
Click to collapse
So you can confirm if you flash this you can revert back to previous rom ie 2.2.1 ? What where you on before that?
Sent from my Desire HD using XDA App
Tested and confirmed both wi-fi and mobile data working for me.
Did you do a full wipe first?
And, which radio are you running? I'm running the latest from the ROM leaked earlier this week.
Im running cyanogen rc2. Just did a full backup with rom manager and wiped data and cache, then flashed.
Had a play on 2.3 then rebooted into recovery to restore my backup. Phone is just the same as it was 30 mins ago.
sent from my DHD
I'm still in the older radio so that could well be the cause. I'll look into upgrading that later.
sent from my DHD
[ROM-AOSP GRH55] Oxygen v2.0-RC1 (Cleanest, fastest ROM on the block *GINGERBREAD*)
http://forum.xda-developers.com/showthread.php?t=829734&page=1
these guys already have a RC1 ? comon guys...
Anyone found google apps add on that works with Gingerbread?
I installed it on my UK based DHD and it installed fine (for a non-working ROM). As already mentioned the data connection wasn't working but it's silky smooth. The keyboard needs the resolution sorted out as it's quite small. I didn't install gapps but most wouldn't work anyway. Did a recovery and restore and now back on Stock Sense.
Sent from my Desire HD using XDA App
Ok can confirm that i have Data working , at least wifi about to test 3G.
I am using the new radio from the RUU this week
Gapps doesnt work spoke to some people on the desire IRC channel and they said to remove some NetworkLocations.apk file but its not even inside the ROM so ?
Think we need to remove that apk from the google apps zip file. Will it need re-signing or can clockwork recovery flash non signed zips?
saquib said:
Think we need to remove that apk from the google apps zip file. Will it need re-signing or can clockwork recovery flash non signed zips?
Click to expand...
Click to collapse
LOL its 2:20Am here, cant even believe i asked that or didnt check that before
anyways think i got gapps going , and if you update your su binary thru super user by mistake you need to use this for r/w instead of adb remount.
Code:
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p25 /system
This is actually pretty usuable... lol ..besides 3G DATA not workin . but wifi does.. calls work.. and yeh..
anyone report any mojor bugs ?
*** edit
and that is because there is no APN list
Sent from my HTC Desire HD running 2.3.1 using XDA App
How did you get it to work?
mero01 said:
LOL its 2:20Am here, cant even believe i asked that or didnt check that before
anyways think i got gapps going , and if you update your su binary thru super user by mistake you need to use this for r/w instead of adb remount.
Code:
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p25 /system
Click to expand...
Click to collapse
Well I tried to download this but the file is now longer available. some one knows of a mirror?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

How to find /boot mount point?

Ok, so I know for the Nexus S the mount point for /boot is:
/dev/block/mtdblock2
But that's only from looking at BM's rom wiper tool. I tried running "mount" under terminal emulator, but it doesn't list the /boot mount point.
I'm hoping to find the mount point on a kindle fire is why I ask. The cyanogen fastboot wiki mentions that it's mtdblock2, but I don't know if this is the case for all android devices.
Any help is appreciated, thanks!
EDIT - spoke to one dev and he said that /boot and /system should never be wiped. Now I'm confused, maybe it's differences due to it being a different device?
Have you tried to ask the question in kindle fire forum?
Sent from my Nexus S 4G using xda premium
shabgard said:
Have you tried to ask the question in kindle fire forum?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
This question isn't really device specific. The reason I haven't asked it there just yet is because there are more devs floating around in the NS forums.
That and the community there is different. Every other thread is a "bricked" thread, where it seems that a lot of users have no idea what fastboot or adb is. =p
"df" doesn't list it for me, so i doubt it is. However, if you do a fresh boot and type in "dmesg" it'll tell you where it's located right up the top (at least on the Nexus S).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Damn it looks different on the KF:
I'm not sure if that's what I need. I don't know if boot partition 2 = /dev/block/mtdblock2.
Ahh, I'm a super newb at this too.
Thanks for the help though.
Never done (or needed to do) any work with locations like this, especially with android. Sorry i can't help further, but maybe someone else around here can shed some more light for you.
Harbb said:
"df" doesn't list it for me, so i doubt it is. However, if you do a fresh boot and type in "dmesg" it'll tell you where it's located right up the top (at least on the Nexus S).
Click to expand...
Click to collapse
/factory doesn't show with df either, although it shows on GN I think...
Sent from my ice cream powered Nexus S
mount won't show the boot partition, because it's not mounted to the file system afaik.
Try
Code:
cat /proc/mtd
On the NS, it is mtd2, aka /dev/mtd/mtd2.
Boot is where the kernel and ramdisk are stored. If you erase boot, your phone will not boot (go figure).
Then I'm confused, what does the format/ boot function in CWM actually wipe?
erikikaz said:
Then I'm confused, what does the format/ boot function in CWM actually wipe?
Click to expand...
Click to collapse
The kernel
Sent from my ice cream powered Nexus S
DarkhShadow said:
The kernel
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
OH! Shoot, so is there any way to manually wipe that?
the kernel is in the boot.img

ubuntu touch - WIP Download available - updated 03/23

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
VERY work in progress. Wifi works flakily use an open network to play with the keyboard tends to freak out when typing in a network password.
This is a PREVIEW of what this platform will become. It is not finished. Many apps are just placeholders. The good news the system image is built and you can just plug in new ubuntu images as they become available.
to install latest daily (as of 03/23/13)
Reboot into Recovery
Backup! - expect everything to be deleted if you do not.
WIPE (wipe data/factory reset) This is required!
Flash system image
Flash Ubuntu image
Flash Layout fix
Reboot
To reverse the process use adb reboot recovery - or hold power off button till it shuts down then restart in recovery - yes it's obnoxious but the reboot and power off commands are absent from ubuntu still. Once back in recovery wipe and flash a replacement android rom and you'll be back to normal.
YOU ARE RESPONSIBLE FOR YOUR OWN ACTIONS DO NOT FLASH THIS IF YOU CAN'T RTFM.
kernel source: https://github.com/RobotApocalypse/kernel_acer_a500
I be following your progress then good work !
I figured you would do this but I still can't find a good reason to run it. Nothing works (which is the nature of this not your fault). lol
blazingwolf said:
I figured you would do this but I still can't find a good reason to run it. Nothing works (which is the nature of this not your fault). lol
Click to expand...
Click to collapse
yeah I have issues ... it will get better as they improve userland. They're moving to a raring base soon and hopefully some of the blanks will be filled in
*fixed layout
randomblame said:
yeah I have issues ... it will get better as they improve userland. They're moving to a raring base soon and hopefully some of the blanks will be filled in
*fixed layout
Click to expand...
Click to collapse
After this gets to a more stable state for the A500 would someone be able to port it to the A200?
wifi is up
Raw speed
Hey Randomblame,
You keep me amazed by the speed at which you are able to get these new iterations running on our 2 year old machine. If anything it has re-validated to my what a good purchase the A500 was. Its developers like you that have made me a huge open source convert and I look forward for t he day when OS's will be device agnostic.
Thanks again for the effort behind this port and hope to see the platform emerge.
OP updated with download links and instructions.
Can I Dual Boot?
I would love to use it and still have my Android
BTW,
Grat work!
TY!
Godmik said:
Can I Dual Boot?
I would love to use it and still have my Android
BTW,
Grat work!
TY!
Click to expand...
Click to collapse
I wouldn't recommend it this uses a massive chunk of the /data partition and its not really something to be used as much as it is something to be toyed with
randomblame said:
I wouldn't recommend it this uses a massive chunk of the /data partition and its not really something to be used as much as it is something to be toyed with
Click to expand...
Click to collapse
can we repartition fs to use separate /data for android and Ubuntu?
He does it again, that ol' randomblame! So, any cautions on backing up and restoring, or is it just like an other Android ROM? I assume there's always APX mode to fall back on in case of catastrophe.
Good job! randomblame:good:
Unfortunately, my tablet is damaged.
pjsports said:
Good job! randomblame:good:
Unfortunately, my tablet is damaged.
Click to expand...
Click to collapse
So's mine bud kids are heartless lol I need to install a touch recovery my volume buttons are done for. Its a pretty easy process I can walk you through the build if you want.
randomblame, I'm developing for another Tegra 2 device, and I"m stuck at a black screen. How long did yours take to boot? Was there any other changes you made?
I'm stuck on the black screen too
Luckily Ubuntu touch still supports adb and logcat for debugging - a black screen isn't exactly something I can trouble shoot read your logs I'm sure the issue will become apparent.
well...
Is it fast and smooth enough to have some FUN with it?
Anyway, Good Job on porting ubuntu touch on our a500! I was really eager to hear about your excellent jelly bean port, so I downloaded it and
flashed it immediately.
randomblame said:
Luckily Ubuntu touch still supports adb and logcat for debugging - a black screen isn't exactly something I can trouble shoot read your logs I'm sure the issue will become apparent.
Click to expand...
Click to collapse
No connection It doesn't recognize it. Would love to read my logs, lol.
I'm already restoring my backup...
sry
but, I'll follow your progress
and again
Thank you!

Categories

Resources