Related
As the title states, I noticed when my barebones build boots it complains about a missing script for the leds. Does anyone have it? I have a feeling missing that script is what is causing the funky led issues. That or it was deprecated, I want to know more about it.
aceoyame said:
As the title states, I noticed when my barebones build boots it complains about a missing script for the leds. Does anyone have it? I have a feeling missing that script is what is causing the funky led issues. That or it was deprecated, I want to know more about it.
Click to expand...
Click to collapse
its in the /bin folder i believe, i would check scoots build
That's the thing though, mine basically is scoots build. Unless he forgot to add perhaps the script in? Because mine was based off a nightly that scoot hasn't used for any of his builds so mine is kinda custom.
aceoyame said:
That's the thing though, mine basically is scoots build. Unless he forgot to add perhaps the script in? Because mine was based off a nightly that scoot hasn't used for any of his builds so mine is kinda custom.
Click to expand...
Click to collapse
I compiled your build a couple of days after compiling RLS5 i think, i haven't included leds.sh in anyof my builds i don't think because i couldn't see that it did a lot, maybe it just activates the wifi and bluetooth leds on startup if wifi was left on over a reboot maybe, dunno, i've attached it anyway.
Edit : Tell a lie, i did include it in my latest build but must have missed it out of RLS5 or accidently deleted it making other changes, dunno, anyway you can put it back in to system/bin
scooter1556 said:
I compiled your build a couple of days after compiling RLS5 i think, i haven't included leds.sh in anyof my builds i don't think because i couldn't see that it did a lot, maybe it just activates the wifi and bluetooth leds on startup if wifi was left on over a reboot maybe, dunno, i've attached it anyway.
Edit : Tell a lie, i did include it in my latest build but must have missed it out of RLS5 or accidently deleted it making other changes, dunno, anyway you can put it back in to system/bin
Click to expand...
Click to collapse
Well whatever the case is at least now I have the file. I only wanted it to get rid of the message lol. How's CM 7 coming along? Anything I can help with?
aceoyame said:
Well whatever the case is at least now I have the file. I only wanted it to get rid of the message lol. How's CM 7 coming along? Anything I can help with?
Click to expand...
Click to collapse
CM7 is coming along ok, the basic android os is running relatively well especially now google have updated there apps to work properly with gingerbread, it's the cyanogen fancy features which are taking the time but without them it would just be a standard AOSP build which defeats the object so still getting CMParts etc sorted at the minute
Well... first:
#
# LED-controller for Kaiser
# by kallt_kaffe
#
kallt_kaffe might have more answers
Second, after 60 seconds, the script enters a while loop that always runs.
Third, it checks for the existance of 2 files:
/sys/class/leds/wifi/brightness
/sys/class/leds/blue/brightnes
And then uses a getprop to findout if wife and bluetooth are on. if yes, it writes '2' to those files probably to set the led on, respectively of course.
If not, sleep 10 seconds, retry.
I belive this as been made deprecated and/or redundante in recent releases, correct me if i'm wrong.
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
I have, for the most part, returned from my leave of absence and hopefully this time around I will be able to provide you folks with something a bit more useful.
Admittedly, this was a fairly halfhearted attempt but, hey, it's something to start with. I branched the CM7 for Nook Color source. Part of the compilation process involves running a script (system/device/bn/encore/extract-files.sh) that extracts proprietary libraries (or something?) from stock Nook Color, so I plugged in a rooted N2E instead for this step and ripped the files off of it. Some files were missing from the N2E, so I copied those over from a Nook Color. Here's a list of those files:
Code:
/system/lib/libOMX.TI.720P.Decoder.so
/system/lib/libomap_mm_library_jni.so
/system/etc/powervr.ini
/system/lib/libpvrPVR2D_FLIPWSEGL.so
/system/lib/libusc.so
/system/lib/libpvrPVR2D_FRONTWSEGL.so
/system/lib/libOpenVG.so
/system/lib/libOpenVGU.so
/system/lib/liba2dp.so
/system/lib/hw/alsa.omap3.so
/system/usr/share/alsa/init/hda
/system/usr/share/alsa/init/00main
/system/usr/share/alsa/init/help
/system/usr/share/alsa/init/default
/system/usr/share/alsa/init/info
/system/usr/share/alsa/init/test
Compilation of the franken-nook-color source went without problems.
Unfortunately although unsurprisingly, the produced userland doesn't boot. I'll keep y'all updated with my progress; this is only the very tip of the iceberk.
I have two NST so I can use one for testing your rom if you promise no to brick it very often ;-)
I have a NST that, while the 3/4's of the screen is broken, it still functions fine and I can see anything in the top right quadrant of the screen. It doesn't do anything else for me, so you're welcome to brick it in the name of experimentation.
Thanks for the offering! I am not really in need of anything just yet but should anything come up I will PM y'all.
Anyhow, I tried again but this time excluded all the missing prop files from the build by editing them out of device-vendor-blobs.mk. It still didn't work so that means we're probably going to have to find a way to actually debug it instead of using trial and error like we have been.
Maybe there is like, a serial port or something on this thing.
klausef said:
Maybe there is like, a serial port or something on this thing.
Click to expand...
Click to collapse
Yes there is a UART on the OMAP3621.
Still, it's hard to get any info out of TI since it's an OEM part.
Does anybody have a real pinout?
Actually, unless somebody has a dead Nook that you can pull the processor off it would be hard to trace.
I guess the best bet would be to look for suspicious unused pc lands.
Can you toggle the charge light gpio as a progress indicator?
You don't need anything special.
As long as you can boot a kernel, which you can, you can do all your debugging over adb. Just enable adbd in the ramdisk.
The use for a serial console is for debugging KERNEL failures.
The firsts thing you really need to work on instead of just trying to boot CM7, is a compatible NST Kernel. Without a CM7 compatible kernel as far as I know it just won't boot. Once you know the kernel works you should start work on getting /system and such to work, as far as I know the major differences between the Nook Color and the Nook Touch are the input types and display types, which means you'll have to replace the drivers with ones that actually work.
GabrialDestruir said:
The firsts thing you really need to work on instead of just trying to boot CM7, is a compatible NST Kernel. Without a CM7 compatible kernel as far as I know it just won't boot. Once you know the kernel works you should start work on getting /system and such to work, as far as I know the major differences between the Nook Color and the Nook Touch are the input types and display types, which means you'll have to replace the drivers with ones that actually work.
Click to expand...
Click to collapse
Thanks for the direction, I kind of have been seeing that getting this working isn't as trivial as swapping a few files. I've been asking on some Freenode channels about what exactly makes a kernel 'CyanogenMod compatible.' There are clearly people out there who know exactly what facilities and stuff need to be backported, but such people are hard to find. Do you have any idea where this kind of stuff is documented? The CyanogenMod wiki seems a bit sparse, although maybe I haven't been looking in the right places...
If it is of any interest to anyone:
http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel.html
I've recompiled U-Boot to call our current N2E kernel with a new `console=[...]` parameter, and recompiled the kernel with USB serial support. I figure I should be able to plug this thing into a linux box and just use `minicom` to look at the kernel's output in this manner. I know this probably won't give too much information about userspace issues but at least hopefully it will give some info on why/if/when/where init fails.
It would be nice if a spare UART could be found directly on the board.
http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel.html said:
The USB subsystem is started rather late in the boot process, console messages printed during boot before the USB subsystem is loaded will be lost.
Click to expand...
Click to collapse
I should be more specific, it's not so much you need to make the current kernel CM7 compatible, as it is you need to make it Android Froyo Compatible, which usually involves porting features from the eclair, if you want to get specifics, try talking with people in #nookcolor or #nook-tablet on Freenode. They may be able to help point you in the right directions for porting the kernel.
Waiting for my NST to come from new continent.
Personally, I would start building original kernel source from b&n. When it works and device boots, then I would clone google repository for kernel 2.6.x and would compare its files with the files from original kernel. And then adding needed source files for booting, and needed device drivers.
I doubt I'll have free time and enough knowledge for that.
Sent from my GT-I9000 using XDA
seeing as we now have the uart http://forum.xda-developers.com/showthread.php?t=1702734 i feel its time to make a cm7 port. it would unlimit the device, and bring it into more compatible apps.
How goes it? Will fundraising speed things up by letting you concentrate more of your time on this project?
imachine said:
How goes it? Will fundraising speed things up by letting you concentrate more of your time on this project?
Click to expand...
Click to collapse
Sorry if you weren't asking me.
I don't write a single line of C code since almost twelve years. I'm a programmer in a very different environment, fact which makes me know that such a port needs a lot of dedication.
In the next weeks I'm gonna be father for the first time and this makes me set completely different goals in my life.
As far as I've understood of cyanogenmod, is that this world is made of brilliant volunteers, some accepting donations, some not. Maybe in the whole cm community, there is somebody with time and experience.
Sent from my GT-I9000 using XDA
I've been considering picking this up as a project, because I'm tired of 2.1, i would like some GB at least I doubt we will see cm9, but cm7 seems doable. I'll have to learn some to do it, but I don't see why it's not outside of reach; now that we have a serial port, and such.
tdcfpp said:
Sorry if you weren't asking me.
Click to expand...
Click to collapse
No problemas, I wasn't. I directed my message at klausef who started this thread, though anyone willing to help out would probably be beneficient from fundraising, were it to start funding a project, instead of a single developer.
If money's a problem, perhaphs starting a kickstarter (or similar) project might help out?
Donating via paypal works as well, but I don't think it's possible to allow public access to account levels in order to motivate the experience of funding, by letting people see how much the project has risen.
i can't wait to get CyanogenMod on my nook! Have you guys discovered anything new?
Cheers!
Soooo, any news? Come on, klausef, we can help! Let us know how the progress is coming along
imachine said:
Soooo, any news? Come on, klausef, we can help! Let us know how the progress is coming along
Click to expand...
Click to collapse
Bump. I've got a great use for a NST / N2E application, and the app is currently compiled for Android 2.2 only. I may not be able to get to the source (and may not be able to make it work in 2.1 even if I did!), so a NST with 2.2 would be ideal!
Okay so there are two multi-boot modifications flowing around XDA for a ton of various devices.. Has anyone ever considered porting one to the robin? lately with all these rock solid Roms it doesn't seem like too bad of an idea and I truly wish I had the experience to do it myself.
https://github.com/chenxiaolong/DualBootPatcher/
and
https://github.com/Tasssadar/multirom
and
https://github.com/efidroid/
Oh hell yes! I'd like to see this!
Desperately waiting for it!
Sounds cool, I can have Omni and XOSP at the same time ;P
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
If you ask me, the lack of the need of the kexec-hardboot patch makes this project superior to multirom
Alexandroid99 said:
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
If you ask me, the lack of the need of the kexec-hardboot patch makes this project superior to multirom
Click to expand...
Click to collapse
I'm taking a look at it and i'm gonna mess around with it and hopefully make an attempt to port it.. Hope all goes well
AnierinB said:
I'm taking a look at it and i'm gonna mess around with it and hopefully make an attempt to port it.. Hope all goes well
Click to expand...
Click to collapse
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
Yeah but unfortunately for me repo is giving me a ton of problems and i've got to get to work. if someone else wants to try this, be my guest.
AnierinB said:
Yeah but unfortunately for me repo is giving me a ton of problems and i've got to get to work. if someone else wants to try this, be my guest.
Click to expand...
Click to collapse
I'm already syncing it. Someone got it to work partially on the Nexus 5X, which is the same arch. So fingers crossed...
Alexandroid99 said:
I'm already syncing it. Someone got it to work partially on the Nexus 5X, which is the same arch. So fingers crossed...
Click to expand...
Click to collapse
Let me know how it goes man :highfive:
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
No dice. Tried to compile lk using msm8994 (SD810- same workaround as 5x) and was able to fastboot boot a nouefi lk.img but but once booted there was no device showing up in fastboot devices which unfortunately is key to the next step
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
valhallen.282 said:
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
Click to expand...
Click to collapse
I got lk to boot using the same lk_base as the 5x so there are a few thing in common because the aboot dump showed the same value. anyways I made some progress: Display to show, finalize_device to execute and was able to build uefi.img and boot it. upon booting uefi the kernel panics and reboots so I have to to figure that out before proceeding to the checklist.
valhallen.282 said:
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
Click to expand...
Click to collapse
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
I've got it to boot and run for the most part but I'm not the most experienced at porting and there are a few things left to do like configuring the fstab.multiboot correctly which is key to multi booting roms and installing the ota through efidroid app via github sever
AnierinB said:
So I've got efi-droid ported and working for the most part. I'm not the most experienced at porting and there are a few things left to do like testing multiboot roms and configuring a local ota sever to do so..
I'm making this post so that I can hand off my findings, config.ini, and my lk_inc.make to someone who has more experience/ someone who can get this done and wants to test multiboot and see if it's a go. Think you can do so and become the maintainer for this project?
Click to expand...
Click to collapse
I wish I was smart enough to do that. I can read code. I can test. Cannot write to save my life. Sorry. That's my truth.
valhallen.282 said:
I wish I was smart enough to do that. I can read code. I can test. Cannot write to save my life. Sorry. That's my truth.
Click to expand...
Click to collapse
As soon as I get these local ota server problems figured out and are able to actually test dual booting a rom I'll pm you with some goodies:good:
It's pretty easy to build yourself after you figure out what variables the lk.mk and config.ini need. Although I have been doing this for 3 days now with many trial and error. Pretty shocked it's even working as good as it is right now because there's been a lot of known issues with 64bit socs
delete
I'm gonna have to put this project behind me... I lack some knowledge on a few areas of the porting process and to configure it correctly is possible but I, myself can not do it. If a developer has the device, and wants to try porting/configuring it then go for it. The main thing is that we are able to get lk, uefi to boot and display screen (properly) so fixing the other issues like fstab.multiboot table should be easy for someone more experienced. At least theres hope with this modification. Sorry folks, I'll stick to my boot logos for now haha.
AnierinB said:
@ValHallen can you download the efi manager application off the play store and tell me what device it gives you an error for? then after doing so can you edit your build prop and add this line: efidroid.server_url=https://raw.githubusercontent.com/anierinbliss/efidroid_ota/master
then delete the app, reboot your phone and reinstall it.. Does it still fail?
Click to expand...
Click to collapse
I think you tagged the wrong person. But I'll try. In a short while.
It's probably best to put all thaz work out in the open including github repos and a separate thread so someone who's capable might stumble upon it and pick up qhere you left off.