Related
This is an experimental build for tattoo derived from HTC Buzz soucres and Hero sources:
http://member.america.htc.com/download/RomCode/Source_and_Binaries/buzz-2.6.29-534e5f81.tar.gz
http://member.america.htc.com/download/RomCode/Source_and_Binaries/hero-2.6.29-5f74b252.tar.gz
build for eclair!
I have setup an github repository, you can crab it here:
http://github.com/segway/Htc-tattoo-kernel-2.6.29-for-eclair
There you will find and the config file. Just copy it as .config and you ready to compile!
I test it at donut original HTC version and everything works except camera
(new configuration and drivers) and akm8973 (the problem is at the
struct akm8973_platform_data compass_platform_data with the LAYOUTS and the
driver at drivers/i2c/chips/akm8973.c. If you use the old struct and the driver
drivers/i2c/chips/akm8973.c from original tattoo kernel the compass works!
Maybe we need and a new /system/bin/akm8973 binary?).
What can you do to help me? Ok you can test the kernel with the android 2.1
system (you can grab also the /system/bin/akm8973 binary from buzz to
test if compass works) and send feedback. As i see in the buzz sources
there are several buzz implementations. On one of them there is present
a mt9t013 camera (see arch/arm/mach-msm/board-buzzc.c). This board
has many similarities with tattoo (akm8973, bma150). So we can get binary
files from official roms (for example /system/bin/akm8973).
At dmesg also i get a: "BUG: scheduling while atomic: kmmcd/9/0x00000002"
which is a sched something bug but the kernel continue to boot. I ll try to figure why.
That' s all
Keep hacking to all of you.
Seg
segway_ said:
This is an experimental build for tattoo derived from HTC Buzz soucres and Hero sources:
http://member.america.htc.com/download/RomCode/Source_and_Binaries/buzz-2.6.29-534e5f81.tar.gz
http://member.america.htc.com/download/RomCode/Source_and_Binaries/hero-2.6.29-5f74b252.tar.gz
build for eclair!
I have setup an github repository, you can crab it here:
http://github.com/segway/Htc-tattoo-kernel-2.6.29-for-eclair
There you will find and the config file. Just copy it as .config and you ready to compile!
I test it at donut original HTC version and everything works except camera
(new configuration and drivers) and akm8973 (the problem is at the
struct akm8973_platform_data compass_platform_data with the LAYOUTS and the
driver at drivers/i2c/chips/akm8973.c. If you use the old struct and the driver
drivers/i2c/chips/akm8973.c from original tattoo kernel the compass works!
Maybe we need and a new /system/bin/akm8973 binary?).
What can you do to help me? Ok you can test the kernel with the android 2.1
system (you can grab also the /system/bin/akm8973 binary from buzz to
test if compass works) and send feedback. As i see in the buzz sources
there are several buzz implementations. On one of them there is present
a mt9t013 camera (see arch/arm/mach-msm/board-buzzc.c). This board
has many similarities with tattoo (akm8973, bma150). So we can get binary
files from official roms (for example /system/bin/akm8973).
At dmesg also i get a: "BUG: scheduling while atomic: kmmcd/9/0x00000002"
which is a sched something bug but the kernel continue to boot. I ll try to figure why.
That' s all
Keep hacking to all of you.
Seg
Click to expand...
Click to collapse
I will test this later if I have time
HCDR.Jacob said:
I will test this later if I have time
Click to expand...
Click to collapse
my rom already contain this kernel compiled from source and full functionally.
if u want i can upload only the zImage and the wlan.ko here or u can extract it from my rom
ikxdf said:
my rom already contain this kernel compiled from source and full functionally.
if u want i can upload only the zImage and the wlan.ko here or u can extract it from my rom
Click to expand...
Click to collapse
Can you upload please?
Sent from my HTC Tattoo using XDA App
ikxdf said:
my rom already contain this kernel compiled from source and full functionally.
if u want i can upload only the zImage and the wlan.ko here or u can extract it from my rom
Click to expand...
Click to collapse
I dont think so. You have used the sources from donut kernel from HTC:
http://member.america.htc.com/download/RomCode/Source_and_Binaries/click-656120.tar.gz
I used the sources from buzz and hero kernels to compile a kernel
for tattoo. There are big differences you can check it with diff..
Seg
segway_ said:
I dont think so. You have used the sources from donut kernel from HTC:
http://member.america.htc.com/download/RomCode/Source_and_Binaries/click-656120.tar.gz
I used the sources from buzz and hero kernels to compile a kernel
for tattoo. There are big differences you can check it with diff..
Seg
Click to expand...
Click to collapse
uh...sorry...i haven't read well
i will download it and wil l take a look but i don't think to find big differences in this kernel...
HCDR.Jacob said:
Can you upload please?
Sent from my HTC Tattoo using XDA App
Click to expand...
Click to collapse
yes. this package contain the zImage and the wlan.ko module already compiled.
PS: the wlan.ko module can work only on 2.1 rom. if u need this moudule for 1.6 or 2.2 rom you have to recompile it. don't try to use a wlan.ko module from another rom...it can't work.
What could be the advantages to use the buzz/hero kernel?
You will lose all the tweak for the tattoo (even if they aren't so much).
francians said:
What could be the advantages to use the buzz/hero kernel?
You will lose all the tweak for the tattoo (even if they aren't so much).
Click to expand...
Click to collapse
i think that the htc release kernel already contain all needed patch for a specific devices... use a specific kernel of another device is not correct...you haven't all specific patch for your device and the kernel contain some not necessary (and unknow) patch for another devices...
i think that is only a losing time...
francians said:
What could be the advantages to use the buzz/hero kernel?
You will lose all the tweak for the tattoo (even if they aren't so much).
Click to expand...
Click to collapse
Ok you have a point but this can lead us to port 2.6.32 kernel (even aosp)..
Think that all the sources files at mach_msm directory is developed for
eclair by HTC.
Also extra tweaks for tattoo can always be imported to this kernel.
PS.: I noticed that from this morning the tattoo kernel at http://developer.htc.com/ change the name-link to
HTC Tattoo - Donut - 2.6.29 kernel source code! ;-P
Seg.
ikxdf said:
i think that the htc release kernel already contain all needed patch for a specific devices... use a specific kernel of another device is not correct...you haven't all specific patch for your device and the kernel contain some not necessary (and unknow) patch for another devices...
i think that is only a losing time...
Click to expand...
Click to collapse
Many things at the phone are the same px. proccessor, akm8973, i2c
chipsets and so we can create a kernel with new drivers and designed
for eclair. Camera is the same with the dreams camera where we have
the source for libcamera!
Seg.
segway_ said:
Many things at the phone are the same px. proccessor, akm8973, i2c
chipsets and so we can create a kernel with new drivers and designed
for eclair. Camera is the same with the dreams camera where we have
the source for libcamera!
Seg.
Click to expand...
Click to collapse
htc take a normal kernel....add some patches if necessary and load the needed modules...
now you can load the needed modules in your kernel, and this operation is possible in ALL kernel versions, but you have lose all tatto patches made from htc, if are present.
the only differences form the 2.6.29 kernel made from htc and the normal or all other kernel are the patches made from htc for ONLY TATTOO DEVICE(if are presents...).
ikxdf said:
htc take a normal kernel....add some patches if necessary and load the needed modules...
now you can load the needed modules in your kernel, and this operation is possible in ALL kernel versions, but you have lose all tatto patches made from htc, if are present.
the only differences form the 2.6.29 kernel made from htc and the normal or all other kernel are the patches made from htc for ONLY TATTOO DEVICE(if are presents...).
Click to expand...
Click to collapse
You are wrong! All the mach_msm dir is different!
Implementation has changed on many files in the dir....
So if you want you can look at it if not ok.
End of discussion!
Seg.
segway_ said:
Ok you have a point but this can lead us to port 2.6.32 kernel (even aosp)..
Think that all the sources files at mach_msm directory is developed for
eclair by HTC.
Also extra tweaks for tattoo can always be imported to this kernel.
PS.: I noticed that from this morning the tattoo kernel at http://developer.htc.com/ change the name-link to
HTC Tattoo - Donut - 2.6.29 kernel source code! ;-P
Seg.
Click to expand...
Click to collapse
Why don't you try to download every single kernel patch from 2.6.29 to 2.6.32 or .33 or .35?
patch -p1 < patch-2.6.29.1
patch -p1 < patch-2.6.29.2
ecc..
segway_ said:
You are wrong! All the mach_msm dir is different!
Implementation has changed on many files in the dir....
So if you want you can look at it if not ok.
End of discussion!
Seg.
Click to expand...
Click to collapse
ok... made what you want. if u don't want made a discussion don't open a thread next time, dude!
bye
francians said:
Why don't you try to download every single kernel patch from 2.6.29 to 2.6.32 or .33 or .35?
patch -p1 < patch-2.6.29.1
patch -p1 < patch-2.6.29.2
ecc..
Click to expand...
Click to collapse
You are welcome to release a 2.6.32 kernel for tattoo by patching the
2.6.29 kernel from HTC. Its not hard..... i am waiting... ;-P
Seg
ikxdf said:
ok... made what you want. if u don't want made a discussion don't open a thread next time, dude!
bye
Click to expand...
Click to collapse
Well, i open a thread to have a good discussion on development something not
arguing about your opinions. That's all. Not hard feelings.
Seg.
segway_ said:
You are welcome to release a 2.6.32 kernel for tattoo by patching the
2.6.29 kernel from HTC. Its not hard..... i am waiting... ;-P
Seg
Click to expand...
Click to collapse
I will release it when you will make work the camera on froyo
segway_ said:
Well, i open a thread to have a good discussion on development something not
arguing about your opinions. That's all. Not hard feelings.
Seg.
Click to expand...
Click to collapse
opinion? segaway...you haven't understand nothing...anything made a good work.
bye
ikxdf said:
opinion? segaway...you haven't understand nothing...anything made a good work.
bye
Click to expand...
Click to collapse
I really don't understand what you are saying...
I only can inform the forum i just boot tattoo with kernel 2.6.32...
<6>[ 0.000000] Initializing cgroup subsys cpu
<5>[ 0.000000] Linux version 2.6.32.15-gf922713 ([email protected]) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #2 PREEMPT Mon Sep 6 18:13:54 EEST 2010
<4>[ 0.000000] CPU: ARMv6-compatible processor [4117b362] revision 2 (ARMv6TEJ), cr=00c5387f
<4>[ 0.000000] CPU: VIPT aliasing data cache, VIPT aliasing instruction cache
<4>[ 0.000000] Machine: bahamas
<7>[ 0.000000] find the hwid tag
<7>[ 0.000000] parse_tag_hwid: hwid = 0x1
<4>[ 0.000000] bahamas_fixup:hwid=0x1
<7>[ 0.000000] find the skuid tag
<7>[ 0.000000] parse_tag_skuid: hwid = 0x1fc04
<4>[ 0.000000] bahamas_fixup:skuid=0x1fc04
<7>[ 0.000000] find the engineer tag
<7>[ 0.000000] parse_tag_engineerid: hwid = 0x0
<4>[ 0.000000] bahamas_fixup:engineerid=0x0
<7>[ 0.000000] find the flash id tag
<7>[ 0.000000] parse_tag_monodie: mono-die = 0x0
......
Click to expand...
Click to collapse
Of course many things don't work yet...... This is done after 30 minutes of work!
Seg
Hey guys,
let's try to get Ubuntu working on our tablets.
adbd is included in the images, so you have a root shell over adb
SDE required.
Extract all.
adb push ubu1204.img.ext4 /data/media/
Reboot - SDE - Flash kernel and initrd
Multiboot menu 0.3 - ubu1204.img.ext4 (from the menu to start the ICS, such as "archos.ext4")
Done.
(passwords: ubuntu - ubuntu root - root)
Working:
- Booting on 80G9 and 101G9
- Touchscreen (touchpad mode)
- Keyboard via OTG cable
- Mass storage on rear USB-prt
- SD card automount on plugin
- LCD backlight brightness control via command line, lol
- Networking (incl. WiFi)
Changelog:
0.2:
- Made by szanalmas
- Upgrade to 12.04
- Kernel 3.0.8+
- Working WiFi (try adding a dummy network, then it works), Sound
- Switched from Unity to Gnome Classic
0.1:
- Initial build.
Todo:
- Bluetooth
- Hardware acceleration
- Camera
- Battery
Download v0.2:
Image: Download
SHA: View
Kernel: Download
SHA: View
Download v0.1:
sysroot_ice.img http://hotfile.com/dl/145362762/7e3f710/ubuntu.img.rar.html MD5:2d9dbc775820db5dda281df84ab7db64
initramfs.cpio.gz http://hotfile.com/dl/145366156/8c56f1d/initramfs.cpio.gz.html MD5:150fc53be381ac3247d44226061868af
zImage http://hotfile.com/dl/145366657/34f75c7/zImage.html MD5:4de6efeec193aa5809f2ff871a96ef2d
Thanks to
- szanalmas for upgrade to 12.04, kernel 3.0.8+, WiFi
- letama for provided kernel + initramfs
- trevd for testing on 101G9 and reuploading stuff
- Adam / OPPO
great a1Pha !
but i would like ubuntu and ICE.. (lol)
This can be made. I'll have to check the initramfs tomorrow
Upload done, post edited - have fun @ testing
a1Pha said:
This can be made. I'll have to check the initramfs tomorrow
Click to expand...
Click to collapse
thx , i testing that this morning
wow. I was going to get working on this when my tablet arrives but you beat me to the race.. maybe we can work on it together in the future
Could you post some screenshots of ubuntu on g9?
dual boot
how would you go about dual bopoting i want to get into the whole programming of it just need a pointer to the start of things
TjaXanK said:
wow. I was going to get working on this when my tablet arrives but you beat me to the race.. maybe we can work on it together in the future
Click to expand...
Click to collapse
For sure - just contact me when your tablet has arrived
142857 said:
Could you post some screenshots of ubuntu on g9?
Click to expand...
Click to collapse
Okay, I have edited the first post and added some links to screenshots.
twinnaz said:
how would you go about dual bopoting i want to get into the whole programming of it just need a pointer to the start of things
Click to expand...
Click to collapse
Sorry, I don't understand your question :S
how would i implement a dualboot
You can take the initramfs.cpio.gz posted by letama in another thread (look at the link to Ice Cream Sandwich - the file is inside the archive you download).
Then extract it and have look at the scripts, which are provided there.
Basically you have to get the system to ask you, from which filesystem image you want to boot
yep! you need to install SDE, restart your device, go in the developer menu and flash the initramfs.cpio.gz that letama posted in the ICS post, atleast that's how it was in the Gen8... by the looks of it the SDE menu is the same. Hope I helped
i wait the multi OS install
2.3
4.0
Ubuntu
Nice, I'll give this a go now.
Edit:
Works on the 101G9.
Keyboard Functions through OTG/Host Cable.
USB Mass Storage (Pen Drive) Functions on 3G Stick Port
Not tried anything else yet.
Are you using a lot of the same kernel objects which android is using?
Excellent Work.
alright thanks
trevd said:
Works on the 101G9.
Keyboard Functions through OTG/Host Cable.
USB Mass Storage (Pen Drive) Functions on 3G Stick Port
Are you using a lot of the same kernel objects which android is using?
Click to expand...
Click to collapse
Thank you very much, and also thanks for testing
I am using initramfs + kernel + modules provided by letama for his ICS-build.
By the way - I will upload a new build this night.
I have managed to get basic network functionality via adb + usbcable, so I have upgraded all packages and installed a touchscreen keyboard.
In the new build the LCD backlight brightness is now set to max on boot.
I also have added a user with sudo-permissions, so now settings are saved on reboot (not like in 0.1 where guest sessions were created).
Oh, and I will change the filesystem type from ext3 to ext4.
Still no real progress on WiFi or sound
P.S.: New build will support choosing between booting ICS and Ubuntu
//edit: sry guys, got some problems with my internet provider. i get reconnects every 30 seconds. i hope they get it fixed till tomorrow... sorry for delay, i'm going to upload the stuff tomorrow..
a1Pha said:
Thank you very much, and also thanks for testing
I am using initramfs + kernel + modules provided by letama for his ICS-build.
Click to expand...
Click to collapse
Might be worth giving it a go with a version 3 kernel, you may get some free driver support. although I could be talking nonsense
a1Pha said:
By the way - I will upload a new build this night.
I have managed to get basic network functionality via adb + usbcable, so I have upgraded all packages and installed a touchscreen keyboard.
In the new build the LCD backlight brightness is now set to max on boot.
I also have added a user with sudo-permissions, so now settings are saved on reboot (not like in 0.1 where guest sessions were created).
Oh, and I will change the filesystem type from ext3 to ext4.
Click to expand...
Click to collapse
I activated the root login with my own password from adb and the touchscreen keyboard worked straight away on the 101. It must come with the the drivers preinstalled. I think letma's' done some work into the difference between the 80 and 101.
a1Pha said:
Still no real progress on WiFi or sound
Click to expand...
Click to collapse
I've been playing with this all night. I think the drivers have been integrated in the main linux kernel so you should be able to build your own.
They could some prebuilt binaries out there as the OMAP4 board seems quite a popular board.
Also you might have some joy with this http://dev.omapzoom.org/pub/scm/integration/
It's all Good!
Archos 101 G9, HTC Sensation, HTC Hero
Hi Guys,
A1Pha, sorry, didn't have time to test your build, too much stuff going on...
Here is a quick feedback on wifi that may help you:
In android, here is how it works (from memory, don't have my laptop to check)
1) you need to create a nvs file corresponding to tablet, check android init.rc for the way it's done there...
2) Then when you do need wifi, insmod the tiwlan.ko
3) Then, load firmware (check wlan_loader in android init.rc, you should be able to reuse the command) and nvs. If all goes well up to here, you should be able to do ifconfig tiwlan0 and it should have a mac address.
4) Then start wpa_supplicant. You need the appropriate version of wpa_supplicant, 0.8 I think in android source code. You may want to build source code from android source with the appropriate options to remove android extensions.
Again, this is from memory, I'll try to give you more details tomorrow.
Regarding audio, this is mostly alsa so it shouldn't be impossible, you should be able to re-use the configuration found in archos rootfs in /usr/ sub directories. You have to insmod the proper modules though.
Best,
LeTama
Suggestion for the sound, try running the alsamixer and playing with that... worked in debian...
letama said:
Hi Guys,
A1Pha, sorry, didn't have time to test your build, too much stuff going on...
Here is a quick feedback on wifi that may help you:
In android, here is how it works (from memory, don't have my laptop to check)
.....
Click to expand...
Click to collapse
ahh. Thanks for that letama , You're a fountain of knowledge.
I'll give it a try during the holidays.
I was playing about with wpa_supplicant and android kernel drivers. I didn't have the right magic ) and my kernel knowledge is still in it's early stages (only been on the linux desktop for 1 year).
[UPDATE]2012-08-06 This is not the only way of getting Dongle's working on Android, If widgets are your thing and you doing feel confident working with system files etc then you may be better served using the ppp widget form draisberghof.de, these are the folks who piratically wrote the book on getting dongles working on linux and by extension android.
[UPDATE]2012-08-06 The source to libhuaweigeneric-ril ( github ) has been updated to include fixes made by omegaRed7 - This massively improves the fault tolerance upon RIL Startup, Tests were carried out on the E173s-1 but it should be beneficial to all modems ( I hope ).
[UPDATE]2012-07-28 As the Rom Version is quite old and it doesn't really require it's own rom I've extracted the files required to implement this functionality - Download Here, The Archive contains a README file with installation instructions
IMPORTANT - pppd permission need changing to 6755 also change to ownership to the root account ( Thanks to __DS__ ). you can do this through adb or terminal emulator
Code:
adb shell chown 0:0 /system/bin/pppd
adb shell chmod 6755 /system/bin/pppd
for this to function
[UPDATE]2012-06-25 Added Forked libhuaweigeneric-ril to Github Repo this includes all the changes I've made - Check This Post For Details
[UPDATE]2012-06-23 Added Github Repo - Check This Post For Details
[UPDATE]2012-06-16 THE DOWNLOAD LINK HAS BEEN UPDATED AS THE FILES IN /etc/system/usb_modeswitch WHERE NAMED INCORRECTLY[/UPDATE]
Hi Folks - This post is going to change fairly often, there is still more info to add, I just got bored with typing for now
The Sales Pitch
This rom aims to provides the same "hands free" approach offered by the Archos 3G Key and extends this functionality to Huawei Branded USB Modems.
Introduction
Here is a custom rom I've currently been hacking away at, if feels like I've had it under wraps for months.
That being the case. I'd like to thking on to enable Huawei USB Modems - This is still a WORK IN PROGRESS but It feels like i've been keeping it under wraps for months, So it's time to throw it out there for further testing. So Dongles at the Ready! It could get a little hacky
WARNING
The Full Size USB Slot has been known to fail from moderate use. As such I would recommend using an USB extensions cable for connecting devices.
VERY IMPORTANT NOTES - PLEASE READ
1. This is definitely not an every day use rom on any other device this woud have been deployed as a recovery flashable update. The reasoning behind the rom deployment is it's only one file to copy and youi're ready to go. It is also a tedious task to manually go through (especially on the 100th time
2. Please don't ask a me if a certain device will work or not. It is not helpful on a number of levels,
a) I simply don't know - I don't own the model in question. Further more you can figure it out yourself.
b) The Chances are that you could probably find out the answer without leaving the comfort of xda - The libhuaweigeneric-ril has been passed around xda like a <Insert Well Used Analogy Here> so a quick search of xda may turn up something useful to reassure you.
c) In reality though we are not going to know if your dongle is working until you "Try It Yourself".
3. if you find your device doesn't work then you need to gather all the relevant information to help get a feel of what's going on; See Below
SUPPORTED DEVICES
The theoretical list of supportted devices come from those devices supportted by usb_wwan and option kernelp drivers.
IMPORTANT NOTES - WHAT YOU NEED TO KNOW
In a perfect world you can download/flash the attached update file. Reload your SDE, Plug a USB 3G Dongle and have It connect and go about you day .
This is the ultimate goal and currently what happens on my own device
TROUBLESHOOTING
There's about a 25% based on my current test this won't happen. There are 2 main ways your connection attempt can fail.
1. The UsbStick has not switched to modem mode
2. The ppp connection script failed
Either Way it would be highly useful post the list of system properties, outputs of dmesg and also a full logcat aswell as the vendor/product id from lsusb,
some like this throught the adb
Code:
adb shell getprops
adb shell lsusb
adb shell dmesg
adb logcat -b radio -b system -b main -b events
Please have a glance over it before posting as It may contain information that you would not want others to see!
ROM DETAILS
Android Version: 4.0.3
Archos Version: SDE 4.06
Removed : Nothing
ADDITIONS
init.dongle.rc - initialization script, I wanted to avoid "polluting" any other init file too much
/lib/modules/usb_wwan.ko and /lib/modules/option.ko - USB Drivers for GSM modems
/system/lib/libhuaweigeneric-ril.so - A slightly tweaked version of DerArtem original huaweigeneric-ril
/system/etc/usb_modeswitch - the latest version of the usb-modeswitch-data
/etc/ppp - Added separate gprs scripts to retain compatibility with the Archos datakey
/system/bin/hotplugd - A new native android service; Manages Modeswitching and connection initialization for any Usb Device which has a valid configuration file present.
DOWNLOAD
3G Modem Redist Pack - For use with newer roms
Hotfile - archos.ext4.update.
INSTALL
Unpack zip and copy unpacked update file to the device
Code:
adb push archos.ext4.update /mnt/storage
restart device in sde mode
script should update automatically
KNOWN ISSUES
"3G Stick Connected" Icon remains in notification list after device disconnection.
pppd needs to be executed with elevated privileges.
pppd is not exiting correctly on some occasions and cause reconnection issues when using multiple sticks.
Thanks go to surdu_petru for the base sde, derAtem for his original work on the libhuaweigeneric-ril.so and pretty much every developer who has worked on these dongles with android, I think I've read every thread on XDA regarding this subject
Hi!
Thanks trevd!
I do not have this USB modem ....but you did a good job for those who have this modem ! Good luck...
i have a Huawei E160E
It is possible to add this modle on your rom ?
---------- Post added at 06:46 PM ---------- Previous post was at 06:23 PM ----------
For the buzz in FRANCE (and in the World :-= )
http://www.jbmm.fr/?p=28280
cajl said:
i have a Huawei E160E
It is possible to add this modle on your rom ?
Click to expand...
Click to collapse
Is this a new model ( released this year )? It may already be in there, The easiest thing to do is plug it in.
If you install this app you can find out what the product_id is and then we can find out for sure.
Thanks
no released in 2009
Device Class: Use class information in the Interface Descriptors (0x0)
Vendor ID: 12d1
Vendor Name: Huawei Technologies Co., Ltd.
Product ID: 03eb
Hi trevd.
Thanks for the work.
Before installing your rom, I'd like to know if my Huawei K3565 is or will be supported.
I can't remember when it was released, but it not a new one ; may be 2009 or 2010.
Rackham666 said:
Hi trevd.
Thanks for the work.
Before installing your rom, I'd like to know if my Huawei K3565 is or will be supported.
I can't remember when it was released, but it not a new one ; may be 2009 or 2010.
Click to expand...
Click to collapse
Hi Rackham666
I'd refer back to my first post, I've tried to make it a little more clear what this "rom" exactly is, more a testing ground, my apologises if that wasn't very clear at first glance, So to switch this query right back at you.
After installing my rom, I'd like to know if your Huawei K3565 is supported?.
For my usn dongle , is it ok for you ?
Okay.
I'll try your additions manually when [email protected] V3 will be released by Petru.
Get The Code
Hi Folks.
I've started a github repo if anyone wants to hack on this stuff.... It only contains the code for the hotplug service at the moment but I will obviously add more when I get chance and apply all the proper GPL licenses to it.
A personal word of note : C is not my first language by any stretch ( although it is fast becoming the case ) so If It causes any memory leaks or starts nuclear war I can't be held responsible, however if there is any noob coding errors in there then I'm ready to learn off those more knowledgeable than I. I have a feeling we have some hardcore developers lurking in Archos Development community
Equally If anyone has any fixes drop me a pm and I'll sort commit access on the repo or post them right here in the thread,
The code can be found here https://github.com/trevd
Hi Folks, Me Again!
Just to let you guys know I've added a forked libhuaweigeneric-ril to my github ( https://github.com/trevd )
It includes the changes I made to enable it to work the Archos.
You'll want to clone the ics branch if you want to compile yourself.
cajl said:
For my usn dongle , is it ok for you ?
Click to expand...
Click to collapse
???
I'm not sure I understand what you mean.... can you explain a little more
Thanks
Hi, I'm sorry if I'm bothering you but I've done the steps for installing this but when I get to sde menu nothing happens. You said script should install the update automatically but nothing happens. Is there something else I have to do?
Sorry again and thank you for your work
Sent from my ARCHOS 101G9 using xda premium
alahkel said:
Hi, I'm sorry if I'm bothering you but I've done the steps for installing this but when I get to sde menu nothing happens. You said script should install the update automatically but nothing happens. Is there something else I have to do?
Sorry again and thank you for your work
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
Hi Alahkel
You're not bothering me .... DO I really sound/come across as that grumpy/angry in my first post.... sometimes I get cranky when I don't get enough sleep.... too much time looking at code.... :laugh:
Thanks for having a go, Are you using the official SDE? and have you got a working SDE Rom already installed?
For now I would forget about the rom image and bear with me, I'm working on an installer APK which will probably better help with testing, I'll also put the manual installation method up for those who want to get dirty with adb.
Hi, i succesfully installed your build then, btw running unoff sde. I have a huawei 170something, I don't remember the model, but it's working great with no problems, but using a otg cable only. I didn't get it to work using the big usb slot
Sent from my ARCHOS 101G9 using xda premium
alahkel said:
Hi, i succesfully installed your build then, btw running unoff sde. I have a huawei 170something, I don't remember the model, but it's working great with no problems, but using a otg cable only. I didn't get it to work using the big usb slot
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
That's great news Interesting that you couldn't/haven't got it working on the full size port... It should function the same as the official Archos Stick, You need to switch on the 3G Stick in the settings and the full size slot should "Just Work". I may have missed that little detail out
If that doesn't work your full size slot is maybe broken A not uncommon issue it seems. unfortunately.
Out of interest what network are you on?
I'm just working on the installer now so you won't be stuck with old archos versions.
trevd said:
That's great news Interesting that you couldn't/haven't got it working on the full size port... It should function the same as the official Archos Stick, You need to switch on the 3G Stick in the settings and the full size slot should "Just Work". I may have missed that little detail out
If that doesn't work your full size slot is maybe broken A not uncommon issue it seems. unfortunately.
Out of interest what network are you on?
I'm just working on the installer now so you won't be stuck with old archos versions.
Click to expand...
Click to collapse
Hi, thx for answering. Well of course I turn on the 3g key in settings for big-size usb and my huawei 3gkey is on indeed (led on key) but the tab doesn't recognize that o.o I'm on tim (italy ) Thank you
Sent from my ARCHOS 101G9 using xda premium
Hi trevd,
i'm guessing this won't work on CM9 by JackpotClavin, or would it? If yes, would i install it the same way as described?
Thanks in advance!
Edit: Sorry i'm obviously still running in 1st gear in the morning... There's no 3G support in the CM9 port so there's no way this would just "work"...
Edit2: And confirmation that i need more coffee: Saw your post in CM9 thread about the successful connection with Archos' 3G stick and a Huawei 3G stick, but only through the browser... Any progress on fixing things so the ppp connection is fully usable by other apps & services?
Hi, trevd!
how to launch the modem on a firmware 4.0.7?
I copy these files from your firmware
init.dongle.rc - initialization script, I wanted to avoid "polluting" any other init file too much
/lib/modules/usb_wwan.ko and /lib/modules/option.ko - USB Drivers for GSM modems
/system/lib/libhuaweigeneric-ril.so - A slightly tweaked version of DerArtem original huaweigeneric-ril
/system/etc/usb_modeswitch - the latest version of the usb-modeswitch-data
/etc/ppp - Added separate gprs scripts to retain compatibility with the Archos datakey
/system/bin/hotplugd - A new native android service; Manages Modeswitching and connection initialization for any Usb Device which has a valid configuration file present.
Click to expand...
Click to collapse
I change the init.rc file for init.dongle.rc start
but the Huawei E1550 modem doesn't work
what it is necessary to change still?
Thanks!
=========================
sorry, everything earned, it was necessary to update a modem firmware
Hi deman05
You were nearly there, init.dongle.rc is imported on the very first line of init.rc so you need both files.
You shouldn't have to do anything with the modem firmware as usb_modeswitch will handle turning the modem.
The files required are.
init.rc
init.dongle.rc
/lib/modules/usb_wwan.ko
/lib/modules/option.ko
/system/lib/libhuaweigeneric-ril.so
/system/bin/hotplugd
Also you need the full contents of the following directories
/system/etc/usb_modeswitch
/system/etc/ppp
/system/etc/chatscripts
I've attached the latest versions to this post (hopefully I've not missed anything), you will need to change the permissions on /system/bin/pppd.
chmod 6755 pppd
[EDIT] I did miss something, please see the first post for the correct download link.
The new version also handles a cold boot ( modem plugged in on startup ) scenario.
If you are still having issues please refer to the troubleshooting section in my original post
Thanks
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
celoxhd
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Original dev supporter:
http://www.androidfilehost.com/?w=files&flid=12461
Click to expand...
Click to collapse
Huge thanks and credits to @titanic_fanatic
He ported the sources and provided all needed stuff to build it
Excellent, many thanks for all the work you put into this for us. We very much appreciate it
On the topic of bugs, I only have two (but I really don't mind at all). The screenshot works except for the resulting image is wavy coloured lines and no vibration regardless of the setting.
We've never had either, so I'm not missing them at all, but wanted to let you know.
Take care Phil
Sent from my SGH-I757M using XDA Premium 4 mobile app
titanic_fanatic said:
Excellent, many thanks for all the work you put into this for us. We very much appreciate it
On the topic of bugs, I only have two (but I really don't mind at all). The screenshot works except for the resulting image is wavy coloured lines and no vibration regardless of the setting.
We've never had either, so I'm not missing them at all, but wanted to let you know.
Take care Phil
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Added you to credits on the device page in main thread and here in OP :good:
screen shots: forget it, I should disable it once for all on new devices. Sadly, we have no working thing for most new devices. Only some Sammy and the mako did work
vibration: can you provide the path for vibrator?, it should be in kernel drivers I guess. Currently I use:
Code:
/sys/class/timed_output/vibrator/enable
We echo some msec value there and it Bzzzzz for that msec
Phil3759 said:
Added you to credits on the device page in main thread and here in OP :good:
screen shots: forget it, I should disable it once for all on new devices. Sadly, we have no working thing for most new devices. Only some Sammy and the mako did work
vibration: can you provide the path for vibrator?, it should be in kernel drivers I guess. Currently I use:
Code:
/sys/class/timed_output/vibrator/enable
We echo some msec value there and it Bzzzzz for that msec
Click to expand...
Click to collapse
That's the correct path Maybe the driver isn't loading properly... I'll see if I can get a dmesg Log when booting recovery to see if the driver actually loads
Sent from my SGH-I757M using XDA Premium 4 mobile app
Vibrator Fixed
Hey @Phil3759, I did a whole lot of investigating tonight and have figured out and fixed the vibration issue. I discovered that it was trying to load the module from /system/lib/modules/vibrator.ko. This is my roms ko file and is currently for cm10.2. The kerenel I setup for this recovery is our cm11 kernel and uses a different module (compiled against that kernel). It was trying to load the cm10.2 module from my rom into the cm11 kernel which obviously doesn't work, so I split the recovery.img added the correct module at /tmp/system/lib/modules added the necessary lines to init.recovery.qcom.rc and repackaged the kernel and new ramdisk.
I have flashed this and tested it. it works like a charm now Can you replace the version in your repo with this new one?
titanic_fanatic said:
Hey @Phil3759, I did a whole lot of investigating tonight and have figured out and fixed the vibration issue. I discovered that it was trying to load the module from /system/lib/modules/vibrator.ko. This is my roms ko file and is currently for cm10.2. The kerenel I setup for this recovery is our cm11 kernel and uses a different module (compiled against that kernel). It was trying to load the cm10.2 module from my rom into the cm11 kernel which obviously doesn't work, so I split the recovery.img added the correct module at /tmp/system/lib/modules added the necessary lines to init.recovery.qcom.rc and repackaged the kernel and new ramdisk.
I have flashed this and tested it. it works like a charm now Can you replace the version in your repo with this new one?
Click to expand...
Click to collapse
If you update your device tree, it would be even better. That way, my next updates won't be affected again
Phil3759 said:
If you update your device tree, it would be even better. That way, my next updates won't be affected again
Click to expand...
Click to collapse
I just finished updating my device tree with the necessary fixes for the vibrator to work in recovery
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6f005f4045551e48adfa0ac228641bf8d6a12128
Also, not that I care, but Amarullz was able to get screenshots working in the latest AromaInstaller (Flamboyan I think). If your interested, maybe ask him what he did to get it to work. He could probably point you to the commits
Take Care
titanic_fanatic said:
I just finished updating my device tree with the necessary fixes for the vibrator to work in recovery
https://github.com/titanic-fanatic/...mmit/6f005f4045551e48adfa0ac228641bf8d6a12128
Also, not that I care, but Amarullz was able to get screenshots working in the latest AromaInstaller (Flamboyan I think). If your interested, maybe ask him what he did to get it to work. He could probably point you to the commits
Take Care
Click to expand...
Click to collapse
Looking at it quickly: why that first extra / at end of copy files?
Also, won't be cleaner to use standard path like /lib/modules?
/tmp can be wiped and modified by installers and recovery
Phil3759 said:
Looking at it quickly: why that first extra / at end of copy files?
Also, won't be cleaner to use standard path like /lib/modules?
/tmp can be wiped and modified by installers and recovery
Click to expand...
Click to collapse
The first / is because it's part of a set of chained product copy files directives:
# Ramdisk
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/ramdisk/init.qcom.usb.rc:root/init.qcom.usb.rc \
# BT firmware
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/firmware/bcm4330B1.hcd:system/etc/firmware/bcm4330B1.hcd \
# Needed for vibrator to work in recovery
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/recovery/root/lib/modules/vibrator.ko:recovery/root/lib/modules/vibrator.ko \
device/samsung/celoxhd/recovery/root/init.recovery.qcom.rc:recovery/root/init.recovery.qcom.rc
Click to expand...
Click to collapse
I did this only to adhere to the existing pattern in my device.mk file, the one appended to the first PRODUCT_COPY_FILES was already there from when I forked the project and took that as being a set of chained commands. If this is wrong, I will change it
I definitely see your point on the /tmp dir. I here the commit that fixes that
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/61da6be2d60a03797ddc31c0187cc5c62bb3a97a
titanic_fanatic said:
The first / is because it's part of a set of chained product copy files directives:
I did this only to adhere to the existing pattern in my device.mk file, the one appended to the first PRODUCT_COPY_FILES was already there from when I forked the project and took that as being a set of chained commands. If this is wrong, I will change it
I definitely see your point on the /tmp dir. I here the commit that fixes that
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/61da6be2d60a03797ddc31c0187cc5c62bb3a97a
Click to expand...
Click to collapse
I uploaded 6.01.2 with your fixed vibrator :good:
PRODUCT_COPY_FILES:
Maybe I am wrong, but usually, in make files, only the last element has no trailing /
Code:
# Ramdisk
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/ramdisk/init.qcom.usb.rc:root/init.qcom.usb.rc
xxx-yyy \
zzz-pppp\
last_one
# BT firmware
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/firmware/bcm4330B1.hcd:system/etc/firmware/bcm4330B1.hcd
# Needed for vibrator to work in recovery
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/recovery/root/tmp/system/lib/modules/vibrator.ko:recovery/root/tmp/system/lib/modules/vibrator.ko \
device/samsung/celoxhd/recovery/root/init.recovery.qcom.rc:recovery/root/init.recovery.qcom.rc
Also, just for info, my full gui builds need these, often in cm.mk:
Code:
TARGET_SCREEN_HEIGHT := 1280
TARGET_SCREEN_WIDTH := 720
Phil3759 said:
I uploaded 6.01.2 with your fixed vibrator :good:
PRODUCT_COPY_FILES:
Maybe I am wrong, but usually, in make files, only the last element has no trailing /
Code:
# Ramdisk
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/ramdisk/init.qcom.usb.rc:root/init.qcom.usb.rc
xxx-yyy \
zzz-pppp\
last_one
# BT firmware
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/firmware/bcm4330B1.hcd:system/etc/firmware/bcm4330B1.hcd
# Needed for vibrator to work in recovery
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/recovery/root/tmp/system/lib/modules/vibrator.ko:recovery/root/tmp/system/lib/modules/vibrator.ko \
device/samsung/celoxhd/recovery/root/init.recovery.qcom.rc:recovery/root/init.recovery.qcom.rc
Also, just for info, my full gui builds need these, often in cm.mk:
Code:
TARGET_SCREEN_HEIGHT := 1280
TARGET_SCREEN_WIDTH := 720
Click to expand...
Click to collapse
It seems that the extra \ was introduced in our JB branch and has never been fixed. Various examples in googles repo confirm that you are correct. I have removed the extra \ and added the properties you mentioned above to the cm.mk file. Here is the relevant commit:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6ce5f482d63cd70cf64a3d1428ad2428844e23cb
Hey @Phil3759, I just downloaded and flashed the latest version. Thanks kindly for the update
I see that I made a boo boo and forgot to update the path to the vibrator in the init.recovery.qcom.rc file and so the vibrator isn't loading. I've fixed that with the following commit:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/b87b3267d75a0de1bb94f68850ae6986ac4dde92
One other thing, for some reason the background is tiled 4 times as if my devices dimensions were not set correctly. I do have that set in my cm.mk file. Here was the commit for that:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6ce5f482d63cd70cf64a3d1428ad2428844e23cb
Is there somewhere else I'm supposed to specify the device screen dimensions?
Thanks again for the new version and I apologize for missing that path in the init.recovery.qcom.rc.
titanic_fanatic said:
Hey @Phil3759, I just downloaded and flashed the latest version. Thanks kindly for the update
I see that I made a boo boo and forgot to update the path to the vibrator in the init.recovery.qcom.rc file and so the vibrator isn't loading. I've fixed that with the following commit:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/b87b3267d75a0de1bb94f68850ae6986ac4dde92
One other thing, for some reason the background is tiled 4 times as if my devices dimensions were not set correctly. I do have that set in my cm.mk file. Here was the commit for that:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6ce5f482d63cd70cf64a3d1428ad2428844e23cb
Is there somewhere else I'm supposed to specify the device screen dimensions?
Thanks again for the new version and I apologize for missing that path in the init.recovery.qcom.rc.
Click to expand...
Click to collapse
About background image:
I think this is the cause:
https://github.com/CyanogenMod/android_device_samsung_celox-common/blob/cm-11.0/celox-common.mk#L45
called here:
https://github.com/titanic-fanatic/...xhd/blob/philz-recovery-cm-11.0/device.mk#L37
Your cm.mk settings are overridden
Maybe just move device resolution from cm.mk to device.mk after Line 37
About the vibrator: do you need exfat through kernel modules? If yes, let me know. It is much faster than fuse. For that, you'll need to compile the kernel with samsung exfat sources. I can guide you for that
Else, link me to what exactly is needed in your kernel for the vibrator to work. If it is just a change in defconfig, I can add it and compile along exfat
Phil3759 said:
About background image:
I think this is the cause:
https://github.com/CyanogenMod/android_device_samsung_celox-common/blob/cm-11.0/celox-common.mk#L45
called here:
https://github.com/titanic-fanatic/...xhd/blob/philz-recovery-cm-11.0/device.mk#L37
Your cm.mk settings are overridden
Maybe just move device resolution from cm.mk to device.mk after Line 37
About the vibrator: do you need exfat through kernel modules? If yes, let me know. It is much faster than fuse. For that, you'll need to compile the kernel with samsung exfat sources. I can guide you for that
Else, link me to what exactly is needed in your kernel for the vibrator to work. If it is just a change in defconfig, I can add it and compile along exfat
Click to expand...
Click to collapse
I see it, and now as you've recommended I reset the values after calling celox-common.mk. The commit is here:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/cd44b44b7cbb0ddb3b649ac5c4f8d5d1f51d7998
As for exfat, I will be adding this when I have some time to rebuild this kernel. We can worry about exfat for the next time you do device updates and hopefully I'll have it ready by that time. I have your main thread in my subscriptions, so I'll know when your ready to release a new version and will remind you to sync with my repo at that time
Thanks for catching that issue with screen size
titanic_fanatic said:
I see it, and now as you've recommended I reset the values after calling celox-common.mk. The commit is here:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/cd44b44b7cbb0ddb3b649ac5c4f8d5d1f51d7998
As for exfat, I will be adding this when I have some time to rebuild this kernel. We can worry about exfat for the next time you do device updates and hopefully I'll have it ready by that time. I have your main thread in my subscriptions, so I'll know when your ready to release a new version and will remind you to sync with my repo at that time
Thanks for catching that issue with screen size
Click to expand...
Click to collapse
np
Let me know if you need info to add exfat
I will update with the current fixes asap
Phil3759 said:
np
Let me know if you need info to add exfat
I will update with the current fixes asap
Click to expand...
Click to collapse
Can I get a link to these fixes please when you have it ready
titanic_fanatic said:
Can I get a link to these fixes please when you have it ready
Click to expand...
Click to collapse
https://github.com/PhilZ-cwm6/GE-Ed...mmit/a8963ca853cfd88466716f8a25434d5c469a2bb9
It is just adding the exfat folder in drivers and edit the makefile with -y to have it built as static. No need to separate modules
Phil3759 said:
https://github.com/PhilZ-cwm6/GE-Ed...mmit/a8963ca853cfd88466716f8a25434d5c469a2bb9
It is just adding the exfat folder in drivers and edit the makefile with -y to have it built as static. No need to separate modules
Click to expand...
Click to collapse
Excellent. I'll add it soon, it should be a pretty quick process.
Quick question though since we are currently having some issues with random reboots in all of my latest builds of cm-11.0. My kernel was updated at some point, and that's when my builds started having random reboots. They are actually not random, but seem rather consistent.
My question is this, do you think this will affect operation in recovery? I believe the reboots are due to kernel panic from a graphics related issue but am not sure if that will only affect the rom and not recovery.
If this might affect recovery, I think I'll build it as a module so I can just add it to my device tree instead of having to update the entire zImage. This will at least give us the old working kernel with the exfat module included.
What do you think?
Sent from my SGH-I757M using XDA Premium 4 mobile app
titanic_fanatic said:
Excellent. I'll add it soon, it should be a pretty quick process.
Quick question though since we are currently having some issues with random reboots in all of my latest builds of cm-11.0. My kernel was updated at some point, and that's when my builds started having random reboots. They are actually not random, but seem rather consistent.
My question is this, do you think this will affect operation in recovery? I believe the reboots are due to kernel panic from a graphics related issue but am not sure if that will only affect the rom and not recovery.
If this might affect recovery, I think I'll build it as a module so I can just add it to my device tree instead of having to update the entire zImage. This will at least give us the old working kernel with the exfat module included.
What do you think?
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you'll end up with magic number mismatch errors
There are some hacks to force loading on mismatch, but, in my previous experience, they failed on many devices
the drivers must be compiled along the zImage
Now, why don't we drop to celox-common kernel which seems to work fine on skyrocket and other phones?
Phil3759 said:
you'll end up with magic number mismatch errors
There are some hacks to force loading on mismatch, but, in my previous experience, they failed on many devices
the drivers must be compiled along the zImage
Now, why don't we drop to celox-common kernel which seems to work fine on skyrocket and other phones?
Click to expand...
Click to collapse
It is for the most part the same kernel with the few quirks of my device. More notably is my devices display drivers are mipi s6e8aa0_720hd and had to fork the kernel to apply some fixes to that driver as it's not maintained by cm.
Hmmm. I'll be the guinea pig. I will build with the new kernel and I'll test the recovery before you upload. I just think that the issue might be a memory leak in android causing the kernel to panic (overlay issue) and might not have an effect in recovery since its graphics are very basic.
I'll let you know when it's ready
Sent from my SGH-I757M using XDA Premium 4 mobile app
General informations:
This thread's aim is only to represent a central meeting and discussion point for BCM21553 developers and, in particular, for the open Kernel/ROM sources development for the Samsung Galaxy Pocket GT-S5300 (codenamed Cori).
Information for common users:
As already described in the previous section, if you are not a developer, please restrict your posts to the general discussion thread so that developers can maintain good communication. Every post that is not strictly respecting these rules will be reported to the forum moderators. Thanks for your understanding.
For any other BCM21553 device related question or information, please, use this thread as a reference point, instead:
[DEVS ONLY][BCM21553 series] CyanogenMod 11 for BCM21553 Development Discussion
As someone already might know, I'm streambinder, from MoltenMotherBoard team.
I have already followed some projects for the GT-S5300, but especially kept in contact
with some of the events related to the porting of ROM and Kernel sources for BCM21553 chipset based devices.
In this precise moment, the sources in my possession allow you to be able to compile
a bugfree CWM 5.0.2.8 (based on CyanogenMod 7 code) with a kernel based on the Samsung stock one.
The only - fundamental - problem was due to the fact that unless I hadn't used the prebuilt INIT binary
token in the Samsung stock firmware boot.img, the phone would not work - or, better, boot up.
This means that until the situation - regarding this issue - doesn't change, our access to the porting of custom ROM
would be barred.
Recently, I decided to give Cori another chance and rework my sources, looking at the wonderful work brought
by the BroadcomCM team on CyanogenMod 9 (in particular, thanks to @bieltv.3 and @Alberto96) and @psyke83 on CyanogenMod 11.
They've not only been able to run these two ROMs in a more or less crude way, but this developer has been able to write
the necessary strings to make the INIT binary of some of these BCM21553 devices opensource.
Strong of this informations, I readjusted some of the sources of BroadcomCM's CyangenMod 9, which includes
all the progress carried out by both the team and psyke83, in order to make them work even on Cori,
and am now next to the first test of the CWM 6.X.X.X, based on IceCreamSandwich code.
At the same time, @akhbh is working on the KitKat code based CWM.
I hope I can give more information about any progress as soon as possible.
The General Discussion thread for non-development issues is here:
*.[DISCUSSION] CyanogenMod 11 For Galaxy Pocket GT-S5300 Discussion Thread
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
streambinder said:
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
Click to expand...
Click to collapse
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
akhbh said:
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
Click to expand...
Click to collapse
Perfect.
Which kernel have you based your build on?
streambinder said:
Perfect.
Which kernel have you based your build on?
Click to expand...
Click to collapse
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
akhbh said:
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
Click to expand...
Click to collapse
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
streambinder said:
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
Click to expand...
Click to collapse
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
akhbh said:
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
Click to expand...
Click to collapse
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
streambinder said:
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori | github.com
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
Click to expand...
Click to collapse
have u tried to build cwm v6 from cm9 source ??
cleverior.ipul said:
have u tried to build cwm v6 from cm9 source ??
Click to expand...
Click to collapse
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
akhbh said:
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
Click to expand...
Click to collapse
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
streambinder said:
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
Click to expand...
Click to collapse
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources coz as said earlier, his kernel is used. Well, we were working together to bring cm11 but weren't successful
akhbh said:
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources.
Click to expand...
Click to collapse
Ok, please send it to me, will compare it with my package.
streambinder said:
Ok, please send it to me, will compare it with my package.
Click to expand...
Click to collapse
Here it is:
http://www.4shared.com/zip/1nKFbOJ2ba/ccccGetux_CM11.html
streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
here the link source https://github.com/cleverior/android_kernel_samsung_cori
i've changed the board name. If your device can not boot after using the zImage from this source, then rename init.bcm21553.rc to init.gt-s5300.rc.
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
akhbh said:
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
Click to expand...
Click to collapse
Sincerely don't what are you talking about.
Anyway, have to try to understand where's the problem with the not-booting CWM.
Will try with your sources and let you know.