Related
closed, i made some typo or something when applying the commit to not include recovery.
You aren't using his overlay.
What I mean is, you aren't giving it the command to use his overlay.
After running Koush's . envsetup.sh, type lunch and see what the options are.
I've only compiled aosp roms for the Moto Droid, but what you have above looks like its running a generic build, instead of one outlined for the incredible.
TARGET_PRODUCT=generic_inc
yes i lunch and choose generic_inc or something like that. Ive built successfully for droid as well and make runs fine but it just wont make ota
and how am i not giving it the command to use his overlay? the inc option is only there because i am.
No need to get all defensive.
Its a problem with the overlay or how its being used. It has to be. I built a generic froyo build sans overlay when the stagefright fix was released so that I could distribute it to the suffering audiophiles out there.
I might be wrong, but doesn't otapackage require data from the overlay?
lol didnt mean to be, its late. soooo how can i go about fixing this?
yes i believe so as it tells it the specifics of the build. I made several changes to the core makefiles and some in the vendor overlays to fix errors. Think this could be why?
Well, I found this, which is basically pulling a patch.
http://comments.gmane.org/gmane.comp.handhelds.android.platform/13747
Worth a shot?
i fixed the problem by changing infreq to ifreq in certain parts of the core makefile. A change that was supposed to be merged.
Good to know, thanks for the update. I wonder if thats the same thing thats done by the above article (end result)?
not my current problem, the 64 bit problem
can you please make it so i can post and not wait 5 mins please lol? i said that out of context.....
still have not fixed the problem :/
Hi, I noob on this of an Android Phone, I have a HTC TOUCH PRO 2, RHOD210.
I install the FROYO X 2011.01.12 and i put the kernel that have the packet than run the camera and this is OK.
My problem is that the wifi interface is not workink, i am try a lot of solutions that found in this forum, but nothing is ok for me, i change the rootfs like suggest in a forum, modify the wifi-nvram.txt and put the mac address of the wifi, i update the kernel to Latest Kernel Commit# 1253, and i have the same problem.
could someone tell me how to solve the wifi of my rhod210?
Please, I do not want to use windows mobile
How about you just run with vanilla FRX03 and then try to get fancy with it?
Let us know how that works, then we can work on updating your kernel. If you're a noob at swimming, you don't start in the deep end...
arrrghhh said:
How about you just run with vanilla FRX03 and then try to get fancy with it?
Let us know how that works, then we can work on updating your kernel. If you're a noob at swimming, you don't start in the deep end...
Click to expand...
Click to collapse
Sorry, i'm only was trying to solve the problems for my self.
I understand that some of these RHOD210 if they have managed to run the wifi.
I tell you that I use from the beginning FRX03 and it worked well, at least part of the telephone, sound and GPS, but other things did not work, so I started to search the forums and trying different solutions. but I have not found a way to walk the wifi which is what most interests me, so probe, with the latest versions of the kernel etc.
Thanks, I know I'm a rookie, but I like trying to find solutions to the problems I have ....
kleper said:
Sorry, i'm only was trying to solve the problems for my self.
I understand that some of these RHOD210 if they have managed to run the wifi.
I tell you that I use from the beginning FRX03 and it worked well, at least part of the telephone, sound and GPS, but other things did not work, so I started to search the forums and trying different solutions. but I have not found a way to walk the wifi which is what most interests me, so probe, with the latest versions of the kernel etc.
Thanks, I know I'm a rookie, but I like trying to find solutions to the problems I have ....
Click to expand...
Click to collapse
Yes, and I'm trying to help you triage. You said a lot in this post, but didn't answer my question.
Does wifi work with a vanilla FRX03 bundle?
arrrghhh said:
Yes, and I'm trying to help you triage. You said a lot in this post, but didn't answer my question.
Does wifi work with a vanilla FRX03 bundle?
Click to expand...
Click to collapse
Does't work wifi in vanilla FRX03, in fact, the phone worki slow with this kernel, with FROYO is more faster.
Thanks.
kleper said:
Does't work wifi in vanilla FRX03, in fact, the phone worki slow with this kernel, with FROYO is more faster.
Thanks.
Click to expand...
Click to collapse
Erm, I guess I should be more specific.
Where did you download vanilla FRX03? Also, FRX03 is Froyo, so I assume you mean that Froyo 'X' build tiad8 put together.
Also, I'm not sure what you mean "slow with this kernel" - by vanilla FRX03 build, I mean the complete bundle - not just the kernel. Plus, kernels are not tied to system images... So I'm not sure what you mean.
arrrghhh said:
Erm, I guess I should be more specific.
Where did you download vanilla FRX03? Also, FRX03 is Froyo, so I assume you mean that Froyo 'X' build tiad8 put together.
Click to expand...
Click to collapse
Yes, is this build, i look de dmesg logs of the phone, and i see an error that say: can't found the mac address of the wifi. and, i look the file, wifi-nvram.txt and this file have the mac address that i look on windows mobile.
kleper said:
Yes, is this build, i look de dmesg logs of the phone, and i see an error that say: can't found the mac address of the wifi. and, i look the file, wifi-nvram.txt and this file have the mac address that i look on windows mobile.
Click to expand...
Click to collapse
I thought I already directed you to this thread, but it seems to be your issue... so follow these directions. See F22's post.
arrrghhh said:
I thought I already directed you to this thread, but it seems to be your issue... so follow these directions. See F22's post.
Click to expand...
Click to collapse
I do that, and don't work for me.
Thanks
kleper said:
I do that, and don't work for me.
Click to expand...
Click to collapse
Well then, I guess you just can't have wifi...
Honestly, every single person either wifi "just works", or they have to do the wifi-nvram trick. I've never heard of anyone not being able to use wifi, that didn't try the wifi-nvram trick - and those people were definitely in the minority. Vast majority of people, wifi works perfectly fine for.
Please, be a little more diligent. I can't do this troubleshooting for you, I can only point you in the right direction. I need you to do some legwork, as I can't see what you're doing.
arrrghhh said:
Well then, I guess you just can't have wifi...
Honestly, every single person either wifi "just works", or they have to do the wifi-nvram trick. I've never heard of anyone not being able to use wifi, that didn't try the wifi-nvram trick - and those people were definitely in the minority. Vast majority of people, wifi works perfectly fine for.
Please, be a little more diligent. I can't do this troubleshooting for you, I can only point you in the right direction. I need you to do some legwork, as I can't see what you're doing.
Click to expand...
Click to collapse
Fine, i go to format again my SD-CARD and start from zero, any installer recomeded? or pick the installer that i want?
how do I find out my exact model, I'm assuming is that it's RHOD210 for photos and that according to information I have read I understand that T-Mobile only has this HTC TOUCH PRO2, can that be part of my error, there is a way to identify exactly which model is?
kleper said:
how do I find out my exact model, I'm assuming is that it's RHOD210 for photos and that according to information I have read I understand that T-Mobile only has this HTC TOUCH PRO2, can that be part of my error, there is a way to identify exactly which model is?
Click to expand...
Click to collapse
Sticker underneath the battery - not on the battery itself. It's usually in tiny gray font.
kleper said:
Fine, i go to format again my SD-CARD and start from zero, any installer recomeded? or pick the installer that i want?
Click to expand...
Click to collapse
Well, I'd format with the HP tool. (Full format, FAT32) Download this bundle as well.
[SOLVED]
Thank you very much to everyone who answered me and all the developers of this project so interesting, yesterday succeeded in solving the problems I had, my SD formatting, reinstalling Froyo x version 2011.01.12 and puts a kernel of the chamber, after That did the trick again wifi-nvram.txt file, according to the link that let me arrrghhh one of the threads of this forum, after that the WIFI has started to work wonders.
Then my HTC Touch Pro 2, RHOD210 remain with:
WIFI
CAMERA
GPS
PHONE, DATA AND YOU
AUDIO
Thank you very much.
Remember to use zImage and Modules package from the same place and that only WPA is working , NO WEP !
eu0741924381 said:
Remember to use zImage and Modules package from the same place and that only WPA is working , NO WEP !
Click to expand...
Click to collapse
WEP actually seems to work on mine. Strange as that is.
Other problems
These days I've been testing my phone RHOD210 Android, after having settled about the WIFI, but I noticed a problem is that the phone is locked, I can receive a call and make a call, and thereafter ceases to operate the module telephony, change the 1214-Dirty kernel that runs the camera for the 1253 and I have the same problem, another thing I noticed is that the speakerphone does not work completely, it is telling me the microphone works but not the headphones, someone happened?
kleper said:
These days I've been testing my phone RHOD210 Android, after having settled about the WIFI, but I noticed a problem is that the phone is locked, I can receive a call and make a call, and thereafter ceases to operate the module telephony, change the 1214-Dirty kernel that runs the camera for the 1253 and I have the same problem, another thing I noticed is that the speakerphone does not work completely, it is telling me the microphone works but not the headphones, someone happened?
Click to expand...
Click to collapse
Uhm... the older kernel doesn't have the commits for speakerphone mic I would say. Once it all gets committed to GIT it will be a lot less confusing - just a lot of code that's in testing right now basically.
jchutch2 said:
WEP actually seems to work on mine. Strange as that is.
Click to expand...
Click to collapse
WEP should never, ever be used in any circumstances if it can be avoided. That protocol is extremely insecure...
arrrghhh said:
Uhm... the older kernel doesn't have the commits for speakerphone mic I would say. Once it all gets committed to GIT it will be a lot less confusing - just a lot of code that's in testing right now basically.
Click to expand...
Click to collapse
What kernel do you recommend for my RHOD210, the 1253 is doing that the phone will be frozen and I have to Quiaro the battery and put it again to restart the system.
Wonder that in the future will be able to remove the windows and flash the device with adro to make it natively? : D
Thank you very much
kleper said:
What kernel do you recommend for my RHOD210, the 1253 is doing that the phone will be frozen and I have to Quiaro the battery and put it again to restart the system.
Wonder that in the future will be able to remove the windows and flash the device with adro to make it natively? : D
Thank you very much
Click to expand...
Click to collapse
Well, I'd recommend 1250 then I guess... Usually I recommend the newest GIT kernel, which is currently 1253.
FYI, you already can remove Windows and flash the device to run Android natively. It's just not as stable as haret, but it's getting there. Plus, it's only a partial NAND boot - only init and the zImage are actually loaded on the MTD if I'm not mistaken, everything else is on the SD card (which is still 99% of the data...)
But, if you're feeling brave and really do want to completely get rid of WinMo, NAND boot away... can't say I didn't warn ya
Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps! We don't make empty promises, we just provide solid and complete builds. No ETA's, no threads without download links or instructions... Enjoy!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for BLAC) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog
Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location)
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
This line should be in the startup.txt file if that wasn't obvious .
Thanks to emc02 for that solution!
The keyboard should be fine, but I've had some Blackstone users complain - if you want, switch the keyboard out with another. mr_grisha's original post. Others have said this is a horrible keyboard, and you should just use Swype. I'm a big fan of use what works for you, so you folks make the decision for yourself!
Anything that's broken in Froyo, is probably broken in this build.
Blackstone users - help me flesh out this section! Anything that's not working let me know!
Changelog March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)
Enabled HSPA icon (someone on GSM please let me know if it actually works).....this does not work on my blackstone.....nor does it work on frx06.......overall gbxoa and frx06 works resonable well.....
Startup.txt that works with frx06 and gbx0a
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msm_blackstone_pad.vibrate=1 msmvkeyb_toggle=off gsensor_axis=-2,-1,3 msmsdcc_nopwrsave rel_path=GBX0A"
boot
use as "rel_path=*****",where ***** is the name of the folder where haret and other files are located (GBX0A in this example),eg if using stock names use FRX06 for frx06 and GBX0A for gbx0a
sensor rotation should be as it is in the text above
also stock android keyboard doesn't work,and keyboard suggested in first post works a bit crappy (with all due respect),so you should use some other,i personally use swype and it doesn't matter if you swype or just type,because swype is great for typing too,it's fast and responses instantly (unlike betterkeyboard)
i think F22's rootfs are modified to fit rhodium which has keyboard and different button mapping so there is no need to use it...you know,no need for additional code lines which are not necessary
i suggest using zeam launcher it's faster and lighter than the stock one
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
if you want to be able to install more apps,go to this thread and grab the data.img maker (resize tool)
http://forum.xda-developers.com/showthread.php?t=824154
if you need storage access,use wifi explorers,they proved very good solution for not being able to access sotrage via usb
welard said:
Enabled HSPA icon (someone on GSM please let me know if it actually works).....this does not work on my blackstone.....nor does it work on frx06.......overall gbxoa and frx06 works resonable well.....
Click to expand...
Click to collapse
Yea, IIRC the new RIL is required to properly show H. Does it show in WinMo? Thanks for the feedback .
farukb said:
not sure if pmem.extra=1 is needed at all and does it perfor better without it,i read somewhere that it does....maybe arrrghhh knows
use as "rel_path=*****",where ***** is the name of the folder where haret and other files are located (GBX0A in this example),eg if using stock names use FRX06 for frx06 and GBX0A for gbx0a
sensor rotation should be as it is in the text above
i've attached ts-calibration for blackstone,so if anyone needs it,it is precisely calibrated....additionally if someone wants to do it by himself,he (she) should use 11** kernels (current are 13**),because calibraiton feature was removed from later kernels
Click to expand...
Click to collapse
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
arrrghhh said:
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
Click to expand...
Click to collapse
yeah...i read that...think it was your post i remember you being allergic to that line
that in blue and red was for user who don't know how to do it,just a little hint....also i think provided startup.txt is ok,i just posted this so someone who maybe modified it or lost it can have it easily without having to download whole 120mb package
farukb said:
yeah...i read that...think it was your post i remember you being allergic to that line
that in blue and red was for user who don't know how to do it,just a little hint....also i think provided startup.txt is ok,i just posted this so someone who maybe modified it or lost it can have it easily without having to download whole 120mb package
Click to expand...
Click to collapse
Ah no worries. Let me know if there is something you think I should change, I don't have a Blackstone and I'm always looking to improve the process for you guys!
arrrghhh said:
Yea, IIRC the new RIL is required to properly show H. Does it show in WinMo? Thanks for the feedback .
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
Click to expand...
Click to collapse
yes it shows in window....thanks
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
if you want to be able to install more apps,go to this thread and grab the data.img maker (resize tool)
http://forum.xda-developers.com/showthread.php?t=824154
copied everything to 5th post,so it's all in one place
farukb said:
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
Click to expand...
Click to collapse
all above quoted the same for me to......sometime loading apps can sometime take time to load and battery life falls quickly when downloading from market.........
farukb said:
also stock android keyboard doesn't work,and keyboard suggested in first post works a bit crappy (with all due respect),so you should use some other,i personally use swype and it doesn't matter if you swype or just type,because swype is great for typing too,it's fast and responses instantly (unlike betterkeyboard)
Click to expand...
Click to collapse
What recommendation do you have? I didn't think Swype was free..?
farukb said:
i think F22's rootfs are modified to fit rhodium which has keyboard and different button mapping so there is no need to use it...you know,no need for additional code lines which are not necessary
Click to expand...
Click to collapse
Probably true, I'll take that part out thanks.
farukb said:
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
Click to expand...
Click to collapse
orly... that's an odd bug. It seems that the hardware is not initialized by Android...
farukb said:
front camera
Click to expand...
Click to collapse
I'll add it, but don't expect it to work anytime soon .
farukb said:
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
Click to expand...
Click to collapse
I remember this bug, related to the battery code. g3rm0's kernel isn't such a good solution, it just kills the battery provider... I'll see if I can bug a dev into fixing it. Not sure what the actual problem is - does this persist even in the newest autobuild kernels?
farukb said:
@arrrghhh, i think you should remove the sensor rotation part of the post,because could confuse people...but then again you're the boss,so do as you please
Click to expand...
Click to collapse
For the DIAM? Is that not required? Sorry 'bout that. I removed it . I want this to be a Blackstone-specific thread, after all it is in the Blackstone forum. So anything I can do to help newbies with Blackstones is great. Keep up the feedback, and let me know how I can improve!
welard said:
all above quoted the same for me to......sometime loading apps can sometime take time to load and battery life falls quickly when downloading from market.........
Click to expand...
Click to collapse
Yup... apps loading for a while are partially due to the old hardware. Some of it might be the SD card being slow... NAND won't be a ton faster, but should give a little boost.
Battery life falls quickly because the battery driver is inherently flawed. There's some new battery software (SCBS) and it should improve this, but it doesn't seem like it'll be implemented into mainline anytime soon (many devices need support...)
arrrghhh said:
What recommendation do you have? I didn't think Swype was free..?
Probably true, I'll take that part out thanks.
orly... that's an odd bug. It seems that the hardware is not initialized by Android...
I'll add it, but don't expect it to work anytime soon .
I remember this bug, related to the battery code. g3rm0's kernel isn't such a good solution, it just kills the battery provider... I'll see if I can bug a dev into fixing it. Not sure what the actual problem is - does this persist even in the newest autobuild kernels?
For the DIAM? Is that not required? Sorry 'bout that. I removed it . I want this to be a Blackstone-specific thread, after all it is in the Blackstone forum. So anything I can do to help newbies with Blackstones is great. Keep up the feedback, and let me know how I can improve!
Yup... apps loading for a while are partially due to the old hardware. Some of it might be the SD card being slow... NAND won't be a ton faster, but should give a little boost.
Battery life falls quickly because the battery driver is inherently flawed. There's some new battery software (SCBS) and it should improve this, but it doesn't seem like it'll be implemented into mainline anytime soon (many devices need support...)
Click to expand...
Click to collapse
will we see meny of these fixes in frx07 and gingerbread in the next release? (nice to see things are happening here again by the way)
@argh
swype is free,you just need to register and you gain access to swype beta
it's called beta because it is made for devices that don't come with if out of the box and therefore are still developing it,but it works great,nevertheless
welard said:
will we see meny of these fixes in frx07 and gingerbread in the next release? (nice to see things are happening here again by the way)
Click to expand...
Click to collapse
well actually,nothing is happening at all all this is available since march (except for some of the incremental updates which chronologically came out later)
farukb said:
well actually,nothing is happening at all all this is available since march (except for some of the incremental updates which chronologically came out later)
Click to expand...
Click to collapse
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
welard said:
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
Click to expand...
Click to collapse
they might,but arrrghhh is a tester,not sure if he is a dev himself,but he could help pursue devs to do it
as for improvements,very few improvements happened at all over last few months to any device supported by xdandroid project
welard said:
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
Click to expand...
Click to collapse
I was always around, but having dedicated threads in the Blackstone section will help. I tried to get others to create threads to support Blackstone, but I guess no one ever did... So here I am! Trying to support without a device.
If anyone feels like donating a device, it would be much appreciated. XDAndroid will pay shipping if you're willing to donate the device to a dev!
farukb said:
they might,but arrrghhh is a tester,not sure if he is a dev himself,but he could help pursue devs to do it
as for improvements,very few improvements happened at all over last few months to any device supported by xdandroid project
Click to expand...
Click to collapse
This is not true! There's been a ton of development over the last few months... It happens in spurts, but there has been quite a bit.
I'm not much of a dev (played around with init, working on getting rid of manual ts-calibration) but I am 'lead tester' for the project, I maintain the wiki, releases, and track bugs on the bugtracker.
arrrghhh said:
I was always around, but having dedicated threads in the Blackstone section will help. I tried to get others to create threads to support Blackstone, but I guess no one ever did... So here I am! Trying to support without a device.
If anyone feels like donating a device, it would be much appreciated. XDAndroid will pay shipping if you're willing to donate the device to a dev!
This is not true! There's been a ton of development over the last few months... It happens in spurts, but there has been quite a bit.
I'm not much of a dev (played around with init, working on getting rid of manual ts-calibration) but I am 'lead tester' for the project, I maintain the wiki, releases, and track bugs on the bugtracker.
Click to expand...
Click to collapse
i have not a device to donate.....but if we all donate for a device that would speed things up much faster...... i think you should start a new thread for donate for a blackstone device......im sure theres lots of blackstone users willing to do this because the end result will pay off for all of us.......
i had a sod and now i can't boot,the animation just keeps looping...hw buttons vibrate then i touch them,but do not work....power button doesn't work either
happened to me once before,but i don't know what i did to solve it...i maybe deleted the data.img
this time i tried to wipe and format the partition,didn't help
i tried with fresh files (except for the data.img) but still nothing...
@arrrghhh: wanna swap with me for your rhodium,if you want it badly?
@werald and others:if we are going to donate a device,it'd be best to donate it do a dev,maybe stinebd,don't know
First of all I want to make some things clear:
This is my own custom build I made with the help of this great tutorial: http://forum.xda-developers.com/showthread.php?t=775505
This has nothing to do with the offical nightly build from Cyanogen and his team.
I won't provide any support for this. If you want to flash this you should know what you do. Don't ask me anything like "How do I flash this?".
This could be even more unstable then the official nightly build since I add commits that are not merged. It's a great feature preview, but I can't guarantee anything. I can't tell you if the features you see here will make it into any official build.
What is it?
Its a custom build of the latest Cyanogen sources spiced up with some not (yet?) merged patches.
I don't know how often I will make new builds, it depends if I find new things I want to try. If there are no new commits that interest me I won't make a new build.
I will only upload builds that work for me. So the basic stuff should work for everyone, if it doesn't try to wipe before flashing. If it still doesn't work use the official nightly/RC/stable/whatever... (Thats the point with "I won't provide any support").
Difference to the official CM nightly
Download
MD5
I made something like this already for the Nexus One and many people liked it.
And since we don't get official nightlys since a long time already I thougt I start making my own nightlys again.
02/10/2012: new build, added latest commits from cm + cherry picked commits (again with AROMA Installer to choose WiFi calling)
02/04/2012: same build but with AROMA Installer. You can choose if you want to have WiFi calling or not before flashing the ROM.
02/01/2012: new build, added latest commits from cm + cherry picked commits
Thanks dude, good work.
I compiled my own CM7 Rom, but not sure how to apply those unapproved changes from the review platform, would u give me a hint ?
pentie said:
Thanks dude, good work.
I compiled my own CM7 Rom, but not sure how to apply those unapproved changes from the review platform, would u give me a hint ?
Click to expand...
Click to collapse
You need to cherry pick them
http://wiki.koha-community.org/wiki/Using_Git_Cherry_Pick
Why is anybody still screwing around with Android 2.3? This line is finished/dead/obsolete. Let it go already.
dhkr234 said:
Why is anybody still screwing around with Android 2.3? This line is finished/dead/obsolete. Let it go already.
Click to expand...
Click to collapse
How is it dead? 2.3 is what our phones can run most efficiently with speed and smoothness, 4.0 is still choppy and major graphical glitches. Not everyone wants an unstable rom which will not be at it's optimum until a while longer.
On the other hand, I will be trying this out and thank you for putting in your time and effort to bring us another rom to choose from
I noticed no wifi calling....
I noticed in your docs that wifi calling is not included, any chance of getting this added back in?
dhkr234 said:
Why is anybody still screwing around with Android 2.3? This line is finished/dead/obsolete. Let it go already.
Click to expand...
Click to collapse
Since ICS ROMs don't have camera fully working I wouldn't consider 2.3 dead. Many people including myself require a fully functional camera.
With that said I actually couldn't get camera and gallery to work on this ROM. I flashed it on top of stable CM 7.1.0 wiping only cache and dalvik.
I'm not going to do a full wipe at this point, neither am I looking for support but thought I would mention it.
dhkr234 said:
Why is anybody still screwing around with Android 2.3? This line is finished/dead/obsolete. Let it go already.
Click to expand...
Click to collapse
The Cyanogenmod team is still going to release CM 7.2. So they're also still "screwing" around with it.
dhkr234 said:
Why is anybody still screwing around with Android 2.3? This line is finished/dead/obsolete. Let it go already.
Click to expand...
Click to collapse
What???
You say that the version which works best on our phone is dead?
You mean 4.0 which brings us graphical glitches, no fully functional camera, bluetooth issues ... is better?
Lets talk about this in half a year again, but for now Gingerbread is the most stable and best performing version for our phones.
bradley_e_smith said:
I noticed in your docs that wifi calling is not included, any chance of getting this added back in?
Click to expand...
Click to collapse
Maybe I'll make an additional zip for wifi calling, I won't include it in the rom for sure since I can't use it.
Just a heads up...for some reason removing the wifi calling files breaks my APN connection with AT&T. Makes no sense on the surface. Put back both the apks and the libs and I've got signal again.
sisterchick said:
Just a heads up...for some reason removing the wifi calling files breaks my APN connection with AT&T. Makes no sense on the surface. Put back both the apks and the libs and I've got signal again.
Click to expand...
Click to collapse
Did you change something in the build.prop too?
Everthing works fine here, making calls, data connection...
Sent from my HTC Vision using Tapatalk
g4rb4g3 said:
Did you change something in the build.prop too?
Everthing works fine here, making calls, data connection...
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
No, I didn't touch build.prop. I thought I may try it again tonight, removing the apks and libs one at a time to see what breaks the connection with AT&T.
sisterchick said:
No, I didn't touch build.prop. I thought I may try it again tonight, removing the apks and libs one at a time to see what breaks the connection with AT&T.
Click to expand...
Click to collapse
Weird, without changing the rilpath in build.prop the libs you pushed won't get loaded...
I'm curious which file is making you connection work again, please tell me when you found it out. Thanks!
Sent from my HTC Vision using Tapatalk
erichung_13 said:
How is it dead? 2.3 is what our phones can run most efficiently with speed and smoothness, 4.0 is still choppy and major graphical glitches. Not everyone wants an unstable rom which will not be at it's optimum until a while longer.
On the other hand, I will be trying this out and thank you for putting in your time and effort to bring us another rom to choose from
Click to expand...
Click to collapse
Agreed 2.3 is the most stable, ICS has a long way to go.
tarroyo said:
Agreed 2.3 is the most stable, ICS has a long way to go.
Click to expand...
Click to collapse
The key word you've used is STABLE.
No need to keep dicking around with what already exists. If you want to use it, fine. But there's nothing left worth adding to it, and DEVELOPERS NEEDED ON 4.0!!!
dhkr234 said:
The key word you've used is STABLE.
No need to keep dicking around with what already exists. If you want to use it, fine. But there's nothing left worth adding to it, and DEVELOPERS NEEDED ON 4.0!!!
Click to expand...
Click to collapse
Your bridge is waiting for you.
dhkr234 said:
The key word you've used is STABLE.
No need to keep dicking around with what already exists. If you want to use it, fine. But there's nothing left worth adding to it, and DEVELOPERS NEEDED ON 4.0!!!
Click to expand...
Click to collapse
Whoa bro, what's up with you? Any kind of development for our phone should be appreciated. ics is on its way. We already have 3 dev teams working on it. If g4rbag3 wants to work on something else and you don't like it, quit dicking around in his thread.
Since I saw some nice commits got merged I made an update.
g4rb4g3 said:
Since I saw some nice commits got merged I made an update.
Click to expand...
Click to collapse
This nigga knows !
#IgnoreTheHaters
Credits goes to st.matt, he gets full credit for the programming. He seemed a little busy, so I thought I'd spread the news so you guys can implement into your builds.
st.matt said:
Also just a run-down of how it works for anyone that is interested:
I use three different elements to get it working. Firstly, I use a small addition to surfaceflinger to set a system property (sys.orientation.landscape) to 1 when it is in landscape mode (either 90 or 270 degrees rotation) and 0 when it is in portrait mode (0 degrees rotation).
When this is set an init service will start depending on the value of sys.orientation.landscape, which in turn starts a script (/system/etc/rotate_lights.sh) which takes the brightness value from the expected led class (ie. if it's changing to landscape it will look at /sys/class/leds/button-backlight-portrait/brightness) and then set this to the new orientation's led class.
The third part is a small modification to the lights lib which also checks that system property when making changes to the button backlight brightness so that it sets it to the correct class.
Click to expand...
Click to collapse
The necessary files/code are on Virtuous' ICS vivo repository: https://github.com/vivo-ICS/android_device_htc_vivo, and you will also need the patched proprietary libsurfaceflinger.so that references to the changes.
Any way to make this backward compatible with cm7.2?
Un1c0de said:
Any way to make this backward compatible with cm7.2?
Click to expand...
Click to collapse
made a CM7.2 kang for you Inc2 users.
All I did was put in the latest commits as of March 03 2012 and added the rotating softkeys. I can't really test it because I don't have an Inc2, so back up your data in case you are not sure if it will work.
You can flash this without wiping if you are on 7.x already.
For the IncS, I know the rotating buttons for them are not perfect. Sometimes you have to toggle the brightness to get it working. Other times it might take a few seconds to rotate instead of immediately. This is because this script was originally written for ICS roms in mind, but it's backwards compatible with GB.
http://www.mediafire.com/?lggqggdx1m4n656
Wow thanks Kaijura. Downloading now, will post back with results
Sent from my Incredible 2 using xda premium
Thanks Kaijura for posting the info, and the CM7 build. Appreciate it a lot
Is this rom dependent? It will only work on cm 7.2? has anyone tried it on miui? Or any other roms?
Sent from my Incredible 2 using xda premium
Ihatepullups said:
Is this rom dependent? It will only work on cm 7.2? has anyone tried it on miui? Or any other roms?
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
knipp21 said:
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Ah, that blows would have been cool... Hey if someone points me in the right direction, I'll try: I know how to use adb and the sdk and I'm an experienced ROM'aholic
Sent from my Incredible 2 using xda premium
Awesome. Hopefully I have time tonight to check it out. Thanks
knipp21 said:
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Ihatepullups said:
Ah, that blows would have been cool... Hey if someone points me in the right direction, I'll try: I know how to use adb and the sdk and I'm an experienced ROM'aholic
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
its different for miui, because we dont build it from source and cant cherry pick commits
miui is more like a sense rom port that uses cm9 or another aosp rom as a "base"
any significant changes have to be done in smali, which is more involved than java source....i k nowwhat has to be changed (or at least part of it) and where for rotating buttons in miui by diffing the builds from aerovan before and after it was implemented but it was a no go on my part...and didnt seem worth the effort to keep pursuing it atm
I tried this yesterday. My phone wouldn't get past the HTC boot screen. I ended up having to pull the battery and reflash my current ROM.
zohner said:
I tried this yesterday. My phone wouldn't get past the HTC boot screen. I ended up having to pull the battery and reflash my current ROM.
Click to expand...
Click to collapse
Hmm, well I guess that didn't work. If you push /system/lib/libsurfaceflinger.so from an earlier working build you should probably be able to boot.
I just copied the file over from the vivo build which seems that it doesn't work with the vivow.
Guess the vivow surfaceflinger is done differently.
kaijura said:
made a CM7.2 kang for you Inc2 users.
All I did was put in the latest commits as of March 03 2012 and added the rotating softkeys. I can't really test it because I don't have an Inc2, so back up your data in case you are not sure if it will work.
You can flash this without wiping if you are on 7.x already.
For the IncS, I know the rotating buttons for them are not perfect. Sometimes you have to toggle the brightness to get it working. Other times it might take a few seconds to rotate instead of immediately. This is because this script was originally written for ICS roms in mind, but it's backwards compatible with GB.
http://www.mediafire.com/?lggqggdx1m4n656
Click to expand...
Click to collapse
Just tried a flash over but didnt work for me. I guess I can always try a wipe and install.
This wouldn't be hard to add to Miui -- as long as they have no weird additions to libsurfaceflinger. You just need the patched liblights, patched libsurfaceflinger (built for CM), script in /system/etc and changes to init.vivo.rc (or init.vivow.rc for Inc2).
Requires no changes to smali or framework.
The other thing is that if someone wants to clean it up and submit it to CM then the MIUI team will pick it up themselves (someone already did this but didn't seem to have to skill / couldn't be bothered to clean it up to their standards and also didn't really submit it correctly).
I would do this but I don't really have the time these days.
Also: I suspect the problem with the lights not working sometimes could be solved just by adding the conditional I have that checks first to see if the brightness is zero to both orientations (in rotate_lights.sh). I will have a quick look at this soon.
just wanted to share a slight modification in the script. When the brightness level is set to the least the leds turn off completely. The attached script makes sure the leds do not turn off completely at this instance. Unzip the file and replace the file in your /etc/ folder. You may want to make a backup of your existing rotate_lights.sh just in case. Ensure the permissions on the file are the same as before after copying.
Just realized that the settings work only the first time when the phone is rotated. I guess I need a better fix. Sorry, remove the attachment as it has undesired issues. Fix No damn good.