• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] Testers wanted

acidburnd said:
:eek:
Click to expand...

lol what was that about

edit: I let it run a bit more after backing up and clearing SD card now my system.img is 194,304 kb.

I'll let it run for about 30 mins and report back if anything larger (I'm using hroark's latest recovery btw)
 
Snake X said:
lol what was that about

edit: I let it run a bit more after backing up and clearing SD card now my system.img is 194,304 kb.

I'll let it run for about 30 mins and report back if anything larger (I'm using hroark's latest recovery btw)
Click to expand...

I get last night

Boot.img
Recovery.img
System.ext4.tar

And hanging on data
 
acidburnd said:
I get last night

Boot.img
Recovery.img
System.ext4.tar

And hanging on data
Click to expand...

same for me (I dont think i remember system.ext4.tar though) but im going to leave it "hanging" for 30 minutes because it might actually be doing something (system.img file increased size after I let it run longer the second time)
 
Snake X said:
same for me (I dont think i remember system.ext4.tar though) but im going to leave it "hanging" for 30 minutes because it might actually be doing something (system.img file increased size after I let it run longer the second time)
Click to expand...

It shouldn't take more than 7 or 8 minutes max to do a backup, at least that's my experience with cwm backup generally.

I had mixed results with backup from the 5.0 builds of cwm hr did, haven't tried the latest but sounds like about the same, I am assuming since he went back to 4.0 that you aren't seeing any progress indicator change or files showing progress as it's trying to make the img files?
 
acidburnd said:
I get last night

Boot.img
Recovery.img
System.ext4.tar

And hanging on data
Click to expand...

Snake X said:
same for me (I dont think i remember system.ext4.tar though) but im going to leave it "hanging" for 30 minutes because it might actually be doing something (system.img file increased size after I let it run longer the second time)
Click to expand...
Guys stop please. Its not that its freezing up on backup at the data portion. It has nothing to do with the backup process its just after several minutes. During backup that just happens to be the timing of it. To prove my point boot into recovery and just browse arounfd and do nothing for about 2 to 5 minutes and eventually it will freeze up. We arent doing this test to achieve a backup (that isnt our objective) but to test the functionality of the CWM.

On a phone with no apps at all installed i actually achieved a full backup within the time before it froze way back on I think it was Sebastian404's b09. So lets stop with this nonsense. There is nothing to do but wait for the next build.
 
MrBobo said:
It shouldn't take more than 7 or 8 minutes max to do a backup, at least that's my experience with cwm backup generally.

I had mixed results with backup from the 5.0 builds of cwm hr did, haven't tried the latest but sounds like about the same, I am assuming since he went back to 4.0 that you aren't seeing any progress indicator change or files showing progress as it's trying to make the img files?
Click to expand...
Correct that build is obviously based on Sebatian404's (the toolchain he was using) and none of his ever showed progress or what the backup was doing. It does however do the work. You just cant see it. All builds to this point freeze after several minutes having nothing to do with any particular process (meaning you dont have to actually do anything at all).
 
Woodstock77 said:
Correct that build is obviously based on Sebatian404's (the toolchain he was using) and none of his ever showed progress or what the backup was doing. It does however do the work. You just cant see it. All builds to this point freeze after several minutes having nothing to do with any particular process (meaning you dont have to actually do anything at all).
Click to expand...
Yeah, I think all of us are just playing as we wait for builds, testing whatever we can to see if there is anything useful we can contribute as far as findings back to the devs... It might make sense to open a new thread and structure it better like some of the rom threads where the latest builds/dev notes/change logs/known issues are on the first posts rather than our current structure where everything is buried in the flow of the thread... that way the discussion wouldn't clutter up the thread so much... Or maybe we could restructure the first post of this thread, I don't know if we can do that or if it has to be a moderator since sebastian is MIA now.

EDIT::

add having a list of things the DEVS want us to test on that first page too :)
 
Snake X said:
well.. backing up feature is important too, right? :D
Click to expand...
Of course and thats why we have been testing that first. I just want you guys to understand what we are doing here. Its not about getting a good backup but making sure CWM works. If doing a backup is the easiest way to test whether or not it still freezes up then thats what we are doiing right now.
 
Ok, I understand now. Final word on the backup though, after almost 1 hr it (system.img) came out to be.. well the same size (194,304kb). oh, and I only got data.img and system.img but still did not show progress after backing up data. Ok, done with that now. Can't wait for next build :D
 
well i got my own warp now, gonna do some private builds and test on my own sexy device.. and when its done, I'll release it to you my loyal testers.. no worries and thanks for the feedback, helped tons... Really appreciate all u guys did for me hroark and sebastian... When im finished with cwm, i'll release a beta build that u guys can test for me...:D
 
QuietStorm1785 said:
well i got my own warp now, gonna do some private builds and test on my own sexy device.. and when its done, I'll release it to you my loyal testers.. no worries and thanks for the feedback, helped tons... Really appreciate all u guys did for me hroark and sebastian... When im finished with cwm, i'll release a beta build that u guys can test for me...:D
Click to expand...

sweet, can you post it in a new thread when you do, this one is pretty tough to follow :)

great to hear, this is such a bottleneck for roms :)
 
QuietStorm1785 said:
well i got my own warp now, gonna do some private builds and test on my own sexy device.. and when its done, I'll release it to you my loyal testers.. no worries and thanks for the feedback, helped tons... Really appreciate all u guys did for me hroark and sebastian... When im finished with cwm, i'll release a beta build that u guys can test for me...:D
Click to expand...

I do like following the progress. I was hopeing to get adb bootloader working tonight so I could participate. I got an Ubuntu install up and running just for this.
 
dont worry, i'll keep ppl updated. Building another version now, built amon ra recovery, tested it, and it had same graphical issues with our phone.... so im gonna try using code from the htc phones to see if it works. Amon ra recovery didnt have the freezing issue, but it did have an issue with selecting items in the menu, also... it had a big time graphical glitch, instead of one screen, there were 4... x_x It does have alot more options for the phone tho, but without being able to select anything i couldnt tell if it worked...-_-

[MAJOR EDIT]

managed to get new build of cwm to make backups, fixed screen rotation issues, seems that the zte warp comes with physically inverted screen, so i hadta invert the buffer 180 degrees to compensate for this, thus fixing the upside down screen, also added opengl driver config to the build.. i think it stopped the freezing issues, but further testing is needed in order to make sure...


[EDIT2]

Fixed mount USB, still havent fixed freezing issues, trying to fix that now... but it's being difficult...-_-
 
You must log in or register to reply here.
Back
Top Bottom