Related
A new release is ready the final Degu.
For both gen7/8 you will need to flash the latest zImage and initramfs included in the download links. <-- not needed if you already have flashed the latest with Crow. no changes in kernel or initramfs for Degu release.
Also to be sure you will need to delete your data.img and let it create a new one or copy your own if you use an image more then 256mb.
For setting up your device look here http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread
Links updated crow release 27-01-2013
For gen7:
http://www.openaos.org/wp-upload/gen7/2013-01-27/
For gen8:
http://www.openaos.org/wp-upload/gen8/2013-01-27/
If you have any issus post them by creating a new ticket see http://dev.openaos.org/wiki/IssueTracking on howto.
Known issues are here: http://dev.openaos.org/wiki/AndroidTicketsFor2.3
If it works well or you have issues you can also leave a reply.
BTW camera should partly work on gen8, tested on a 101IT taking photos. Video recording will freeze the app. Not tested with apps that use the cam only with the included camera app.
A43IT has a different camera, so I don't know if it will work.
Thanks,
divx118
Usefull links for setting up the devices:
Gen7 devices: http://dev.openaos.org/wiki/SettingUpMultiRootGen7
Gen8 devices: http://dev.openaos.org/wiki/SettingUpMultiRootGen8
General info: http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread
Building your own image: http://dev.openaos.org/wiki/AndroidBuildEnvironment
Degu final (27-01-2013)
------------------------------------------------------------------------------------------------------------------------------------
Changelog:
- Smoother youtube video playback for gen8
- More apps in the market available for gen7 and gen8 (also thanks to utopik for this)
- Internal storage should now properly display free available memory for gen7 and gen8
- Fixed bookmark for gapps in the browser for gen7 and gen8
- Overal speed improvement.
Unfortunately you will need a fresh data.img to let these fixes take effect.
Crow final (25-12-2012)
------------------------------------------------------------------------------------------------------------------------------------
First don't forget to flash he new zImage (kernel) and initramfs it is in the archive kernel_gen7_20120512_114451.tar.gz for gen7 and kernel_gen8_20120409_002900.tar.gz for gen8 unpack it (with winrar if you are on windows) and only use "zImage" and "initramfs.cpio.gz"
Changelog see http://www.openaos.org/archives/821
Bull final (09-04-2012)
------------------------------------------------------------------------------------------------------------------------------------
First don't forget to flash he new zImage (kernel) and initramfs it is in the archive kernel_gen7_20120512_114451.tar.gz for gen7 and kernel_gen8_20120409_002900.tar.gz for gen8 unpack it (with winrar if you are on windows) and only use "zImage" and "initramfs.cpio.gz"
Only for gen7: If you flash the new kernel and initramfs also delete the old menu.lst when it is there. If you have custom lines in there add them later after you first booted in the new menu.lst that is created.
Only for gen8: If you first boot the image it happens sometimes that omap_vout isn't loaded correctly this means it can't create the overlay for playback video and uses the software renderer. If you just reboot it is ok. It only happens atleast to me on the very first boot.
Some improvements first the kernel and initramfs:
- Correct orientation of the bootmenu for A101IT
- Updated the kernel with latest archos GPL release which means that the ones with broken USB host on their A101IT it gets working again when booting stock through the bootmenu.
- For gen7 updated initramfs to match the one from gen8
- Added unionfs support, so you can have root with rw access on stock android.
Improvements on Gingerbread:
- smoother camera because of using the overlay to display the stream. Known issues: - display is cropped so you don't see the whole camera - Recording still doesn't work.
- Youtube app works.
- Hardware accelerated video for atleast youtube app and some mp4 files, maybe more if someone can test some different formats that would be nice. Rotation does work for youtube app, there are still some issues when rotating playing a regular mp4.
- On gen8 you can also play hw accelerated flash videos in the browser now, of course not all pages will work.
- wifi location should work now. <-- same for gen7
- Fix not enough storage when installing apps by moving /cache also to the data.img. <-- same for gen7
- Update to latest CM code. <-- same for gen7
RC2 (24-12-2011)
------------------------------------------------------------------------------------------------------------------------------------
This will be the final Bull release or there must be some major bugs discovered in the next few days.
There is now a new feature added (thanks to illifant). The data is now in a separate image "data.img" if it is not there it will be auto created. 256 MB is standard. You can replace it with a bigger one from the download link gen8_data.img.tar.bz2.
If you unpack with for example winrar you see three images 256MB, 512MB, 1024MB just pick a size and copy that to the root of your archos. Rename it to "data.img"
As mentioned you don't have todo this if you want to use 256MB that will be created automaticly.
All your data, apps and gapps are in data.img. So on a next upgrade you won't have to reinstall everything again.
Also the size of the actual image is reduced, for gen7 it is 180MB and for gen8 256MB.
Don't forget to flash the new zImage (kernel) and initramfs it is in kernel_gen7_20111224_181411.tar.bz2 for gen7 and kernel_gen8_20111224_213037.tar.gz for gen8 unpack it with winrar and only use "zImage" and "initramfs.cpio.gz"
(if not specified otherwise the fixes are for gen7 and gen8)
Gingerbread Image:
- Deep sleep improved, however to work properly keep adb disabled. (it is now disabled by default.)
- Charging A43 for USB and wall charger is fixed (gen8)
- External sd-card is now mounted on /mnt/storage/sdcard (same as on archos firmware).
- Updated with latest CM code.
- New modules from updated kernel build (gen8)
- Other small fixes see the closed tickets.
zImage and initramfs.cpio.gz:
- Initramfs script updated, if it fails it will now display an error message instead of just rebooting.
- Kernel updated to latest archos firmware (2.4.81) kernel (gen8)
RC1 (06-11-2011)
------------------------------------------------------------------------------------------------------------------------------------
Somethings that are changed since anoa release:
(if not specified otherwise the fixes are for gen7 and gen8)
- Fixed headphone speaker switch
- partly camera working for atleast A101IT I think also A70, don't know for A43IT because it has a different cam. (gen8)
- Fixed permission errors when using ext3 formatted internal memory
- Fixed some browser crashes. Due to using v8 javascript engine again instead of jsc
- Fixed crash when going to browser settings
- Fixed deep sleep which should be working now.
- Fixed mounting/unmounting external sdcard.
- Calibration app included for A32 and A43. (Under settings)
- Updated to latest CM code
- Kernel updated to latest sources from archos firmware 2.4.65
- Fixed correct rotation for A101, only bootmenu is still upsidedown.
- GPS working for gen7 devices
- some other small things
Tips:
1) Playing youtube videos on CM fail with standard player http://pastebin.com/YAZc0z74 , but can be done with mobo player or mx player by using for example opera mobile and setting the user agent to desktop.
i'll give it a try now
The Bootmenu doesn't start. It hangs on the first Archos Screen (before OpenAOS).
It don't creates the menu.lst file also.
(Archos 101 G8)
airwolf1544 said:
The Bootmenu doesn't start. It hangs on the first Archos Screen (before OpenAOS).
It don't creates the menu.lst file also.
(Archos 101 G8)
Click to expand...
Click to collapse
I'm having the same issue.
(Archos 70 8GB)
airwolf1544 said:
The Bootmenu doesn't start. It hangs on the first Archos Screen (before OpenAOS).
It don't creates the menu.lst file also.
(Archos 101 G8)
Click to expand...
Click to collapse
You are right, something went wrong with the upload of the zImage, if you check md5sum it is wrong. I will post when it is fixed. Should be soon.
divx118
EDIT: zImage is fixed now if you already downloaded it just redownload
hey - great to hear about further development - sadly the gen8 links seems to be down ...
www.openaos.org/wp-upload/gen8/2011-11-06/ReleaseCandidate_UNSUPPORTED/
Error: Connection interrrupted
Perrhaps just partial - will try again later
EDIT: working now again
After choosing "Gingerbread-Entry" in Aos-Menu my 101 shortly shows the "openaos"- Bootlogo and then reboots in Archos-Standard.
What is wrong?? I used all files from the Link mentioned above.
Any ideas?
P.S: Reload of the files is not possible because it seems like openaos.org is down ;-(
We are having some issues with dev.openaos.org which will hopefully soon be solved.
The problem you have is a corrupted zImage. It should be fine now once you can redownload it.
Sorry for the inconvenience,
divx118
EDIT: wrote too soon, seems the links are accessible again
Hubelbert said:
After choosing "Gingerbread-Entry" in Aos-Menu my 101 shortly shows the "openaos"- Bootlogo and then reboots in Archos-Standard.
What is wrong?? I used all files from the Link mentioned above.
Any ideas?
P.S: Reload of the files is not possible because it seems like openaos.org is down ;-(
Click to expand...
Click to collapse
Is the name right? openaos-gingerbread.img.gz
airwolf1544 said:
Is the name right? openaos-gingerbread.img.gz
Click to expand...
Click to collapse
Yes that should be correct, just tested it myself. Just deleted my image, menu.lst flashed the initramfs and kernel and booted.
divx118
Oops sorry, need some more coffee this morning it was meant for Hubelbert.
Nice work..
Bugger - I sholdn't have installed UrukDroid yesterday (I read you can add Uruk to Mulitiboot, but what if its already installed?)
Whats the fixes/updates with this release please, or is it on the site?
SWFlyerUK said:
Bugger - I sholdn't have installed UrukDroid yesterday
Whats the fixes/updates with this release please, or is it on the site?
Click to expand...
Click to collapse
- Fixed headphone speaker switch
- partly camera working for atleast A101IT I think also A70, don't know for A43IT because it has a different cam.
- Fixed permission errors when using ext3 formatted internal memory
- Fixed some browser crashes. Due to using v8 javascript engine again instead of jsc
- Fixed crash when going to browser settings
- Fixed deep sleep which should be working now.
- Fixed mounting/unmounting external sdcard.
- Calibration app included for A32 and A43. (Under settings)
- Updated to latest CM code
- Kernel updated to latest sources from archos firmware 2.4.65
- some other small things
divx118
hey divx - do we have any working way of dualboot urukdroid and Cyanogen?
For me this is the major reason for less contribution on openAOS - as i need a working stable device for dialy use - but also really want to help u with cyanogen...
Searched for it some time ago already but due to the different kernels this was really hard to figure out...
anyway will try yours again now and check out the new release
FrEcP said:
hey divx - do we have any working way of dualboot urukdroid and Cyanogen?
For me this is the major reason for less contribution on openAOS - as i need a working stable device for dialy use - but also really want to help u with cyanogen...
Searched for it some time ago already but due to the different kernels this was really hard to figure out...
anyway will try yours again now and check out the new release
Click to expand...
Click to collapse
Unfortunately not, maybe in the future when we can boot different kernels. We just follow the archos kernel sources with some minor additions to also allow booting of other linux distros. We want however always be able to boot stock android with our kernel which gives you btw root access, because of using unionfs.
I don't know how much difference there is between the urukdroid kernel and ours never looked at it.
divx118
So far it is running smooth. Great job guys.
I noticed 3 things so far.
1) my speakers make a "pop" sound when the device goes into and comes out of sleep. They also did that in Anoa.
2) I can swipe between the different home screens OK, but if I try to use the desktop dots next to the dock then ADW force closes.
3) Camera worked great the first time, then the second time I went back in it, it is green and gray colored. Tried changing the color effect settings of the camera and it looks the same every time. Rebooting fixed the greenish look and I have been in it multiple times now and it is staying normal so not sure what caused it the first time.
marcusmarcus said:
So far it is running smooth. Great job guys.
I noticed 3 things so far.
1) my speakers make a "pop" sound when the device goes into and comes out of sleep. They also did that in Anoa.
2) I can swipe between the different home screens OK, but if I try to use the desktop dots next to the dock then ADW force closes.
3) Camera worked great the first time, then the second time I went back in it, it is green and gray colored. Tried changing the color effect settings of the camera and it looks the same every time. Rebooting fixed the greenish look and I have been in it multiple times now and it is staying normal so not sure what caused it the first time.
Click to expand...
Click to collapse
1) Yes I noticed that too, I will see if I can poke one of the archos guys to know what is causing this issue.
2) Yes, it is a known issue. If you go into ADWlauncher settings the dots will disappear. I know what is causing the problem just need some time to create a proper fix.
3) Never had this on the 101. What kind of device do you have? A101 A70 or A43
Thanks for reporting back,
divx118
BTW there are still some problems accessing dev.openaos.org if the downloadlink doesn't work try again later.
divx118 said:
1) Yes I noticed that too, I will see if I can poke one of the archos guys to know what is causing this issue.
2) Yes, it is a known issue. If you go into ADWlauncher settings the dots will disappear. I know what is causing the problem just need some time to create a proper fix.
3) Never had this on the 101. What kind of device do you have? A101 A70 or A43
Thanks for reporting back,
divx118
BTW there are still some problems accessing dev.openaos.org if the downloadlink doesn't work try again later.
Click to expand...
Click to collapse
1) I was incorrect about my speakers popping in Anoa, they crackled in that, so the pop I think is an improvement
2) that's good news. I don't use the dots as I prefer to swipe, I just accidentally click one and that is how I found out.
3)I have an A70 8GB. I'm not sure what would have caused it, I have not been able to reproduce it since rebooting the device.
marcusmarcus said:
3)I have an A70 8GB. I'm not sure what would have caused it, I have not been able to reproduce it since rebooting the device.
Click to expand...
Click to collapse
Good to know it works on the A70, it wasn't tested yet.
divx118
You are right. I forgot a 'dot' between img and gz
Now everything is fine and it works very smooth. Seems even smoother than Urukdroid.
Great job. I continue testing.
This is not a thread to say ‘thanks’ to developers. Only post here if you have some input in this development progress, by either fixing bugs, or coming up with ideas (and ideally, try your idea and report what happens).
Having that said, let’s move on to where we are at the moment. Currently, we have a build which is based upon Ice Cold Sandwich 6.2 Test Edition for the HTC Desire HD. This build boots up by flashing my custom kernel on it, based on Flyer HC Original Kernel Source, with some patches:
-Quota2 Support
-Genlock Support
-Updated KGSL driver by applying Lord Clockans patches from his kernel
The ZIP we are working on now, can be downloaded here:http://w728685.open.ge.tt/1/files/9iI3CbF/0/blob?download
This ZIP contains a build which is mainly Lord Clockans ICS, with essential changes in the ROM to get it booting (we used LeeDroid’s Flyer HC as the donor ROM). This ROM is made for a HoneyComb HBOOT!
After you have flashed that ZIP, this is the kernel you need: http://ge.tt/9iI3CbF/v/1
You MUST flash this kernel to get it up and running, or it’ll just loop in the logcat complaining about unsupported stuff.
This set should do the following:
-Boot up (bootanimation resets after some time, it’s ok, it will boot within 5 minutes).
-Touchscreen works after you did this: open ADB Shell (by entering ‘adb shell’ on your pc,), and send the command “echo ‘1’> /sys/android_touch/event_google”. Now touchscreen should be working. (For some reason the file 90flyerhacks in /system/etc/init.d doesn’t do its job. If anyone has a clue > say so!) Also, the ntrig.c file in /drivers/input/touchscreen/ is modified in the kernel, don’t know if it helped though.
-Full Hardware Accceleration
-Screen is bugged at certain moments (seems to happen especially during things concering wallpapers. Rendering a wallpaper, showing a heavy LWP, etc.). The build.prop file contains some lines such as:
ro.fb.mode=1
debug.composition.type=gpu/mdp
debug.fb.rgb565=0
Perhaps we have to change these lines to get it running without issues (strange thing is, logcat doesn’t seem to make an issue about this). We can also try a recompile of the kernel using the entire driver folder from Lord Clockans kernel (it’s in /drivers/gpu/msm/ in his kernel, and /drivers/video/msm/gpu/kgsl_adreno205_hc in ours, moving the folder to where it should be causes issues, so we keep it like this for the time being).
-Sound is working
-Backcamera seems to be working fine, haven’t tested frontcamera.
-Hardware buttons under the screen aren’t working, and this should be a low
priority for now. It isn’t ideal to use them in ICS anyway (different button functions in comparison with the softbuttons), and I think we shouldn’t focus on this for now.
-GPS switch can be enabled, haven’t tested whether it works.
-Bluetooth switch can be enabled, but turns off automatically after about ten seconds.
-WiFi switch can’t be changed, logcat tells us that it can’t connect with /dev/rfkill, applying this patch in the ramdisk could fix it:
https://github.com/OpenSensation/an...mmit/da09360d70888a7e126871ab2ae5b218514cad18
-Power button and Volume buttons work fine.
-Pen works after we send the event_google command mentioned before.
If the ROM immediately reboots within 10 seconds and it seems like it’s looping, and you can’t even logcat, hold down Power and Volume Down until you get to HBOOT, select FASTBOOT, and enter ‘fastboot erase cache’ in the CMD/Terminal, and reboot, and it should work.
And that’s about it for the current things we know I think. If you manage to fix something, please write down and report what you did to fix it, so we can keep a list. I will work on a vendor folder using the known information, so we can compile a ROM from source, made for our device.
And last, but not least: don’t post here asking for release dates. We will do our utmost best to bring ICS experience to the Flyer, but do not bug us. Thanks.
Now let’s get this up and running guys! I will keep a log of what is fixed and what is not, so we can keep the thread organized. Else we’ll have 50 ZIPs around, not knowing which one is the right one et cetera.
Source code of kernel: http://github.com/Chaosz-X
Ramdisk will be uploaded tomorrow.
Donations are much appreciated, as I'm developing and building atm on a 1.67GHz Dual core...
Donations can me made to [email protected] using Paypal.
i suggest creating two repos... one for ROM and one for kernel... that way single file changes can be tracked even on ROM front, not just kernel...
willing devs can fork those repo and send pull requests to main repo when they get stuff working
I'm not a developer, and I have nothing but love for all the great devs that worked so hard to bring ICS to the Flyer.
Might I suggest, however, that instead of pursuing CM9 builds, the next effort be centered around porting the Android Open Kang Project (AOKP) ROM? In terms of features and customizations, it's considerably ahead of CM9, with numerous supported devices to boot.
I think this ROM, versus CM9, would give users the most flexible and dynamic ICS experience for their Flyer.
Chaosz-X said:
-Touchscreen works after you did this: open ADB Shell (by entering ‘adb shell’ on your pc,), and send the command “echo ‘1’> /sys/android_touch/event_google”. Now touchscreen should be working. (For some reason the file 90flyerhacks in /system/etc/init.d doesn’t do its job. If anyone has a clue > say so!)
Click to expand...
Click to collapse
Does it work if you add
write /sys/android_touch/event_google 1
to the init.rc file?
Could you post the init.rc file where you trigger the init.d scripts?
nickiberli said:
Does it work if you add
write /sys/android_touch/event_google 1
to the init.rc file?
Could you post the init.rc file where you trigger the init.d scripts?
Click to expand...
Click to collapse
yes that should work correctly
No, I didn't add that. I'll try it tomorrow (or one of you, if you have a Linux machine ready. Laptop with Ubuntu is having some issues atm, can fix it tomorrow).
So, assuming that's working, let's get to the display. We know that it causes issues, but how?
-Logcat doesn't error (except for HtcEbdLog, saying something about rotation, which seems to happen when glitches occur. Perhaps we need to swap the files?)
-At the very beginning, it does tell that initOverlay failed. This overlay-thing is baked in the ROM, and can be disabled in the ROM itself by setting an option to 'false' in the vendor setup. We don't know if it fixes the issue, but since the attempts to add this functionality to the kernel failed, it could be a better idea to fix it in the ROM to get rid of the error.
Any other suggestions?
Edit: and before I forget, tomorrow I'll check the ZIP for what is changed in comparison with the ROM it is based upon, so we know what we have to add in to a new build too.
Chaosz-X said:
No, I didn't add that. I'll try it tomorrow (or one of you, if you have a Linux machine ready. Laptop with Ubuntu is having some issues atm, can fix it tomorrow).
So, assuming that's working, let's get to the display. We know that it causes issues, but how?
-Logcat doesn't error (except for HtcEbdLog, saying something about rotation, which seems to happen when glitches occur. Perhaps we need to swap the files?)
-At the very beginning, it does tell that initOverlay failed. This overlay-thing is baked in the ROM, and can be disabled in the ROM itself by setting an option to 'false' in the vendor setup. We don't know if it fixes the issue, but since the attempts to add this functionality to the kernel failed, it could be a better idea to fix it in the ROM to get rid of the error.
Any other suggestions?
Edit: and before I forget, tomorrow I'll check the ZIP for what is changed in comparison with the ROM it is based upon, so we know what we have to add in to a new build too.
Click to expand...
Click to collapse
u want me to add stuff to that ramdisk?
start a github repo for the ramdisk and ROM too... trust me... its VERY helpful...
I'll start installing Ubuntu within 30 minutes, and will add everything to a GitHub by tonight within about 3 hours I think.
Chaosz-X said:
I'll start installing Ubuntu within 30 minutes, and will add everything to a GitHub by tonight within about 3 hours I think.
Click to expand...
Click to collapse
thats great... it should make keeping track of changes much easier and other interested devs can contribute if they want...
Hello, all.
Attempting to help by working on the build.prop settings. I'm S-OFF with revolutionary and have my device fully configured with the Honeycomb HBOOT/radio/bootloader/etc.
After flashing the ROM and the kernel, the device would immediately reboot upon attempting to return to the main recovery menu. I had to fastboot oem rebootRUU and reflash Globatron's PG41IMG-WIFI-light-B10 zip to get recovery back.
The device never proceeded to the boot animation.
Thracks said:
Hello, all.
Attempting to help by working on the build.prop settings. I'm S-OFF with revolutionary and have my device fully configured with the Honeycomb HBOOT/radio/bootloader/etc.
After flashing the ROM and the kernel, the device would immediately reboot upon attempting to return to the main recovery menu. I had to fastboot oem rebootRUU and reflash Globatron's PG41IMG-WIFI-light-B10 zip to get recovery back.
The device never proceeded to the boot animation.
Click to expand...
Click to collapse
I can confirm this happened to me also. The only difference is that I was using the kernel for a port of mine, and it did the same thing.
Yes, it is known that for some reason, Go Back already reboots the device. It's no problem though, it works fine anyway. If it is really looping the bootanimation every ten seconds, keep Vol Down and Power pressed, until you get to HBOOT. Select FASTBOOT, and enter 'fastboot erase cache' in the terminal. Then reboot on the device, and it should boot up fine.
Also, kernel won't work on Honeycomb, haven't checked why it doesn't though (and I won't btw, our goal is not to make a new kernel for Honeycomb, but for ICS, where it does its job fine).
Kernel source is uploaded to my Github: http://github.com/Chaosz-X
Edit the CROSS_COMPILE for your toolchain, and it should compile fine (it does here).
Will add the link to the OP within 5 minutes, ramdisk will be uploaded tomorrow.
If chaos has a device tree set up for the Flyer/View, no build prop editing should be necessary, can just submit requests - but I don't notice it on the git.
Thanks for uploading, I'll have a look and see what has changed so far. It's a little difficult to keep track of the changes since there are no commits that document the patches applied over time, but I'll try to make do with what you've got.
Is this straight from flyer HC kernel source?
I may be doing this wrong, but the touch screen commands do not seem to be working for me
Cimer said:
I may be doing this wrong, but the touch screen commands do not seem to be working for me
Click to expand...
Click to collapse
You have to type it in manually. Copying and pasting does not work, at least it did not for me. I think the issue is with the '
lawguy said:
You have to type it in manually. Copying and pasting does not work, at least it did not for me. I think the issue is with the '
Click to expand...
Click to collapse
It may just be me, I tried manual too. I had to use http://forum.xda-developers.com/showthread.php?t=1379875 since I'm stuck on Windows 8..maybe something is up with that. I guess I will just need to sit and wait =/
Cimer said:
It may just be me, I tried manual too. I had to use http://forum.xda-developers.com/showthread.php?t=1379875 since I'm stuck on Windows 8..maybe something is up with that. I guess I will just need to sit and wait =/
Click to expand...
Click to collapse
Hang tight for now. Wifi Does not work and the screen freaks out. I'm sure that these things will be fixed soon.
Going to upload ramdisk source within an hour, and try to apply a fix for WiFi, and try to fix the touchscreen by using the command in init.rc mentioned here earlier.
The new modem arrived, I have Internet again, so we have remote access to our Linux machine and can start compiling etc again
Indeed, we're grabbing AOKP source code now. Within about 2 hours we think, we'll start compiling the ROM for the HTC Flyer. Don't know if it will work out, but we have to start somewhere
Finally we get CWM Recovery for Dell Strek Pro.
[StreakPro][Recovery][Beta]Clockwork Mod 6.0.1.1
http://forum.xda-developers.com/showthread.php?p=29847686#post29847686
This CWM made by manii
and I am a tester (because SPro launch only in Japan)
I already asked to Cyanogen mod and AOKP.
But Kang said "we don't support dell" and Cyanogen mod no answer
I'm looking for custom rom developers.
Please help me
Regards.
Sent from my GS01 using xda premium
Help
Anyone figured out how to enter into recovery mode of dell GS01?:crying:
hatoo said:
Finally we get CWM Recovery for Dell Strek Pro.
[StreakPro][Recovery][Beta]Clockwork Mod 6.0.1.1
http://forum.xda-developers.com/showthread.php?p=29847686#post29847686
This CWM made by manii
and I am a tester (because SPro launch only in Japan)
I already asked to Cyanogen mod and AOKP.
But Kang said "we don't support dell" and Cyanogen mod no answer
I'm looking for custom rom developers.
Please help me
Regards.
Sent from my GS01 using xda premium
Click to expand...
Click to collapse
It's in the works. CM10.1 compiles just fine, but i'm getting bootloops due lack of ion support in 2.6 kernel. I've managed to (mostly) port spro-specific things to CodeAurora's 3.4 kernel and fixed all compilation errors, but spro's device configuration routine is sort of different from vanilla msm8260 (some things are being configured by aboot, yet it's performing some checks that are unclear to me at the moment). Currently kernel fails to boot and device is getting into the blink-camera's flash-and-switch-screen-off mode (same mode device gets when it's turned on with volume-up+volume-down keys).
Oh, and by the way: i've tried to contact both Compal (odm and actual kernel developer for spro) and Dell to get information about what kernel was used in that unreleased 062-world wide dell rom. Compal's mailserver refused to deliver my message, and Dell's opensource departament people responded only once askung if i seek information on 2.6 kernel. I've re-stated that i'm seeking information on 062 rom and 3.x kernel - no word from them since then
So, we're up to ourselves with this one. If anyone's capable and willing to help with resolving 3.4 kernel boot issues - drop a line into this thread - i'll upload my current kernel tree to github.
---------- Post added at 10:03 PM ---------- Previous post was at 09:59 PM ----------
Anyone figured out how to enter into recovery mode of dell GS01?:crying:
Click to expand...
Click to collapse
Power+volume up+home if i recall it correctly. Another way is to issue
Code:
fastboot boot your-recovery-image-name.img
while in fastboot mode.
For those who it may concern
Here's a list of my SPro-related repos (in order of appearance):
2.6 kernel - original dell sources bumped to .14 along with other additions. should be suitable for ics-based roms.
caf-3.4 kernel - my current point of interest.
device/dell/msm8660-common and device/dell/streakpro - device source trees for cyanogenmod 10.1, both based on htc pyramid device trees.
While I've never had a SPro, good luck with it.
Awesome!
I use GS01 as my main device, so I'm looking forward to your custom ROM!
Sort of update.
Dell responded:
I apologize for the delay. I have learned that we did not update to 3.x. I think you may have the latest versions. Thank you for your inquiry.
Click to expand...
Click to collapse
So, we're on our own. Great..
Request
Trying to figure if androidboot.serialno= is really unique per-device.
I would like to ask StreakPro owners to post output of their device's cat /proc/cmdline output here. Command should be issued as root user, so you'll need to install TheManii's Superuser.zip via cwm.
Thanks in advance.
Is this ok?
kibuuka said:
Trying to figure if androidboot.serialno= is really unique per-device.
I would like to ask StreakPro owners to post output of their device's cat /proc/cmdline output here. Command should be issued as root user, so you'll need to install TheManii's Superuser.zip via cwm.
Thanks in advance.
Click to expand...
Click to collapse
# cat /proc/cmdline
cat /proc/cmdline
console=ttyHSL0,115200,n8 androidboot.hardware=qcom androidboot.emmc=true androi
dboot.hw_id=5 androidboot.serialno=205108 androidboot.baseband=msm
hatoo said:
# cat /proc/cmdline
cat /proc/cmdline
console=ttyHSL0,115200,n8 androidboot.hardware=qcom androidboot.emmc=true androi
dboot.hw_id=5 androidboot.serialno=205108 androidboot.baseband=msm
Click to expand...
Click to collapse
Yep just what I needed, thanks hatoo.
kibuuka said:
Yep just what I needed, thanks hatoo.
Click to expand...
Click to collapse
Hi Kibuuka!
What about DS5 ICS development, are still working on it?
Regards...
Dell steak 5 can't enter fastboot and always restarting somebody help me pls
unlock
Not really the right thread to ask that, but not able to get into fastboot or not able to get into recovery?
Dell Streak Pro GS01 (E mobile)
Kindly requesting for help with my phone mentioned above,
i was looking for methods to root, i ran super one click and got my phone stuck on the E mobile logo,
i cannot find any support on the internet,
am so frustrated
shakes1883 said:
Kindly requesting for help with my phone mentioned above,
i was looking for methods to root, i ran super one click and got my phone stuck on the E mobile logo,
i cannot find any support on the internet,
am so frustrated
Click to expand...
Click to collapse
First of all - as a rule of thumb you're better NOT to use one-click solutions for anything - these ARE evil.
Let's think you don't want to/can't disassemble it.
You'll need:#1 drivers for Spro - grab it here, #2 fastboot and adb binaries - grab these, #3 one of the stock ROMs - TheManii did a great job collecting them - select one containing SPro in filename from here, #4 CWM recovery image - grab this one (courtesy of TheManii) and #5 - superuser flasheable package (by TheManii as well)
You have to wait until phone's battery is fully drained.
After that you need to connect it to pc. It will enter so called "charge-only state" (charging battery animation). Wait until it fully charges (LED will become green). Disconnect it from pc/power supply now.
Then you'll need to turn it on by pushing power button AND volume down at the same time to enter fastboot mode - screen will go black with two lines on it:
Code:
FATBOOT!!!!
Version 0.5
Connect your phone to pc - you'll see third line
Code:
USB cable connected
and windows will ask for drivers for device (if you don't have them installed already)
After drivers installation you're set to fix you problem.
Open command prompt and cd to a dir containing adb and fastboot binaries (let's assume full path is y:\adb\ and you have copied CWM image into this folder):
Code:
cd y:\adb\
Then boot (we don't flash it this time preserving your device's warranty ) into CMW recovery
Code:
fastboot boot y:\adb\SPro-6.0.1.2.img
You'll see good'ol CWM recovery screen. Navigate to "Mounts and storage", then select "mount USB storage". Your pc will now be able to access phone's internal and external storage. Now copy ROM image of choice and superuser package to either of phone's partitions you've connected to pc on previous step.
Select Unmount in CWM menu (AFTER you did a safe device removal in windows - thin precaution will save you some nerves).
Navigate to "install zip from sdcard", then to "choose zip from sdcard", select ROM image you've copied previously, select "Yes - Install update-zip-you-have-selected.zip"
CWM will install ROM image for you.
Now do the same selecting superuser package instead of ROM image and install it as well.
Select "reboot system now". If everything's ok you'll see your device booting into your newly installed ROM. If it doesn't - get to fastboot mode again, boot CMW image and do a factory reset using it ("wipe data/factory reset").
I'll just leave it here
Not creating separate thread for this, just teasing a bit .
http://www.mediafire.com/download/oje1t47k1ght15w/cm_streakpro-ota-3ead3941fd.zip
Summary: cyanogenmod-10.1 for StreakPro
NOT suitable for everyday use as of yet (mediaserver lockup bug is showstopper here), testing purposes only.
prerequisites:
baseband that is newer than 061 to get gsm voice working. (tested using baseband taken from MIL_2.0.12.0)
CWM recovery (to install it )
Working:
Boot
Speaker/wired headset/handset audio
Voice calls
Wifi
adb is enabled by default
3d seem to be working (gfxbench runs just as fine as on 061-World-Wide-Dell ROM)
Sensors (partially, there seem to be a problem with proximity sensor in phone app)
Hardware buttons (+button leds)
Touchscreen
Top LED (behaves differently, green while charging, blinks white on unread sms/email)
Battery stats (consumption measurement values are taken from similar device (htc pyramid) - if someone has access to real values for SPro - please share)
Buggy/not working at all:
Mobile data (known, working on fixing it)
Tethering (haven't touched it yet)
Bluetooth (haven't touched it yet)
UMS (internal/external SD are recognized and accesseable by apps, but pc mounting fails due to Settings segfault)
Camera (halfway there - cameras are being recognized by system/applications but currently we're unable to capture image. i'm working on it)
Mediaserver seem to be locking up boot process 9 times of 10. adb shell killall mediaserver will resume it.
You're encouraged to issue adb shell pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
to make mediascanner stop eating battery and cpu time like crazy.
No video in Youtube app. (haven't touched it yet)
Mute switch (low priority, got several options how to fix it, have to decide which is better)
bug reports aren't really needed, i'm aware of problems current build has and slowly (tbh - very slowly, shortage of spare time) progressing on those.
if someone's able/wishes to help fixing bugs - device tree and kernel are on my github.
kibuuka said:
Not creating separate thread for this, just teasing a bit .
http://www.mediafire.com/download/oje1t47k1ght15w/cm_streakpro-ota-3ead3941fd.zip
Summary: cyanogenmod-10.1 for StreakPro
NOT suitable for everyday use as of yet (mediaserver lockup bug is showstopper here), testing purposes only.
prerequisites:
baseband that is newer than 061 to get gsm voice working. (tested using baseband taken from MIL_2.0.12.0)
CWM recovery (to install it )
Working:
Boot
Speaker/wired headset/handset audio
Voice calls
Wifi
adb is enabled by default
3d seem to be working (gfxbench runs just as fine as on 061-World-Wide-Dell ROM)
Sensors (partially, there seem to be a problem with proximity sensor in phone app)
Hardware buttons (+button leds)
Touchscreen
Top LED (behaves differently, green while charging, blinks white on unread sms/email)
Battery stats (consumption measurement values are taken from similar device (htc pyramid) - if someone has access to real values for SPro - please share)
Buggy/not working at all:
Mobile data (known, working on fixing it)
Tethering (haven't touched it yet)
Bluetooth (haven't touched it yet)
UMS (internal/external SD are recognized and accesseable by apps, but pc mounting fails due to Settings segfault)
Camera (halfway there - cameras are being recognized by system/applications but currently we're unable to capture image. i'm working on it)
Mediaserver seem to be locking up boot process 9 times of 10. adb shell killall mediaserver will resume it.
You're encouraged to issue adb shell pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
to make mediascanner stop eating battery and cpu time like crazy.
No video in Youtube app. (haven't touched it yet)
Mute switch (low priority, got several options how to fix it, have to decide which is better)
bug reports aren't really needed, i'm aware of problems current build has and slowly (tbh - very slowly, shortage of spare time) progressing on those.
if someone's able/wishes to help fixing bugs - device tree and kernel are on my github.
Click to expand...
Click to collapse
WOW! AMAZING! Never expect Streak pro will have CM. Thank you so much for you work.
Finally!!
So nice ROM!!
I love you Kibu lol
Please Support Custom rom dell streak pro
I know many xda dev community is a good: Good:, the dell streak pro help you make a rom version 4.x so it works better : O
thanks!
- CPU: Qualcomm MSM8260A Snapdragon, 1.5 GHz Dual-Core Processor
- RAM: 1 GB Memory: 4 GB
- External Memory MicroSD (T-Flash) up to 32 GB
- Camera: 8.0 MP, support LED flash, autofocus
- Cinematography: FullHD 1080p @ 30fps
- Battery capacity: 1520 mAh
- Super AMOLED Plus display with 16 million colors Resolution giai540 x 960 pixels Size 4.3 inches
- OS: 2.3.5 Androi
are looking forward to the help of kibuuka well as helping people in xda
kibuuka said:
Not creating separate thread for this, just teasing a bit .
Summary: cyanogenmod-10.1 for StreakPro
NOT suitable for everyday use as of yet (mediaserver lockup bug is showstopper here), testing purposes only.
prerequisites:
baseband that is newer than 061 to get gsm voice working. (tested using baseband taken from MIL_2.0.12.0)
CWM recovery (to install it )
Working:
Boot
Speaker/wired headset/handset audio
Voice calls
Wifi
adb is enabled by default
3d seem to be working (gfxbench runs just as fine as on 061-World-Wide-Dell ROM)
Sensors (partially, there seem to be a problem with proximity sensor in phone app)
Hardware buttons (+button leds)
Touchscreen
Top LED (behaves differently, green while charging, blinks white on unread sms/email)
Battery stats (consumption measurement values are taken from similar device (htc pyramid) - if someone has access to real values for SPro - please share)
Buggy/not working at all:
Mobile data (known, working on fixing it)
Tethering (haven't touched it yet)
Bluetooth (haven't touched it yet)
UMS (internal/external SD are recognized and accesseable by apps, but pc mounting fails due to Settings segfault)
Camera (halfway there - cameras are being recognized by system/applications but currently we're unable to capture image. i'm working on it)
Mediaserver seem to be locking up boot process 9 times of 10. adb shell killall mediaserver will resume it.
You're encouraged to issue adb shell pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
to make mediascanner stop eating battery and cpu time like crazy.
No video in Youtube app. (haven't touched it yet)
Mute switch (low priority, got several options how to fix it, have to decide which is better)
bug reports aren't really needed, i'm aware of problems current build has and slowly (tbh - very slowly, shortage of spare time) progressing on those.
if someone's able/wishes to help fixing bugs - device tree and kernel are on my github.
Click to expand...
Click to collapse
hope you help fix bugs present in nodules rom, dell community treak pro users have been waiting for this day ever. thank you very much
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
AOSP+ 0.8 - Android 4.3
AOSP+ is a collaboration ROM from myself and Lloir. Lloir enjoys using pure vanilla AOSP whereas I have always enjoyed the features from CM or AOKP. After trying out AOSP I was impressed with its speed and smoothness and found I actually only missed a few small things from those other ROMs so decided to port over just those features. The result: AOSP+
For all the changes over AOSP, see the second post.
All code that is not built directly from the google repositories can be found on github here https://github.com/AospPlus/
3rd party apps included in the ROM:
Superuser by Koush
LockClock from CM - much as Lloir hates it, i quite like it so it's gone in
Torch from CM
ShareLogs from cornedor - we will provide NO support unless the logs from this app are included with your post!
We welcome suggestions of other things people like from other ROMs that you want included but we want to try and keep all changes as light as possible to stay as close to AOSP as we can. Also, feel free to add your own features and make pull requests to our repos to have them included.
Kernel
Source: https://github.com/AospPlus/android_kernel_htc_enrc2b-BLADE
The boot.img in the ROM is the BLADE kernel. This contains ramdisk changes required for 4.3 so must be flashed.
Downloads
ROM
GAPPS
Installation
Extract boot.img from ROM zip and install from bootloader
Code:
fastboot flash boot boot.img
A factory reset and system wipe is always recommended (use Titanium to backup/restore your apps and data) but may not be required. If you have issues, please try and recreate them after a factory reset/system wipe before reporting them.
Install ROM and GAPPS from recovery
Wipe cache/dalvik
Reboot.
Thanks to...
@Lloir for working with me to get 4.3 working
@maxwen for his BLADE kernel
@corne for his ShareLogs tool
CyanogenMod Team
XDA:DevDB Information
AOSP+ 4.3, a ROM for the HTC One X+
Contributors
tombriden, Lloir
ROM OS Version: 4.3.x Jellybean
Based On: AOSP
Version Information
Status: Testing
Created 2013-09-16
Last Updated 2013-10-28
Everything seems to be working except for...
Known Issues
Camera only at 5MP
MHL
SELinux is disabled
HD videos don't work
Video recording now works but freezes when you press stop
Some issues with calls over BT
Changelog
2013-10-28 - 0.9.0 - Experimental
Updated audio blobs to official enrc2b JB 4.2 blobs!!! (huge thanks to Thömy in the endeavoru forums for this one)
Back to a stock based kernel to work with new audio blobs, all BLADE features are now missing
Removed Advanced Settings menu as none of them are applicable to the current kernel
2013-10-14 - 0.8.9
Updated to AOSP 4.3.1_r1 (JLS36I)
Reverted KSM changes to see if that was the cause of random reboots
2013-09-20 - 0.8.8
Re-added T-Mobile theme engine
Re-added overlay to disable Nfc by default
Fixed bluetooth
Updated sources to AOSP 4.3_r3.1
No more Superuser countdown
2013-09-17 - 0.8.7
Fixed superuser daemon not starting from ramdisk
Enable KSM
Updated AOSP sources to 4.3_r3 (JLS36C)
2013-09-14 - 0.8.6
Fixed double tap home
Synced device tree with cm
2013-09-04 - 0.8.5
All other 4.2.2 libs that can be updated, now have been updated.
Synced up with the CM device repos to make my life easier when working on both
Fix for hardware decoding/encoding video (so HD videos and camcorder work (though now a different issue with recording))
SELinux now on in permissive mode
Fix audioflinger crash on receipt of notifications
2013-08-26 - 0.8.4
Update to android-4.3_r2.2 (JSS15Q)
Updated a whole bunch of blobs from 4.2.2 OTA
2013-08-19 - 0.8.3
Only override the picture-size-values if the string is actually broken (fixes issue with front camera resolutions also being overridden and so causing it to crash)
fix ramdisk issue that cause Torch to FC
2013-08-18 - 0.8.2
Modified camera wrapper to return picture-size-values from previous vendor lib as new one is >256 chars
2013-08-18 - 0.8.1
Back to using BLADE rom; still too early days for mine
Re-added Advanced Settings to control BLADE options
2013-08-17 - 0.8
New kernel based closely on HTC stock
Updated camera proprietary libs from latest HTC 4.2.2 dump
Option to map double-press on home
Existing AOSP+ features rebased on Android 4.3
Volume wake option
Disable safe headset warning
Hardware keys remapping option
Improved display of metadata on lock screen music widget
Green LED at 100% when charging, not 90
Reboot option
Swapped round the Wifi QuickTile press/longpress functionality (ie press to enable/disable, long press to go to settings)
Rearranged of the quick tiles to what I think is a better layout, with radio/network icons grouped together, ending with Airplane mode that disables them all
Integration of SuperUser into Settings
FAQ
Titanium Backup won't restore/backup apks
Open Preferences
Select Backup folder location
Press back until you get back to /
Select /sdcard
Press use current folder
Select 'No' when asked to move backup files
\o/ i suppose i better sort out PaP soon
Am I stupid or what, cause I see the EndeavorUParts.apk in the zip but no Advanced settings in the settings?
Oh yeh, I forgot to exclude it from the build. Normally you'd get to if from Settings but as the ROM doesn't come with BLADE it'd only confuse things to have it there as none of the options would work
Sent from my One X+ using Tapatalk 4
tombriden said:
Oh yeh, I forgot to exclude it from the build. Normally you'd get to if from Settings but as the ROM doesn't come with BLADE it'd only confuse things to have it there as none of the options would work
Sent from my One X+ using Tapatalk 4
Click to expand...
Click to collapse
Does the kernel have S2W support so I can activate it from an app on the market, and also should I flash the blade patched kernel after I flash the rom, cause I flashed it before and ended up with no signal at all, and then flashed the included kernel and everything works?
Ranomez said:
Does the kernel have S2W support so I can activate it from an app on the market, and also should I flash the blade patched kernel after I flash the rom, cause I flashed it before and ended up with no signal at all, and then flashed the included kernel and everything works?
Click to expand...
Click to collapse
No this doesn't have s2w, and i just realised that the script to copy the BLADE modules is in the ramdisk so won't be there once you've repacked it. What you can do though, is download this https://github.com/AospPlus/android.../aosp-plus_4.2.2-r1.1/scripts/01-module-check
then push to init.d while in recovery and make it executable
Code:
adb reboot recovery
adb shell mount /system
adb push 01-module-check /system/etc/init.d/
adb shell chmod 755 /system/etc/init.d/01-module-check
then flash blade and hopefully it'll work
failing that, it might be worth giving an existing blade-42 a try; i know it didn't work on open master (pre 4.3) but i don't think i've tried it on 4.3 itself
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Hi,
I just installed this ROM but I am having no sound
Is there a way to fix it?
Hmm, audio's working here; can you just try reflashing the kernel followed by
Code:
fastboot erase cache
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
In a call I get no sound if I try to switch to speackers, only normal calls working, also Viper4Android doesen't want to install the driver and gives an error asking if I am rooted and having busybox, installed busybox installer from sterycson from the play store and it says just Busybox installed and where it is, no version, Installing fails.....any help, allready reflashed the rom so thats not the problem?
EDIT: also included Camera app can only go to 5MP, and Focal can go to 6
tombriden said:
Hmm, audio's working here; can you just try reflashing the kernel followed by
Code:
fastboot erase cache
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Hi,Yes I just tried but the sound is still not working
ForceField said:
Hi,Yes I just tried but the sound is still not working
Click to expand...
Click to collapse
Ranomez said:
In a call I get no sound if I try to switch to speackers, only normal calls working, also Viper4Android doesen't want to install the driver and gives an error asking if I am rooted and having busybox, installed busybox installer from sterycson from the play store and it says just Busybox installed and where it is, no version, Installing fails.....any help, allready reflashed the rom so thats not the problem?
EDIT: also included Camera app can only go to 5MP, and Focal can go to 6
Click to expand...
Click to collapse
Ok, can you guy's flash this for me please:
It's a 43 build of @maxwens BLADE kernel, compiled inline using his source here (as always, huge thanks to him for his work on it)
Hopefully that'll sort the audio issues and i'll take a look at the Camera next
tombriden said:
Ok, can you guy's flash this for me please: http://downloads.kanger.me/getdownl...lusINTER/aosp-plus/boot-BLADE-43-20130818.img
It's a 43 build of @maxwens BLADE kernel, compiled inline using his source here (as always, huge thanks to him for his work on it)
Hopefully that'll sort the audio issues and i'll take a look at the Camera next
Click to expand...
Click to collapse
I just flashed another ROM.
OK,I will reflash AOSP+ and the new kernel and report back
---------- Post added at 09:58 AM ---------- Previous post was at 09:44 AM ----------
Ok,I Reflashed ASOP+ with the new kernel
Sound is Working but Wifi is broken
ForceField said:
I just flashed another ROM.
OK,I will reflash AOSP+ and the new kernel and report back
---------- Post added at 09:58 AM ---------- Previous post was at 09:44 AM ----------
Ok,I Reflashed ASOP+ with the new kernel
Sound is Working but Wifi is broken
Click to expand...
Click to collapse
Ok, i kind of expected that but now i know the audio is fixed i can do a new build. Thanks for testing
if you want wifi back you can do: adb shell su -c 'insmod /lib/modules/bcmdhd.ko'
tombriden said:
Ok, i kind of expected that but now i know the audio is fixed i can do a new build. Thanks for testing
if you want wifi back you can do: adb shell su -c 'insmod /lib/modules/bcmdhd.ko'
Click to expand...
Click to collapse
Ok thanks I will try this command. Really liked the speed of this ROM.It's a Porsche compared to others
0.8.1 uploaded with built-in BLADE kernel and EndeavoruParts accessible from Settings -> Advanced
Camera still at 5MP though :/
tombriden said:
0.8.1 uploaded with built-in BLADE kernel and EndeavoruParts accessible from Settings -> Advanced
Camera still at 5MP though :/
Click to expand...
Click to collapse
Perhaps using an other camer app would let us use the 8MP, because Focal lets us use 6MP?
Anyway your rom is great, close to perfection for me, the only thing missing would be any kind of lockscreen shortcuts but that's only me and I wanna say your rom is great.
Ranomez said:
Perhaps using an other camer app would let us use the 8MP, because Focal lets us use 6MP?
Anyway your rom is great, close to perfection for me, the only thing missing would be any kind of lockscreen shortcuts but that's only me and I wanna say your rom is great.
Click to expand...
Click to collapse
Thanks
Other camera apps will have the same issue. It's down to the new camera libraries from the 4.2.2 dump returning a 302character string for the supported picture sizes but they get read into a 256 string buffer thus cutting off all the higher resolutions :\
I've put a fix into our camera wrapper so it just returns the same supported resolutions as the previous library did. It's uploaded in a new ROM, 0.8.2 but the only file changed is camera.tegra.so so if you don't want to reflash, extract it from system/lib/hw and push in recovery with
Code:
adb shell mount /system/
adb push camera.tegra.so /system/lib/hw/
adb shell chmod 644 /system/lib/hw/camera.tegra.so
tombriden said:
Thanks
Other camera apps will have the same issue. It's down to the new camera libraries from the 4.2.2 dump returning a 302character string for the supported picture sizes but they get read into a 256 string buffer thus cutting off all the higher resolutions :\
I've put a fix into our camera wrapper so it just returns the same supported resolutions as the previous library did. It's uploaded in a new ROM, 0.8.2 but the only file changed is camera.tegra.so so if you don't want to reflash, extract it from system/lib/hw and push in recovery with
Code:
adb shell mount /system/
adb push camera.tegra.so /system/lib/hw/
adb shell chmod 644 /system/lib/hw/camera.tegra.so
Click to expand...
Click to collapse
Thank you, and thanks god I don't need to reflash, cause I started flashing 8.1 at my previows comment and just finished seting up all my things (xposed, touchwiz, playstation certs, viper4android and some others) and really don't want to flash again, lol.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, we will laugh at you, all, at the same time.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATIONS
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
CHECK KNOWN ISSUES HERE
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
Google Apps: Link 1 Link 2
TWRP Recovery: https://www.androidfilehost.com/?fid=24052804347766143
CHANGELOG
Download
GAPPS for CM-12.1
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't mean Out-of-Respect!!!
source
https://github.com/cyanogenmod/android_device_htc_enrc2b
https://github.com/cyanogenmod/android_kernel_htc_enrc2b
https://github.com/cyanogenmod/android_device_htc_tegra3-common
Contributors
Lloir, Thomy
Source Code: http://github.com/cyanogenmod
Working Not Working: Eventually Change log
This will be edited and updated as I make progress
Working 7/7/15:
Audio
Touch
Display
Vibrator
WIFI
Bluetooth
DATA/GSM/RIL (except for sim pin)
BATTERY
ROTATION
GPS
Not Working 7/7/14:
Device encryption
CHANGELOG
?/05/16 (well it's finally coming out) in 2017
05/05/17 -- FINAL
cgroups fixed
RIL Fixes (GSM/DATA)
3G Mtu changed, should see an increase in speed.
Security patches, fixes loads of security issues
X+ now shows up instead of the ONE (MTP) (pulled from AndyLavr git)
SElinux fix up (pulled from AndyLavr git)
CM main source update
and a load of other stuff.
------------------------------------------------------
27/11/15 ------ MD5 b9ae858d0a881ae6a24958caa067360e
Sdcard symlink is fixed? it's storage/sdcard0 (for me anyway test it for me)
Added more sepolicies for the ril :silly:
Updated main cm source
FULL WIPE
------------------------------------------------------
5/11/15
CM update which includes Security updates from Google https://groups.google.com/forum/#!topic/android-security-updates/GwZn7sixask
Reverted the changes I made to sdcard, which means /sdcard is now able to be accessed again.
------------------------------------------------------
25/10/15
More selinux denial's fixed thanks to @el-Loko logs
Let me know if the sim card issue still arises.
I've made changes to MTP and the /sdcard /storage area's
------------------------------------------------------
24/10/15
Sepolicies updated, hopfully the no sim issue will be fixed now. https://github.com/Lloir/android_device_htc_enrc2b-2/commits/cm-12.1
No more selinux denial's that I could find. All eliminated.
Source update
Kernel update's thanks to @ntemis https://github.com/Lloir/htc_kernel_oxp/commits/cm-12.1
Sim toolkit now show's and works
GPS lock is oh oh so much quicker
If google maps has a hissy fit let it die and reload it.
------------------------------------------------------
28/8/15
Updated source (Which includes the chrome fix)
------------------------------------------------------
26/8/15
Updated source
Revert my bluetooth breakage change, so BT works as it should.
------------------------------------------------------
7/8/15
http://review.cyanogenmod.org/#/c/93232/
http://review.cyanogenmod.org/#/c/105285/ + http://review.cyanogenmod.org/#/c/105284/
http://review.cyanogenmod.org/#/c/105100/ (This is a security fix hence the build today) Issue with this, currently will get sorted for a future build
Mainline cm update ^^ those changes are not merged into CM but I've picked them to go into this rom for my own personal build. I will share this build
------------------------------------------------------
7/7/2015
CM general update
CVE's patched (security) http://review.cyanogenmod.org/#/c/102586/
NFC Update
Low memory killer updated
USB OTG Enabled
Brightness should be brighter (Should)
Re-implemented the powerhal from CM-10.2 (For those of you who have been around here for ages)
Updated the keymaster file based off of the grouper (Security)
A ton of patches from the grouper kernel http://review.cyanogenmod.org/#/c/102546/
VFS/ Compaction changes http://review.cyanogenmod.org/#/c/102597/
------------------------------------------------------
20/6/2015
CM mainrom update
GPS working in permissive only mode
-----------------------------------------------------
9/4/2015
12.1 update
Chrome/Firefox work
Updated with most recent CM source
------------------------------------------------------
6/4/2015
CM-12.1
DO NOT DIRTY FLASH OVER CM-12.0 IT WILL CRASH
gps is still broken
everything below counts
NEEDS KERNEL FLASH as usual
------------------------------------------------------
6/4/2015
New Kernel, not loaded with crap. This kernel is WIP. NO SMARTMAX on it, No S2W (Let the rage begin)
Might have turned the audio up...Sounds like it, need someone to confirm
Button light stays on when it needs to now.
------------------------------------------------------
3/4/2015
Fixed No Data issue FLASH THE NEW ROM AND BOOTIMG
------------------------------------------------------
2/4/2015 or 3/4/2015 depending on where you live
1st actual working release so lets start the change log
Battery WORKING
Source updated to today's released source
SELINUX DISABLED
Rotating working
GPS broken
regretting this...check the post above this one...
sooooo I know a load of you have downloaded this? Any bugs I've not listed?
Lloir said:
sooooo I know a load of you have downloaded this? Any bugs I've not listed?
Click to expand...
Click to collapse
Sorry man cant use it daily without the battery being fixed! Other than that the camera works? at least for the most part
just installed it and i am suprised...very smooth.
still installing apps for daily use. will of cause report if theres anything to report.
what excactly does not work with cam? i can shoot pics and they look as pretty as they should.
so, happy new year to every1!
el-Loko said:
just installed it and i am suprised...very smooth.
still installing apps for daily use. will of cause report if theres anything to report.
what excactly does not work with cam? i can shoot pics and they look as pretty as they should.
so, happy new year to every1!
Click to expand...
Click to collapse
It wasn't working for me, but yeah, all of you say it works, so I'll take your word. :good:
Lloir said:
It wasn't working for me, but yeah, all of you say it works, so I'll take your word. :good:
Click to expand...
Click to collapse
I'll jump in as soon as builds with proper battery comes up.
And, thank you for being an awesome dev.
Lloir said:
sooooo I know a load of you have downloaded this? Any bugs I've not listed?
Click to expand...
Click to collapse
installing right now, can't wait to test!
i moved on to the OPO as daily driver, so i don't have to care about stability, but also i'm eager to see how the HOX+ runs Android5! Thanks for your awesome work!:good:
reaper90 said:
installing right now, can't wait to test!
i moved on to the OPO as daily driver, so i don't have to care about stability, but also i'm eager to see how the HOX+ runs Android5! Thanks for your awesome work!:good:
Click to expand...
Click to collapse
Yeah, I need to move on soon, so new devs are going to be needed for the X+ by the next major release.
Lloir said:
Yeah, I need to move on soon, so new devs are going to be needed for the X+ by the next major release.
Click to expand...
Click to collapse
This device is more than two years old now, i don't think there will be new devs coming to this device. Although i know not everyone wants to buy or can afford a new device every two years, i think this one has done it's job. while htc dropped support after only one year, i think some quite stable 4.4 roms are more than we could have asked for!
first impression on this build:
runs pretty good so far, camera not working here, kickstarting the battery from TWRP does not really work for me (maybe i'm doing something wrong) and when using adb shell, the charging led stays forever on.
Camera working fine here !
and whats the purpose of turning the battery on..? I could reboot and its working fine. I did not execute any command. But the battery shows 66% even though its lower than that. So the only problem we face if we dont turn it on is that we cant see the real percentage or what....?
backb0ne5p1d0r said:
Camera working fine here !
and whats the purpose of turning the battery on..? I could reboot and its working fine. I did not execute any command. But the battery shows 66% even though its lower than that. So the only problem we face if we dont turn it on is that we cant see the real percentage or what....?
Click to expand...
Click to collapse
Pretty much, not tested to see if it doesn't charge though....it will ALWAYS show 66%
Also are you using a 3rd party app for camera??
I don't mind it showing 66 as it's not my main phone.
And No, but I flashed GApps.
All I did was full wipe, Flash boot.img, flash ROM, flash GApps. Then the ROM booted and had a working camera
I think I found a temporary fix for the battery problem!
Go to the store, download 2 apps.
1) Boot shell
2) sudo for android.
Open sudo for android and click "Install Sudo"
Then open Boot Shell and click add command button. And add the command "sudo /system/bin/htcbatt"
Now reboot your phone and the battery stats will still be there
backb0ne5p1d0r said:
I think I found a temporary fix for the battery problem!
Go to the store, download 2 apps.
1) Boot shell
2) sudo for android.
Open sudo for android and click "Install Sudo"
Then open Boot Shell and click add command button. And add the command "sudo /system/bin/htcbatt"
Now reboot your phone and the battery stats will still be there
Click to expand...
Click to collapse
Yeah, there's that.
I have it fixed here, just not happy with the fix at the moment. IF People want to fix it this temp way do the following :
reboot into TWRP
mount system
adb shell
chmod 777 system/bin/htcbatt
reboot
If your not happy with using a 777 chmod then that's understandable, I'm trying out a 2nd fix as we speak, this will also help me to fix the battery issue in TWRP too
Things that are now working on my local build
Device Encryption
Battery + Battery LED
IF I'm happy with the battery fix, I'll do that release today.
Still broken :
GPS --- Kinda borked.
Rotating
Button lights are a little yeah.
This is going to be replaced with omni-L
Stay tuned, Not releasing ANYTHING until I have a nice working build of a ROM, not going to be releasing half-assed builds anymore.
Ok, after 2 days of daily use i can say that this rom is very stable, no reboots or freezes. Only GPS and auto-rotate is not working for me, but (orig)cam does its job.
One tip for the battety sidekick:
Instead of doing the trick via pc do it in a shell on your phone but dont kill the process with ctrl-c.