Hi guy!
After some days without any answer, i have worked on Kitkat.
It seems that it boots on my tab.... :angel:
Wait the fist release on 2.6.29 kernel
And 2.6.37 for A70S2 (HC and FROYO)
:good::fingers-crossed::good:
Bizcuite
Amazing Biz... you are my hero :good:
airwolf1544 said:
Amazing Biz... you are my hero :good:
Click to expand...
Click to collapse
I will to become all red stop stop please lol
Well it rests a lots of works!!!!
I have just boot logo.
I will try to boot it with 2.6.29 kernel, but it must be ok and have the same result (only BT and upnp should (/could) not worked).
For 4 days i will be at home and works when i have times to work on it.
Bizcuite
bizcuite said:
i will become all red stop stop please lol
well it rests a lots of works!!!!
I have just boot logo.
I will try to boot it with 2.6.29 kernel, but it must be ok and have the same result (only bt and upnp should (/could) not worked).
For 4 days i will be at home and works when i have times to work on it.
Bizcuite
Click to expand...
Click to collapse
ready to test sir!
Wow, just wow. Amazing!
Sharpen you swords (charge your batteries) and get ready for fiiiiiiight (and get ready for teeeeeeeeest)
bizcuite said:
I will to become all red stop stop please lol
Well it rests a lots of works!!!!
I have just boot logo.
I will try to boot it with 2.6.29 kernel, but it must be ok and have the same result (only BT and upnp should (/could) not worked).
For 4 days i will be at home and works when i have times to work on it.
Bizcuite
Click to expand...
Click to collapse
I know its much work.. but you try it..
airwolf1544 said:
I know its much work.. but you try it..
Click to expand...
Click to collapse
Oooooh yes its lots of work. And patience to wait the compilation finish it...
I recompile all atm. I had forgotten to include all device.mk file maybe I will have trebuchet at first start (yes I compile cm11 ).
Gpu driver and libs seems to work... I have the boot logo (and a crash system. Bootloop)
First screenshot is near
Bizcuite
Sent from my GT-N7100 using xda app-developers app
Just a question: Are you gonna make this use ART, cause that's what I guess u will do and that's something that I guess will make the tab faster, but as far as I understand as of now ART makes a lot of apps not work (at least for now till they are updated)?
Ranomez said:
Just a question: Are you gonna make this use ART, cause that's what I guess u will do and that's something that I guess will make the tab faster, but as far as I understand as of now ART makes a lot of apps not work (at least for now till they are updated)?
Click to expand...
Click to collapse
You have the choice. you can choose in dev option dalvik or art.
Or chane an option in buid.prop, set libdvm to libart or inverse.
I have a boot failure at start, i try to fix it.
Bizcuite
Welcome Kitkat
Bizcuite
bizcuite said:
Welcome Kitkat
Bizcuite
Click to expand...
Click to collapse
I would like to try also kitkat on my 101, gen. 8 :good:
greeting
mika67 said:
I would like to try also kitkat on my 101, gen. 8 :good:
greeting
Click to expand...
Click to collapse
It will be possible with 2.6.29 kernel i think.
ATM on A70S2 - Gen9 kernel 2.6.35-7:
-TS working
-3D working
-Soft button activated on my tab (to see on others tabs)
Not working:
-sound (don't know why atm)
-BT (just have to configure init.rc)
-Wifi (recompile all with Wlan option, must work after)
-looooots of thing that i have not tested.
Another thing, Kitkat must have system in a different partition, you will have to install 3 image files in the sdcard (root of system, system and data).
I think that i will use directly the internal sdcard partition and write partitions directly on the sdcard (like a real partition, not an image -> better perf ). BUT a wipe of the sdcard is necessary (one time).
Bizcuite
bizcuite said:
It will be possible with 2.6.29 kernel i think.
ATM on A70S2 - Gen9 kernel 2.6.35-7:
-TS working
-3D working
-Soft button activated on my tab (to see on others tabs)
Not working:
-sound (don't know why atm)
-BT (just have to configure init.rc)
-Wifi (recompile all with Wlan option, must work after)
-looooots of thing that i have not tested.
Another thing, Kitkat must have system in a different partition, you will have to install 3 image files in the sdcard (root of system, system and data).
I think that i will use directly the internal sdcard partition and write partitions directly on the sdcard (like a real partition, not an image -> better perf ). BUT a wipe of the sdcard is necessary (one time).
Bizcuite
Click to expand...
Click to collapse
Send me something to test - I am getting exited!
bizcuite said:
It will be possible with 2.6.29 kernel i think.
Another thing, Kitkat must have system in a different partition, you will have to install 3 image files in the sdcard (root of system, system and data).
I think that i will use directly the internal sdcard partition and write partitions directly on the sdcard (like a real partition, not an image -> better perf ). BUT a wipe of the sdcard is necessary (one time).
Bizcuite
Click to expand...
Click to collapse
Hi biz,
I think that with the first test would be not so bad if the installation only with
3 image file would take place (simpler installation).
If the new system has then beta status could one then the partition
on the internal SD card drove through .
Are already curious on the new system
greeting
mika67 said:
Hi biz,
I think that with the first test would be not so bad if the installation only with
3 image file would take place (simpler installation).
If the new system has then beta status could one then the partition
on the internal SD card drove through .
Are already curious on the new system
greeting
Click to expand...
Click to collapse
Partitions directmy wrote on the internal sdcard will be option at start.
Now. The main PB is the wifi hal. Because wpa supplicant v0.6 and wl1271 driver has been deleted from the code source of Android. I try to compile it for 2.6.35 (more easy because drivers are updated).
Let me see if there is a way to have wifi for 2.6.29 kernel.
Bizcuite
Sent from my GT-N7100 using xda app-developers app
ready to test for 101IT when you have something
Will the touchscreen be as difficult to make work as the last kernel you worked on these last few weeks ?
Cheers!
4qu4rius said:
ready to test for 101IT when you have something
Will the touchscreen be as difficult to make work as the last kernel you worked on these last few weeks ?
Cheers!
Click to expand...
Click to collapse
I don't know
But it will be more easy to fix than with CM9 (first experience in android compilation for remember )
FYI:
I had few time to try the new image that i have compiled.
It's compiled with CM options (wasn't the case in CM9). Bootlogo is CM, themes doesn't crashed, but it lakes a little thing to fix.
I will try to fix wifi this week end if i have more times to dev.
I progress about it, ATM i try with 2.6.35 (only for A70S2), and i hope that it will worked with 2.6.29 (for all others tabs), mac80211 module is included into this kernel, but maybe the driver cannot be compatible
Bizcuite
bizcuite said:
I don't know
But it will be more easy to fix than with CM9 (first experience in android compilation for remember )
FYI:
I had few time to try the new image that i have compiled.
It's compiled with CM options (wasn't the case in CM9). Bootlogo is CM, themes doesn't crashed, but it lakes a little thing to fix.
I will try to fix wifi this week end if i have more times to dev.
I progress about it, ATM i try with 2.6.35 (only for A70S2), and i hope that it will worked with 2.6.29 (for all others tabs), mac80211 module is included into this kernel, but maybe the driver cannot be compatible
Bizcuite
Click to expand...
Click to collapse
Biz
Any progress on this?
Thanks
Mikerla said:
Biz
Any progress on this?
Thanks
Click to expand...
Click to collapse
Yes and no, i work on it when i have times.
I try to find any ways to have a working wifi. I use CM11 wifi drivers but i cannot use it correctly (myukernel or CM11 is not configured properly).
When i have a working wifi i will upload an alpha release.
For screen and navigation button, i think that there will have no pb with it. The managment about this is very different.
To fix:
-Wifi
-external/internal sdcard not seen
-OMX codecs
-Sound HAL
-BT
-ALL
Bizcuite
Related
This thread is for installation, help,
known bugs
and infos/faqs
for the shortly released build of cyanogen for the gen 8 archos
it is only "recommended" to use it with the a101 or the 70
link: http://www.openaos.org
installation:
install sde
install open aos recovery
Download the last Cyanogen img file from here: http://download.openaos.org/bubu/gen8/android/Rename the file to openaos-gingerbread then copy it to the root of your Archos
edit the menue.lst (with notepad++) to:
Archos|ARCHOS|ARCHOS|/init|0
Angstrom||/rootfs.img|/sbin/init|1
Ginger-bread||/openaos-gingerbread.img|/init|0
(add an empty line at the end)
unix breaks must be enabled in notepad++ if you are on windows.
Reboot your Archos and hold down VOL - (Down) Button, select "Developer Edition" and select in the Boot Menu "Ginger-bread".
if nothing is helping try(wont boot/ wont show ginger-bread):
http://www.filesonic.com/file/1302552154/menu.lst
bugs:
Not working:
Bluetooth
accelerated Video decoding
Suspend
TS calibration on A28/A32/A43
orientation has it hickups
Known problems:
general instability / random crashes
hard to use on resistive TS models due to missing calibration
faq:
What's working ?
Currently working:
SGX/EGL 3D acceleration
WiFi
Touchscreen
Orientation
Android Market
alot more...
screan not working on normal orientation on the a101?
activate 180* in settings-cyanogensettings-display
updating:
just exchange the img
historyin unseperated datetime)
initial 20110623
update1 20110626
update2 20110628
update3 20110629
Update4 20110708 more stability, faster
developing........ in a real guide and how to......
all credits to the geniuses of openaos and especially bubu.
and thank them(bubu,@dm8tbr and divx) for this guide too they been super helpfull
sent from my droid (not the one you are looking for)
Great!!!!!!!!!!!!!!!!!!!
I'm very excited to finally have an actual file in hand for CM7. Just FYI though, before you flash too soon:
Not working:
Audio
Bluetooth
Accelerometer
accelerated Video decoding
Suspend
TS calibration on A28/A32/A43
Known problems:
general instability / random crashes
Touchscreen has problems on the A101
hard to use on resistive TS models due to missing calibration
There's still some work to be done before it's a daily use ROM, but hopefully we can help out and fix some of these issues.
Great news guys! Look forward to testing it.
How do I edit the list?
Code:
Cyanogen||/cyanogen.img|/sbin/init|1
Update
This is really great, but you can notice this is an alfa version
coen22 said:
How do I edit the list?
Code:
Cyanogen||/cyanogen.img|/sbin/init|1
Update
This is really great, but you can notice this is an alfa version
Click to expand...
Click to collapse
see how to.....
Greeaaat
but i'll wait until its a "daily use"rom like ninja said
for now, Urukdroid is great for me
Lenn said:
Greeaaat
but i'll wait until its a "daily use"rom like ninja said
for now, Urukdroid is great for me
Click to expand...
Click to collapse
what a helpfull post again
sent from my droid (not the one you are looking for)
gbohm said:
what a helpfull post again
sent from my droid (not the one you are looking for)
Click to expand...
Click to collapse
3 guys above e posted exactly the same, but whatever...
ok i cant get this to show in the boot menu. i have put the .img file on my tab with the usb. then i edited the list like this : Cyanogen||/cyanogen.img|/sbin/init|1
what did i do wrong?
saprano614 said:
ok i cant get this to show in the boot menu. i have put the .img file on my tab with the usb. then i edited the list like this : Cyanogen||/cyanogen.img|/sbin/init|1
what did i do wrong?
Click to expand...
Click to collapse
what is the images name?
please follow my how to to the letter....
sent from my droid (not the one you are looking for)
it is cyanogen.img i think the problem is that i can get it to copy to the root. when i use sufile browser it is in the sdcard folder. and when i try to copy it to the root it says i dont have enough space. is there a way to have this on the sdcard and still work?
saprano614 said:
it is cyanogen.img i think the problem is that i can get it to copy to the root. when i use sufile browser it is in the sdcard folder. and when i try to copy it to the root it says i dont have enough space. is there a way to have this on the sdcard and still work?
Click to expand...
Click to collapse
not that i know copy it to your pc mount your archos then copy it to root and please name it like i wrote and edit your menue file like i wrote
Sent from my A101IT using XDA Premium App
Gr888888, i think we must support them, we should donate what we committed before.
gbohm said:
not that i know copy it to your pc mount your archos then copy it to root and please name it like i wrote and edit your menue file like i wrote
Sent from my A101IT using XDA Premium App
Click to expand...
Click to collapse
i did and still nothing. i will try again i just reset android
saprano614 said:
i did and still nothing. i will try again i just reset android
Click to expand...
Click to collapse
i will post my menue.lst if you want
sent from my droid (not the one you are looking for)
saprano614 said:
i did and still nothing. i will try again i just reset android
Click to expand...
Click to collapse
you have to modify it and name it openaos-gingerbread.img did you gunzip it? it should have 5xxmb.
btw put an empty line at the end of the menue.lst
sent from my droid (not the one you are looking for)
gbohm said:
i will post my menue.lst if you want
sent from my droid (not the one you are looking for)
Click to expand...
Click to collapse
please do and i will try later.
saprano614 said:
please do and i will try later.
Click to expand...
Click to collapse
no garantie it won't kill your phone
http://www.filesonic.com/file/1302552154/menu.lst
Lenn said:
3 guys above e posted exactly the same, but whatever...
Click to expand...
Click to collapse
That's probably why you got such a response funny enough im sure you was one of the first crying out for Cyanogen on gen8 at least we have something and not just a topic with users slagging each other off!!
Thankyou gbohm openaos and especially bubu for all of your hard work, great start
NOTE: This will probably no longer be maintained. It was the result of me playing around with the kernel from scratch instead of trying to understand what changes others have made and why they had made them! Now I'm a little more confident I'll probably be using DooMLoRD's kernel as a base for any changes I make to the Ray: [Kernel] [Ray] DooMLoRD's Kernel for Ray
hartej said:
Been playing around with Kernel development and created an overclocked kernel for the 4.0.2.A.0 stock Rom.
There's nothing too speciall in it at the moment, but lets you overclock the Ray to 1.9Ghz using the source released by SE and the modified CPU steps that IF2 posted here: http://forum.xda-developers.com/showthread.php?t=1165355
There's no custom bootloader/Clockwork mod and no additional governers (at the moment) although I may add these in future as I learn more.
It seems to work well enough, and everything seems to be working as standard. I experience random lock-ups at 1.9 and occasionally 1.8Ghz, especially when it goes into/out of sleep when the screen turns off. Lower frequencies seem stable though.
This is released as-is, I'm using it myself but I can't be held responsible for any instabilities or failures you might experience. Just thought it might be of use to some people.
The new .img file can be downloaded from here: http://dl.dropbox.com/u/17615284/4.0.2.A.0-V0.13-2011-12-18.img
Alternatively, I've posted a version of the DooMLoRD kernel for the Ray which has a ton more features. This can be found here: http://forum.xda-developers.com/showthread.php?t=1400121
To install just use fastboot in the usual way. To return to stock, extract kernel.sin from the official update image using WinZip/WinRar etc and flash using fastboot again.
Click to expand...
Click to collapse
I'll post any updates here from now on.
Changelog:
19/12/2011 - V0.13 - As people have quite rightly pointed out, V0.12 boots at 1.8GHz as default, which causes multiple reboots. I hadn't noticed this as I had SetCPU reduce it to 1GHz as soon as the system started. The only change to this version is to have it boot at 1GHz as default, it's up to the user to increase it themselves.
28/10/2011 - V0.12 - Added Clockwork Recovery v5.0.2.6 (Spam Vol[-] when phone starts up, use volume keys to navigate, home to select, back for back)
28/10/2011 - V0.11 - Started playing with the Ramdisk - as a first start I've made it rootable. Things like "Adb remount" work now.
26/10/2011 - V0.1 - intial release
Current version:
~~~~~~~~~
V0.13 can be downloaded here: http://dl.dropbox.com/u/17615284/4.0.2.A.0-V0.13-2011-12-18.img
Older versions:
~~~~~~~~~
V0.12 can be downloaded here: http://dl.dropbox.com/u/17615284/4.0.2.A.0-OverclockV0.12.img
V0.11 can be downloaded here: http://dl.dropbox.com/u/17615284/4.0.2.A.0-OverclockV0.11.img
get new kernel~nice
tested it works really cool
thanks!!!!!
Like it...
thanks
Glad to see the "Recovery option" is available.
I tested v0.11+OC 1.3Ghz -> no problem.
However, v0.12+OC 1.2 or 1.3 -> keep on rebooting.
v0.12+no OC (use default 1Ghz) -> no problem.
im on 012+oc 1.5mhz, still working well....
great works!
great work, thx for your efforts
the included cwm is it dooms latest?
http://forum.xda-developers.com/showthread.php?t=1172885
"[v12 onwards] modified recovery to support /sd-ext backup/restore (remember /sd-ext has to be the 2nd partition on ur sdcard [mmcblk0p2] for this to work)"
if it is not I think that would be usefull with ext support, now you can use a2sd for xperia, bu it is not possible to make nand backup bcs cwm dit not recognize ext partition.
can you add donation possibility, would like to support your work
Thank you a thousand times! :d
2 questions though:
- I have to reroot my phone after this?
- Do I have to rename the download to boot.img?
Thanks 4 sharing!!!
-No
-No
;-)
funiewski said:
great work, thx for your efforts
the included cwm is it dooms latest?
http://forum.xda-developers.com/showthread.php?t=1172885
"[v12 onwards] modified recovery to support /sd-ext backup/restore (remember /sd-ext has to be the 2nd partition on ur sdcard [mmcblk0p2] for this to work)"
if it is not I think that would be usefull with ext support, now you can use a2sd for xperia, bu it is not possible to make nand backup bcs cwm dit not recognize ext partition.
can you add donation possibility, would like to support your work
Click to expand...
Click to collapse
It's not the latest I'm afraid so I doubt the ext backup would work. I'll see what I can do for the next release when I get a chance.
At some point I was also going to see if it's possible to change the MTD partition structure to give more space to /data. At the moment adb reports:
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock0 400.0M 241.8M 158.2M 60% /system
/dev/block/mtdblock3 420.0M 270.3M 149.7M 64% /data
This means that there's over 150MB of 'free' space in system that could be given over to the data partition instead of being effectively lost. May or may not be possible - don't know enough about the system yet.
As for donations - this is as much a learning experience for me than anything else, and at the moment I'm mostly applying things that others have done instead of making any breakthroughs myself so I wouldn't feel happy taking donations, but the thought is appreciated.
Bazonga said:
Thank you a thousand times! :d
2 questions though:
- I have to reroot my phone after this?
- Do I have to rename the download to boot.img?
Click to expand...
Click to collapse
You'll have to put it into fastboot mode by powering on and holding Vol[+], then flash using "Fastboot flash boot <filename>" - you can rename it or not, provided the <filename> part matches. You shouldnt have to reroot.
kkline38 said:
Glad to see the "Recovery option" is available.
I tested v0.11+OC 1.3Ghz -> no problem.
However, v0.12+OC 1.2 or 1.3 -> keep on rebooting.
v0.12+no OC (use default 1Ghz) -> no problem.
Click to expand...
Click to collapse
That's strange, i've got it overclocked to 1.5Ghz and it seems to be really stable. As far as I'm aware the only change I made between the two was adding clockwork - there shouldn't be any other difference... I'll look into it.
Double reboot only 10 min after flashing and without changing frequencies..
Bazonga said:
Double reboot only 10 min after flashing and without changing frequencies..
Click to expand...
Click to collapse
Without having your device in front of me I don't know how much I can do to help, but I'll look into it once I have the time. Unfortunately I have other things on the go at the moment so it probably won't be till next week.
hartej said:
Without having your device in front of me I don't know how much I can do to help, but I'll look into it once I have the time. Unfortunately I have other things on the go at the moment so it probably won't be till next week.
Click to expand...
Click to collapse
Thanks, I flashed the stock kernel back for now, Ray kept rebooting on me for no reason..
hartej said:
That's strange, i've got it overclocked to 1.5Ghz and it seems to be really stable. As far as I'm aware the only change I made between the two was adding clockwork - there shouldn't be any other difference... I'll look into it.
Click to expand...
Click to collapse
Do you use SetCPU ? (I use SetCPU 2.2.4)
What's the parameters did you use to OC 1.5Ghz ?
"ondemand" ? "powersave" ? "performance" ? or ?
Currently I changed back to V0.11. (it's stable for me)
kkline38 said:
Do you use SetCPU ? (I use SetCPU 2.2.4)
What's the parameters did you use to OC 1.5Ghz ?
"ondemand" ? "powersave" ? "performance" ? or ?
Currently I changed back to V0.11. (it's stable for me)
Click to expand...
Click to collapse
Yup, think I'm on 2.14 though - I doubt this would make a difference but its possible I guess.
I leave everything as-is (So ondemand governor) but reduce the min to 122MHz and increase max to 1.5GHz. Still confused as to why the previous version is more stable for some, but I'll have a look at the differences.
hi! thank you for this kernel.
now question. can you include USB_otg into your kernel? it's realised in DooMLorD kernel for arc (link). is it possible to do this feature for our device?
P.S. sorry for my english, i'm from Russia
vdsirotkin said:
hi! thank you for this kernel.
now question. can you include USB_otg into your kernel? it's realised in DooMLorD kernel for arc (link). is it possible to do this feature for our device?
P.S. sorry for my english, i'm from Russia
Click to expand...
Click to collapse
Don't worry about your English - my Russian is much worse!
I'm developing this for my own uses (selfish I know) while I work out how it's all put together. I'll add OTG to my list although I can't promise anything.
thanks
take it
Tried 0.12 and was really happy there´s clockwork for my ray But I have to go back to stock kernel. v0.12 randomly freezes and then reboots (btw. ray gets hot untill reboot).
I didn´t overclock and use rooted 4.0.2.A.0.42.
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.
After too many work's and to many white night GB now working, off course there's no GSM waitin to Rebellos and Oleg work's on. Thank's for them to make this possible.
First Picture :
This ddms because S8530 no lcd then S8500 can use it with LCD view.
Update :
First pre-alpha SD
Work : Touch screen, Screen rotate...
Don't work : Wifi, Audio, all key...
I9000 factroyfs XJVO, initramfs XJVP full with modification!!!
Kernel GB some modif but not necessary, dont remember now
Just to clarify, all the work is mine except the kernel which is Rebellos and Oleg, I had no choice to use the kernel in order to work on porting Gb. But it will be confidentially.
Very very nice
Cant wait for LCD drivers to get ready.. badly want to play with android even if there are countless things left to fix
suggest not calling it "release" because it's certainly not rename thread?
maybe *MAYBE* pre-alpha release once it's shown on a phone with working display - S8530 has slightly different sdcard interface apparently... i've not been able to mount anything yet on my S8500, well done getting platform to start on S8530.
nbates66 said:
suggest not calling it "release" because it's certainly not rename thread?
maybe *MAYBE* pre-alpha release once it's shown on a phone with working display - S8530 has slightly different sdcard interface apparently... i've not been able to mount anything yet on my S8500, well done getting platform to start on S8530.
Click to expand...
Click to collapse
Its some corrupt with disk_policy i disabled it. there's maybe difference but im not sure. Send you later script you will see. For now some little issue with touch screen.
Very well done my friend ^^
Tigrouzen said:
After too many work's and to many white night GB now working, off course there's no GSM waitin to Rebellos and Oleg work's on. Thank's for them to make this possible.
Click to expand...
Click to collapse
Thumbs Up! I just finished my GB kernel compile, (but I replaced the init with the old one in the intramfs - I need my Bada, too ) but I can not test it until later this afternoon or evening... I'm on S8500 ...
Which version of OS did you used?
i've had disk policy disabled in all my builds as well, trying another variation now after redoing my filesystem though, Tigrouhzen are you able to mount moviNAND as well yet?
Gud start ..
this GB port can work on S8500 right ? the s-AMOLED drivers are already ready with the devs unlike the wave II i believe..
so this Gingerbread port will display on the wave S8500 Screen?
nbates66 said:
i've had disk policy disabled in all my builds as well, trying another variation now after redoing my filesystem though, Tigrouhzen are you able to mount moviNAND as well yet?
Click to expand...
Click to collapse
Yes verry wel mounted all partition.
anghelyi said:
Thumbs Up! I just finished my GB kernel compile, (but I replaced the init with the old one in the intramfs - I need my Bada, too ) but I can not test it until later this afternoon or evening... I'm on S8500 ...
Which version of OS did you used?
Click to expand...
Click to collapse
OK, it boots here, too, to some extent: I can see the boot logo, but I haven't provided a filesystem to it so it reboots after a while... But my Bada is intact so later I'll try to mount the filesystem, too!
anghelyi said:
OK, it boots here, too, to some extent: I can see the boot logo, but I haven't provided a filesystem to it so it reboots after a while... But my Bada is intact so later I'll try to mount the filesystem, too!
Click to expand...
Click to collapse
Because its on initramfs. If you want your bada intact dont forget disabled disk_policy. I use Gb init full from i9000. The big hardly its you need to change script and some script on system also, and make right symlink then ive got problem with symlink doesnt make any link then i make on my initramfs a link, like mount ext2 /dev/block/mmcblk1p2 /sd2 ln -s /sd2/system /system....etc...
I go to sleep some good night !!!
Edit: nbates66 ive got a real all scripts, booting in sd version froyo then adb pull /*.rc
i've been able to get gb kernel to execute for a while but no filesystems yet, anyways, for filesystems you make, ensure you configure the toolbox symlinks, this will help ensure all services work correctly later on:
http://dl.dropbox.com/u/55049485/gb_binsymlinks.sh
(the files are slightly different to in froyo apparently, but same thing is done)
hmmm current sources less functional for me compared to the ones a few days ago, with this kernel source set i cannot get adb to work(worked on gb build a few days ago), still no filesystem mounts working on S8500 as far as i can tell either (yes, symlink method doesn't work either)
Tigrouzen said:
Because its on initramfs. If you want your bada intact dont forget disabled disk_policy. I use Gb init full from i9000. The big hardly its you need to change script and some script on system also, and make right symlink then ive got problem with symlink doesnt make any link then i make on my initramfs a link, like mount ext2 /dev/block/mmcblk1p2 /sd2 ln -s /sd2/system /system....etc...
I go to sleep some good night !!!
Edit: nbates66 ive got a real all scripts, booting in sd version froyo then adb pull /*.rc
Click to expand...
Click to collapse
It's no news for me to change the scripts, played a lot with that in Froyo But as I see the apply_disk_policy is commented out in the latest init.rc...
nbates66: with disabled disk policy is it safe for Bada to use the original init ? (oh, man, I checked the script you provided... I remember doing the same by hand some months ago )
anghelyi said:
nbates66: with disabled disk policy is it safe for Bada to use the original init ?
Click to expand...
Click to collapse
which one? If you mean the init here: http://code.google.com/p/badadroid-kernel/source/list
then yes and haven't corrupted my bada for 2 weeks! Haven't tried using the froyo init on Gingerbread kernel since a while ago though(gingerbread requires ueventd).
nbates66 said:
which one? If you mean the init here: http://code.google.com/p/badadroid-kernel/source/list
then yes and haven't corrupted my bada for 2 weeks! Haven't tried using the froyo init on Gingerbread kernel since a while ago though(gingerbread requires ueventd).
Click to expand...
Click to collapse
Was it with the latest one? As Rebellos replaced the initramfs completly!
yes i just tried two kernels with that init executable from latest file push, my bada OS is intact just i can't do anything with the kernels without adb or device mounting capability
nbates66 said:
yes i just tried two kernels with that init executable from latest file push, my bada OS is intact just i can't do anything with the kernels without adb or device mounting capability
Click to expand...
Click to collapse
Thanks! I'll replace the old one then and later do some tests!
how about getting the old irc port channel up to discuss some results and ideas?
I saw that you wrote that screen rotation works. I was wondering, if you can charge the battery of the phone?
Awesome work, thank you a lot. I will donate next month.
Good work, awsome work indeed,
Just for asking, is this a Cyanogen Mod 7 version of GB for Galaxy S? If it is, then it's awsome work... If it isn't, why you don't pick it up? I have 0 knowledge in this so it can be a noob question, but I am interested in knowing that
Cheers
This is thread for devlopment and discussion for cm10.1 (BCM21654)
myself working on Samsung galaxy pocket neo duos(S5312)
@Alonso1398 working on Samsung galaxy music
Contibutors:
@k2wl @Unjustified Dev @Alonso1398 @dhinesh77 @psych.half
Status for Cm10.1 on pocket neo duos (s5312)
Status for Cm10.1 on pocket neo duos (s5312)
First bootable cm 10.1 rom on S5312/S5310
Whats working ?
vibration
hardware buttons
external-sdcard
apps install
egl
camera(video recording force close because of antibanding feature)
sound
sensors
bluetooth ( minor bug only => unable to connect to any devices)
Wi-Fi
Storage
Ril,
whats not working ?
Source:
https://github.com/dhinesh77/android_device_samsung_corsica
Status for Cm10.1 on galaxy music
Status for Cm10.1 on galaxy music
Compiling again... I think thus time the bluedroid problem didn't show, hope it ends without more errors, also a question, when you managed to get to bootanimation, did you disabled hadware rendering by just editing build.prop?
Enviado desde mi GT-S6010L mediante Tapatalk
Alonso1398 said:
Compiling again... I think thus time the bluedroid problem didn't show, hope it ends without more errors, also a question, when you managed to get to bootanimation, did you disabled hadware rendering by just editing build.prop?
Enviado desde mi GT-S6010L mediante Tapatalk
Click to expand...
Click to collapse
for the first time disabled hardware rendering, due to that all apps force closes, after fixing egl force close error solved
dhinesh77 said:
for the first time disabled hardware rendering, due to that all apps force closes, after fixing egl force close error solved
Click to expand...
Click to collapse
Soo now finished compiling and installed but got a bootloop. Something interesting is that if restore boot from stock via cwm, it passes the bootanimation and a window that says android upgrading appears but when it finishes, then makes the bootanimation again and do the same eternally.
Updated a lot my device tree based on yours. Here is the device tree, the only folder that didn't modified was overlay, also the files from rootdir are the ones from my device (except init.recovery.rhea_ss_ivoryss.rc).
This are the files I'm using as proprietary blobs. Also I haven't modified my kernel source and had to comment"TARGET_USERIMAGES_USE_EXT4" from boardconfig.mk because for some reason was giving errors while compiling.
Also when trying taking logcat via adb it stucks on - waiting for device -
I was so close of getting it to boot :crying:
Edit: I think the files from the rootdir folder on my tree are the ones that should be edited, so already edited them to be like from your tree and I'm compiling again
Edit2: Editing those files to much do even worse, get stucked on the device logo so most of the files from rootdir are still the ones from the device. Also updated the system.prop file that was forgetting but still didn't worked to past bootanimation. Been really hard trying to fix it, could someone give me a hand?
Alonso1398 said:
Soo now finished compiling and installed but got a bootloop. Something interesting is that if restore boot from stock via cwm, it passes the bootanimation and a window that says android upgrading appears but when it finishes, then makes the bootanimation again and do the same eternally.
Updated a lot my device tree based on yours. Here is the device tree, the only folder that didn't modified was overlay, also the files from rootdir are the ones from my device (except init.recovery.rhea_ss_ivoryss.rc).
This are the files I'm using as proprietary blobs. Also I haven't modified my kernel source and had to comment"TARGET_USERIMAGES_USE_EXT4" from boardconfig.mk because for some reason was giving errors while compiling.
Also when trying taking logcat via adb it stucks on - waiting for device -
I was so close of getting it to boot :crying:
Edit: I think the files from the rootdir folder on my tree are the ones that should be edited, so already edited them to be like from your tree and I'm compiling again
Edit2: Editing those files to much do even worse, get stucked on the device logo so most of the files from rootdir are still the ones from the device. Also updated the system.prop file that was forgetting but still didn't worked to past bootanimation. Been really hard trying to fix it, could someone give me a hand?
Click to expand...
Click to collapse
yup sure i will.....from two days broad band is not working so I can't come to online. ....
you can take logs without adb too... if rom didn't booted just return back to cwm and flash aroma file mAnager and go to data/tombstones in that folder many files present. . copy allfiles to sd view in gedit ... error message will be in Brown colour... this helps to fix all bugs. .. I fixed for pocket neo like this method only.. since adb is working only after authorizing pc in development settings...
dhinesh77 said:
yup sure i will.....from two days broad band is not working so I can't come to online. ....
you can take logs without adb too... if rom didn't booted just return back to cwm and flash aroma file mAnager and go to data/tombstones in that folder many files present. . copy allfiles to sd view in gedit ... error message will be in Brown colour... this helps to fix all bugs. .. I fixed for pocket neo like this method only.. since adb is working only after authorizing pc in development settings...
Click to expand...
Click to collapse
Thanks a lot, didn't know that trick of aroma file manager, now finally made it boot :victory::victory:
Status:
Whats working?
-It boots
-Touch
-Hardware buttons (home fixed and now wakes the device)
-Camera (all modes)
-Vibration
-Rotation
-CRT effect
-Sound
-Wi-fi
-Bluetooth (it can receive files but not sure if it can send)
-Storage (both internal and external)
-Button for start reproducing music tough it can't stop it
-Microphone
-Ril
What's not working?
-fm radio
Notes:
-For some reason the glow effect wile sliding is orange instead of blue
Edit: Link to the thread here
Great going guys . Hatsoff to ur work. Waiting for completion
Sent from my GT-S6012 using Tapatalk
Alonso1398 said:
Thanks a lot, didn't know that trick of aroma file manager, now finally made it boot :victory::victory:
Status:
Whats working?
-It boots
-Touch
-Hardware buttons (home fixed and now wakes the device)
-Camera (I think)
-Vibration
-Rotation
-CRT effect
What's not working?
-Sound
-Ril
-Wi-fi
-Bluetooth
-Storage (both internal and external)
-No baseband
Notes:
-The button for start reproducing music I think it works but since there's no music because of storage problems, it can't reproduce anything but long pressing the button will open Apollo
-For some reason the glow effect wile sliding is orange instead of blue
-Also is it me or the unlock glow thing is kinda small?
Click to expand...
Click to collapse
Nice, i amanged to mount external storage but not internal memory, though external storage is working still many apps not opening because of no internal storage(since internal is seted as default)...
Latest strategy:
1.Wifi Hotspot working (but normal WIFI not working)
2. Bluetooth able to turn on and searching devices, but unable to connect to that..
3. Hardly tried still ril coulnt be fixed
dhinesh77 said:
Nice, i amanged to mount external storage but not internal memory, though external storage is working still many apps not opening because of no internal storage(since internal is seted as default)...
Latest strategy:
1.Wifi Hotspot working (but normal WIFI not working)
2. Bluetooth able to turn on and searching devices, but unable to connect to that..
3. Hardly tried still ril coulnt be fixed
Click to expand...
Click to collapse
I made dual boot to speed up process but for some reason every build made isn't booting even if I know it's going to boot and tombstones sometimes aren't generated so will going to download source again...
I keeped a booting build and fixed sound for it, so my next step is try fixing storage (since both internal and external aren't working)
Alonso1398 said:
I made dual boot to speed up process but for some reason every build made isn't booting even if I know it's going to boot and tombstones sometimes aren't generated so will going to download source again...
I keeped a booting build and fixed sound for it, so my next step is try fixing storage (since both internal and external aren't working)
Click to expand...
Click to collapse
bro over 95% of all bugs solved except one thats is ril
dhinesh77 said:
bro over 95% of all bugs solved except one thats is ril
Click to expand...
Click to collapse
Lol, I'm like turtle speed fixing problems then will try too with ril
Alonso1398 said:
Lol, I'm like turtle speed fixing problems then will try too with ril
Click to expand...
Click to collapse
any progress regarding ril ?
dhinesh77 said:
any progress regarding ril ?
Click to expand...
Click to collapse
Not so far, and this error 7 problem is worrying me, the builds shouldn't give that error since the device tree is almost the same as before when I was on the vbox, so being slowed down trying to fix it but I think my only actual solution is being replacing system folder on older flashable builds also storage seems like a headache for my device, already looked at your tree but still not working
Alonso1398 said:
Not so far, and this error 7 problem is worrying me, the builds shouldn't give that error since the device tree is almost the same as before when I was on the vbox, so being slowed down trying to fix it but I think my only actual solution is being replacing system folder on older flashable builds also storage seems like a headache for my device, already looked at your tree but still not working
Click to expand...
Click to collapse
dont worry bro i am here to help you between , all issues on samsung pocket neo duos is solved including ril....
Thanks a lot, the weird not installing problem it still there, however I can take the old working build and replace the system folder and boot.img with new ones compiled so somehow that way I can still be working however replacing the META-INF from the new builds doesn't work. I'm trying to apply the fixes for my device so now so far internal storage is finally working but external still doesn't, now that camera opens, discovered that camcoder isn't working for me, and bluetooth its activating but actually don't know if it can connect to other devices.
Thanks a lot for the help you are offering, really.
Edit: Wi-fi fixed however still without baseband and ril
Enviado desde mi MW0711 mediante Tapatalk
hi bro , i saw on github that you have merged pull request, w8ing for outcome
dhinesh77 said:
hi bro , i saw on github that you have merged pull request, w8ing for outcome
Click to expand...
Click to collapse
Thanks a lot for those pull requests, they fixed external storage tough internal just needed some changes. However ril still isn't working, I think that even my phone doesn't detect the sim card. Also I think microphone isnt' working too
At least most functions are working now thanks to you :highfive:
Alonso1398 said:
Thanks a lot for those pull requests, they fixed external storage tough internal just needed some changes. However ril still isn't working, I think that even my phone doesn't detect the sim card. Also I think microphone isnt' working too
At least most functions are working now thanks to you :highfive:
Click to expand...
Click to collapse
Do you patched the patches mentioned by pawitp in thread for grand duos ? ....