This is gonna be the thread where I post the CWM I've been working on
First things first, here comes a newb question
Its my first time working with CWM, do i need the entire android source to compile it ? or just the source from koushs github. Also here is my nifty solution for navigation
The linux kernel has a few different types of events, the main two that CWM uses are
EV_KEY which is key event
and
EV_REL which is the trackball usually
the trackball even reads the movement and past a certain threshold fakes an up or down key event.
what I'm doing is adding in EV_ABS (touch event) to the input thread so that when it reads a screen touch it will fake a down key event similar to how the EV_REL works.
Now this is just the initial idea, in the future I want to make the touch event work like the trackball so to go up/down you swipe up/down, but this will do for now.
Controls will be as such
Tap = Move Down
Power = Select
Also once navigation is workin im going to be modifying it to set bootmode before exiting recovery so as to get rid of the current problem of not being able to exit recovery.
correct me if im wrong but here are the bootmodes i need
idme bootmode 0x4000 (normal boot)
idme bootmode 0x5001 (reboot recovery)
update 12/16 9pm
working on fixing some bugs with touch input and fixing rebooting from recovery
system is recognizing touch input properly and recovery boots properly, and when bootmode value is set to normal also boots the system correct.
Update 2
Got Reboot Working correctly from recovery and still workin out some touch nav bugs, will finish up tomorrow hopefully
UPDATE 12/17
Havent had time today t work on it like i planned, still issues with the touch input moving the cursor too far. Working on it now
UPDATE 12/18 1:30am
Touch Icons are drawn and in the correct position, working on mapping to correct functions
update 10:50pm
For some reason cannot get the touch coordinates to line up with the icons, even though the icons should be right over them.....not sure whats going on =/ gonna have to redo a few things to see what might be happening and why a key event isnt being injected
UPDATE 12/19
ReWriting the the input get for my touch controls to simplify it and make it easier to debug. Got work though till 4 so its gonna have to wait
awesome, I was sitting stuck in recovery on my mytouch today and using the trackball thinking of this as well. bravo my friend. seems very feesable
Sent from my HTC Glacier using xda premium
smirkis said:
awesome, I was sitting stuck in recovery on my mytouch today and using the trackball thinking of this as well. bravo my friend. seems very feesable
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Thats the idea, and though there are other touch recovery in development, I've been using CWM for a long time and like and trust its (at least for me) reliability
You have to have the full android source code. it goes in the bootable directory.
death2all110 said:
You have to have the full android source code. it goes in the bootable directory.
Click to expand...
Click to collapse
i figured...syncing now...will let you guys know the progress when there is some.
idme bootmode 4002 is fastboot
Sent from my SPH-D710 using xda premium
If you got questions ask koush he is always on twitter , but you can always go to CyanogenMOD irc on freenode
Sent from my SPH-D710 using xda premium
My understanding is that you need the whole source, but you can build just the recovery by typing: make recoveryimage.
There is a guide here:
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Hope you get farther then I did. I must have missed a step somewhere because I cant get it to build.
tecookie whats the issue you're having?
ok guys....touch recovery working...let me work out the kinks then we are good =]
It's weird. Seems like yesterday I was getting a different error.
# make recoveryimage
build/core/product_config.mk:196: *** device/amazon_kindl_fire/boot.img/device_boot.img.mk: PRODUCT_NAME must be a valid C identifier, not "full_boot.img". Stop.
Click to expand...
Click to collapse
I was following this guide and everything seemed to be going well up to the "build/tools/device/mkvendor.sh..." point. I got the "Done" output from that command but also a bunch of other stuff, some of which looked like they might have been errors.
I think I might just re-sync and try again.
---------- Post added at 06:22 PM ---------- Previous post was at 06:17 PM ----------
ECOTOX said:
ok guys....touch recovery working...let me work out the kinks then we are good =]
Click to expand...
Click to collapse
Wo! Awesome! Looking forward to it.
ECOTOX said:
ok guys....touch recovery working...let me work out the kinks then we are good =]
Click to expand...
Click to collapse
WHAT?! This is great news! I'm very excited to hear this! I don't even have a kindle fire yet, but plan on getting one for christmas and I was worried I might not be able to hack it as well as other devices without a usable recovery. But this is great news! Glad to see many talented devs working on the fire, just makes that 200$ a great investment
TWRP
dubt17 said:
WHAT?! This is great news! I'm very excited to hear this! I don't even have a kindle fire yet, but plan on getting one for christmas and I was worried I might not be able to hack it as well as other devices without a usable recovery. But this is great news! Glad to see many talented devs working on the fire, just makes that 200$ a great investment
Click to expand...
Click to collapse
you should check the TWRP it is a more basic recovery that works just like clockworkrecovery and its all touch its been in development but now i balive it is now fully working its just not up yet, you should check it out http://forum.xda-developers.com/showthread.php?t=1356425
Poler166 said:
you should check the TWRP it is a more basic recovery that works just like clockworkrecovery and its all touch its been in development but now i balive it is now fully working its just not up yet, you should check it out http://forum.xda-developers.com/showthread.php?t=1356425
Click to expand...
Click to collapse
I know, I'm not doing this just for a recovery, i want to see if i can do it =P Also I like CWM
ECOTOX said:
I know, I'm not doing this just for a recovery, i want to see if i can do it =P Also I like CWM
Click to expand...
Click to collapse
Any estimates when it'll be ready for release?
Sent from my Kindle Fire using xda premium
Earliest tomorrow
Sent from my Nexus S 4G using Tapatalk
ECOTOX said:
Earliest tomorrow
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
I can help you out if you want?
Poler166 said:
you should check the TWRP it is a more basic recovery that works just like clockworkrecovery and its all touch its been in development but now i balive it is now fully working its just not up yet, you should check it out http://forum.xda-developers.com/showthread.php?t=1356425
Click to expand...
Click to collapse
TWRP is a little better choice in recovery for tablets, but it never helps to have several options
death2all110 said:
I can help you out if you want?
Click to expand...
Click to collapse
Nah, thanks though, you've been alot of help already. I'm exhausted and need to sleep, so when I wake up i'm guessing around 4 more hours work and the initial release will be ready
Sent from my Nexus S 4G using Tapatalk
brett10 said:
TWRP is a little better choice in recovery for tablets, but it never helps to have several options
Click to expand...
Click to collapse
u mean never hurts? how can u claim twrp is a better choice when its not out. cwm is known by many and some just feel comfortable using it. stop trolling, development is development. even if they both got released the same day, people with choice will choose whatever recovery they wanna use. I personally like cwm, but would use whatever is available to our devices that's stable.
Congrats on the progress, can't wait to test it out.
Sent from my HTC Glacier using xda premium
Related
Hey Guys!
Well I seen a thread in the general section talking about the posssibility of Android 3.0 or Honeycomb for Hero. I decided to have a go at porting a Magic HC ROM and so here it is. It works okay, can be sluggish at times but it's really only a proof of concept but if there's enough interest I'll consider improving it to try and get everything working. This ROM is really a joint effort between me and Ybinnenweg, he's helped me develop every rom i've ever built so far so we may as well stick together .
Thanks to:
yohshua for the original rom.
Ybinnenweg for his advice and support
Elelinux for the update-script
Okay down to business..
Whats working?
- Led's
- Auto-Rotate ( it rotates after using camera but doesn't rotate back :L )
- Full Honeycomb UI
- Auto-Brightness
- SD Card mount?
- Key Lights
- Not sure what else.. find out!
Whats not working?
- Sound
- SMS
- Calls
- Camera
- USB Storage
- Bluetooth
- Wifi
Thanks to Ybinnenweg for screens
Downloads:
Superuser Fix
HeroGetsHoney v0.1
P.S: I know it says welcome to Elelinux-speedmachine, that's only because i used his updater-script. It'll be fixed in the next build
Changelog
v0.2:
Options
- Las Venturas 0.4.5 Kernel: http://www.multiupload.com/4LSROB7RQM
Wow! Any screens? How fast is it?
OMG! Great news!
I can't post screens atm, as I use my phone for work and can't use a ROM that has limited functionality for a while, I'll try get something up later. The speed is okay, it's not great but it's using fly-kernel12a, not tried using LV with it so i'm not sure if that will improve the speed. Test it out for me, any feedback is much appreciated
Nice to see you working on this but you've a lot of work to do good luck with it.
Hope this one is easier to port than MIUI
iPasta said:
Nice to see you working on this but you've a lot of work to do good luck with it.
Hope this one is easier to port than MIUI
Click to expand...
Click to collapse
Thanks, at least I have sources for this one
I tried flashing, it said verification failed because it's missing a file, data/app/Contacts.apk something like that
djdavis said:
I tried flashing, it said verification failed because it's missing a file, data/app/Contacts.apk something like that
Click to expand...
Click to collapse
what recovery are you using?
I'm using RA 1.6.2a
Lol, didn't thought it was possible to port because Google hadn't released the code I am willing to try as soon it gets a bit more usable
As the dev is AFK
Here are the screens that I've taken, they will be on the OP
the rest..
djdavis said:
I'm using RA 1.6.2a
Click to expand...
Click to collapse
okay, seems to be problems with amonRA, try using clockwork?
very cool! I cant believe our Hero's can do this, I guess they are living up to their names! also you guys are my heroes!
Habarug said:
Lol, didn't thought it was possible to port because Google hadn't released the code I am willing to try as soon it gets a bit more usable
Click to expand...
Click to collapse
I'm sure that Elelinux had Honeycomb running on the Hero shortly after it was released by Google ... ?
It booted was as good as it got though ⊙_⊙
Sent from my Hero using XDA Premium App
swatsbiz said:
I'm sure that Elelinux had Honeycomb running on the Hero shortly after it was released by Google ... ?
It booted was as good as it got though ⊙_⊙
Sent from my Hero using XDA Premium App
Click to expand...
Click to collapse
Thats true, don't think he ever posted on here though. I think it was more out of interest that he done it rather than a official ROM.
Just curious, will calling and sending text messages ever be fixed?
Look there is no market seeing the screenshot
riemervdzee said:
Just curious, will calling and sending text messages ever be fixed?
Click to expand...
Click to collapse
Probably, I'm having a look at that just now actually, the magic rom has sms working so we should be able to get that fixed aswell
I wanted to really start from scratch so I went through some of the Samsung open source code and found that there were some unnecessary modules being loaded. That could be what's causing some problems (although I haven't had much but think it's signal related or Sprint's towers being updated), but with no overclocking and the changes, it could solve everything? Dunno still.
So I tried my best to trip the bloat-code out and try to keep it as stock as possible (no overclock), perhaps some of you can test this out for me.
Changelog
v.1
- CWM 4.0.1.5
- Superuser 3.0 + fixed su, now installs in /system/bin, you can update the binaries with SuperUser app.
- init.d support (/system/etc/init.d)
- Bootanimation support
- fixed Airplane toggle
Things to test:
- LOS?
- Video out? - sorry my video out adapter is still being shipped, I think I enabled it but can't really check???
-Airplane toggle should be fixed
Things I am working on:
- Boot splash logo? Still working on that, if anyone knows how to change it, please let me know.
- Recompiling CWM from scratch, add external SD support, fix wipe issue
- Add infrastructure to wifi tether and USB tether?
Devs, u r free to steal my stuff, or stuff I stole I really don't remember from taking too much energy pills, taking a big white line from Stevie Jobs, "Good artists copy, great artists steal.".
If you have some knowledge to share, plz don't forget to email me at zedomax [at] gmail.com
If this works well, I will build off it or otherwise I will keep optimizing until its fully stable.
Thanks guys, you rock!
Download here:
v1:
ODIN tar:
http://downloadandroidrom.com/file/.../SPH-D710_Zedomax_EpicTouchKernelStock-v1.tar
CWM zip:
http://downloadandroidrom.com/file/.../SPH-D710_Zedomax_EpicTouchKernelStock-v1.zip
Yess!!! Thanks zedo. Will give it a whirl. Permission to use in StarBurst once stable?
Sent from my Epic Touch 4G
Odin'ed it over StarBurst 1.2, seems to work good but only been using it for 2min
Gonna test this out, thanks for all of your hard work, Zenomax!
Flashing now.
Boots up. Will be testing until I can get mine to work, but I think I had the same intent as yours does. Boots into CWM just fine too.
Cool! I'll be trying this when I get home. And I won't be bugging you anymore about the yellow triangle anymore... I have my usb jig coming in the mail.
Samsung Galaxy S II
Thanks and keep up the good work, it's well appreciate it
Sent from my SPH-D710 using xda premium
Flashed fine over 4.1beta. Seems to be working well, airplane mode working. Under 4.1 I seem to suffer routine LOS when on the road but not when at home, so it may take a while to fully test but so far so good.
Thanks for all the hard work.
PhantomHacker said:
Yess!!! Thanks zedo. Will give it a whirl. Permission to use in StarBurst once stable?
Sent from my Epic Touch 4G
Click to expand...
Click to collapse
Yes of course, any time, I thought everything was open source? LOL
zedomax said:
Yes of course, any time, I thought everything was open source? LOL
Click to expand...
Click to collapse
I like to ask anyway. ...Signal strength seems better may be placebo though.
PhantomHacker said:
I like to ask anyway. ...Signal strength seems better may be placebo though.
Click to expand...
Click to collapse
my understanding was that signal strength and quality was taken care by the radios/modems, not the kernel...
frifox said:
my understanding was that signal strength and quality was taken care by the radios/modems, not the kernel...
Click to expand...
Click to collapse
Was talking about wifi.
Sent from my Epic Touch 4G
Root is still messed up for me with your kernel Zedomax, so please make one that doesn't have root or even busybox(unless it's needed for the recovery) as root & busybox can be added through CWM if the user wants
great work zedo! i'll test it out once i get back to work. somehow i left ALL my micro usb cables at work like an idiot.
I had the LOS today, had to restart my phone three times in the span of three hours. So, being frustrated, I booted in to CWM, wiped my davlik and flashed back to v1.1. Then I wiped davlik again, flashed back to v1.2 and rebooted. Haven't have a LOS issue since. So far so good...
Sent from my SPH-D710 using XDA App
My bad, I totally misread the title. I though I was posting in the other kernal thread by Zedo.
Sent from my SPH-D710 using XDA App
ccline84 said:
My bad, I totally misread the title. I though I was posting in the other kernal thread by Zedo.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Should just edit the first one
Sent from my SPH-D710 using xda premium
big thanx zedo.
Calkulin said:
Root is still messed up for me with your kernel Zedomax, so please make one that doesn't have root or even busybox(unless it's needed for the recovery) as root & busybox can be added through CWM if the user wants
Click to expand...
Click to collapse
I personally think CWM is causing some issues right now... no evidence behind it, just a suspicion.
silversx80 said:
I personally think CWM is causing some issues right now... no evidence behind it, just a suspicion.
Click to expand...
Click to collapse
CWM probably can't cause issues since it's in recovery, it doesn't fire up unless u r actually in recovery but CWM we all using right now have issues as they are based off SG2 CWM binaries. Someone has to compile a CWM for Epic4GT from scratch or at least hack it. I am gonna try that soon but compiling kernels is just taking too much time, I've been 24/7 compiling for like a whole week, get no other work done, i seriously need to go out to a rave and get f--ed up for couple days. Then my head will be clear, compiling will be fun.
I just got an OTA update on my a100. I was a bit wary about taking an update, since I could find no information on it on the web, but I figured someone has to take a risk. The device downloaded 2.001.01 and installed it and my system went from Kernal 2.6.36.3 to 2.6.36.3+ and from build number Acer_A100_1.012.05_COM_GEN2 to Acer_a100_2.001.01_COM_GEN2
Other than that, I've noticed no changes, but I did not loose root, which was my main concern.
If this should be in the development section, let me know.
If anyone knows what changes were made in this update, or where I can get more information about it, I'd like to hear about it.
Thanks
I'm pulling it down now, thanks for letting me know I keep root. I was worried about that as well.
Sent from my A100 using XDA Premium App
I hope I catch you in time, but I'm now not sure I kept root. Superuser app came up just fine, but now titanium backup is saying it can't get root. I'll have to investigate further, but it looks like I was wrong before and now I need to see if I can reroot. did iconiaroot ever get updated for a100?
please tell me if it fixed the headphone issue.
Please tell me what the headphone issue is. Then I'll see what I can do.
if you are using the headphones and acer sync starts sound comes from both the headphones and the speakers
I don't use acer sync, so I can't really test that. I'm a bit more concerned about getting root back at the moment, but I might be able to check for you tomorrow, if no one gets to it in the meantime. Good luck.
You guys located in the US? Mine keep saying system up-to-date
Sent from Wicced's rooted A100 16gb HoneyComb 3.2 using XDA PREMIUM
Well, crap, root is gone. I'll try to redo it tomorrow, too sleepy to type right. It also reset my sweet boot animation.
Sent from my A100 using XDA Premium App
wicced247 said:
You guys located in the US? Mine keep saying system up-to-date
Sent from Wicced's rooted A100 16gb HoneyComb 3.2 using XDA PREMIUM
Click to expand...
Click to collapse
Indeed I am in the US. Like the other guy, no Idea what it actually did besides kill root and change my boot animation.
Sent from my A100 using XDA Premium App
yes fl they control it by region in the states i believe. so as not to pull an apple fail
wicced247 said:
You guys located in the US? Mine keep saying system up-to-date
Sent from Wicced's rooted A100 16gb HoneyComb 3.2 using XDA PREMIUM
Click to expand...
Click to collapse
Yeah, California here.
reverendbill said:
Well, crap, root is gone. I'll try to redo it tomorrow, too sleepy to type right. It also reset my sweet boot animation.
Sent from my A100 using XDA Premium App
Click to expand...
Click to collapse
Sorry I jumped the gun on the root call, I really thought superuser would have displayed some kind of error if I'd lost root, but I forgot to check Titanium. I've tried iconiaroot 1.3 and it didn't work, so i'm going to try the adb method. If that doesn't work, I'll just have to wait till someone who knows more about this stuff than me can make some progress.
HA! I fixed it!
I used a terminal emulater to run the root commands, THEN I ran iconiaroot 1.3 (which I assume just installed superuser.apk, since it wasn't able to get su on its own) and I'm rooted once again. I need to update superuser, busybox, reinstall adblock, and get rid of the bloat again, but then I'll be back to normal.
Here's the commands for the emulator btw, I got them from the "how to root" thread. If they don't work for you, try doing it the ADB way. (the best way is to open this page on your tablet,and cut and paste the lines (without the outside quotation marks) into the terminal emulator.)
"/system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`' "
"/system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`' "
"/system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`' "
Edit: BTW I can't tell if it came with the update, or if it self-updated, but I now have a new version of android market which doesn't force you into landscape mode. That always annoyed me.
mine is showing no update either showing kernel 2.6.36.3
max69power said:
mine is showing no update either showing kernel 2.6.36.3
Click to expand...
Click to collapse
So I'm not the only one not getting the update... I wonder why
Sent from Wicced's rooted A100 16gb HoneyComb 3.2 using XDA PREMIUM
Sorry guys, if I'd thought about it before I updated, I would have saved the update file to share with you. It didn't occur to me that some people wouldn't get it right away.
I don't see the update.zip in my sdcard, is there anywhere else they might have left a copy or is it gone after a successful update?
Looks like the issue with sound playing through speakers despite headphones being plugged in was finally addressed, thank god.
skitzles said:
Looks like the issue with sound playing through speakers despite headphones being plugged in was finally addressed, thank god.
Click to expand...
Click to collapse
Woot! This is amazing. This was the only bug that was driving me nuts. Anytime that you plug in headphones before starting music/videos, it would play out of both. I am so happy this has been fixed.
I wonder why I haven't been prompted for the update yet.
I'd imagine it has something to do with them avoiding an "apple fail" as someone stated earlier. Probably rolling out the update to a select region to make sure their is no catastrophic behavior, or bogging down their servers. When I updated to IOS5 they didn't accomidate for the flood of people they received and I had a hard bricked device for just over 12 hours. SOFUN.
skitzles said:
Looks like the issue with sound playing through speakers despite headphones being plugged in was finally addressed, thank god.
Click to expand...
Click to collapse
Nice
Sent from Wicced's rooted A100 16gb HoneyComb 3.2 using XDA PREMIUM
Okey I talked to some members on this forum that asked me to help out getting a asop/cm9 version up and running for your phone. I don't have this phone but I'm giving it a try anyway.
Please don't use this rom for MOD's without permissions. Lets try getting it to work first!!!
This thread will be more organized and better looking after a while.
I don't have the device so deving isn't that easy. Luckily I've had good help from Lloir, I'm going to set up a channel on IRC freenode server so everyone can help and get support.
Development will probably be a bit slow until I get the device. If you want donate so I can afford the device then it's possible through paypal.
I'm going to provide download links and more information on a blog, it's an easy way to sponsor me. Click on a ad when you visit the site and sponsor both my work and so I can buy the phone.
Alpha v0.3
Full ROM
Gapps is not included download from here:
http://cmw.22aaf3.com/gapps/gapps-ics-20120317-signed.zip
Support thread for the ROM
Working:
LED
Touchscreen
Vibrate
Hardware buttons
All Sensors
Most HW buttons work
3g
SMS
Sound
Calling
Not working:
Not sure
GPS
Compass
USB mounting
Wifi
and a lot more
Changelog
Code:
Alpha
v 0.3 /28.06/
Many changes under the hood, but nothing functioning properly yet
But we got all working HW buttons
v 0.2 /17.06/
Starts without FC's
Fully working touchscreen
Most HW buttons work
3g
sms
Calling
Sound is working
All sensors
v 0.1 /16.06/
Initial build
Very unstable
Nothing you can do except have a look
If anyone could pull the proprietary files like this: http://www.droidforums.net/forum/steel-droid/196475-guide-how-build-your-own-rom-cm7-source.html
Then it would be really appricated and help the progress
Thanks to: Lloir, CM team and Evervolv, Drewis and Shaky for teaching me this stuff
Welcome to One V forum brother...
Reserved...
Nice stuff sand ..if you need any help or for testing or anything pm me
Sent from my HTC One V using XDA
Uploading a build right now.
I doubt it'll work since I didn't get the proprietary files, but tried with some backtracking anyway.
http://ge.tt/api/1/files/1ApXNDJ/0/blob?download
Nice to know if logcat works and how far it gets in booting
If anyone is up for testing then I'm on IRC at freenode server in #ics_desire_nexus_dev (not gonna bother setting up a chan before I'm a bit further)
Sandvold said:
Uploading a build right now.
I doubt it'll work since I didn't get the proprietary files, but tried with some backtracking anyway.
http://ge.tt/api/1/files/1ApXNDJ/0/blob?download
Nice to know if logcat works and how far it gets in booting
If anyone is up for testing then I'm on IRC at freenode server in #ics_desire_nexus_dev (not gonna bother setting up a chan before I'm a bit further)
Click to expand...
Click to collapse
update 1:
Ok didnt even boot....
"assert failed: get prop("ro.product.device") == "primo"
anyway it goes on a bit, i also know how to fix that, the problem, it's a faulty update-binary....i can give you my meta-inf if you want after i try it (thanks to htc-phones there), in your rom, ALSO i'll try and sort out the proprietary files for you today
Update 2:
your logcat, http://pastebin.com/A5cwnF73 im just going out for 20mins and i'll try and sort out the proprietary files
Lloir said:
update 1:
Ok didnt even boot....
"assert failed: get prop("ro.product.device") == "primo"
anyway it goes on a bit, i also know how to fix that, the problem, it's a faulty update-binary....i can give you my meta-inf if you want after i try it (thanks to htc-phones there), in your rom, ALSO i'll try and sort out the proprietary files for you today
Update 2:
your logcat, http://pastebin.com/A5cwnF73 im just going out for 20mins and i'll try and sort out the proprietary files
Click to expand...
Click to collapse
Can you repost pastebin....the pink doesnt work...nice work sandvold already ready for some debugging....
Sent from my HTC One V using XDA
here we go this should be easier
Working on it, will see how much I can do before I go to work
Also proprietary would be great
Really close now.
Thx Lloir for testing.
It's booting up until it vibrates on lights turns on. So we're at the stage before it's booting!
*edit
It's booted, still alot of issues
I've made a blog with download links.
It's an easy way for me to get some income to continue using time on this So please click on ONE ad if you visit the blog.
If you want to add download links then add it in comments
should had seen me.....i was like a child when it booted....
Okey have fun with the build. It's not very usable yet, but at least you can have a look
I won't have time to do much today, but I'll probably drop something improved tomorrow.
And click on ONE ad if you visit the site, so I might afford a One V
IMPORTANT
for those of you who test the Alpha build, on 1ST BOOT, your phone will boot into a black screen, you need to hold the power button until your device powers down, and then just power it back up, it WILL boot on 2nd time round.
Oh btw i need a new logcat from both boots + all the fc's
Sent from my HTC Desire using XDA
Lloir said:
IMPORTANT
for those of you who test the Alpha build, on 1ST BOOT, your phone will boot into a black screen, you need to hold the power button until your device powers down, and then just power it back up, it WILL boot on 2nd time round.
Click to expand...
Click to collapse
Logcat after boot please ...
Sent from my HTC One V using XDA
shubhamchamaria said:
Logcat after boot please ...
Sent from my HTC One V using XDA
Click to expand...
Click to collapse
i said i'll do it, im bit busy doing other stuff on this at the moment...i need to flash back to Alpha from Test3 so i'll do it soon
can only go uphill from here... Ha ha...
Im Starting to get grumpy n that now lol, i'll upload the logcats in the next hour or so, then i'll probably get some sleep, as i worked last night lol
EDIT:
Took awhile for the phone to go into deep sleep this time round....here's the logcat though 1st boot, im not going to fc every app that pops up so i did a couple for the log, i'll reboot and get a 2nd cat ina mo
https://www.dropbox.com/s/wqgzjwzsuxus8cn/1stboot.txt
too big for XDA so there it is ^
by the looks of things SDcard works and USB works (notifications)
for some reason i cannot get a 2nd logcat....not sure why.....but i think the 1st logcat by there should cover it....
Lloir said:
Im Starting to get grumpy n that now lol, i'll upload the logcats in the next hour or so, then i'll probably get some sleep, as i worked last night lol
EDIT:
Took awhile for the phone to go into deep sleep this time round....here's the logcat though 1st boot, im not going to fc every app that pops up so i did a couple for the log, i'll reboot and get a 2nd cat ina mo
https://www.dropbox.com/s/wqgzjwzsuxus8cn/1stboot.txt
too big for XDA so there it is ^
by the looks of things SDcard works and USB works (notifications)
for some reason i cannot get a 2nd logcat....not sure why.....but i think the 1st logcat by there should cover it....
Click to expand...
Click to collapse
Thank you will have a look tomorrow
Sent from my HTC Desire using XDA
Sandvold said:
Thank you will have a look tomorrow
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
no worries, im going to work on my next task for you now
sumairmh said:
Welcome to One V forum brother...
Reserved...
Click to expand...
Click to collapse
Why may I ask did you reserve this placeholder?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"~Rush
Sent from my HTC One X, using XDA Premium.
Some of you requested a working CM10, so i'll provide some up-to-date test builds.
Downloadlink: http://www.mediafire.com/?7d2xd0xw9gantpo
Gapps: http://goo.im/devs/OliverG96/gapps-lite/gapps-jb-20120726-lite-rebased.zip (Flash them after you have booted, don't know it these gapps work.)
I don't have much time coming weeks so i'll change the layout of this thread later.
I don't have a HTC Hero, so I don't know what works, what doesn't. I don't even know if it boots.
YOU have to test and report what's working/bugs. It will go slow but it's all I can do.
I have used Shelnutt's CM10 build for HTC Hero CDMA which is quite the same.
Don't forget to push the THANKS button and to thank shelnutt for his builds!
Is this the rom or only gapps ?
hammadjavaid said:
Is this the rom or only gapps ?
Click to expand...
Click to collapse
I just added the downloadlink.
Won't boot. And windows doesnt accept the driver, so no logcat...
Tried first time for a while, and the bootanimation seemed to pick up some speed..
Edit logcatting now! One of the first things I saw was:
I/cm ( 88): Welcome to Android 4.1.2 / CyanogenMod-10-20130105-UNOFFICIAL-heroc
Click to expand...
Click to collapse
Phew, it booted. Animations are a bit slow...
Whole log: http://www.pasteall.org/38695/text
Trackball use shows a mousecursor
Power button does not give a response (so no screenshot)
BT switches on!
WIFI doesnt switch on ...
Does boot. Not very fast rom. Camera is missing. Pleasing on the eye looks nice .
Sent from my Hero using xda app-developers app
It boots, that's a good thing. CM10 is indeed slower as CM9 on my Magic too, probably because it uses even more memory and don't forget it just a raw build.
I'll see if I can get some things improved with scripts.
PowerPlop said:
It boots, that's a good thing. CM10 is indeed slower as CM9 on my Magic too, probably because it uses even more memory and don't forget it just a raw build.
I'll see if I can get some things improved with scripts.
Click to expand...
Click to collapse
Happy to test. My hero is up for sale so I dont know how long i'm able to test it.
How can you dev something if you cant test it? I'm a software dev, but I need my debugger all the time..
jogai said:
Happy to test. My hero is up for sale so I dont know how long i'm able to test it.
How can you dev something if you cant test it? I'm a software dev, but I need my debugger all the time..
Click to expand...
Click to collapse
Because we know what it takes to make it work since the process is almost same, our devices Hero and Magic are not that much different so the steps that are needed to port to magic are not that different from steps needed to port it for hero
jogai said:
Happy to test. My hero is up for sale so I dont know how long i'm able to test it.
How can you dev something if you cant test it? I'm a software dev, but I need my debugger all the time..
Click to expand...
Click to collapse
It's quite easy since once you know which files have to be replaced, you just have to repeat it for every ROM you port. :good:
PowerPlop said:
It's quite easy since once you know which files have to be replaced, you just have to repeat it for every ROM you port. :good:
Click to expand...
Click to collapse
Just to let you know, if you need any help with anything, PM me
Next week i'll try some builds on my HTC Magic first and if things are improved, I will release new builds.
This Rom is for HERO C
dodge67 said:
Does boot. Not very fast rom. Camera is missing. Pleasing on the eye looks nice .
Sent from my Hero using xda app-developers app
Click to expand...
Click to collapse
try some speed tweaks like pure performance x, if this has init.d support...