Successfully ported. Partially working.
Whats working?
-Touchscreen
-Bluetooth
-GPU
-Camera
-Softkeys
-NFC
-Butter
-SDcard
-ADB
-USB
What's not working?
-Audio
-Wifi
-GSM
-libwvm
-More stuffs not working.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
More Proper Screenshot
Download: http://files.mrks.me/JRN84D_NS.zip (md5: 28e935c14c31f38940b0c9ced0778766)
----------------------------------------------------------------------------------------------------------------------
SDK port by Steve676 (Wifi Working)
http://forum.xda-developers.com/showpost.php?p=28113909&postcount=258 No Gapps
DaXmax said:
Hey guys, i eventually trying to port Jelly Bean on our device, but its a no go, anyone can help here?
Code:
I/Netd ( 9965): Netd 1.0 starting
I/mediaserver( 9964): ServiceManager: 0x40ce2d80
I/AudioFlinger( 9964): Using default 3000 mSec as standby time.
I/CameraService( 9964): CameraService started (pid=9964)
W/AudioFlinger( 9964): findSuitableHwDev_l() loading well know audio hw modules
E/AudioFlinger( 9964): int android::load_audio_interface(char const*, audio_hw_d
evice_t**) wrong audio hw device version 0000
I/AudioFlinger( 9964): loadHwModule() error -22 loading module primary
E/AudioFlinger( 9964): int android::load_audio_interface(char const*, audio_hw_d
evice_t**) wrong audio hw device version 0000
I/AudioFlinger( 9964): loadHwModule() error -22 loading module a2dp
E/AudioFlinger( 9964): int android::load_audio_interface(char const*, audio_hw_d
evice_t**) couldn't load audio hw module audio.usb (No such file or directory)
I/AudioFlinger( 9964): loadHwModule() error -2 loading module usb
E/AudioPolicyManagerBase( 9964): Failed to initialize hardware output stream, sa
mplingRate: 0, format 0, channels 0
E/AudioPolicyService( 9964): couldn't init_check the audio policy (No such devic
e)
E/SchedPolicy( 9964): open of /dev/cpuctl/apps/bg_non_interactive/tasks failed:
No such file or directory
E/BandwidthController( 9965): runIptablesCmd(): failed /system/bin/iptables -t r
aw -N bw_raw_PREROUTING res=256
E/BandwidthController( 9965): runIptablesCmd(): failed /system/bin/ip6tables -t
raw -N bw_raw_PREROUTING res=256
D/MDnsDS ( 9965): MDnsSdListener::Hander starting up
E/Netd ( 9965): Unable to start MDnsSdListener (Invalid argument)
E/SocketListener( 9965): Obtaining file descriptor socket 'mdns' failed: Invalid
argument
I/Netd (10086): Netd 1.0 starting
I/ServiceManager( 72): service 'media.audio_flinger' died
I/ServiceManager( 72): service 'media.player' died
I/ServiceManager( 72): service 'media.camera' died
I/ServiceManager( 72): service 'media.audio_policy' died
I/Netd (10112): Netd 1.0 starting
Click to expand...
Click to collapse
Is this the whole log?
rlasalle15 said:
Is this the whole log?
Click to expand...
Click to collapse
Yes, i already fixed the kernel boot already, thats only the starting, do you want to work together so we can served a working JB till the official one comes?
DaXmax said:
Yes, i already fixed the kernel boot already, thats only the starting, do you want to work together so we can served a working JB till the official one comes?
Click to expand...
Click to collapse
yea I will send you a PM with my gmail addy
I'm not much of a expert but ,
something with audio drivers ? have you tried replacing them
E/AudioFlinger( 9964): int android::load_audio_interface(char const*, audio_hw_d evice_t**) wrong audio hw device version 0000
Click to expand...
Click to collapse
and also check files on bin folder . can't say much without goods on hand unfortunately , doesn't have the bandwidth to download the files right now
Oodie said:
I'm not much of a expert but ,
something with audio drivers ? have you tried replacing them
and also check files on bin folder . can't say much without goods on hand unfortunately , doesn't have the bandwidth to download the files right now
Click to expand...
Click to collapse
yea tons of fmjar edits are in order in addition to the audio files
I'm not good at this part, but one korean developer(jijonheyoni, galaxy s2 korean varient dev) said that this problem can be caused because kernel's library and platform library is not corresponding.....(I'm just translating..)
Sent from my Nexus S using xda app-developers app
ioplkj13 said:
I'm not good at this part, but one korean developer(jijonheyoni, galaxy s2 korean varient dev) said that this problem can be caused because kernel's library and platform library is not corresponding.....(I'm just translating..)
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
yeah , quite possible , since JB kernel is updated ( as i think lookin @ GN's screenshots ) & the kernel should correspond with audio/video drivers
& also there are huge improvements in video & audio in JB even wifi & network i guess .
There are multiple devs for One X and SGS3 that's got a booting and functional port of JB to their devices. You could try contacting one of them.
Sent from my Nexus S using Tapatalk 2
Oodie said:
yeah , quite possible , since JB kernel is updated ( as i think lookin @ GN's screenshots ) & the kernel should correspond with audio/video drivers
& also there are huge improvements in video & audio in JB even wifi & network i guess .
Click to expand...
Click to collapse
The ramdisks arent to much different. There are few new files though. init.trace.rc and init.usb.rc...but other then those its pretty close. Shouldnt we be able to use an ICS boot.img? I could be way off here but we are kinda backporting from a totally different device then what we have. I think a lot of fmjar edits could get it closer.
Have you tried packaging the from with a cm9 kernel, and then simply bring in all libraries, etc. it mentions?
Sent from my Nexus S using Tapatalk 2
treUse said:
Have you tried packaging the from with a cm9 kernel, and then simply bring in all libraries, etc. it mentions?
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Its gonna be a little tougher then that I think. When you bring over all the libs from CM or AOKP then you have to add in all the native methods in fmjar and services jar. I think we are gonna have to strace a lot of this and see what libs are playing nice and what ones arent.
rlasalle15 said:
yea I will send you a PM with my gmail addy
Click to expand...
Click to collapse
ok.
Oodie said:
I'm not much of a expert but ,
something with audio drivers ? have you tried replacing them
and also check files on bin folder . can't say much without goods on hand unfortunately , doesn't have the bandwidth to download the files right now
Click to expand...
Click to collapse
Could be, but the bin is already replaced with the sdk + Gnex's jb bin... And some are still ics because of Nexus S hardware.
rlasalle15 said:
yea tons of fmjar edits are in order in addition to the audio files
Click to expand...
Click to collapse
Neh, Faryaab didn't edit the fm.jar and it worked fine.
ioplkj13 said:
I'm not good at this part, but one korean developer(jijonheyoni, galaxy s2 korean varient dev) said that this problem can be caused because kernel's library and platform library is not corresponding.....(I'm just translating..)
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Oodie said:
yeah , quite possible , since JB kernel is updated ( as i think lookin @ GN's screenshots ) & the kernel should correspond with audio/video drivers
& also there are huge improvements in video & audio in JB even wifi & network i guess .
Click to expand...
Click to collapse
Nope. Kernel doesn't improves anything. It's only the framework.jar and the libs.
rlasalle15 said:
The ramdisks arent to much different. There are few new files though. init.trace.rc and init.usb.rc...but other then those its pretty close. Shouldnt we be able to use an ICS boot.img? I could be way off here but we are kinda backporting from a totally different device then what we have. I think a lot of fmjar edits could get it closer.
Click to expand...
Click to collapse
i edited the ramdisk, so the schedconfig didn't spammed on my log.
Looks like you're either missing libs or you have the incorrect libs in /system/lib/hw
Nope. Kernel doesn't improves anything. It's only the framework.jar and the libs.
i edited the ramdisk, so the schedconfig didn't spammed on my log.[/QUOTE]
What are you porting off of?
tgascoigne said:
Looks like you're either missing libs or you have the incorrect libs in /system/lib/hw
Click to expand...
Click to collapse
I added the power, keystore and timezone? Is that enough?
rlasalle15 said:
What are you porting off of?
Click to expand...
Click to collapse
Stock IMM76D.
twadda218 said:
If you get this up and running it would be a dream! especially since it'll be a daxmax!!!:good:
Click to expand...
Click to collapse
Yer, but i can't confirm to get this working.
Hi,
You are porting Jelly Bean with ICS libs ?
http://forum.xda-developers.com/showthread.php?t=1738197
This guy could help?
Sent from my Nexus S using xda premium
GalaxyUser said:
Hi,
You are porting Jelly Bean with ICS libs ?
Click to expand...
Click to collapse
nope. If i did that, ofc Jelly Bean wont boot.
Looking at the log, it seems like it's missing audio drivers that it is specifically looking for. It looks like the ICS kernels that you may or may not be using is probably missing the specific drivers that Jelly Bean is looking at.
I think it might help if you could maybe port the kernel that was originally compiled for Android 4.1 and ensure that it has the Nexus S drivers instead of the Galaxy Nexus drivers.
This is of course just a hypothesis and I could be absolutely wrong as I'm not a ROM developer.
deltatux
Related
F-Cuk-R : Automated MIUI GB ROM Cooker for FB0 devices
What does one do when their cheap mobile device doesn't get official support from the elite rom developers?
One is forced to experiment and learn to do it himself! But obviously, not everyone is able to invest the time or maybe have the stamina to do it, so here is a solution for those who bought this Android phone thinking its vfm but were disappointed when they could not get those regular "nightly" or "weekly" updates.
I have made a single step Automatic ROM cooker to port all future MIUI GB releases.
All the proprietary FB0 libraries are pre-included in the program and all the steps of the cooking process including recompiling the framework files and modifying the build.prop and update-script are automated.
Features preincluded in the automated process:
mOCk OC (64 MHz - 2 GHz) and Undervolting kernel with 2 way call recording patch
Sony Bravia postprocessing engine
No headset bug and no incoming call volume bug
Native Wifi hotspot feature/tethering working
USB tethering working
Timezone has been set to IST (+5:30)
Ads blocker hosts included and enhanced to block all Google ads
Spare Parts
CM7 camera beside MIUI camera
Angry GPS
Custom and improved GPS.conf for Indian users
Equalizer app
X5 settings
G-sensor calibration app
E-Compass calibration app
Power button app
Compass
The following apps will be automatically removed from the rom:
BugReport.apk
MIUIStats.apk
TelocationProvider.apk
You needn't wipe dalvik cache since the update script automatically does it.
Requirements:
You need Java Runtime Environment 1.6 installed for apktool to work.
Download apktool from here
Also add apktool.jar, apktool.bat and aapt.exe to your system PATH.
This can be done by editing your Windows environment variables manually or copying these files to %WINDIR% or to %SystemRoot%\system32
Please note that this limitation is due to apktool. if you can successfully decompile and recompile using apktool manually, there is no reason why the app won't work.
Else, your rom won't boot as it will lack crucial files like services.jar and framework-res.apk which have to be modified to port the rom.
You need a stable Windows PC.
I have tested this only on Windows XP 32 bit.
Windows Vista/7 and higher may require admin privileges.
I prefer to port MIUI releases for Desire HD but it can possibly handle U8800 releases too.
Step (yes only one):
Just download the rom to be modded and run the F-Cuk-R program
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's it. Your modded rom port will be created in a couple of seconds to minutes (depending on your computer's power)
The app is multithreaded and would thrash your multicore processor and your hard disk / ssd!
Tip: For most efficiency and speed (500% boost), I recommend the use of a ramdisk like me. Google for Gavotte ramdisk driver.
Takes less than a minute for me to port takes 15 minutes to download and 2 hours for me to upload!
But bear in mind, this took me days to code and weeks to accomplish.
I hope it was worth it
Although due care has been taken to keep this bug free and optimal, please do not blame me for any loss monetary or otherwise happening due to the use of this program.
You are free to post any rom you mod/port using this tool but I would appreciate a humble mention if this helped you
Download v1.5
Let me know if it works for you or not!
Man, You're very kind, made for us apps like this,,,
And Thank You Very much sir. Free Radical.
Does this support ICS roms?
You are the MAN !!!!
tarunongo said:
Does this support ICS roms?
Click to expand...
Click to collapse
Nope. I am yet to learn that.
If there was a 2way call recording kernel for ICS, it would definitely overcome my inertia.
For now, I am happy with MIUI GB.
Sent from my Spice MI-410 on my MIUI 2.3.23 port
Hi FR...
I think its amazing,
Thank you
edowar said:
Hi FR...
I think its amazing,
Thank you
Click to expand...
Click to collapse
Your bash script and mk file proved very useful.
If only I knew how to compile from source
You must teach me cm7/cm9 porting! I'll automate it.
Okay I lied.
I accomplished this in less than 10 days from being a total noob to this and I have a full time job
It would be even funnier if you knew what I do for a living :lol:
Sent from my Spice MI-410 on my MIUI 2.3.23 port
So now this forum is going to be flooded with MIUI Roms for our Smartfone
The more the merrier
Btw, anyone tried yet?
Please give me some input whether this is working or not before MIUI 2.3.30.
Sent from my Spice MI-410 on my MIUI 2.3.23 port
Thats cool FR.....
Great.... wil definitely try it ....
After several days I'm off in porting browse xda, then I found this great app.
Very great app FR...!
I've my own also but in bash script and not perfect yet going to add native wifi.
About native wifi, have you found it? I was found it in framework-res.apk at array.xml, several lines has to be changed but I forgot. I was tried but failed to boot. I still out of home, hope today I can continue the work.
Editted: woooww... I just knew that you already knew that... you'll be a real android dev FR....! Hats off and two tumbs for you!
Sent from my CSL-MI410
For native wifi tethering I believe
Code:
<string-array name="config_tether_wifi_regexs">
<item>wl0.1</item>
should be changed to
Code:
<string-array name="config_tether_wifi_regexs">
<item>softap.*</item>
I have just added this to my cooker.
Shall verify and update the first page if it works.
Yes, those lines... but also several lines like ppp and others... sorry I'm not at front of pc, I'm still on the way to home so I can't give you detail. But I think you will easily find them.
Edited: I'll be arrived home in an hour, then I'll try your cooker! And hope we can continue to discuss.
If I'm not wrong, the rest lines should be just several lines below that wl0.*
Sent from my CSL-MI410
DHD rom arrays.xml already has this:
Code:
<string-array translatable="false" name="config_tether_upstream_regexs">
<item>"rmnet\\d"</item>
<item>"wlan\\d"</item>
<item>"ppp\\d"</item>
</string-array>
btw, my build.prop references to wlan0 so I don't think eth0 is needed.
Besides, wifi is working, only tethering is not right?
Free Radical said:
DHD rom arrays.xml already has this:
Code:
<string-array translatable="false" name="config_tether_upstream_regexs">
<item>"rmnet\\d"</item>
<item>"wlan\\d"</item>
<item>"ppp\\d"</item>
</string-array>
btw, my build.prop references to wlan0 so I don't think eth0 is needed.
Besides, wifi is working, only tethering is not right?
Click to expand...
Click to collapse
Yup you're right. How's the result?
Free Radical said:
Your bash script and mk file proved very useful.
If only I knew how to compile from source
You must teach me cm7/cm9 porting! I'll automate it.
Okay I lied.
I accomplished this in less than 10 days from being a total noob to this and I have a full time job
It would be even funnier if you knew what I do for a living :lol:
Sent from my Spice MI-410 on my MIUI 2.3.23 port
Click to expand...
Click to collapse
good program mate. let me try it, but I can't find the download link? or its my operamini problem? or my eyes priblem? hehe
I think build from source like cm7/9 was already automated. just fixing bug is not automated and need more time and resources.
huh, I'm still lazy to learn it again, I must beat my laziness to start build from source again. hahaha
v1.1 has some problem
Shall upload the update later today.
Could not fix wifi issue since recompiling framework-res.apk is giving me boot loops.
I found a bug, when you decompile service.jar, you forgot to add a space char between service.jar file path and the destination folder path.
Sent from my CSL-MI410
CacingKalung said:
I found a bug, when you decompile service.jar, you forgot to add a space char between service.jar file path and the destination folder path.
Sent from my CSL-MI410
Click to expand...
Click to collapse
no that's not it.
(you decompiled my program too ?)
I corrected that, but recompiling framework-res, with or without any changes, still causes the bootloop.
run at which platform?
Windows/Linux/Android?
Hi All,
Who I Am: My name is Mauro Ribeiro I'm from Brazil and I HATE long walks its gets even worst if its on the beach. I have 15+ years of experience on Linux, 5+ on Java. I do work as a Network Admin for a Large Brazilian Company.
Why: It comes my time to help this nice community that gaved me so much.
What: Linux Kernel 3.0.15 based on Samsung sources with Speedmod Patch's.
This kernel DOES NOT HAVE MMC_CAP_ERASE so it SHOULD be safe.
Its basicly Speedmod K3-3 Kernel with A TON OF MODULES. There are modules for USB Ethernet, USB Sound, USB Serial and Much much more.
BE CAREFUL WHEN YOU LOAD MODULES, MODULES USES MEMORY AND MEMORY IS A PRECIOUS RESOURCE.
MODULES ARE AT: /data/local/modules
IF YOU DON'T KNOW HOW TO LOAD A MODULE THIS KERNEL IS NOT FOR YOU.
ITS NOT A DAILY DRIVER KERNEL HAS ALOT OF STUFF. ITS FOR TESTING.
Be patient when I say that I'm working on something, My computer is a P3 with 1 Gig of ram. So everything takes time and I have to work too.
I'm 100% open to sugestions. Wanna chat about this kernel? I'm mdrjr @ freenode! come on IRC and chat with me. Leave this topic for development only.
I'm always at #project-voodoo .. come and chat.
DON'T PM ME. COME AND CHAT
Attached file is a ZIP that SHOULD BE FLASHED THRU CWM!
kernels are at:
http://www.mdrjr.net/kernel
v5:
Now that modules aren't on initramfs anymore
We have USB Serial and USB Wifi adapters!
YAY!
Let your BackTrack / Wifi Sniffing go
Also, moved files from XDA to my Hosting.
v4:
Added some missing stuff.
Build another TON of modules.
To make kernel smaller and friendly on RAM. Modules from now on will be at /data/local/modules.
v3:
Fixed some errors most of the stuff is pre-built inside the kernel now.
Removed USB-Serial Support. Ask me if you need this back.
v2:
Some idiot (ME) forgot that hardcore disable's logging for his kernel I have it enabled now.
Enabled logging and more logging.
v1:
Samsung ICS update 3 + Speedmod Patch K3-3.
Compiled with a tons of modules
modded initramfs
PS: Sorry for the typo on the date or.. i'm posting from the future.
Thanks goes to:
Linux (Linus)
Google (Android)
Samsung (For the phone)
Francisco Franco (For his work that I stoled... sorry, just few lines of code I'm using on this kernel)
Speedmod (For releasing all his work too and making this possible)
Chainfire (Plenty of instructions around and his work for android is HUGE)
Supercurio (Greate guy talked couple of lines with him. And his awesome job on Sound/Video on android)
If I'm missing someone else.. PM and I'll give you credit.
I don t know how to load a module...
I want anyway that the usb module for attach a fiio E 17 is loaded by default.
How to?
Inviato dal mio GT-N7000 con Tapatalk 2
You should not include the modules in the initramfs. The initramfs is always in memory, so this way the modules waste the precious RAM even if not loaded. It is better to have them on the large emmc partition.
BTW, the kernel's copyright license is GPL, a link to the binary should always be accompanied by a link to the source.
MatanZ said:
You should not include the modules in the initramfs. The initramfs is always in memory, so this way the modules waste the precious RAM even if not loaded. It is better to have them on the large emmc partition.
BTW, the kernel's copyright license is GPL, a link to the binary should always be accompanied by a link to the source.
Click to expand...
Click to collapse
Its on the OP KERNEL IS SPEEDMOD KERNEL! Get the source from there. Its the same source.
And again on OP its a NOT A DAILY DRIVEN KERNEL. ITS FOR TESTING ONLY.
gattari said:
I don t know how to load a module...
I want anyway that the usb module for attach a fiio E 17 is loaded by default.
How to?
Inviato dal mio GT-N7000 con Tapatalk 2
Click to expand...
Click to collapse
I don't know what Chipset your USB DAC uses ;( sorry.
mdrjr said:
IF YOU DON'T KNOW HOW TO LOAD A MODULE THIS KERNEL IS NOT FOR YOU.
Click to expand...
Click to collapse
gattari said:
I don t know how to load a module...
I want anyway that the usb module for attach a fiio E 17 is loaded by default.
How to?
Click to expand...
Click to collapse
No no, dont fill development threads with this rubbish - google it and learn - then you can use this
panyan said:
No no, dont fill development threads with this rubbish - google it and learn - then you can use this
Click to expand...
Click to collapse
I simply want to test usb + dac.
I don t able to test no problem I don t test.
Pardon for rubbish.
Inviato dal mio GT-N7000 con Tapatalk 2
gattari said:
I don t know how to load a module...
I want anyway that the usb module for attach a fiio E 17 is loaded by default.
How to?
Inviato dal mio GT-N7000 con Tapatalk 2
Click to expand...
Click to collapse
A lot of USB DAC's are supported by the USB audio soundcard standard. The E7 (note not the E17) is confirmed to be working on S3. Some users have suggested a firmware upgrade for the E17 might solve things. Things are moving along nicely though. It seems Samsung are ahead of us but being tight lipped about it.....
Can't load module.
insmod says
'unknown symbol in module or invalid parameter'
Also I found this, it details what modules the Nook Colour Dev team took to enable usb DAC.
Looks like we're missing a module?
insmod /drv/snd-hwdep.ko
insmod /drv/snd-rawmidi.ko
insmod /drv/snd-usbmidi-lib.ko
insmod /drv/snd-usb-audio.ko
From this page
Also, @mdrjr where can I find you on freenode?
krypton_the_slayer said:
Can't load module.
insmod says
'unknown symbol in module or invalid parameter'
Also I found this, it details what modules the Nook Colour Dev team took to enable usb DAC.
Looks like we're missing a module?
insmod /drv/snd-hwdep.ko
insmod /drv/snd-rawmidi.ko
insmod /drv/snd-usbmidi-lib.ko
insmod /drv/snd-usb-audio.ko
From this page
Also, @mdrjr where can I find you on freenode?
Click to expand...
Click to collapse
#project-voodoo
and Yes, I got that issue as well... rebuilding stuff now.
mdrjr said:
#project-voodoo
and Yes, I got that issue as well... rebuilding stuff now.
Click to expand...
Click to collapse
Another xda dev pointed me to this dmesg output from an s3 when connecting a c media dac
http://pastebin.com/nHmTRUN6
This is something like we'll see on success.
Sent from my GT-N7000 using XDA
nice job
but too many logging may cause battery goes faster?
Anyone test the module for usb dac?
Cmedia I suppose.
Inviato dal mio GT-N7000 con Tapatalk 2
Qoome said:
nice job
but too many logging may cause battery goes faster?
Click to expand...
Click to collapse
Yes.. it may cause battery and RAM usage.
krypton_the_slayer said:
Another xda dev pointed me to this dmesg output from an s3 when connecting a c media dac
http://pastebin.com/nHmTRUN6
This is something like we'll see on success.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Drivers are built-in on V3. You shouldn't need any modules to get it working.
Wow I don't know much about kernels but os this mean I can connect external usb dac like galaxy s3? I like that! Now my note will be an ultimate sound machine!
Sent from my GT-N7000 using XDA
Well done and thanks mdrjr , we have the device (cheap c-media, but it conforms to usb generic audio) recognised, listed under /dev/snd and
alsa-aplay -l
gives
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And also a bunch of new devices listed in /dev/snd
audio1
controlC1
dsp1
mixer1
pcmC1D0c, pcdC1D0p
Now for a bit of alsa.conf hacking!
For others reading, if you have a USB DAC and are rooted on a Samsung based ICS ROM, if you want to test, first, download and flash the kernel from CWM (reboot recovery, flash zip from sdcard, flash M1v3.zip) reboot
then please download Alsamixer from the Market - link below. It will install ALSA components and a handy app, (please be careful with it, you can damage you speakers/possibly hearing!)
https://play.google.com/store/apps/details?id=com.skvalex.alsamixer&feature=nav_result#?t=W251bGwsMSwxLDMsImNvbS5za3ZhbGV4LmFsc2FtaXhlciJd
And install a terminal app
Then in a terminal type these
su
alsa_aplay -l
If you have more than one device listed, should be USB generic audio, then you have advanced to level 1 on the "get usb audio on my note" challenge!
If it says anything other than USB generic audio, let us know what. There is a chance that many more devices can be supported, if they work under a linux environment. So feel free to test there first.
Next up, custom alsa.conf configuration - level 2!
Still testing, but Alsamixer app might yeild some results if you play with it but I think we need an entry in alsa.conf or somewhere first.
Big boss at the end of level 3 will be a custom app for selecting input/output devices
I tried appending this code below in /system/etc/asound.conf
pcm.!default {
type plug
slave {
pcm "hw:1,0"
}
}
This is pretty much what others have been doing (same code to get USB devices working under linux)
And I tried various other ways of doing the same thing but ultimately got the output below each time :-( You can see I used a standard PCM 16bit stereo 44kHz wav file.
[email protected]:/sdcard # alsa_aplay -D plughw:1,0 test.wav
Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
aplay: set_params:1117: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (125011 125012)
PERIOD_SIZE: 5513
PERIOD_BYTES: 22052
PERIODS: (3 4)
BUFFER_TIME: 500000
BUFFER_SIZE: 22050
BUFFER_BYTES: 88200
TICK_TIME: 0
not sure if I'm missing something in asound.conf or if we're missing support in another library.
EDIT:
I've been poking around other sources that have USB audio support working.
One suggestion is that the order of module loading matters, and I wonder how we are affected since you compiled all the drivers into the kernel.
The drivers in order of insertion others are using are as follows
snd-hwdep.ko (this is part of speedmod kernel)
snd-rawmidi.ko
snd-usbmidi-lib.ko
snd-usb-audio.ko
Don't know about the order of these but pretty sure they're essential
snd-mixer-oss.ko
snd-pcm-oss.ko
krypton_the_slayer said:
I tried appending this code below in /system/etc/asound.conf
pcm.!default {
type plug
slave {
pcm "hw:1,0"
}
}
This is pretty much what others have been doing (same code to get USB devices working under linux)
And I tried various other ways of doing the same thing but ultimately got the output below each time :-( You can see I used a standard PCM 16bit stereo 44kHz wav file.
[email protected]:/sdcard # alsa_aplay -D plughw:1,0 test.wav
Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
aplay: set_params:1117: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (125011 125012)
PERIOD_SIZE: 5513
PERIOD_BYTES: 22052
PERIODS: (3 4)
BUFFER_TIME: 500000
BUFFER_SIZE: 22050
BUFFER_BYTES: 88200
TICK_TIME: 0
not sure if I'm missing something in asound.conf or if we're missing support in another library.
EDIT:
I've been poking around other sources that have USB audio support working.
One suggestion is that the order of module loading matters, and I wonder how we are affected since you compiled all the drivers into the kernel.
The drivers in order of insertion others are using are as follows
snd-hwdep.ko (this is part of speedmod kernel)
snd-rawmidi.ko
snd-usbmidi-lib.ko
snd-usb-audio.ko
Don't know about the order of these but pretty sure they're essential
snd-mixer-oss.ko
snd-pcm-oss.ko
Click to expand...
Click to collapse
Loading sequence does matter that's the main reason to leave it to kernel handle.
When you build modules as built-in kernel keeps the loaded all time at ram so you don't have to worry about loading.. its all there.
I'll check and see if snd-mixer-oss and snd-pcm-oss are there...
Meanwhile can you run alsa_aplay -D plughw:1,0 -vvv test.wav
and give us the output? getting that extra verbosity may help.
no difference with more verbosity
Sent from my GT-N7000 using XDA
I've compiled android 4.1.1 for the GalaxyTab 10.1. It's really EXPERIMENTAL, only for those curious to see Jelly Bean working.
NOT WORKING
- Front-facing camera
- 3G & 4G (SCH-I905)
WORKING
- Rear camera (GT-P7510)
- Wi-Fi (thanks to pershoot)
- Audio (thanks to pershoot)
- HW accelerated video (thanks to rmcc)
- Google Now
- Network based location
Pretty much everything else, but things may fail.
Remember that I'm not responsible if something happens to your tablet, flash this at your own risk.
Backup everything you think you'll need in case something goes wrong and a factory reset is needed.
All credit for the kernel goes to pershoot, it's pretty much the same from ICS with minimal changes.
CM10 OR AOSP?
CM10 is a customized ROM with additions to the system: About
AOSP (Android Open Source Project) is android in pure form, just straight out from Google: About
Which one to choose is your decision.
This ROM includes a few additions from CM10, just the necessary so it won't deviate much from AOSP. This additions are:
- Extended boot menu (long pressing power button).
- Performance settings (to control overclock and other settings without an external app).
- Kill app back button.
- Toggle system bar (hide/show system bar - merged from sgt7)
BEFORE INSTALLING
Check that you have the last version of your recovery, and that it's the right one for your model. If you don't do this you'll get assert error 7 when trying to install.
For CWM, go to this thread: [Recovery] ClockworkMod - 5.5.0.4
For TWRP, go to this thread:[Recovery] Team Win Recovery Project (TWRP) - 2.2.0
A full wipe is recommended, also formating /system . (Do this before reporting problems)
DOWNLOADS
Wi-Fi Only (GT-P7510) -> 09-08-12.12-36-jellybean-alpha-p4wifi-sig.zip
Mirror: 09-08-12.12-36-jellybean-alpha-p4wifi-sig.zip (thanks to kingofcomedy)
md5: fac75f1a2168f0d4c36fc0e13f642fb2
sha1: 8c7ac13af63eb145920eac020879f75e97d59da0
Wi-Fi+3G (GT-P7500) -> Coming soon. In the meantime, try the CM10 version.
Verizon LTE (SCH-I905) -> 09-08-12.14-09-jellybean-alpha-p4vzw-sig.zip
Mirror: 09-08-12.14-09-jellybean-alpha-p4vzw-sig.zip
md5: 0a14927a73ca0834ea994ad3128a6d33
sha1: 4aad8f8bcc075cdd59357d2250f76778669f4aab
Google Apps
gapps-jb-20120729.zip
Mirror 01: gapps-jb-20120729.zip
Mirror 02: gapps-jb-20120729.zip (thanks to kingofcomedy)
Mirror 03: gapps-jb-20120729.zip
gapps-jb-20120717-signed.zip
gapps-jb-20120716-signed.zip
Do not flash this version, link only for reference -> gapps-jb-20120726-signed.zip [source]
FLASH SUPPORT
Check this guide: [GUIDE] [HOW-TO] Install Adobe Flash Player on Android 4.1 Jelly Bean
Be aware, it may cause troubles with web surfing, consider this before reporting problems.
VIDEOS
ICS compared to JB (galaxytab 10.1) (thanks to severinca)
Android Jelly bean 4.1.1 Galaxy Tab 10.1 (thanks to illmatic24)
Jelly bean su galaxy tab 10.1 (thanks to spippo [Italian])
Android 4.1 Jelly Bean on the Samsung Galaxy Tab 10.1 (thanks to ljungberg3)
BUILD YOUR OWN
For those interested in building this ROM, you can try my Linux script. It doesn't set the build environment (gcc, git, java, etc), that depends of your distro. But it should make things easier.
Code:
git clone https://github.com/maplesci/jellybeanBuilder.git ~/development/scripts/jellybeanBuilder
You can change the work directories, and be sure to change the paths for the java exports.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
amazing Work Thank you so much!
Great work once you get wifi working we can try it and take it for a spin, going to keep an eye on this threa :good:
yessir!
Appreciate you taking the time to compile this, Maple
Want to share ur device files? I would like to compile for 3g model van and try to fix wifi.
Did you make changes tot kernel?
How to Install I downloaded it a couple of times keep getting assert failed: getprop("ro.product.device") == "p4wifi"
Following this thread. Thanks for the work thus far
ann1hil4tionfyc said:
How to Install I downloaded it a couple of times keep getting assert failed: getprop("ro.product.device") == "p4wifi"
Click to expand...
Click to collapse
Just remove Line 2 and 3 from updater-script file in /META-INF/com/google/android/
anybody any luck with wifi ??
build.prop says wlan0 but on pershoots ics it's name is eth0
E/WifiStateMachine( 285): Failed to load driver!
E/WifiStateMachine( 285): DriverFailedState
130|[email protected]:/ # ifconfig eth0 up
error: SIOCSIFFLAGS (Operation not permitted)
255|[email protected]:/ # ifconfig wlan0 up
error: SIOCGIFFLAGS (No such device)
Aaroneke said:
Just remove Line 2 and 3 from updater-script file in /META-INF/com/google/android/
anybody any luck with wifi ??
build.prop says wlan0 but on pershoots ics it's name is eth0
E/WifiStateMachine( 285): Failed to load driver!
E/WifiStateMachine( 285): DriverFailedState
130|[email protected]:/ # ifconfig eth0 up
error: SIOCSIFFLAGS (Operation not permitted)
255|[email protected]:/ # ifconfig wlan0 up
error: SIOCGIFFLAGS (No such device)
Click to expand...
Click to collapse
Thanks
Aaroneke said:
Want to share ur device files? I would like to compile for 3g model van and try to fix wifi.
Did you make changes tot kernel?
Click to expand...
Click to collapse
Of course, just wait a little, I'm not at my main PC at the moment. Also, I'll try to compile one for the P4, but because I don't have that model, I can't be sure that it will boot.
Aaroneke said:
Just remove Line 2 and 3 from updater-script file in /META-INF/com/google/android/
anybody any luck with wifi ??
build.prop says wlan0 but on pershoots ics it's name is eth0
Click to expand...
Click to collapse
Yeah, that was me playing around and since it doesn't work at the moment, I didn't change it back. eth0 doesn't work either. The problem is that the module doesn't work (at boot it won't load, and loading it manually doesn't help).
MapleSyrup said:
Of course, just wait a little, I'm not at my main PC at the moment. Also, I'll try to compile one for the P4, but because I don't have that model, I can't be sure that it will boot.
Yeah, that was me playing around and since it doesn't work at the moment, I didn't change it back. eth0 doesn't work either. The problem is that the module doesn't work (at boot it won't load, and loading it manually doesn't help).
Click to expand...
Click to collapse
Would it be inappropriate if I complained just for the sake of complaining lol? JK, thanks for the port, I look forward to everything working!!!!
cool.. wanna try the 3G version xD
Damnit.. This was fast ...
Can't wait to have WiFi working.. (no need of Camera for now) !!
Thanks for making this possible.
Pierrick
thanks, i'll be following the thread!
hows project butter on this? lol
Ah I was waiting for this. Thanks a lot. I can't wait for wifi to be working. And the camera? I kinda forgot that this tablet had one since I've been on CyanogenMod ever since januari!
Sent from my GT-P7510 using XDA Premium HD app
gonna give it a try. thanks
Wow, loaded it up and holy crap is the thing ridiculously fast and smooth. Just what this tab needed. I mean, AOKP Milestone 6 is running very nicely too - but this JB Rom is really nice. Once Wifi is resolved I'll run it daily.
badogg said:
Wow, loaded it up and holy crap is the thing ridiculously fast and smooth. Just what this tab needed. I mean, AOKP Milestone 6 is running very nicely too - but this JB Rom is really nice. Once Wifi is resolved I'll run it daily.
Click to expand...
Click to collapse
I only hope this is super smooth when it's finished, hate seeing lag on this thing so much
In other news DAMN that was fast, thanks! Gonna try it out and maybe even try work on it if I haven't forgotten stuff
---------- Post added at 05:39 PM ---------- Previous post was at 05:03 PM ----------
Alright, it's definitely smoother than ICS, but input lag is still ridiculously high. Guess its a hardware thing. I'm gonna try out some of the old troublesome apps, see if they're any smoother. Maybe I won't throw this into the death pile.
GazaIan said:
I only hope this is super smooth when it's finished, hate seeing lag on this thing so much
In other news DAMN that was fast, thanks! Gonna try it out and maybe even try work on it if I haven't forgotten stuff
---------- Post added at 05:39 PM ---------- Previous post was at 05:03 PM ----------
Alright, it's definitely smoother than ICS, but input lag is still ridiculously high. Guess its a hardware thing. I'm gonna try out some of the old troublesome apps, see if they're any smoother. Maybe I won't throw this into the death pile.
Click to expand...
Click to collapse
tried and find some lag on the rom i kind of fell ics a little more "stable" i don't know what word to use but of course it's only alpha and you know i am pretty sure that once samsung release the official ics this will be fantastic as most of the lags and problems on ics are just about it.
This thread is for the development progress of the Dell Streak 7 running Jelly Bean Android 4.1.2 using Cyanogenmod 10 as the basis.
It is now being moved up a version, from Alpha 0.4 to Alpha 1.0.
This reverts us to the ICS-B4 partition layout. The reason being is that Dell decieded to be different and it causes problems with the sdcard fuse daemon. But switching to this layout, it allowed the sdcard daemon to work correctly and give us more space.
Developers:
giveen - CM10 Port / Kernel Updates
geramy - Sound and other fixes.
DJ_Steve - Sound idea that worked.
Thanks:
Cyanogenmod team - for making the port actually pretty easy
geramy - for all your incredible help getting sound going.
snargledorf - basically rebuilding CM9 for the Dell Streak 7 , to which I was able to base my work off of.
DJ_Steve - for teaching me and all the tips and putting up with my annoying questions
My wife - giving me grace and putting up with the hours I put into this
(oops forgot a couple people)
_motley - for clues onto framebuffers and overlays failing, without him it would have never booted
Borkata - for help with wifi and other little hints.
pengus77 - for helping me fix wifi on CM10.1 (and invertly new changes on CM10 had the same problem)
https://github.com/giveen/android_device_dell_streak7
Alpha v1.1E
Working:
Boots!!!
Touchscreen
Hapatic feedback
External SD
Internal Storage (shows full space, can install apps to it, but you cannot store anything on it)
Power button
Brightness
Root
Capacitive buttons
Bluetooth (audio as well, so far the only way audio works)
WIFI
MTP to external SD
Sound
Headphones - are a bit loud and volume control doesn't always work
Speakers - is a bit quiet and sometimes takes a moment for it to adjust volumes
Not Working:
camera (what do you think I am...a miracle worker?)
GPS (turns on but doesn't lock on)
Sensors
What else doesn't work...I"m still checking it all out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recognized Donators:
azrael
Mohamad R. (let me know your screen name and I'll change this )
Robert Trier
Bradley F.
Fixed a bunch and it looks like surfaceflinger is segfaulting, will look at tomorrow morning
My errors
E/Netd ( 79): Unable to open quota2 logging socket
init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead
init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead
init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
init: using deprecated syntax for specifying property 'sys.usb.config', use ${name} instead
F/libc ( 81): Fatal signal 7 (SIGBUS) at 0x4102f1cc (code=2), thread 146 (SurfaceFlinger)
Cannot load library: link_image[1891]: 84 could not load needed library 'libaudio.so' for 'audio.primary.tegra.so' (reloc_library[1306]: 84 cannot locate
E/AudioFlinger( 84): int android::load_audio_interface(char const*, audio_hw_device_t**) couldn't load audio hw module audio.primary (Invalid argument)
I/DEBUG ( 80): pid: 81, tid: 146, name: SurfaceFlinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 80): signal 7 (SIGBUS), code 2 (BUS_ADRERR), fault addr 4102f1cc
D/SensorService( 270): nuSensorService starting...
E/SensorService( 270): couldn't load sensors module (No such file or directory)
W/EntropyMixer( 270): Caused by: libcore.io.ErrnoException: open failed: ENOENT (No such file or directory)
giveen said:
My errors
E/Netd ( 79): Unable to open quota2 logging socket
init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead
init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead
init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
init: using deprecated syntax for specifying property 'sys.usb.config', use ${name} instead
F/libc ( 81): Fatal signal 7 (SIGBUS) at 0x4102f1cc (code=2), thread 146 (SurfaceFlinger)
Cannot load library: link_image[1891]: 84 could not load needed library 'libaudio.so' for 'audio.primary.tegra.so' (reloc_library[1306]: 84 cannot locate
E/AudioFlinger( 84): int android::load_audio_interface(char const*, audio_hw_device_t**) couldn't load audio hw module audio.primary (Invalid argument)
I/DEBUG ( 80): pid: 81, tid: 146, name: SurfaceFlinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 80): signal 7 (SIGBUS), code 2 (BUS_ADRERR), fault addr 4102f1cc
D/SensorService( 270): nuSensorService starting...
E/SensorService( 270): couldn't load sensors module (No such file or directory)
W/EntropyMixer( 270): Caused by: libcore.io.ErrnoException: open failed: ENOENT (No such file or directory)
Click to expand...
Click to collapse
attach your init.rc, init.goldfish.rc and init.streak7.rc files, I guess 2 people looking over this could provide more help than just one
See your PM's
Are you guys "teasing" all us Streak 7 owners with this Jelly Bean Rom thread?
ICS just dropped and Jelly Bean...?
What is the difference and is Jelly Bean going to be a easier build if so?
I thought Jelly Bean was just ascetic changes, not a revamp.
Please tell me you are really developing the rom cause I was about to gift it to a friend but now im holding off.... I would hate to indian give it....
Jb has better performance just like every new version of Android. Also a bunch if new features
Do you have an estimated time of when you want to complete this or is it as ling as it takes?
ashyk36 said:
Do you have an estimated time of when you want to complete this or is it as ling as it takes?
Click to expand...
Click to collapse
Don't ask for ETA's.. just be patient and wait like everyone else, we don't provide ETA's as we could have errors or other variables that could influence the completion of roms (from server going down to zombie apocalypse)
Who has Jelly Bean on the Dell Streak 7 booting right now....yeah this guy does.
I'd be interested in seeing if my flash script is stable enough to work on more then my 1 sucessful test flash.
If/when you're willing to seed me a copy to test stuff on my end, I'd be happy to report back on it. But I have a ton of backlog to keep me busy, so take your time.
Oh: I'm still a little confused, do you have a working version of CWM for ICS partitions?
I can blind-port a version if you give me the geometries of it.
(I'd like to see the output from a live system to check against the nvflash config)
Stuck at boot animation...but I can taste those yummy beans.... work on it tomorrow.
giveen said:
Stuck at boot animation...but I can taste those yummy beans.... work on it tomorrow.
Click to expand...
Click to collapse
get a logcat and see what errors are occurring
This isn't my first rodeo. Lol. Logcat will be up in the morning.
Sent from my Nexus 7
as long as we get everything working I guess its all good
Would love for camera to work.
Sent from my Nexus 7
take HS7R8 camera drivers and cross reference wih nexus 7 ones to see if anything is different (other than addressing... unless its the same in which case it may just work)
You'd need the source code for the camera drivers for that to work.
All we have are the binaries for them
Exactly.
Sent from my Nexus 7
Camera was working in froyo to my knowledge why not give the source for that a try? (unless that too is also just binaries)
LOLIGEN-III (Developers Preview)[Nougat 7.0 themed][CM 7.2 based]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey guys . here is a good news for the loligen series fans.today I am presenting Android nougat 7.0 themed LOLIGEN ROM for sgy duos.this is a developer preview that means that it will have some bugs including the cm7's own bugs.in future these bugs will be fixed by further updates. anyone can try this ROM. and is free to modify it.so here we go.
Source ROM link--http://forum.xda-developers.com/galaxy-y/development/nutella-rom-galaxy-y-t3425087
CONTENTS
+ Bugs
+ Screenstots
+ Downloads
+ Installing Process
+ Credits
BUGS
--Only 1 sim working
--Wifi tethering not working
--FM Radio, Offline charging issues
--Specific CyanogenMod HW animations (CRT animations, Render effects, Rotation Animation)
--USB tethering
--Screenshot Bug(Common cm7 problem :3 )
--White on white in some apps (ex.Root Explorer)
--FC when long tap widget on statusbar
SCREENSHOTS
DOWNLOADS
http://d-h.st/Ob5R
INSTALLING PROCESS
--put the ROM in the SD-card.
--go to recovery
--go to cwm recovery
--wipe data,cache,dalvik-cache,system.
--mount system,data,cache,SD card.
--go to install zip
--choose zip from SD card
--install it
--go back
--reboot system now
--the first boot will take some time to boot up.
--DONE !
CREDITS
@Allah SWT
@shelowe
@raisul2010.5396
@c4lb0r0
@Zane Kilgore
@AuliaYF
@tentenponce
@bieltv.3
@SpaceCaker
@Alberto96
@Lopicl.00
@psyke83
@androidarmv6 team
XDA
@autoradio78
@venkat kamesh
@iamareebjamal
@LolaTion
@MuSaddiq
@potato
Team Optimus nexus me
@BroadcomCM Team
@SpaceCaker
@Lopicl.00
@Mackeif
@savie
@prototype-U
@Kissingmylove
@percy-g2
@PsychoGame
@viper520
@EatHeat
@niyonsv
@droidbuster
@hulgo
@arpan.asr
@HootanParsa
XDA:DevDB Information
LOLIGEN-3.0 [Nougat 7.0 themed], ROM for the Galaxy Y Duos
Contributors
[email protected], [email protected]
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 3.0.x
Based On: CYANOGENMOD 7.2
Version Information
Status: Beta
Current Beta Version: 3.1.0
Beta Release Date: 2016-07-24
Created 2016-07-24
Last Updated 2016-07-25
space for development
Is this the exact S5360 rom? what did you modify ? only the install-script? are 5360 roms fully compatible with 6102? just single-chip instead of dual?
hum.. just installed it.. seems good..
fbs said:
Is this the exact S5360 rom? what did you modify ? only the install-script? are 5360 roms fully compatible with 6102? just single-chip instead of dual?
Click to expand...
Click to collapse
Yes it is exact copy of nougat me S5360 ROM in terms of UI .I have just ported this ROM means made s5360 ROM to work on s6102.I have not only modified the install scripts but also the other things in the rom which made this rom compatible in s6102. S5360 Roms are not fully compatible with s6102 u need to modify them first to work on s6102.
thanks for the explanation.. it's kinda smooth and stable here.. I can test anything if you want..
question: how can I exchange internal with external memory? is there a permanent way without link2sd? I've already partitioned a sdcard with ext2/fat32 partitions but then whats the best way to use it?
and swapping support?
ps.: u can get technical, I know linux, adb access etc
fbs said:
thanks for the explanation.. it's kinda smooth and stable here.. I can test anything if you want..
question: how can I exchange internal with external memory? is there a permanent way without link2sd? I've already partitioned a sdcard with ext2/fat32 partitions but then whats the best way to use it?
and swapping support?
ps.: u can get technical, I know linux, adb access etc
Click to expand...
Click to collapse
Hi, you can refer to this thread it works on zombie kernel:-http://forum.xda-developers.com/showthread.php?t=2751155&page=1
[email protected] said:
Hi, you can refer to this thread it works on zombie kernel:-http://forum.xda-developers.com/showthread.php?t=2751155&page=1
Click to expand...
Click to collapse
this method does not work.. also it keeps telling me that SU needs to be updated, but it fails to update..
08-25 22:57:51.593 I/Superuser( 2499): Result: 3.0
08-25 22:57:51.593 W/System.err( 2499): java.lang.Exception: unknown su
08-25 22:57:51.601 W/System.err( 2499): at com.koushikdutta.superuser.util.SuHelper.checkSu(SuHelper.java:17)
08-25 22:57:51.609 W/System.err( 2499): at com.koushikdutta.superuser.MainActivity$7.run(MainActivity.java:270)
08-25 22:57:52.046 I/ActivityManager( 1579): Displayed com.koushikdutta.superuser/.MainActivity: +1s205ms
08-25 22:57:59.398 E/su ( 2513): stat failed with 2: No such file or directory
08-25 22:57:59.398 W/su ( 2513): request rejected (10012->0 /system/bin/sh)
08-25 22:57:59.406 W/System.err( 2499): java.lang.Exception: non zero result
08-25 22:57:59.406 W/System.err( 2499): at com.koushikdutta.superuser.MainActivity$3.run(MainActivity.java:176)
and since I installed a new zombie kernel, I'm stuck in it's bootscreen.. lol
D:\adb>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
fbs said:
and since I installed a new zombie kernel, I'm stuck in it's bootscreen.. lol
D:\adb>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
U don't need to install zombie kernel loligen 3.0 is already having zombie kernel in it
Sent from my Lenovo P1 using XDA Labs
good rom but no Gapps even playstore not workin well fix this plz
justAmin said:
good rom but no Gapps even playstore not workin well fix this plz
Click to expand...
Click to collapse
Gapps are just bloatware. They take up a lot of space, if you want Gapps u can install it by yourself.
For playstore install an update of it by yourself, and if will be OK
I thought there was a new zombie kernel for it as I couldn't find new governors, overclocking and different i/o schedulers.
And that app2sd stuff is buggy, didn't work, nor swapping.. I think it was made for stock kernel not for CM like this.
ps: Android 6 comes with sdcard->internal natively (Adoption), and ZRAM also.. is it too difficult to put that natively on this rom/CM7 ?
ps2: can't see icons labels/names on launcher.. tried to disable and re-enable that option on holo launcher but didn't work...
fbs said:
I thought there was a new zombie kernel for it as I couldn't find new governors, overclocking and different i/o schedulers.
And that app2sd stuff is buggy, didn't work, nor swapping.. I think it was made for stock kernel not for CM like this.
ps: Android 6 comes with sdcard->internal natively (Adoption), and ZRAM also.. is it too difficult to put that natively on this rom/CM7 ?
ps2: can't see icons labels/names on launcher.. tried to disable and re-enable that option on holo launcher but didn't work...
Click to expand...
Click to collapse
I don't think that adoption of sdcar can be done on any gingerbread running device. That will be much difficult to do so.
U can try another launcher .I think it is a bug because this launcher is highly modded. Or try to y restore any
backup of Holo launcher that is having labels enabled.
Good luck:good:
I couldn't watch a mkv video with mx player.. got the logcat complaining something about "libBRCM_omx_core.so"
Googled for it and found a bigger version of it, replaced it, and now the video works...
https://github.com/vivekkalady/vendor_samsung_totoro/tree/master/proprietary/media
aren't you using these libs?
-rw-r--r-- 1 root root 2192344 Sep 4 02:22 libBRCM_omx_core.so
-rw-r--r-- 1 root root 2171280 Aug 1 2008 libBRCM_omx_core.so.bkp
link is dead
Dowload link is expired
[email protected] said:
U don't need to install zombie kernel loligen 3.0 is already having zombie kernel in it
Sent from my Lenovo P1 using XDA Labs
Click to expand...
Click to collapse
Please update the download link or give me a mirror link.