[DEV] Kernel Editing/HTC PUCCINI ROM DEVELOPMENT - Eee Pad Transformer Android Development

UPDATE, LOOKS LIKE IT'S GOING TO BE (ALMOST) IMPOSSIBLE TO PORT ENTIRE ROM, LOOKING INTO BITS AND PIECES THAT CAN BE PULLED.
here's the leak, for those who want it: http://forum.xda-developers.com/showthread.php?t=1240772
My progress. My kernel won't boot. I changed the bootclasspath and added some things to the init.rc, but it won't work, rebooting BEFORE THE CAMERA CLICK. If i flash clemsyn 3.1 v18 on top, the camera clicks, but it still reboots.
No logcat.
Anyone have any ideas? obviously it's not just the kernel, but the rom. I deleted stuff from the rom to fit onto the transformer, and hopefully I didn't mess it up. But i'm good at cramming **** onto the G1 and generally know what to use.
My kernel is based on prime 1.6. This is a 3.1 rom. I edited the bootclasspath and changed default.prop according to the puccini boot.img. both extracted perfectly, and my new kernel packaged up all nice. It, however, does not boot.
Any ideas are welcome. There wasn't a bootloader update in 3.2 or something that would prevent booting a 3.1 rom? food for thought.
If anyone wants me to upload my work so far, let me know.
Thanks for your input,
jcarrz1
p.s. the only part I wasn't sure about was the mkbootimg options, based on what RaYmaN said in another thread, http://forum.xda-developers.com/showthread.php?t=1121379 I followed his advice to omit cmdline option. I think that's the correct way, anyone else interpret differently?
Rayman's tools were the heart of this effort, thanks a bunch. Also to Roach2010 for a solid 3.1 base.
Jcarrz1
Teaser
{
"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"
}
Thank me for my efforts

Isn't HTC using a Qualcomm soc? That could mean they are using a different instruction set which cause the reboot.
could be the reason why they got it booting on the flyer and we don't have success on tegra devices
Let's see if someone else with a tegra device is successful and gets it booting.
Edit: sometimes I should read more carefully. If your kernel doesn't boot there is something really strange going on. Can't you flash stock 3.1, replace the boot loader and try your port again?

missing some info about the images your using ..
you have build the kernel , oke but witch ramdisk did you used?
witch kernel did you used ?
kernel config file?

Is it a 3.1 or a 3.2 rom?

one word, NEON

gnufabio said:
Is it a 3.1 or a 3.2 rom?
Click to expand...
Click to collapse
The OP said in the first post that it is a 3.1 Rom
Mark.

The following is from surfaceflinger
Code:
Attribute Section: aeabi
File Attributes
Tag_CPU_name: "ARM v7"
Tag_CPU_arch: v7
Tag_CPU_arch_profile: Application
Tag_ARM_ISA_use: Yes
Tag_THUMB_ISA_use: Thumb-2
Tag_VFP_arch: VFPv3
Tag_NEON_arch: NEONv1
Tag_ABI_PCS_wchar_t: 4
Tag_ABI_FP_denormal: Needed
Tag_ABI_FP_exceptions: Needed
Tag_ABI_FP_number_model: IEEE 754
Tag_ABI_align8_needed: Yes
Tag_ABI_enum_size: int
Tag_ABI_HardFP_use: SP and DP
In short the puccini rom will never run on a Tegra2 device, ANY Tegra2 device, as the Tegra2 SoC lacks NEON support

lilstevie said:
The following is from surfaceflinger
Code:
Attribute Section: aeabi
File Attributes
Tag_CPU_name: "ARM v7"
Tag_CPU_arch: v7
Tag_CPU_arch_profile: Application
Tag_ARM_ISA_use: Yes
Tag_THUMB_ISA_use: Thumb-2
Tag_VFP_arch: VFPv3
Tag_NEON_arch: NEONv1
Tag_ABI_PCS_wchar_t: 4
Tag_ABI_FP_denormal: Needed
Tag_ABI_FP_exceptions: Needed
Tag_ABI_FP_number_model: IEEE 754
Tag_ABI_align8_needed: Yes
Tag_ABI_enum_size: int
Tag_ABI_HardFP_use: SP and DP
In short the puccini rom will never run on a Tegra2 device, ANY Tegra2 device, as the Tegra2 SoC lacks NEON support
Click to expand...
Click to collapse
Yup. Although if you swap the surfaceflinger to a Tegra2 generic one, it *should* work.
I'm sure that the kernel will NEVER boot on our device, as it's for Qualcomm platform, not Tegra2. But the ROM itself worth playing around, mostly if we can get the nice Launcher with themes.

fonix232 said:
Yup. Although if you swap the surfaceflinger to a Tegra2 generic one, it *should* work.
I'm sure that the kernel will NEVER boot on our device, as it's for Qualcomm platform, not Tegra2. But the ROM itself worth playing around, mostly if we can get the nice Launcher with themes.
Click to expand...
Click to collapse
yes, you could swap the flinger, but you still have the problem of everything else,
the point of that was not that just this one binary, but the whole rom, that also means the launcher and everything use NEON.
Also the kernel not running is a given, that is hw specific. My point is the ROM itself will not run

Thanks everybody for your advice. I stupidly assumed that "oh look it's a 1280x800 honeycomb tablet" lets port the software.
However, my kernel question persists; what did I do wrong? is it right to use mkbootimg in the way I did?
Thanks everyone.

I know nothing about this, but I just wanted to say how cool this is and thanks. Please don't pull a meejay and run out on us after giving us a release date Hopefully this goes smoother than porting TouchWiz UX

Isn't there a sense port that's partially functional on galaxy s devices? If so, then this is entirely possible with hours of dev work done on it to me, the only issue I see is the NEON problem, if that gets a work around the problems are the same problems involved in any port to any device, this is the coolest idea I've seen for my tf, I'll be watching development closely

How can i extract the System.img from the Leak?

Kevterminator said:
How can i extract the System.img from the Leak?
Click to expand...
Click to collapse
use Linux Reader

Great work man keep in touch

Might be worth trying the new hc update leak for the htc flyer. The hardware on the flyer isn't too much different other than processor so might be easier.
Sent from my T-Mobile G2 using xda premium

Having a different processor can mean COMPLETELY different sets of features supported by the processor. A lot of HTC's additional software (Sense and such) runs hand in hand with processor features as well as specific hooks into the kernel and frameworks that will not work unless on hardware capable of supporting it (among other things). Hence, why 99.9% of all Sense ports have failed in the past.

This all sounds like a wicked idea to me! Keep up the good work dude, it would be great to see it boot!

jcarrz1 said:
Thanks everybody for your advice. I stupidly assumed that "oh look it's a 1280x800 honeycomb tablet" lets port the software.
However, my kernel question persists; what did I do wrong? is it right to use mkbootimg in the way I did?
Thanks everyone.
Click to expand...
Click to collapse
Yes it's the correct way.
For recompile the stock kernel refer to this: http://forum.xda-developers.com/showthread.php?t=1197147
for creating the boot image :http://forum.xda-developers.com/showthread.php?t=1193737
Good luck!

HTC
Anyone no if i can install the HTC Clock on my Transformer?

Related

[KERNEL] Unofficial Fresh Toast thread

I'm starting this thread as I'd like a place to talk about the Fresh Toast kernel as it doesn't look like one has been started yet. If flipz decides to make his own thread at some point then we can delete this one.
The Following is from http://geekfor.me/evo/21/fresh-toast-experimental/
Geek For Me is proud to release:
Fresh Toast Custom Kernel for your Sprint Evo 4g
Experimental, and only available through Fresh Updater.
Fresh Toast was a popular collaboration rom by toastcfh and myself for the CDMA Hero. I am proud to announce that it’s now available for the Evo! Rather than being offered as a separate rom it is now going to be offered as an update/patch for Fresh Evo. If you are running Fresh Rom 0.5.3 or 1.0.0 (testers/donors only right now) then you can get the update by enabling experimental roms in Fresh Updater (more info below). There are 0 changes made to the rom itself other than drivers, all of the changes are in the kernel.
The release notes on this are going to be very brief right now, and so is support. Please report any issues that you guys come across but don’t be too surprised by that due to it’s experimental nature. You all are the testers!
Fresh Toast Features:
* CompCache / ramzswap
o This is actually already included in Fresh Evo, but thanks to the new kernel it is hard coded in there and works a lot better.
* Overclock available up to 1.27ghz, however it doesn’t seem to totally function above about 1.15ghz.
o Only tested with SetCPU. Should also work fine with Overclock Widget. Neither are included.
o If you are reporting OC issues then make sure to say which application you are using. And don’t report it if it’s related to problems when going above 1.1ghz.
* Undervolt — http://en.wikipedia.org/wiki/Dynamic_voltage_scaling#Undervolting
o This lowers the voltage required by the processor at lower clock speeds, thus reducing heat and battery drain.
* Ext4 support — http://en.wikipedia.org/wiki/Ext4
o If using apps2sd then you can convert your ext partition to ext4. Read the wikipedia article for noted benefits.
o You can use AmonRA to convert from ext3 to ext4 without any data loss, just keep in mind that if you try using another rom that doesn’t support ext4 then it won’t be able to read it. Going from ext4 back to ext3 will require re-partitioning your sdcard.
* Both kernels contain extensive tweaks related to speed, power, VM, etc. More details and information to come on all of those tweaks.
* Brain F**k Scheduler aka BFS (optional) – http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
o One version of the kernel includes BFS and one doesn’t. BFS will definitely make your phone run faster but it’s done with a possible side effect of stability. Test it out and see if you have any issuers.
o If you are reporting any problems with Fresh Toast then make sure and say if you are using the BFS kernel or not.
o If you aren’t sure what a scheduler is: it’s basically what is responsible for queuing up work for the processor to do. From an engineering standpoint even though we can multitask on our phone, the CPU is technically doing only one thing at a time. A scheduler is what controls which job the CPU is working on and which ones are next. This replaces the stock android one with BFS.
Reporting an issue? Please give us which kernel number you are using (#13 or #20 — you can get this by going to Settings < About Phone < Software Information < Kernel Version) and also which overclock application you are using.
Download:
This can only be downloaded through Fresh Updater, and only if you are on Fresh Evo 0.5.3 or 1.0.0 (testers/donors only for now). Users coming from Fresh Evo 1.0.0 should not have to worry about wiping or doing anything special. If coming from 0.5.3 then a wipe might be required to get it booted, I didn’t test. Fresh Updater also has the kernels included with Fresh Evo so that you can go back to them if you have any issues with Fresh Toast. As always make sure you do a nandroid.
You must enable experimental roms in order to have them show up.
Fresh Updater > Menu > Configuration > Rom Update Settings > Display Experimental Roms — Then check for updates.
{
"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"
}
I'm currently testing out the fresh toast kernels on the DC 3.2.3 rom, I'll post back about my findings soon.
edit: So far it doesn't appear to be working with the DC rom. It's just hanging on boot. I'll give it a bit longer but its already
been sitting on the intial htc EVO 4g logo for 5 minutes.
edit2: I've been unable to get the DC Rom to boot with either of the fresh toast kernels. even with a data wipe. i'm going to try
again.. if anyone else gets it working please post.
Does this have the fps uncap? N if so for which hardware?
madunix said:
Does this have the fps uncap? N if so for which hardware?
Click to expand...
Click to collapse
it does not. given the tearing problem that the toast + epson fps fix kernel has, at this point I just want a kernel
that will enable over/underclocking. the fresh toast kernel fills that niche.
Actually we have been testing this Rom since it came out. Check the last pages of posts here.http://forum.xda-developers.com/showthread.php?t=700448&page=254
cds36 said:
Actually we have been testing this Rom since it came out. Check the last pages of posts here.http://forum.xda-developers.com/showthread.php?t=700448&page=254
Click to expand...
Click to collapse
that thread is about the fresh rom, this thread is about the fresh toast kernel
OneStepAhead said:
it does not. given the tearing problem that the toast + epson fps fix kernel has, at this point I just want a kernel
that will enable over/underclocking. the fresh toast kernel fills that niche.
Click to expand...
Click to collapse
How is it functioning on DC 2.3.2?
blassilando said:
How is it functioning on DC 2.3.3?
Click to expand...
Click to collapse
so far its not booting. i'm going to try a data wipe, but i didn't think that was necessary with kernels.
Relax just saying it is being talked about in his fresh rom thread. http://forum.xda-developers.com/showthread.php?t=700448&page=248 anyone else can reference that as well as this thread.
cds36 said:
Relax just saying it is being talked about in his fresh rom thread. http://forum.xda-developers.com/showthread.php?t=700448&page=248 anyone else can reference that as well as this thread.
Click to expand...
Click to collapse
sorry if i said something to offend you.. it was not my intention at all
OneStepAhead said:
sorry if i said something to offend you.. it was not my intention at all
Click to expand...
Click to collapse
No not at all man, no worries good to have a thread just for this rom. Flipz is doing some amazing work. I have installed a few roms and fresh has been the most stable for me. With this new kernel Rom for the first time I have seen a huge improvement in battery life. Can't wait to see what version 1 brings
does this kernel support the cams? didnt read anything one way or the other yet.
mr_black03 said:
does this kernel support the cams? didnt read anything one way or the other yet.
Click to expand...
Click to collapse
Both work correctly.
If u wanna use my binary in dc or anything else ull have to extract the binary kernel from the boot.img and compile it with the ramdisk from the Rom u are going to flash it to. Also ill need to modify the ramdisk to run compache/ ramzswap scripts and grab the modules from the fresh toast build also. Add all that to ur build and flash the newly compiled boot.img and u should be toasted up
No Problems
No problems here - Flashed using Amon_RA recovery. Running Fresh 0.5.3 ROM.
Quick question - I've been running the Fresh Toast kernal with BFS pretty nicely for about a day now, but I'm still unsure about a few things. How does the undervolting work? Is it automatic if I underclock the CPU, or is it always undervolted? Right now I have SetCPU set to a max of 1152.
nowhere2010 said:
No problems here - Flashed using Amon_RA recovery. Running Fresh 0.5.3 ROM.
Click to expand...
Click to collapse
which one of the kernels are you using
toastcfh said:
If u wanna use my binary in dc or anything else ull have to extract the binary kernel from the boot.img and compile it with the ramdisk from the Rom u are going to flash it to. Also ill need to modify the ramdisk to run compache/ ramzswap scripts and grab the modules from the fresh toast build also. Add all that to ur build and flash the newly compiled boot.img and u should be toasted up
Click to expand...
Click to collapse
thanks, sounds like i have some more learning to do before I could pull something like that off. i'm unemployed at the moment so time is on my side
OneStepAhead said:
which one of the kernels are you using
Click to expand...
Click to collapse
I'm using the one with no BFS.
I just flashed the bfs kernel coming from the latest fresh Rom. I went toast CPU and my max is at 599????

[DEV] Porting Photon kernel 2.6.32 here

. .
cardsharing said:
Hi all developers, i open this thread about porting kernel for photon here. Im working on it and here is interested stuf about bcm4329
Click to expand...
Click to collapse
good link, will follow it!
i'm sure we can find useful stuff on 2.6.32 and backport on 2.6.29.
differences between arch/arm/msm on both versions are quite big, thus im not sure how easy it is to upgrade photon kernel.
i found a way to get some terminal console and some debug outbut:
just install the HTC Sync for HTC Aria, it gives you the USB ADB driver: link here
Then, in a command window, execute following commands:
Code:
adb devices => tells you if your device is recognized
adb shell => launch a basic linux shell
type "dmesg" to have the debug message
"dmesg | /bin/more" to have the same but page by page (press space enter to go next page)
you can also install android applications:
adb install <name of file>
Click to expand...
Click to collapse
at first look, you can see the kernel is compiled with loaaads of debug output.
and we can already see a recurrent segfault that might be the cause of some of the issues we have.
Note: adb.exe enclosed in zip file of this message
Maybe it's a good idea to make a list of all issues we experience at this moment in the first post. That way, we can handle them one by one
This is my list now:
- Battery driver doesn't work.
- Maybe that has to do with the battery driver, but when I use my device with Android for about a half an hour (Angry Birds), the back side comes very warm...
- Data not working (WiFi and GPRS as well)
- Buttons need realignment
- Sometimes it happens that when I turn my device off just with the power button, the lights under the hardware keys keep going.
guys have you seen here?
http://forum.xda-developers.com/showpost.php?p=11390094&postcount=6
Kernel 2.6.32 with Android 2.3 on HTC Aria!
{
"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"
}
I'm trying to find where they got the kernel 2.6.32, in cyanogen repository the kernel stops at 2.6.29:
https://github.com/CyanogenMod/htc-kernel-liberty
-r0bin- said:
guys have you seen here?
http://forum.xda-developers.com/showpost.php?p=11390094&postcount=6
Kernel 2.6.32 with Android 2.3 on Aria!
Click to expand...
Click to collapse
And can we get Aria kernel working on Photon? Can you do this?
_Madmatt said:
And can we get Aria kernel working on Photon? Can you do this?
Click to expand...
Click to collapse
yes, cotulla used the kernel of liberty (which is HTC Aria)
actually I think I found the latest kernel \o/
https://github.com/attn1/htc-kernel-msm7227
done by attn1, main contributor of cyanogen for HTC Aria/Liberty
let's try this!!!
-r0bin- said:
yes, cotulla used the kernel of liberty (which is HTC Aria)
actually I think I found the latest kernel \o/
https://github.com/attn1/htc-kernel-msm7227
done by attn1, main contributor of cyanogen for HTC Aria/Liberty
let's try this!!!
Click to expand...
Click to collapse
Try? Shouldn't we do some modifications first?
_Madmatt said:
Try? Shouldn't we do some modifications first?
Click to expand...
Click to collapse
yes, we need to implement cotulla's patch
seems he duplicated the "liberty" files to "photon" in arch/arm/msm and did light modifications
we can do a diff vs the htc aria official source code to have it all
-r0bin- said:
yes, we need to implement cotulla's patch
seems he duplicated the "liberty" files to "photon" in arch/arm/msm and did light modifications
we can do a diff vs the htc aria official source code to have it all
Click to expand...
Click to collapse
Can you do that? I don't have enough Linux knowledge But I'm always ready to try kernels
-r0bin- said:
yes, we need to implement cotulla's patch
seems he duplicated the "liberty" files to "photon" in arch/arm/msm and did light modifications
we can do a diff vs the htc aria official source code to have it all
Click to expand...
Click to collapse
Attention!
i do not want to pick at cotulla, but in fact we want to use his changes for another port it is to say: his code is kind of mess
you can really see that he stopped working on it instantly..
Either someone cleans this up or you will really have to understand what he intended to do!
schlund said:
Attention!
i do not want to pick at cotulla, but in fact we want to use his changes for another port it is to say: his code is kind of mess
you can really see that he stopped working on it instantly..
Either someone cleans this up or you will really have to understand what he intended to do!
Click to expand...
Click to collapse
Well..I think the reason he stopped instantly is here
Cotulla dumped the project few hours after this post,some of you may call it coincidence,but i think Cotulla was reading what we were writting there.
helping someone who is swearing you work is....(i don't wanna use bad words)
if i were him i will do exactly the same!
we need to be thankful that he even released the working haret for us
. .
who can tell ...
hi I want to know about how to custom the haret image. and how to solve the connect problem. so does the battery. so just tell me the general steps.. I am willing to test the image. thanks all the developers.
cardsharing said:
Guys i will post tomorow here all modified 2.6.32 files, dont have time to upload in this time.
Click to expand...
Click to collapse
yeah we'll all be interested to have that.
cardsharing said:
P.S. tracaplaca my english is bad and im sorry for this, ok? PLEASE froget me and my post and please dont post here if your post is not about developming, PLEASE, OK? Cotulla have donatins from me ten minutes after his post abut working photon project and this was my big thanks to big Cotula. So please forget all old posts and please back to post, ok?
Click to expand...
Click to collapse
hey guys don't fight
schlund said:
Attention!
i do not want to pick at cotulla, but in fact we want to use his changes for another port it is to say: his code is kind of mess
you can really see that he stopped working on it instantly..
Either someone cleans this up or you will really have to understand what he intended to do!
Click to expand...
Click to collapse
agree with you.
i'm not sure every single modification is required (code looks like "modif here, compile and see if it works better"), but it's incredible chance to have a working source code and we all thanks cotulla for his work. this way we have a chance to have a clean code starting from the liberty/aria source code.
it seems he tried to investigate the wifi issue (many wifi files modified compare to liberty) but with no luck.
in the kernel configuration he released, he said we could get the kernel debug traces on the PC.
do you guys know how to get it? plugging usb cable when android is booting does not seems to help.
reason I'm asking is, it seems there are lot of debug informations available but so far i cannot access to them...
-r0bin- said:
agree with you.
i'm not sure every single modification is required (code looks like "modif here, compile and see if it works better"), but it's incredible chance to have a working source code and we all thanks cotulla for his work. this way we have a chance to have a clean code starting from the liberty/aria source code.
it seems he tried to investigate the wifi issue (many wifi files modified compare to liberty) but with no luck.
in the kernel configuration he released, he said we could get the kernel debug traces on the PC.
do you guys know how to get it? plugging usb cable when android is booting does not seems to help.
reason I'm asking is, it seems there are lot of debug informations available but so far i cannot access to them...
Click to expand...
Click to collapse
maybe is this
http://droidbar.net/2010/09/how-to-enable-usb-debugging-mode/
That option is enabled by default on the 2.2. image that have been posted.
I think you have to use adb tool as said here to see the output.
. .
thanks! yeah you see it takes time
can you compile the kernel and send the zImage as well?
. .

[ROM]Flytouch 5 ICS Custom Firmware: The Blazing Dragon

Blazing Dragon ICS 2.1.1 - Android 4.0.3 - Made by Gaboros​
{
"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"
}
I am not responsible for any damage in your device. Use everything at your own risk and only if you sure you have the proper device!
Please read the FAQ before you post any question!​
Blazing Dragon ICS 2.1.1: http://www.mediafire.com/download.php?fzzaci4fzhr5a15
System app updates for 2.1.1 - 13-10-2012: http://www.mediafire.com/?9q4wd8wtc2bj58t
More high resolution screen shots: https://www.dropbox.com/sh/1kxjg8v21450ia0/hm-_kMywZj
Full installation and upgrade guide: http://www.text-upload.com/read,t11139
Previous Stock and Blazing Dragon ICS ROMs:
Stock ROMs for flash tool: http://www.mediafire.com/?7tq77i9ot5ks5
Blazing Dragon ICS ROMs for CWM recovery: http://www.mediafire.com/?x984448bo4g1g
Current features:
Code:
Android 4.0.3.
Deodexed.
Whole system structure change.
CWM based update.
Supports ad hoc network.
Designed for 10" instead of 7".
Has root by default.
Different boot.img.
Changed system apks.
Based on stock 0502.
Custom boot animation support.
The screen calibrate itself on first boot.
Market let you download more app then stock.
Pinch-to-zoom.
A lot of small improvement.
Statusbar toggle buttons.
Full changelog which contains every releases: http://www.text-upload.com/read,t11248
Full credits list: http://www.text-upload.com/read,t11056
Click here to donate​
Thank you! works very good!
I'm so proud I could cry lol
I'll get to work pulling the apps and framework and deodixng for you, I'll see if I can grab the framework and bluetooth drivers from 314 and port them over.
Thank you again! I'm also proud lol.
Deodexing not worked for me yesterday. The deodexing script went great, it deodexed every apk and framework jar from the system, but after pushing them back, it just gave me a boot loop.
I'm also working on it.
Im a noob at flashing roms. Can you please list the step by step
Download the flash tool and the rom, but in the same folder both. Press the reset on your tablet and when you release immediately press the menu+power button. In the flash tool select the ini file depend on you have 512 or 1 gb and for the other slot the vortex.pak and press the button... this is the short version
You can found the long here:
http://www.apad.tv/apadforum/showthread.php?2066-ibex-Flytouch-5-Wopad-System-Update
Ok does anyone know if i have the right tablet??
Model number: Android Tab10
Android Version: v2.2
Kernel version 2.6.32.9
Build number FRF85B
I have the ibex Flytouch 4 apad. will this work for me?? The link to the step by step was for the flytouch 5 wopad. I just want to be absolutely sure cuz I would really hate to brick this thing
ClicquotRose said:
Ok does anyone know if i have the right tablet??
Model number: Android Tab10
Android Version: v2.2
Kernel version 2.6.32.9
Build number FRF85B
Click to expand...
Click to collapse
I don't think so...
ClicquotRose said:
I have the ibex Flytouch 4 apad. will this work for me?? The link to the step by step was for the flytouch 5 wopad. I just want to be absolutely sure cuz I would really hate to brick this thing
Click to expand...
Click to collapse
I don't know... I know that the Flytouch 5 and 6 is the same but I don't know about the 4, sorry.
you need a cortex a8 which is: Flytouch 4s/5s/6/7/V10
one question: i have a huge battery drain. do you have this also?
Does bluestack drain the battery ?
naf said:
you need a cortex a8 which is: Flytouch 4s/5s/6/7/V10
one question: i have a huge battery drain. do you have this also?
Click to expand...
Click to collapse
Better drain is the bug of the stock rom, and because we don't have the source I haven't found a workaround yet. Hopefully it will be fixed in the stock rom soon. One thing is for sure: it not use deep idle mod, so it almost drain as fast as when your screen is off, when it on. (except the screen, of course). But if you power off your device totally when you not use it and it only turned on when you use it, the battery just similar to 2.3.
http://ap.viewsonic.com/my/kbase/article.php?id=728
This is the kernel source from viewpad 10s VC882 Cortex a8
also discussed here:
http://forum.xda-developers.com/showthread.php?t=1617759
naf said:
http://ap.viewsonic.com/my/kbase/article.php?id=728
This is the kernel source from viewpad 10s VC882 Cortex a8
also discussed here:
http://forum.xda-developers.com/showthread.php?t=1617759
Click to expand...
Click to collapse
Wow! Thanks! But I don't think this is the same device but it could work... to tell you the truth I not really want to modify the kernel. It could be dangerous... But I take a look at it.
Yesterday I got a weird idea. Port the Clockworkmod recovery to our device.
It could be very useful but currently I don't know I have enough knowledge to do that.
Edit: just now see what you linked contain the source of the recovery... I just try to compile it, and see is it working on our device or not. Maybe we have a change to clockwork recovery?
I just got a tablet as a gift. On the box it says SuperPad VI, but on the sales receipt it says Tablet PC SuperPad IV. In settings it just says MID. Is it one of those tablets you are speaking of here? I would like to root it. Sorry it is my first tablet and i am still a noob on it.
claus1953 said:
I just got a tablet as a gift. On the box it says SuperPad VI, but on the sales receipt it says Tablet PC SuperPad IV. In settings it just says MID. Is it one of those tablets you are speaking of here? I would like to root it. Sorry it is my first tablet and i am still a noob on it.
Click to expand...
Click to collapse
As mentioned before my naf:
you need a cortex a8 which is: Flytouch 4s/5s/6/7/V10
So it should work.
do you have android 2.2 installed? then 90% possibility of being a ft4. android 2.3 could be a superpad 6. or FT6
If you're not sure what tablet you have then download any of the benchmarking apps off the market and see what CPU it says you have.
If it says it's an X220 then you have a DISCO, P041 or SAWEE these are Froyo 2.2, there's some that have been sold with the build.prop edited to say they are Gingerbread 2.3 but they aren't, they are still 2.2
If it's a Cortex A8 then this rom will work on it, but only if it's a 10 inch resistive screen.
Thanks for your answers, i installed android system info and it gives following data among other
Andriod version 2.3
cpu abi armeabi v7a
maker vimicro
device vortex
screen 1024x600 160 dpi
processor armv7 processor rev 2
vimicro vortex android 2.3.... you have a superpad VI...
This is the Mediafire Folder from Gaboros:
http://www.mediafire.com/?0zcplz34db4pq
there you will find your firmware and flashtools...

[32A/B?][6.35] Cyanogenmod 9 -- Fast | Stable | Best

I ported Cyanogenmod 9 for the Hero build by Jordfaz. (Thanks to him!)
{
"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"
}
Downloadlink: Cyanogenmod 9
Installation:
- Flash Lights_format_all (See other thread!)
- Flash CM9
- Reboot
- 32B: Flash a 32B kernel after flash of the ROM
After installation
- After boot: Go to ADWSettings - system - advanced - enable wallpaper hack and scroll cache: low quality --> This will fix your UI.
- To disable CRT-animation: Displays - animation OFF (Thanks toi SaySpaceman! ;p)
Working:
- Calls/SMS
- Data
- Youtube!
- Screenshot!
- Perfect rotation!
- ...
Not working:
- Bluetooth
- GPS
Changelog:
Code:
-- Cyanogenmod 9 --
v1.0
* Initial release
Hit the THANKS button, if you use this ROM!
I will complete this thread at a later time, but for the next month I'll have to study a lot , so maybe no time for uploading and completing thread.
You can disable the CRT animation. You go to Settings->Display->You turn off the Screen off animation.
I haven't found any bugs yet, everything works very smooth and even YouTube works! :good:
I think this is the best ROM for our "legacy" device
SaySpaceman said:
You can disable the CRT animation. You go to Settings->Display->You turn off the Screen off animation.
I haven't found any bugs yet, everything works very smooth and even YouTube works! :good:
I think this is the best ROM for our "legacy" device
Click to expand...
Click to collapse
Thank you! Didn't know you could manually enable/disable it.
i really want to try this rom in my old htc magic!
I would like to know wich recovery do you use and recommend to flash your rom.
another question is the funcionability of the apps with this rom
thank you for all your work for "our" device.
stiker said:
i really want to try this rom in my old htc magic!
I would like to know wich recovery do you use and recommend to flash your rom.
another question is the funcionability of the apps with this rom
thank you for all your work for "our" device.
Click to expand...
Click to collapse
I think you can only flash it with CWM recovery.
All apps that work on GB, will work in ICS.
But the Play Store will show a lot more apps, but a lot of them will force close when you try to open them.
But in general, everything should be smoother.
ok. This rom is good. But it is slow when download from playstore. Thanks!
Thanks for CM9, i was looking for some stable rom
I will try this ROM and will let u know my findings
Thank you for porting this over. I have neglected my HTC Magic for quite some time now, finally got it out, dusted it and went through the flashing bits for this. Stable and much smoother than I expected to have on a (relatively) dated device. Are the processor options under 'Performance' settings disabled or is it meant to be on 'ondemand' all the time?
Yanguang said:
Thank you for porting this over. I have neglected my HTC Magic for quite some time now, finally got it out, dusted it and went through the flashing bits for this. Stable and much smoother than I expected to have on a (relatively) dated device. Are the processor options under 'Performance' settings disabled or is it meant to be on 'ondemand' all the time?
Click to expand...
Click to collapse
You can't change any options in Performance. I'll see if I can change that, because now, if the displayed CPU speeds are right, the CPU is constantly running on 710 Mhz when you used it.
Default cpu frequence 710MHz is not stable enough to bootup my phone, could you please lower down to 650MHz please?
jejer said:
Default cpu frequence 710MHz is not stable enough to bootup my phone, could you please lower down to 650MHz please?
Click to expand...
Click to collapse
Did you try to flash it? My phone doesn't run on 710 either, but it does boot.
Yes, I flashed it. During boot, cat /proc/cpuinfo get 710MHz and boot failed. After set it to 620MHz, it bootup success.
Your ROM works great, thanks!
jejer said:
Yes, I flashed it. During boot, cat /proc/cpuinfo get 710MHz and boot failed. After set it to 620MHz, it bootup success.
Your ROM works great, thanks!
Click to expand...
Click to collapse
Ok, thanks! I'll set it to a lower speed in next version.
I would really advise against overclocking by default. The majority of these devices can overclock to acceptable speeds, but others can't do much at all. My mytouch 3g, for example, would freeze at anything above 595mhz, and it was most stable at 537 or below. So even with that lower overclock you decided on, I still wouldn't be able to use this without modifying the rom.
There are plenty of ways to make this recommended, but optional. You could put an oc script in a separate zip to flash. Or you could start using the fancy Aroma installer. Ezterry's yesno binary is really easy to implement.
tvall said:
I would really advise against overclocking by default. The majority of these devices can overclock to acceptable speeds, but others can't do much at all. My mytouch 3g, for example, would freeze at anything above 595mhz, and it was most stable at 537 or below. So even with that lower overclock you decided on, I still wouldn't be able to use this without modifying the rom.
There are plenty of ways to make this recommended, but optional. You could put an oc script in a separate zip to flash. Or you could start using the fancy Aroma installer. Ezterry's yesno binary is really easy to implement.
Click to expand...
Click to collapse
I didn't know the cpu was running at a higher speed. I thought it was a bug in performance section, who was showing the wrong speed, since my HTC Magic normally freezes at 710 Mhz.
It's been years since I last flashed a MyTouch3G (32B)... Just got back one that I'd gifted away two years ago, it decided not to boot around Christmas and I brought it home to wipe/reflash.
Glad to see work still being done on this old device! It's ahead of my G2X in Roms.. That's effin sad.
Now if I can just remember how you flash a kernel on this thing....
EDIT:
I'm a bit confused about the kernel.... the thread linked doesn't actually seem to be any specific kernel??? More "how to flash a kernel safely" and hboot/radio files. I already have the required hboot/radio! So which kernel do I use??
EDIT 2:
N/m.... can't be assed to sit here all night trying to figure out which kernel to use on an antique phone. Went with Gingerbread instead.
tutorial and links - SPL/radio/ROM
lotherius said:
It's been years since I last flashed a MyTouch3G (32B)... Just got back one that I'd gifted away two years ago, it decided not to boot around Christmas and I brought it home to wipe/reflash.
Glad to see work still being done on this old device! It's ahead of my G2X in Roms.. That's effin sad.
Now if I can just remember how you flash a kernel on this thing....
EDIT:
I'm a bit confused about the kernel.... the thread linked doesn't actually seem to be any specific kernel??? More "how to flash a kernel safely" and hboot/radio files. I already have the required hboot/radio! So which kernel do I use??
EDIT 2:
N/m.... can't be assed to sit here all night trying to figure out which kernel to use on an antique phone. Went with Gingerbread instead.
Click to expand...
Click to collapse
<<Check my signature below!>>
<<Goog flashing>>
Edited post (correction below)
Sorry for the wrong info on flashing your 32B device, I did not notice that your device was not a 32A sapphire but the 32B instead!
I think the answer you're looking for is here:
[ROM][WIP] United ICS - http://forum.xda-developers.com/showthread.php?t=1647493
"kernel -
ezterry's kernel + ics patches and some performance tweaks (enabled 710mhz overclock and other things) http://www.mediafire.com/?py8asp6ab109dyl
ezterry's ezgb 1.5.2 http://sandbox.devnull.name/android/ezgb-kernel/ezgb-2636-v1.5.2_S.zip "
<< info from tvall - http://forum.xda-developers.com/member.php?u=3038499 >>
lotherius said:
It's been years since I last flashed a MyTouch3G (32B)... Just got back one that I'd gifted away two years ago, it decided not to boot around Christmas and I brought it home to wipe/reflash.
Glad to see work still being done on this old device! It's ahead of my G2X in Roms.. That's effin sad.
Now if I can just remember how you flash a kernel on this thing....
EDIT:
I'm a bit confused about the kernel.... the thread linked doesn't actually seem to be any specific kernel??? More "how to flash a kernel safely" and hboot/radio files. I already have the required hboot/radio! So which kernel do I use??
EDIT 2:
N/m.... can't be assed to sit here all night trying to figure out which kernel to use on an antique phone. Went with Gingerbread instead.
Click to expand...
Click to collapse
You have to take a working 32B kernel, preferably a flashable zip. The link in the opening post isn't directing to a kernel, but search for it in the G1 section and you will find a lot kernels.
ICS is much faster, so I would suggest you try it.
Can you point me into the right direction? My dad has an old Magic 32B with Radio 27.08. What Kernel should i use? Or what ICS Version are you talking about?
Thanks in advance.
when is out the final version?

Need info about touchscreen related files on LineageOS.

Hi People!
I have an SM-T355Y which does not have any official or unofficial LineageOS ports. So, I am using a ROM for a similar device (SM-T350) which has some unofficial ROMs..
The screen has some scaling difference between the SM-T350 and T-355Y models due to which touches in around 75% of the screen get scaled to entire 100% - so to click something at the right bottom corner, I have to touch a point which is around 1.5 inches from bottom and 0.5 inches from right. Crude representation below:
Touching blue point will click at orange point:
{
"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"
}
Is there some config file that I can edit to scale the touch response so that I get the click below the point I touch?
Or is there a 'mapping' file that I can use?
Do let me know if I can try some other tricks.
Rahul.raj said:
Hi People!
I have an SM-T355Y which does not have any official or unofficial LineageOS ports. So, I am using a ROM for a similar device (SM-T350) which has some unofficial ROMs..
The screen has some scaling difference between the SM-T350 and T-355Y models due to which touches in around 75% of the screen get scaled to entire 100% - so to click something at the right bottom corner, I have to touch a point which is around 1.5 inches from bottom and 0.5 inches from right. Crude representation below:
Touching blue point will click at orange point:
Is there some config file that I can edit to scale the touch response so that I get the click below the point I touch?
Or is there a 'mapping' file that I can use?
Do let me know if I can try some other tricks.
Click to expand...
Click to collapse
You need a kernel that is compatible with your model number. Your device and the similar device have slightly different hardware, therefore, the kernel from the other device is slightly different than yours.
This isn't the kind of thing where you can just edit some system files, this has to be done by installing a compatible kernel. You will have to try finding a kernel that is already made for your specific model number or you will have to build a new kernel from the ground up yourself by compiling the new kernel using the source code for your device(if it is available). Or, you can try using a kernel from other similar devices. Or, you can try porting a kernel to make it work on your device.
If you are lucky, you might find something that is already compatible that you can just install as it is. If you can't find something compatible, you'll have to compile a new kernel or port an existing kernel.
Droidriven said:
<...>
Click to expand...
Click to collapse
Thanks for the guidance.
Possibly dumb questions:
1. Can a kernel specifically compiled for my device be 'flashed' into the currently installed setup, through PC or TWRP, or do I need to 'integrate' it into the ROM and flash the ROM again?
2. As I said, my device is unsupported by LineageOS. What would be a good resource for me to follow to build a device specific kernel?
Rahul.raj said:
Thanks for the guidance.
Possibly dumb questions:
1. Can a kernel specifically compiled for my device be 'flashed' into the currently installed setup, through PC or TWRP, or do I need to 'integrate' it into the ROM and flash the ROM again?
2. As I said, my device is unsupported by LineageOS. What would be a good resource for me to follow to build a device specific kernel?
Click to expand...
Click to collapse
1) the kernel can be flashed via TWRP if it has been converted into a flashable .zip file, can can take a copy of your lineageOS ROM .zip and delete the ROM system.img from the .zip and replace it with the kernel file. It is risky if you don't edit the .zip file correctly, you might want to consider using a method that converts your kernel file directly into a flashable .zip the same way ROM .zips are created.
2)first, you need to do some Google searching to see if your device's stock kernel source has been released to the public. If it isn't publicly available, you will not be able to build a device specific kernel. Or you can try finding LineageOS ROMs for similar devices and extract the kernel from those ROMs and flash them on your device. You could also find the lineagOS kernel source code for those other devices/ROMs and try compiling your own kernel from those lineageOS kernel sources.
Thanks a ton for the feedback.
There is no ROM/ kernel for my device and the 'similar' device has the scaling issue.
Having said that there was a Marshmallow kernel from Ashyx: But I am not confident that it will work with a Nougat ROM.
I looked at the compile instructions for LineageOS, but that has a step where it needs to download proprietary files from a device already running LineageOS ROM. Kind of chicken and egg problem it seems.
Looks like there is no way ahead on this.

Categories

Resources